• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    This document provides a method for an originating base station to transmit a Quality of Service (QoS) flow mapping rule for radio data carrier (DRB) to a destination base station in a wireless communication system and a device that supports the method. The method may comprise: a step of receiving a measurement result from a target cell, from a terminal; a step to determine the transfer of the terminal to a destination base station, based on the measurement result; and a step of transmitting a transfer request message including a rule for mapping QoS flow to DRB from a source base station to the destination base station.
    公开号:BR112019000608B1
    申请号:R112019000608-7
    申请日:2018-01-05
    公开日:2021-02-09
    发明作者:Jian Xu；Daewook Byun；Seokjung KIM；Sunyoung Lee
    申请人:Lg Electronics Inc；
    IPC主号:
    专利说明:

    BACKGROUND OF THE INVENTION Field of Invention
    [001] The present invention relates to a wireless communication system and, more particularly, to a method for transmitting, through a base station, a rule for quality of service (QoS) flow mapping for radio data bearer (DRB) and a device that supports it. Correlated Technique
    [002] Quality of Service (QoS) refers to the technology to transmit various types of traffic (mail, data transmission, sounds or images) to end users, depending on their characteristics. The most fundamental QoS parameter is bandwidth, cell transfer delay (CTD), cell delay variation (CDV) or cell loss rate (CLR).
    [003] In order to meet the demand for wireless data traffic, which has been increasing since the commercialization of a fourth generation (4G) communication system, efforts are being made to develop a fifth generation (5G) communication system or pre-5G communication system. For this reason, a 5G communication system or pre-5G communication system is referred to as a network communication system in addition to 4G or a post-long term evolution (LTE) system. SUMMARY OF THE INVENTION
    [004] With the introduction of the concept of a QoS flow for data packet transmission between a 5G core network and a new RAN, a rule for mapping QoS to a DRB is necessary. However, a base station (BS) cannot know a flow mapping rule from QoS to DRB to a neighboring BS. Thus, for example, when a user equipment (UE) is transferred from the BS to the neighboring BS, the neighboring BS cannot determine which QoS flow mapping rule to neighboring DRB BS needs to apply to the UE. When BSs have different QoS-to-DRB flow mapping rules, for example, a destination BS may not correctly transmit a packet forwarded from a source BS to a UE. Therefore, QoS to DRB flow mapping rules need to be shared between BSs.
    [005] One modality provides a method for transmitting, by a source base station, a rule for mapping the QoS flow for radio data carrier (DRB) to a destination base station in a wireless communication system. The method may include: receipt of user equipment (UE), a measurement result from a target cell; determining a handover from the UE to the destination base station, based on the measurement result; and transmitting a transfer request message to the destination base station including the rule for QoS to DRB flow mapping from the originating base station.
    [006] Another modality provides a method for transmitting, through a master base station, a rule for mapping the Quality of Service (QoS) flow to the radio carrier (DRB) to a secondary base station in a wireless communication system. The method may include: receipt of user equipment (UE), a measurement result from the secondary base station; determining a data download to the secondary base station, based on the measurement result; and transmission, to the secondary base station, of the rule for the QoS to DRB flow mapping of the main base station.
    [007] Another modality provides a source base station for transmitting a rule for mapping the Quality of Service (QoS) flow to radio carrier data (DRB) to a destination base station in a wireless communication system. The originating base station can include a memory; a transceiver; and a processor, connected with the memory and the transceiver, which: controls the transceiver to receive, from a user equipment (UE), a measurement result from a target cell; determines a transfer from the UE to the destination base station, based on the measurement result; and controls the transceiver to transmit a transfer request message to the destination base station including the rule for QoS to DRB flow mapping from the originating base station.
    [008] A rule for flow mapping from QoS to DRB can be shared between base stations. BRIEF DESCRIPTION OF THE DRAWINGS
    [009] Figure 1 shows an architecture of the LTE system.
    [010] Figure 2 shows a control plan for an LTE system radio interface protocol.
    [011] Figure 3 shows a user plan of an LTE system radio interface protocol.
    [012] Figure 4 shows a 5G system architecture.
    [013] Figure 5 shows a 5G system wireless interface protocol for a user plan.
    [014] Figure 6 shows the mapping between a QoS and DRB flow.
    [015] Figure 7 shows a procedure for forwarding a flow mapping rule from QoS to DRB in a transfer procedure according to an embodiment of the present invention.
    [016] Figures 8A and 8B show a procedure for forwarding a flow mapping rule from QoS to DRB in an unloading procedure in accordance with an embodiment of the present invention.
    [017] Figure 9 shows a procedure for forwarding a flow mapping rule from QoS to DRB in an Xn interface configuration procedure according to an embodiment of the present invention.
    [018] Figure 10 shows a procedure for forwarding a flow mapping rule from QoS to DRB in an Xn interface configuration update procedure according to an embodiment of the present invention.
    [019] Figures 11A and 11B show a procedure for forwarding a flow mapping rule from QoS to DRB in a transfer procedure according to an embodiment of the present invention.
    [020] Figures 12A and 12B show a procedure for forwarding a QoS flow packet in a transfer procedure according to an embodiment of the present invention.
    [021] Figure 13 is a block diagram illustrating a method in which a source BS transmits a flow mapping rule from QoS to DRB to a destination BS according to an embodiment of the present invention.
    [022] Figure 14 is a block diagram illustrating a method in which a master BS transmits a flow mapping rule from QoS to DRB to a secondary BS according to an embodiment of the present invention.
    [023] Figure 15 is a block diagram illustrating a wireless communication system in accordance with the modality of the present invention. DESCRIPTION OF EXAMPLE MODALITIES
    [024] The technology described below can be used in various wireless communication systems, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA). Multiple access by single carrier frequency division (SC-FDMA), etc. CDMA can be implemented with radio technology, such as universal access to terrestrial radio (UTRA) or CDMA-2000. TDMA can be implemented with radio technology such as the global system for mobile communications (GSM) / general packet rate service (GPRS) / enhanced data rate for GSM evolution (EDGE). OFDMA can be implemented with radio technology such as the institute of electrical and electronic engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UTRA (ETRATRA), etc. IEEE 802.16m has evolved from IEEE 802.16e, and provides backward compatibility of a system based on IEEE 802.16e. UTRA is part of a universal mobile telecommunications system (UMTS). The Long Term Evolution (LTE) 3rd generation (3GPP) partnership project is part of a UMTS (E-UMTS) evolved using E-UTRA. 3GPP LTE uses OFDMA on a downlink and uses SC-FDMA on an uplink. LTE-advanced (LTE-A) is an evolution of LTE. 5G is an evolution of LTE-A.
    [025] For clarity, the following description will focus on LTE-A. However, the technical characteristics of the present invention are not limited to them.
    [026] Figure 1 shows an architecture of the LTE system. The communication network is widely deployed to provide a variety of communication services, such as voice over internet protocol (VoIP) through IMS and packet data.
    [027] With reference to figure 1, the architecture of the LTE system includes one or more user equipment (UE; 10), an evolved UMTS terrestrial radio access network (E-UTRAN) and an evolved packet core (EPC) . The UE 10 refers to communication equipment carried by a user. UE 10 can be fixed or mobile and can be referred to as other terminology, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, etc.
    [028] E-UTRAN includes one or more evolved B-nodes (eNB) 20, and a plurality of UEs can be located in a cell. ENB 20 provides an end point of a control plan and a user plan for the UE 10. The eNB 20 is generally a fixed station that communicates with the UE 10 and can be referred to as another terminology, such as a base station (BS), a base transceiver system (BTS), an access point, etc. An eNB 20 can be implanted per cell. There is one or more cells within the eNB 20 coverage. A single cell is configured to have one of the selected bandwidths of 1.25, 2.5, 5, 10 and 20 MHz, etc., and provides data transmission services. downlink or uplink for multiple UEs. In that case, different cells can be configured to provide different bandwidths.
    [029] From now on, a downlink (DL) denotes communication from eNB 20 in relation to UE 10, and an uplink (UL) denotes communication from UE 10 to eNB 20. In DL, a transmitter can be a part of eNB 20, and a receiver can be a part of UE 10. In UL, the transmitter can be a part of UE 10 and the receiver can be a part of eNB 20.
    [030] The EPC includes a mobility management entity (MME) in charge of the control plan functions, and a system architecture evolution gateway (SAE) that is responsible for the user plan functions. The MME / S-GW 30 can be positioned at the end of the network and connected to an external network. The MME has access information to the UE or capacity information from the UE, and this information can be used mainly in the management of mobility of the UE. The S-GW is a gateway of which a terminal is an E-UTRAN. The MME / S-GW 30 provides a session endpoint and mobility management function for the UE 10. The EPC may further include a packet data network (PDN) gateway (PDN-GW). The PDN-GW is a gateway of which an endpoint is a PDN.
    [031] The MME provides several functions, including non-access layer (NAS) signaling for eNBs 20, NAS signaling security, access layer security (AS) control, Inter core (CN) network node signaling for mobility between 3GPP access networks, idle UE reach capability (including paging relay control and execution), tracking area list management (for idle and active UE), P-GW and S- selection GW, MME selection for transfers with MME change, selection of GRPS support node in service (SGSN) for transfers to 2G or 3G 3GPP access networks, roaming, authentication, carrier management functions including establishment of dedicated support, system support public warning (PWS) (which includes earthquake and tsunami warning system (ETWS) and commercial mobile alert system (CMAS) message transmission). The S-GW host offers several functions, including packet filtering per user (for example, deep packet inspection), legal interception, allocation of Internet Protocol (IP) addresses, transport level packet marking at the service level DL, UL and DL, gating and rate application, DL rate application based on APN-AMBR. For clarity, the MME / S-GW 30 will be referred to here simply as a “gateway”, but it is understood that this entity includes both the MME and the S-GW.
    [032] Interfaces for user traffic transmission or traffic control can be used. The UE 10 and eNB 20 are connected via a Uu interface. ENBs 20 are interconnected via an X2 interface. Neighboring eNBs can have a mesh network structure that has the X2 interface. The eNBs 20 are connected to the EPC via an S1 interface. The eNBs 20 are connected to the MME via an S1-MME interface, and are connected to the S-GW via the S1-U interface. The S1 interface supports a many-to-many relationship between the eNB 20 and the MME / S-GW.
    [033] eNB 20 can perform selection functions for gateway 30, routing towards gateway 30 during radio resource control (RRC) activation, paging message scheduling and transmission, broadcast channel scheduling and transmission (BCH), dynamic resource allocation for UEs 10 in both UL and DL, configuration and provisioning of eNB measurements, radio carrier control, radio admission control (RAC) and connection mobility control in the LTE_ACTIVE state. In EPC, and as noted above, gateway 30 can perform paging source functions, LTE_IDLE state management, user plane encryption, SAE carrier control and encryption protection and NAS signaling integrity.
    [034] Figure 2 shows a control plan for an LTE system radio interface protocol. Figure 3 shows a user plan of a radio interface protocol for an LTE system.
    [035] Layers of a radio interface protocol between the UE and the E-UTRAN can be classified into a first layer (L1), a second layer (L2) and a third layer (L3) based on the bottom three layers of the open system interconnection model (OSI) that is well known in the communication system. The radio interface protocol between the UE and the E-UTRAN can be divided horizontally into a physical layer, a data link layer and a network layer, and can be divided vertically into a control plane (plane C) that it is a stack of protocols for transmitting the control signal and a user plane (U plane) which is a stack of protocols for transmitting data information. The radio interface protocol layers exist in pairs in the UE and the E-UTRAN and are responsible for transmitting data from the Uu interface.
    [036] A physical layer (PHY) belongs to L1. The PHY layer provides an upper layer with an information transfer service through a physical channel. The PHY layer is connected to a medium access control (MAC) layer, which is a top layer of the PHY layer, through a transport channel. A physical channel is mapped to the transport channel. Data is transferred between the MAC layer and the PHY layer through the transport channel. Between different PHY layers, that is, a PHY layer of a transmitter and a PHY layer of a receiver, data is transferred through the physical channel using radio resources. The physical channel is modulated using an orthogonal frequency division multiplexing OFDM scheme and uses time and frequency as a radio resource.
    [037] The PHY layer uses multiple channels of physical control. A physical downlink control channel (PDCCH) reports to a UE about the allocation of resources from a paging channel (PCH) and a shared downlink channel (DL-SCH) and hybrid automatic repeat order information (HARQ) related to the DL-SCH. The PDCCH may carry an UL grant to report to the UE on the allocation of UL transmission resources. A physical control format indicator channel (PCFICH) reports the number of OFDM symbols used for PDCCHs to the UE and is transmitted in each subframe. A physical hybrid ARQ indicator channel (PHICH) carries a HARQ acknowledgment (ACK) / non-acknowledgment (NACK) signal in response to UL transmission. A physical uplink control channel (PUCCH) carries UL control information, such as HARQ ACK / NACK for DL transmission, scheduling request and CQI. A shared physical uplink channel (PUSCH) carries a shared UL-uplink (SCH) channel.
    [038] A physical channel consists of a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain. A subframe consists of a plurality of symbols in the time domain. A subframe consists of a plurality of resource blocks (RBs). A RB consists of a plurality of symbols and a plurality of subcarriers. In addition, each subframe can use specific subcarriers of symbols specific to a corresponding subframe for a PDCCH. For example, a first symbol in the subframe can be used for the PDCCH. The PDCCH carries dynamic allocated resources, such as a physical resource block (PRB) and a modulation and coding scheme (MCS). A transmission time interval (TTI), which is a unit time for data transmission, can be equal to a length of a subframe. The length of a subframe can be 1 ms.
    [039] The transport channel is classified into a common transport channel and a dedicated transport channel, depending on whether the channel is shared or not. A DL transport channel for transmitting data from the network to the UE includes a transmission channel (BCH) for transmitting system information, a paging channel (PCH) for transmitting a paging message, a DL-SCH for transmitting user traffic or control signals, etc. DL-SCH supports HARQ, dynamic link adaptation varying the modulation, encoding and transmission power, and allocation of dynamic and semi-static resources. DL-SCH can also allow for cell-wide transmission and the use of beam conformation. System information carries one or more blocks of system information. All blocks of information in the system can be transmitted with the same periodicity. Traffic or control signals from a multimedia broadcast / multicast service (MBMS) can be transmitted via the DL-SCH or a multicast channel (MCH).
    [040] A UL transport channel for transmitting data from the UE to the network includes a random access channel (RACH) for transmitting an initial control message, an UL-SCH for transmitting user traffic or control signals, etc. UL-SCH supports HARQ and dynamic link adaptation by varying the transmission power and potentially modulation and encoding. UL-SCH can also allow the use of beam forming. RACH is normally used for initial access to a cell.
    [041] A MAC layer belongs to L2. The MAC layer provides services for a radio link control (RLC) layer, which is a top layer of the MAC layer, through a logical channel. The MAC layer provides a function for mapping multiple logical channels to multiple transport channels. The MAC layer also provides a logical channel multiplexing function, mapping multiple logical channels to a single transport channel. A MAC sublayer provides data transfer services on logical channels.
    [042] Logical channels are classified into control channels for transferring information from the control plane and traffic channels for transferring information from the user plane, according to a type of information transmitted. That is, a set of logical channel types is defined for different data transfer services offered by the MAC layer. The logical channels are located above the transport channel and are mapped to the transport channels.
    [043] Control channels are used only for transferring information from the control plan. The control channels provided by the MAC layer include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH) and a channel dedicated control (DCCH). BCCH is a downlink channel for transmitting system control information. The PCCH is a downlink channel that transfers paging information and is used when the network does not know a UE's location cell. CCCH is used by UEs that do not have an RRC connection to the network. MCCH is a point-to-multipoint downlink channel used to transmit MBMS control information from the network to an UE. DCCH is a two-way point-to-point channel used by UEs that have an RRC connection that transmits dedicated control information between a UE and the network.
    [044] Traffic channels are used only for the transfer of information from the user plan. The traffic channels provided by the MAC layer include a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH). The DTCH is a point-to-point channel, dedicated to a UE for the transfer of user information and can exist in both the uplink and the downlink. MTCH is a point-to-multipoint downlink channel for transmitting traffic data from the network to the UE.
    [045] Uplink connections between logical channels and transport channels include the DCCH that can be mapped to UL-SCH, the DTCH that can be mapped to UL-SCH and the CCCH that can be mapped to UL-SCH. Downlink connections between logical channels and transport channels include the BCCH that can be mapped to the BCH or DL-SCH, the PCCH that can be mapped to the PCH, the DCCH that can be mapped to the DL-SCH and the DTCH that can be mapped to the DL-SCH, the MCCH which can be mapped to the MCH, and the MTCH which can be mapped to the MCH.
    [046] An RLC layer belongs to L2. The RLC layer provides a function for adjusting a data size, so as to be suitable for a lower layer to transmit the data, concatenating and segmenting the data received from an upper layer in a radio section. In addition, to ensure a variety of quality of service (QoS) required by a radio carrier (RB), the RLC layer provides three modes of operation, that is, a transparent mode (TM), an unrecognized mode (UM) and a recognized mode (AM). AM RLC provides a retransmission function through an automatic retry request (ARQ) for reliable data transmission. Meanwhile, a function of the RLC layer can be implemented with a function block within the MAC layer. In this case, the RLC layer may not exist.
    [047] A layer of packet data convergence protocol (PDCP) belongs to L2. The PDCP layer provides a header compression function that reduces unnecessary control information, so that data transmitted using IP packets, such as IPv4 or IPv6, can be transmitted efficiently over a radio interface that has relatively high bandwidth. small. Header compression increases the efficiency of transmission in the radio section by transmitting only the information needed in a data header. In addition, the PDCP layer provides a security function. The security function includes encryption that prevents third-party inspection and integrity protection that prevents manipulation of third-party data.
    [048] A radio resource control layer (RRC) belongs to L3. The RLC layer is located in the lowest part of L3 and is defined only in the control plane. The RRC layer assumes the role of controlling a radio resource between the UE and the network. For this, the UE and the network exchange an RRC message through the RRC layer. The RRC layer controls logical channels, transport channels and physical channels in relation to the configuration, reconfiguration and release of RBs. An RB is a logical path provided by L1 and L2 for the distribution of data between the UE and the network. That is, RB means a service provided to L2 for data transmission between the UE and the E-UTRAN. The configuration of RB involves a process to specify a radio protocol layer and channel properties to provide a particular service and to determine its detailed parameters and operations. The RB is classified into two types, that is, a signaling RB (SRB) and a data RB (DRB). The SRB is used as a path to transmit an RRC message on the control plane. DRB is used as a path to transmit user data on the user plane.
    [049] A Non-Access Stratum (NAS) layer placed over the RRC layer performs functions such as session management and mobility management.
    [050] With reference to figure 2, the RLC and MAC layers (terminated in the eNB on the network side) can perform functions such as scheduling, automatic repeat request (ARQ) and hybrid automatic repeat request (HARQ). The RRC layer (terminated in the eNB on the network side) can perform functions such as transmission, paging, RRC connection management, RB control, mobility functions in addition to UE measurement and control reporting. The NAS control protocol (terminated at the gateway's MME on the network side) can perform functions such as SAE carrier management, authentication, LTE_IDLE mobility handling, LTE_IDLE paging source and security control for signaling between the gateway and the UE .
    [051] With reference to figure 3, the RLC and MAC layers (terminated in the eNB on the network side) can perform the same functions for the control plane. The PDCP layer (terminated in the eNB on the network side) can perform user plane functions, such as header compression, integrity protection and encryption.
    [052] The following will describe a 5G network architecture.
    [053] Figure 4 shows a 5G system architecture.
    [054] In the evolved packet core (EPC), which is the core network architecture of the existing evolved packet system (EPS), functions, landmarks and protocols are defined for each entity, as a mobility management entity ( MME), a service gateway (S-GW) and a packet data network gateway (P-GW).
    [055] In a 5G core network (or main NextGen network), however, functions, landmarks and protocols are defined for each network function (NF). In other words, in the main 5G network, functions, reference points and protocols are not defined for each entity.
    [056] With reference to the figure. 4, the architecture of the 5G system includes one or more UEs 10, a next generation radio access network (NG-RAN) and a next generation core (NGC).
    [057] The NG-RAN can include one or more 40 gNBs, and a plurality of UEs can exist in a cell. GNB 40 provides an end point for a control plan and a user plan for a UE. GNB 40 generally refers to a fixed station that communicates with the UE 10 and can be referred to by another term, such as a base station (BS), a base transceiver system (BTS) or an access point. One gNB 40 can be implanted per cell. There may be one or more cells in the gNB 40 coverage.
    [058] The NGC may include an access and mobility function (AMF) and a session management function (SMF) that are responsible for the functions of the control plan. the AMF can be responsible for a mobility management role, and the SMF can be responsible for a session management role. The NGC can include a user plan function (UPF) that is responsible for the user plan functions.
    [059] An interface for transmitting user traffic or transmitting traffic control can be used. UE 10 and gNB 40 can be connected via an NG3 interface. The gNBs 40 can be connected to each other via an Xn interface. Neighboring gNBs 40 can form a mesh network structure through the Xn interface. The 40 gNBs can be connected to the NGC via an NG interface. The 40 gNBs can be connected to the AMF via an NG-C interface and can be connected to the UPF via an NG-U interface. The NG interface supports many-to-many relationships between gNBs 40 and MME / UPF 50.
    [060] A gNB host can perform functions for radio resource management, IP header compression and user data stream encryption, selection of an AMF in the UE attachment when no routing to an AMF can be determined from the information provided by a UE, routing the user data plan to one or more UPFs, programming and transmitting a paging message (originating from an AMF), programming and transmitting system broadcast information (originating from an AMF or O & M ) or measurement or measurement report configuration for mobility and scheduling.
    [061] An AMF host can perform primary functions, such as NAS signaling termination, NAS signaling security, AS security control, inter-CN signaling for mobility between 3GPP access networks, accessibility in the EU idle mode (including control and execution of retransmission of paging), list management of tracking areas for UEs in idel and active modes, selection of AMF for transfers with an AMF change), authentication of access and authorization of access, including verification of roaming rights.
    [062] An UPF host can perform primary functions, such as an anchoring point for intra / inter-RAT mobility (where applicable), an external PDU session point for interconnecting to a data network, routing and packet forwarding, inspection of user plan and packages that are part of the application of political rules, traffic usage report, an uplink classifier to route traffic flows to a data network, a branch point to support a multi-homing PDU session, manipulation of QoS for a user plan, for example, packet filtering, and applying UL / DL rate, uplink traffic verification (SDF to QoS flow mapping), transport-level packet marking on an uplink and downlink , or downlink packet buffering and triggering downlink data notification.
    [063] An SMF host can perform primary functions, such as session management, allocation and management of the IP address of the UE, selection and control of an UP function, configuration of traffic routing by an UPF to route traffic to a suitable destination, control part of QoS and policy enforcement, or notification of downlink data.
    [064] Figure 5 shows a wireless interface protocol from a 5G system to a user plan.
    [065] Referring to figure 5, the 5G system's wireless interface protocol for the user plan can include a new layer, which is a service data adaptation protocol (SDAP), compared to an LTE system. The main services and functions of the SDAP layer are the mapping between a QoS flow and a radio data carrier (DRB) and the QoS flow ID (QFI) tagging in uplink and downlink packets. A single SDAP protocol entity can be configured for each individual PDU session, except for dual connectivity (DC), where two entities can be configured.
    [066] Figure 6 shows the mapping between a QoS flow and a DRB.
    [067] In an uplink, a BS can control the mapping of a QoS flow to a DRB using reflective mapping or explicit configuration. In reflection mapping, for each DRB, a UE can monitor a QoS flow ID in a downlink packet and can apply the same mapping to an uplink. To enable reflective mapping, BS can mark the downlink packet using a Uu with the QoS flow ID. In the explicit configuration, however, BS can configure flow mapping for QoS DRB. In this specification, flow mapping from QoS to DRB can be conceptually equivalent to flow mapping to DRB or flow ID mapping from QoS to DRB.
    [068] In a legacy LTE-based system, an EPS or E-RAB carrier can be mapped to a one-to-one DRB. This mapping is based on the concept of a carrier on a wireless interface and a main network. In addition, a one-to-one mapping principle can be applied to all nodes in a network. According to the 5G system, the concept of QoS flow is introduced for the transmission of data packets between a 5G core network and a new RAN. However, the DRB concept is still maintained on a Uu interface between the new RAN and an UE. Thus, a rule may be necessary to map a QoS flow to a DRB. That is, a QoS to DRB flow mapping rule may be required to map a specific flow to a particular DRB.
    [069] Currently, a BS cannot know a flow mapping rule from QoS to DRB to a neighboring BS. Therefore, when a UE is transferred from the BS to the neighboring BS, the neighboring BS cannot determine which flow mapping rule from QoS to DRB that the neighboring BS needs to apply to the UE. Alternatively, when a packet for the UE is downloaded to the neighboring BS, the neighboring BS cannot know which QoS to DRB flow mapping rule the neighboring BS needs to apply to the downloaded packet. The flow mapping rules from QoS to DRB to different nodes can be the same or different when transferring from a UE or unloading packets to another node, and transfer / unloading delays or packet loss can be caused by such mapping rules . For example, during a transfer between a source BS and a destination BS, the destination BS must immediately transmit a packet forwarded from the source BS to a UE. However, when the source BS and the destination BS have different flow mapping rules from QoS to DRB, the destination BS may not correctly transmit the packet forwarded from the source BS to the UE. Alternatively, when the source BS and the destination BS have different flow mapping rules from QoS to DRB, the destination BS can transmit the packet forwarded from the source BS to another UE. That is, the forwarded packet can be transmitted to the UE or to the other UE through an incorrect DRB. To solve this problem, the flow mapping rules from QoS to DRB need to be shared between the BSs. Hereinafter, a method for transmitting a QoS to DRB flow mapping rule and a support device thereof will be described according to an embodiment of the present invention.
    [070] Figure 7 shows a procedure for forwarding a flow mapping rule from QoS to DRB in a transfer procedure according to an embodiment of the present invention.
    [071] With reference to figure 7, in step S701, a BS of origin can configure a UE measurement procedure according to the area restriction information. The source BS can be a gNB or an improved eNB. The source BS can configure a UE to perform measurements at a beam level.
    [072] In step S702, the UE can measure a target cell as configured in the system information. The UE can then process a measurement report. The UE can send the measurement report to the originating BS.
    [073] In step S703, using the measurement report, the originating BS can determine the triggering of a transfer procedure. In addition, the source BS can determine to include a QoS to DRB flow mapping rule from the source BS to the destination BS. The target BS can be either a gNB or an enhanced eNB. The QoS flow can have a QoS profile.
    [074] In step S704, the source BS can initiate the transfer procedure to the destination BS. The transfer procedure can be initiated by sending a transfer request message including the QoS to DRB flow mapping rule to the target BS. In addition, the transfer request message may include other necessary parameters. The QoS flow can have a QoS profile.
    [075] In step S705, admission control can be performed by the destination BS on the PDU session connection sent from the source BS based on QoS. When the destination BS maps a QoS stream to a DRB on the BS side destination, the received QoS to DRB flow mapping rule can be considered by the destination BS, which can help the user experience during UE mobility. The QoS flow can have a QoS profile.
    [076] In step S706, the destination BS can prepare for an L1 / L2 transfer. The destination BS can send a transfer request confirmation (ACK) message to the originating BS. The transfer request ACK message can notify the originating BS if the same similar QoS to DRB flow mapping rule or rule is used. A specific indication can be used to report whether the same flow mapping rule for the same or similar DRB is used for the target BS. When the originating BS receives the specific indication, the originating BS can determine how to handle a data packet, such as forwarding data. This information can be a reference for the original BS to determine whether to transfer the UE.
    [077] In step S707, the originating BS can send a transfer command to the UE. The UE can then access the target cell.
    [078] In step S708, the source BS can send an SN status transfer message to the destination BS. The SN status transfer message can be sent for forwarding data.
    [079] In step S709, the destination BS can send a path switching request message to 5G core CP. The path switching request message can be sent to report that the UE has changed a cell including the context of the PDU session to be switched. A downlink ID and BS address for a PDU session can be included in the context of the PDU session.
    [080] In step S710, the 5G core PLC can establish a user plane path for the PDU session on a central network. The downlink ID and the BS address for the PDU session can be sent to a user plan gateway (UPGW).
    [081] In step S711, the core 5G PLC can send an ACK message from the path switch to the destination BS.
    [082] In step S712, the destination BS can send a UE context release message (UE context release), thereby notifying the originating BS of the transfer's success. The target BS can then trigger the release of resources by the source BS.
    [083] In step S713, upon receiving the UE context release message, the source BS can release resources related to the control and radio plan associated with the UE context. Any data forwarding in progress can continue.
    [084] According to the proposed modality of the present invention, with a new concept of QoS flow in a 5G core and a new 5G RAN, it is possible to improve the UE experience, such as smooth transfer or service continuity in data packets , and facilitate a RAN node to better handle data packets for a specific UE during a transfer.
    [085] Figures 8A and 8B show a procedure for forwarding a flow mapping rule from QoS to DRB in a unloading procedure in accordance with an embodiment of the present invention.
    [086] With reference to figure 8A, in step S801, a master BS can configure an UE measurement procedure, according to the area restriction information. The master BS can be a gNB or an enhanced eNB. The master BS can have dual connectivity with a secondary BS and can also have multiple connectivity with two or more secondary BSs. The secondary BS can be a gNB or an improved eNB.
    [087] In step S802, the UE can measure a target cell as configured in the system information. The UE can then process a measurement report. The UE can send the measurement report to the originating BS.
    [088] In step S803, using the measurement report, the master BS can determine the request of the secondary BS to allocate radio resources for specific flow (s). In addition, the master BS can determine the inclusion of a QoS to DRB flow mapping rule from the master BS in the secondary BS. The QoS flow can have a QoS profile.
    [089] In step S804, the master BS can transmit the flow mapping rule from QoS to DRB to the secondary BS. The QoS to DRB flow mapping rule can be included in a secondary node add request message or a secondary node modify request message. In addition, the secondary node add request message or the secondary node change request message may include other necessary parameters. The QoS flow can have a QoS profile.
    [090] In step S805, admission control can be performed by the secondary BS in connection to the PDU session sent by the master BS based on QoS. When the secondary BS maps a QoS flow to a DRB next to the secondary BS, the QoS to DRB flow mapping rule received can be considered by the secondary BS, which can help the user experience during UE mobility. The QoS flow can have a QoS profile.
    [091] In step S806, when an RRM entity on the secondary node is able to accept the resource request, the secondary BS sends the secondary node addition ACK message or a secondary node modification ACK message to the master BS. The ACK message of adding the secondary node or the ACK message of modifying the secondary node can notify the primary BS if the same or similar QoS to DRB flow mapping rule is used. A specific indication can be used to report whether the same or similar flow mapping rule from QoS to DRB is used for the secondary BS. When the master BS receives the specific indication, the master BS can determine how to handle a data packet, such as forwarding data. This information can be a reference for the master BS to determine whether to discharge the QoS flow.
    [092] In step S807, the master BS can send a transfer command to the UE.
    [093] Steps S808 to S816 illustrated in figure 8B are similar to the dual connectivity inheritance procedure and therefore a detailed description will be omitted
    [094] According to the proposed modality of the present invention, with a new concept of QoS flow in a 5G core and a new 5G RAN, it is possible to improve the UE experience, such as smooth downloading of data packets from a master node or service continuity in data packets, and to facilitate a RAR node to better handle data packets for a specific UE during download procedures in dual connectivity or multiple connectivity.
    [095] Figure 9 shows a procedure for forwarding a flow mapping rule from QoS to DRB in an Xn interface configuration procedure according to an embodiment of the present invention.
    [096] A QoS to DRB flow mapping rule can be exchanged between RANs when a RAN interface (for example, Xn interface) is configured.
    [097] With reference to figure 9, in step S910, a first RAN can send a configuration request message from the RAN interface to a second RAN. The RAN interface configuration request message can include a QoS to DRB flow mapping rule from the first RAN. In addition, the RAN interface configuration request message can include the global ID of the first RAN. The first RAN can be a gNB or an enhanced eNB. When a neighboring RAN node needs to use the same rule as the first RAN QoS to DRB flow mapping rule, the first RAN QoS to DRB flow mapping rule can be transmitted to the neighboring RAN node.
    [098] In step S920, upon receiving the QoS to DRB flow mapping rule from the first RAN, the second RAN can take into account the QoS to DRB flow mapping rule from the first RAN for a specific EU procedure, to manipulate a data packet. For example, the UE's specific procedure for handling the data packet may be a data mobility or routing procedure. Subsequently, the second RAN can send a configuration response message from the RAN interface to the first RAN. The configuration response message from the RAN interface can include a QoS to DRB flow mapping rule from the second RAN. In addition, the configuration response message from the RAN interface can include the global ID of the second RAN. The second RAN can be a gNB or an enhanced eNB.
    [099] Then, the first RAN can perform an appropriate operation based on the parameter received for the specific procedure of the UE to manipulate the data packet on the side of the first RAN.
    [0100] According to the proposed modality of the present invention, with a new concept of QoS flow in a 5G core and a new 5G RAN, it is possible to improve the UE experience, such as smooth downloading of data packets from a master node, smooth transfer or service continuity in data packets and to make it easier for a RAR node to better handle data packets for a specific UE, during download procedures in dual connectivity or multiple connectivity or during transfer.
    [0101] Figure 10 shows a procedure for forwarding a flow mapping rule from QoS to DRB in an Xn interface configuration update procedure, according to an embodiment of the present invention.
    [0102] A QoS to DRB flow mapping rule can be exchanged between RANs when a RAN interface configuration (for example, Xn interface) is updated.
    [0103] Referring to figure 10, in step S1010, a first RAN can send a request message to update the configuration of the RAN interface to a second RAN. The RAN interface configuration update request message can include an updated QoS to DRB flow mapping rule from the first RAN. In addition, the RAN interface configuration update request message can include the global ID of the first RAN. The first RAN can be a gNB or an enhanced eNB. When the first RAN updates the QoS to DRB flow mapping rule from the first RAN, the updated QoS to DRB flow mapping rule from the first RAN can be transmitted to a neighboring RAN node.
    [0104] In step S1020, upon receiving the updated QoS to DRB flow mapping rule from the first RAN, the second RAN may take into account the updated QoS to DRB flow mapping rule from the first RAN for a specific procedure UE, to manipulate a data packet. For example, the UE's specific procedure for handling the data packet may be a data mobility or routing procedure. Subsequently, the second RAN can send a response message to update the configuration of the RAN interface to the first RAN. The RAN interface configuration update response message can include a QoS to DRB flow mapping rule from the second RAN. Alternatively, the RAN interface configuration update response message can include an updated QoS to DRB flow mapping rule from the second RAN. In addition, the RAN interface configuration update response message can include the global ID of the second RAN. The second RAN can be a gNB or an enhanced eNB.
    [0105] Then, the first RAN can perform an appropriate operation based on the received parameter for the specific procedure of the UE to manipulate the data packet on the side of the first RAN.
    [0106] According to the proposed modality of the present invention, with a new concept of QoS flow in a 5G core and a new 5G RAN, it is possible to improve the UE experience, such as smooth downloading of data packets from a master node, smooth transfer or service continuity in data packets and to facilitate a RAR node to better handle data packets for a specific UE during download procedures in dual connectivity or multiple connectivity or during transfer.
    [0107] Figures 11A and 11B show a procedure for forwarding a flow mapping rule from QoS to DRB in a transfer procedure according to an embodiment of the present invention.
    [0108] According to the proposed procedure, when the transfer of a UE is performed between neighboring BSs having an Xn interface, a source BS can notify a destination BS of a QoS to DRB flow mapping rule from the BS of origin. In this document, it is assumed that a QoS stream that reaches any BS needs to pass through an SDAP layer that performs QoS to DRB flow mapping, the source BS and the destination BS may have different rules for mapping QoS flow to DRB and a packet passing through the SDAP layer needs to be forwarded to the destination BS.
    [0109] With reference to figure 11A, in step S1101, the source BS can configure a UE measurement procedure. A measurement control message can be transmitted from the source BS to a UE. The source BS can be a gNB or an improved eNB.
    [0110] In step S1102, a measurement report message can be triggered and can be transmitted to the originating BS.
    [0111] In step S1103, upon receiving the measurement report message, the originating BS can determine the transfer of the UE based on a measurement report and RRM information.
    [0112] In step S1104, the originating BS can transmit a transfer request message to the destination BS, so that the destination BS prepares for distribution. The target BS can be either a gNB or an enhanced eNB.
    [0113] In step S1105, upon receiving the transfer request message from the source BS, the destination BS can perform admission control and can configure a required resource based on the received E-RAB QoS information.
    [0114] In step S1106, the destination BS can transmit a transfer request ACK message to the source BS in response to the transfer request message.
    [0115] In step S1107, upon receiving the transfer request ACK message from the destination BS, the originating BS can generate an RRC connection reconfiguration message including a transparent container to be transmitted to the UE as an RRC message to execute the transfer. When the reconfiguration message from the RRC connection is received, the UE can perform make-before-break transfer without releasing connection until establishing RRC connection with the target BS or can carry out normal transfer that releases RRC connection with the originating gNB.
    [0116] In step S1108, the originating BS can buffer uplink data to be transmitted to a central network and downlink data to be transmitted to the UE. When the source BS supports make-before-break transfer, the source BS can transmit downlink data to the UE or it can receive uplink data to be transmitted to the main network.
    [0117] In step S1109, the source BS can transmit an SN status transfer message including the QoS to DRB flow mapping rule from the source BS to the destination BS. Alternatively, in order to provide the QoS to DRB flow mapping rule from the source BS to the destination BS, a new message can be used and can be transmitted before forwarding data.
    [0118] In step S1110, upon receiving the SN status transfer message or the new message, the destination BS can remap a forwarded packet based on the QoS to DRB flow mapping rules of the source BS and the BS of destiny. That is, for the forwarded packet, the destination BS can perform the DRB-to-QoS mapping according to the QoS to DRB flow mapping rule of the originating BS. Subsequently, the destination BS can perform flow mapping from QoS to DRB according to the same mapping rule. The destination BS can buffer the remapped packet.
    [0119] In step S1111, when the UE successfully accesses the destination BS, the UE can transmit a complete RRC connection reconfiguration message to the destination BS to confirm the distribution. Upon receiving the complete reconfiguration message from the RRC connection, the destination BS can begin to send the buffered packet to the UE.
    [0120] With reference to figure 11B, in step S1112, the destination BS can transmit a dowlink switching request message including a dowlink TEID to the AMF. The downlink TEID can be allocated to indicate that the UE has changed the BS.
    [0121] In step S1113, upon receiving the downlink path switching request message from the target BS, the AMF can determine that an SMF can continue to serve the UE. The AMF can then transmit a modification PDU session request message, including a downlink TEID to the target SM to the SMF, in order to request a downlink path switch to the target BS.
    [0122] In step S1114, after receiving the AMF PDU modification session request message, SMF can determine the switching of a downlink path towards the destination BS. The SMF can then select an appropriate UPGW or UPF that transmits a downlink packet to the target BS.
    [0123] In step S1115, SMF can send the PDU modification session request message including the downlink TEID to the selected UPGW or UPF to release any user plan / TNL resources towards the source BS.
    [0124] In step S1116, upon receiving the PDU modification session request message, the UPGW or UPF can transmit one or more "end marker" packets on an old route to the originating BS. The UPGW or UPF can then release any resources from the user plan / TNL towards the source BS.
    [0125] In step S1117, the UPGW or UPF can send a PDU modification session response message to the SMF.
    [0126] In step S1118, upon receiving the PDU modification session response message from the UPGW or UPF, the SMF can transmit the PDU modification session response message to the AMF.
    [0127] In step S1119, upon receiving the response message from the SMF PDU modification session, the AMF may transmit an ACK request for commutation to the destination BS to inform that the downlink path commutation to the BS destination is complete
    [0128] In step S1120, upon receiving the AMF path switch request ACK message, the destination BS can transmit a UE context release message to the source BS to indicate the success of the transfer and initiate the release of resources by the original BS.
    [0129] In step S1121, upon receiving the UE context release message from the target BS, the originating BS can release resources related to the control and radio plan associated with the UE context.
    [0130] A packet to which the QoS to DRB flow mapping rule of the source BS is applied can be forwarded to the destination BS and can be transmitted directly to the UE without any additional process to prevent packet loss during forwarding data on the source BS side. According to the proposed embodiment of the present invention, it is possible to improve the UE experience, such as smooth transfer, and to facilitate a RAN node to handle data packets better for a specific UE during a transfer.
    [0131] Figures 12A and 12B show a procedure for forwarding a QoS flow packet in a transfer procedure according to an embodiment of the present invention.
    [0132] According to the proposed procedure, when the transfer of a UE is performed between neighboring BSs having an Xn interface, a source BS can buffer a specific QoS flow packet. The specific QoS flow packet can be a packet received from an UPGW or UPF before the QoS to DRB flow mapping is applied. The specific QoS flow packet can be a packet that is obtained by applying QoS flow mapping to DRB to a packet that has passed through an SDAP layer but has not yet been transmitted to a UE. The specific QoS flow packet can be a packet that is obtained by applying QoS flow mapping to DRB to a packet received from a UE. The source BS can forward the specific QoS flow packet to a destination BS. In this document, it is assumed that a QoS flow that reaches any BS must pass through an SDAP layer that performs flow QoS mapping to DRB, the source BS and the target BS may have different flow mapping rules for DRB and the packet passing through the SDAP layer needs to be forwarded to the destination BS.
    [0133] With reference to figure 12A, in step S1201, the source BS can configure a UE measurement procedure. A measurement control message can be transmitted from the source BS to a UE. The source BS can be a gNB or an improved eNB.
    [0134] In step S1202, a measurement report message can be triggered and can be transmitted to the originating BS.
    [0135] In step S1203, upon receiving the measurement report message, the originating BS can determine the transfer from the EU, based on a measurement report and RRM information.
    [0136] In step S1204, the source BS can transmit a transfer request message to the destination BS, so that the destination BS prepares for distribution. The target BS can be either a gNB or an enhanced eNB.
    [0137] In step S1205, upon receiving the transfer request message from the source BS, the destination BS can perform admission control and can configure a required resource based on the received E-RAB QoS information.
    [0138] In step S1206, the destination BS can transmit a transfer request ACK message to the source BS in response to the transfer request message.
    [0139] In step S1207, upon receiving the transfer request ACK message from the destination BS, the originating BS can generate an RRC connection reconfiguration message including a transparent container to be transmitted to the UE as an RRC message to execute the transfer. When the reconfiguration message from the RRC connection is received, the UE can perform make-before-break transfer without releasing connection until establishing RRC connection with the target BS or can carry out normal transfer that releases RRC connection with the originating gNB.
    [0140] In step S1208, the source BS can buffer a specific QoS flow packet. The specific QoS flow packet can be a packet received from an UPGW or UPF before the QoS to DRB flow mapping is applied. The specific QoS flow packet can be a packet that is obtained by applying QoS flow mapping to DRB to a packet that has passed through the SDAP layer, but has not yet been transmitted to a UE. The specific QoS flow packet can be a packet that is obtained by applying QoS flow mapping to DRB to a packet received from a UE. When the source BS supports make-before-break transfer, the source BS can transmit downlink data that has passed the SDAP layer to the UE or can receive uplink data to be transmitted to the main network.
    [0141] In step S1209, the source BS can transmit an SN status transfer message to the destination BS. In addition, the source BS can forward the specific QoS flow packet to the destination BS.
    [0142] In step S1210, after receiving the SN status transfer message, the destination BS can buffer the specific QoS flow packet forwarded from the source BS.
    [0143] In step S1211, when the UE successfully accesses the destination BS, the UE can transmit a complete RRC connection reconfiguration message to the destination BS to confirm the distribution. Upon receiving the complete reconfiguration message from the RRC connection, the destination BS can begin sending the buffered packet to the UE using the QoS to DRB flow mapping rule from the destination BS.
    [0144] With reference to figure 12B, in step S1212, the destination BS can transmit a downlink path switching request message including a downlink TEID to an AMF. The downlink TEID can be allocated to indicate that the UE has changed the BS.
    [0145] In step S1213, upon receiving the downlink path switching request message from the destination BS, the AMF can determine that an SMF can continue to serve the UE. The AMF can then transmit a modification PDU session request message including a downlink TEID to the destination SM for the SMF in order to request a downlink path switch to the destination BS.
    [0146] In step S1214, upon receiving the AMF PDU modification session request message, the SMF can determine the switching of a downlink path towards the destination BS. The SMF can then select an appropriate UPGW or UPF that transmits a downlink packet to the target BS.
    [0147] In step S1215, the SMF can send the PDU modification session request message including the downlink TEID to the selected UPGW or UPF to release any user plan / TNL resources toward the source BS.
    [0148] In step S1216, upon receiving the PDU modification session request message, the UPGW or UPF can transmit one or more "final marker" packets on an old route to the originating BS. The UPGW or UPF can then release any resources from the user plan / TNL towards the source BS.
    [0149] In step S1217, the UPGW or UPF can send a PDU modification session response message to the SMF.
    [0150] In step S1218, upon receiving the response message from the PDU modification session from the UPGW or UPF, the SMF can transmit the response message from the PDU modification session to the AMF.
    [0151] In step S1219, upon receiving the SMF PDU modification session response message, the AMF may transmit an ACK request for commutation to the destination BS to inform that the downlink path commutation to the BS destination is complete.
    [0152] In step S1220, upon receiving the AMF path switching request ACK message, the destination BS can transmit a UE context release message to the originating BS to indicate the success of the transfer and initiate the transfer of resources by the original BS.
    [0153] In step S1221, upon receiving the UE context release message from the target BS, the source BS can release resources related to the radio and control plan associated with the UE context.
    [0154] As a QoS flow packet to which the QoS to DRB flow mapping rule is not applied can be forwarded to the destination BS via the Xn interface, it may be necessary to provide the destination BS with additional information via of a package header. or signage. According to the proposed embodiment of the present invention, it is possible to improve the UE experience, such as smooth transfer, and to facilitate a RAN node to handle data packets better for a specific UE during a transfer.
    [0155] For convenience of description, it has been shown above only that a QoS to DRB flow mapping rule is routed in an Xn transfer procedure, but the present invention is not limited to that. A QoS to DRB flow mapping rule can also be routed in a transfer procedure using a new control plan interface between a 5G core CP node and a BS. In this case, a QoS to DRB flow mapping rule transmitted by a source BS can be forwarded to a destination BS via the CP 5G core.
    [0156] Figure 13 is a block diagram illustrating a method in which a source BS transmits a flow mapping rule from QoS to DRB to a destination BS according to an embodiment of the present invention.
    [0157] With reference to figure 13, in step S1310, the source BS can receive a measurement result from a target cell of a UE.
    [0158] In step S1320, the source BS can determine the transfer from the UE to the destination BS based on the measurement result.
    [0159] In step S1330, the source BS can transmit a transfer request message including a QoS to DRB flow mapping rule from the source BS to the destination BS. The QoS to DRB flow mapping rule can be a rule used for the source BS to map a specific QoS flow to a specific DRB. When the transfer request message including the QoS to DRB flow mapping rule is passed to the destination BS, the QoS to DRB flow mapping rule can be used for the destination BS to map a QoS flow for a DRB.
    [0160] In addition, the source BS can receive from the destination BS, an indication that shows whether the QoS to DRB flow mapping rule included in the transfer request message is used for the destination BS. In addition, the originating BS can control the forwarding of data from the originating BS to the destination BS based on the indication received. The transfer to the destination BS can be determined based on the indication received.
    [0161] The QoS flow can include a QoS profile.
    [0162] Figure 14 is a block diagram illustrating a method in which a master BS transmits a flow mapping rule from QoS to DRB to a secondary BS according to an embodiment of the present invention.
    [0163] With reference to figure 14, in step S1410, the master BS can receive a measurement result from the secondary BS of the UE.
    [0164] In step S1420, the master BS can determine the data download to the secondary BS based on the measurement result.
    [0165] In step S1430, the master BS can transmit a QoS to DRB flow mapping rule from the master BS to the secondary BS.
    [0166] The QoS to DRB flow mapping rule can be a rule used for the master BS to map a specific QoS flow to a specific DRB. When the QoS to DRB flow mapping rule is passed to the secondary BS, the QoS to DRB flow mapping rule can be used for the secondary BS to map a QoS flow to a DRB.
    [0167] In addition, the master BS can receive, from the secondary BS, an indication that shows whether the QoS to DRB flow mapping rule is used for the secondary BS. In addition, the master BS can control the forwarding of data from the master BS to the secondary BS based on the indication received. The download of data to the secondary BS can be determined based on the indication received.
    [0168] The QoS to DRB flow mapping rule can be included in a secondary node add request message or a secondary node modify request message.
    [0169] Figure 15 is a block diagram illustrating a wireless communication system in accordance with the embodiment of the present invention.
    [0170] An UE 1500 includes a processor 1501, a memory 1502 and a transceiver 1503. Memory 1502 is connected to processor 1501 and stores various information to drive processor 1501. Transceiver 1503 is connected to processor 1501, and transmits and / or receives radio signals. The 1501 processor implements the proposed functions, processes and / or methods. In the above embodiment, an UE operation can be implemented by processor 1501.
    [0171] BS 1510 includes a 1511 processor, a 1512 memory and a 1513 transceiver. The 1512 memory is connected to the 1511 processor and stores various information to drive the 1511 processor. The 1513 transceiver is connected to the 1511 processor, and transmits and / or receives radio signals. The 1511 processor implements the proposed functions, processes and / or methods. In the above modality, a BS operation can be implemented by the 1511 processor.
    [0172] An AMF 1520 includes a 1521 processor, a 1522 memory and a 1523 transceiver. The 1522 memory is connected to the 1521 processor and stores various information to drive the 1521 processor. The 1523 transceiver is connected to the 1521 processor, and transmits and / or receives radio signals. The 1521 processor implements the proposed functions, processes and / or methods. In the above modality, an AMF operation can be implemented by the 1521 processor.
    [0173] The processor may include an application specific integrated circuit (ASIC), a separate chip set, a logic circuit and / or a data processing unit. The memory may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and / or other equivalent storage devices. The transceiver may include a baseband circuit to process a wireless signal. When the modality is implemented in software, the methods mentioned above can be implemented with a module (ie, process, function, etc.) to perform the functions mentioned above. The module can be stored in memory and can be executed by the processor. The memory can be located inside or outside the processor and can be coupled to the processor using several well-known means.
    [0174] Various methods based on the present specification have been described with reference to the drawings and reference numbers given in the drawings based on the above mentioned examples. Although each method describes multiple steps or blocks in a specific order for convenience of explanation, the invention disclosed in the claims is not limited to the order of the steps or blocks, and each step or block can be implemented in a different order, or can be performed simultaneously with other steps or blocks. In addition, those skilled in the art may know that the invention is not limited to each of the steps or blocks, and at least one different step can be added or deleted without departing from the scope and spirit of the invention.
    [0175] The aforementioned modality includes several examples. It should be noted that those skilled in the art know that all possible combinations of examples cannot be explained, and they also know that various combinations can be derived from the technique of this specification. Therefore, the scope of protection of the invention must be determined by combining several examples described in the detailed explanation, without departing from the scope of the claims that follow.
    权利要求:
    Claims (15)
    [0001]
    1. Method for transmitting, by a source base station, a rule for mapping Quality of Service (QoS) flow to radio carrier data (DRB)) to a destination base station in a wireless communication system, CHARACTERIZED by the fact that the method comprises: receiving, from a user equipment (UE), a measurement result from a target cell; determine a transfer from the UE to the destination base station, based on the measurement result; and transmit, to the destination base station, a transfer request message including the rule for QoS to DRB flow mapping from the source base station.
    [0002]
    2. Method, according to claim 1, CHARACTERIZED by the fact that the rule for mapping QoS flow to DRB is used to map a certain QoS flow to a specific DRB at the originating base station.
    [0003]
    3. Method, according to claim 1, CHARACTERIZED by the fact that the rule for mapping the QoS to DRB flow is used to map the QoS to DRB flow at the destination base station if the transfer request message including the rule for flow mapping from QoS to DRB is transmitted to the destination base station.
    [0004]
    4. Method, according to claim 1, CHARACTERIZED by the fact that it additionally comprises: receiving, from the destination base station, an indication that indicates whether the rule for QoS to DRB flow mapping included in the request message transfer is used or not at the destination base station.
    [0005]
    5. Method, according to claim 4, CHARACTERIZED by the fact that it additionally comprises: controlling the forwarding of data from the source base station to the destination base station, based on the indication received.
    [0006]
    6. Method, according to claim 4, CHARACTERIZED by the fact that the transfer to the destination base station is determined, based on the indication received.
    [0007]
    7. Method, according to claim 1, CHARACTERIZED by the fact that the QoS flow includes a QoS profile.
    [0008]
    8. Method for transmitting, through a master base station, a rule for mapping Quality of Service (QoS) flow to radio carrier data (DRB) to a secondary base station in a wireless communication system, the CHARACTERIZED method by the fact that it comprises: receiving, from a user equipment (UE), a measurement result from the secondary base station; determining a download of data to the secondary base station, based on the measurement result; and transmit, to the secondary base station, the rule for mapping QoS flow to DRB from the master base station.
    [0009]
    9. Method, according to claim 8, CHARACTERIZED by the fact that the rule for mapping QoS flow to DRB is used to map a given QoS flow to a specific DRB at the main base station.
    [0010]
    10. Method, according to claim 8, CHARACTERIZED by the fact that the rule for mapping QoS flow to DRB is used to map QoS flow to DRB at the secondary base station if the rule for mapping QoS flow to DRB is transmitted to the secondary base station.
    [0011]
    11. Method, according to claim 8, CHARACTERIZED by the fact that it additionally comprises: receiving, from the secondary base station, an indication that indicates whether the rule for mapping QoS flow to DRB is used or not at the base station secondary.
    [0012]
    12. Method, according to claim 11, CHARACTERIZED by the fact that it further comprises: controlling the forwarding of data from the master base station to the secondary base station, based on the indication received.
    [0013]
    13. Method according to claim 11, CHARACTERIZED by the fact that the data downloaded to the secondary base station is determined based on the indication received.
    [0014]
    14. Method, according to claim 8, CHARACTERIZED by the fact that the rule for flow mapping from QoS to DRB is included in a request for adding a secondary node or in a request for modifying a secondary node.
    [0015]
    15. Originating base station to transmit a rule for Quality of Service (QoS) flow mapping for radio data carrier (DRB) to a destination base station in a wireless communication system, the CHARACTERIZED originating base station by the fact that it understands: a memory; a transceiver; and a processor, connected with the memory and the transceiver, which: controls the transceiver to receive, from a user equipment (UE), a measurement result from a target cell; determines a transfer from the UE to the destination base station, based on the measurement result; and controls the transceiver to transmit a transfer request message to the destination base station including the rule for mapping
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112019000608B1|2021-02-09|methods and source base station to transmit rule for flow mapping from qos to drb
    US10798624B2|2020-10-06|Method and apparatus for transmitting data in CU-DU split scenario
    JP2020503781A|2020-01-30|Method and apparatus for establishing DRB
    ES2740775T3|2020-02-06|Procedure and apparatus for assigning data to divide carriers into dual connectivity
    US10869353B2|2020-12-15|Method and apparatus for modifying radio bearer in CU-DU split scenario
    BR112019015657A2|2020-03-31|METHOD TO PERFORM QUALITY OF SERVICE | REFLECTIVE IN WIRELESS COMMUNICATION SYSTEM AND A DEVICE FOR THE SAME
    US20190150220A1|2019-05-16|Method and apparatus for establishing bearer
    US11089571B2|2021-08-10|Method for performing a RAN based paging and device supporting the same
    US11184791B2|2021-11-23|Access control method and device for supporting same
    US10791540B2|2020-09-29|Method and apparatus for keeping SCG configuration
    CN110999521A|2020-04-10|Method and device for recovering RRC connection in CU-DU division scene
    US20200146040A1|2020-05-07|Method and apparatus for selecting carrier
    US20190349813A1|2019-11-14|Method for controlling flow and apparatus for supporting same
    US20210176740A1|2021-06-10|Method and apparatus for selecting carrier
    CN110892749A|2020-03-17|Method and apparatus for modifying mapping rules
    KR20110036507A|2011-04-07|Method of controlling data flow within a wireless communication system
    同族专利:
    公开号 | 公开日
    AU2018206315B2|2020-07-16|
    US11140585B2|2021-10-05|
    JP6808809B2|2021-01-06|
    BR112019000608A2|2019-07-30|
    CN108605254A|2018-09-28|
    CA3030542A1|2018-07-12|
    MX2019006242A|2019-08-12|
    KR20190006573A|2019-01-18|
    KR102155338B1|2020-09-11|
    US20190357093A1|2019-11-21|
    US20200120558A1|2020-04-16|
    WO2018128462A1|2018-07-12|
    HK1257754A1|2019-10-25|
    EP3567919A1|2019-11-13|
    PH12019500230A1|2019-10-28|
    EP3567919A4|2020-08-05|
    CA3030542C|2020-07-14|
    RU2733066C1|2020-09-29|
    US10893446B2|2021-01-12|
    SG11201811794YA|2019-01-30|
    CN108605254B|2021-06-11|
    JP2019525587A|2019-09-05|
    AU2018206315A1|2019-01-24|
    CL2019000847A1|2019-06-28|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    EP2213119B1|2007-11-16|2014-01-08|Nokia Solutions and Networks Oy|Mapping quality of service for intersystem handover|
    CN102017697B|2008-04-21|2014-04-23|艾利森电话股份有限公司|QCI mapping at roaming and handover|
    US8902805B2|2008-10-24|2014-12-02|Qualcomm Incorporated|Cell relay packet routing|
    US20110261747A1|2010-04-02|2011-10-27|Interdigital Patent Holdings, Inc.|Method and apparatus for supporting communication via a relay node|
    US8630607B2|2011-07-15|2014-01-14|Verizon Patent And Licensing Inc.|Emergency call handoff between heterogeneous networks|
    CN103096400B|2011-10-28|2015-11-18|普天信息技术研究院有限公司|Method for handover control in a kind of relay system|
    US20150124601A1|2012-05-16|2015-05-07|Nokia Corporation|Method and apparatus for network traffic offloading|
    US9479973B2|2012-08-02|2016-10-25|Telefonaktiebolaget Lm Ericsson |Node and method for handing over a sub-set of bearers to enable multiple connectivity of a terminal towards several base stations|
    CN110087266B|2012-08-23|2021-09-28|交互数字专利控股公司|Providing physical layer resources to different serving sites|
    US20150215838A1|2012-09-12|2015-07-30|Nokia Corporation|Method and apparatus for mobility control in heterogenous network|
    CN105144782B|2012-11-02|2019-08-13|瑞典爱立信有限公司|For coordinating the method that mobility is arranged between RAT|
    WO2014133589A1|2013-03-01|2014-09-04|Intel Corporation|Wireless local area network traffic offloading|
    WO2014148749A1|2013-03-21|2014-09-25|엘지전자 주식회사|Method for switching data between plurality of communications systems and apparatus therefor|
    CN105359582B|2013-07-02|2019-06-11|Lg电子株式会社|The method and apparatus of switching are executed in a wireless communication system|
    CN104737579A|2013-08-09|2015-06-24|华为技术有限公司|Measurement method and device, information interaction method and device, and residing method and device|
    CN104469869B|2013-09-23|2019-08-13|中兴通讯股份有限公司|A kind of small cell switching method and base station|
    US9420503B2|2014-01-21|2016-08-16|Cisco Technology, Inc.|System and method for seamless mobility in a network environment|
    ES2761608T3|2014-04-15|2020-05-20|Nokia Solutions & Networks Oy|Interworking with a carrier-based system|
    GB2526617A|2014-05-30|2015-12-02|Nec Corp|Communication system|
    EP3162011A4|2014-06-30|2018-02-28|Intel IP Corporation|An apparatus and method enhancing quality of service architecture for lte|
    CN104363598B|2014-11-25|2018-03-23|电信科学技术研究院|A kind of DRB mapping methods and device|
    CN106034314A|2015-03-10|2016-10-19|电信科学技术研究院|Data transmission method and data transmission device|
    US9730120B2|2015-06-01|2017-08-08|Intel Corporation|Handover using group evolved packet system bearers|
    CN110995773B|2016-05-24|2021-01-05|华为技术有限公司|QoS control method and device|
    EP3499964B1|2016-08-10|2021-06-23|Nec Corporation|Radio access network node, wireless terminal, core network node, and methods for these|
    CN107734563B|2016-08-12|2020-02-07|电信科学技术研究院|Method and device for processing QoS parameters in switching scene|
    CN107889255B|2016-09-30|2022-02-25|华为技术有限公司|Communication method, device, system, terminal and access network equipment|
    CN111885642A|2016-11-02|2020-11-03|中兴通讯股份有限公司|Switching method and device|
    US20180242205A1|2016-11-04|2018-08-23|Telefonaktiebolaget Lm Ericsson |Systems and Methods of Handing Over a Wireless Device|
    CN109952781A|2016-11-04|2019-06-28|瑞典爱立信有限公司|For handling the UE, network node and method of data grouping|
    US20190075482A1|2016-11-04|2019-03-07|Telefonaktiebolaget Lm Ericsson |Reflective mapping of flows to radio bearers|
    US10433224B2|2016-12-02|2019-10-01|Htc Corporation|Device and method of handling data transmissions after a handover|
    GB201621072D0|2016-12-12|2017-01-25|Samsung Electronics Co Ltd|NR QOS handling|
    EP3550876A4|2016-12-29|2019-11-20|LG Electronics Inc. -1-|Method and apparatus for establishing drb|
    MX2019006242A|2017-01-05|2019-08-12|Lg Electronics Inc|Method and device for transmitting rule for qos flow to drb mapping.|
    JP6908712B2|2017-01-11|2021-07-28|テレフオンアクチーボラゲット エルエム エリクソン（パブル）|5G QoS Flow vs. Wireless Bearer Remapping|MX2019006242A|2017-01-05|2019-08-12|Lg Electronics Inc|Method and device for transmitting rule for qos flow to drb mapping.|
    JP6908712B2|2017-01-11|2021-07-28|テレフオンアクチーボラゲット エルエム エリクソン（パブル）|5G QoS Flow vs. Wireless Bearer Remapping|
    CN110169118A|2017-01-13|2019-08-23|Lg电子株式会社|The method and device of UL grouping is sent based on service qualitystream in a wireless communication system|
    WO2018196102A1|2017-04-27|2018-11-01|北京小米移动软件有限公司|Information transmission method and apparatus and computer readable storage medium|
    CN108809596A|2017-05-05|2018-11-13|华为技术有限公司|A kind of communication means and device based on reversion service flow properties|
    CN111163495B|2017-05-08|2021-04-09|华为技术有限公司|Method and device for moving among communication systems|
    EP3435700B1|2017-07-24|2020-09-16|ASUSTek Computer Inc.|Method and apparatus for serving quality of serviceflow in a wireless communication system|
    EP3665924A4|2017-08-09|2020-10-21|ZTE Corporation|Quality of service implementations for separating user plane|
    CN109548096B|2017-08-11|2021-12-03|华为技术有限公司|Communication method, base station, terminal equipment and system|
    US11184819B2|2018-09-20|2021-11-23|Qualcomm Incorporated|Avoiding out of order uplink data reception upon data radio bearer release, handover to another data radio bearer, or quality of service flow addition|
    US11044640B2|2018-09-20|2021-06-22|Nokia Technologies Oy|Uplink bearer binding in handover|
    CN111405625B|2018-09-28|2021-06-29|华为技术有限公司|Switching method, base station, communication system and storage medium|
    CN110972337B|2018-09-29|2021-09-14|中国移动通信有限公司研究院|Data transmission method, device and system, SDAP entity and storage medium|
    CN111093233A|2018-10-24|2020-05-01|中国移动通信有限公司研究院|Switching control method, device and base station|
    CN109526026B|2018-10-29|2021-11-23|中国电子科技集团公司第三十六研究所|End/Start Mark-based uplink SDAP remapping method and device|
    CN111263398B|2018-11-30|2021-08-31|华为技术有限公司|Service transmission measuring method and device|
    CN111726819B|2019-03-19|2021-11-02|大唐移动通信设备有限公司|Method and device for establishing and updating base station link|
    CN111757397B|2019-03-28|2021-11-16|大唐移动通信设备有限公司|Method and device for forwarding data|
    KR20210107152A|2019-04-01|2021-08-31|엘지전자 주식회사|Method and apparatus for performing data transmission while handling enhanced handover in a wireless communication system|
    CN110677889B|2019-09-24|2021-11-23|京信网络系统股份有限公司|Data transmission method and device, access network equipment and readable storage medium|
    CN113473525A|2020-03-31|2021-10-01|华为技术有限公司|Data transmission method and device|
    WO2021081569A2|2020-04-07|2021-04-29|Zeku, Inc.|Uplink data plane management for quality of service data transfer|
    法律状态:
    2020-07-14| B06A| Patent application procedure suspended [chapter 6.1 patent gazette]|
    2020-12-01| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-02-09| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 05/01/2018, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US201762442887P| true| 2017-01-05|2017-01-05|
    US201762442483P| true| 2017-01-05|2017-01-05|
    US62/442,887|2017-01-05|
    US62/442,483|2017-01-05|
    PCT/KR2018/000252|WO2018128462A1|2017-01-05|2018-01-05|Method and device for transmitting rule for qos flow to drb mapping|
    [返回顶部]