WO2020035056A1 - 服务节点更新方法、终端设备和网络侧设备 - Google Patents

服务节点更新方法、终端设备和网络侧设备 Download PDF

Info

Publication number
WO2020035056A1
WO2020035056A1 PCT/CN2019/101020 CN2019101020W WO2020035056A1 WO 2020035056 A1 WO2020035056 A1 WO 2020035056A1 CN 2019101020 W CN2019101020 W CN 2019101020W WO 2020035056 A1 WO2020035056 A1 WO 2020035056A1
Authority
WO
WIPO (PCT)
Prior art keywords
source node
node
terminal device
pdcp
bearer
Prior art date
Application number
PCT/CN2019/101020
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 JP2021507805A priority Critical patent/JP7250114B2/ja
Priority to KR1020217007809A priority patent/KR102455840B1/ko
Priority to SG11202101545SA priority patent/SG11202101545SA/en
Priority to EP19850568.7A priority patent/EP3840468A4/en
Publication of WO2020035056A1 publication Critical patent/WO2020035056A1/zh
Priority to US17/174,140 priority patent/US11689969B2/en
Priority to US18/313,077 priority patent/US20230276308A1/en

Links

Images

Classifications

    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/026—Multicasting of data during hand-off
    • 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
    • H04W36/185—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection using make before break
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a method for updating a service node, a terminal device, and a network-side device.
  • terminal equipment also known as user equipment UE
  • DC Dual Connectivity
  • the purpose of the embodiments of the present disclosure is to provide a service node update method, a terminal device, and a network-side device to process the layer two protocol entity corresponding to the data radio bearer during the service node update process, so that the user plane data remains continuous during the service node update process. Without interruption.
  • a method for updating a service node is provided and executed by a terminal device.
  • the method includes:
  • the configuration information including first connection configuration information for maintaining a connection between a source node and a target node at the same time during a service node update process, and information for releasing a connection with the source node and connecting with the target node Second connection configuration information;
  • a method for updating a service node which is executed by a network-side device, wherein the network-side device includes a source node in a service node update process, and the method includes:
  • the configuration information including first connection configuration information used to maintain the connection between the source node and the target node at the same time during the service node update process, and information for releasing the connection with the source node and connecting with the target node
  • the second connection configuration information including first connection configuration information used to maintain the connection between the source node and the target node at the same time during the service node update process, and information for releasing the connection with the source node and connecting with the target node The second connection configuration information.
  • a method for updating a service node which is executed by a network-side device, wherein the network-side device includes a target node in a service node update process, and the method includes:
  • a terminal device includes:
  • a configuration message receiving module configured to receive configuration information, where the configuration information includes first connection configuration information for maintaining a connection between a source node and a target node at the same time during a service node update process, and for releasing a connection with the source node and Second connection configuration information connected to the target node;
  • a first reconfiguration module configured to apply the first connection configuration information to process a layer two protocol entity corresponding to a bearer between the terminal device and the source node, and reconfigure the bearer as a source node Separate bearing
  • a second reconfiguration module is configured to apply the second connection configuration information to process a layer two protocol entity corresponding to the bearer, and reconfigure the source node split bearer to a target node bearer.
  • a network-side device in a fifth aspect, includes a source node in a service node update process.
  • the network-side device includes:
  • a configuration information sending module configured to send configuration information, the configuration information includes first connection configuration information used to maintain a connection between a source node and a target node during a service node update process, and used to release a connection with the source node and Second connection configuration information connected with the target node.
  • a network-side device includes a target node in a service node update process.
  • the network-side device includes:
  • a first source node state transition message and a PDCP PDU receiving module configured to receive a first source node state transition message sent by a source node during a service node update process and a first PDCP PDU received from a source node separation bearer;
  • a sending status update module configured to update the sending status of the sending PDCP entity in the target node based on the first source node status transition message and the first PDCP PDU;
  • a second source node state transition message and a PDCP PDU receiving module configured to receive a second source node state transition message sent by the source node and a second PDCP PDU received from a target bearer;
  • the receiving status update module is configured to update the receiving status of the receiving PDCP entity in the target node based on the second source node status transition message and the second PDCP PDU.
  • a terminal device including: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the computer program is executed by the processor, the computer program is implemented as follows: Steps of the method described in the first aspect.
  • a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements the steps of the method according to the first aspect.
  • a network-side device including: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the computer program is implemented when the processor is executed by the processor. Steps of the method as described in the second aspect.
  • a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements the steps of the method according to the second aspect.
  • a network-side device including: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the computer program is executed by the processor, Implementing the steps of the method according to the third aspect.
  • a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements the steps of the method according to the third aspect.
  • the terminal device after receiving the configuration information, applies the first connection configuration information that is used to maintain the connection between the source node and the target node at the same time during the service node update process, and reloads the bearer between the terminal device and the source node.
  • the source node is configured to separate the bearer
  • the second connection configuration information for releasing the connection to the source node and connected to the target node is applied to reconfigure the source node separated bearer as the target node bearer.
  • the solution provided by the embodiment of the present disclosure uses the source node to separate the bearer, so that the terminal device does not need to disconnect the connection to the source node during the service node update, and only after successfully updating to the target node. Disconnect from the source node, so that continuous user interface data can be achieved without interruption.
  • FIG. 1 is a schematic flowchart of a service node update method performed by a terminal device according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a service node update method performed by a source node according to an embodiment of the present disclosure
  • FIG. 3 is another schematic flowchart of a service node update method performed by a source node according to an embodiment of the present disclosure
  • FIG. 4 is another schematic flowchart of a service node update method performed by a source node according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a service node update method performed by a target node according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of a downlink data link during a service node update process according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a uplink data link during a service node update process according to an embodiment of the present disclosure
  • FIG. 8 is a first schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 9 is a first schematic structural diagram of a network-side device according to an embodiment of the present disclosure.
  • FIG. 10 is a second schematic structural diagram of a network-side device according to an embodiment of the present disclosure.
  • FIG. 11 is a second schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 12 is a third schematic structural diagram of a network-side device according to an embodiment of the present disclosure.
  • GSM Global System for Mobile
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Advanced
  • NR New Radio
  • the terminal device can be a terminal device, such as a mobile phone (also called a "cellular" phone) and a computer with a terminal device.
  • a mobile phone also called a "cellular" phone
  • Radio access networks exchange languages and / or data.
  • the base station can be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or a base station (NodeB) in WCDMA, or an evolving base station (eNB or e-NodeB, evolutional Node B) in LTE, and
  • BTS Base Transceiver Station
  • NodeB base station
  • eNB evolved base station
  • gNB 5G base station
  • the terminal equipment adopts a single connection SC (Single Connectivity) architecture.
  • SC Single Connectivity
  • the terminal equipment moves from one cell (that is, the coverage area of the base station) to another cell, or the communication quality in the cell decreases due to external interference
  • the service node often needs to be replaced.
  • the terminal device needs to disconnect from the source node before it can establish a new connection with the target node. Therefore, this service node update method will cause data interruption on the user plane and affect the user experience.
  • terminal equipment also called user equipment UE uses a dual-connected DC (full name Dual Connectivity) architecture to improve wireless resource utilization, reduce system switching delay, and thereby improve user and system performance.
  • the dual-connected DC architecture includes two cell groups, namely the main cell group MCG (full name Cell Group) and the secondary cell group SCG (full name Secondary Cell Group), and the main cell group MCG corresponds to the network-side master node MN (full name Master Node), and the secondary cell group SCG corresponds to the secondary node SN (full name Secondary Node) on the network side.
  • the primary cell group MCG includes a primary cell PCell (full name Primary Cell) and a secondary cell SCell (full name Secondary Cell)
  • the secondary cell group SCG includes a primary and secondary cell PSCell (full name Primary Cell) and a secondary cell (Secondary Cell, SCell) ).
  • the primary cell PCell and the primary and secondary cells PSCell can also be collectively referred to as a special cell SpCell (the full name is Special Cell, which means the primary cell PCell in the primary cell group MCG or the secondary cell group SCG).
  • the update of the service node can be realized based on the multi-connection capability of the terminal device, so that during the update of the service node, the terminal device does not need to disconnect the connection with the source node, but disconnects after successfully updating to the target node Open the connection with the source node, so that the user plane data can be continuous without interruption.
  • the method for updating a service node provided in the embodiment of the present disclosure provides a processing method of a layer two protocol entity corresponding to a data radio bearer during the service node update process, so as to ensure continuous and uninterrupted user plane data.
  • an embodiment of the present disclosure provides a method for updating a service node, which is executed by a terminal device.
  • the method may include:
  • Step 101 Receive configuration information.
  • the service node update method provided in the embodiments of the present disclosure is applicable to a variety of scenarios that require service node update. For example, a handover of a serving node is performed, or a secondary node is replaced. Specifically, in a scenario where a serving node is handed over (Handover), the source node may be specifically a source base station, and the target node may be specifically a target base station. In the scenario of changing the secondary node (SN), the source node may be specifically the source secondary node SN, and the target node may be the target secondary node SN. It can be understood that the connection architecture of the terminal device before the service node update is different, and the network-side device that initiates the service node update may also be different.
  • the source node (which can be specifically the source base station) issues the configuration to the terminal device. information.
  • the configuration information may be delivered by the master node MN of the two nodes. If a signaling bearer SRB3 (full name Signal Resource Bearer 3) has been established between the secondary node SN and the terminal device in the two nodes, the secondary node SN can also directly send configuration information to the terminal device in order to replace the secondary device. Node (SN change).
  • SRB3 full name Signal Resource Bearer 3
  • the configuration information received by the terminal device may come from a source node that has established a connection with the terminal device, such as a source base station or a source auxiliary node SN, or may be from a master node MN in a multi-connection architecture.
  • the configuration information sent by the network-side device can be sent in the form of a radio resource control RRC (full name Radio Resource Control) message.
  • RRC full name Radio Resource Control
  • the configuration information received by the terminal device is also received in the form of an RRC message.
  • this configuration information can also be referred to as reconfiguration information.
  • the configuration process initiated by the configuration information can also be called a reconfiguration process.
  • the configuration information received by the terminal device in step 101 includes first connection configuration information and second connection configuration information, where the first connection configuration information is used to maintain the source node while the service node is being updated. It is connected to the target node, and the second connection configuration information is used to release the connection with the source node and connect with the target node.
  • first connection configuration information is used to maintain the source node while the service node is being updated. It is connected to the target node, and the second connection configuration information is used to release the connection with the source node and connect with the target node.
  • Step 103 Apply the first connection configuration information to process the layer two protocol entity corresponding to the bearer between the terminal device and the source node, and reconfigure the bearer as a source node separate bearer.
  • the terminal device After receiving the configuration information (also known as an RRC reconfiguration message) from the network-side device, the terminal device can apply the first connection configuration information to reconfigure the bearer between the terminal device and the source node (specifically, data
  • the radio bearer DRB is reconfigured as a source node separate bearer.
  • the terminal device can perform the following processing on the Layer 2 protocol entity corresponding to the bearer:
  • the terminal device assembles the packet data convergence protocol PDCP (full name Packet) carried in the cell group of the source node.
  • Data (Convergence Protocol) entity was reconfigured.
  • the reconfiguration of the PDCP entity may be to apply the separation bearer threshold carried in the first connection configuration information to the PDCP entity, so that the PDCP entity can determine whether to use the source node or the destination based on the separation bearer threshold in the source node separation bearer. Nodes send and receive data.
  • the terminal device controls the radio link control RLC (full name Radio Link Control) entity carried in the source node cell group and The medium access control MAC (full name Medium Access Control) entity in the source node cell group remains unchanged, so that the source node can normally send and receive data during the service node update process.
  • RLC full name Radio Link Control
  • MAC full name Medium Access Control
  • the terminal device In the above-mentioned process of reconfiguring the bearer between the terminal device and the source node based on the first connection configuration information, the terminal device also establishes the RLC entity in the target node cell group carried in the target node and the target node cell group MAC entity so that the target node can send and receive data during the service node update process.
  • the terminal device applies the first connection configuration information, the terminal device will maintain the connection between the source node and the target node during the service update process. Therefore, the first connection configuration information can be referred to as a dual connection configuration (DC configuration) information.
  • DC configuration dual connection configuration
  • Step 105 Apply the second connection configuration information to process the Layer 2 protocol entity corresponding to the bearer, and reconfigure the source node split bearer to the target node bearer.
  • the terminal device can further apply the second connection configuration information in the configuration information issued by the network-side device to reconfigure the source node to separate the bearer. Configured as the destination node bearer.
  • the terminal device can perform the following processing on the Layer 2 protocol entity corresponding to the bearer:
  • the MAC entity carried in the target node cell group remains unchanged.
  • the terminal device reconfigures the PDCP entity carried in the source node cell group of the source node to the target node's target
  • the PDCP entity in the node cell group enables the target node to send and receive data to and from the terminal device.
  • the terminal device also keeps the RLC entity and MAC entity carried in the target node cell group unchanged, so that it can perform normal operations with the target node. Data sending and receiving.
  • the terminal device releases the RLC entity and the MAC entity carried in the source node cell group while establishing a connection with the target node, thereby The connection between the terminal device and the source node can be completely released. At this point, the update of the service node is completed.
  • the specific process is different according to the type of the RLC entity. Specifically, if the RLC entity carried in the source node cell group is a long-term evolution LTE type RLC entity, the RLC entity is released after the RLC entity is rebuilt. Specifically, if the RLC entity carried in the source node cell group is a new air interface NR type RLC entity, the RLC entity can be released directly.
  • the terminal device applies the second connection configuration information, the terminal device will release the connection with the source node and connect with the target node. Therefore, the second connection configuration information can be referred to as single connection configuration (SC configuration) information. .
  • SC configuration single connection configuration
  • the terminal device performs step 103 and applies the first connection configuration information to reconfigure the bearer between the terminal device and the source node to separate the source node from the bearer, so that the terminal device can simultaneously maintain the source node during the service node update process.
  • the terminal device executes step 105 and applies the second connection configuration information to reconfigure the source node split bearer to the target node bearer, so that the terminal device can release the connection with the source node and only maintain the connection with the target node. Therefore, during the update of the service node, the terminal device does not need to disconnect the connection with the source node, and then disconnects the connection with the source node after successfully updating to the target node, thereby enabling continuous and uninterrupted user plane data.
  • the terminal device may further send instruction information to the source node, where the instruction information is used to indicate whether the terminal device has applied the first connection configuration information.
  • the source node after the source node receives the instruction information, it can know whether the terminal device has applied the first connection configuration information, and after the terminal device has applied the first connection configuration information, the bearer of the terminal device and the source node is reconfigured as the source. In the case where the node separates the bearer, it sends a second source node state transition message to the target node to notify the target node of the data receiving status of the source node and forward the data received from the source node separate bearer to the target node.
  • the indication information sent by the terminal device to the source node may be included in a PDCP sub-header.
  • the terminal device sends instruction information to the source node
  • the PDCP subheader of the data packet can send the instruction information to the source node.
  • the indication information in the PDCP subheader of the data packet may be reflected by using a preset indication bit in the current PDCP subheader.
  • the value of the preset indication bit in the subheader is "1", which indicates that the terminal device has applied the first connection configuration information; the value of the preset indication bit in the subheader is "0", which indicates that the terminal device has not applied the first connection configuration information. Connection configuration information.
  • the instruction information sent by the terminal device to the source node may be sent multiple times.
  • the terminal device may set the indication information in the PDCP subheader of the data packet, so that the indication information indicates The terminal device has applied the first connection configuration information; then, the terminal device may further send the instruction information to the source node to indicate that the terminal device has applied the first connection configuration information.
  • the second connection configuration information is applied to process the Layer 2 protocol entity corresponding to the bearer, and the source node separate bearer is reconfigured as the target.
  • the terminal device can also send a PDCP status report (PDCP status report) to the target node to inform the target node of the terminal device's status of receiving data.
  • PDCP status report PDCP status report
  • the terminal device sends a PDCP status report to the target node when the terminal device meets the trigger condition (the trigger condition here is specifically that the terminal device has applied the second connection configuration information and reconfigured the source node split bearer to the target node bearer).
  • the function is a function that can be configured through an RRC message. Therefore, the network-side device can configure this function in the RRC message sent to the terminal device.
  • the terminal device after receiving the configuration information, applies the first connection configuration information that is used to maintain the connection between the source node and the target node at the same time during the service node update process, and reloads the load between the terminal device and the source node
  • the source node is configured to separate the bearer
  • the second connection configuration information for releasing the connection to the source node and connected to the target node is applied to reconfigure the source node separated bearer as the target node bearer. Therefore, in the process of updating the service node, the solution provided by the embodiment of the present disclosure uses the source node to separate the bearer, so that the terminal device does not need to disconnect the connection to the source node during the service node update, and only after successfully updating to the target node. Disconnect from the source node, so that continuous user interface data can be achieved without interruption.
  • an embodiment of the present disclosure provides a service node update method, which is performed by a network-side device, where the network The side device includes the source node in the service node update process.
  • the method includes:
  • Step 201 Send configuration information.
  • the configuration information includes first connection configuration information used to maintain the connection between the source node and the target node during the service node update process, and second connection for releasing the connection to the source node and connecting to the target node. Configuration information.
  • the configuration information sent by the source node in performing step 201 corresponds to the configuration information received in step 101 by the terminal device in the embodiment shown in FIG. 1.
  • the description of the configuration information in the embodiment shown in FIG. 1 is applicable, and is not repeated here.
  • the terminal device After the terminal device applies the first connection configuration information, the terminal device will remain connected to the source node and the target node at the same time. Therefore, both the source node and the target node can receive and send data with the terminal device. Therefore, the source node needs to synchronize the data transmission and reception with the terminal device to the target node. Specifically, it may include a sending status of downlink data sent by the source node to the terminal device, and a receiving status of uplink data received from the terminal device.
  • the source node may initiate a source node status transfer (SN) status transfer process after sending the configuration information to the terminal device.
  • the source node may execute step 203 to send a first source node status transition (SN status transfer) message to the target node, so as to notify the target node of the data sending status of the source node.
  • the source node may also execute step 205 to send the PDCP service data unit SDU corresponding to the data forwarding (Data forwarding) process of the downlink data to the target node.
  • Data forwarding data forwarding
  • the source node may also execute step 207 to send the first PDCP protocol data unit PDU corresponding to the source node split bearer to the target node, where the first PDCP PDU is sent from the source node split bearer to the terminal device by the source node.
  • the source node before the source node sends a PDCP service data unit SDU corresponding to the Data Forwarding process to the target node, it can first establish a first tunnel between the source node and the target node. PDCP and SDU corresponding to the downlink data forwarding process.
  • a second channel (tunnel) between the source node and the target node may be established first, and this channel is used to carry the source Nodes separately carry the corresponding PDCP PDUs.
  • the PDCP SDU forwarded by the source node to the target node may include the original downlink data that the source node intends to send to the terminal device but has not yet processed, and may also include the source node that has sent to the terminal device but has not yet received the return The original downlink data of the received success message.
  • the first PDCP PDU forwarded by the source node to the target node includes downlink data sent by the source node from the source node to the terminal device.
  • the source node can synchronize the transmission of the downlink data from the source node to the terminal device to the target node, thereby ensuring the continuity of user plane data transmission during the service node update process. Meet the data service needs.
  • the source node may further perform step 209 to receive instruction information from the terminal device, where the instruction information is used to indicate whether the terminal device has applied the first connection configuration information.
  • the instruction information received by the source node corresponds to the instruction information sent by the terminal device. Therefore, the relevant description about the indication information in the embodiment shown in FIG. 1 is applicable, and is not repeated here.
  • the source node After the source node receives the instruction information, when the instruction information indicates that the terminal device has applied the first connection configuration information, it indicates that the terminal node has reconfigured the bearer between the terminal device and the source node as a source node separate bearer. Therefore, the terminal node You can send data to both the source and destination nodes.
  • the source node may perform step 211 and send the second node to the target node when the indication information indicates that the terminal device has applied the first connection configuration information.
  • the source node state transition message is used to notify the target node of the data receiving status of the source node.
  • Step 213 can also be performed to forward the data received from the source node's separate bearer to the target node (that is, the uplink data forwarding data performed by the source node). forwarding process).
  • the source node can synchronize the source node receiving uplink data from the terminal device to the target node by sending the above data and messages to the target node, thereby ensuring the continuity of user plane data transmission during the service node update process. Meet the data service needs.
  • the source node after the source node sends the configuration information to the terminal device, it can also send the PDCP reception status information of the terminal device to the target node, so as to inform the target node of the terminal device's reception of PDCP.
  • the source node needs to determine the PDCP reception status information of the terminal device before sending the PDCP reception status information of the terminal device to the target node.
  • the source node may determine the PDCP reception status information of the terminal device based on at least one of HARQ (Hybrid Automatic Repeat Request) information of the MAC layer and an RLC status report received by the RLC layer.
  • HARQ Hybrid Automatic Repeat Request
  • the PDCP receiving status information of the terminal device determined by the source node based on the HARQ information of the MAC layer and / or the RLC status report received by the RLC layer can reflect the situation of the PDCP receiving data of the terminal device to a certain extent.
  • Sending this PDCP receiving status information to the target node can help the target node understand the PDCP receiving data of the terminal device.
  • the source node sends configuration information to the terminal device, so that after receiving the configuration information, the terminal device can apply the first connection configuration information for maintaining the connection between the source node and the target node during the service node update process,
  • the bearer between the terminal device and the source node is reconfigured as a source node separated bearer, and then the second connection configuration information for releasing the connection to the source node and connected to the target node is applied to reconfigure the source node separated bearer as a target Node bearer.
  • the solution provided by the embodiment of the present disclosure uses the source node to separate the bearer, so that the terminal device does not need to disconnect the connection to the source node during the service node update, and after successfully updating to the target node, Disconnect from the source node, so that continuous user interface data can be achieved without interruption.
  • the source node will also initiate the RRC reconfiguration process to the terminal device and send the downstream data sent to the terminal device and the uplink data received from the terminal device to the target node to synchronize to the target node, thereby further ensuring that during the service node update process This improves the continuity of user plane data transmission and can meet the service requirements of business data.
  • an embodiment of the present disclosure also provides a service node update method, which is performed by a network-side device, where: The network-side device includes a target node in the service node update process.
  • the method includes:
  • Step 301 Receive a first source node state transition message sent by a source node during a service node update process and a first PDCP PDU received from a source node separation bearer.
  • the target node executes the first source node status transition (SN_status_transfer) message received from the source node in step 301, and in the embodiment shown in FIG. 2, the source node executes the first Corresponding to a source node state transition message, the target node executes the first PDCP PDU received in step 301 and received from the source node to separate the bearer from the source node, and the source node executes step 207 to the target in the embodiment shown in FIG. 2
  • the first PDCP PDU sent by the node corresponds. I won't repeat them here.
  • Step 303 Update the sending status of the sending PDCP entity in the target node based on the first source node state transition message and the first PDCP PDU.
  • the target node Based on the first source node state transition message and the first PDCP PDU sent by the source node, the target node can learn the situation where the source node sends data to the terminal device after initiating the RRC reconfiguration process. Therefore, the target node can The sending status of the sending PDCP entity is updated, so that the updated sending status can fully reflect the situation where the network-side device sends data to the terminal device.
  • Step 305 Receive a second source node state transition message sent by the source node and a second PDCP PDU received from the target bearer.
  • the target node executes the second source node status transition (SN status transfer) message received from the source node in step 305, and the second node sends the second node to the target node in step 211 in the embodiment shown in FIG. 2.
  • the source node status transition message corresponds, and is not repeated here.
  • Step 307 Update the receiving status of the receiving PDCP entity in the target node based on the second source node state transition message and the second PDCP PDU.
  • the target node can learn the situation where the source node receives data from the terminal device after initiating the RRC reconfiguration process. Therefore, the target node can receive the PDCP entity's The receiving status is updated, so that the updated receiving status can completely reflect the situation that the network-side device receives data from the terminal device.
  • the target node can also receive the PDCP reception status information of the terminal device sent by the source node, in order to understand the status of the terminal device receiving the network-side downlink data. It can be understood that the PDCP reception status information received by the target node corresponds to the PDCP reception status information sent by the source node. I won't repeat them here.
  • the target node can also receive the PDCP status report sent by the terminal device, so as to understand the situation in which the terminal device receives downlink data on the network side. It can be understood that the PDCP status report received by the target node corresponds to the PDCP status report sent by the terminal device, and is not repeated here.
  • the target node may further resend the data that the terminal device failed to receive to the terminal device based on at least one of the PDCP reception status information and the PDCP status report In order to achieve reliable transmission of user plane data.
  • the network-side device (only the source node at this time) sends data to the terminal device according to the data link shown in FIG. 6 (a). Send downlink data.
  • the terminal device After the source node sends configuration information to the terminal device, based on the first connection configuration information, the terminal device reconfigures the bearer between the terminal device and the source node to separate the source node from the bearer, and the terminal device will simultaneously maintain the source during the service node update process.
  • the node is connected to the target node. Therefore, the network-side equipment (including the source node and the destination node) will send downlink data to the terminal equipment according to the data link shown in Figure 6 (b).
  • the terminal device After the terminal device reconfigures the source node split bearer as the target node bearer based on the second connection configuration information, the terminal device will release the connection with the source node and connect with the target node. Therefore, the network-side device (only the target node at this time) will send downlink data to the terminal device according to the data link shown in FIG. 6 (c).
  • the network-side device (only the source node at this time) follows the data link shown in Figure 7 (a) from the terminal device. Receive upstream data.
  • the terminal device After the source node sends configuration information from the terminal device, the terminal device reconfigures the bearer between the terminal device and the source node to separate the source node from the bearer based on the first connection configuration information, and the terminal device will simultaneously maintain the source during the service node update process.
  • the node is connected to the target node. Therefore, the network-side equipment (including the source node and the destination node) will receive uplink data from the terminal equipment according to the data link shown in FIG. 7 (b).
  • the terminal device After the terminal device reconfigures the source node split bearer as the target node bearer based on the second connection configuration information, the terminal device will release the connection with the source node and connect with the target node. Therefore, the network-side device (only the target node at this time) will receive the uplink data from the terminal device according to the data link shown in FIG. 7 (c).
  • the source node sends configuration information to the terminal device, so that after receiving the configuration information, the terminal device can apply the first connection configuration information for maintaining the connection between the source node and the target node during the service node update process,
  • the bearer between the terminal device and the source node is reconfigured as a source node separated bearer, and then the second connection configuration information for releasing the connection to the source node and connected to the target node is applied to reconfigure the source node separated bearer as a target Node bearer.
  • the solution provided by the embodiment of the present disclosure uses the source node to separate the bearer, so that the terminal device does not need to disconnect the connection to the source node during the service node update, and after successfully updating to the target node, Disconnect from the source node, so that continuous user interface data can be achieved without interruption.
  • the source node will also initiate the RRC reconfiguration process to the terminal device and send the downstream data sent to the terminal device and the uplink data received from the terminal device to the target node to synchronize to the target node, thereby further ensuring that during the service node update process This improves the continuity of user plane data transmission and can meet the service requirements of business data.
  • an embodiment of the present disclosure further provides a terminal device capable of implementing the service node update method in the embodiment shown in FIG. 1.
  • the terminal equipment includes:
  • a configuration message receiving module 401 is configured to receive configuration information.
  • the configuration information includes first connection configuration information for maintaining a connection between a source node and a target node during a service node update process, and for releasing a connection with the source node and with the target node. Connected second connection configuration information;
  • a first reconfiguration module 403, configured to apply the first connection configuration information to process the layer two protocol entity corresponding to the bearer between the terminal device and the source node, and reconfigure the bearer as a source node separate bearer;
  • the second reconfiguration module 405 is configured to apply the second connection configuration information to process the Layer 2 protocol entity corresponding to the bearer, and reconfigure the source node split bearer to the target node bearer.
  • the first reconfiguration module 403 may specifically include:
  • a first reconfiguration unit configured to reconfigure a packet data convergence protocol PDCP entity carried in a source node cell group of a source node
  • a first holding unit configured to keep a radio link control RLC entity carried in a source node cell group unchanged
  • a second holding unit configured to keep a medium access control MAC entity carried in a source node cell group unchanged
  • a first establishing unit configured to establish an RLC entity in a target node cell group carried on the target node
  • the second establishing unit is configured to establish a MAC entity carried in the target node cell group.
  • the second reconfiguration module 405 may specifically include:
  • a second reconfiguration unit configured to reconfigure a PDCP entity carried in a source node cell group of a source node into a PDCP entity in a target node cell group of a target node;
  • a first release unit configured to release an RLC entity carried in a source node cell group
  • a second release unit configured to release the MAC entity carried in the source node cell group
  • a third holding unit configured to keep the RLC entity carried in the target node cell group unchanged
  • the fourth holding unit is configured to keep the MAC entity carried in the target node cell group unchanged.
  • the first release unit may specifically include at least one of the following:
  • Rebuilding release sub-unit for releasing the RLC entity if the RLC entity is a long-term evolution LTE type RLC entity
  • the direct release subunit is used to directly release the RLC entity if the RLC entity is a new air interface NR type RLC entity.
  • the terminal device may further include:
  • the instruction information sending module is configured to send instruction information to the source node, and the instruction information is used to indicate whether the terminal device has applied the first connection configuration information.
  • the foregoing instruction information sending module may be specifically configured to send instruction information to a source node through a PDCP subheader of a data packet.
  • the above instruction information sending module may specifically include:
  • An instruction information setting unit configured to set the instruction information in the PDCP subheader of the data packet after the first connection configuration information is applied to reconfigure the bearer between the terminal device and the source node to separate the source node from the bearer;
  • the instruction information sending unit is configured to send instruction information to the source node to indicate that the terminal device has applied the first connection configuration information.
  • the foregoing terminal device may further include:
  • the status report sending module is configured to send a PDCP status report to the target node.
  • the terminal device provided by the embodiment of the present disclosure can implement the service node update method in the foregoing embodiment shown in FIG. 1, and the relevant descriptions of the service node update method in the embodiment shown in FIG. 1 are applicable to this implementation. For example, we will not repeat them here.
  • an embodiment of the present disclosure further provides a network-side device that can implement the service node update method in the embodiment shown in FIG. 2.
  • the network-side device includes a source node during a service node update process.
  • the network-side equipment includes:
  • a configuration information sending module 501 is configured to send configuration information.
  • the configuration information includes first connection configuration information for maintaining a connection between a source node and a target node at the same time during a service node update process, and for releasing a connection with the source node and with the target node. Connected second connection configuration information.
  • the source node may further include:
  • a first source node state transition message sending module configured to send a first source node state transition message to a target node, and the first source node state transition message is used to notify the target node of a data transmission status of the source node;
  • the PDCP SDU forwarding module is used to send a PDCP service data unit SDU corresponding to the downlink data forwarding process to the target node;
  • the PDCP PDU sending module is configured to send the first PDCP protocol data unit PDU corresponding to the source node split bearer to the target node, and the first PDCP PDU is sent from the source node split bearer to the terminal device by the source node.
  • the source node may further include:
  • a first channel establishing module is configured to establish a first channel between a source node and a target node, and the first channel is used to carry a PDCP and SDU corresponding to a downlink data forwarding process.
  • the source node may further include:
  • a second channel establishment module is used to establish a second channel between the source node and the target node, and the second channel is used to carry the source node to separate the corresponding PDCP PDU.
  • the source node may further include:
  • the instruction information receiving module is configured to receive instruction information, and the instruction information is used to indicate whether the terminal device has applied the first connection configuration information.
  • the source node may further include:
  • a second source node state transition message sending module configured to send a second source node state transition message to a target node when the indication information indicates that the terminal device has applied the first connection configuration information
  • a receiving data forwarding module configured to forward data received from the source node detached bearer to the target node when the indication information indicates that the terminal device has applied the first connection configuration information, and a second source node state transition message is used to notify the target node Data receiving status of the source node.
  • the source node may further include:
  • the receiving status information sending module is configured to send PDCP receiving status information of the terminal device to the target node.
  • the source node may further include:
  • the receiving status information determining module is configured to determine the PDCP receiving status information of the terminal device based on at least one of HARQ information of the hybrid automatic repeat request at the MAC layer and an RLC status report received by the RLC layer.
  • the network-side device is a master node MN in a multi-connection architecture.
  • the network-side device provided in the embodiment of the present disclosure can implement the service node update method in the embodiment shown in FIG. 2 described above, and the relevant descriptions of the service node update method in the embodiment shown in FIG. 2 are applicable to this The embodiment is not repeated here.
  • an embodiment of the present disclosure further provides a network-side device that can implement the method for updating a service node in the embodiment shown in FIG. 5.
  • the network-side device includes a target node in a service node update process.
  • the network-side equipment includes:
  • a sending status update module 603, configured to update the sending status of the sending PDCP entity in the target node based on the first source node status transition message and the first PDCP PDU;
  • the receiving status update module 607 is configured to update the receiving status of the receiving PDCP entity in the target node based on the second source node status transition message and the second PDCP PDU.
  • the network-side device may further include at least one of the following:
  • a receiving status information receiving unit configured to receive PDCP receiving status information of a terminal device sent by a source node
  • the status report receiving unit is configured to receive a PDCP status report sent by the terminal device.
  • the network-side device may further include:
  • the data retransmission module is configured to resend the data that the terminal device did not successfully receive to the terminal device based on at least one of the PDCP reception status information and the PDCP status report.
  • the network-side device provided by the embodiment of the present disclosure can implement the service node update method in Embodiment 3 shown in FIG. 5 described above, and the relevant descriptions of the service node update method in the embodiment shown in FIG. 5 are applicable to this method. The embodiment is not repeated here.
  • FIG. 11 is another block diagram of a terminal device (also referred to as a mobile terminal) according to an embodiment of the present disclosure.
  • the terminal device 700 shown in FIG. 11 includes: at least one processor 701, a memory 702, at least one network interface 704, and a user interface 703.
  • the various components in the terminal device 700 are coupled together via a bus system 705.
  • the bus system 705 is configured to implement connection and communication between these components.
  • the bus system 705 includes a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are marked as the bus system 705 in FIG. 11.
  • the user interface 703 may include a display, a keyboard, or a pointing device (for example, a mouse, a trackball, a touch panel, or a touch screen).
  • a pointing device for example, a mouse, a trackball, a touch panel, or a touch screen.
  • the memory 702 in the embodiment of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM, DDRSDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synch link DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory 702 stores the following elements, executable modules or data structures, or a subset of them, or their extended set: an operating system 7021 and an application program 7022.
  • the operating system 7021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, etc., for implementing various basic services and processing hardware-based tasks.
  • the application program 7022 includes various application programs, such as a media player (Player), a browser (Browser), and the like, and is used to implement various application services.
  • a program for implementing the method of the embodiment of the present disclosure may be included in the application program 7022.
  • the terminal device 700 further includes a computer program stored in the memory 709 and executable on the processor 710.
  • the computer program is executed by the processor 701, the following steps are implemented:
  • the configuration information including first connection configuration information for maintaining a connection between a source node and a target node at the same time during a service node update process, and information for releasing a connection with the source node and connecting with the target node Second connection configuration information;
  • the method disclosed in the foregoing embodiments of the present disclosure may be applied to the processor 701, or implemented by the processor 701.
  • the processor 701 may be an integrated circuit chip and has a signal processing capability. In the implementation process, each step of the above method may be completed by using hardware integrated logic circuits or instructions in the form of software in the processor 701.
  • the above processor 701 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field, Programmable Gate Array, FPGA), or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present disclosure may be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present disclosure may be directly embodied as being executed by a hardware decoding processor, or may be executed and completed by using a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature computer-readable storage medium, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
  • the computer-readable storage medium is located in the memory 702, and the processor 701 reads the information in the memory 702 and completes the steps of the foregoing method in combination with its hardware.
  • a computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor 701, each step of the embodiment of the method for updating a service node is implemented.
  • the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSP), digital signal processing devices (DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general-purpose processor, controller, microcontroller, microprocessor, other for performing functions described in this disclosure Electronic unit or combination thereof.
  • ASICs application-specific integrated circuits
  • DSP digital signal processors
  • DSPD digital signal processing devices
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • controller microcontroller
  • microprocessor other for performing functions described in this disclosure Electronic unit or combination thereof.
  • the technology described in the embodiments of the present disclosure may be implemented by modules (such as procedures, functions, and the like) that perform the functions described in the embodiments of the present disclosure.
  • Software codes may be stored in a memory and executed by a processor.
  • the memory may be implemented in the processor or external to the processor.
  • an embodiment of the present disclosure further provides a terminal device, including a processor 701 and a memory 702, and a computer program stored on the memory 702 and executable on the processor 701, the computer program being executed by the processor 701
  • a terminal device including a processor 701 and a memory 702, and a computer program stored on the memory 702 and executable on the processor 701, the computer program being executed by the processor 701
  • FIG. 12 is a structural diagram of a network-side device applied in the embodiment of the present disclosure, which can implement the details of the service node update method in the embodiment shown in FIG. 2 and achieve the same effect.
  • the network-side device 2600 includes: a processor 2601, a transceiver 2602, a memory 2603, a user interface 2604, and a bus interface, of which:
  • the network-side device 2600 further includes: a computer program stored in the memory 2603 and executable on the processor 2601.
  • the computer program is processed ⁇ 2601 implements the following steps during execution:
  • the configuration information including first connection configuration information used to maintain the connection between the source node and the target node at the same time during the service node update process, and information for releasing the connection with the source node and connecting with the target node
  • the second connection configuration information including first connection configuration information used to maintain the connection between the source node and the target node at the same time during the service node update process, and information for releasing the connection with the source node and connecting with the target node The second connection configuration information.
  • the computer program is executed by the processor 2601 to implement the following steps:
  • the bus architecture may include any number of interconnected buses and bridges, and one or more processors specifically represented by the processor 2601 and various circuits of the memory represented by the memory 2603 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein.
  • the bus interface provides an interface.
  • the transceiver 2602 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.
  • the user interface 2604 may also be an interface capable of externally connecting internally required devices.
  • the connected devices include, but are not limited to, a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 2601 is responsible for managing the bus architecture and general processing, and the memory 2603 may store data used by the processor 2601 when performing operations.
  • An embodiment of the present disclosure further provides a computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
  • the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, also by hardware, but in many cases the former is better.
  • Implementation Based on this understanding, the technical solution of the present disclosure that is essentially or contributes to the existing technology can be embodied in the form of a software product that is stored in a storage medium (such as ROM / RAM, magnetic disk, The optical disc) includes several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of the present disclosure.
  • a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Abstract

本公开公开了一种服务节点更新方法，由终端设备执行，该方法包括：接收配置信息，配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与源节点的连接并与目标节点连接的第二连接配置信息；应用第一连接配置信息，对终端设备与源节点之间的承载所对应的层二协议实体进行处理，将承载重配置为源节点分离承载；应用第二连接配置信息，对承载所对应的层二协议实体进行处理，将源节点分离承载重配置为目标节点承载。

Description

服务节点更新方法、终端设备和网络侧设备
相关申请的交叉引用
本申请主张在2018年8月17日在中国提交的中国专利申请号No.201810942878.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信领域，尤其涉及一种服务节点更新方法、终端设备和网络侧设备。
背景技术
在相关移动通信系统中，当终端设备从一个小区(即基站的覆盖范围)移动到另一个小区，或者由于外界干扰导致在小区内通信质量下降时，为了保持终端设备的通信，往往需要更换服务节点。在更新服务节点时，终端设备需要先断开与源节点的连接，才能够与目标节点建立新的连接。因此，这种服务节点更新方式会产生用户面的数据中断，影响用户体验。
随着移动通信技术的发展，5G(5 Generation，第五代)移动通信系统应运而生。为提高无线资源利用率，降低系统切换时延，进而提高用户和系统性能，在5G系统中，终端设备(也可称为用户设备UE)可采用双连接DC(Dual Connectivity)架构，基于终端设备的多连接能力实现服务节点的更新，保证用户面数据的连续不中断,以满足低时延业务数据的服务需求。
因此，亟需提供一种服务节点更新方法，以处理服务节点更新过程中数据无线承载所对应的层二协议实体。
发明内容
本公开实施例的目的是提供服务节点更新方法、终端设备和网络侧设备，以处理服务节点更新过程中数据无线承载所对应的层二协议实体，使得用户面数据在服务节点更新过程中保持连续不中断。
第一方面，提供了一种服务节点更新的方法，由终端设备执行，该方法 包括：
接收配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息；
应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将所述承载重配置为源节点分离承载；
应用所述第二连接配置信息，对所述承载所对应的层二协议实体进行处理，将所述源节点分离承载重配置为目标节点承载。
第二方面，提供了一种服务节点更新方法，由网络侧设备执行，其中，所述网络侧设备包括服务节点更新过程中的源节点，该方法包括：
发送配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息。
第三方面，提供了一种服务节点更新方法，由网络侧设备执行，其中，所述网络侧设备包括服务节点更新过程中的目标节点，该方法包括：
接收服务节点更新过程中的源节点发送的第一源节点状态转换消息和从源节点分离承载接收的第一PDCP PDU；
基于所述第一源节点状态转换消息和所述第一PDCP PDU，更新所述目标节点中的发送PDCP实体的发送状态；
接收所述源节点发送的第二源节点状态转换消息和从目标承载接收的第二PDCP PDU；
基于所述第二源节点状态转换消息和所述第二PDCP PDU，更新所述目标节点中的接收PDCP实体的接收状态。
第四方面，提供了一种终端设备，该终端设备包括：
配置消息接收模块，用于接收配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息；
第一重配置模块，用于应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将所述承载重配置 为源节点分离承载；
第二重配置模块，用于应用所述第二连接配置信息，对所述承载所对应的层二协议实体进行处理，将所述源节点分离承载重配置为目标节点承载。
第五方面，提供了一种网络侧设备，该网络侧设备包括服务节点更新过程中的源节点，该网络侧设备包括：
配置信息发送模块，用于发送配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息。
第六方面，提供了一种网络侧设备，该网络侧设备包括服务节点更新过程中的目标节点，该网络侧设备包括：
第一源节点状态转换消息和PDCP PDU接收模块，用于接收服务节点更新过程中的源节点发送的第一源节点状态转换消息和从源节点分离承载接收的第一PDCP PDU；
发送状态更新模块，用于基于所述第一源节点状态转换消息和所述第一PDCP PDU，更新所述目标节点中的发送PDCP实体的发送状态；
第二源节点状态转换消息和PDCP PDU接收模块，用于接收所述源节点发送的第二源节点状态转换消息和从目标承载接收的第二PDCP PDU；
接收状态更新模块，用于基于所述第二源节点状态转换消息和所述第二PDCP PDU，更新所述目标节点中的接收PDCP实体的接收状态。
第七方面，提供了一种终端设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第一方面所述的方法的步骤。
第八方面，提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如第一方面所述的方法的步骤。
第九方面，提供了一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第二方面所述的方法的步骤。
第十方面，提供了一种计算机可读存储介质，所述计算机可读存储介质 上存储有计算机程序，所述计算机程序被处理器执行时实现如第二方面所述的方法的步骤。
第十一方面，提供了一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第三方面所述的方法的步骤。
第十二方面，提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如第三方面所述的方法的步骤。
在本公开实施例中，终端设备在接收到配置信息后，应用用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载，并应用用于释放与源节点的连接并与目标节点连接的第二连接配置信息，将源节点分离承载重配置为目标节点承载。因此，在服务节点更新过程中，本公开实施例提供的方案，利用源节点分离承载，实现了服务节点更新期间终端设备不需要断开与源节点的连接，而在成功更新到目标节点后再断开与源节点的连接，因而能够实现用户面数据的连续不中断。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本公开的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开实施例提供的由终端设备执行的服务节点更新方法的流程示意图；
图2是本公开实施例提供的由源节点执行的服务节点更新方法的流程示意图；
图3是本公开实施例提供的由源节点执行的服务节点更新方法的又一流程示意图；
图4是本公开实施例提供的由源节点执行的服务节点更新方法的再一流程示意图；
图5是本公开实施例提供的由目标节点执行的服务节点更新方法的流程示意图；
图6是本公开实施例服务节点更新过程中下行数据的链路示意图；
图7是本公开实施例服务节点更新过程中上行数据的链路示意图；
图8是本公开实施例提供的终端设备的结构示意图一；
图9是本公开实施例提供的网络侧设备的结构示意图一；
图10是本公开实施例提供的网络侧设备的结构示意图二；
图11是本公开实施例提供的终端设备的结构示意图二；
图12是本公开实施例提供的网络侧设备的结构示意图三。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开的技术方案，可以应用于各种通信系统，例如：全球移动通讯系统(GSM，Global System of Mobile communication)，码分多址(CDMA，Code Division Multiple Access)系统，宽带码分多址(WCDMA，Wideband Code Division Multiple Access)，通用分组无线业务(GPRS，General Packet Radio Service)，长期演进(LTE，Long Term Evolution)/增强长期演进(LTE-A，Long Term Evolution advanced)，NR(New Radio)等。
用户端(UE，User Equipment)，也可称之为终端设备(Mobile Terminal)、移动终端设备等，可以经无线接入网(例如，RAN，Radio Access Network)与一个或多个核心网进行通信，终端设备可以是终端设备，如移动电话(或称为“蜂窝”电话)和具有终端设备的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。
基站，可以是GSM或CDMA中的基站(BTS，Base Transceiver Station)，也可以是WCDMA中的基站(NodeB)，还可以是LTE中的演进型基站(eNB 或e-NodeB，evolutional Node B)及5G基站(gNB)，本公开并不限定，但为描述方便，下述实施例以gNB为例进行说明。
在相关移动通信系统中，终端设备采用单连接SC(Single Connectivity)架构，当终端设备从一个小区(即基站的覆盖范围)移动到另一个小区，或者由于外界干扰导致在小区内通信质量下降时，为了保持终端设备的通信，往往需要更换服务节点。在更新服务节点时，终端设备需要先断开与源节点的连接，才能够与目标节点建立新的连接。因此，这种服务节点更新方式会产生用户面的数据中断，影响用户体验。
在5G系统中，终端设备(也可称为用户设备UE)，采用了双连接DC(全称Dual Connectivity)架构，以提高无线资源利用率，降低系统切换时延，从而提高用户和系统性能。双连接DC架构中包括两个小区组，分别是主小区组MCG(全称Master Cell Group)和辅小区组SCG(全称Secondary Cell Group)，而主小区组MCG对应于网络侧的主节点MN(全称Master Node)，而辅小区组SCG对应于网络侧的辅节点SN(全称Secondary Node)。更进一步地，主小区组MCG包括主小区PCell(全称Primary Cell)和辅小区SCell(全称Secondary Cell)，辅小区组SCG包括主辅小区PSCell(全称Primary Secondary Cell)和辅小区(Secondary Cell，SCell)。其中主小区PCell和主辅小区PSCell也可统称为特殊小区SpCell(全称Special Cell，意指主小区组MCG或者辅小区组SCG中的主小区PCell)。
因此，在5G系统中，可以基于终端设备的多连接能力实现服务节点的更新，使得在服务节点更新期间，终端设备不需要断开与源节点的连接，而在成功更新到目标节点后再断开与源节点的连接，因而能够实现用户面数据的连续不中断。
为达到以上目的，本公开实施例提供的服务节点更新方法中，给出了服务节点更新过程中对数据无线承载所对应的层二协议实体的处理方式，以保证用户面数据的连续不中断。
以下结合附图，详细说明本公开各实施例提供的技术方案。
参见图1所示，本公开实施例提供了服务节点更新方法，由终端设备执行，该方法可包括：
步骤101：接收配置信息。
需要说明的是，本公开实施例所提供的服务节点更新方法，适用于多种需要进行服务节点更新的场景。例如，进行服务节点的切换(Handover)，或者更换辅节点(SN change)等。具体的，在进行服务节点的切换(Handover)这一场景下，源节点可具体为源基站，目标节点可具体为目标基站。在更换辅节点(SN change)这一场景下，源节点可具体为源辅节点SN，目标节点可具体为目标辅节点SN。可以理解到，终端设备在服务节点更新前的连接架构不同，发起服务节点更新的网络侧设备也可能有所不同。
例如，如果在进行服务节点更新之前，终端设备仅连接到一个服务节点(此时，可以理解为终端设备处于单连接架构)，则由源节点(可具体为源基站)向终端设备下发配置信息。
又例如，如果在进行服务节点更新之前，终端设备连接到两个节点(此时，可以理解为终端设备处于多连接架构)，则可以由两个节点中的主节点MN下发配置信息。如果两个节点中的辅节点SN与终端设备之间已经建立了信令承载三SRB3(全称Signal Resource Bearer 3)，则也可以由该辅节点SN直接向终端设备下发配置信息，以便更换辅节点(SN change)。
因此，相对应的，终端设备接收到的配置信息，可以来自于与终端设备建立了连接的源节点，例如源基站或者源辅节点SN，也可以来自于多连接架构下的主节点MN。
还需要说明的是，网络侧设备(具体为源节点或者多连接架构下的主节点MN)向终端设备发送的配置信息，可以以无线资源控制RRC(全称Radio Resource Control)消息的方式发送。相对应的，终端设备接收到的配置信息，也是以RRC消息的方式接收的。
能够理解，由于网络侧设备向终端设备发送的配置信息用于重配置终端设备的数据无线承载DRB(全称Data Radio Bearer)，因此，该配置信息也可称为重配置信息，网络侧设备通过发送配置信息发起的配置过程，也可称为重配置过程。
在本公开实施例中，终端设备执行步骤101接收到的配置信息中，包括第一连接配置信息和第二连接配置信息，其中，第一连接配置信息用于服务 节点更新过程中同时保持源节点和目标节点连接，第二连接配置信息用于释放与源节点的连接并与目标节点连接。以下将详细说明终端设备基于配置信息进行服务节点更新的具体过程。
步骤103：应用第一连接配置信息，对终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将承载重配置为源节点分离承载。
终端设备在接收到网络侧设备下发的配置信息(也可称为RRC重配置消息)后，可以应用第一连接配置信息进行重配置，将终端设备与源节点之间的承载(具体为数据无线承载DRB)重配置为源节点分离承载。在这一重配置过程中，终端设备对该承载所对应的层二协议实体可以进行以下处理：
重配置承载在源节点的源节点小区组中的分组数据汇聚协议PDCP实体；
保持承载在源节点小区组中的无线链路控制RLC实体不变；
保持承载在源节点小区组中的介质访问控制MAC实体不变；
建立承载在目标节点的目标节点小区组中的RLC实体；
建立承载在目标节点小区组中的MAC实体。
可以理解到，在上述基于第一连接配置信息对终端设备与源节点之间的承载进行重配置的过程中，终端设备对该承载在源节点的小区组中的分组数据汇聚协议PDCP(全称Packet Data Convergence Protocol)实体进行了重配置。可选的，对PDCP实体的重配置，可以是对PDCP实体应用第一连接配置信息中携带的分离承载阈值，使得PDCP实体在源节点分离承载中，可以基于分离承载阈值确定使用源节点还是目标节点进行数据收发。
在上述基于第一连接配置信息对终端设备与源节点之间的承载进行重配置的过程中，终端设备对该承载在源节点小区组中的无线链路控制RLC(全称Radio Link Control)实体和源节点小区组中的介质访问控制MAC(全称Medium Access Control)实体均保持不变，使得源节点在服务节点更新的过程中能够正常的收发数据。
在上述基于第一连接配置信息对终端设备与源节点之间的承载进行重配置的过程中，终端设备还建立了该承载在目标节点的目标节点小区组中的RLC实体以及在目标节点小区组中的MAC实体，以便目标节点可以在服务节点更新的过程中进行数据的收发。
需要说明的是，由于终端设备应用第一连接配置信息，将使得终端设备在服务更新过程中同时保持源节点和目标节点的连接，因此，可以将第一连接配置信息称为双连接配置(DC configuration)信息。
步骤105：应用第二连接配置信息，对承载所对应的层二协议实体进行处理，将源节点分离承载重配置为目标节点承载。
终端设备在将终端设备与源节点之间的承载重配置为源节点分离承载之后，可以进一步应用网络侧设备下发的配置信息中的第二连接配置信息进行重配置，将源节点分离承载重配置为目标节点承载。在这一重配置过程中，终端设备对该承载所对应的层二协议实体可以进行以下处理：
将承载在源节点的源节点小区组中的PDCP实体重配置成目标节点的目标节点小区组中的PDCP实体；
释放承载在源节点小区组中的RLC实体；
释放承载在源节点小区组中的MAC实体；
保持承载在目标节点小区组中的RLC实体不变；
保持承载在目标节点小区组中的MAC实体不变。
可以理解到，在上述基于第二连接配置信息将源节点分离承载重配置为目标节点承载的过程中，终端设备将承载在源节点的源节点小区组中的PDCP实体重配置成目标节点的目标节点小区组中的PDCP实体，使得目标节点可以与终端设备进行数据的收发。
在上述基于第二连接配置信息将源节点分离承载重配置为目标节点承载的过程中，终端设备还保持承载在目标节点小区组中的RLC实体和MAC实体不变，从而可以与目标节点进行正常的数据收发。
在上述基于第二连接配置信息将源节点分离承载重配置为目标节点承载的过程中，终端设备在与目标节点建立连接的同时，释放承载在源节点小区组中的RLC实体和MAC实体，从而可以完全释放终端设备与源节点的连接，至此，完成了服务节点的更新。
可选的，终端设备在释放承载在源节点小区组中的RLC实体时，根据RLC实体的类型的不同，具体的过程也有所不同。具体的，若承载在源节点小区组中的RLC实体为长期演进LTE类型的RLC实体，则在重建RLC实体 之后，再释放RLC实体。具体的，若承载在源节点小区组中的RLC实体为新空口NR类型的RLC实体，则可以直接释放RLC实体。
需要说明的是，由于终端设备应用第二连接配置信息，将使得终端设备释放与源节点的连接并与目标节点连接，因此，可以将第二连接配置信息称为单连接配置(SC configuration)信息。
可以理解到，终端设备执行步骤103，应用第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载，可以使得终端设备在服务节点更新过程中同时保持与源节点和目标节点连接。终端设备执行步骤105，应用第二连接配置信息，将源节点分离承载重配置为目标节点承载，可以使得终端设备释放与源节点的连接，而仅与目标节点保持连接。因此，在服务节点更新期间，终端设备不需要断开与源节点的连接，而在成功更新到目标节点后再断开与源节点的连接，因而能够实现用户面数据的连续不中断。
在本公开实施例中，终端设备还可以向源节点发送指示信息，该指示信息用于指示终端设备是否已应用第一连接配置信息。
对应的，源节点接收到该指示信息后，即可获知终端设备是否已应用第一连接配置信息，并在终端设备已应用第一连接配置信息，将终端设备与源节点的承载重配置为源节点分离承载的情况下，向目标节点发送第二源节点状态转换消息，用于向目标节点通知源节点的数据接收状态，并将从源节点分离承载接收到的数据转发至目标节点。
可选的，终端设备向源节点发送的指示信息，可以包含在PDCP子头(header)中。换言之，终端设备向源节点发送指示信息，可以通过数据包的PDCP子头向源节点发送指示信息。
可选的，在数据包的PDCP子头中的指示信息，可以使用目前PDCP子头中的预设指示位来反映。例如，子头中预设指示位的取值为“1”，表示终端设备已应用第一连接配置信息；子头中预设指示位的取值为“0”，表示终端设备尚未应用第一连接配置信息。
可以理解到，终端设备向源节点发送的指示信息，可以多次发送。可选的，在应用第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载之后，终端设备可以设置数据包的PDCP子头中的指示信息， 使得指示信息表示终端设备已应用第一连接配置信息；然后，终端设备可进一步向源节点发送该指示信息，以指示终端设备已应用第一连接配置信息。
可选的，在终端设备与源节点之间的承载为确定模式的承载时，在应用第二连接配置信息，对承载所对应的层二协议实体进行处理，将源节点分离承载重配置为目标节点承载之后，终端设备还可以向目标节点发送PDCP状态报告(PDCP status report)，以便告知目标节点终端设备接收数据的情况。
需要说明的是，终端设备在满足触发条件(此处的触发条件具体为终端设备已应用第二连接配置信息，将源节点分离承载重配置为目标节点承载)时向目标节点发送PDCP状态报告的功能，为可以通过RRC消息进行配置的功能。因此，网络侧设备可以在向终端设备发送的RRC消息中对这一功能进行配置。
在本公开实施例中，终端设备在接收到配置信息后，应用用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载，并应用用于释放与源节点的连接并与目标节点连接的第二连接配置信息，将源节点分离承载重配置为目标节点承载。因此，在服务节点更新过程中，本公开实施例提供的方案，利用源节点分离承载，实现了服务节点更新期间终端设备不需要断开与源节点的连接，而在成功更新到目标节点后再断开与源节点的连接，因而能够实现用户面数据的连续不中断。
参见2所示，与由终端设备执行的服务节点更新方法和目标节点执行的服务节点更新方法相对应的，本公开实施例提供了一种服务节点更新方法，由网络侧设备执行，其中，网络侧设备包括服务节点更新过程中的源节点。该方法包括：
步骤201：发送配置信息，配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与源节点的连接并与目标节点连接的第二连接配置信息。
可以理解到，源节点执行步骤201发送的配置信息，与图1所示的实施例中终端设备执行步骤101接收的配置信息相对应。图1所示的实施例中关于配置信息的阐述均适用，此处不再赘述。
可以理解到，在终端设备应用第一连接配置信息之后，终端设备将同时保持与源节点和目标节点连接，因此，源节点和目标节点均能够与终端设备进行数据的接收与发送。因此，源节点需要将与终端设备之间的数据收发情况同步到目标节点。具体的，可以包括源节点发送给终端设备的下行数据的发送状态，以及从终端设备接收到的上行数据的接收状态。
对于源节点发送给终端设备的下行数据，源节点可以在向终端设备发送配置信息之后，发起源节点状态转换(SN Status transfer)过程。在这一过程中，参见图3所示，源节点可以执行步骤203，向目标节点发送第一源节点状态转换(SN status transfer)消息，以便向目标节点通知源节点的数据发送状态。源节点还可以执行步骤205，向目标节点发送下行数据的数据转发(Data forwarding)过程对应的PDCP服务数据单元SDU。源节点还可以执行步骤207，向目标节点发送源节点分离承载对应的第一PDCP协议数据单元PDU，其中，第一PDCP PDU由源节点从源节点分离承载发送至终端设备。
在具体实施时，源节点在向目标节点发送下行数据转发(Data forwarding)过程对应的PDCP服务数据单元SDU之前，可以先建立源节点和目标节点之间的第一通道(tunnel)，该通道用于承载下行数据转发过程对应的PDCP SDU。
在具体实施时，源节点在向目标节点发送源节点分离承载对应的PDCP协议数据单元PDU之前，还可以先建立源节点和目标节点之间的第二通道(tunnel)，该通道用于承载源节点分离承载对应的PDCP PDU。
可以理解到，源节点向目标节点转发的PDCP SDU，可以包括源节点拟向终端设备发送、但尚未处理的原始下行数据，还可以包括源节点已向终端设备发送、但尚未接收到终端设备返回的接收成功消息的原始下行数据。源节点向目标节点转发的第一PDCP PDU，包括源节点从源节点分离承载发送至终端设备的下行数据。
能够理解，源节点通过向目标节点发送上述数据和消息，能够将源节点向终端设备发送下行数据的情况同步至目标节点，从而在服务节点更新的过程中保证了用户面数据传输的连续性，满足了数据的服务需求。
本公开实施例中，参见图4所示，源节点在发送配置信息之后，还可以执行步骤209，接收来自终端设备的指示信息，该指示信息用于指示终端设 备是否已应用第一连接配置信息。可以理解到，源节点接收到的指示信息，与终端设备发送的指示信息相对应。因此，图1所示的实施例中关于指示信息的相关阐述均适用，此处不再赘述。
源节点在接收到指示信息后，当指示信息指示终端设备已应用第一连接配置信息时，表示终端节点已经将终端设备与源节点之间的承载重配置为源节点分离承载，因此，终端节点既可以向源节点发送数据，也可以向目标节点发送数据。
因此，对于源节点从终端设备接收到的上行数据，参见图4所示，源节点可以在指示信息指示终端设备已应用第一连接配置信息的情况下，执行步骤211，向目标节点发送第二源节点状态转换消息，用于向目标节点通知源节点的数据接收状态，还可以执行步骤213，将从源节点分离承载接收到的数据转发至目标节点(也就是源节点执行的上行数据转发data forwarding过程)。
能够理解，源节点通过向目标节点发送上述数据和消息，能够将源节点从终端设备接收上行数据的情况同步至目标节点，从而在服务节点更新的过程中保证了用户面数据传输的连续性，满足了数据的服务需求。
可选的，源节点在向终端设备发送配置信息之后，还可以向目标节点发送终端设备的PDCP接收状态信息，以便将终端设备接收PDCP的情况告知目标节点。
需要说明的是，源节点在向目标节点发送终端设备的PDCP接收状态信息之前，需要先确定终端设备的PDCP接收状态信息。具体的，源节点可以基于MAC层的混合自动重传请求HARQ(Hybrid Automatic Repeat Request)信息以及RLC层接收到的RLC状态报告中至少一项，确定终端设备的PDCP接收状态信息。可以理解到，源节点基于MAC层的HARQ信息和/或RLC层接收到的RLC状态报告确定出的终端设备的PDCP接收状态信息，能在一定程度上反映终端设备的PDCP接收数据的情况，因此，将此PDCP接收状态信息发送到目标节点，能够帮助目标节点了解终端设备的PDCP接收数据的情况。
在本公开实施例中，源节点向终端设备发送配置信息，使得终端设备在 接收到配置信息后，能够应用用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载，再进而应用用于释放与源节点的连接并与目标节点连接的第二连接配置信息，将源节点分离承载重配置为目标节点承载。从而，在服务节点更新过程中，本公开实施例提供的方案，利用源节点分离承载，实现了服务节点更新期间终端设备不需要断开与源节点的连接，而在成功更新到目标节点后再断开与源节点的连接，因而能够实现用户面数据的连续不中断。
在此基础上，源节点还将向终端设备发起RRC重配置过程后发送至终端设备的下行数据以及从终端设备接收到的上行数据同步至目标节点，从而在服务节点更新的过程中，进一步保证了用户面数据传输的连续性，能够满足业务数据的服务需求。
参见图5所示，与由终端设备执行的服务节点更新方法和源节点执行的服务节点更新方法相对应的，本公开实施例还提供一种服务节点更新方法，由网络侧设备执行，其中，网络侧设备包括服务节点更新过程中的目标节点。该方法包括：
步骤301：接收服务节点更新过程中的源节点发送的第一源节点状态转换消息和从源节点分离承载接收的第一PDCP PDU。
能够理解，目标节点执行步骤301接收到的、来自于源节点的第一源节点状态转换(SN status transfer)消息，与图2所示的实施例中源节点执行步骤203向目标节点发送的第一源节点状态转换消息相对应，目标节点执行步骤301接收到的、来自于源节点从源节点分离承载接收的第一PDCP PDU，与图2所示的实施例中源节点执行步骤207向目标节点发送的第一PDCP PDU相对应。此处不再赘述。
步骤303：基于第一源节点状态转换消息和第一PDCP PDU，更新目标节点中的发送PDCP实体的发送状态。
基于源节点发送的第一源节点状态转换消息和第一PDCP PDU，目标节点能够获知源节点在发起RRC重配置过程以后向终端设备发送数据的情况，因此，目标节点可以据此对目标节点中发送PDCP实体的发送状态进行更新，使得更新后的发送状态能够完整反映网络侧设备向终端设备发送数据的情况。
步骤305：接收源节点发送的第二源节点状态转换消息和从目标承载接收的第二PDCP PDU。
能够理解，目标节点执行步骤305接收到的、来自源节点的第二源节点状态转换(SN status transfer)消息，与图2所示的实施例中源节点执行步骤211向目标节点发送的第二源节点状态转换消息相对应，此处不再赘述。
步骤307：基于第二源节点状态转换消息和第二PDCP PDU，更新目标节点中的接收PDCP实体的接收状态。
基于第二源节点状态转换消息和第二PDCP PDU，目标节点能够获知源节点在发起RRC重配置过程以后从终端设备接收数据的情况，因此，目标节点可以据此对目标节点中接收PDCP实体的接收状态进行更新，使得更新后的接收状态能够完整反映网络侧设备从终端设备接收数据的情况。
除此之外，目标节点还可以接收源节点发送来的终端设备的PDCP接收状态信息，以便了解终端设备接收网络侧下行数据的情况。可以理解到，目标节点接收到的PDCP接收状态信息，与源节点发送的PDCP接收状态信息相对应。此处不再赘述。
除此之外，目标节点还可以接收终端设备发送来的PDCP状态报告，以便了解终端设备接收网络侧下行数据的情况。可以理解到，目标节点接收到的PDCP状态报告，与终端设备发送的PDCP状态报告相对应，此处不再赘述。
在接收到PDCP接收状态信息和PDCP状态报告中至少一项的基础上，目标节点可以进一步基于PDCP接收状态信息和PDCP状态报告中至少一项，将终端设备未成功接收的数据重新发送至终端设备，以便实现用户面数据的可靠传输。
参见图6所示，在服务节点更新过程中，在源节点发起RRC重配置过程之前，网络侧设备(此时仅为源节点)按照图6(a)中所示的数据链路向终端设备发送下行数据。
在源节点向终端设备发送配置信息，终端设备基于第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载后，终端设备在服务节点更新过程中将同时保持源节点和目标节点连接。因此，网络侧设备(包 括源节点和目标节点)将按照图6(b)中所示的数据链路向终端设备发送下行数据。
在终端设备基于第二连接配置信息，将源节点分离承载重配置为目标节点承载后，终端设备将释放与源节点的连接，并与目标节点连接。因此，网络侧设备(此时仅为目标节点)将按照图6(c)中所示的数据链路向终端设备发送下行数据。
参见图7所示，在服务节点更新过程中，在源节点发起RRC重配置过程之前，网络侧设备(此时仅为源节点)按照图7(a)中所示的数据链路从终端设备接收上行数据。
在源节点从终端设备发送配置信息，终端设备基于第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载后，终端设备在服务节点更新过程中将同时保持源节点和目标节点连接。因此，网络侧设备(包括源节点和目标节点)将按照图7(b)中所示的数据链路从终端设备接收上行数据。
在终端设备基于第二连接配置信息，将源节点分离承载重配置为目标节点承载后，终端设备将释放与源节点的连接，并与目标节点连接。因此，网络侧设备(此时仅为目标节点)将按照图7(c)中所示的数据链路从终端设备接收上行数据。
在本公开实施例中，源节点向终端设备发送配置信息，使得终端设备在接收到配置信息后，能够应用用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载，再进而应用用于释放与源节点的连接并与目标节点连接的第二连接配置信息，将源节点分离承载重配置为目标节点承载。从而，在服务节点更新过程中，本公开实施例提供的方案，利用源节点分离承载，实现了服务节点更新期间终端设备不需要断开与源节点的连接，而在成功更新到目标节点后再断开与源节点的连接，因而能够实现用户面数据的连续不中断。
在此基础上，源节点还将向终端设备发起RRC重配置过程后发送至终端设备的下行数据以及从终端设备接收到的上行数据同步至目标节点，从而在服务节点更新的过程中，进一步保证了用户面数据传输的连续性，能够满足 业务数据的服务需求。
参见图8所示，与图1所示的实施例提供的服务节点更新方法相对应的，本公开实施例还提供一种终端设备，能够实现图1所示的实施例中的服务节点更新方法。该终端设备包括：
配置消息接收模块401，用于接收配置信息，配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与源节点的连接并与目标节点连接的第二连接配置信息；
第一重配置模块403，用于应用第一连接配置信息，对终端设备与源节点之间的承载所对应的层二协议实体进行处理，将承载重配置为源节点分离承载；
第二重配置模块405，用于应用第二连接配置信息，对承载所对应的层二协议实体进行处理，将源节点分离承载重配置为目标节点承载。
可选的，上述第一重配置模块403中，可具体包括：
第一重配置单元，用于重配置承载在源节点的源节点小区组中的分组数据汇聚协议PDCP实体；
第一保持单元，用于保持承载在源节点小区组中的无线链路控制RLC实体不变；
第二保持单元，用于保持承载在源节点小区组中的介质访问控制MAC实体不变；
第一建立单元，用于建立承载在目标节点的目标节点小区组中的RLC实体；
第二建立单元，用于建立承载在目标节点小区组中的MAC实体。
可选的，上述第二重配置模块405中，可具体包括：
第二重配置单元，用于将承载在源节点的源节点小区组中的PDCP实体重配置成目标节点的目标节点小区组中的PDCP实体；
第一释放单元，用于释放承载在源节点小区组中的RLC实体；
第二释放单元，用于释放承载在源节点小区组中的MAC实体；
第三保持单元，用于保持承载在目标节点小区组中的RLC实体不变；
第四保持单元，用于保持承载在目标节点小区组中的MAC实体不变。
可选的，上述第一释放单元，可具体包括以下至少一项：
重建释放子单元，用于若RLC实体为长期演进LTE类型的RLC实体，在重建RLC实体之后，释放RLC实体；
直接释放子单元，用于若RLC实体为新空口NR类型的RLC实体，直接释放RLC实体。
可选的，上述终端设备还可包括：
指示信息发送模块，用于向源节点发送指示信息，指示信息用于指示终端设备是否已应用第一连接配置信息。
可选的，上述指示信息发送模块，可具体用于通过数据包的PDCP子头向源节点发送指示信息。
可选的，上述指示信息发送模块，可具体包括：
指示信息设置单元，用于在应用第一连接配置信息，将终端设备与源节点之间的承载重配置为源节点分离承载之后，设置数据包的PDCP子头中的指示信息；
指示信息发送单元，用于向源节点发送指示信息，以指示终端设备已应用第一连接配置信息。
可选的，承载为确定模式的承载时，上述终端设备还可包括：
状态报告发送模块，用于向目标节点发送PDCP状态报告。
能够理解，本公开实施例提供的终端设备，能够实现前述图1所示的实施例中的服务节点更新方法，图1所示的实施例中关于服务节点更新方法的相关阐述均适用于本实施例，此处不再赘述。
参见图9所示，与图2所示实施例提供的服务节点更新方法相对应的，本公开实施例还提供一种网络侧设备，能够实现图2所示的实施例中的服务节点更新方法。其中，该网络侧设备包括服务节点更新过程中的源节点。该网络侧设备包括：
配置信息发送模块501，用于发送配置信息，配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与源节点的连接并与目标节点连接的第二连接配置信息。
可选的，上述源节点还可包括：
第一源节点状态转换消息发送模块，用于向目标节点发送第一源节点状态转换消息，第一源节点状态转换消息用于向目标节点通知源节点的数据发送状态；
PDCP SDU转发模块，用于向目标节点发送下行数据转发过程对应的PDCP服务数据单元SDU；
PDCP PDU发送模块，用于向目标节点发送源节点分离承载对应的第一PDCP协议数据单元PDU，第一PDCP PDU由源节点从源节点分离承载发送至终端设备。
可选的，上述源节点还可包括：
第一通道建立模块，用于建立源节点和目标节点之间的第一通道，该第一通道用于承载下行数据转发过程对应的PDCP SDU。
可选的，上述源节点还可包括：
第二通道建立模块，用于建立源节点和目标节点之间的第二通道，该第二通道用于承载源节点分离承载对应的PDCP PDU。
可选的，上述源节点还可包括：
指示信息接收模块，用于接收指示信息，指示信息用于指示终端设备是否已应用第一连接配置信息。
可选的，上述源节点还可包括：
第二源节点状态转换消息发送模块，用于当指示信息指示终端设备已应用第一连接配置信息时，向目标节点发送第二源节点状态转换消息；
接收数据转发模块，用于当指示信息指示终端设备已应用第一连接配置信息时，将从源节点分离承载接收到的数据转发至目标节点，第二源节点状态转换消息用于向目标节点通知源节点的数据接收状态。
可选的，上述源节点还可包括：
接收状态信息发送模块，用于向目标节点发送终端设备的PDCP接收状态信息。
可选的，上述源节点还可包括：
接收状态信息确定模块，用于基于MAC层的混合自动重传请求HARQ信息以及RLC层接收到的RLC状态报告中至少一项，确定终端设备的PDCP 接收状态信息。
可选的，上述网络侧设备中，网络侧设备为多连接架构下的主节点MN。
能够理解，本公开实施例提供的网络侧设备，能够实现前述图2所示的实施例中的服务节点更新方法，图2所示的实施例中关于服务节点更新方法的相关阐述均适用于本实施例，此处不再赘述。
参见图10所示，与图5所示实施例提供的服务节点更新方法相对应的，本公开实施例还提供一种网络侧设备，能够实现图5所示实施例中的服务节点更新方法。其中，该网络侧设备包括服务节点更新过程中的目标节点。该网络侧设备包括：
第一源节点状态转换消息和PDCP PDU接收模块601，用于接收服务节点更新过程中的源节点发送的第一源节点状态转换消息和从源节点分离承载接收的第一PDCP PDU；
发送状态更新模块603，用于基于第一源节点状态转换消息和第一PDCP PDU，更新目标节点中的发送PDCP实体的发送状态；
第二源节点状态转换消息和PDCP PDU接收模块605，用于接收源节点发送的第二源节点状态转换消息和从目标承载接收的第二PDCP PDU；
接收状态更新模块607，用于基于第二源节点状态转换消息和第二PDCP PDU，更新目标节点中的接收PDCP实体的接收状态。
可选的，上述网络侧设备还可包括以下至少一项：
接收状态信息接收单元，用于接收源节点发送来的终端设备的PDCP接收状态信息；
状态报告接收单元，用于接收终端设备发送来的PDCP状态报告。
可选的，上述网络侧设备还可包括：
数据重发模块，用于基于PDCP接收状态信息和PDCP状态报告中至少一项，将终端设备未成功接收的数据重新发送至终端设备。
能够理解，本公开实施例提供的网络侧设备，能够实现前述图5所示的实施例3中的服务节点更新方法，图5所示实施例中关于服务节点更新方法的相关阐述均适用于本实施例，此处不再赘述。
图11是本公开实施例的终端设备(又称为移动终端)的另一框图。图11 所示的终端设备700包括：至少一个处理器701、存储器702、至少一个网络接口704和用户接口703。终端设备700中的各个组件通过总线系统705耦合在一起。可理解，总线系统705用于实现这些组件之间的连接通信。总线系统705除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图11中将各种总线都标为总线系统705。
其中，用户接口703可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(trackball)、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器702可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本公开实施例描述的系统和方法的存储器702旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器702存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统7021和应用程序7022。
其中，操作系统7021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序7022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序 7022中。
在本公开实施例中，终端设备700还包括：存储在存储器上709并可在处理器710上运行的计算机程序，计算机程序被处理器701执行时实现如下步骤：
接收配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息；
应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将所述承载重配置为源节点分离承载；
应用所述第二连接配置信息，对所述承载所对应的层二协议实体进行处理，将所述源节点分离承载重配置为目标节点承载。
上述本公开实施例揭示的方法可以应用于处理器701中，或者由处理器701实现。处理器701可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器701中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器701可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的计算机可读存储介质中。该计算机可读存储介质位于存储器702，处理器701读取存储器702中的信息，结合其硬件完成上述方法的步骤。具体地，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器701执行时实现如上述服务节点更新方法实施例的各步骤。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固 件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
可选的，本公开实施例还提供一种终端设备，包括处理器701，存储器702，存储在存储器702上并可在所述处理器701上运行的计算机程序，该计算机程序被处理器701执行时实现上述服务节点更新方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
请参阅图12，图12是本公开实施例应用的网络侧设备的结构图，能够实现图2所示实施例中服务节点更新方法的细节，并达到相同的效果。如图12所示，网络侧设备2600包括：处理器2601、收发机2602、存储器2603、用户接口2604和总线接口，其中：
在本公开实施例中，网络侧设备2600还包括：存储在存储器上2603并可在处理器2601上运行的计算机程序，当网络侧设备包括服务节点更新过程中的源节点时，计算机程序被处理器2601、执行时实现如下步骤：
发送配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息。
当网络侧设备包括服务节点更新过程中的目标节点时，计算机程序被处理器2601、执行时实现如下步骤：
接收服务节点更新过程中的源节点发送的第一源节点状态转换消息和从源节点分离承载接收的第一PDCP PDU；
基于所述第一源节点状态转换消息和所述第一PDCP PDU，更新所述目标节点中的发送PDCP实体的发送状态；
接收所述源节点发送的第二源节点状态转换消息和从目标承载接收的第二PDCP PDU；
基于所述第二源节点状态转换消息和所述第二PDCP PDU，更新所述目标节点中的接收PDCP实体的接收状态。
在图12中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器2601代表的一个或多个处理器和存储器2603代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机2602可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的终端设备，用户接口2604还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器2601负责管理总线架构和通常的处理，存储器2603可以存储处理器2601在执行操作时所使用的数据。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述服务节点更新方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的 技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本公开各个实施例所述的方法。
上面结合附图对本公开的实施例进行了描述，但是本公开并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本公开的启示下，在不脱离本公开宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本公开的保护之内。

Claims (46)

  1. 一种服务节点更新方法，由终端设备执行，所述方法包括：
    接收配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息；
    应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将所述承载重配置为源节点分离承载；
    应用所述第二连接配置信息，对所述承载所对应的层二协议实体进行处理，将所述源节点分离承载重配置为目标节点承载。
  2. 根据权利要求1所述方法，其中，应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，包括：
    重配置所述承载在所述源节点的源节点小区组中的分组数据汇聚协议PDCP实体；
    保持所述承载在所述源节点小区组中的无线链路控制RLC实体不变；
    保持所述承载在所述源节点小区组中的介质访问控制MAC实体不变；
    建立所述承载在所述目标节点的目标节点小区组中的RLC实体；
    建立所述承载在所述目标节点小区组中的MAC实体。
  3. 根据权利要求1所述方法，其中，应用所述第二连接配置信息，对所述承载所对应的层二协议实体进行处理，包括：
    将所述承载在所述源节点的源节点小区组中的PDCP实体重配置成所述目标节点的目标节点小区组中的PDCP实体；
    释放所述承载在所述源节点小区组中的RLC实体；
    释放所述承载在所述源节点小区组中的MAC实体；
    保持所述承载在所述目标节点小区组中的RLC实体不变；
    保持所述承载在所述目标节点小区组中的MAC实体不变。
  4. 根据权利要求3所述方法，其中，释放所述承载在所述源节点小区组中的RLC实体，包括以下至少一项：
    若所述RLC实体为长期演进LTE类型的RLC实体，在重建所述RLC实 体之后，释放所述RLC实体；
    若所述RLC实体为新空口NR类型的RLC实体，直接释放所述RLC实体。
  5. 根据权利要求1～4之任一项所述方法，还包括：
    向所述源节点发送指示信息，所述指示信息用于指示所述终端设备是否已应用所述第一连接配置信息。
  6. 根据权利要求5所述方法，其中，向所述源节点发送指示信息，具体为：
    通过数据包的PDCP子头向所述源节点发送所述指示信息。
  7. 根据权利要求5所述方法，其中，向所述源节点发送指示信息，具体包括：
    在应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将所述承载重配置为源节点分离承载之后，设置数据包的PDCP子头中的指示信息；
    向所述源节点发送所述指示信息，以指示所述终端设备已应用所述第一连接配置信息。
  8. 根据权利要求1所述方法，其中，所述承载为确定模式的承载时，在应用所述第二连接配置信息，对所述承载所对应的层二协议实体进行处理，将所述源节点分离承载重配置为目标节点承载之后，所述方法还包括：
    向所述目标节点发送PDCP状态报告。
  9. 一种服务节点更新方法，由网络侧设备执行，其中，所述网络侧设备包括服务节点更新过程中的源节点，所述方法包括：
    发送配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息。
  10. 根据权利要求9所述方法，其中，在发送配置信息之后，所述方法还包括：
    所述源节点向所述目标节点发送以下至少一项：
    第一源节点状态转换消息，所述第一源节点状态转换消息用于向所述目 标节点通知所述源节点的数据发送状态；
    下行数据转发过程对应的PDCP服务数据单元SDU；
    源节点分离承载对应的第一PDCP协议数据单元PDU，所述第一PDCP PDU由所述源节点从所述源节点分离承载发送至终端设备。
  11. 根据权利要求10所述方法，其中，在所述源节点向所述目标节点发送所述下行数据转发过程对应的PDCP服务数据单元SDU之前，所述方法还包括：
    所述源节点建立源节点和目标节点之间的第一通道，所述第一通道用于承载所述下行数据转发过程对应的PDCP SDU。
  12. 根据权利要求10所述方法，其中，在所述源节点向所述目标节点发送所述源节点分离承载对应的PDCP协议数据单元PDU之前，所述方法还包括：
    所述源节点建立源节点和目标节点之间的第二通道，所述第二通道用于承载源节点分离承载对应的PDCP PDU。
  13. 根据权利要求9所述方法，其中，在发送配置信息之后，所述方法还包括：
    所述源节点接收指示信息，所述指示信息用于指示所述终端设备是否已应用所述第一连接配置信息。
  14. 根据权利要求13所述方法，其中，在所述源节点接收指示信息之后，所述方法还包括：
    当指示信息指示所述终端设备已应用所述第一连接配置信息时，所述源节点向所述目标节点发送第二源节点状态转换消息，并将从源节点分离承载接收到的数据转发至所述目标节点，所述第二源节点状态转换消息用于向所述目标节点通知所述源节点的数据接收状态。
  15. 根据权利要求9所述方法，其中，在发送配置信息之后，所述方法还包括：
    所述源节点向所述目标节点发送终端设备的PDCP接收状态信息。
  16. 根据权利要求15所述方法，其中，在所述源节点向所述目标节点发送终端设备的PDCP接收状态信息之前，所述方法还包括：
    所述源节点基于MAC层的混合自动重传请求HARQ信息以及RLC层接收到的RLC状态报告中至少一项，确定终端设备的所述PDCP接收状态信息。
  17. 根据权利要求9所述方法，其中，所述网络侧设备还包括多连接架构下的主节点MN。
  18. 一种服务节点更新方法，由网络侧设备执行，其中，所述网络侧设备包括服务节点更新过程中的目标节点，所述方法包括：
    接收服务节点更新过程中的源节点发送的第一源节点状态转换消息和从源节点分离承载接收的第一PDCP PDU；
    基于所述第一源节点状态转换消息和所述第一PDCP PDU，更新所述目标节点中的发送PDCP实体的发送状态；
    接收所述源节点发送的第二源节点状态转换消息和从目标承载接收的第二PDCP PDU；
    基于所述第二源节点状态转换消息和所述第二PDCP PDU，更新所述目标节点中的接收PDCP实体的接收状态。
  19. 根据权利要求18所述方法，其中，所述方法还包括以下至少一项：
    接收所述源节点发送来的终端设备的PDCP接收状态信息；
    接收终端设备发送来的PDCP状态报告。
  20. 根据权利要求19所述方法，还包括：
    基于所述PDCP接收状态信息和所述PDCP状态报告中至少一项，将所述终端设备未成功接收的数据重新发送至所述终端设备。
  21. 一种终端设备，包括：
    配置消息接收模块，用于接收配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息；
    第一重配置模块，用于应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将所述承载重配置为源节点分离承载；
    第二重配置模块，用于应用所述第二连接配置信息，对所述承载所对应的层二协议实体进行处理，将所述源节点分离承载重配置为目标节点承载。
  22. 根据权利要求21所述终端设备，其中，所述第一重配置模块中，包括：
    第一重配置单元，用于重配置所述承载在所述源节点的源节点小区组中的分组数据汇聚协议PDCP实体；
    第一保持单元，用于保持所述承载在所述源节点小区组中的无线链路控制RLC实体不变；
    第二保持单元，用于保持所述承载在所述源节点小区组中的介质访问控制MAC实体不变；
    第一建立单元，用于建立所述承载在所述目标节点的目标节点小区组中的RLC实体；
    第二建立单元，用于建立所述承载在所述目标节点小区组中的MAC实体。
  23. 根据权利要求21所述终端设备，其中，所述第二重配置模块，包括：
    第二重配置单元，用于将所述承载在所述源节点的源节点小区组中的PDCP实体重配置成所述目标节点的目标节点小区组中的PDCP实体；
    第一释放单元，用于释放所述承载在所述源节点小区组中的RLC实体；
    第二释放单元，用于释放所述承载在所述源节点小区组中的MAC实体；
    第三保持单元，用于保持所述承载在所述目标节点小区组中的RLC实体不变；
    第四保持单元，用于保持所述承载在所述目标节点小区组中的MAC实体不变。
  24. 根据权利要求23所述终端设备，其中，所述第一释放单元，包括以下至少一项：
    重建释放子单元，用于若所述RLC实体为长期演进LTE类型的RLC实体，在重建所述RLC实体之后，释放所述RLC实体；
    直接释放子单元，用于若所述RLC实体为新空口NR类型的RLC实体，直接释放所述RLC实体。
  25. 根据权利要求21～24之任一项所述终端设备，其中，所述终端设备还包括：
    指示信息发送模块，用于向所述源节点发送指示信息，所述指示信息用于指示所述终端设备是否已应用所述第一连接配置信息。
  26. 根据权利要求25所述终端设备，其中，所述指示信息发送模块，具体用于：
    通过数据包的PDCP子头向所述源节点发送所述指示信息。
  27. 根据权利要求25所述终端设备，其中，所述指示信息发送模块，具体包括：
    指示信息设置单元，用于在应用所述第一连接配置信息，对所述终端设备与所述源节点之间的承载所对应的层二协议实体进行处理，将所述承载重配置为源节点分离承载之后，设置数据包的PDCP子头中的指示信息；
    指示信息发送单元，用于向所述源节点发送所述指示信息，以指示所述终端设备已应用所述第一连接配置信息。
  28. 根据权利要求21所述终端设备，其中，所述承载为确定模式的承载时，所述终端设备还包括：
    状态报告发送模块，用于向所述目标节点发送PDCP状态报告。
  29. 一种网络侧设备，所述网络侧设备包括服务节点更新过程中的源节点，所述网络侧设备包括：
    配置信息发送模块，用于发送配置信息，所述配置信息包括用于服务节点更新过程中同时保持源节点和目标节点连接的第一连接配置信息，以及用于释放与所述源节点的连接并与所述目标节点连接的第二连接配置信息。
  30. 根据权利要求29所述网络侧设备，其中，所述源节点还包括：
    第一源节点状态转换消息发送模块，用于向所述目标节点发送第一源节点状态转换消息，所述第一源节点状态转换消息用于向所述目标节点通知所述源节点的数据发送状态；
    PDCP SDU转发模块，用于向所述目标节点发送下行数据转发过程对应的PDCP服务数据单元SDU；
    PDCP PDU发送模块，用于向所述目标节点发送源节点分离承载对应的第一PDCP协议数据单元PDU，所述第一PDCP PDU由所述源节点从所述源节点分离承载发送至终端设备。
  31. 根据权利要求30所述网络侧设备，其中，所述源节点还包括：
    第一通道建立模块，用于建立源节点和目标节点之间的第一通道，所述第一通道用于承载下行数据转发过程对应的PDCP SDU。
  32. 根据权利要求30所述网络侧设备，其中，所述源节点还包括：
    第二通道建立模块，用于建立源节点和目标节点之间的第二通道，所述第二通道用于承载源节点分离承载对应的PDCP PDU。
  33. 根据权利要求29所述网络侧设备，其中，所述源节点还包括：
    指示信息接收模块，用于接收指示信息，所述指示信息用于指示所述终端设备是否已应用所述第一连接配置信息。
  34. 根据权利要求33所述网络侧设备，其中，所述源节点还包括：
    第二源节点状态转换消息发送模块，用于当指示信息指示所述终端设备已应用所述第一连接配置信息时，向所述目标节点发送第二源节点状态转换消息；
    接收数据转发模块，用于当指示信息指示所述终端设备已应用所述第一连接配置信息时，将从源节点分离承载接收到的数据转发至所述目标节点，所述第二源节点状态转换消息用于向所述目标节点通知所述源节点的数据接收状态。
  35. 根据权利要求29所述网络侧设备，其中，所述源节点还包括：
    接收状态信息发送模块，用于向所述目标节点发送终端设备的PDCP接收状态信息。
  36. 根据权利要求35所述网络侧设备，其中，所述源节点还包括：
    接收状态信息确定模块，用于基于MAC层的混合自动重传请求HARQ信息以及RLC层接收到的RLC状态报告中至少一项，确定终端设备的所述PDCP接收状态信息。
  37. 根据权利要求29所述网络侧设备，其中，所述网络侧设备还包括多连接架构下的主节点MN。
  38. 一种网络侧设备，所述网络侧设备包括服务节点更新过程中的目标节点，所述网络侧设备包括：
    第一源节点状态转换消息和PDCP PDU接收模块，用于接收服务节点更 新过程中的源节点发送的第一源节点状态转换消息和从源节点分离承载接收的第一PDCP PDU；
    发送状态更新模块，用于基于所述第一源节点状态转换消息和所述第一PDCP PDU，更新所述目标节点中的发送PDCP实体的发送状态；
    第二源节点状态转换消息和PDCP PDU接收模块，用于接收所述源节点发送的第二源节点状态转换消息和从目标承载接收的第二PDCP PDU；
    接收状态更新模块，用于基于所述第二源节点状态转换消息和所述第二PDCP PDU，更新所述目标节点中的接收PDCP实体的接收状态。
  39. 根据权利要求38所述网络侧设备，其中，所述网络侧设备还包括以下至少一项：
    接收状态信息接收单元，用于接收所述源节点发送来的终端设备的PDCP接收状态信息；
    状态报告接收单元，用于接收终端设备发送来的PDCP状态报告。
  40. 根据权利要求39所述网络侧设备，其中，所述网络侧设备还包括：
    数据重发模块，用于基于所述PDCP接收状态信息和所述PDCP状态报告中至少一项，将所述终端设备未成功接收的数据重新发送至所述终端设备。
  41. 一种终端设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至8中任一项所述的方法的步骤。
  42. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至8中任一项所述的方法的步骤。
  43. 一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求9至17中任一项所述的方法的步骤。
  44. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求9至17中任一项所述的方法的步骤。
  45. 一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并 可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求18至20中任一项所述的方法的步骤。
  46. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求18至20中任一项所述的方法的步骤。
PCT/CN2019/101020 2018-08-17 2019-08-16 服务节点更新方法、终端设备和网络侧设备 WO2020035056A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2021507805A JP7250114B2 (ja) 2018-08-17 2019-08-16 サービスノードの更新方法、端末機器、および、ネットワーク側機器
KR1020217007809A KR102455840B1 (ko) 2018-08-17 2019-08-16 서빙 노드 업데이트 방법, 단말기와 네트워크 장치
SG11202101545SA SG11202101545SA (en) 2018-08-17 2019-08-16 Service node updating method, terminal device, and network-side device
EP19850568.7A EP3840468A4 (en) 2018-08-17 2019-08-16 UPDATE PROCESS FOR SERVICE NODES, TERMINAL DEVICE AND NETWORK DEVICE
US17/174,140 US11689969B2 (en) 2018-08-17 2021-02-11 Service node updating method, terminal device, and network-side device
US18/313,077 US20230276308A1 (en) 2018-08-17 2023-05-05 Service node updating method, terminal device, and network-side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810942878.5 2018-08-17
CN201810942878.5A CN110839267B (zh) 2018-08-17 2018-08-17 服务节点更新方法、终端设备和网络侧设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/174,140 Continuation US11689969B2 (en) 2018-08-17 2021-02-11 Service node updating method, terminal device, and network-side device

Publications (1)

Publication Number Publication Date
WO2020035056A1 true WO2020035056A1 (zh) 2020-02-20

Family

ID=69525193

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/101020 WO2020035056A1 (zh) 2018-08-17 2019-08-16 服务节点更新方法、终端设备和网络侧设备

Country Status (7)

Country Link
US (2) US11689969B2 (zh)
EP (1) EP3840468A4 (zh)
JP (1) JP7250114B2 (zh)
KR (1) KR102455840B1 (zh)
CN (1) CN110839267B (zh)
SG (1) SG11202101545SA (zh)
WO (1) WO2020035056A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4181600A4 (en) * 2020-07-31 2024-01-17 Huawei Tech Co Ltd LOGIC CHANNEL (LCH) CONFIGURATION METHOD, COMMUNICATION DEVICE AND COMMUNICATION SYSTEM

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747422B (zh) * 2020-05-27 2024-02-02 中国联合网络通信集团有限公司 网络服务切换方法、装置、设备以及存储介质
CN114449602B (zh) * 2022-01-27 2024-02-06 深圳Tcl新技术有限公司 切换方法、存储介质及无线通信装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统
CN106162774A (zh) * 2015-04-09 2016-11-23 中兴通讯股份有限公司 跨MeNB切换方法、装置及基站
CN107113677A (zh) * 2014-12-17 2017-08-29 高通股份有限公司 使用双活动连接的切换
WO2018113410A1 (zh) * 2016-12-20 2018-06-28 中兴通讯股份有限公司 一种无线链路管理的方法及装置、系统、存储介质
CN108282824A (zh) * 2017-01-05 2018-07-13 电信科学技术研究院 一种状态更新方法、节点和用户终端

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103582054B (zh) * 2012-07-27 2017-08-11 电信科学技术研究院 一种进行切换的方法和装置
JP6445032B2 (ja) 2013-11-01 2018-12-26 サムスン エレクトロニクス カンパニー リミテッド ベアラを再構成する方法及び装置
EP3304974B1 (en) * 2015-05-29 2022-03-23 Apple Inc. Seamless mobility for 5g and lte systems and devices
KR101954495B1 (ko) * 2015-09-23 2019-03-07 주식회사 케이티 단말의 이동성 제어 방법 및 그 장치
KR102420991B1 (ko) * 2016-08-09 2022-07-14 삼성전자주식회사 무선통신 시스템에서 사용자 평면 동작을 관리하기 위한 방법 및 장치
US10750410B2 (en) 2016-09-30 2020-08-18 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
CN108307538B (zh) * 2016-09-30 2023-05-02 夏普株式会社 用于建立/重配置数据承载的方法和设备
KR102324214B1 (ko) * 2017-01-06 2021-11-12 삼성전자 주식회사 차세대 이동 통신 시스템에서 이중 접속의 데이터 처리를 가속화하는 방법 및 장치
WO2018144758A1 (en) * 2017-02-02 2018-08-09 Intel IP Corporation Generation node-b (gnb), user equipment (ue) and methods for handover based on multi-connectivity in new radio (nr) systems
KR20180090658A (ko) * 2017-02-03 2018-08-13 삼성전자주식회사 이동통신 시스템에서 다중 연결을 사용한 핸드오버 시 보안 키를 처리하는 방법 및 장치
EP3577928B1 (en) * 2017-02-03 2021-03-31 Telefonaktiebolaget LM Ericsson (publ) Handover with zero ms user plane interruption
US10292081B2 (en) * 2017-02-03 2019-05-14 Lg Electronics Inc. Method and apparatus for performing partial handover for continuous data transmission in wireless communication system
US11546815B2 (en) * 2017-03-22 2023-01-03 Idac Holdings, Inc. System and methods for phased reconfiguration in wireless systems
CN108924876A (zh) * 2017-03-24 2018-11-30 华为技术有限公司 数据传输方法、接入网设备、终端及通信系统
WO2018203702A1 (en) * 2017-05-05 2018-11-08 Samsung Electronics Co., Ltd. Method and apparatus for coordination of rrc configurations between interworking nodes in dual connectivity
US10448289B2 (en) * 2017-05-05 2019-10-15 Futurewei Technologies, Inc. System and method for handovers in a dual connectivity communications system
WO2018203300A1 (en) * 2017-05-05 2018-11-08 Telefonaktiebolaget Lm Ericsson (Publ) Split signalling radio bearer in handover
US20200084682A1 (en) * 2017-05-05 2020-03-12 Samsung Electronics Co., Ltd System, data transmission method and network equipment supporting pdcp duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment
US10805836B2 (en) * 2017-05-05 2020-10-13 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (PDCP) entity
WO2018230027A1 (ja) * 2017-06-15 2018-12-20 日本電気株式会社 無線アクセスネットワークノード及び無線端末並びにこれらの方法
US20200196374A1 (en) * 2017-06-16 2020-06-18 Intel Corporation L2 handling for bearer type change
CN109863731B (zh) * 2017-08-03 2020-11-10 华为技术有限公司 数据传输方法、相关设备及通信系统
US11147002B2 (en) * 2017-08-11 2021-10-12 Huawei Technologies Co., Ltd. Data transmission method and related device
US11323923B2 (en) * 2017-08-21 2022-05-03 Samsung Electronics Co., Ltd. Method and system for communication in wireless communication network
CN111194535B (zh) * 2017-10-09 2023-06-06 瑞典爱立信有限公司 主节点、辅助节点以及在其中执行的方法
WO2019095088A1 (zh) * 2017-11-14 2019-05-23 华为技术有限公司 一种切换的方法以及设备
US11071025B2 (en) * 2018-06-29 2021-07-20 FG Innovation Company Limited Cell handover with minimum mobility interruption
US11044632B2 (en) * 2019-05-13 2021-06-22 Qualcomm Incorporated Header compression handling during handover
KR20220102002A (ko) * 2021-01-12 2022-07-19 삼성전자주식회사 무선 통신 시스템에서 이중 접속을 수행하는 방법 및 장치
KR20220103514A (ko) * 2021-01-15 2022-07-22 한국전자통신연구원 고속 열차 환경에서의 통신 방법 및 장치
KR20220135595A (ko) * 2021-03-30 2022-10-07 삼성전자주식회사 무선 통신 시스템에서 서비스를 제공하는 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107113677A (zh) * 2014-12-17 2017-08-29 高通股份有限公司 使用双活动连接的切换
CN106162774A (zh) * 2015-04-09 2016-11-23 中兴通讯股份有限公司 跨MeNB切换方法、装置及基站
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统
WO2018113410A1 (zh) * 2016-12-20 2018-06-28 中兴通讯股份有限公司 一种无线链路管理的方法及装置、系统、存储介质
CN108282824A (zh) * 2017-01-05 2018-07-13 电信科学技术研究院 一种状态更新方法、节点和用户终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Centralised User Plane-Dual Connectivity", 3GPP TSG-RAN WG3 MEETING #99 R3-181267, 2 March 2018 (2018-03-02), XP051401714 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4181600A4 (en) * 2020-07-31 2024-01-17 Huawei Tech Co Ltd LOGIC CHANNEL (LCH) CONFIGURATION METHOD, COMMUNICATION DEVICE AND COMMUNICATION SYSTEM

Also Published As

Publication number Publication date
SG11202101545SA (en) 2021-03-30
US20210168668A1 (en) 2021-06-03
EP3840468A4 (en) 2021-11-10
US11689969B2 (en) 2023-06-27
KR102455840B1 (ko) 2022-10-17
CN110839267A (zh) 2020-02-25
JP2021533703A (ja) 2021-12-02
US20230276308A1 (en) 2023-08-31
CN110839267B (zh) 2022-01-28
KR20210044844A (ko) 2021-04-23
JP7250114B2 (ja) 2023-03-31
EP3840468A1 (en) 2021-06-23

Similar Documents

Publication Publication Date Title
US11076334B2 (en) Data forwarding method, device, and communications system
US11184811B2 (en) Method and device for anchor replacement
CN113766591B (zh) 一种接入控制方法、终端设备、基站及存储介质
US11310711B2 (en) Radio resource control RRC configuration method and related device
US11689969B2 (en) Service node updating method, terminal device, and network-side device
WO2020146991A1 (zh) 一种数据流处理方法、设备及存储介质
JP2019050587A (ja) 複数の同時無線アクセス技術によるデータ伝送のためのモバイル端末および方法
JP7035082B2 (ja) ユーザプレーンリンク確立方法、基地局、およびモビリティ管理デバイス
WO2020001257A1 (zh) 一种数据传输方法及装置
EP3664507A1 (en) Communication method, base station, terminal device and system
WO2022073491A1 (zh) 切换方法、装置、终端设备、网络设备及存储介质
US20230171823A1 (en) Information transmission method, network device and terminal
WO2021068199A1 (zh) 一种切换处理方法、网络设备
US20230199600A1 (en) Method and communications apparatus for configuring assistance information
WO2021249477A1 (zh) 切换多播业务的方法及设备
JP2018174597A (ja) ベアラ管理装置、方法及び通信システム
WO2023061339A1 (zh) 一种数据传输方法及通信装置
WO2024000110A1 (zh) 一种小区切换方法及装置、终端设备、网络设备
WO2023213299A1 (zh) 数据传输处理方法及装置
WO2022148205A1 (zh) 多连接下的切换方法和装置
WO2021051384A1 (zh) 一种切换处理方法、网络设备
WO2020124540A1 (zh) 一种数据包重排序方法、电子设备及存储介质
WO2020107340A1 (zh) 一种数据处理方法、设备及存储介质

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021507805

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217007809

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019850568

Country of ref document: EP

Effective date: 20210317