WO2019242749A1 - Procédé et dispositif de transfert intercellulaire - Google Patents

Procédé et dispositif de transfert intercellulaire Download PDF

Info

Publication number
WO2019242749A1
WO2019242749A1 PCT/CN2019/092328 CN2019092328W WO2019242749A1 WO 2019242749 A1 WO2019242749 A1 WO 2019242749A1 CN 2019092328 W CN2019092328 W CN 2019092328W WO 2019242749 A1 WO2019242749 A1 WO 2019242749A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran device
qos flow
drb
qfi
terminal device
Prior art date
Application number
PCT/CN2019/092328
Other languages
English (en)
Chinese (zh)
Inventor
胡星星
张宏平
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19823238.1A priority Critical patent/EP3790319B1/fr
Priority to EP23183440.9A priority patent/EP4243486A3/fr
Priority to AU2019290751A priority patent/AU2019290751B2/en
Publication of WO2019242749A1 publication Critical patent/WO2019242749A1/fr
Priority to US17/111,200 priority patent/US11457392B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H04W36/0044—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of quality context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a method and device for handover.
  • 5G 5th generation wireless communication technology
  • 5G will support various types of network deployment and application types, including higher-speed experience and greater bandwidth access capabilities, lower latency and highly reliable information interaction, larger-scale, low-cost machine-type communication equipment Access and management.
  • QoS quality of service
  • DRB data radio bearers
  • a protocol data unit (PDU) session can include one or more data flows (such as Internet Protocol (IP) flows), where one or more data flows with the same QoS requirements constitute a QoS flow , So a PDU session contains one or more QoS flows.
  • Data packets of one or more QoS flows can be carried on one DRB for transmission, and data packets of one or more QoS flows carried on one DRB have the same forwarding processing, for example, the same scheduling strategy, queuing management strategy, Rate matching strategy, etc.
  • the uplink data packet and downlink data packet of a QoS flow can be carried on the same DRB, or can be carried on different DRBs.
  • the length of the QFI is 6 bits, that is, one PDU session can include 0 to 63 QoS flows.
  • the length of the QFI used by different PDU sessions can be different.
  • the QFI of some PDU sessions can be 6 bits
  • the QFI of some PDU sessions can be 8 bits
  • the QFI of some PDU sessions can be 10 bits. Wait. Support for different QFI lengths can reflect the capabilities of each network element in communication.
  • some radio access network (RAN) devices can support 6-bit, 8-bit, and 10-bit QFI, and some RAN devices can only support 6-bit QFI.
  • some RAN devices can only support 6-bit QFI.
  • the terminal device switches between different RAN devices, if the terminal device uses a 10-bit QFI when communicating with the source RAN device, but the target RAN device does not support a 10-bit QFI, that is, the source RAN device and the target RAN Devices have different support capabilities for QFI.
  • An embodiment of the present application provides a handover method, so that a terminal device maintains data transmission continuity when switching between RAN devices with different QFI support capabilities.
  • an embodiment of the present application provides a handover method.
  • the method includes: a source radio access network RAN device sends a handover request to a target RAN device, and the handover request includes a quality of service flow configured by the source RAN device for a terminal device.
  • the source RAN device receives a handover request confirmation from the target RAN device, the handover request confirmation including the QFI length information configured by the target RAN device for the terminal device; the source RAN device sends a handover command to the terminal device, The handover command includes QFI length information configured by the target RAN device for the terminal device; the source RAN device performs data transfer to the target RAN device; and the source RAN device receives an instruction to release the terminal device context from the target RAN device.
  • the QFI length information is at least one of the following three parameters: a length value of the QFI, a value range of the QFI, and a length level of the QFI.
  • the source RAN device performs data transfer to the target RAN device, including: the source RAN device adapts a QFI length configured for the terminal device to a target RAN device configured for the terminal device. After the QFI length, data transfer is performed to the target RAN device.
  • the target RAN device performs corresponding admission control according to the QFI support capability of the source RAN device and its own QFI support capability, so that the service data can be transmitted using the QFI supported by the target RAN device after the terminal device switches, Ensure the continuity of business data transmission.
  • an embodiment of the present application provides a handover method.
  • the method includes: a target radio access network RAN device receives a handover request from a source RAN device, and the handover request includes a quality of service flow configured by the source RAN device for a terminal device.
  • the target RAN device Identifies QFI length information; the target RAN device performs admission control; the target RAN device sends a handover request confirmation to the source RAN device, the handover request confirmation includes the QFI length information configured by the target RAN device for the terminal device; the target RAN The device receives data transfer from the source RAN device; the target RAN device receives access from the terminal device; the target RAN device sends a path transfer request to the core network CN device; the target RAN device receives a path transfer confirmation from the CN device; and The target RAN device sends an indication of releasing the terminal device context to the source RAN device.
  • the QFI length information is at least one of the following three parameters: a length value of the QFI, a value range of the QFI, and a length level of the QFI.
  • the target RAN device performs admission control, including: the target RAN device performs the access control on the terminal according to the QFI length information configured by the source RAN device for the terminal device and the QFI support capability of the target RAN device.
  • the device performs admission control.
  • the target RAN device receiving data transfer from the source RAN device includes: the target RAN device receives the source RAN device and adapts the QFI length configured for the terminal device to the target RAN device as Data transfer after the QFI length configured by the terminal device.
  • the target RAN device performs corresponding admission control according to the QFI support capability of the source RAN device and its own QFI support capability, so that the service data can be transmitted using the QFI supported by the target RAN device after the terminal device switches, Ensure the continuity of business data transmission.
  • a first access network device for performing the first aspect or the method in any possible implementation manner of the first aspect.
  • the first access network device may include a And a unit for performing the method in the first aspect or any possible implementation manner of the first aspect.
  • a second access network device for performing the second aspect or the method in any possible implementation manner of the second aspect.
  • the second access network device may include a A unit for performing the method in the second aspect or any one of the possible implementation manners of the second aspect.
  • a first access network device including a memory and a processor, where the memory is configured to store a computer program, and the processor is configured to call and run the computer program from the memory, so that the first access network
  • the device executes the first aspect or the method in any possible implementation manner of the first aspect.
  • a second access network device including a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the second access network
  • the device executes the second aspect or the method in any possible implementation manner of the second aspect.
  • a computer program product includes computer program code.
  • the computer program code is used by a communication unit, a processing unit, or a transceiver of a communication device (for example, an access network device or a terminal device).
  • the communication device is caused to execute the method in any one of the first to second aspects or the first to second aspects.
  • a computer-readable storage medium stores a program, and the program causes a computer to execute any one of the first to second aspects or the first to second aspects.
  • FIG. 1 is a network side part of a communication system provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a format of a PDU session container according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an enhanced PDU session container format provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a handover process provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another handover process provided by an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a source RAN device according to an embodiment of the present application.
  • FIG. 8 is another schematic block diagram of a source RAN device according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a target RAN device according to an embodiment of the present application.
  • FIG. 10 is another schematic block diagram of a target RAN device according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a CN device according to an embodiment of the present application.
  • FIG. 12 is another schematic block diagram of a CN device according to an embodiment of the present application.
  • system and "network” are often used interchangeably herein.
  • the term “and / or” in this document is only a kind of association relationship describing related objects, which means that there can be three kinds of relationships, for example, A and / or B can mean: A exists alone, A and B exist simultaneously, and exists alone B these three cases.
  • the character "/" in this text generally indicates that the related objects are an "or" relationship.
  • the handover method and apparatus provided in the embodiments of the present application are applicable to handover of a terminal device when different RAN devices have different QFI support capabilities.
  • FIG. 1 shows a network side portion 100 of a communication system provided in an embodiment of the present application.
  • the network side portion 100 includes a next generation core network (next generation core (NGC) (also referred to as 5GC) and a next generation wireless access network (5GC).
  • NGC next generation core network
  • 5GC next generation wireless access network
  • 5GC mainly includes control plane network elements (such as mobility management function (AMF) and session management function (SMF), etc.) and user plane network element (UPF).
  • AMF is mainly responsible for terminal equipment access and mobility management
  • SMF is mainly responsible for session management, terminal IP address allocation, etc.
  • UPF is mainly responsible for data packet routing and forwarding, QoS management, etc.
  • AMF, SMF and UPF can also be called core network (CN) equipment.
  • the network elements of NG-RAN mainly include next-generation base stations, such as next-generation Node B (gNB) or next-generation evolved Node B (ng-eNB).
  • the gNB and ng-eNB are also called RAN devices and provide user plane and control plane functions.
  • the interface between 5GC and NG-RAN can be defined as an NG interface.
  • the control plane interface between 5GC and NG-RAN can be defined as an NG-C interface
  • the user plane interface between 5GC and NG-RAN can be defined.
  • NG-U interface; the interface between different network elements (such as two gNBs) of NG-RAN can be defined as Xn interface.
  • the network elements of NG-RAN in Figure 1 can also be access points (APs) in Wireless Local Area Networks (WLAN), base stations (BTS) in GSM or CDMA, and WCDMA.
  • APs access points
  • WLAN Wireless Local Area Networks
  • BTS base stations
  • WCDMA Wideband Code Division Multiple Access
  • Base station (NodeB, NB) or relay station or access point, or in-vehicle equipment, wearable equipment, and network equipment in the future 5G network or future evolution of public land mobile network (PLMN)
  • the network access device may be, for example, a transmission and reception point (TRP), a centralized processing unit (CU), a distributed processing unit (DU), and the like.
  • TRP transmission and reception point
  • CU centralized processing unit
  • DU distributed processing unit
  • the terminal device communicates with the network element of the NG-RAN through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell managed by the network element of the NG-RAN, and the cell may belong to a macro cell ( macro cell), a super cell, or a small cell.
  • the small cell may include: a city cell, a micro cell, a pico cell, a micro cell Femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • CU and DU can be physically separated or deployed together. Multiple DUs can be connected to one CU. One DU can also connect multiple CUs. The CU and the DU can be connected through a standard interface (such as an F1 interface).
  • the respective functions of CU and DU can be divided according to the protocol layer of the wireless network. For example, radio resource control (RRC), service data adaptation protocol stack (SDAP), and packet data convergence layer protocol (PDCP) layer functions are set in the CU, and the wireless chain
  • RRC radio resource control
  • SDAP service data adaptation protocol stack
  • PDCP packet data convergence layer protocol
  • RLC radio control
  • MAC media access control
  • PHY physical
  • the division of the CU and DU processing functions according to this protocol layer is only an example, and the respective functions of the CU and DU can also be divided in other ways.
  • the CU or DU can also be divided into parts with a protocol layer. Processing functions.
  • part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are set in the DU.
  • the functions of the CU or DU may also be divided according to service types or other system requirements.
  • the functions that need to meet the delay requirements in processing time are set in the DU, and the functions that do not need to meet the delay requirements in processing events are set in the CU.
  • the CU may also have one or more functions of the core network.
  • One or more CUs can be set centrally or separately.
  • the CU can be set on the network side to facilitate centralized management.
  • the DU can have multiple radio frequency functions, and can also set the radio frequency function remotely.
  • the functions of the CU can be implemented by one entity or by different entities.
  • the functions of the CU can be further divided to separate the control plane (CP) and the user plane (UP), that is, the control plane (CU-CP) and the CU user plane (CU-UP) of the CU.
  • CU-CP and CU-UP can be implemented by different functional entities, and CU-CP and CU-UP can be coupled with the DU to complete the functions of the RAN device.
  • the CU-CP is responsible for the control plane functions, mainly including RRC and PDCP-C.
  • PDCP-C is mainly responsible for encryption and decryption of control plane data, integrity protection, and data transmission.
  • CU-UP is responsible for user plane functions, mainly including SDAP and PDCP-U.
  • SDAP is mainly responsible for processing the data of the core network and mapping the data stream to the wireless bearer.
  • PDCP-U is mainly responsible for data plane encryption and decryption, integrity protection, header compression, serial number maintenance, and data transmission.
  • CU-CP and CU-UP can be connected through standard interfaces (such as E1 interface).
  • CU-CP means that the gNB is connected to the core network through the NG interface, and is connected to the DU through F1-C.
  • CU-UP is connected to DU through F1-U.
  • the PDCP-C is also in the CU-UP.
  • Terminal equipment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user Agent or user device.
  • the terminal device can be a station (ST) in WLAN, it can be a cell phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital processing (personal digital assistant, PDA) devices, handheld devices with wireless communication capabilities, relay devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and next-generation communication systems, such as in 5G networks Terminal equipment in the future, or terminal equipment in a future evolved PLMN.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the terminal device may also be a wearable device.
  • Wearable devices can also be referred to as wearable smart devices, which are the general name for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a device that is worn directly on the body or is integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also powerful functions through software support, data interaction, and cloud interaction.
  • Broad-spectrum wearable smart devices include full-featured, large-sized, full or partial functions that do not rely on smart phones, such as smart watches or smart glasses, and only focus on certain types of application functions, and need to cooperate with other devices such as smart phones Use, such as smart bracelets, smart jewelry, etc. for physical signs monitoring.
  • the NG-RAN equipment and terminal equipment of the 5G system have added the SDAP layer on top of the packet data convergence layer protocol (PDCP) layer.
  • PDCP packet data convergence layer protocol
  • One PDU session corresponds to one.
  • the SDAP layer is responsible for the mapping of the QoS flow to the DRB, and may add the QFI corresponding to the QoS flow to the header of the data packet of the QoS flow.
  • the NG-RAN may configure whether an uplink data packet or a downlink data packet in a DRB of a terminal device carries an SDAP header through an RRC message. When the downlink data packet is configured to carry the SDAP header, the SDAP layer of the RAN device needs to carry the QFI for each downlink data packet.
  • FIG. 2 shows a SDAP protocol data unit format, in which the RDI field, RQI field, and QFI field form the header of the SDAP protocol data unit.
  • the RDI field is used to indicate whether the AS layer performs reflection mapping
  • the RQI field is used to indicate whether the NAS layer performs reflection QoS.
  • the AS layer is mainly responsible for the mapping relationship between QoS flows and data radio bearers (DRB).
  • NG-RAN For downlink data, NG-RAN is implemented through mapping rules at the AS layer, that is, NG-RAN configures the mapping relationship between QoS flows and DRB, and provides QoS services for QoS flows through DRB on the air interface.
  • NG-RAN Notifying the terminal device of the mapping relationship between the QoS flow and the DRB.
  • One or more QoS flows can be mapped onto one DRB. Data packets on the same DRB get the same forwarding processing.
  • NG-RAN can configure the mapping relationship between uplink transmission of QoS flow and DRB for the terminal device by means of RRC signaling or reflective mapping.
  • Reflection mapping refers to that the terminal device detects the QFI carried in the downlink data packet, and maps the uplink data packet with the same QFI QoS flow to the DRB carrying the downlink data packet, that is, the uplink data packet and the downlink data packet are carried in the same DRB. on. Exemplarily, a downlink data packet of a QoS flow is mapped to the first DRB. If reflection mapping is adopted at the AS layer, an uplink data packet of the QoS flow is also mapped to the first DRB.
  • Different RAN devices have different support capabilities for QFI due to their respective capabilities or different implemented protocol versions. For example, some RAN devices can only support short-length QFI (that is, the QFI value range is small), while other RAN devices can support short-length QFI and long-length QFI (that is, the QFI value range is large).
  • the terminal device is switched from one RAN device to another RAN device, the QFI support capabilities of different RAN devices are different, so the service data cannot be performed according to the QFI used by the terminal device in the source RAN device. Transmission, otherwise the target RAN device may fail to recognize the corresponding QFI, resulting in loss of business data.
  • an embodiment of the present application provides a technical solution for switching a terminal device between RAN devices with different QFI support capabilities.
  • FIG. 3 illustrates a format of a PDU session container for indicating a QFI QoS flow of 6 bits in length.
  • the format of the PDU session container will change when it transmits data with other RAN devices or with CN devices, such as QFI marked with a longer number of bits.
  • FIG. 4 illustrates an enhanced PDU session container format in which the QFI is 14 bits in length. It should be understood that the enhanced PDU session container shown in FIG. 4 is only exemplary, and there may be other ways to enhance the format shown in FIG. 3 to identify QFIs with a length greater than 6 bits, which will not be described herein again.
  • the terminal device can report its support capability for QFIs of different lengths to the CN device through NAS signaling.
  • the terminal device may also report its support capability for QFIs of different lengths to the RAN device through AS signaling.
  • the CN device may send the terminal device's acquired QFI support capabilities of different lengths to the RAN device.
  • the RAN device may also send the terminal device's acquired QFI support capability to the CN device.
  • the RAN device can also report its own support for QFIs of different lengths to the CN device, such as through NG setup request messages, RAN configuration update messages, and AMF configuration update confirmations.
  • the acknowledgement message or the NG reset message carries the corresponding indication.
  • the RAN device can report its capability of not supporting longer QFI (such as QFI longer than 6 bits) to the CN device, such as in the AMF configuration update failure / error indication message.
  • the cause field carries a corresponding indication.
  • the CN device can also notify the RAN device of its own ability to support QFIs of different lengths, such as through NG setup response (NG setup response) messages, RAN configuration update confirmation (RAN configuration update acknowledgement) messages, AMF configuration update (AMF configuration update) ) Message or NG reset (NG reset) message carries the corresponding indication.
  • NG setup response NG setup response
  • RAN configuration update confirmation RAN configuration update acknowledgement
  • AMF configuration update AMF configuration update
  • NG reset NG reset
  • the CN device can notify the RAN device of its ability not to support longer QFI (such as QFI longer than 6 bits), such as via NG setup failure message, RAN configuration update failure / error indication (RAN configuration The cause field in the update failure / error indication message carries the corresponding indication. Therefore, the CN device learns the RAN device and the terminal device's support capabilities for QFIs of different lengths, so as to determine the length of the QFI used when establishing or modifying a PDU session for the terminal device. Through the above steps, the length of the QFI used for data transmission between the terminal device and the RAN device, and the RAN device and the CN device is determined.
  • QFI such as QFI longer than 6 bits
  • different RAN devices may support short QFI (such as a 6-bit length) and some RAN devices may support a longer QFI (such as a 10-bit length) due to their respective capabilities or different implemented protocol versions. ).
  • the terminal device switches between different RAN devices, the network needs to adapt the QFI capabilities of different RAN devices.
  • FIG. 5 is a schematic flowchart of a handover method of a terminal device according to an embodiment of the present application. It should be understood that FIG. 5 is a schematic flowchart of a communication method according to an embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are merely examples, and other operations may be performed in the embodiment of the present application Or a modification of various operations in FIG. 5. In addition, each step in FIG. 5 may be performed in a different order than that presented in FIG. 5, and it may not be necessary to perform all operations in FIG. 5.
  • the method 500 is applicable to a scenario where the QFI support capability of the source RAN device switched by the terminal device is higher than the QFI support capability of the target RAN device.
  • the process includes the following steps:
  • the source RAN device sends a handover request to the target RAN device.
  • the handover request includes QFI length information configured by the source RAN device for the terminal device.
  • the QFI length information may be for a PDU session or for a DRB. It should be understood that when the terminal device has multiple DRBs, the handover request includes QFI length information of each DRB.
  • the handover request contains the QFI length information of each PDU.
  • the handover request also includes the QFI and QoS parameters of one or more QoS flows in the PDU session or DRB. It is worth noting that when the source RAN device establishes communication with the terminal device, the source RAN device sends QFI length information of each PDU session or each DRB that communicates with the terminal device to the terminal device. In this step, the source RAN device sends the QFI length information of each PDU session or DRB to the target RAN device.
  • the source RAN device sends the QFI length information used by the PDU session to the target RAN device.
  • the QFI length values used by all QoS flows in the PDU session are the same.
  • a PDU session includes three QoS flows, each of which is identified using a QFI with a length of 6 bits.
  • the source RAN device sends the length information of multiple QFIs used by the PDU session to the target RAN device.
  • different QoS flows in the PDU session may use different QFI lengths.
  • a PDU session includes three QoS flows.
  • the first QoS flow can be identified by a QFI with a length of 6 bits
  • the second QoS flow can be identified by a QFI with a length of 8 bits
  • the third QoS flow can be identified by a length of A 10-bit QFI is used for identification; optionally, the first and second QoS flows may be identified using a QFI with a length of 6 bits, and a third QoS flow may be identified using a QFI with a 10-bit length.
  • one piece of QFI length information sent by the source RAN device to the target RAN device may be for all QoS flows in one DRB.
  • the length information of the QFI may have various forms to indicate the length of the QFI.
  • the length information of the QFI may be a length value of the QFI.
  • the length information of a QFI is the length value of the QFI, such as 6 bits, 8 bits, or 10 bits.
  • the length information of the QFI may be a value range of the QFI.
  • the length information of a QFI is the QFI value range, such as 0 to 63 (the value range corresponds to a QFI length of 6 bits), 0 to 255 (the value range corresponds to a QFI length of 8 bits), Or 0 to 1023 (this value range corresponds to a QFI length of 10 bits) and so on.
  • the length information of the QFI may be a length level of the QFI.
  • the length information of a QFI is the QFI length level, such as a long QFI or a short QFI.
  • different lengths of the QFI that can be used by the network side and the terminal device are set by the standard or defined by the operator, such as 6 and 10 bits, and both the network side and the terminal device have been obtained before the PDU session is established. The information.
  • the QFI length information sent by the source RAN device to the target RAN device is short QFI, it means that the QFI length used by the source RAN device is 6 bits; if the QFI length information sent by the source RAN device to the target RAN device is A long QFI indicates that the QFI length used by the source RAN device is 10 bits.
  • the source RAN device may indicate by using a 1-bit field. For example, setting a bit value of this field to "0" means using a short QFI, and setting a bit value of this field to "1" means using a long QFI.
  • a QFI can have multiple levels of length, such as long QFI, medium QFI, and short QFI.
  • the network side and the terminal device are set by the standard or defined by the operator.
  • the network side and the terminal device can use three or more different lengths, such as 6-bit, 8-bit, and 10-bit.
  • the terminal device has obtained this information.
  • the QFI length information sent by the source RAN device to the target RAN device is short QFI, it means that the QFI length used by the source RAN device is 6 bits; if the QFI length information sent by the source RAN device to the target RAN device is Medium QFI indicates that the QFI length used by the source RAN device is 8 bits; if the QFI length information sent by the source RAN device to the target RAN device is long QFI, it means that the QFI length used by the source RAN device is 10 bits.
  • the source RAN device may indicate by using a 2-bit field. For example, setting the bit value of this field to "00" means using short QFI, and setting the bit value of this field to "01" means using medium QFI. Setting the bit value of this field to "10” means using long QFI.
  • the QFI length information can also be indicated by other implicit methods, such as indirect indication through other information.
  • the source RAN device notifies the target RAN device of the SDAP header length information configured for the terminal device, and implicitly indicates different QFI lengths when the SDAP header length belongs to different ranges. For example, when the SDAP header length is greater than 1 byte, it indicates that the QFI length is 8 bits, and when the SDAP header length is less than or equal to 1 byte, it indicates that the QFI length is 6 bits.
  • the handover request message may further include QFI length information of uplink transmission of the QoS flow and QFI length information of downlink transmission of the QoS flow, respectively.
  • the handover request message includes QFI length information of uplink transmission of all QoS flows and QFI length information of downlink transmission of all QoS flows in the PDU session.
  • the handover request message includes QFI length information of uplink transmission of one or more QoS flows and QFI length information of downlink transmission of one or more QoS flows in the PDU session.
  • the handover request may further include the QFI support capability of the terminal device, such as the length information of the QFI used by the terminal device.
  • the target RAN device performs admission control.
  • the target RAN device performs admission control on the terminal device according to its support capability, resource situation, QFI length information sent by the source RAN device, and its own QFI support capability for the service that the terminal device communicates with the source RAN device. Further, the target RAN device may also perform admission control on the terminal device according to the QFI support capability of the terminal device.
  • the target RAN device may deny access to the QoS flow of the terminal device outside its support capability range.
  • the target RAN device also denies access to the QoS flow of the terminal device according to other criteria.
  • the QFI range supported by the source RAN device is 0 to 255
  • the QFI range supported by the target RAN device is 0 to 63. It means that the QFI support capability of the target RAN device is lower than the QFI support capability of the source RAN device, then the target RAN device Admission control may be considered for QoS flows in the source RAN device with QFI values ranging from 0 to 63, while QoS flows with QFI values ranging from 64 to 255 may be directly rejected. It should be understood that when the QFI support capability of the target RAN device is lower than the QFI support capability of the source RAN device, the target RAN device can still identify the QFI sent by the source RAN device.
  • the target RAN device can only support QFI with a range of 0 to 63 (that is, 6-bit length), and the source RAN device includes a QFI range of 0 to 255 (that is, 8-bit length), the target RAN device still has It can recognize QFI with a range of 64 to 255, but it does not support 8-bit QFI.
  • the target RAN device sends a handover request confirmation to the source RAN device.
  • the handover request confirmation includes QFI length information configured by the target RAN device for the terminal device. It should be understood that the target RAN device configures the QFI length information for the terminal device according to its QFI support capability, and the target RAN device may further configure the QFI length information for the terminal device according to the QFI support capability of the terminal device.
  • the QFI length information may be for a PDU session or for a DRB. It should be understood that when the terminal device has multiple DRBs, the handover request includes QFI length information of each DRB. When the terminal device has multiple PDU sessions, the handover request contains the QFI length information of each PDU.
  • the QFI length information may be a display indication or an implicit indication.
  • the handover request confirmation also includes the QFI of one or more QoS flows in the PDU session admitted by the target RAN device after admission control.
  • the handover request confirmation further includes the QFI of one or more QoS flows that the target RAN device rejects after admission control. These rejected QoS flows may be rejected by the target RAN device due to insufficient resources of the target RAN device, or may be rejected by the target RAN device because the QFI target RAN device of these QoS is not supported.
  • the target RAN device allocates tunnel information for each successfully accepted PDU session for data transfer.
  • the handover request confirmation may further include data transfer tunnel information, and the tunnel information may include PDU session level tunnel information, and may also include DRB level tunnel letter information; or the tunnel information includes PDU session level tunnel information.
  • the tunnel information includes the transport layer address and the tunnel port identification.
  • the source RAN device sends a handover command to the terminal device.
  • the handover command includes QFI length information configured by the target RAN device for the terminal device.
  • the QFI length information may be for a PDU session or for a DRB. It should be understood that when the terminal device has multiple DRBs, the handover request includes QFI length information of each DRB. When the terminal device has multiple PDU sessions, the handover request contains the QFI length information of each PDU.
  • the handover command also includes the QFI of one or more QoS flows accepted by the target RAN device after admission control.
  • the source RAN device sends a data transfer to the target RAN device.
  • the source RAN device directly transfers data to the target RAN device.
  • the source RAN device first transfers data to the CN device, and then the CN device transfers the data to the target RAN device.
  • the QFI length information needs to be included in the GTP-U header, and the QFI length of the QoS flow of the source device at the source RAN device is greater than the QFI length supported by the target RAN device.
  • the QFI format for transmission, the target RAN device cannot recognize it. Therefore, the source RAN device needs to send using the QFI length supported by both the source RAN device and the target RAN device.
  • the source RAN device performs QoS flow adaptation, that is, the source RAN device adapts the QFI of one or more QoS flows of the terminal device in the source RAN device to the QFI supported by the target RAN device, and then performs data transfer.
  • the source RAN device adapts the QFI length configured for the terminal device to the QFI length configured for the terminal device by the target RAN device, and then performs data transfer to the target RAN device.
  • the terminal device accesses the target RAN device.
  • the terminal device accesses the target RAN device, and establishes communication with the target RAN device to implement data transmission.
  • the target RAN device sends a path transfer request to the CN device.
  • the CN device sends a path transfer confirmation to the target RAN device.
  • the CN device may send an end marker to the source RAN device to indicate that the CN device does not subsequently send any data to the source RAN device; the source RAN device may also forward the end marker to the target RAN device.
  • the target RAN device sends an indication of releasing the terminal device context to the source RAN device.
  • the target RAN device performs corresponding admission control according to the QFI support capability of the source RAN device and its own QFI support capability, so that the service data can be transmitted using the QFI supported by the target RAN device after the terminal device switches, Ensure the continuity of business data transmission.
  • FIG. 6 is a schematic flowchart of another handover method of a terminal device according to an embodiment of the present application. It should be understood that FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present application, and illustrates detailed communication steps or operations of the method, but these steps or operations are merely examples, and other operations may be performed in the embodiment of the present application. Or a modification of various operations in FIG. 6. In addition, each step in FIG. 6 may be performed in a different order from that presented in FIG. 6, and it may not be necessary to perform all operations in FIG. 6.
  • the method 600 is applicable to a scenario where the QFI support capability of the source RAN device switched by the terminal device is higher than the QFI support capability of the target RAN device.
  • the process includes the following steps:
  • the source RAN device sends a switching request to the CN device.
  • the handover requirement includes the identity of the target RAN device.
  • the CN device performs QoS flow adaptation.
  • the CN device receives the handover request sent by the source RAN device, and queries the QFI support capability of the target RAN device according to the identity of the target RAN device in the handover requirement.
  • the QoS flow information sent by the CN device to the target RAN device is adapted according to the QFI support capability of the target RAN device.
  • the CN device performs QoS flow adaptation, that is, the CN device adapts the QFI of one or more QoS flows of the terminal device in the source RAN device to the QFI supported by the target RAN device.
  • the range of QFI values supported by the source RAN device is 0 to 255 and the range of QFI values supported by the target RAN device is 0 to 63
  • the range of QFI values corresponding to the QoS flow sent by the CN device to the target RAN device It is 0 to 63.
  • CN equipment needs to perform QoS flow adaptation.
  • the CN device may adopt different methods to adapt the QoS flow between the source RAN device and the target RAN device.
  • the CN device only sends the QFI and QoS parameters of the QoS flow within the range of the QFI support capability of the target RAN device to the target RAN device for admission control.
  • the CN device aggregates one or more QoS flows of the terminal devices served by the source RAN device into one QoS flow with a new QFI.
  • the CN device sends three QoS flows to the source RAN device.
  • the QoS flows are aggregated into a new QoS flow, and the original three QoS flows are indicated by three QFIs.
  • the new QoS flows need only one QFI to indicate, thereby reducing the number of QoS flows. It should be understood that the QFI range of the QoS flow used to indicate the terminal device of the source RAN device can be reduced by this QoS flow aggregation method.
  • the QFI range of the QoS flow of the terminal device of the source RAN device is 0 to 255. After the aggregation of these QoS flows, the number of generated QoS flows can be greatly reduced, so that the QFI range used to indicate the aggregated QoS flows is between 0 and 63.
  • the source RAN device can support QFI ranging from 0 to 255
  • the target RAN device can support QFI ranging from 0 to 63
  • the QFI support capability of the source RAN device is higher than the QFI support capability of the target RAN device.
  • the CN device adapts the QFI corresponding to the QoS flow of the terminal device from a range of 0 to 255 to a range of 0 to 63, for example, a QFI with a value of "00110101" is adapted to a value The QFI is "110101" so that the QFI value range meets the QFI support capability of the target RAN device.
  • the CN device can directly reject the QoS flow for which the terminal device has a QFI value of more than 63 in the source RAN device without sending it to the target RAN device for admission control.
  • the QoS flow whose QFI value is "01001011" is directly rejected because the upper two bits of the QFI value are non-zero, which exceeds the length of the QFI supported by the target RAN device.
  • the CN device aggregates and adapts multiple QoS flows of the terminal device in the source RAN device to a new QoS flow on the target RAN device.
  • the CN device aggregates the three QoS flows of the terminal device in the source RAN device with values of "00101101", "01001110", and "10001101" into a QoS flow in the target RAN device and sends the QoS flow to the QFI.
  • the value is "100111”.
  • the CN device sends a handover request to the target RAN device.
  • the switching request includes the QFI and QoS parameters of one or more QoS flows after the CN device performs QoS flow adaptation.
  • the target RAN device performs admission control.
  • the target RAN device performs admission control on the QoS flow according to the QFI received from the CN device and the QoS parameters of the corresponding QoS flow.
  • the target RAN device performs admission control according to its own ability to support the service of the terminal device and the resource situation.
  • the target RAN device sends a handover request confirmation to the CN device.
  • the target RAN device sends the QFI of the QoS flow through admission control to the CN device.
  • the handover request confirmation includes tunnel information allocated by the target RAN device for each admitted PDU session, and the tunnel information is used for data transmission between the target RAN device and the CN device.
  • the tunnel information can be PDU session level or DRB level.
  • the target RAN device can perform full configuration, that is, re-configure all RRC resources for the terminal device (such as wireless bearer Configuration, etc.) without having to inherit the corresponding RRC configuration in the source RAN device.
  • the CN device performs QoS flow restoration.
  • the CN device performs QoS flow restoration according to the admission control result of the target RAN device. Specifically, the CN device performs QoS flow restoration, that is, the CN device restores the QFI of one or more QoS flows of the terminal device that has been adapted to the target RAN device to one or more QoS flows of the terminal device at the source RAN device.
  • QFI QoS flow adaptation
  • a terminal device with a QFI value of "00110101” in the source RAN device is adapted to a QFI value of "110101" in the target RAN device.
  • the target RAN device accepts the QoS flow corresponding to the QFI.
  • the CN device restores the QFI value of the terminal device in the target RAN device to "110101" to the terminal device.
  • the QFI value of the source RAN device is "00110101".
  • the CN device sends a handover command to the source RAN device.
  • the handover command includes the QoS flow of the communication between the source RAN device and the terminal device admitted by the target RAN device.
  • the handover command further includes an RRC resource allocated by the target RAN device to the terminal device.
  • the handover command may further include a correspondence between a QoS flow of the terminal device at the source RAN device and an adapted QoS flow at the target RAN device.
  • the source RAN device sends a handover command to the terminal device.
  • the handover command includes RRC resources allocated by the target RAN device to the terminal device.
  • the source RAN device performs data transfer to the target RAN device.
  • the source RAN device directly forwards data to the target RAN device.
  • the source RAN device transfers data in the PDU session tunnel.
  • the QFI information carried in the GTP-U header needs to use the QFI length supported by both the source RAN device and the target RAN device, and the source RAN device can send it according to the CN device.
  • the corresponding relationship between the target RAN device and the QFI of the source RAN device after mapping the QFI of the source RAN device to the QFI of the target RAN device, the data of the QoS flow corresponding to the QFI is forwarded to the target RAN device.
  • the source RAN device adapts the QFI length configured for the terminal device to the QFI length configured for the terminal device by the target RAN device, and then performs data transfer to the target RAN device.
  • the source RAN device forwards the data to the CN device, and the CN device forwards the data to the target RAN device.
  • the source RAN device can use the QFI length supported by the source RAN device to transfer the data to the CN device, and the CN device uses the adapted method to transfer the data to the target RAN device.
  • the terminal device accesses the target RAN device.
  • the target RAN device sends a path transfer request to the CN device.
  • the CN device sends a path transfer confirmation to the target RAN device.
  • the target RAN device sends an indication of releasing the terminal device context to the source RAN device.
  • steps 610-613 are similar to steps 506-509 of the foregoing embodiment, and details are not described herein again.
  • the CN device may send an end marker to the source RAN device to indicate that the CN device will no longer send data to the source RAN device in the future; the source RAN device may also forward the end marker to the target RAN device. .
  • the CN device adapts the QoS flow according to the QFI support capability of the source RAN device and the QFI support capability of the target RAN device, so that the service data of the terminal device can be processed using the QFI supported by the target RAN device.
  • Transmission ensures the continuity of business data transmission.
  • the source RAN device can also actively make the QFI length used by itself and the target RAN device The supported QFI lengths are equal before initiating handover. Specifically, the source RAN device obtains the QFI support capability of the target RAN device before sending a handover request or a handover request. The source RAN device adapts the QoS flow of the terminal device between different QFI capabilities, and includes the QFI of the adapted QoS flow in sending the handover request or handover request.
  • the source RAN device can support QFI ranging from 0 to 255
  • the target RAN device can support QFI ranging from 0 to 63
  • the QFI support capability of the source RAN device is higher than the QFI support capability of the target RAN device.
  • the source RAN device establishes an Xn interface with the target RAN device or in other cases, the source RAN device acquires the QFI support capability of the target RAN device.
  • the source RAN device performs QoS flow adaptation, that is, the QFI corresponding to the QoS flow of the terminal device is adapted from the range of 0 to 255 to the range of 0 to 63.
  • the source RAN device sends a handover request to the target RAN device or sends a handover request to the CN device, it includes the adapted QFI.
  • the source RAN device adapts the QoS flow to a QFI of "110101” and the QoS parameters of the QoS flow are sent to the target RAN device or CN device .
  • the handover process of the terminal device is similar to the handover process in the prior art, and details are not described herein again.
  • the source RAN device actively performs capacity adaptation according to its own QFI support capability and the target RAN device's QFI support capability, so that the service data can be transmitted using the QFI supported by the target RAN device after the terminal device is switched, ensuring that Continuity of business data transmission.
  • the handover procedure of the terminal device is similar to the handover procedure in the prior art.
  • the target RAN device learns from the handover request received by the source RAN device that the QFI support capability of the source RAN device is lower than its own QFI support capability; at this time, the target RAN device actively makes its own QFI length and the source RAN device support
  • the QFI lengths are equal, that is, the same QFI as the source RAN device is used to indicate the QoS flow.
  • the source RAN device can support QFI ranging from 0 to 63
  • the target RAN device can support QFI ranging from 0 to 255
  • the QFI support capability of the source RAN device is lower than the QFI support capability of the target RAN device.
  • the target RAN device receives a 6-bit QFI in the handover request from the source RAN device
  • the target RAN device does not use its higher QFI support capability to convert the QFI to an 8-bit length, but still uses the 6-bit length QFI and does not change the value of QFI.
  • the target RAN device needs to notify the CN device of the QFI length information used for the terminal device, for example, by means of a path transfer request. In this way, it is no longer necessary to perform adaptation between QFIs of different lengths during the handover process, and each device in the network can perform operations according to the existing handover process.
  • the target RAN device actively performs capacity adaptation according to its QFI support capability and the QFI support capability of the target RAN device, so that after the terminal device switches service data, it can use the QFI supported by the target RAN device to transmit, ensuring that Continuity of business data transmission.
  • the source RAN device when the existing terminal device switches between different RAN devices, the source RAN device includes the mapping relationship between the QoS flow configured by the source RAN device for the terminal device and the DRB in the handover request message sent to the target RAN device.
  • the source RAN device In the case where the AS layer uses reflection mapping, that is, the uplink transmission of a QoS flow and the downlink transmission of the QoS flow are mapped to the same DRB, the source RAN device only needs to transfer the QoS flow configured for the terminal device to The mapping relationship of the DRB may be sent to the target RAN device.
  • the AS layer does not use reflection mapping, the uplink transmission of a QoS flow and the downlink transmission of the QoS flow can be mapped to different DRBs.
  • the uplink transmission and downlink transmission of the QoS flow have different QoS. parameter. Therefore, the existing handover request message is no longer suitable for non-reflective mapping scenarios.
  • the source RAN device sends the mapping relationship between the uplink transmission of a QoS flow configured to the terminal device to the DRB and / or the mapping relationship between the downlink transmission of the QoS flow and the DRB to the target RAN device, thereby After the handover, ensure that the downstream device delivers the downstream data packets to the upper layer in order and the target RAN device forwards the upstream data packets to the CN device in order.
  • the source RAN device includes a mapping of the QoS flow uplink and downlink transmission to the DRB in the handover request message sent to the target RAN device. relationship.
  • the mapping relationship between uplink and downlink transmission of the QoS flow to the DRB refers to a mapping relationship between uplink transmission to the DRB of a QoS flow configured by the source RAN device for the terminal device and / or a mapping relationship between downlink transmission to the DRB of the QoS flow.
  • the mapping relationship between the uplink and downlink transmission of the QoS flow to the DRB may be expressed in an explicit manner, a container manner, or a combination of the two methods.
  • the source RAN device sends the source DRB to the QoS flow to the target RAN device.
  • the mapping list includes the QFI of one or more QoS flows and the downstream differences of the one or more QoS flows.
  • the source RAN device includes a mapping relationship between uplink and downlink transmission of the QoS flow to the DRB in the handover request message sent to the CN device.
  • the handover request message sent by the CN device to the target RAN device includes a mapping relationship between uplink and downlink transmission of the QoS flow to the DRB.
  • the source RAN device In the process of the terminal device switching from the source RAN device to the target RAN device, for the downlink transmission, the source RAN device needs to forward the downlink data that has not been correctly received by the terminal device to the target RAN device during the downlink transmission, and the target RAN device repeats it. Issued to the terminal device.
  • the target RAN device obtains the mapping relationship between the uplink and downlink transmission of the QoS flow configured by the source RAN device for the terminal device to the DRB.
  • the target RAN device can The RAN device sends downlink data to the terminal device on a DRB with the same configuration.
  • the target RAN device For the new downlink data sent from the CN device, if the target RAN device changes the mapping of the downlink transmission of the QoS flow to the DRB, the target RAN device uses the new DRB to send the downlink data; if the target RAN device uses the source RAN device With the same mapping relationship, the target RAN device sends downlink data on a DRB with the same configuration as the source RAN device. The target RAN device first sends the data forwarded from the source RAN device, and then sends the new downlink data received from the core network. If the target RAN device does not adopt the same mapping relationship as the source RAN device, the target RAN device will send new downlink data received from the CN device on the new DRB.
  • the target RAN device can confirm that the downlink data transferred from the source RAN device is correctly received by the terminal device, and then send the new downlink data received from the CN device to the terminal device, thereby ensuring the continuity of service data transmission and ensuring
  • the terminal device can sequentially submit the received downlink data to the upper layer (such as the application layer).
  • the source RAN device For uplink transmission, the source RAN device needs to forward the data that was not received in order in the uplink transmission to the target RAN device.
  • the terminal device needs to resend the uplink data that has not been correctly received by the source RAN device to the target RAN device in the uplink transmission.
  • the target RAN device sorts the uplink data received from the source RAN device and the terminal device and sends it to the CN device.
  • the terminal device For uplink data that has not been correctly received by the source RAN device, the terminal device resends the uplink data to the target RAN device on a DRB with the same configuration as the source RAN device.
  • the terminal device sends an end marker on the source DRB to indicate that the terminal device no longer sends uplink data on the source DRB.
  • the terminal transmits the uplink data on the new DRB adopted by the target RAN device.
  • the end tag is an end tag control PDU of the SDAP layer of the terminal device.
  • the terminal device transmits new uplink data on the source DRB.
  • the target RAN device when the target RAN device changes the mapping relationship of the QoS flow to the uplink transmission to the DRB, the target RAN device starts to receive the QoS flow received from the new DRB after receiving the end marker sent by the terminal device.
  • the data is submitted to the core network, thereby ensuring the continuity and orderly submission of business data.
  • the source RAN device configures a mapping relationship between uplink and downlink transmission of one or more QoS flows to the DRB for the terminal device. Further, the source RAN device notifies the terminal device of the mapping relationship of the uplink transmission of the one or more QoS flows to the DRB through air interface signaling. It should be understood that these operations are not limited to being performed before the terminal device is switched, and may be performed when the serving RAN device performs DRB configuration when the terminal device establishes communication with the RAN device.
  • the uplink data and the downlink data of the terminal device after the handover can be effectively transmitted on the appropriate DRB. To ensure the continuity and orderly submission of business data transmission.
  • the target RAN device acquires the QFI support capability of the other party, for example, the QFI support capability of the source RAN device and the target RAN device are exchanged during the Xn port establishment process.
  • the specific handover process is consistent with FIG. 5 and FIG. 6.
  • the main difference is that the source RAN device and the target RAN device do not need to exchange corresponding QFI length information during the handover process.
  • service data can be transmitted using the QFI supported by the target RAN device after the terminal device is switched, thereby ensuring the continuity of service data transmission.
  • FIG. 7 shows a schematic block diagram of a communication device 700 according to an embodiment of the present application.
  • the communication device 700 may correspond to (for example, be configured on or be itself) the source RAN device described in the foregoing method embodiments.
  • the communication device 700 may include a processor 701 and a transceiver 702, and the processor and the transceiver are communicatively connected.
  • the communication device 700 further includes a memory 703, and the memory 703 is communicatively connected to the processor 701.
  • the processor 701, the memory 703, and the transceiver 702 may be communicatively connected.
  • the memory 703 may be used to store instructions, and the processor 701 is configured to execute the instructions stored in the memory to control the transceiver 702 to send information or signals.
  • the processor 701 and the transceiver 702 are respectively configured to perform various actions or processes performed by the source RAN device in the foregoing method embodiments.
  • detailed description is omitted.
  • FIG. 8 shows a schematic block diagram of a communication apparatus 800 according to an embodiment of the present application.
  • the communication apparatus 800 may correspond to (for example, be configured on or be itself) the source RAN device described in the foregoing method embodiments.
  • the communication device 800 may include a receiving module 801, a processing module 802, and a sending module 803.
  • the processing module 802 is communicatively connected to the receiving module 801 and the sending module 803, respectively.
  • Each module or unit in the communication device 800 is configured to perform each action or processing procedure performed by the source RAN device in each of the foregoing method embodiments.
  • detailed description is omitted.
  • FIG. 9 shows a schematic block diagram of a communication device 900 according to an embodiment of the present application.
  • the communication device 900 may correspond to (for example, be configured on or be itself) a target RAN device described in each of the foregoing method embodiments.
  • the communication device 900 may include a processor 901 and a transceiver 902, and the processor and the transceiver are communicatively connected.
  • the communication device 900 further includes a memory 903, and the memory 903 is communicatively connected to the processor 901.
  • the processor 901, the memory 903, and the transceiver 902 may be communicatively connected.
  • the memory 903 may be used to store instructions.
  • the processor 901 is configured to execute the instructions stored in the memory to control the transceiver 902 to send information or signals.
  • the processor 701 and the transceiver 702 are respectively configured to perform various actions or processing processes performed by the target RAN device in the foregoing method embodiments. Here, in order to avoid redundant description, detailed description is omitted.
  • FIG. 10 shows a schematic block diagram of a communication apparatus 1000 according to an embodiment of the present application.
  • the communication apparatus 1000 may correspond to (for example, be configured on or be itself) a target RAN device described in each of the foregoing method embodiments.
  • the communication device 1000 may include a receiving module 1001, a processing module 1002, and a sending module 1003.
  • the processing module 1002 is communicatively connected to the receiving module 1001 and the sending module 1003, respectively.
  • Each module or unit in the communication device 1000 is configured to perform each action or processing procedure performed by the target RAN device in each of the foregoing method embodiments.
  • detailed description is omitted.
  • FIG. 11 shows a schematic block diagram of a communication device 1100 according to an embodiment of the present application.
  • the communication device 1100 may correspond to (for example, be configured on or be itself) the CN device described in the foregoing method embodiments.
  • the communication device 1100 may include a processor 1101 and a transceiver 1102, and the processor and the transceiver are communicatively connected.
  • the communication device 1100 further includes a memory 1103, and the memory 1103 is communicatively connected to the processor 1101.
  • the processor 1101, the memory 1103, and the transceiver 1102 may be communicatively connected.
  • the memory 1103 may be used to store instructions, and the processor 1101 is configured to execute the instructions stored in the memory to control the transceiver 702 to send information or signals.
  • the processor 701 and the transceiver 702 are respectively configured to perform various actions or processing processes performed by the CN in the foregoing method embodiments. Here, in order to avoid redundant description, detailed description is omitted.
  • FIG. 12 shows a schematic block diagram of a communication device 1200 according to an embodiment of the present application.
  • the communication device 1200 may correspond to (for example, be configured on or be itself) the CN device described in the foregoing method embodiments.
  • the communication device 1200 may include a receiving module 1201, a processing module 1202, and a sending module 1203.
  • the processing module 1202 is communicatively connected to the receiving module 1201 and the sending module 1203, respectively.
  • Each module or unit in the communication device 1200 is configured to perform each action or processing performed by the CN device in each of the foregoing method embodiments.
  • detailed description is omitted.
  • the processor (701, 901, 1101) in the device embodiment of the present application may be a central processing unit (Central Processing Unit), a network processor (Network Processor, NP), a hardware chip, or any combination.
  • the above-mentioned hardware chip may be an Application-Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof.
  • the above PLD can be a complex programmable logic device (Complex Programmable Logic Device (CPLD), field-programmable gate array (FPGA), general array logic (Generic Array logic, GAL) or any combination.
  • the memory (703, 903, 1103) in the device embodiment of the present application may be volatile memory (Volatile Memory), such as Random-Access Memory (Random-Access Memory, RAM for short); or non-volatile memory ( Non-Volatile Memory, such as Read-Only Memory (ROM), Flash Memory, Hard Disk Drive (HDD) or Solid-State Drive (SSD); It may also be a combination of the above-mentioned types of memories.
  • volatile memory such as Random-Access Memory (Random-Access Memory, RAM for short
  • Non-Volatile Memory such as Read-Only Memory (ROM), Flash Memory, Hard Disk Drive (HDD) or Solid-State Drive (SSD)
  • ROM Read-Only Memory
  • HDD Hard Disk Drive
  • SSD Solid-State Drive
  • the disclosed apparatus and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of units is only a logical function division.
  • multiple units or components may be combined or integrated.
  • To another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this patent application essentially or part that contributes to the existing technology or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, Contains several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method of each embodiment of this patent application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random access Memory), a magnetic disk or an optical disk, and various program codes that can be stored The medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de transfert intercellulaire. Le procédé comprend les étapes suivantes : un dispositif de réseau d'accès radio (RAN) source envoie une demande de transfert intercellulaire à un dispositif RAN cible, la demande de transfert intercellulaire comprenant des informations de longueur d'un identifiant de flux de service (QFI) attribué à un dispositif terminal par le dispositif RAN source ; le dispositif RAN cible effectue une commande d'admission ; le dispositif RAN cible envoie un accusé de réception de demande de transfert intercellulaire au dispositif RAN source, l'accusé de réception de demande de transfert intercellulaire comprenant des informations de longueur d'un QFI attribué au dispositif terminal par le dispositif RAN cible ; le dispositif RAN source envoie une commande de transfert intercellulaire au dispositif terminal, la commande de transfert intercellulaire comprenant des informations de longueur d'un QFI attribué au dispositif terminal par le dispositif RAN cible ; le dispositif RAN source transfère des données au dispositif RAN cible ; le dispositif RAN cible accorde l'accès au dispositif terminal ; le dispositif RAN cible envoie une demande de transfert de chemin à un dispositif de réseau central (CN) et reçoit un accusé de réception de transfert de chemin ; et le dispositif RAN cible envoie une instruction de libération de contexte de dispositif terminal au dispositif RAN source.
PCT/CN2019/092328 2018-06-22 2019-06-21 Procédé et dispositif de transfert intercellulaire WO2019242749A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP19823238.1A EP3790319B1 (fr) 2018-06-22 2019-06-21 Procédé et dispositif de transfert intercellulaire
EP23183440.9A EP4243486A3 (fr) 2018-06-22 2019-06-21 Procédé et dispositif de transfert intercellulaire
AU2019290751A AU2019290751B2 (en) 2018-06-22 2019-06-21 Handover method and apparatus
US17/111,200 US11457392B2 (en) 2018-06-22 2020-12-03 Handover method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810654981.X 2018-06-22
CN201810654981.XA CN110636580B (zh) 2018-06-22 2018-06-22 一种切换方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/111,200 Continuation US11457392B2 (en) 2018-06-22 2020-12-03 Handover method and apparatus

Publications (1)

Publication Number Publication Date
WO2019242749A1 true WO2019242749A1 (fr) 2019-12-26

Family

ID=68967166

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/092328 WO2019242749A1 (fr) 2018-06-22 2019-06-21 Procédé et dispositif de transfert intercellulaire

Country Status (5)

Country Link
US (1) US11457392B2 (fr)
EP (2) EP4243486A3 (fr)
CN (3) CN110636580B (fr)
AU (1) AU2019290751B2 (fr)
WO (1) WO2019242749A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021109474A1 (fr) * 2020-05-19 2021-06-10 Zte Corporation Procédés et systèmes pour le transfert de données de multidiffusion pendant les procédures de mobilité dans les réseaux de communication sans fil
WO2021198879A1 (fr) * 2020-04-02 2021-10-07 Nokia Solutions And Networks Oy Adaptation du fonctionnement d'un appareil

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3711347B1 (fr) * 2017-11-17 2022-07-20 Telefonaktiebolaget LM Ericsson (publ) Commande de notification sur des interfaces de ran
WO2020096396A1 (fr) * 2018-11-09 2020-05-14 Lg Electronics Inc. Prise en charge d'un transfert inter-gnb dans une connectivité multiple de couche supérieure
TWI758046B (zh) * 2020-01-06 2022-03-11 聯發科技股份有限公司 處理多重進接協定資料單元會話切換之方法及其使用者設備
CN114071578A (zh) * 2020-07-30 2022-02-18 维沃移动通信有限公司 数据传输方法、装置、核心网设备及接入网侧设备
CN114079870B (zh) * 2020-08-13 2023-06-02 华为技术有限公司 通信方法及装置
CN115175255A (zh) * 2021-04-01 2022-10-11 华为技术有限公司 一种多播广播业务的传输切换方法及装置
CN113692006B (zh) * 2021-08-24 2022-05-13 北京云智软通信息技术有限公司 通信管理方法、接入网单元及通信系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107548127A (zh) * 2016-06-23 2018-01-05 北京三星通信技术研究有限公司 支持数据传输的方法和设备
WO2018110952A2 (fr) * 2016-12-12 2018-06-21 Samsung Electronics Co., Ltd. Appareil et procédé de commande de flux de données dans un système de communication sans fil

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101473679B (zh) * 2006-06-16 2012-11-14 诺基亚公司 在系统间切换的情况下用于为终端传送pdp上下文信息的设备和方法
CN104363598B (zh) 2014-11-25 2018-03-23 电信科学技术研究院 一种drb映射方法及装置
US11026133B2 (en) * 2015-04-24 2021-06-01 Nokia Solutions And Networks Oy Flexible quality of service for inter-base station handovers within wireless network
EP3852431B1 (fr) * 2016-08-01 2022-07-13 Samsung Electronics Co., Ltd. Procédés et appareils de gestion de la communication de données dans un réseau de communication sans fil
CN108024294B (zh) * 2016-11-02 2020-08-07 中兴通讯股份有限公司 切换方法及装置
WO2018130968A1 (fr) * 2017-01-11 2018-07-19 Telefonaktiebolaget Lm Ericsson (Publ) Flux de qos 5g vers un remappage de support radio
WO2018144855A1 (fr) * 2017-02-03 2018-08-09 Intel IP Corporation Bit de priorié de mise en correspondance de flux de qualité de service sur support radio de données
KR102265907B1 (ko) * 2017-03-22 2021-06-16 엘지전자 주식회사 무선 통신 시스템에서 서비스 품질 (QoS) 구조 기반으로 상향링크 패킷을 전송하는 방법 및 이를 위한 장치
CN107018542A (zh) 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质
CN109151915B (zh) * 2017-06-16 2023-11-17 夏普株式会社 用于数据分组递送的方法、用户设备和基站
EP3435700B1 (fr) * 2017-07-24 2020-09-16 ASUSTek Computer Inc. Procédé et appareil permettant de fournir une qualité de service (qos) d'écoulement dans un système de communication sans fil
CN107302777A (zh) * 2017-08-28 2017-10-27 北京北方烽火科技有限公司 一种通信切换方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107548127A (zh) * 2016-06-23 2018-01-05 北京三星通信技术研究有限公司 支持数据传输的方法和设备
WO2018110952A2 (fr) * 2016-12-12 2018-06-21 Samsung Electronics Co., Ltd. Appareil et procédé de commande de flux de données dans un système de communication sans fil

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CMCC: "Short QFI in SDAP header", 3GPP TSG-RAN WG2 MEETING #101 BIS R2-1805525, vol. RAN WG2, 6 April 2018 (2018-04-06), pages 1 - 3, XP051415996 *
HUAWEI ET AL: "DL and UL QoS Flow to DRB mapping", 3GPP TSG-RAN WG2 MEETING#AH-1807, R2-1809974, vol. RAN WG2, 22 June 2018 (2018-06-22), Montreal, Canada, pages 1 - 3, XP051525796 *
HUAWEI ET AL: "Further discussion on information for handover", 3GPP TSG-RAN WG2#101 , R2-1802468, vol. RAN WG2, 16 February 2018 (2018-02-16), Athens, Greece, pages 1 - 5, XP051400146 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021198879A1 (fr) * 2020-04-02 2021-10-07 Nokia Solutions And Networks Oy Adaptation du fonctionnement d'un appareil
WO2021109474A1 (fr) * 2020-05-19 2021-06-10 Zte Corporation Procédés et systèmes pour le transfert de données de multidiffusion pendant les procédures de mobilité dans les réseaux de communication sans fil

Also Published As

Publication number Publication date
US11457392B2 (en) 2022-09-27
EP3790319A1 (fr) 2021-03-10
EP3790319B1 (fr) 2023-08-02
AU2019290751A1 (en) 2020-12-24
CN117858180A (zh) 2024-04-09
CN110636580A (zh) 2019-12-31
CN110636575B (zh) 2020-11-24
US20210092661A1 (en) 2021-03-25
EP4243486A3 (fr) 2023-11-08
EP3790319A4 (fr) 2021-07-14
CN110636575A (zh) 2019-12-31
EP4243486A2 (fr) 2023-09-13
AU2019290751B2 (en) 2022-06-02
CN110636580B (zh) 2024-01-26

Similar Documents

Publication Publication Date Title
WO2019242749A1 (fr) Procédé et dispositif de transfert intercellulaire
CN110999520B (zh) 无线接入网节点、核心网节点和无线终端及其方法
US11647557B2 (en) Radio access network node, radio terminal, and methods therefor
CN110383895B (zh) 在切换过程期间获取按需系统信息的方法
EP3614736B1 (fr) Procédé et appareil de gestion de transferts
EP3624530A1 (fr) Procédé de traitement d'informations et appareil associé
WO2019242714A1 (fr) Procédé et appareil de transmission de données
WO2019029643A1 (fr) Procédé de communication, station de base, dispositif terminal et système
TW202021411A (zh) 無效協定資料單元會話之處理方法及其使用者設備
WO2020063438A1 (fr) Procédé pour la coordination d'une transmission répétée
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2022001738A1 (fr) Procédé de traitement d'informatique à la frontière mobile, et dispositif associé
US20190104439A1 (en) Data transmission method, apparatus, and system
CN112470544A (zh) 终端装置、基站装置以及方法
WO2019096117A1 (fr) Procédé et dispositif d'envoi de message, procédé et dispositif d'envoi de politique, support de stockage, et processeur
CN112913322A (zh) 终端装置、基站装置以及方法
WO2020164614A1 (fr) Informations d'assistance ainsi que procédé et appareil pour les distribuer
WO2023246746A1 (fr) Procédé de communication et dispositif associé
WO2022027653A1 (fr) Procédé de transmission d'informations, appareil de communication et support de stockage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19823238

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019823238

Country of ref document: EP

Effective date: 20201202

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019290751

Country of ref document: AU

Date of ref document: 20190621

Kind code of ref document: A