WO2018127243A1 - 网络实体切换的方法、终端及网络实体设备 - Google Patents

网络实体切换的方法、终端及网络实体设备 Download PDF

Info

Publication number
WO2018127243A1
WO2018127243A1 PCT/CN2018/076497 CN2018076497W WO2018127243A1 WO 2018127243 A1 WO2018127243 A1 WO 2018127243A1 CN 2018076497 W CN2018076497 W CN 2018076497W WO 2018127243 A1 WO2018127243 A1 WO 2018127243A1
Authority
WO
WIPO (PCT)
Prior art keywords
network entity
new
terminal
data packet
configuration parameter
Prior art date
Application number
PCT/CN2018/076497
Other languages
English (en)
French (fr)
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 US16/476,056 priority Critical patent/US20190335369A1/en
Publication of WO2018127243A1 publication Critical patent/WO2018127243A1/zh

Links

Images

Classifications

    • 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
    • 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
    • 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/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method, a terminal, and a network entity device for network entity handover.
  • the network will trigger a mobility event, as shown in FIG. 1 , which is an ordinary dual-connected mobile scenario.
  • the UE and the first eNB and the second eNB both maintain a wireless connection.
  • Figure 2 shows the traditional switching process, including:
  • the source eNB sends measurement control to the terminal, the terminal transmits the data packet with the source eNB, the data packet is transmitted between the source eNB and the serving gateway, and the source eNB performs uplink configuration for the terminal.
  • the terminal sends a measurement report to the source eNB
  • the source eNB decides to switch
  • the source eNB sends a handover request to the target eNB
  • the target eNB agrees to handover and accepts the handover request
  • the target eNB feeds back a handover request response to the source eNB, and performs downlink configuration by the source eNB to the terminal;
  • the source eNB sends an RRC (Radio Resource Control) configuration, a reconfiguration, and the like to the terminal, and after receiving the configuration information, the terminal leaves the original cell and synchronizes to the new cell.
  • RRC Radio Resource Control
  • the source eNB transmits the data packet to the target eNB, and transmits the sequence number status of the data packet to the target eNB, and transmits the data to the target eNB, and the data packet is buffered by the target eNB;
  • the terminal synchronizes with the target eNB
  • the target eNB sends an uplink configuration to the terminal
  • the terminal After the terminal sends the RRC configuration and reconfiguration to the target eNB, and completes, the data packet is transmitted by the target eNB, and the data packet is transmitted by the target eNB to the serving gateway.
  • the target eNB sends a path switch request to the MME
  • the MME After receiving the path conversion request, the MME sends a modify bearer request to the serving gateway.
  • the serving gateway After the serving gateway converts the downlink path, the serving gateway sends an end Marker to the source eNB, and after receiving the feedback from the source eNB, the serving gateway performs data packet transmission with the target ENB.
  • the serving gateway sends a modify bearer response to the MME
  • the MME sends a path switch response to the target eNB
  • the target eNB sends a release context message to the source eNB;
  • the source eNB releases the corresponding resource.
  • the above process uses the data transmission between the terminal and the original eNB to be interrupted, and the service is continued after accessing the target eNB, thus causing a large data interruption.
  • the source eNB sends a request to the target eNB to allow the target eNB to join the source network (the configuration information carrying the serving gateway);
  • the target eNB and the source eNB send a response to join the source side network (the configuration information carrying the service gateway);
  • the source eNB sends an RRC connection reconfiguration message to the UE;
  • the UE sends an RRC connection reconfiguration complete message to the source eNB;
  • the source eNB sends a configuration complete message to the target eNB
  • the target eNB performs a random access procedure with the UE.
  • the signaling anchor does not change, and belongs to the mobility event on the RAN (Radio Access Network) side, and the data is not interrupted.
  • a multi-connected UE can simultaneously connect two or more network entities (each network entity includes at least one independent MAC entity);
  • signal bearer and/or data bearer PDCP Packet Data Convergence Protocol
  • functional entity including logical entities including security/compression/sorting functions
  • core network The termination point for the connection and/or data connection
  • One or more slave network entities (the PDCP functional entity without signaling bearer and the termination point of the core network signaling connection, mainly participating in data transmission, having at least RLC (Radio Link Layer Control Protocol) and MAC for each bearer And functional entities such as the physical layer (segmentation/serialization/multiplexing/scheduling/encoding/modulation, etc.).
  • the UE after the occurrence of the mobility event shown in FIG. 1 above will be in a multi-connection state.
  • the UE may not cause a service interruption in the mobility event, but for the multi-connection UE, the anchor point does not remain unchanged, which may bring many disadvantages to the system.
  • the performance of the entire system is degraded.
  • inter-node mobility events under the traditional network architecture cannot meet the higher demands for mobile performance. For example, keeping data interruptions minimal (even 0ms) during handover has become a basic requirement for next-generation network development.
  • the embodiments of the present disclosure provide a method for switching a network entity, a terminal, and a network entity device, which can ensure seamless transfer of service data, thereby improving adverse effects on the system.
  • an embodiment of the present disclosure provides the following technical solutions:
  • a method for switching a network entity includes:
  • a new configuration parameter of the second network entity that is connected to the terminal is that the second network entity is configured according to the first network entity Transmitted, configured to change the anchor point from the first network entity to the indication information of the anchor point change operation of the second network entity;
  • the method further includes:
  • the second network entity converts the path from the first network entity to the second network entity according to the anchor point change confirmation message, performs data transmission with the second network entity.
  • the step of performing data transmission with the second network entity includes:
  • the received new data packet from the second network entity is processed by the first configuration sublayer.
  • the step of sending the new data packet sent to the second network entity to the second network entity by using the first configuration sublayer includes:
  • the data packet header carries: the data packet includes indication information that is sent to the second network entity.
  • the step of processing the received new data packet from the second network entity by using the first configuration sublayer includes:
  • the data packets After the data packets are sequentially decrypted, reordered, and decompressed, they are sent to the in-order transmission and repeated detection function entities for processing.
  • the step of being sent to the in-order transmission and the repeated detection function entity for processing includes:
  • Decrypting the data packet sending it to the reordering entity, and forwarding the sequenced new data packet to the decompressing entity of the first configuration sublayer for decompression operation according to the header information, and then sending the sequence to the reordering operation Transmit and repeat detection functional entities for processing; or
  • the data packet is decrypted, sent to the reordering entity and the decompressed entity for corresponding processing, and then sent to the in-order transmission and repeated detection function entities for processing.
  • the new data packet comprises: a new signaling data packet and/or a new service data packet.
  • the second network entity after converting the path from the first network entity to the second network entity, according to the anchor change confirmation message, further includes:
  • the step of transmitting the service data packet with the first network entity includes:
  • the step of transmitting the service data packet sent to the first network entity to the bottom layer by using the second configuration sublayer, and sending the data packet to the first network entity includes:
  • the service data packet sent to the first network entity is sequentially compressed and encrypted, the service data packet is sent to the first network entity through the bottom layer according to the routing information.
  • the step of transmitting the received service data packet from the first network entity to the second configuration sublayer through the bottom layer for processing includes:
  • the service data packets received from the first network entity through the bottom layer are sequentially decrypted, reordered, and decompressed, and then sent to the sequential transmission and repeated detection function entities for processing.
  • the switching method further includes:
  • the second configuration sub-layer release operation is triggered.
  • the triggering conditions that the new configuration parameter takes effect include:
  • the terminal When the terminal receives the new configuration parameter, it immediately takes effect, and sends a triggering information to notify the second network entity, so that the second network entity performs an effective triggering operation on the new configuration parameter; or
  • the terminal When the terminal receives the indication information sent by the second network entity through the bottom layer, the terminal performs an effective triggering operation on the new configuration parameter, and when the second network entity sends the indication information, the The new configuration parameters are validated to trigger the operation; or
  • the terminal After receiving the new configuration parameter, the terminal triggers the effective operation of the new configuration parameter at a preset time point, and the second network entity takes effect on the new configuration parameter at the preset time point. Trigger action.
  • the trigger information carries a sequence number of a new data packet sent to the second network entity
  • the indication information carries a sequence number of a new data packet sent by the second network entity to the UE.
  • An embodiment of the present disclosure further provides a method for switching a network entity, including:
  • the new configuration parameter is used to enable the terminal to perform a new configuration according to the configuration parameter, and after the new configuration is completed,
  • the anchor is switched to the second network entity.
  • the second network entity is the first network entity according to the radio channel condition of the terminal, the load status of the network entity, the path delay between the terminal and the network entity, and/or the radio resource management.
  • a policy a network entity selected among a plurality of network entities that are connected to the terminal.
  • the indication information at least includes: based on the new configuration information of the second network entity, the new configuration information includes: security context information based on the second network entity.
  • the indication information further includes: an effective time point of the new configuration information, a wireless configuration parameter based on a signaling bearer of the first network entity, and/or a data bearer based on the first network entity.
  • Packet Data Convergence Protocol PDCP Configuration Parameters Packet Data Convergence Protocol PDCP Configuration Parameters.
  • the new configuration parameter includes: a new encryption algorithm based on the second network entity, a radio configuration parameter of the signaling bearer, a packet data convergence protocol PDCP parameter of the data bearer, and/or an update data bearer from the first A wireless parameter of the underlying transmission used by a network entity to the second network entity.
  • the step of the first network entity sending the new configuration parameter to the terminal includes:
  • the first network entity sends the new configuration parameter to the terminal by using a radio resource control RRC message.
  • the switching method further includes:
  • the first network entity When the first network entity receives the sequence number of the new data packet notified by the second network entity, determining that the service data packet sent by the first network entity before the sequence number to the terminal has been All the terminals are correctly received, and the service data packet sent by the terminal is correctly received, triggering the first network entity to release its configuration sublayer, and the connection relationship between the configuration sublayer and the bottom layer of the first network entity. .
  • An embodiment of the present disclosure further provides a method for switching a network entity, including:
  • the second network entity that is connected to the terminal receives the indication information that is sent by the first network entity that is connected to the terminal, and changes the anchor point from the first network entity to the anchor point change operation of the second network entity;
  • a new configuration parameter to the first network entity, and sending, by the first network entity, the new configuration parameter to the terminal, where the new configuration parameter is used to The terminal performs a new configuration according to the new configuration parameter, and after the new configuration is completed, switches the anchor point to the second network entity.
  • the switching method further includes:
  • the path is converted by the first network entity to the second network entity according to the anchor point change confirmation message or according to a new configuration parameter that is in effect.
  • the step of converting the path from the first network entity to the second network entity according to the anchor point change confirmation message or according to the new configuration parameter that is in effect includes:
  • the switching method further includes:
  • the step of performing data transmission with the terminal includes:
  • the received new data packet from the terminal is processed through the configuration sublayer.
  • the step of sending the new data packet sent to the terminal to the terminal by using the configuration sublayer of the second network entity includes:
  • a new sequence number is added to the packet header of the data packet sent to the terminal, and compression, encryption, and data packet header processing are sequentially performed to obtain a new data packet, which is sent to the terminal through the bottom layer according to the routing information.
  • the data packet header includes: the data packet includes indication information of new data sent to the terminal.
  • the step of processing the received new data packet from the terminal by using the configuration sublayer includes:
  • the data packets After the data packets are sequentially decrypted, reordered, and decompressed, they are sent to the in-order transmission and repeated detection function entities for processing.
  • the new data packet comprises: a new signaling data packet and/or a new service data packet.
  • the triggering conditions of the new configuration parameter are:
  • the triggering action is performed on the new configuration parameter, where the trigger message is trigger information sent by the terminal immediately after receiving the new configuration parameter;
  • the triggering action is performed on the new configuration parameter, where the indication information is used to enable the terminal to trigger the new configuration parameter;
  • the effective operation of the new configuration parameter is triggered at a preset time point, and the terminal performs an effective triggering operation on the new configuration parameter at the preset time point.
  • the second network entity does not perform reset/reestablishment of the underlying transmission.
  • An embodiment of the present disclosure further provides a terminal, including:
  • a receiver configured to perform a function of: receiving, by a first network entity that is connected to the terminal, a new configuration parameter of a second network entity that is connected to the terminal, the new configuration parameter is
  • the second network entity is configured according to the indication information that is sent by the first network entity to change the anchor point from the first network entity to the anchor point change operation of the second network entity;
  • the transmitter is configured to perform a function of not performing reset/reestablishment of the underlying transmission when the new configuration parameter is in effect, and transmitting an anchor change confirmation message to the second network entity.
  • An embodiment of the present disclosure further provides a network entity device, including:
  • a transmitter configured to perform a function of: transmitting, to the second network entity that is connected to the terminal, an indication that the anchor point is changed from the first network entity to an anchor point change operation of the second network entity;
  • a receiver configured to perform a function of: receiving a new configuration parameter returned by the second network entity according to the indication information;
  • the transmitter is further configured to send the new configuration parameter to the terminal, where the new configuration parameter is used to enable the terminal to perform a new configuration according to the configuration parameter, and after the new configuration is completed, The anchor point is switched to the second network entity.
  • An embodiment of the present disclosure further provides a network entity device, including:
  • a receiver configured to perform: a function for receiving, by a first network entity that is connected to the terminal, an indication that the anchor point is changed from the first network entity to an anchor point change operation of the second network entity;
  • a transmitter configured to perform a function of: returning, to the first network entity, a new configuration parameter according to the indication information, and transmitting, by the first network entity, the new configuration parameter to the The terminal, the new configuration parameter is used to enable the terminal to perform a new configuration according to the new configuration parameter, and after the new configuration is completed, switch the anchor point to the second network entity.
  • the primary network entity may select a certain one of the secondary network entities (the second network entity) as the new anchor point, triggering the anchor point (referring to the primary network) Entity) changes operations; ensures seamless transfer of business data.
  • FIG. 1 is a schematic diagram of a network scenario in which a terminal is connected in multiples in the related art
  • FIG. 2 is a schematic flowchart of a path switching between terminals in different network entities in the related art
  • FIG. 3 is a schematic diagram showing another process of path switching between terminals in different network entities in the related art
  • FIG. 4 is a schematic flowchart diagram of a method for switching a network entity performed by a terminal side according to some embodiments of the present disclosure
  • FIG. 5 is a schematic diagram showing a process of processing downlink data by a PDCP entity on a terminal side according to some embodiments of the present disclosure
  • FIG. 6 is a schematic diagram showing a process of processing uplink data by a PDCP entity on a terminal side according to some embodiments of the present disclosure
  • FIG. 7 is a schematic flowchart diagram of a method for switching a network entity on a first network entity side according to some embodiments of the present disclosure
  • FIG. 8 is a schematic flowchart diagram of a method for switching a network entity on a second network entity side according to some embodiments of the present disclosure
  • FIG. 9 is a schematic flow chart showing an implementation example 1 of the present disclosure.
  • FIG. 10 is a flow chart showing the implementation example 2 of the present disclosure.
  • some embodiments of the present disclosure provide a method for switching a network entity, including:
  • Step 41 Receive, by the first network entity that is connected to the terminal, a new configuration parameter of the second network entity that is connected to the terminal, where the new configuration parameter is that the second network entity is configured according to the And configured by the network entity to change the anchor point from the first network entity to the indication information of the anchor point change operation of the second network entity;
  • Step 42 When the new configuration parameter is valid, no reset/reestablishment of the underlying transmission is performed, and an anchor change confirmation message is sent to the second network entity.
  • the triggering conditions for the new configuration parameters of the terminal to take effect include:
  • the terminal When the terminal receives the new configuration parameter, it takes effect immediately, and sends a triggering information to notify the second network entity, so that the second network entity performs an effective triggering operation on the new configuration parameter;
  • the trigger information carries a sequence number of a new data packet sent to the second network entity;
  • the terminal When the terminal receives the indication information sent by the second network entity through the bottom layer, the terminal performs an effective triggering operation on the new configuration parameter, and when the second network entity sends the indication information, The new configuration parameter performs an effective triggering operation; wherein the indication information carries a sequence number of a new data packet sent by the second network entity to the UE; or
  • the terminal After the new configuration parameter is received, the terminal triggers the effective operation of the new configuration parameter at a preset time point, and the second network entity pairs the new configuration parameter at the preset time point.
  • the trigger action is valid.
  • the primary network entity may select a certain one of the secondary network entities (the second network entity) as the new anchor point, triggering the anchor point (referring to the primary network entity) Change operations; ensure that business data is seamlessly transferred to improve the adverse impact on the system.
  • Some embodiments of the present disclosure provide a method for switching a network entity, including:
  • Step 41 Receive, by the first network entity that is connected to the terminal, a new configuration parameter of the second network entity that is connected to the terminal, where the new configuration parameter is that the second network entity is configured according to the And configured by the network entity to change the anchor point from the first network entity to the indication information of the anchor point change operation of the second network entity;
  • Step 42 When the new configuration parameter is valid, no reset/reestablishment of the underlay transmission is performed, and an anchor change confirmation message is sent to the second network entity.
  • Step 43 After the second network entity converts the path from the first network entity to the second network entity according to the anchor point change confirmation message, perform data transmission with the second network entity.
  • the step of performing data transmission with the second network entity includes:
  • Step 431 In the uplink direction, send a new data packet sent to the second network entity to the second network entity by using a first configuration sublayer; or
  • Step 432 The downlink packet receives the received new data packet from the second network entity through the first configuration sublayer.
  • the first configuration sub-layer may be a PDCP (Packet Data Convergence Protocol) configuration sub-layer, and the foregoing step 431 may specifically include:
  • PDCP Packet Data Convergence Protocol
  • Step 4311 Add a new sequence number to the packet header of the data packet sent to the second network entity, and sequentially compress, encrypt, and add data packet header processing to obtain a new data packet.
  • Step 4312 Send the new data packet to the second network entity by using an underlay according to the routing information.
  • the data packet header carries: the data packet includes indication information of new data sent to the second network entity.
  • the new data packet includes: a new signaling data packet and/or a new service data packet.
  • the UE does not perform the layer 2/physical layer reconstruction and reset operations for each DRB (data resource block) and/or SRB (signal resource block).
  • DRB data resource block
  • SRB signal resource block
  • the two sets of PDCP sub-configurations as a whole remain connected to the original 2 or more layer 2/physical layers.
  • RLC/MAC/PHY Physical Layer
  • the new PDCP SDU is assigned a new SN (Sequence Number) and will be delivered to the new configuration sublayer.
  • PDU Protocol Data Unit
  • the above step 432 may specifically include:
  • Step 4321 Perform a de-packet operation on the received new data packet from the second network entity, to obtain a processed data packet.
  • Step 4322 after the data packet is sequentially decrypted, reordered, and decompressed, and then sent to the sequential transmission and the repeated detection function entity for processing; specifically,
  • the decompressing entity of the sublayer performs a decompression operation, and finally sends the function to the in-order transmission and the repetitive detection function (shares the same reordering entity with the second configuration sublayer) for processing; or
  • the new data packet includes: a new signaling data packet and/or a new service data packet.
  • the UE does not perform the layer 2/physical layer reconstruction and reset operations for each DRB (data resource block) and/or SRB (signal resource block).
  • DRB data resource block
  • SRB signal resource block
  • the two sets of PDCP sub-configurations as a whole remain connected to the original 2 or more layer 2/physical layers.
  • any RLC (Radio Link Control) PDCP PDU Packet Data Unit
  • the de-heading operation is performed. If the PDU header contains a new data indication, the PDU is delivered to the new configuration sublayer, and sequentially Decrypt, reorder, decompress, and then submit to the in-order transfer and repeat detection functions;
  • the PDU header does not contain a new data indication
  • the PDU is submitted to the old configuration sublayer, and similar operations are performed in sequence, and finally, the in-order transmission and the repeated detection function are also submitted.
  • the triggering conditions for the new configuration parameters of the terminal to take effect include:
  • the terminal When the terminal receives the new configuration parameter, it takes effect immediately, and sends a triggering information to notify the second network entity, so that the second network entity performs an effective triggering operation on the new configuration parameter;
  • the trigger information carries a sequence number of a new data packet sent to the second network entity;
  • the terminal When the terminal receives the indication information sent by the second network entity through the bottom layer, the terminal performs an effective triggering operation on the new configuration parameter, and when the second network entity sends the indication information, The new configuration parameter performs an effective triggering operation; wherein the indication information carries a sequence number of a new data packet sent by the second network entity to the UE; or
  • the terminal After the new configuration parameter is received, the terminal triggers the effective operation of the new configuration parameter at a preset time point, and the second network entity pairs the new configuration parameter at the preset time point.
  • the trigger action is valid.
  • the primary network entity may select one of the secondary network entities (second network entity) as a new anchor point, triggering an anchor point (referring to the primary network entity)
  • the operation is changed; and the second network entity that further implements the new anchor performs signaling transmission and/or data transmission with the terminal, thereby ensuring seamless transfer of service data, thereby improving the adverse impact on the system.
  • Some embodiments of the present disclosure provide a method for switching a network entity, including:
  • Step 41 Receive, by the first network entity that is connected to the terminal, a new configuration parameter of the second network entity that is connected to the terminal, where the new configuration parameter is that the second network entity is configured according to the And configured by the network entity to change the anchor point from the first network entity to the indication information of the anchor point change operation of the second network entity;
  • Step 42 When the new configuration parameter is valid, no reset/reestablishment of the underlay transmission is performed, and an anchor change confirmation message is sent to the second network entity.
  • Step 43 After the second network entity converts the path from the first network entity to the second network entity according to the anchor point change confirmation message, perform service data packet with the first network entity. transmission.
  • step 43 the step of transmitting the service data packet with the first network entity includes:
  • the service data packet sent to the first network entity is transmitted to the bottom layer through the second configuration sublayer, and sent to the first network entity;
  • the received service data packet from the first network entity is transmitted to the second configuration sublayer through the bottom layer for processing.
  • the second configuration sublayer may be a PDCP (Packet Data Convergence Protocol) configuration sublayer.
  • PDCP Packet Data Convergence Protocol
  • the specific processing flow in the uplink direction includes:
  • the service data packet sent to the first network entity is sequentially compressed and encrypted, the service data packet is sent to the first network entity through the bottom layer according to the routing information.
  • the specific processing flow in the downlink direction includes:
  • the service data packets received from the first network entity through the bottom layer are sequentially decrypted, reordered, and decompressed, and then sent to the sequential transmission and repeated detection function entities for processing.
  • the terminal When the terminal receives the new configuration parameter, it takes effect immediately, and sends a triggering information to notify the second network entity, so that the second network entity performs an effective triggering operation on the new configuration parameter;
  • the trigger information carries a sequence number of a new data packet sent to the second network entity;
  • the terminal When the terminal receives the indication information sent by the second network entity through the bottom layer, the terminal performs an effective triggering operation on the new configuration parameter, and when the second network entity sends the indication information, The new configuration parameter performs an effective triggering operation; wherein the indication information carries a sequence number of a new data packet sent by the second network entity to the UE; or
  • the terminal After the new configuration parameter is received, the terminal triggers the effective operation of the new configuration parameter at a preset time point, and the second network entity pairs the new configuration parameter at the preset time point.
  • the trigger action is valid.
  • the first network entity acts as a new slave network entity, and the terminal can perform transmission of the service data packet.
  • the terminal if the terminal has received correctly, the data packet from the first network entity before the sequence number of the data packet of the second network entity is received by the first network entity. After the acknowledgment message of the uplink data packet sent by all the terminals before the sequence number, the second configuration sub-layer release operation is triggered. Thereby, the processing load of the terminal can be reduced.
  • the primary network entity may select one of the secondary network entities (second network entity) as a new anchor point, triggering an anchor point (referring to the primary network entity) And changing the operation; further implementing the signaling and/or data service transmission by the second network entity and the terminal of the new anchor point, and further implementing the first network entity of the original anchor point as the slave network entity, implementing the terminal and the first
  • the data service transmission of the network entity can ensure the seamless transfer of business data, thereby improving the adverse impact on the system.
  • the network side selects a certain slave network entity as the new primary network according to the radio channel condition, load status, path delay, or other RRM (Radio Resource Management) policy of the UE.
  • Entity triggering an anchor (referring to the primary network entity) to change operations; ensuring that business data is seamlessly transferred, thereby improving the adverse impact on the system.
  • All bearer PDCP entities are transferred from the primary network entity (the first network entity) to the target secondary network entity (the second network entity) and perform the reconstruction operation;
  • the signaling termination point of the terminal to the core network is the primary network entity
  • the signalling termination point of the terminal to the core network is the target slave network entity.
  • the target becomes a new anchor (primary network entity) from the network entity, while other network entities (including the original primary network entity) become new slave entities.
  • the network side reconfigures the signaling bearer and/or the PDCP related parameters of the data bearer at the target anchor point or may update other functional entity parameters, etc., and sends these parameters to the UE through the RRC message of the primary network entity.
  • the configuration takes effect immediately.
  • an indication is sent through the physical layer or the MAC layer or the RLC layer.
  • the new configuration parameters of the network side take effect.
  • the configuration information of the network side can be only one piece of indication information, and the latest or last uplink PDCP sequence number can be carried to the UE.
  • the network side triggers the new configuration parameters of the network side to take effect. This includes establishing a new mapping relationship, generating a new downstream PDCP sequence number, and so on.
  • the network side sends the indication information to the UE through the physical layer or the MAC layer or the RLC layer to notify the UE that the configuration takes effect.
  • the information may be only one piece of indication information, or may carry the latest or last downlink PDCP sequence number to the UE.
  • the UE does not take effect immediately after receiving the new configuration parameter, and adopts a time point manner, that is, when a specified time point arrives, a new configuration parameter is triggered, and the network side also triggers a new configuration parameter at the specified time point.
  • the new PDCP serial number is determined by the uplink and downlink.
  • some embodiments of the present disclosure further provide a method for switching a network entity, including:
  • Step 71 The first network entity that is connected to the terminal sends, to the second network entity that is connected to the terminal, to change the anchor point from the first network entity to the indication information of the anchor point change operation of the second network entity.
  • Step 72 The first network entity receives a new configuration parameter that is returned by the second network entity according to the indication information.
  • Step 73 The first network entity sends the new configuration parameter to the terminal. Specifically, the first network entity sends the new configuration parameter to the terminal by using a radio resource control RRC message.
  • the new configuration parameter is used to enable the terminal to perform a new configuration according to the configuration parameter, and after the new configuration is completed, switch the anchor point to the second network entity.
  • the primary network entity may select one of the secondary network entities (second network entity) as a new anchor point, triggering an anchor point (referring to the primary network entity) Change operations; ensure seamless transfer of business data to improve the adverse impact on the system.
  • the second network entity is the first network entity according to the wireless channel condition of the terminal, the load status of the network entity, the path delay between the terminal and the network entity, and/or A radio resource management policy, one of a plurality of network entities selected to remain connected to the terminal.
  • the indication information at least includes: based on new configuration information of the second network entity, the new configuration information includes: security context information based on the second network entity.
  • the indication information further includes: an effective time point of the new configuration information, a wireless configuration parameter based on a signaling bearer of the first network entity, and/or a packet data aggregation based on a data bearer of the first network entity.
  • Protocol PDCP configuration parameters are included in The indication information.
  • the new configuration parameter includes: a new encryption algorithm based on the second network entity, a wireless configuration parameter of a signaling bearer, a packet data convergence protocol PDCP parameter of a data bearer, and/or an update data bearer from a first network entity to The wireless parameters of the underlying transmission used by the second network entity.
  • the method may further include:
  • the first network entity When the first network entity receives the sequence number of the new data packet notified by the second network entity, determining that the service data packet sent by the first network entity before the sequence number to the terminal has been All the terminals are correctly received, and the service data packet sent by the terminal is correctly received, triggering the first network entity to release its configuration sublayer, and the connection relationship between the configuration sublayer and the bottom layer of the first network entity. . Thereby reducing the processing load of the network entity.
  • an anchor change indication is initiated by the primary network entity (the first network entity) to the target secondary network entity (the second network entity), wherein at least the new security context information is included, or Old wireless configuration parameters, etc.
  • the target After the target receives the indication from the network entity, it selects a new encryption algorithm and configures the new wireless parameters.
  • the target then returns the corresponding configuration parameters from the network entity to the primary network entity, and the final RRC message is synthesized by the primary network entity and sent to the UE.
  • all network entities do not perform layer 2/physical layer reconstruction and reset operations.
  • all PDCP PDUs perform a de-head operation to determine whether it is new data and submit it to the correct target PDCP layer.
  • the RLC/MAC/PHY continues to maintain the original transmission activity; at the same time, a new mapping relationship is established with the new PDCP entity, and PDU data from the new PDCP entity is allowed to be processed.
  • some embodiments of the present disclosure provide a method for switching a network entity, including:
  • Step 81 The second network entity that is connected to the terminal receives the indication information that is sent by the first network entity that is connected to the terminal, and changes the anchor point from the first network entity to the anchor point change operation of the second network entity.
  • Step 82 Return, according to the indication information, a new configuration parameter to the first network entity, and send the new configuration parameter to the terminal by the first network entity, where the new configuration parameter is used. And causing the terminal to perform a new configuration according to the new configuration parameter, and after the new configuration is completed, switch the anchor point to the second network entity.
  • the primary network entity may select one of the secondary network entities (second network entity) as a new anchor point, triggering an anchor point (referring to the primary network entity) Changing the operation; and further configuring the new configuration parameter and sending it to the terminal, so that the terminal can further perform data transmission with the second network entity according to the new configuration parameter, thereby ensuring seamless transfer of service data, thereby improving the system.
  • the handover method further includes:
  • Step 83 The second network entity receives an anchor change confirmation message fed back by the terminal according to the new configuration parameter.
  • Step 84 Convert a path from the first network entity to the second network entity according to the anchor point change confirmation message or according to a new configuration parameter that is in effect;
  • the path change request message is sent to the session gateway controller (SGC) according to the anchor point change confirmation message or according to the valid new configuration parameter;
  • SGC session gateway controller
  • the switching method may further include:
  • Step 85 Perform data transmission with the terminal.
  • a new data packet sent to the terminal is sent to the terminal by using a configuration sublayer of the second network entity
  • a new sequence number is added to the packet header of the data packet sent to the terminal, and compression, encryption, and data packet header processing are sequentially performed to obtain a new data packet, which is sent to the a terminal; wherein the data packet header includes: the data packet includes indication information of new data sent to the terminal.
  • the received new data packet from the terminal is processed by the configuration sublayer;
  • the data packets After the data packets are sequentially decrypted, reordered, and decompressed, they are sent to the in-order transmission and repeated detection function entities for processing.
  • the new data packet includes: a new signaling data packet and/or a new service data packet.
  • the triggering conditions for the validation of the new configuration parameter of the second network entity include:
  • the triggering action is performed on the new configuration parameter, where the trigger message is trigger information sent by the terminal immediately after receiving the new configuration parameter;
  • the triggering action is performed on the new configuration parameter, where the indication information is used to enable the terminal to trigger the new configuration parameter;
  • the effective operation of the new configuration parameter is triggered at a preset time point, and the terminal performs an effective triggering operation on the new configuration parameter at the preset time point.
  • the second network entity After the new configuration parameter takes effect, the second network entity does not perform reset/reestablishment of the underlying transmission.
  • FIG. 9 is a schematic flow chart of an implementation example 1 of the present disclosure. As shown in FIG. 9, the UE maintains a wireless connection with two network entities, and the handover procedure includes steps 1 to 10.
  • Step 1 The original primary network entity (the first network entity) selects one of the secondary network entities (the second network entity) as the new primary network entity according to the wireless channel condition, load status, path delay or other RRM policy of the UE. Triggering an anchor (referring to the primary network entity) to change operations;
  • Step 2 The original primary network entity initiates an anchor change indication to the target slave network entity, where at least the new security context information (such as a new key Key eNodeB Star and Next Hop Chaining Count, etc.) or a new configuration time is included.
  • the effective point in addition, it may include all the wireless configuration parameters carried by the old signaling, or the PDCP configuration parameters of the old data bearer;
  • Step 3 After receiving the indication from the network entity, the target saves the new configuration parameters, selects a new encryption algorithm, configures all wireless parameters carried by the new signaling, and/or configures PDCP parameters of the new data bearer, or updates the data bearer. Wireless parameters such as RLC/MAC/PHY from the network entity part. The target then returns the corresponding configuration parameters from the network entity to the primary network entity;
  • Step 4 The final RRC message is synthesized by the original primary network entity and sent to the UE.
  • the parameter includes at least a new security context (such as security parameters required for the UE to generate a new security key and/or a newly selected encryption algorithm, etc.), and the network side may indicate the time effective point of the new configuration;
  • a new security context such as security parameters required for the UE to generate a new security key and/or a newly selected encryption algorithm, etc.
  • Step 5 When the specified time point arrives, the UE triggers the new configuration to take effect, and sends an anchor change confirmation message to the network side, and the network side also triggers the new configuration parameter to take effect at the specified time point;
  • Step 6 Once the new configuration takes effect, the UE does not perform Layer 2/physical layer reconstruction and reset operations, and there are two sets of PDCP sub-configurations for each DRB and/or SRB.
  • the two sets of PDCP sub-configurations as a whole remain connected to the original 2 or more layer 2/physical layers.
  • any PDCP PDU of any RLC is received, and a de-heading operation is performed. If the PDU header contains a new data indication, the PDU is delivered to the new configuration sublayer, decrypted, reordered, decompressed, and then Submit to in-order transfer and repeat detection functions;
  • the PDU header does not contain a new data indication
  • the PDU is delivered to the old configuration sublayer, and similar operations are performed in sequence, and finally, the in-order transmission and the repeated detection function are also submitted.
  • the new PDCP SDU will be assigned to the new configuration sublayer, and then compressed, encrypted, and added to the PDU header.
  • the header will contain new data indication, and then the data will be forwarded according to the routing information. Data transmission on the RLC/MAC/PHY connection.
  • Step 7 The target slave network entity, after receiving the RRC reconfiguration complete message from the UE (ie, the anchor change confirmation message), or after the new configuration takes effect, performs a path conversion operation, and the specific operation is after the traditional X2 switchover.
  • the path conversion operation is similar.
  • Step 8 Once the new configuration takes effect, all network entities do not perform an L2 reset operation.
  • the RLC/MAC/PHY continues to maintain the original transmission activity; at the same time, the new PDCP entity establishes a new mapping relationship with the RLC/MAC/PHY, and the generated new PDCP PDU is Submitted to the underlying layer (RLC) for new data transmission activities, where each new PDU header carries an indication of a new data packet.
  • RLC underlying layer
  • any PDCP PDU received (such as a local RLC or a new slave network PDU) is de-headed. If the PDU header contains a new data indication, the PDU is delivered to the new PDCP entity. , decrypting, reordering, decompressing, and then submitting to the local in-order transmission and repeat detection functions;
  • the PDU header does not contain a new data indication
  • the PDU is transmitted to the PDCP layer of the old primary network entity through the interface, and similar operations are performed in sequence, and finally the local sequential transmission and repeated detection functions are submitted.
  • the RLC/MAC/PHY continues to maintain the original transmission activity; at the same time, it establishes a new mapping relationship with the PDCP layer of the new primary network entity and allows receiving PDCP PDUs from the new primary network entity. .
  • any PDCP PDU from the local RLC needs to be de-headed. If the PDU header does not contain a new data indication, the PDU is submitted to the local old PDCP entity, decrypted, reordered, decompressed, and then submitted. Local in-sequence transfer and repeat detection. If the PDU header contains a new data indication, the PDU is delivered to the new PDCP entity through the interface, and similar operations are performed in sequence, and finally the local sequential transmission and repeated detection functions are submitted.
  • Step 9 On the UE side, the PDCP entity determines that the downlink PDUs before all the new data sequence numbers have been correctly received. At the same time, it is determined that all the uplink PDUs have been acknowledged before the new data sequence number, and the old PDCP configuration sublayer release operation is triggered.
  • Step 10 Similarly, on the network side, in the downlink direction, the new PDCP entity needs to notify the old PDCP entity of the starting value of the new data sequence number of the downlink PDU, and the old PDCP entity is responsible for determining whether all the old downlink PDUs have been
  • the new PDCP entity after receiving the new uplink PDU, the new PDCP entity notifies the old PDCP entity of the new data sequence number start value, and the old PDCP entity is responsible for determining whether all the old uplink PDUs are correct.
  • the old primary network entity will then trigger the old PDCP entity release operation while releasing the old PDCP layer and the connection relationship with each RLC/MAC/PHY.
  • FIG. 10 is a flow chart showing the implementation example 2 of the present disclosure. As shown in FIG. 10, the UE maintains a wireless connection with two network entities, and the handover procedure includes steps 1 to 10.
  • Step 1 Same as step 1 of Embodiment 1;
  • Step 2 The original primary network entity initiates an anchor change indication to the target from the network entity, where at least the new security context information (eg, new key Key eNodeB Star and Next Hop Chaining Count, etc.) is included; and may include old signaling All wireless configuration parameters carried, or PDCP configuration parameters of the old data bearer;
  • the new security context information eg, new key Key eNodeB Star and Next Hop Chaining Count, etc.
  • Step 3 same as step 3 of Embodiment 1;
  • Step 4 The final RRC message is synthesized by the original primary network entity and sent to the UE.
  • the parameter includes at least a new security context (such as security parameters and/or newly selected encryption algorithms required for the UE to generate a new security key);
  • Step 5 After receiving the configuration, the UE takes effect immediately, and sends a message to notify the network, and then sends an anchor change confirmation message to the network side.
  • the trigger information is only one indication signaling, and may also carry the latest or last uplink PDCP sequence number to the network side;
  • Step 6 same as step 6 of Embodiment 1;
  • Step 7 After receiving the indication information from the UE, the target slave network entity enters a new configuration effective state, or after the new configuration takes effect, performs a path conversion operation, which is similar to the traditional X2 switched path conversion operation.
  • Steps 8 to 10 The same as steps 8 to 10 of the first embodiment.
  • the UE maintains a wireless connection with two network entities, and the handover procedure includes steps 1 through 10.
  • Step 1 Same as step 1 of Embodiment 1;
  • Step 2 The original primary network entity initiates an anchor change indication to the target from the network entity, where at least the new security context information (eg, new key Key eNodeB Star and Next Hop Chaining Count, etc.) is included; and may include old signaling All wireless configuration parameters carried, or PDCP configuration parameters of the old data bearer;
  • the new security context information eg, new key Key eNodeB Star and Next Hop Chaining Count, etc.
  • Step 3 same as step 3 of Embodiment 1;
  • Step 4 The final RRC message is synthesized by the original primary network entity and sent to the UE.
  • the parameter includes at least a new security context (such as security parameters and/or newly selected encryption algorithms required for the UE to generate a new security key);
  • Step 5 After receiving the new configuration, the UE triggers a new configuration to take effect when receiving the indication information sent by the network side, and the network side triggers the new configuration parameter to take effect before sending the indication information, and then sends an anchor change. Confirm the message to the network side.
  • Step 6 same as step 6 of Embodiment 1;
  • Step 7 After receiving the indication information from the UE, the target slave network entity enters a new configuration effective state, or after the new configuration takes effect, performs a path conversion operation, which is similar to the traditional X2 switched path conversion operation.
  • Steps 8 to 10 The same as steps 8 to 10 of the first embodiment.
  • the primary network entity may select a certain slave network entity as a new anchor point, triggering an anchor point (referring to the primary network entity) to change operations, specifically, performing at least the following two One or both operations are performed simultaneously.
  • All bearer PDCP entities are transferred from the primary network entity to the target secondary network entity and reconstructed, and second, the signaling termination point and/or data is changed to the core network.
  • the path from the primary network entity to the target secondary network entity); in addition, other functional entities other than the PDCP entity (such as RLC/MAC/physical layer and the like) remain unchanged; the business data can be seamlessly transferred. Thereby improving the adverse effects on the system.
  • the original primary network entity initiates an anchor change indication to the target from the network entity, where at least the new security context information (such as a new key Key eNodeB Star and Next Hop Chaining Count, and the like), or a new configuration time entry point;
  • the new security context information such as a new key Key eNodeB Star and Next Hop Chaining Count, and the like
  • it may include all wireless configuration parameters carried by the old signaling, or PDCP configuration parameters of the old data bearer;
  • the target After receiving the indication from the network entity, the target saves the new location parameter, selects a new encryption algorithm, configures all wireless parameters carried by the new signaling, and/or configures PDCP parameters of the new data bearer, or updates the data bearer in the slave Radio parameters such as RLC/MAC/PHY of the network entity part.
  • the target then returns the corresponding configuration parameters from the network entity to the primary network entity;
  • the original primary network entity synthesizes a final RRC message and sends the message to the UE.
  • the parameter includes at least a new security context (such as security parameters required for the UE to generate a new security key and/or a newly selected encryption algorithm, etc.), and the network side may indicate the time effective point of the new configuration;
  • the UE does not perform the layer 2/physical layer reconstruction and reset operations, and there are two sets of PDCP sub-configurations for each DRB and/or SRB.
  • the two sets of PDCP sub-configurations as a whole remain connected to the original 2 or more layer 2/physical layers. For example, in the downlink direction, any PDCP PDU of any RLC is received, and a de-heading operation is performed.
  • the PDU header contains a new data indication
  • the PDU is delivered to the new configuration sublayer, decrypted, reordered, decompressed, and then Submitted to the in-order transmission and re-detection function; if the PDU header does not contain new data indication, the PDU is submitted to the old configuration sub-layer, and similar operations are performed in sequence, and finally, the in-order transmission and re-detection functions are also submitted.
  • all RLC/MAC/PHY continue to maintain the original transmission activity; at the same time, the new PDCP SDU will be assigned to the new configuration sublayer after the new SN is allocated, and then compressed, encrypted, and added to the PDU header.
  • the new data indication will be included, and then the data will be transferred to the appropriate RLC/MAC/PHY connection for data transmission based on the routing information.
  • the target from the network entity after receiving the RRC reconfiguration complete message from the UE (ie, the anchor change confirmation message), or after the new configuration takes effect, the path conversion operation is performed, and the specific operation and the traditional X2 switching path are performed. Conversion operation is similar
  • the new configuration takes effect, all network entities do not perform the L2 reset operation.
  • the RLC/MAC/PHY continues to maintain the original transmission activity; at the same time, the new PDCP entity establishes a new mapping relationship with the RLC/MAC/PHY, and the generated new PDCP PDU is Submitted to the underlying layer (RLC) for new data transmission activities, where each new PDU header carries an indication of a new data packet.
  • RLC underlying layer
  • any PDCP PDU received (such as a local RLC or a new slave network PDU) is de-headed. If the PDU header contains a new data indication, the PDU is delivered to the new PDCP entity.
  • the RLC/MAC/PHY continues to maintain the original transmission activity; at the same time, it establishes a new mapping relationship with the PDCP layer of the new primary network entity and allows receiving PDCP PDUs from the new primary network entity. .
  • any PDCP PDU from the local RLC needs to be de-headed.
  • the PDU header does not contain a new data indication, the PDU is submitted to the local old PDCP entity, decrypted, reordered, decompressed, and then submitted. Local in-sequence transfer and repeat detection. If the PDU header contains a new data indication, the PDU is delivered to the new PDCP entity through the interface, and similar operations are performed in sequence, and finally the local sequential transmission and repeated detection functions are submitted.
  • the UE side the PDCP entity, determines that the downlink PDUs before all the new data sequence numbers have been correctly received. At the same time, it is determined that all the uplink PDUs have been acknowledged before the new data sequence number, and the old PDCP configuration sublayer release operation is triggered.
  • the new PDCP entity needs to notify the old PDCP entity of the start value of the new data sequence number of the downlink PDU, and the old PDCP entity is responsible for determining whether all the old downlink PDUs have been acknowledged;
  • the new PDCP entity After receiving the new uplink PDU, the new PDCP entity notifies the old PDCP entity of the new data sequence number start value, and the old PDCP entity is responsible for determining whether all the old uplink PDUs have been correctly received.
  • the old primary network entity will then trigger the old PDCP entity release operation while releasing the old PDCP layer and the connection relationship with each RLC/MAC/PHY.
  • the UE side takes effect immediately after receiving the new configuration, and sends a message to notify the network, and then sends an anchor change confirmation message to the network side.
  • the triggering information is only one indication signaling, and may also carry the latest or last uplink PDCP sequence number to the network side; or the network side may notify the UE configuration through the physical layer or the MAC layer or the RLC layer indication information, which may be only one
  • the indication information may also carry the latest or last downlink PDCP sequence number and the like to the UE. After the UE receives the new configuration, it does not take effect immediately. The new configuration takes effect at the specified time.
  • Some embodiments of the present disclosure also provide a terminal, including:
  • a receiver configured to perform a function of: receiving, by a first network entity that is connected to the terminal, a new configuration parameter of a second network entity that is connected to the terminal, the new configuration parameter is
  • the second network entity is configured according to the indication information that is sent by the first network entity to change the anchor point from the first network entity to the anchor point change operation of the second network entity;
  • the transmitter is configured to perform a function of not performing reset/reestablishment of the underlying transmission when the new configuration parameter is in effect, and transmitting an anchor change confirmation message to the second network entity.
  • the embodiment of the terminal is a device or device corresponding to the method in the foregoing embodiment. All the implementation manners in the foregoing embodiments are applicable to the embodiment of the terminal, and the same technical effects can be achieved.
  • Some embodiments of the present disclosure also provide a network entity device, including:
  • a transmitter configured to perform a function of: transmitting, to the second network entity that is connected to the terminal, an indication that the anchor point is changed from the first network entity to an anchor point change operation of the second network entity;
  • a receiver configured to perform a function of: receiving a new configuration parameter returned by the second network entity according to the indication information;
  • the transmitter is further configured to send the new configuration parameter to the terminal, where the new configuration parameter is used to enable the terminal to perform a new configuration according to the configuration parameter, and after the new configuration is completed, The anchor point is switched to the second network entity.
  • the network entity device is a device or device corresponding to the method on the first network entity side described in the foregoing embodiment, and all implementation manners in the foregoing embodiments are applicable to the device embodiment, and can also achieve the same. Technical effect.
  • Some embodiments of the present disclosure also provide a network entity device, including:
  • a receiver configured to perform: a function for receiving, by a first network entity that is connected to the terminal, an indication that the anchor point is changed from the first network entity to an anchor point change operation of the second network entity;
  • a transmitter configured to perform a function of: returning, to the first network entity, a new configuration parameter according to the indication information, and transmitting, by the first network entity, the new configuration parameter to the The terminal, the new configuration parameter is used to enable the terminal to perform a new configuration according to the new configuration parameter, and after the new configuration is completed, switch the anchor point to the second network entity.
  • the network entity device is a device or device corresponding to the method on the second network entity side described in the foregoing embodiment, and all implementation manners in the foregoing embodiments are applicable to the device embodiment, and can also achieve the same. Technical effect.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • 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 to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, a portion of the technical solution of the present disclosure that contributes in essence or to the related art or a part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
  • the objects of the present disclosure can also be achieved by running a program or a set of programs on any computing device.
  • the computing device can be a well-known general purpose device.
  • the objects of the present disclosure may also be realized by merely providing a program product including program code for implementing the method or apparatus. That is to say, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure.
  • the storage medium may be any known storage medium or any storage medium developed in the future.
  • various components or steps may be decomposed and/or recombined.

Abstract

本公开公开了一种网络实体的切换方法、终端及网络实体设备，其中方法包括：接收与终端保持连接的第一网络实体发送的，与终端保持连接的第二网络实体的新的配置参数，新的配置参数是第二网络实体根据第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；在新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给第二网络实体。

Description

网络实体切换的方法、终端及网络实体设备
相关申请的交叉引用
本申请主张在2017年1月6日在中国提交的中国专利申请号No.201710012121.1的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种网络实体切换的方法、终端及网络实体设备。
背景技术
UE(用户设备)移动到两个网络实体(eNB，演进的节点B)的信号覆盖交叠处后，网络将触发移动性事件，如图1所示，为一普通的双连接的移动场景，UE和第一eNB和第二eNB均保持无线连接。
图2为传统的切换流程，包括：
0.源eNB和目标eNB以及MME(移动管理实体)以及SG(服务网关)之间进行区域限制设置；
1.源eNB向终端发送测量控制，终端与源eNB传输数据包，源eNB与服务网关之间传输数据包，源eNB为终端进行上行链路配置；
2.终端向源eNB发送测量报告；
3.源eNB决定切换；
4.源eNB向目标eNB发送切换请求；
5.目标eNB同意切换，并接纳该切换请求；
6.目标eNB向源eNB反馈切换请求响应，并由源eNB向终端进行下行链路配置；
7.源eNB向终端发送RRC(Radio Resource Control，无线资源控制)配置，重配置等以及移动控制信息，终端接收到这些配置信息后，离开原小区，并同步到新小区；
8.源eNB传输数据包到目标eNB，并传送数据包的序号状态给目标eNB， 并传送数据到目标eNB，由目标eNB缓存这些数据包；
9.终端与目标eNB进行同步；
10.目标eNB向终端发送上行链路配置；
11.终端向目标eNB发送RRC配置、重配置，并完成后，与目标eNB进行数据包的传输，并由目标eNB将数据包传输给服务网关；
12.目标eNB向MME发送路径转换请求；
13.MME收到该路径转换请求后，向服务网关发送修改承载请求；
14.服务网关在转换下行路径后，向源eNB发送结束Marker，服务网关在接收到源eNB的反馈后，与目标ENB进行数据包的传输；
15.服务网关向MME发送修改承载响应；
16.MME向目标eNB发送路径转换响应；
17.目标eNB向源eNB发送释放上下文消息；
18.源eNB释放相应的资源。
上述流程采用的是先中断终端与原eNB侧的数据传输，接入到目标eNB后再继续业务传输，因此会导致较大的数据中断。
为此，可以采用一种与传统DC(数据中断)操作类似，如把目标节点，作为SeNB加入到源侧通信中，采用Split DRB(断开数据无线承载)模式，如下图3：
1.源eNB向目标eNB发送，让目标eNB加入源侧网络的请求(携带有服务网关的配置信息)；
2.目标eNB和源eNB发送加入源侧网络的响应(携带有服务网关的配置信息)；
3.源eNB向UE发送RRC连接重配置消息；
4.UE向源eNB发送RRC连接重配置完成消息；
5.源eNB向目标eNB发送配置完成消息；
6.目标eNB与UE进行随机接入过程。
上述移动性事件中，没有核心网信令，即信令锚点不变化，属于RAN(无线接入网)侧的移动性事件，且数据无中断。
多连接UE可以同时连接两个以上网络实体(每个网络实体至少包含一 个独立的MAC实体)；
其中，仅有一个主网络实体(信令承载和/或数据承载的PDCP(分组数据汇聚协议)功能实体(包括安全/压缩/排序等功能的逻辑实体)所在的网络实体，以及与核心网信令连接和/或数据连接的终止点)；以及
1个或多个从网络实体(没有信令承载的PDCP功能实体以及核心网信令连接的终止点，主要参与数据传输，针对每个承载至少具有类似RLC(无线链路层控制协议)和MAC以及物理层等的功能实体(分段/串接/复用/调度/编码/调制等功能))。
上述图1所示的移动事件发生后的UE将处于多连接状态。按照相关技术实现以及上述的多连接操作，可以使得UE在移动性事件中没有业务中断发生，但对于多连接UE，不会一直保持锚点不改变的状态，这样会给系统带来很多不利的结果，如过长的传输路径，过于集中的处理负荷等，从而使得整个系统的性能下降。随着网络的不断演进，传统网络架构下的节点间移动事件无法满足针对移动性能提出的更高需求。例如，切换过程中保持数据中断最小(甚至为0ms)已经成为下一代网络发展的基本需求。
发明内容
本公开实施例提供了一种网络实体的切换方法、终端及网络实体设备，可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
为解决上述技术问题，本公开的实施例提供如下技术方案：
一种网络实体的切换方法，包括：
接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体。
可选地，在所述发送锚点改变确认消息给所述第二网络实体后，所述方法还包括：
在所述第二网络实体根据所述锚点改变确认消息，将路径由所述第一网络实体转换到所述第二网络实体后，与所述第二网络实体进行数据传输。
可选地，所述与所述第二网络实体进行数据传输的步骤包括：
将发送给所述第二网络实体的新的数据包通过第一配置子层发送给所述第二网络实体；或者
将接收到的来自所述第二网络实体的新的数据包通过所述第一配置子层进行处理。
可选地，将发送给所述第二网络实体的新的数据包通过第一配置子层发送给所述第二网络实体的步骤包括：
将发送给所述第二网络实体的数据包的包头中增加新的序号，并依次进行压缩、加密、增加数据包包头处理后，得到新的数据包；
根据路由信息，将所述新的数据包通过底层发送给所述第二网络实体。
可选地，所述数据包包头携带有：该数据包中包括有发送给所述第二网络实体的新的数据的指示信息。
可选地，将接收到的来自所述第二网络实体的新的数据包通过所述第一配置子层进行处理的步骤包括：
对接收到的来自所述第二网络实体的新的数据包，进行去包头操作，得到处理后的数据包；
对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
可选地，对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理的步骤包括：
对所述数据包进行解密操作，发送给重排序实体，再依据头部信息，将排完序的新数据包转发给第一配置子层的解压缩实体进行解压缩操作，之后发送给按序传输和重复检测功能实体进行处理；或者
对所述数据包进行解密操作，发送给重排序实体和解压缩实体进行相应处理，之后发送给按序传输和重复检测功能实体进行处理。
可选地，所述新的数据包包括：新的信令数据包和/或新的业务数据包。
可选地，所述第二网络实体根据所述锚点改变确认消息，将路径由所述 第一网络实体转换到所述第二网络实体后，还包括：
与所述第一网络实体进行业务数据包的传输。
可选地，与所述第一网络实体进行业务数据包的传输的步骤包括：
将发送给所述第一网络实体的业务数据包通过第二配置子层传输到底层，并发送给所述第一网络实体；或者
将接收到的来自所述第一网络实体的业务数据包通过所述底层传输到所述第二配置子层进行处理。
可选地，将发送给所述第一网络实体的业务数据包通过第二配置子层传输到底层，并发送给所述第一网络实体的步骤包括：
将发送给所述第一网络实体的业务数据包依次进行压缩、加密处理后，根据路由信息，将所述业务数据包通过底层发送给所述第一网络实体。
可选地，将接收到的来自所述第一网络实体的业务数据包通过所述底层传输到所述第二配置子层进行处理的步骤包括：
对通过底层接收到的来自所述第一网络实体的业务数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
可选地，所述切换方法，还包括：
若所述终端已经正确接收，所述第二网络实体的数据包的序列号之前的来自第一网络实体的数据包，且接收到所述第一网络实体接收到所述序列号之前的所有终端发送的上行数据包的确认消息后，触发所述第二配置子层释放操作。
可选地，所述新的配置参数生效的触发条件包括：
所述终端接收到新的配置参数时，立刻生效，并发送一触发信息通知所述第二网络实体，使所述第二网络实体对所述新的配置参数进行生效触发操作；或者
所述终端在接收到所述第二网络实体通过底层发送的指示信息时，对所述新的配置参数进行生效触发操作，且所述第二网络实体在发送所述指示信息时，对所述新的配置参数进行生效触发操作；或者
所述终端接收到新的配置参数后，在一预设时间点触发所述新的配置参数的生效操作，所述第二网络实体在所述预设时间点对所述新的配置参数进 行生效触发操作。
可选地，所述触发信息携带有向所述第二网络实体发送的新的数据包的序列号；
所述指示信息携带有所述第二网络实体发送给所述UE的新的数据包的序列号。
本公开的实施例还提供一种网络实体的切换方法，包括：
与终端保持连接的第一网络实体向与所述终端保持连接的第二网络实体发送，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
所述第一网络实体接收所述第二网络实体根据所述指示信息返回的新的配置参数；
所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
可选地，所述第二网络实体是所述第一网络实体根据所述终端的无线信道条件、网络实体的负荷状况、所述终端与网络实体之间的路径时延和/或无线资源管理策略，在与所述终端保持连接的多个网络实体中选择的一个网络实体。
可选地，所述指示信息至少包括：基于所述第二网络实体的新的配置信息，所述新的配置信息包括：基于所述第二网络实体的安全上下文信息。
可选地，所述指示信息还包括：所述新的配置信息的生效时间点、基于所述第一网络实体的信令承载的无线配置参数和/或基于所述第一网络实体的数据承载的分组数据汇聚协议PDCP配置参数。
可选地，所述新的配置参数包括：基于所述第二网络实体的新的加密算法、信令承载的无线配置参数、数据承载的分组数据汇聚协议PDCP参数和/或更新数据承载从第一网络实体到第二网络实体所用到的底层传输的无线参数。
可选地，所述第一网络实体将所述新的配置参数发送给所述终端的步骤包括：
所述第一网络实体将所述新的配置参数，通过无线资源控制RRC消息发送给所述终端。
可选地，所述切换方法，还包括：
所述第一网络实体在接收到所述第二网络实体通知的新的数据包的序列号时，确定所述序列号之前的所述第一网络实体发送给所述终端的业务数据包已被所述终端全部正确接收，且已正确接收所述终端发送的业务数据包，触发所述第一网络实体释放其配置子层，以及该配置子层与所述第一网络实体的底层的连接关系。
本公开的实施例还提供一种网络实体的切换方法，包括：
与终端保持连接的第二网络实体接收与终端保持连接的第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
根据所述指示信息，向所述第一网络实体返回新的配置参数，并由所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述新的配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
可选地，所述切换方法还包括：
所述第二网络实体接收所述终端根据所述新的配置参数完成配置后反馈的锚点改变确认消息；
根据所述锚点改变确认消息或者根据生效的新的配置参数，将路径由所述第一网络实体转换到所述第二网络实体。
可选地，根据所述锚点改变确认消息或者根据生效的新的配置参数，将路径由所述第一网络实体转换到所述第二网络实体的步骤包括：
根据所述锚点改变确认消息或者根据生效的新的配置参数，向会话网关控制器发送路径转换的请求消息；
接收所述会话网关控制器返回的路径由所述第一网络实体转换到所述第二网络实体的转换完成响应消息。
可选地，所述切换方法还包括：
与所述终端进行数据传输。
可选地，与所述终端进行数据传输的步骤包括：
将发送给所述终端的新的数据包通过所述第二网络实体的配置子层发送给所述终端；或者
将接收到的来自所述终端的新的数据包通过所述配置子层进行处理。
可选地，将发送给所述终端的新的数据包通过所述第二网络实体的配置子层发送给所述终端的步骤包括：
将发送给所述终端的数据包的包头中增加新的序号，并依次进行压缩、加密、增加数据包包头处理后，得到新的数据包，根据路由信息，通过底层发送给所述终端。
可选地，所述数据包包头包括：该数据包中包括有发送给所述终端的新的数据的指示信息。
可选地，将接收到的来自所述终端的新的数据包通过所述配置子层进行处理的步骤包括：
对接收到的来自所述终端的新的数据包，进行去包头操作，得到处理后的数据包；
对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
可选地，所述新的数据包包括：新的信令数据包和/或新的业务数据包。
可选地，所述新的配置参数的生效的触发条件包括：
接收到所述终端发送的触发信息时，对所述新的配置参数进行生效触发操作，所述触发消息是终端在接收到新的配置参数后立即生效后发送的触发信息；或者
向所述终端通过底层发送的指示信息之前，对所述新的配置参数进行生效触发操作，所述指示信息用于使所述终端对所述新的配置参数进行生效触发操作；或者
在一预设时间点触发所述新的配置参数的生效操作，所述终端在所述预设时间点对所述新的配置参数进行生效触发操作。
可选地，所述新的配置参数生效后，所述第二网络实体不进行底层传输的复位/或重建。
本公开的实施例还提供一种终端，包括：
接收机，被配置为执行如下功能：用于接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
发射机，被配置为执行如下功能：用于在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体。
本公开的实施例还提供一种网络实体设备，包括：
发射机，被配置为执行如下功能：用于向与所述终端保持连接的第二网络实体发送，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
接收机，被配置为执行如下功能：用于接收所述第二网络实体根据所述指示信息返回的新的配置参数；
所述射机还用于将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
本公开的实施例还提供一种网络实体设备，包括：
接收机，被配置为执行如下功能：用于接收与终端保持连接的第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
发射机，被配置为执行如下功能：用于根据所述指示信息，向所述第一网络实体返回新的配置参数，并由所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述新的配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
在本公开的上述实施例中，对于多连接的UE，主网络实体(第一网络实体)可选择某一个从网络实体(第二网络实体)作为新的锚点，触发锚点(指主网络实体)改变操作；可以确保业务数据进行无缝转移。
附图说明
图1表示相关技术中终端多连接的网络场景示意图；
图2表示相关技术中终端在不同网络实体间的路径切换的一种流程示意图；
图3表示相关技术中终端在不同网络实体间的路径切换的另一种流程示意图；
图4表示本公开一些实施例的终端侧执行的网络实体的切换方法的流程示意图；
图5表示本公开一些实施例的终端侧的PDCP实体处理下行数据的过程示意图；
图6表示本公开一些实施例的终端侧的PDCP实体处理上行数据的过程示意图；
图7表示本公开一些实施例的第一网络实体侧的网络实体切换方法的流程示意图；
图8表示本公开一些实施例的第二网络实体侧的网络实体切换方法的流程示意图；
图9表示本公开的实现实例1的流程示意图；
图10表示本公开的实现实例2的流程示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
如图4所示，本公开的一些实施例提供了一种网络实体的切换方法，包括：
步骤41，接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
步骤42，在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体。
该实施例中，终端的新的配置参数生效的触发条件包括：
1)所述终端接收到新的配置参数时，立刻生效，并发送一触发信息通知所述第二网络实体，使所述第二网络实体对所述新的配置参数进行生效触发操作；其中，所述触发信息携带有向所述第二网络实体发送的新的数据包的序列号；或者
2)所述终端在接收到所述第二网络实体通过底层发送的指示信息时，对所述新的配置参数进行生效触发操作，且所述第二网络实体在发送所述指示信息时，对所述新的配置参数进行生效触发操作；其中，所述指示信息携带有所述第二网络实体发送给所述UE的新的数据包的序列号；或者
3)所述终端接收到新的配置参数后，在一预设时间点触发所述新的配置参数的生效操作，所述第二网络实体在所述预设时间点对所述新的配置参数进行生效触发操作。
本公开的上述实施例中，对于多连接的UE，主网络实体(第一网络实体)可选择某一个从网络实体(第二网络实体)作为新的锚点，触发锚点(指主网络实体)改变操作；可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
本公开的一些实施例提供了一种网络实体的切换方法，包括：
步骤41，接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
步骤42，在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体；
步骤43，在所述第二网络实体根据所述锚点改变确认消息，将路径由所述第一网络实体转换到所述第二网络实体后，与所述第二网络实体进行数据传输。
具体的，与所述第二网络实体进行数据传输的步骤包括：
步骤431，上行方向，将发送给所述第二网络实体的新的数据包通过第一配置子层发送给所述第二网络实体；或者
步骤432，下行方向将接收到的来自所述第二网络实体的新的数据包通过所述第一配置子层进行处理。
其中，该第一配置子层可以是PDCP(分组数据汇聚协议)配置子层，上述步骤431具体可以包括：
步骤4311，将发送给所述第二网络实体的数据包的包头中增加新的序号，并依次进行压缩、加密、增加数据包包头处理后，得到新的数据包；
步骤4312，根据路由信息，将所述新的数据包通过底层发送给所述第二网络实体。
其中，所述数据包包头携带有：该数据包中包括有发送给所述第二网络实体的新的数据的指示信息。所述新的数据包包括：新的信令数据包和/或新的业务数据包。
如图5所示，UE在对新的配置参数触发生效操作后，不执行层2/物理层的重建和复位操作，针对每个DRB(数据资源块)和/或SRB(信令资源块)存在两套PDCP子配置。
这两套PDCP子配置作为一个整体同时与原来的2或多条层2/物理层保持连接。
在上行方向，所有RLC/MAC/PHY(Physical layer，物理层)继续保持原来的传输活动；同时，新的PDCP SDU分配新的SN(Sequence Number，序列号)后将递交给新的配置子层，依次进行压缩，加密，增加PDU(Protocol Data Unit，协议数据单元)头，其中头中将包含新数据指示，然后根据路由信息，将数据传递给合适的RLC/MAC/PHY连接上进行数据传输。
上述步骤432具体可以包括：
步骤4321，对接收到的来自所述第二网络实体的新的数据包，进行去包头操作，得到处理后的数据包；
步骤4322，对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理；具体的，
对所述数据包进行解密操作，然后发送给重排序实体(与第二配置子层 共享同一个重排序实体)，然后再依据头部信息，将排完序的新数据包转发给第一配置子层的解压缩实体进行解压缩操作，最后发送给按序传输和重复检测功能实体(与第二配置子层共享同一个重排序实体)进行处理；或者
对所述数据包进行解密操作，然后发送给重排序实体(与第二配置子层共享同一个重排序实体)，解压缩实体(与第二配置子层共享同一个解压缩实体)进行相应处理，最后发送给按序传输和重复检测功能实体(与第二配置子层共享同一个重排序实体)进行处理。
所述新的数据包包括：新的信令数据包和/或新的业务数据包。
如图6所示，UE在对新的配置参数触发生效操作后，不执行层2/物理层的重建和复位操作，针对每个DRB(数据资源块)和/或SRB(信令资源块)存在两套PDCP子配置。
而这两套PDCP子配置作为一个整体同时与原来的2或多条层2/物理层保持连接。
在下行方向，接收到任何一个RLC(无线链路控制)的PDCP PDU(分组数据单元)，进行去头操作，如PDU头中包含新数据指示，将PDU递交给新的配置子层，依次进行解密，重排序，解压缩，然后提交给按序传输和重复检测功能；
而如PDU头中没包含新数据指示，将PDU递交给旧的配置子层，依次执行类似的操作，最后也提交给按序传输和重复检测功能。
该实施例中，终端的新的配置参数生效的触发条件包括：
1)所述终端接收到新的配置参数时，立刻生效，并发送一触发信息通知所述第二网络实体，使所述第二网络实体对所述新的配置参数进行生效触发操作；其中，所述触发信息携带有向所述第二网络实体发送的新的数据包的序列号；或者
2)所述终端在接收到所述第二网络实体通过底层发送的指示信息时，对所述新的配置参数进行生效触发操作，且所述第二网络实体在发送所述指示信息时，对所述新的配置参数进行生效触发操作；其中，所述指示信息携带有所述第二网络实体发送给所述UE的新的数据包的序列号；或者
3)所述终端接收到新的配置参数后，在一预设时间点触发所述新的配置 参数的生效操作，所述第二网络实体在所述预设时间点对所述新的配置参数进行生效触发操作。
在所述实施例中，对于多连接的UE，主网络实体(第一网络实体)可选择某一个从网络实体(第二网络实体)作为新的锚点，触发锚点(指主网络实体)改变操作；并进一步实现新的锚点的第二网络实体与终端进行信令传输和/或数据传输，可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
本公开的一些实施例提供了一种网络实体的切换方法，包括：
步骤41，接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
步骤42，在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体；
步骤43，在所述第二网络实体根据所述锚点改变确认消息，将路径由所述第一网络实体转换到所述第二网络实体后，与所述第一网络实体进行业务数据包的传输。
该实施例中，步骤43中，与所述第一网络实体进行业务数据包的传输的步骤包括：
上行方向，将发送给所述第一网络实体的业务数据包通过第二配置子层传输到底层，并发送给所述第一网络实体；或者
下行方向，将接收到的来自所述第一网络实体的业务数据包通过所述底层传输到所述第二配置子层进行处理。
该第二配置子层可以是PDCP(分组数据汇聚协议)配置子层，
其中，上行方向的具体处理流程包括：
将发送给所述第一网络实体的业务数据包依次进行压缩、加密处理后，根据路由信息，将所述业务数据包通过底层发送给所述第一网络实体。
其中，下行方向的具体处理流程包括：
对通过底层接收到的来自所述第一网络实体的业务数据包依次进行解密、 重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
终端的新的配置参数生效的触发条件包括：
1)所述终端接收到新的配置参数时，立刻生效，并发送一触发信息通知所述第二网络实体，使所述第二网络实体对所述新的配置参数进行生效触发操作；其中，所述触发信息携带有向所述第二网络实体发送的新的数据包的序列号；或者
2)所述终端在接收到所述第二网络实体通过底层发送的指示信息时，对所述新的配置参数进行生效触发操作，且所述第二网络实体在发送所述指示信息时，对所述新的配置参数进行生效触发操作；其中，所述指示信息携带有所述第二网络实体发送给所述UE的新的数据包的序列号；或者
3)所述终端接收到新的配置参数后，在一预设时间点触发所述新的配置参数的生效操作，所述第二网络实体在所述预设时间点对所述新的配置参数进行生效触发操作。
该实施例中，第一网络实体作为新的从网络实体，与终端可以进行业务数据包的传输。
进一步的，该实施例中，若所述终端已经正确接收，所述第二网络实体的数据包的序列号之前的来自第一网络实体的数据包，且接收到所述第一网络实体接收到所述序列号之前的所有终端发送的上行数据包的确认消息后，触发所述第二配置子层释放操作。从而可以减小终端的处理负担。
本公开的该实施例，对于多连接的UE，主网络实体(第一网络实体)可选择某一个从网络实体(第二网络实体)作为新的锚点，触发锚点(指主网络实体)改变操作；并进一步实现新的锚点的第二网络实体与终端进行信令传输和/或数据业务传输，并进一步实现将原锚点的第一网络实体作为从网络实体，实现终端与第一网络实体的数据业务传输，可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
本公开的上述实施例中，网络侧会根据UE的无线信道条件，负荷状况，路径时延或其他RRM(Radio Resource Management，无线资源管理)策略等，选择某一个从网络实体作为新的主网络实体，触发锚点(指主网络实体)改变操作；可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
具体的，至少执行下面两个操作之一或两个操作同时执行：
其一，所有承载的PDCP实体从主网络实体(第一网络实体)转移到目标从网络实体(第二网络实体)并进行重建操作；
其二，改变终端到核心网的信令终止点和/或数据路径(从主网络实体到目标从网络实体)，相关技术中，终端到核心网的信令终止点是主网络实体，在本公开的实施例中，终端到核心网的信令终止点是目标从网络实体。
一旦新的配置参数生效，目标从网络实体，变成新的锚点(主网络实体)，而其他网络实体(包括原主网络实体)变成新的从网络实体。
对于锚点改变操作，网络侧重新配置信令承载和/或数据承载在目标锚点的PDCP相关参数或可能更新其他功能实体参数等，并通过主网络实体的RRC消息将这些参数发给UE。
在UE侧，接收到新的配置参数(至少包括新的安全上下文配置和/或新的头压缩配置)后，立刻配置生效，上行方向，通过物理层或MAC层或RLC层发送一指示，通知网络侧新的配置参数生效，具体地可以仅是一条指示信息，也可以携带最新或最后的上行PDCP序列号等给UE；网络侧接收到指示后，将触发网络侧的新的配置参数生效，包括建立新的映射关系，生成新的下行PDCP序列号等等。
可选地，由网络侧通过物理层或MAC层或RLC层向UE发送指示信息，通知UE配置生效，具体可以仅是一条指示信息，也可以携带最新或最后的下行PDCP序列号等给UE。
可选地，UE接收到新的配置参数后不立刻生效，采用时间点的方式，即在指定时间点到达时触发新的配置参数生效，网络侧也在该指定时间点，触发新的配置参数生效，上、下行确定新的PDCP序列号。
如图7所示，本公开的一些实施例还提供一种网络实体的切换方法，包括：
步骤71，与终端保持连接的第一网络实体向与所述终端保持连接的第二网络实体发送，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
步骤72，所述第一网络实体接收所述第二网络实体根据所述指示信息返 回的新的配置参数；
步骤73，所述第一网络实体将所述新的配置参数发送给所述终端，具体的，所述第一网络实体将所述新的配置参数，通过无线资源控制RRC消息发送给所述终端；所述新的配置参数用于使所述终端根据所述配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
本公开的该实施例，对于多连接的UE，主网络实体(第一网络实体)可选择某一个从网络实体(第二网络实体)作为新的锚点，触发锚点(指主网络实体)改变操作；可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
其中，该实施例中，所述第二网络实体是所述第一网络实体根据所述终端的无线信道条件、网络实体的负荷状况、所述终端与网络实体之间的路径时延和/或无线资源管理策略，在与所述终端保持连接的多个网络实体中选择的一个网络实体。
所述指示信息至少包括：基于所述第二网络实体的新的配置信息，所述新的配置信息包括：基于所述第二网络实体的安全上下文信息。
所述指示信息还包括：所述新的配置信息的生效时间点、基于所述第一网络实体的信令承载的无线配置参数和/或基于所述第一网络实体的数据承载的分组数据汇聚协议PDCP配置参数。
所述新的配置参数包括：基于所述第二网络实体的新的加密算法、信令承载的无线配置参数、数据承载的分组数据汇聚协议PDCP参数和/或更新数据承载从第一网络实体到第二网络实体所用到的底层传输的无线参数。
该实施例中，该方法还可以进一步包括：
所述第一网络实体在接收到所述第二网络实体通知的新的数据包的序列号时，确定所述序列号之前的所述第一网络实体发送给所述终端的业务数据包已被所述终端全部正确接收，且已正确接收所述终端发送的业务数据包，触发所述第一网络实体释放其配置子层，以及该配置子层与所述第一网络实体的底层的连接关系。从而减轻网络实体的处理负担。
本公开的该实施例中，在网络侧，由主网络实体(第一网络实体)，向目标从网络实体(第二网络实体)，发起锚点改变指示，其中至少包含新安全上 下文信息，或旧的无线配置参数等。
目标从网络实体接收指示后，选择新的加密算法，配置新的无线参数。
然后目标从网络实体返回相应配置参数给主网络实体，并由主网络实体合成最终RRC消息发送给UE。
一旦新配置生效，所有网络实体不执行层2/物理层的重建和复位操作等，在上行方向，所有PDCP PDU先执行去头操作，判断是否为新数据，从而提交给正确的目标PDCP层。
在下行方向，RLC/MAC/PHY继续保持原来的传输活动；同时，与新的PDCP实体建立新的映射关系，并允许处理来自新的PDCP实体的PDU数据。
如图8所示，本公开的一些实施例提供一种网络实体的切换方法，包括：
步骤81，与终端保持连接的第二网络实体接收与终端保持连接的第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
步骤82，根据所述指示信息，向所述第一网络实体返回新的配置参数，并由所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述新的配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
本公开的该实施例，对于多连接的UE，主网络实体(第一网络实体)可选择某一个从网络实体(第二网络实体)作为新的锚点，触发锚点(指主网络实体)改变操作；并可以进一步配置新的配置参数，并发送给终端，使得终端可以根据该新的配置参数，与第二网络实体进一步进行数据传输，可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
该实施例中，切换方法还包括：
步骤83，所述第二网络实体接收所述终端根据所述新的配置参数完成配置后反馈的锚点改变确认消息；
步骤84，根据所述锚点改变确认消息或者根据生效的新的配置参数，将路径由所述第一网络实体转换到所述第二网络实体；
具体的，根据所述锚点改变确认消息或者根据生效的新的配置参数，向会话网关控制器(SGC)发送路径转换的请求消息；
接收所述会话网关控制器(SGC)返回的路径由所述第一网络实体转换到所述第二网络实体的转换完成响应消息。
该实施例中，切换方法还可以进一步包括：
步骤85，与所述终端进行数据传输。
具体的，下行方向，将发送给所述终端的新的数据包通过所述第二网络实体的配置子层发送给所述终端；
具体的，将发送给所述终端的数据包的包头中增加新的序号，并依次进行压缩、加密、增加数据包包头处理后，得到新的数据包，根据路由信息，通过底层发送给所述终端；其中，所述数据包包头包括：该数据包中包括有发送给所述终端的新的数据的指示信息。
或者上行方向，将接收到的来自所述终端的新的数据包通过所述配置子层进行处理；
具体的，对接收到的来自所述终端的新的数据包，进行去包头操作，得到处理后的数据包；
对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
其中，所述新的数据包包括：新的信令数据包和/或新的业务数据包。
本公开的该实施例中，第二网络实体的所述新的配置参数的生效的触发条件包括：
接收到所述终端发送的触发信息时，对所述新的配置参数进行生效触发操作，所述触发消息是终端在接收到新的配置参数后立即生效后发送的触发信息；或者
向所述终端通过底层发送的指示信息之前，对所述新的配置参数进行生效触发操作，所述指示信息用于使所述终端对所述新的配置参数进行生效触发操作；或者
在一预设时间点触发所述新的配置参数的生效操作，所述终端在所述预设时间点对所述新的配置参数进行生效触发操作。
其中，所述新的配置参数生效后，所述第二网络实体不进行底层传输的复位/或重建。
下面具体说明上述实施例的具体实现场景，包括实现示例1、实现示例2和实现示例3。
图9是本公开的实现实例1的流程示意图。如图9所示，UE与两个网络实体维持无线连接，切换流程包括步骤1至10。
步骤1：原主网络实体(第一网络实体)根据UE的无线信道条件，负荷状况，路径时延或其他RRM策略等，选择某一个从网络实体(第二网络实体)作为新的主网络实体，触发锚点(指主网络实体)改变操作；
步骤2：原主网络实体，向目标从网络实体，发起锚点改变指示，其中至少包含新安全上下文信息(如：新的秘钥Key eNodeB Star和Next Hop Chaining Count等类似参数)，或新配置时间生效点；此外可能包含旧信令承载的所有无线配置参数，或旧数据承载的PDCP配置参数；
步骤3：目标从网络实体接收指示后，保存新的配置参数，选择新的加密算法，配置新信令承载的所有无线参数，和/或配置新数据承载的PDCP参数，或更新该数据承载在从网络实体部分的RLC/MAC/PHY等无线参数。然后目标从网络实体返回相应配置参数给主网络实体；
步骤4：由原主网络实体合成最终RRC消息发送给UE。
参数中至少包括新的安全上下文(如为了让UE生成新安全密钥所需的安全参数和/或新选择的加密算法等)，此外，网络侧可以标明新配置的时间生效点；
步骤5：在指定时间点到达时，UE触发新配置生效，并发送锚点改变确认消息给网络侧，同时网络侧也在指定时间点触发新的配置参数的生效；
步骤6：一旦新配置生效，UE不执行层2/物理层的重建和复位操作，针对每个DRB和/或SRB存在两套PDCP子配置。
而这两套PDCP子配置作为一个整体同时与原来的2或多条层2/物理层保持连接。
例如，在下行方向，接收到任何一个RLC的PDCP PDU，进行去头操作，如PDU头中包含新数据指示，将PDU递交给新的配置子层，依次进行解密，重排序，解压缩，然后提交给按序传输和重复检测功能；
而如PDU头中没包含新数据指示，将PDU递交给旧的配置子层，依次 执行类似的操作，最后也提交给按序传输和重复检测功能。
在上行方向，所有RLC/MAC/PHY继续保持原来的传输活动；
同时，新的PDCP SDU分配新的SN后将递交给新的配置子层，依次进行压缩，加密，增加PDU头，其中头中将包含新数据指示，然后根据路由信息，将数据传递给合适的RLC/MAC/PHY连接上进行数据传输。
步骤7：目标从网络实体，在接收到来自UE的RRC重配置完成消息后(即锚点改变确认消息)，或者在新配置生效后，将执行路径转换操作，具体操作与传统的X2切换后路径转换操作类似。
步骤8：一旦新配置生效，所有网络实体不执行L2复位操作。
例如，对于新的主网络实体，在下行方向，RLC/MAC/PHY继续保持原来的传输活动；同时，新的PDCP实体与RLC/MAC/PHY建立新的映射关系，而产生的新PDCP PDU被递交给底层(RLC)进行新数据传输活动，其中每个新PDU头中携带指示为新数据包。
在上行方向，接收到任何一个PDCP PDU(如来自本地的RLC或来自新的从网络实体的PDU)，都进行去头操作，如PDU头中包含新数据指示，将PDU递交给新的PDCP实体，依次进行解密，重排序，解压缩，然后提交给本地的按序传输和重复检测功能；
而如PDU头中没包含新数据指示，将PDU通过接口传递给旧的主网络实体的PDCP层，依次执行类似的操作，最后提交给本地的按序传输和重复检测功能。
对于新的从网络实体，在下行方向，RLC/MAC/PHY继续保持原来的传输活动；同时，与新主网络实体的PDCP层建立新的映射关系，并允许接收来自新主网络实体的PDCP PDU。
在上行方向，来自本地RLC的任何一个PDCP PDU都需要进行去头操作，如PDU头中没包含新数据指示，将PDU提交给本地旧PDCP实体，依次执行解密，重排序，解压缩，然后提交给本地的按序传输和重复检测功能。如PDU头中包含新数据指示，将PDU通过接口递交给新的PDCP实体，依次执行类似的操作，最后提交给本地的按序传输和重复检测功能。
步骤9：UE侧，PDCP实体，判断已经正确接收所有新数据序列号之前 的下行PDU；同时，判断新数据序列号之前所有上行PDU已经得到确认，将触发旧的PDCP配置子层释放操作。
步骤10：类似地，在网络侧，在下行方向，新的PDCP实体需要通知旧的PDCP实体下行PDU新数据序列号的起始值，而旧的PDCP实体负责判断是否所有旧的下行PDU都已经被确认；同时在上行方向，新的PDCP实体收到新的上行PDU后，将新数据序列号起始值通知旧的PDCP实体，而旧的PDCP实体负责判断是否所有旧的上行PDU都已经正确接收。然后旧的主网络实体将触发旧的PDCP实体释放操作，同时释放旧的PDCP层以及与各RLC/MAC/PHY的连接关系。
图10表示本公开的实现实例2的流程示意图。如图10所示，UE与两个网络实体维持无线连接，切换流程包括步骤1至10。
步骤1：与实施例1的步骤1同；
步骤2：原主网络实体向目标从网络实体发起锚点改变指示，其中至少包含新安全上下文信息(如：新的秘钥Key eNodeB Star和Next Hop Chaining Count等类似参数)；此外可能包含旧信令承载的所有无线配置参数，或旧数据承载的PDCP配置参数；
步骤3：与实施例1的步骤3同；
步骤4：由原主网络实体合成最终RRC消息发送给UE。参数中至少包括新的安全上下文(如为了让UE生成新安全密钥所需的安全参数和/或新选择的加密算法等)；
步骤5：UE接到配置后，立刻生效，并发送信息通知网络，随后发送锚点改变确认消息给网络侧。触发信息仅是一条指示信令，也可以携带最新或最后的上行PDCP序列号等给网络侧；
步骤6：与实施例1的步骤6同；
步骤7：目标从网络实体，在接收到来自UE的指示信息后，进入新配置生效状态，或者在新配置生效后，将执行路径转换操作，具体操作与传统的X2切换后路径转换操作类似。
步骤8～10：与实施例1的步骤8～10同。
在实现实例3中，UE与两个网络实体维持无线连接，切换流程包括步骤 1至10。
步骤1：与实施例1的步骤1同；
步骤2：原主网络实体向目标从网络实体发起锚点改变指示，其中至少包含新安全上下文信息(如：新的秘钥Key eNodeB Star和Next Hop Chaining Count等类似参数)；此外可能包含旧信令承载的所有无线配置参数，或旧数据承载的PDCP配置参数；
步骤3：与实施例1的步骤3同；
步骤4：由原主网络实体合成最终RRC消息发送给UE。参数中至少包括新的安全上下文(如为了让UE生成新安全密钥所需的安全参数和/或新选择的加密算法等)；
步骤5：UE接到新配置后，并在接收到网络侧发送的指示信息时触发新的配置生效，而网络侧在发送所述指示信息之前触发新的配置参数的生效，随后发送锚点改变确认消息给网络侧。
步骤6：与实施例1的步骤6同；
步骤7：目标从网络实体，在接收到来自UE的指示信息后，进入新配置生效状态，或者在新配置生效后，将执行路径转换操作，具体操作与传统的X2切换后路径转换操作类似。
步骤8～10：与实施例1的步骤8～10同。
本公开的上述实施例中，对于多连接的UE，主网络实体可选择某一个从网络实体作为新的锚点，触发锚点(指主网络实体)改变操作，具体的，至少执行下面两个操作之一或两个操作同时执行，其一，所有承载的PDCP实体从主网络实体转移到目标从网络实体并进行重建操作，其二为，改变到核心网的信令终止点和/或数据路径(从主网络实体到目标从网络实体)；此外，允许除PDCP实体外的其他功能实体(如RLC/MAC/物理层等类似功能实体)保持不变化；可以确保业务数据进行无缝转移，从而改善对系统的不利影响。
其中，原主网络实体向目标从网络实体发起锚点改变指示，其中至少包含新安全上下文信息(如：新的秘钥Key eNodeB Star和Next Hop Chaining Count等类似参数)，或新配置时间生效点；此外可能包含旧信令承载的所有无线配置参数，或旧数据承载的PDCP配置参数；
其中，目标从网络实体接收指示后，保存新的位置参数，选择新的加密算法，配置新信令承载的所有无线参数，和/或配置新数据承载的PDCP参数，或更新该数据承载在从网络实体部分的RLC/MAC/PHY等无线参数。然后目标从网络实体返回相应配置参数给主网络实体；
其中，原主网络实体合成最终RRC消息发送给UE。参数中至少包括新的安全上下文(如为了让UE生成新安全密钥所需的安全参数和/或新选择的加密算法等)，此外，网络侧可以标明新配置的时间生效点；
其中，一旦新配置生效，UE不执行层2/物理层的重建和复位操作，针对每个DRB和/或SRB存在两套PDCP子配置。而这两套PDCP子配置作为一个整体同时与原来的2或多条层2/物理层保持连接。例如，在下行方向，接收到任何一个RLC的PDCP PDU，进行去头操作，如PDU头中包含新数据指示，将PDU递交给新的配置子层，依次进行解密，重排序，解压缩，然后提交给按序传输和重复检测功能；而如PDU头中没包含新数据指示，将PDU递交给旧的配置子层，依次执行类似的操作，最后也提交给按序传输和重复检测功能。在上行方向，所有RLC/MAC/PHY继续保持原来的传输活动；同时，新的PDCP SDU分配新的SN后将递交给新的配置子层，依次进行压缩，加密，增加PDU头，其中头中将包含新数据指示，然后根据路由信息，将数据传递给合适的RLC/MAC/PHY连接上进行数据传输。
其中，目标从网络实体，在接收到来自UE的RRC重配置完成消息后(即锚点改变确认消息)，或者在新配置生效后，将执行路径转换操作，具体操作与传统的X2切换后路径转换操作类似
其中，一旦新配置生效，所有网络实体不执行L2复位操作。例如，对于新的主网络实体，在下行方向，RLC/MAC/PHY继续保持原来的传输活动；同时，新的PDCP实体与RLC/MAC/PHY建立新的映射关系，而产生的新PDCP PDU被递交给底层(RLC)进行新数据传输活动，其中每个新PDU头中携带指示为新数据包。在上行方向，接收到任何一个PDCP PDU(如来自本地的RLC或来自新的从网络实体的PDU)，都进行去头操作，如PDU头中包含新数据指示，将PDU递交给新的PDCP实体，依次进行解密，重排序，解压缩，然后提交给本地的按序传输和重复检测功能；而如PDU头中没包含 新数据指示，将PDU通过接口传递给旧的主网络实体的PDCP层，依次执行类似的操作，最后提交给本地的按序传输和重复检测功能。对于新的从网络实体，在下行方向，RLC/MAC/PHY继续保持原来的传输活动；同时，与新主网络实体的PDCP层建立新的映射关系，并允许接收来自新主网络实体的PDCP PDU。在上行方向，来自本地RLC的任何一个PDCP PDU都需要进行去头操作，如PDU头中没包含新数据指示，将PDU提交给本地旧PDCP实体，依次执行解密，重排序，解压缩，然后提交给本地的按序传输和重复检测功能。如PDU头中包含新数据指示，将PDU通过接口递交给新的PDCP实体，依次执行类似的操作，最后提交给本地的按序传输和重复检测功能。
其中，UE侧，PDCP实体，判断已经正确接收所有新数据序列号之前的下行PDU；同时，判断新数据序列号之前所有上行PDU已经得到确认，将触发旧的PDCP配置子层释放操作。
其中，在网络侧，在下行方向，新的PDCP实体需要通知旧的PDCP实体下行PDU新数据序列号的起始值，而旧的PDCP实体负责判断是否所有旧的下行PDU都已经被确认；同时在上行方向，新的PDCP实体收到新的上行PDU后，将新数据序列号起始值通知旧的PDCP实体，而旧的PDCP实体负责判断是否所有旧的上行PDU都已经正确接收。然后旧的主网络实体将触发旧的PDCP实体释放操作，同时释放旧的PDCP层以及与各RLC/MAC/PHY的连接关系。
其中，UE侧，接收到新配置后，立刻生效，并发送信息通知网络，随后发送锚点改变确认消息给网络侧。触发信息仅是一条指示信令，也可以携带最新或最后的上行PDCP序列号等给网络侧；或由网络侧通过物理层或MAC层或RLC层指示信息通知UE配置生效，具体可以仅是一条指示信息，也可以携带最新或最后的下行PDCP序列号等给UE。或者UE接收到新配置后，并不立刻生效，在指定的时间点新配置生效。
本公开的一些实施例还提供一种终端，包括：
接收机，被配置为执行如下功能：用于接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第 一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
发射机，被配置为执行如下功能：用于在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体。
需要说明的是，该终端的实施例是与上述实施例所述方法对应的装置或者设备，上述实施例中所有实现方式均适用于该终端的实施例中，也能达到相同的技术效果。
本公开的一些实施例还提供一种网络实体设备，包括：
发射机，被配置为执行如下功能：用于向与所述终端保持连接的第二网络实体发送，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
接收机，被配置为执行如下功能：用于接收所述第二网络实体根据所述指示信息返回的新的配置参数；
所述射机还用于将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
需要说明的，该网络实体设备是与上述实施例所述的第一网络实体侧的方法对应的装置或者设备，上述实施例中所有实现方式均适用于该装置的实施例中，也能达到相同的技术效果。
本公开的一些实施例还提供一种网络实体设备，包括：
接收机，被配置为执行如下功能：用于接收与终端保持连接的第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
发射机，被配置为执行如下功能：用于根据所述指示信息，向所述第一网络实体返回新的配置参数，并由所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述新的配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
需要说明的，该网络实体设备是与上述实施例所述的第二网络实体侧的方法对应的装置或者设备，上述实施例中所有实现方式均适用于该装置的实施例中，也能达到相同的技术效果。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程 序代码的介质。
此外，需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行，某些步骤可以并行或彼此独立地执行。对本领域的普通技术人员而言，能够理解本公开的方法和装置的全部或者任何步骤或者部件，可以在任何计算装置(包括处理器、存储介质等)或者计算装置的网络中，以硬件、固件、软件或者它们的组合加以实现，这是本领域普通技术人员在阅读了本公开的说明的情况下运用他们的基本编程技能就能实现的。
因此，本公开的目的还可以通过在任何计算装置上运行一个程序或者一组程序来实现。所述计算装置可以是公知的通用装置。因此，本公开的目的也可以仅仅通过提供包含实现所述方法或者装置的程序代码的程序产品来实现。也就是说，这样的程序产品也构成本公开，并且存储有这样的程序产品的存储介质也构成本公开。显然，所述存储介质可以是任何公知的存储介质或者将来所开发出来的任何存储介质。还需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行。某些步骤可以并行或彼此独立地执行。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (36)

  1. 一种网络实体的切换方法，包括：
    接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
    在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体。
  2. 根据权利要求1所述的切换方法，其中，在所述发送锚点改变确认消息给所述第二网络实体后，所述方法还包括：
    在所述第二网络实体根据所述锚点改变确认消息，将路径由所述第一网络实体转换到所述第二网络实体后，与所述第二网络实体进行数据传输。
  3. 根据权利要求2所述的切换方法，其中，所述与所述第二网络实体进行数据传输的步骤包括：
    将发送给所述第二网络实体的新的数据包通过第一配置子层发送给所述第二网络实体；或者
    将接收到的来自所述第二网络实体的新的数据包通过所述第一配置子层进行处理。
  4. 根据权利要求3所述的切换方法，其中，将发送给所述第二网络实体的新的数据包通过第一配置子层发送给所述第二网络实体的步骤包括：
    将发送给所述第二网络实体的数据包的包头中增加新的序号，并依次进行压缩、加密、增加数据包包头处理后，得到新的数据包；
    根据路由信息，将所述新的数据包通过底层发送给所述第二网络实体。
  5. 根据权利要求4所述的切换方法，其中，所述数据包包头携带有：该数据包中包括有发送给所述第二网络实体的新的数据的指示信息。
  6. 根据权利要求3所述的切换方法，其中，将接收到的来自所述第二网络实体的新的数据包通过所述第一配置子层进行处理的步骤包括：
    对接收到的来自所述第二网络实体的新的数据包，进行去包头操作，得 到处理后的数据包；
    对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
  7. 根据权利要求6所述的切换方法，其中，对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理的步骤包括：
    对所述数据包进行解密操作，发送给重排序实体，再依据头部信息，将排完序的新数据包转发给第一配置子层的解压缩实体进行解压缩操作，之后发送给按序传输和重复检测功能实体进行处理；或者
    对所述数据包进行解密操作，发送给重排序实体和解压缩实体进行相应处理，之后发送给按序传输和重复检测功能实体进行处理。
  8. 根据权利要求3-7中任一项所述的切换方法，其中，所述新的数据包包括：新的信令数据包和/或新的业务数据包。
  9. 根据权利要求3所述的切换方法，其中，所述第二网络实体根据所述锚点改变确认消息，将路径由所述第一网络实体转换到所述第二网络实体后，所述方法还包括：
    与所述第一网络实体进行业务数据包的传输。
  10. 根据权利要求9所述的切换方法，其中，与所述第一网络实体进行业务数据包的传输的步骤包括：
    将发送给所述第一网络实体的业务数据包通过第二配置子层传输到底层，并发送给所述第一网络实体；或者
    将接收到的来自所述第一网络实体的业务数据包通过所述底层传输到所述第二配置子层进行处理。
  11. 根据权利要求10所述的切换方法，其中，将发送给所述第一网络实体的业务数据包通过第二配置子层传输到底层，并发送给所述第一网络实体的步骤包括：
    将发送给所述第一网络实体的业务数据包依次进行压缩、加密处理后，根据路由信息，将所述业务数据包通过底层发送给所述第一网络实体。
  12. 根据权利要求10所述的切换方法，其中，将接收到的来自所述第一 网络实体的业务数据包通过所述底层传输到所述第二配置子层进行处理的步骤包括：
    对通过底层接收到的来自所述第一网络实体的业务数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
  13. 根据权利要求9所述的切换方法，还包括：
    若所述终端已经正确接收，所述第二网络实体的数据包的序列号之前的来自第一网络实体的数据包，且接收到所述第一网络实体接收到所述序列号之前的所有终端发送的上行数据包的确认消息后，触发所述第二配置子层释放操作。
  14. 根据权利要求1所述的切换方法，其中，所述新的配置参数生效的触发条件包括：
    所述终端接收到新的配置参数时，立刻生效，并发送一触发信息通知所述第二网络实体，使所述第二网络实体对所述新的配置参数进行生效触发操作；或者
    所述终端在接收到所述第二网络实体通过底层发送的指示信息时，对所述新的配置参数进行生效触发操作，且所述第二网络实体在发送所述指示信息时，对所述新的配置参数进行生效触发操作；或者
    所述终端接收到新的配置参数后，在一预设时间点触发所述新的配置参数的生效操作，所述第二网络实体在所述预设时间点对所述新的配置参数进行生效触发操作。
  15. 根据权利要求14所述的切换方法，其中，所述触发信息携带有向所述第二网络实体发送的新的数据包的序列号；
    所述指示信息携带有所述第二网络实体发送给所述UE的新的数据包的序列号。
  16. 一种网络实体的切换方法，包括：
    与终端保持连接的第一网络实体向与所述终端保持连接的第二网络实体发送，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
    所述第一网络实体接收所述第二网络实体根据所述指示信息返回的新的 配置参数；
    所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
  17. 根据权利要求16所述的切换方法，其中，所述第二网络实体是所述第一网络实体根据所述终端的无线信道条件、网络实体的负荷状况、所述终端与网络实体之间的路径时延和/或无线资源管理策略，在与所述终端保持连接的多个网络实体中选择的一个网络实体。
  18. 根据权利要求16所述的切换方法，其中，所述指示信息至少包括：基于所述第二网络实体的新的配置信息，所述新的配置信息包括：基于所述第二网络实体的安全上下文信息。
  19. 根据权利要求18所述的切换方法，其中，所述指示信息还包括：所述新的配置信息的生效时间点、基于所述第一网络实体的信令承载的无线配置参数和/或基于所述第一网络实体的数据承载的分组数据汇聚协议PDCP配置参数。
  20. 根据权利要求16所述的切换方法，其中，所述新的配置参数包括：基于所述第二网络实体的新的加密算法、信令承载的无线配置参数、数据承载的分组数据汇聚协议PDCP参数和/或更新数据承载从第一网络实体到第二网络实体所用到的底层传输的无线参数。
  21. 根据权利要求16所述的切换方法，其中，所述第一网络实体将所述新的配置参数发送给所述终端的步骤包括：
    所述第一网络实体将所述新的配置参数，通过无线资源控制RRC消息发送给所述终端。
  22. 根据权利要求16所述的切换方法，还包括：
    所述第一网络实体在接收到所述第二网络实体通知的新的数据包的序列号时，确定所述序列号之前的所述第一网络实体发送给所述终端的业务数据包已被所述终端全部正确接收，且已正确接收所述终端发送的业务数据包，触发所述第一网络实体释放其配置子层，以及该配置子层与所述第一网络实体的底层的连接关系。
  23. 一种网络实体的切换方法，包括：
    与终端保持连接的第二网络实体接收与终端保持连接的第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
    根据所述指示信息，向所述第一网络实体返回新的配置参数，并由所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述新的配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
  24. 根据权利要求23所述的切换方法，还包括：
    所述第二网络实体接收所述终端根据所述新的配置参数完成配置后反馈的锚点改变确认消息；
    根据所述锚点改变确认消息或者根据生效的新的配置参数，将路径由所述第一网络实体转换到所述第二网络实体。
  25. 根据权利要求24所述的切换方法，其中，根据所述锚点改变确认消息或者根据生效的新的配置参数，将路径由所述第一网络实体转换到所述第二网络实体的步骤包括：
    根据所述锚点改变确认消息或者根据生效的新的配置参数，向会话网关控制器发送路径转换的请求消息；
    接收所述会话网关控制器返回的路径由所述第一网络实体转换到所述第二网络实体的转换完成响应消息。
  26. 根据权利要求24所述的切换方法，还包括：
    与所述终端进行数据传输。
  27. 根据权利要求26所述的切换方法，其中，与所述终端进行数据传输的步骤包括：
    将发送给所述终端的新的数据包通过所述第二网络实体的配置子层发送给所述终端；或者
    将接收到的来自所述终端的新的数据包通过所述配置子层进行处理。
  28. 根据权利要求27所述的切换方法，其中，将发送给所述终端的新的数据包通过所述第二网络实体的配置子层发送给所述终端的步骤包括：
    将发送给所述终端的数据包的包头中增加新的序号，并依次进行压缩、加密、增加数据包包头处理后，得到新的数据包，根据路由信息，通过底层发送给所述终端。
  29. 根据权利要求28所述的切换方法，其中，所述数据包包头包括：该数据包中包括有发送给所述终端的新的数据的指示信息。
  30. 根据权利要求27所述的切换方法，其中，将接收到的来自所述终端的新的数据包通过所述配置子层进行处理的步骤包括：
    对接收到的来自所述终端的新的数据包，进行去包头操作，得到处理后的数据包；
    对所述数据包依次进行解密、重排序、解压缩处理后，发送给按序传输和重复检测功能实体进行处理。
  31. 根据权利要求27-30中任一项所述的切换方法，其中，所述新的数据包包括：新的信令数据包和/或新的业务数据包。
  32. 根据权利要求24所述的切换方法，其中，所述新的配置参数的生效的触发条件包括：
    接收到所述终端发送的触发信息时，对所述新的配置参数进行生效触发操作，所述触发消息是终端在接收到新的配置参数后立即生效后发送的触发信息；或者
    向所述终端通过底层发送的指示信息之前，对所述新的配置参数进行生效触发操作，所述指示信息用于使所述终端对所述新的配置参数进行生效触发操作；或者
    在一预设时间点触发所述新的配置参数的生效操作，所述终端在所述预设时间点对所述新的配置参数进行生效触发操作。
  33. 根据权利要求24所述的切换方法，其中，所述新的配置参数生效后，所述第二网络实体不进行底层传输的复位/或重建。
  34. 一种终端，包括：
    接收机，被配置为执行如下功能：用于接收与终端保持连接的第一网络实体发送的，与所述终端保持连接的第二网络实体的新的配置参数，所述新的配置参数是所述第二网络实体根据所述第一网络实体发送的，将锚点由第 一网络实体改变为第二网络实体的锚点改变操作的指示信息配置的；
    发射机，被配置为执行如下功能：用于在所述新的配置参数生效时，不进行底层传输的复位/或重建，并发送锚点改变确认消息给所述第二网络实体。
  35. 一种网络实体设备，包括：
    发射机，被配置为执行如下功能：用于向与所述终端保持连接的第二网络实体发送，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
    接收机，被配置为执行如下功能：用于接收所述第二网络实体根据所述指示信息返回的新的配置参数；
    所述发射机还用于将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
  36. 一种网络实体设备，包括：
    接收机，被配置为执行如下功能：用于接收与终端保持连接的第一网络实体发送的，将锚点由第一网络实体改变为第二网络实体的锚点改变操作的指示信息；
    发射机，被配置为执行如下功能：用于根据所述指示信息，向所述第一网络实体返回新的配置参数，并由所述第一网络实体将所述新的配置参数发送给所述终端，所述新的配置参数用于使所述终端根据所述新的配置参数进行新的配置，并在新的配置完成后，将锚点切换到所述第二网络实体。
PCT/CN2018/076497 2017-01-06 2018-02-12 网络实体切换的方法、终端及网络实体设备 WO2018127243A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/476,056 US20190335369A1 (en) 2017-01-06 2018-02-12 Method for network entity handover, terminal and network entity device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710012121.1A CN108282830B (zh) 2017-01-06 2017-01-06 一种网络实体切换的方法、终端及网络实体设备
CN201710012121.1 2017-01-06

Publications (1)

Publication Number Publication Date
WO2018127243A1 true WO2018127243A1 (zh) 2018-07-12

Family

ID=62789155

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076497 WO2018127243A1 (zh) 2017-01-06 2018-02-12 网络实体切换的方法、终端及网络实体设备

Country Status (3)

Country Link
US (1) US20190335369A1 (zh)
CN (1) CN108282830B (zh)
WO (1) WO2018127243A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018035431A1 (en) * 2016-08-18 2018-02-22 Convida Wireless, Llc Network service exposure for service and session continuity
WO2020015733A1 (zh) * 2018-07-19 2020-01-23 Oppo广东移动通信有限公司 D2d通信的方法和终端设备
CN110831258A (zh) * 2018-08-10 2020-02-21 华为技术有限公司 一种数据传输的方法及装置
CN110839266B (zh) * 2018-08-17 2021-12-24 维沃移动通信有限公司 一种信息的处理方法、用户侧设备及网络侧设备
BR112021002576A2 (pt) * 2018-08-17 2021-05-11 Telefonaktiebolaget Lm Ericsson (Publ) nó de rede, primeiro nó de rede e dispositivo sem fio para manipular uma comutação de enlace de um dispositivo sem fio e métodos relacionados
CN110944368A (zh) * 2018-09-25 2020-03-31 电信科学技术研究院有限公司 一种切换过程中传输数据的方法和设备
CN111132244A (zh) * 2018-10-31 2020-05-08 电信科学技术研究院有限公司 一种切换方法、装置及终端
CN109618419B (zh) * 2018-12-19 2021-10-26 中兴通讯股份有限公司 一种用于支持双连接的安全处理方法及系统
CN113678504A (zh) * 2019-09-20 2021-11-19 Oppo广东移动通信有限公司 一种切换处理方法、网络设备
CN117413565A (zh) * 2021-06-07 2024-01-16 高通股份有限公司 具有l2 ue到网络中继的双连通性移动性管理

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014075210A1 (zh) * 2012-11-13 2014-05-22 华为技术有限公司 传输数据的方法、基站和用户设备
CN104937985A (zh) * 2013-02-01 2015-09-23 联发科技股份有限公司 本地区域无线网中低开销移动性管理
CN104935414A (zh) * 2014-03-21 2015-09-23 上海贝尔股份有限公司 一种在双连接系统中传输信息的方法和装置
CN105122863A (zh) * 2013-01-18 2015-12-02 联发科技股份有限公司 小小区网络中rlm以及rlf机制的处理
US9538575B2 (en) * 2014-01-30 2017-01-03 Sharp Kabushiki Kaisha Systems and methods for dual-connectivity operation
WO2017075824A1 (zh) * 2015-11-06 2017-05-11 广东欧珀移动通信有限公司 锚点更换的方法及设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160135107A1 (en) * 2014-11-06 2016-05-12 Qualcomm Incorporated Migration of local anchors in a wireless mesh network
CN106211244B (zh) * 2015-05-07 2021-01-22 中兴通讯股份有限公司 一种实现蜂窝网络重定位的方法和基站
US10512096B2 (en) * 2015-07-01 2019-12-17 Lg Electronics Inc. Method for transmitting data in dual connectivity and a device therefor
EP3527035B1 (en) * 2016-10-17 2021-08-25 Telefonaktiebolaget LM Ericsson (publ) Methods and apparatuses for providing multiple radio access network connectivity to terminal device
US11240720B2 (en) * 2017-06-02 2022-02-01 FG Innovation Company Limited Methods, devices, and systems for service-driven mobility management

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014075210A1 (zh) * 2012-11-13 2014-05-22 华为技术有限公司 传输数据的方法、基站和用户设备
CN105122863A (zh) * 2013-01-18 2015-12-02 联发科技股份有限公司 小小区网络中rlm以及rlf机制的处理
CN104937985A (zh) * 2013-02-01 2015-09-23 联发科技股份有限公司 本地区域无线网中低开销移动性管理
US9538575B2 (en) * 2014-01-30 2017-01-03 Sharp Kabushiki Kaisha Systems and methods for dual-connectivity operation
CN104935414A (zh) * 2014-03-21 2015-09-23 上海贝尔股份有限公司 一种在双连接系统中传输信息的方法和装置
WO2017075824A1 (zh) * 2015-11-06 2017-05-11 广东欧珀移动通信有限公司 锚点更换的方法及设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "Discussion on Mobility Enhancement", 3GPP TSG RAN WG2 MEETING #95 R2-164766, 26 August 2016 (2016-08-26), Gothenburg, Sweden, XP051133623, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_95/Docs/> *
HUAWEI: "Simultaneous Data Transmission in Inter-eNB Handover", 3GPP TSG-RAN WG2 MEETING #94 R2-163657, 27 May 2016 (2016-05-27), Nanjing, XP051095366, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_94/Docs/> *

Also Published As

Publication number Publication date
US20190335369A1 (en) 2019-10-31
CN108282830A (zh) 2018-07-13
CN108282830B (zh) 2019-09-17

Similar Documents

Publication Publication Date Title
WO2018127243A1 (zh) 网络实体切换的方法、终端及网络实体设备
EP3610673B1 (en) Access node and methods for handovers in a dual connectivity communications system
WO2018127238A1 (zh) 信息处理方法及装置
US9999028B2 (en) Data transmission method, base station, and user equipment
WO2018171738A1 (zh) 切换的方法和设备
AU2017424739B2 (en) Switching method, access network device and terminal device
EP3499949B1 (en) Method, device and system for processing control signalling
JP2021527990A (ja) 移動通信システムで効率的なパケット重複送信のための方法及び装置
CN106134099A (zh) 用于在移动通信系统中使用多个载波来发送和接收数据的方法和设备
TW200935940A (en) Method for performing handover procedure and creating data
WO2018127219A1 (zh) 一种减少中断时延的方法、装置及用户设备
JP6643472B2 (ja) スプリット・ベアラを受信するユーザ装置からのフロー制御フィードバック
WO2018127220A1 (zh) 一种数据转发方法及装置
JP2017530644A (ja) データ同期処理方法及び装置
CN108282824A (zh) 一种状态更新方法、节点和用户终端
CN111585721B (zh) 一种实体建立的处理方法及装置
CN112449348A (zh) 通信方法和通信装置
TWI797414B (zh) 用於行動性增強之方法及其使用者設備
CN111918335B (zh) 处理数据包的方法和装置
WO2017133595A1 (zh) 数据处理的方法及装置
US10064237B2 (en) Communication apparatus, and layer 2 state control method
WO2020029445A1 (zh) 无线通信方法、通信设备、芯片和通信系统
KR20210023687A (ko) 이동 통신 시스템의 보안키 관리 방법 및 이를 위한 장치

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: 18736118

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 04.10.2109)

122 Ep: pct application non-entry in european phase

Ref document number: 18736118

Country of ref document: EP

Kind code of ref document: A1