WO2019154317A1 - 分组数据汇聚协议pdcp重复机制的激活方法及节点设备 - Google Patents

分组数据汇聚协议pdcp重复机制的激活方法及节点设备 Download PDF

Info

Publication number
WO2019154317A1
WO2019154317A1 PCT/CN2019/074403 CN2019074403W WO2019154317A1 WO 2019154317 A1 WO2019154317 A1 WO 2019154317A1 CN 2019074403 W CN2019074403 W CN 2019074403W WO 2019154317 A1 WO2019154317 A1 WO 2019154317A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
bearer
repetition mechanism
pdcp repetition
uplink
Prior art date
Application number
PCT/CN2019/074403
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 EP19751843.4A priority Critical patent/EP3751955B1/en
Priority to US16/967,669 priority patent/US11729846B2/en
Priority to KR1020207025703A priority patent/KR102389742B1/ko
Publication of WO2019154317A1 publication Critical patent/WO2019154317A1/zh

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and a node device for a packet data convergence protocol PDCP repetition mechanism.
  • a UMTS Terrestrial Radio Access Network In a Long Term Evolution (LTE) system, a UMTS Terrestrial Radio Access Network (E-UTRAN) is composed of a plurality of evolved Node Bs (eNodeBs), an eNodeB and an evolved packet.
  • the Evolved Packet Core network is connected through the S1 interface, and the eNodeBs are connected through the X2 interface.
  • CU central unit
  • RRC radio resource control
  • DU distributed node
  • the interface (NG) of the base station and the core network is suspended at the CU, and the interface (Xn) between the base stations is also suspended at the CU.
  • the manner of CU/DU separation on the RAN side is divided into high-level separation and low-level separation.
  • the high-level separation scheme is Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP) in CU, Radio Link Control (RLC), and media intervention.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • Control Media Access Control
  • MAC Physical layer and RF in DU.
  • the RRC message is mapped into a corresponding PDCP Protocol Data Unit (PDU) through the PDCP layer, and then the PDCP PDU data stream is included in the CU/DU in the form of a container (container).
  • PDU Packet Control Protocol
  • the interface AP message it is transmitted through the control plane.
  • the DU distributes the data stream to the corresponding layer 2 entity, and continues to process the data and send it to the UE.
  • the control plane adopts the Stream Control Transmission Protocol (SCTP) protocol stack to ensure the reliability of data transmission.
  • SCTP Stream Control Transmission Protocol
  • a special user plane tunnel is established between the CU and the DU for each data bearer (DRB).
  • DRB data bearer
  • the CU passes the data corresponding to the DRB to the PDCP and then passes the corresponding tunnel to the tunnel.
  • DU data bearer
  • CA Carrier Aggregation
  • the NR introduces duplication of CA based on PD and Double Connection (DC).
  • the CA-based PDCP duplication is a PDCP data packet sent to two Radio Link Control (RLC) entities located under the same node;
  • RLC Radio Link Control
  • the data transfer between the PDCP layer and the RLC layer is an internal implementation
  • the DRB and the PDCP PDU corresponding to the Signaling Bearer (SRB) are transferred between the CU and the DU.
  • SRB Signaling Bearer
  • the DC-based PDCP duplication is a PDCP packet sent to two RLC entities located under two nodes.
  • the MAC can activate UL PDCP duplication of a bearer.
  • how to activate UL PDCP duplication requires consideration of standard support.
  • Embodiments of the present disclosure provide a method for activating a packet data convergence protocol PDCP repetition mechanism and a node device. Resolving whether the repetition mechanism of the UL of the bearer is activated or inactive while configuring the PDCP repetition mechanism for the bearer.
  • an embodiment of the present disclosure provides the following technical solutions:
  • a method for activating a packet data convergence protocol PDCP repetition mechanism includes:
  • the second node receives the notification message sent by the first node when the bearer is configured to configure the PDCP repetition mechanism
  • the second node After receiving the notification message, the second node changes or determines an activation or deactivation state of the PDCP repetition mechanism of the uplink of the bearer.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism and activates/deactivates the PDCP repetition mechanism of the uplink of the bearer.
  • the second node after receiving the notification message, changes an activation or deactivation state of the PDCP repetition mechanism of the uplink of the bearer, including:
  • the second node After the second node receives the indication information of the PDCP repetition mechanism of the uplink of the bearer that is activated/deactivated, the second node changes the activation/deactivation of the PDCP repetition mechanism of the uplink of the bearer. status.
  • the second node changes an activation/deactivation state of the PDCP repetition mechanism of the uplink of the bearer, including:
  • the second node changes the activation/deactivation state of the uplink of the bearer through the medium access control control unit MAC CE signaling.
  • the second node After the second node receives the indication information of the PDCP repetition mechanism of the uplink that activates the bearer carried by the notification message, or the second node changes the deactivation state of the uplink of the bearer. After the activation status, it also includes:
  • the second node provides a service of a corresponding priority to the bearer according to an activation state of the uplink of the bearer.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism.
  • the determining, by the second node, the activation or deactivation status of the PDCP repetition mechanism of the uplink of the bearer after receiving the notification message includes:
  • the second node After receiving the notification message, the second node sends a response message to the first node, where the response message carries the activation message, when determining the PDCP repetition mechanism of the uplink of the bearer is activated. Indicated information of the PDCP repetition mechanism of the uplink carried.
  • the second node is a distribution node when the first node is a central node in a scenario where the central node CU/distributed DU is separated in a scenario where the central node CU/distributed DU is separated;
  • the second node is the secondary node SN.
  • An embodiment of the present disclosure further provides a method for activating a packet data convergence protocol PDCP repetition mechanism, including:
  • the first node configures the PDCP repetition mechanism for the bearer
  • the first node configures a PDCP repetition mechanism for the bearer according to the auxiliary information reported by the second node.
  • the auxiliary information includes: at least one of a second node supporting a carrier aggregation CA scenario, a high-reliability ultra-low latency communication URLLC service, and status information of a channel currently supported by the second node.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism and activates/deactivates the PDCP repetition mechanism of the uplink of the bearer.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism.
  • the sending, by the first node, the notification message to the second node further includes:
  • the second node is a distribution node when the first node is a central node in a scenario where the central node CU/distribution node DU is separated according to the PDCP repetition mechanism of the carrier aggregation CA; or
  • the second node is the secondary node SN.
  • An embodiment of the present disclosure further provides a node device, including:
  • transceiver a transceiver, a memory, a processor, and a computer program stored on the memory and operable on the processor;
  • the transceiver is configured to receive a notification message that is sent when the first node is configured to carry a PDCP repetition mechanism
  • the processor is configured to modify or determine an activation or deactivation state of an uplink PDCP repetition mechanism of the bearer after receiving the notification message.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism and activates/deactivates the PDCP repetition mechanism of the uplink of the bearer.
  • the processor After the processor receives the indication information of the PDCP repetition mechanism of the uplink that is activated/deactivated in the notification message, the processor changes the PDCP repetition of the uplink of the bearer. The activation/deactivation state of the mechanism.
  • the transceiver is further configured to change an activation/deactivation state of an uplink of the bearer by using a medium access control control unit MAC CE signaling.
  • the processor is further configured to provide a service of a corresponding priority to the bearer according to an activation state of an uplink of the bearer.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism.
  • the transceiver After receiving the notification message, the transceiver sends a response message to the first node when determining the PDCP repetition mechanism for activating the uplink of the bearer, where the response message carries an activation The indication information of the PDCP repetition mechanism of the uplink that is carried.
  • the packet aggregation protocol PDCP repetition mechanism based on the carrier aggregation CA in the scenario where the central node CU/distribution node DU is separated, when the first node is a central node, the second node is a distribution node;
  • the second node is the secondary node SN.
  • An embodiment of the present disclosure further provides a node device, including:
  • transceiver a transceiver, a memory, a processor, and a computer program stored on the memory and operable on the processor;
  • the transceiver is configured to send a notification message to the second node when the PDCP repetition mechanism is configured for the bearer, and enable the second node to change or determine the PDCP of the uplink of the bearer after receiving the notification message.
  • the activation or deactivation state of the repetition mechanism is configured to send a notification message to the second node when the PDCP repetition mechanism is configured for the bearer, and enable the second node to change or determine the PDCP of the uplink of the bearer after receiving the notification message.
  • the transceiver configures a PDCP repetition mechanism for the bearer according to the auxiliary information reported by the second node.
  • the auxiliary information includes: at least one of a second node supporting a carrier aggregation CA scenario, a high-reliability ultra-low latency communication URLLC service, and status information of a channel currently supported by the second node.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism and activates/deactivates the PDCP repetition mechanism of the uplink of the bearer.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism.
  • the transceiver is further configured to receive, by the second node, a response message sent by the second node according to the notification message when determining an uplink PDCP repetition mechanism of the bearer, where the response message carries The indication information of the PDCP repetition mechanism of the uplink of the bearer is activated.
  • the second node is a distribution node when the first node is a central node in a scenario where the central node CU/distribution node DU is separated according to the PDCP repetition mechanism of the carrier aggregation CA; or
  • the second node is the secondary node SN.
  • An embodiment of the present disclosure further provides an activation apparatus for a PDCP repetition mechanism, including:
  • a transceiver module configured to receive a notification message sent by the first node when the PDCP repetition mechanism is configured to be carried by the first node;
  • a processing module configured to: after receiving the notification message, change or determine an activation or deactivation state of the PDCP repetition mechanism of the uplink of the bearer.
  • An embodiment of the present disclosure further provides an activation apparatus of a packet data convergence protocol PDCP repetition mechanism, including:
  • a transceiver module configured to send a notification message to the second node when the PDCP repetition mechanism is configured for the bearer; and after the receiving, by the second node, the PDCP repetition mechanism of the uplink of the bearer is changed or determined Activation or deactivation status.
  • Embodiments of the present disclosure also provide a computer storage medium comprising instructions that, when executed by a computer, cause a computer to perform the method as described above.
  • the second node receives the notification message that is sent when the first node is configured to carry the PDCP repetition mechanism, and the second node activates the PDCP repetition of the uplink of the bearer according to the notification message.
  • Mechanism; CA-based PDCP repetition mechanism in the scenario of CU/DU separation, the first node is a CU and the second node is a DU, and the embodiment of the present disclosure provides how to configure a CA-based PDCP repetition mechanism while Indicates the status (ie, activation or deactivation) of the PDCP repetition mechanism of the currently carried UL and the behavior of subsequent DUs.
  • the first node is the MN and the second node is the SN.
  • the embodiment of the present disclosure provides how to indicate the PDCP repetition mechanism of the UL of the bearer while configuring the DC-based PDCP repetition mechanism. The state of activation or deactivation and subsequent SN behavior.
  • Figure 1 shows a schematic diagram of a CU/DU separation architecture
  • Figure 2 shows the repetition mechanism of PDCP based on CA and DC
  • Figure 3 shows the repetition mechanism of DC-based PDCP
  • FIG. 4 is a flow chart showing a method for activating a packet data convergence protocol PDCP repetition mechanism according to an embodiment of the present disclosure
  • Figure 5 is a block diagram showing the structure of a node device of an embodiment of the present disclosure.
  • Figure 6 shows a block diagram of a node device of an embodiment of the present disclosure.
  • the activation/deactivation of the repetition mechanism of the UL of the bearer is configured, and the configuration scheme of activation/deactivation of the repeated mechanism of the UL of the bearer is given.
  • an embodiment of the present disclosure provides a method for activating a packet data convergence protocol PDCP repetition mechanism, including:
  • Step 11 The second node receives a notification message sent by the first node when the PDCP repetition mechanism is configured to be bearer.
  • Step 12 After receiving the notification message, the second node changes or determines an activation or deactivation state of the PDCP repetition mechanism of the uplink of the bearer.
  • the second node is a distribution node (DU);
  • the DC-based PDCP repetition mechanism when the first node is a MN, the second node is an SN.
  • the second node receives, by the second node, a notification message that is sent when the PDCP repetition mechanism is configured for the bearer; after receiving the notification message, the second node changes or determines the uplink of the bearer.
  • the activation or deactivation state of the PDCP repetition mechanism thus, when the bearer is configured with the PDCP repetition mechanism, the uplink (UL) repetition mechanism of the bearer may be activated or deactivated to fill the gap of the related technology.
  • Step 111 The second node receives a notification message that is sent when the first node is configured to carry a PDCP repetition mechanism.
  • the notification message carries a PDCP repetition mechanism configured by the bearer and an uplink/PDCP that activates/deactivates the bearer. Instructions for the repeat mechanism.
  • Step 121 After receiving the indication information of the PDCP repetition mechanism of the uplink that is activated/deactivated in the notification message, the second node changes the activation of the PDCP repetition mechanism of the uplink of the bearer. / Deactivated state.
  • the second node changes an activation/deactivation state of the PDCP repetition mechanism of the uplink of the bearer, including: the second node changes the bearer by using Medium Access Control Control Unit (MAC CE) signaling The active/deactivated state of the uplink.
  • MAC CE Medium Access Control Control Unit
  • the second node receives the indication information of the PDCP repetition mechanism of the uplink that activates the bearer carried by the notification message, or the second node changes the uplink deactivation of the bearer After the status is active, it also includes:
  • Step 131 The second node provides a service of a corresponding priority to the bearer according to an activation state of the uplink of the bearer.
  • the CU For the CA-based PDCP repetition mechanism, in the CU/DU separation scenario, the CU, according to the auxiliary information reported by the DU, notifies the DU that the UL repetition mechanism of the bearer is activated when the PDCP repetition mechanism is configured for a bearer.
  • the subsequent DU may change the activation of the bearer by using MAC signaling, specifically MAC CE signaling. / Deactivate the state, and provide the corresponding priority service for the bearer according to the activation state.
  • the connected UE accesses a gNB of a CU/DU separation architecture, and the UE requests to initiate an ultra-high reliability low latency communication (URLLC) service.
  • the CU Based on the indication of the core network, the CU establishes a bearer-related context supporting the URLLC service in the DU by using a UE context modification request message according to the auxiliary information of the DU, where the bearer carries the PDCP repetition mechanism and the bearer.
  • An indication of the activation/deactivation status of the UL PDCP repetition mechanism includes:
  • Step 1 The core network requests the Radio Access Network (RAN) to establish a bearer corresponding to the URLLC service.
  • RAN Radio Access Network
  • Step 2 Based on the auxiliary information provided before the DU, for example, whether the DU supports the CA, whether the URL is supported, and the current channel condition, the CU sends a UE context modification request message to the DU, and the message notifies the DU to establish a bearer supporting the PDCP repetition mechanism. At the same time, the CU informs that the DU UL repetition mechanism has been activated. Further, the bearer supports the PDCP repetition mechanism and the state information that the bearer UL repetition mechanism has been activated/deactivated, and may also be directly sent by the CU to the UE.
  • Step 3 After receiving the message, the DU learns that the bearer supports the PDCP repetition mechanism and the UL repetition mechanism has been activated. Considering that the UE needs to perform high priority processing. Subsequently, the DU may decide whether to perform activation/deactivation of the UL repetition mechanism according to the network condition, and the DU responds to the request of the CU by using a UE Context modification response message. Further, after the DU changes the activation/deactivation state of the UL repeating mechanism of the bearer, the DU may also notify the UE of the activation/deactivation state of the UL repeating mechanism of the changed bearer.
  • Step 4 The CU initiates an RRC Connection reconfiguration (RRC Connection Reconfiguration) process to the UE.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the primary node (MN) according to the auxiliary information reported by the secondary node (SN), when the MN informs the SN to configure a repetition mechanism for a bearer, simultaneously notifies the SN that the UL repetition mechanism of the bearer is activated.
  • the subsequent SN can change the activation/deactivation status of the bearer through MAC signaling, and provide the corresponding priority service for the bearer according to the activation state.
  • the UE accesses both LTE and NR, and the UE requests to initiate a URLLC service.
  • the SgNB modification request message is used to establish a context related to the split bearer supporting the URLLC service in the SN, where the bearer carries an indication that the bearer supports the PDCP repetition mechanism and the bearer The activation/deactivation state of the UL's PDCP repetition mechanism.
  • the method includes:
  • Step 1 The core network requests the RAN to establish a bearer corresponding to the URLLC service.
  • Step 2 SN-based auxiliary information, such as whether to support the URLLC service, the current channel situation, etc.
  • the MN sends an SgNB modification request message to the SN, the message notifying the SN to establish a Split bearer supporting the repetition mechanism, and the MN notifying the SN UL repetition mechanism Already activated.
  • the bearer supports the PDCP repetition mechanism and the state information that the bearer UL repetition mechanism has been activated/deactivated, and may also be directly sent by the MN to the UE.
  • Step 3 After receiving the message, the SN learns that the bearer supports the repetition mechanism and the UL repetition mechanism has been activated, and considers that the UE needs to be processed with high priority. Subsequently, the SN may decide whether to perform activation/deactivation of the UL repetition mechanism according to the network condition, and the SN responds to the MN request through the SgNB modification response message. Further, after the SN changes the activation/deactivation state of the UL repeating mechanism of the bearer, the SN may also notify the UE of the activation/deactivation state of the UL repeating mechanism of the changed bearer.
  • Step 4 The MN initiates an RRC Connection reconfiguration process to the UE.
  • the second implementation method of the embodiment shown in FIG. 1 is as follows:
  • Step 112 The second node receives the notification message that is sent when the first node is configured to carry the PDCP repetition mechanism, and the notification message carries the indication information that the bearer is configured with the PDCP repetition mechanism.
  • Step 122 After receiving the notification message, the second node sends a response message to the first node when determining that the PDCP repetition mechanism of the uplink of the bearer is activated, where the response message carries The indication information of the PDCP repetition mechanism of the uplink of the bearer is activated.
  • the CU only informs the DU that a bearer is configured with a repetition mechanism, and the DU determines that the bearer is currently needed, activates the UL repeat mechanism, and carries the activation in the response message to the CU.
  • the indication of the UL repetition mechanism the CU informs the UE through a RRC message that a bearer is configured with a repetition mechanism and activates the UL repetition mechanism.
  • the connected UE accesses a gNB of a CU/DU separation architecture, and the UE requests to initiate a URLLC service.
  • the CU Based on the indication of the core network, the CU establishes a bearer-related context supporting the URLLC service in the DU through the UE context modification request message, and the DU considers that the bearer currently needs to activate the UL repeat mechanism, and carries the PDCP repetition mechanism activation/deactivation in the UE context modification response.
  • Activation status includes:
  • Step 1 The core network requests the RAN to establish a bearer corresponding to the URLLC service.
  • Step 2 The CU sends a UE context modification request message to the DU, and the message notifies the DU to establish a bearer supporting the repetition mechanism.
  • Step 3 After receiving the message, the DU learns that the bearer supports the repetition mechanism.
  • the DU determines the UL repetition mechanism that needs to activate the bearer according to the current radio condition.
  • the DU instructs the CU to activate the UL repetition mechanism in the UE Context modification response message. Further, after determining the activation/deactivation state of the relaying mechanism of the UL of the bearer, the DU may also notify the UE of the activation/deactivation state of the relaying mechanism of the bearer UL.
  • Step 4 The CU initiates an RRC Connection reconfiguration process to the UE according to the information in the received UE Context modification response message.
  • the MN For the PDCP repetition mechanism of the base DC, the MN only informs the SN that a bearer is configured with duplication. The SN determines that the bearer needs to activate the UL repeat mechanism, and the response message to the MN carries an indication of activating the UL repeat mechanism, and the MN passes the RRC message. The UE is notified that a bearer is configured with a repetition mechanism and that the UL repeat mechanism is activated.
  • the UE accesses both LTE and NR, and the UE requests to initiate a URLLC service.
  • the MN Based on the indication of the core network, the MN establishes a context related to the split bearer supporting the URLLC service in the SN through the SgNB modification request message, where the bearer carries an indication that the PDCP repetition mechanism is supported.
  • the SN believes that the bearer currently needs to activate the UL repeat mechanism, and carries the activation/deactivation state of the PDCP repetition mechanism in the SgNB modification response.
  • the method includes:
  • Step 1 The core network requests the RAN to establish a bearer corresponding to the URLLC service.
  • Step 2 The MN sends an SgNB modification request message to the SN, and the message informs the SN to establish a SPLIT bearer supporting the repetition mechanism.
  • Step 3 After receiving the message, the SN learns that the bearer supports the repetition mechanism. According to the current radio condition, it is considered that the UL repetition mechanism needs to be activated.
  • the SN indicates that the MN activates the UL repetition mechanism in the SgNB modification response message. Further, after determining the activation/deactivation state of the relaying mechanism of the UL of the bearer, the SN may also notify the UE of the activation/deactivation state of the relaying mechanism of the bearer UL.
  • Step 4 The MN initiates an RRC Connection reconfiguration process to the UE according to the information in the received SgNB modification response message.
  • the following two methods are provided to activate/deactivate the UL repetition mechanism when configuring the bearer repetition mechanism:
  • Method 1 According to the auxiliary information reported by the DU, the CU notifies the DU that the UL repeat mechanism of the bearer is activated/deactivated when the repeat mechanism is configured for a bearer, and the subsequent DU may change the activation of the bearer by using MAC signaling. Deactivate the state and provide the corresponding priority service for the bearer according to the activation state.
  • Method 2 The CU only informs the DU that a bearer is configured with a repetition mechanism.
  • the DU determines that the bearer needs to activate the UL repeat mechanism.
  • the response message to the CU carries an indication of activating the UL repeat mechanism, and the CU notifies the UE of the bearer by using an RRC message. (bearer) configures the repetition mechanism and activates the UL's repetition mechanism.
  • the present disclosure teaches how to indicate the state of the current PDCP repetition mechanism (ie, activation or deactivation) and the behavior of subsequent DUs while configuring the CA-based PDCP repetition mechanism in the CU/DU separation scenario.
  • an embodiment of the present disclosure further provides a node device 50, including:
  • the transceiver 51 is configured to receive a notification message that is sent when the first node is configured to carry the PDCP repetition mechanism.
  • the processor 52 is configured to modify or determine an activation or deactivation state of the PDCP repetition mechanism of the uplink of the bearer after receiving the notification message.
  • the transceiver and the processor may be communicably connected through a bus or an interface
  • the node device may further include a memory 53 or the like for storing corresponding data of the transceiver or the processor in processing data, the memory and the transceiver.
  • the processor can be communicatively connected via a bus interface or an interface.
  • the packet aggregation protocol based on the carrier aggregation CA, the PDCP repetition mechanism in the scenario where the central node CU/distribution node DU is separated, when the first node is the central node, the second node a distribution node; the notification message carries indication information that the bearer is configured with a PDCP repetition mechanism and a PDCP repetition mechanism that activates/deactivates the uplink of the bearer.
  • the processor changes the PDCP of the uplink of the bearer.
  • the activation/deactivation state of the repeat mechanism is not limited to:
  • the transceiver is further configured to change an activation/deactivation state of an uplink of the bearer by using a medium access control control unit MAC CE signaling.
  • the processor is further configured to provide, according to an activation status of the uplink of the bearer, a service of a corresponding priority for the bearer.
  • the dual-connected DC-based packet data convergence protocol PDCP repetition mechanism when the first node is the master node MN, the second node is the secondary node SN;
  • the indication information carrying the PDCP repetition mechanism is configured.
  • the transceiver after receiving the notification message, the transceiver sends a response message to the first node when determining a PDCP repetition mechanism for activating the uplink of the bearer, where the response message carries an activation message.
  • the indication information of the bearer PDCP repetition mechanism of the bearer is a device of the second node corresponding to the method on the second node side, and all implementations of the method on the second node side are applicable to the embodiment, and the same technical effects can be achieved.
  • An embodiment of the present disclosure further provides a node device, including:
  • a transceiver configured to send a notification message to the second node when the PDCP repetition mechanism is configured for the bearer; and after the receiving, by the second node, the PDCP repetition mechanism of the uplink of the bearer is changed or determined Activation or deactivation status.
  • the node device may further include a processor that processes the data, and a memory that stores the data, and the processor and the memory may be communicably connected to the transceiver through a bus or an interface;
  • the second node is a distribution node in a scenario where the central node CU/distribution node DU is separated;
  • the transceiver configures a PDCP repetition mechanism for the bearer according to the auxiliary information reported by the second node.
  • the auxiliary information includes: at least one of a second node supporting a carrier aggregation CA scenario, a high-reliability ultra-low latency communication URLLC service, and situation information of a channel currently supported by the second node.
  • the notification message carries the indication information that the bearer is configured with a PDCP repetition mechanism and activates/deactivates the PDCP repetition mechanism of the uplink of the bearer.
  • the second node when the first node is a master node MN, the second node is a secondary node SN based on a dual-connected DC-based PDCP repetition mechanism.
  • the notification message carries indication information that the bearer is configured with a PDCP repetition mechanism.
  • the transceiver is further configured to: receive, by the second node, a response message that is sent by the second node according to the notification message when determining an uplink PDCP repetition mechanism of the bearer, where the response message is carried There is indication of activation of the PDCP repetition mechanism of the uplink of the bearer.
  • This embodiment is a device of the first node corresponding to the method on the first node side, and all implementations of the method on the first node side are applicable to the embodiment, and the same technical effects can be achieved.
  • an embodiment of the present disclosure further provides an activation device 60 for a PDCP repetition mechanism, which is applied to a second node, and includes:
  • the transceiver module 61 is configured to receive a notification message that is sent when the first node is configured to carry the PDCP repetition mechanism.
  • the processing module 62 is configured to modify or determine an activation or deactivation state of the PDCP repetition mechanism of the uplink of the bearer after receiving the notification message.
  • the embodiment is a device of the second node corresponding to the method on the second node side, and all implementations of the method on the second node side are applicable to the embodiment, and the same technical effect can be achieved. .
  • An embodiment of the present disclosure further provides an apparatus for activating a packet data convergence protocol PDCP repetition mechanism, which is applied to a first node, and includes:
  • a transceiver module configured to send a notification message to the second node when the PDCP repetition mechanism is configured for the bearer; and after the receiving, by the second node, the PDCP repetition mechanism of the uplink of the bearer is changed or determined Activation or deactivation status.
  • the embodiment is a device of the first node corresponding to the method on the first node side, and all implementations of the method on the first node side are applicable to the embodiment, and the same technical effect can be achieved. .
  • An embodiment of the present disclosure further provides a communication device, including:
  • a processor configured to perform a function of: receiving a notification message sent by the first node when carrying a configuration packet data convergence protocol PDCP repetition mechanism; and after receiving the notification message, changing or determining an uplink of the bearer Activation or deactivation of the PDCP repetition mechanism.
  • An embodiment of the present disclosure further provides a communication device, including:
  • a processor configured to perform a function of: sending a notification message to the second node when the PDCP repetition mechanism is configured for the bearer; and causing the second node to change or determine the uplink of the bearer after receiving the notification message The activation or deactivation state of the PDCP repetition mechanism of the road.
  • Embodiments of the present disclosure also provide a computer storage medium comprising instructions that, when executed by a computer, cause a computer to perform a method on a first node or a second node side as described above.
  • the second node receives the notification message that is sent when the first node is configured to carry the PDCP repetition mechanism, and the second node changes or determines the uplink of the bearer after receiving the notification message.
  • the activation or deactivation state of the PDCP repetition mechanism of the link in the scenario of CU/DU separation, in the scenario where the CU/DU is separated, the first node is a CU, and the second node is a DU, how is the embodiment of the present disclosure given While configuring the CA-based PDCP repetition mechanism, the status of the PDCP repetition mechanism of the currently carried UL (ie, activation or deactivation) and the behavior of subsequent DUs are indicated.
  • the first node is the MN and the second node is the SN.
  • the embodiment of the present disclosure provides how to indicate the PDCP repetition mechanism of the UL of the bearer while configuring the DC-based PDCP repetition mechanism. The state of activation or deactivation and subsequent SN behavior.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, a portion of the technical solution of the present disclosure that contributes in essence or to the related art or a part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
  • the objects of the present disclosure can also be achieved by running a program or a set of programs on any computing device.
  • the computing device can be a well-known general purpose device.
  • the objects of the present disclosure may also be realized by merely providing a program product including program code for implementing the method or apparatus. That is to say, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure.
  • the storage medium may be any known storage medium or any storage medium developed in the future.
  • various components or steps may be decomposed and/or recombined.

Landscapes

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

Abstract

本公开公开了一种分组数据汇聚协议PDCP重复机制的激活方法及节点设备，其中，分组数据汇聚协议PDCP重复机制的激活方法包括：第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。

Description

分组数据汇聚协议PDCP重复机制的激活方法及节点设备
相关申请的交叉引用
本申请主张在2018年2月9日在中国提交的中国专利申请No.201810133812.1的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种分组数据汇聚协议PDCP重复机制的激活方法及节点设备。
背景技术
在长期演进(Long Term Evolution，LTE)系统中，陆地无线接入网(UMTS Terrestrial Radio Access Network，E-UTRAN)由多个演进的节点B(Evolution Node B，eNodeB)组成,eNodeB与演进型分组核心网(Evolved Packet Core network，EPC)之间通过S1接口连接，eNodeB之间通过X2接口连接。
在5G系统中，考虑引入一个中心节点(Central Unit，CU)进行集中的控制和调度，无线资源控制(Radio Resource Control，RRC)的功能以及部分层2或/和层1功能在该中心节点CU，基站其他功能部署在分布节点(Distribute Unit，DU)上。
基站和核心网的接口(NG)中止于CU，基站之间的接口(Xn)也中止于CU。
无线接入网(Radio Access Network，RAN)侧的CU/DU分离：
如图1所示：RAN侧的CU/DU分离的方式分为高层分离和低层分离。其中，高层分离的方案是无线资源控制协议((Radio Resource Control，RRC)、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)在CU；无线链路层控制(Radio Link Control，RLC)、媒体介入控制(Media Access Control，MAC)以及物理层以及RF在DU。
对于控制面信令，在CU，将RRC消息经过PDCP层影射成对应的PDCP协议数据单元(Protocol Data Unit，PDU)，然后将该PDCP PDU数据流以容 器(container)的形式包含在CU/DU的接口AP消息中，通过控制面进行传递。DU将该数据流分发到相应的层2实体上，继续对该数据进行处理并发给UE。由于控制面采用了流控制传输协议(Stream Control Transmission Protocol，SCTP)协议栈，保证了数据传输的可靠性。
对于用户面数据，CU和DU之间会对每个数据承载(DRB)都建立一个专门的用户面通道(tunnel)，CU将DRB对应的数据在经过PDCP的处理后，通过对应的tunnel传递给DU。
2)基于载波聚合(Carrier Aggregation，CA)的PDCP的重复机制(duplication)
为了支持数据的可靠传输，NR中引入了基于CA以及双连接(Double Connection，DC)的PDCP的duplication。
如图2所示：基于CA的PDCP duplication是一个PDCP数据包发给位于同一个节点下的两个无线链路层控制(Radio Link Control，RLC)实体；
对于PDCP和RLC位于同一节点的场景，PDCP层和RLC层之间的数据传递是内部实现；
但是，对于CU/DU分离的场景，DRB以及信令承载(SRB)对应的PDCP PDU在CU和DU之间传递。
如何在配置承载的PDCP的duplication时，激活上行链路的PDCP重复机制(UL PDCP duplication)需要标准的支持。
3)基于双连接(DC)的PDCP的duplication
如图3所示：基于DC的PDCP duplication是一个PDCP数据包发给位于两个节点下的两个RLC实体，在基于DC的PDCP duplication的情况下，MAC可以激活某个承载的UL PDCP duplication，在初始配置承载的PDCP duplication的时候，如何激活UL PDCP duplication需要考虑标准上的支持。
目前，对于CU/DU分离场景下，如何在配置承载支持基于CA的duplication的同时激活UL duplication还没有完整的方案。
同时，在MR-DC场景下，对于如何在配置承载支持基于DC的duplication的同时激活UL duplication也没有完整的方案。
发明内容
本公开实施例提供了一种分组数据汇聚协议PDCP重复机制的激活方法及节点设备。解决在为承载配置PDCP重复机制的同时，指示该承载的UL的重复机制是激活还是非激活状态。
为解决上述技术问题，本公开的实施例提供如下技术方案：
一种分组数据汇聚协议PDCP重复机制的激活方法，包括：
第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；
所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
其中，所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，所述第二节点在接收到所述通知消息后，更改所述承载的上行链路的PDCP重复机制的激活或者去激活状态，包括：
所述第二节点接收到所述通知消息携带的激活/去激活所述承载的上行链路的PDCP重复机制的指示信息后，更改所述承载的上行链路的PDCP重复机制的激活/去激活状态。
其中，所述第二节点更改所述承载的上行链路的PDCP重复机制的激活/去激活状态，包括：
所述第二节点通过介质访问控制控制单元MAC CE信令，更改所述承载的上行链路的激活/去激活状态。
其中，所述第二节点接收到所述通知消息携带的激活所述承载的上行链路的PDCP重复机制的指示信息后，或者所述第二节点更改所述承载的上行链路的去激活状态为激活状态后，还包括：
所述第二节点根据所述承载的上行链路的激活状态，为所述承载提供相应优先级的服务。
其中，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息。
其中，所述第二节点在接收到所述通知消息后，确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态，包括：
所述第二节点在接收到所述通知消息后，在确定激活所述承载的上行链 路的PDCP重复机制时，向所述第一节点发送响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，基于载波聚合CA的PDCP重复机制，在中心节点CU/分布DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
基于双连接DC的PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。
本公开的实施例还提供一种分组数据汇聚协议PDCP重复机制的激活方法，包括：
第一节点为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
其中，所述第一节点根据所述第二节点上报的辅助信息，为承载配置PDCP重复机制。
其中，所述辅助信息包括：第二节点是否支持载波聚合CA场景、高可靠超低时延通信URLLC业务、所述第二节点当前支持的信道的情况信息中的至少一项。
其中，所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息。
其中，第一节点向第二节点发送通知消息后还包括：
所述第一节点接收所述第二节点根据所述通知消息，在确定激活所述承载的上行链路的PDCP重复机制时，发送的响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，基于载波聚合CA的PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
基于双连接DC的PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。
本公开的实施例还提供一种节点设备，包括：
收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，
所述收发机，用于接收第一节点为承载配置PDCP重复机制时发送的通知消息；
所述处理器，用于在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
其中，所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，所述处理器在所述收发机接收到所述通知消息携带的激活/去激活所述承载的上行链路的PDCP重复机制的指示信息后，更改所述承载的上行链路的PDCP重复机制的激活/去激活状态。
其中，所述收发机还用于通过介质访问控制控制单元MAC CE信令，更改所述承载的上行链路的激活/去激活状态。
其中，所述处理器还用于根据所述承载的上行链路的激活状态，为所述承载提供相应优先级的服务。
其中，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息。
其中，所述收发机在接收到所述通知消息后，在确定激活所述承载的上行链路的PDCP重复机制时，向所述第一节点发送响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，基于载波聚合CA的分组数据汇聚协议PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
基于双连接DC的分组数据汇聚协议PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。
本公开的实施例还提供一种节点设备，包括：
收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，
所述收发机，用于为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的 上行链路的PDCP重复机制的激活或者去激活状态。
其中，所述收发机根据所述第二节点上报的辅助信息，为承载配置PDCP重复机制。
其中，所述辅助信息包括：第二节点是否支持载波聚合CA场景、高可靠超低时延通信URLLC业务、所述第二节点当前支持的信道的情况信息中的至少一项。
其中，所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息。
其中，所述收发机还用于，接收所述第二节点根据所述通知消息，在确定激活所述承载的上行链路的PDCP重复机制时，发送的响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
其中，基于载波聚合CA的PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
基于双连接DC的PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。
本公开的实施例还提供一种PDCP重复机制的激活装置，包括：
收发模块，用于接收第一节点为承载配置PDCP重复机制时发送的通知消息；
处理模块，用于在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
本公开的实施例还提供一种分组数据汇聚协议PDCP重复机制的激活装置，包括：
收发模块，用于为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
本公开的实施例还提供一种计算机存储介质，包括指令，当所述指令在计算机运行时，使得计算机执行如上所述的方法。
本公开实施例的有益效果是：
本公开的上述实施例中，通过第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；所述第二节点根据所述通知消息，激活所述承载的上行链路的PDCP重复机制；基于CA的PDCP重复机制，在CU/DU分离的场景下，第一节点为CU，第二节点为DU，本公开的实施例给出了如何在配置基于CA的PDCP重复机制的同时，指示当前承载的UL的PDCP重复机制的状态(即激活或者去激活)以及后续DU的行为。同时，在MR-DC的场景下，第一节点为MN，第二节点为SN，本公开的实施例给出了如何在配置基于DC的PDCP重复机制的同时指示该承载的UL的PDCP重复机制的状态，即激活或者去激活以及后续SN的行为。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1表示CU/DU分离架构示意图；
图2表示基于CA以及DC的PDCP的重复机制；
图3表示基于DC的PDCP的重复机制；
图4表示本公开的实施例一种分组数据汇聚协议PDCP重复机制的激活方法流程图；
图5表示本公开的实施例节点设备的结构框图；
图6表示本公开的实施例节点设备的模块框图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
本公开的实施例，通过在配置承载的PDCP重复机制时，配置该承载的UL的重复机制的激活/去激活，给出了承载的UL的重复机制的激活/去激活的配置方案。
如图4所示，本公开的实施例提供一种分组数据汇聚协议PDCP重复机制的激活方法，包括：
步骤11，第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；
步骤12，所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
该实施例中，基于CA的PDCP重复机制，在CU/DU分离的场景下，所述第一节点为中心节点(CU)时，所述第二节点为分布节点(DU)；
基于DC的PDCP重复机制，所述第一节点为MN时，所述第二节点为SN。
该实施例中，通过第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态；从而实现在承载配置了PDCP重复机制时，可以对该承载的上行链路(UL)重复机制的激活或者去激活，填补上相关技术的空白。
该图1所示实施例的第一种实现方法：
步骤111，第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
步骤121，所述第二节点接收到所述通知消息携带的激活/去激活所述承载的上行链路的PDCP重复机制的指示信息后，更改所述承载的上行链路的PDCP重复机制的激活/去激活状态。
其中，所述第二节点更改所述承载的上行链路的PDCP重复机制的激活/去激活状态，包括：所述第二节点通过介质访问控制控制单元(MAC CE)信令，更改所述承载的上行链路的激活/去激活状态。
进一步地，所述第二节点接收到所述通知消息携带的激活所述承载的上 行链路的PDCP重复机制的指示信息后，或者所述第二节点更改所述承载的上行链路的去激活状态为激活状态后，还包括：
步骤131，所述第二节点根据所述承载的上行链路的激活状态，为所述承载提供相应优先级的服务。
对于基于CA的PDCP重复机制，在CU/DU分离的场景下，CU根据DU上报的辅助信息，CU在为某个承载配置PDCP重复机制的时候，同时通知DU该承载的UL重复机制是激活/去激活状态，DU在接收到CU为承载配置PDCP重复机制以及承载的UL重复机制是激活/去激活状态后，后续DU可以通过MAC信令，具体可以是MAC CE信令，改变该承载的激活/去激活状态，并根据激活状态为该承载提供相应的优先级的服务。
具体实现时，连接态的UE接入一个CU/DU分离架构的gNB，该UE请求发起一个超高可靠低时延通信(URLLC)业务。基于核心网的指示，根据DU的辅助信息，CU通过UE上下文修改请求(UE context modification request)消息，在DU建立支持URLLC业务的承载相关的上下文，其中，携带该承载支持PDCP重复机制以及该承载的UL的PDCP重复机制的激活/去激活状态的指示。该方法包括：
步骤一：核心网向无线接入网(Radio Acess Network，RAN)请求建立URLLC业务对应的承载。
步骤二：基于DU之前提供的辅助信息，比如DU是否支持CA，是否支持URLLC业务，目前的信道情况等，CU向DU发送UE context modification request消息，该消息通知DU建立支持PDCP重复机制的承载，同时，CU通知DU UL重复机制已经激活。进一步地，该承载支持PDCP重复机制以及该承载UL重复机制已经激活/去激活的状态信息，也可以由CU直接发送给UE。
步骤三：DU收到消息后获知该承载支持PDCP重复机制并且UL重复机制已经激活，考虑需要对该UE进行高优先级的处理。后续，DU可以根据网络状况决定是否进行UL重复机制的激活/去激活，DU通过UE上下文修改响应(UE Context modification response)消息响应CU的请求。进一步地，DU在更改承载的UL的重复机制的激活/去激活状态后，也可以将更改 后的承载的UL的重复机制的激活/去激活状态通知UE。
步骤四：CU向UE发起RRC连接重配置(RRC Connection reconfiguration，RRC为无线资源控制)过程。
而对于基于DC的PDCP重复机制，主节点(MN)根据辅节点(SN)上报的辅助信息，MN在通知SN为某个承载配置重复机制的时候，同时通知SN该承载的UL重复机制是激活/去激活状态，后续SN可以通过MAC信令改变该承载的激活/去激活状态，并根据激活状态为该承载提供相应的优先级的服务。
具体实现时，UE同时接入LTE和NR，该UE请求发起一个URLLC业务。基于核心网的指示，根据SN的辅助信息，通过SgNB修改请求(SgNB modification request)消息在SN建立支持URLLC业务的split承载相关的上下文，其中，携带该承载支持PDCP重复机制的指示以及该承载的UL的PDCP重复机制的激活/去激活状态。该方法包括：
步骤一：核心网向RAN请求建立URLLC业务对应的承载。
步骤二：基于SN的辅助信息，比如是否支持URLLC业务，目前的信道情况等，MN向SN发送SgNB修改请求消息，该消息通知SN建立支持重复机制的Split承载，同时，MN通知SN UL重复机制已经激活。进一步地，该承载支持PDCP重复机制以及该承载UL重复机制已经激活/去激活的状态信息，也可以由MN直接发送给UE。
步骤三：SN收到消息后获知该承载支持重复机制并且UL重复机制已经激活，考虑需要对该UE进行高优先级的处理。后续，SN可以根据网络状况决定是否进行UL重复机制的激活/去激活，SN通过SgNB modification response消息响应MN的请求。进一步地，SN在更改承载的UL的重复机制的激活/去激活状态后，也可以将更改后的承载的UL的重复机制的激活/去激活状态通知UE。
步骤四：MN向UE发起RRC Connection reconfiguration过程。
该图1所示实施例的第二种实现方法：
步骤112，第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；所述通知消息携带有所述承载被配置PDCP重复机制的指示信息。
步骤122，所述第二节点在接收到所述通知消息后，在确定激活所述承载的上行链路的PDCP重复机制时，向所述第一节点发送响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
对于基于CA的PDCP重复机制，在CU/DU分离的场景下，CU仅通知DU某个承载配置了重复机制，DU判断该承载目前需要，激活UL重复机制，在给CU的响应消息中携带激活UL重复机制的指示，CU通过RRC消息通知UE某个bearer(承载)配置了重复机制并且以及激活UL的重复机制。
具体实现时，连接态的UE接入一个CU/DU分离架构的gNB，该UE请求发起一个URLLC业务。基于核心网的指示，CU通过UE context modification request消息在DU建立支持URLLC业务的承载相关的上下文，DU认为该承载目前需要激活UL重复机制，在UE context modification response中携带PDCP重复机制的激活/去激活状态。该方法包括：
步骤一：核心网向RAN请求建立URLLC业务对应的承载。
步骤二：CU向DU发送UE context modification request消息，该消息通知DU建立支持重复机制的承载。
步骤三：DU收到消息后获知该承载支持重复机制，DU根据目前的无线状况决定需要激活该承载的UL重复机制，DU在UE Context modification response消息中指示CU激活UL重复机制。进一步地，DU在确定承载的UL的重复机制的激活/去激活状态后，也可以将承载的UL的重复机制的激活/去激活状态通知UE。
步骤四：CU根据收到的UE Context modification response消息中的信息，向UE发起RRC Connection reconfiguration过程。
而对于基DC的PDCP重复机制，MN仅通知SN某个承载配置了duplication，SN判断该承载目前需要激活UL重复机制，在给MN的响应消息中携带激活UL重复机制的指示，MN通过RRC消息通知UE某个bearer(承载)配置了重复机制并且以及激活UL的重复机制。
具体实现时，UE同时接入LTE和NR，该UE请求发起一个URLLC业务。基于核心网的指示，MN通过SgNB modification request消息在SN建立支持URLLC业务的split承载相关的上下文，其中，携带该承载支持PDCP重 复机制的指示。SN认为该承载目前需要激活UL重复机制，在SgNB modification response中携带PDCP重复机制的激活/去激活状态。该方法包括：
步骤一：核心网向RAN请求建立URLLC业务对应的承载。
步骤二：MN向SN发送SgNB modification request消息，该消息通知SN建立支持重复机制的SPLIT承载。
步骤三：SN收到消息后获知该承载支持重复机制，根据目前的无线状况，认为需要激活UL重复机制，SN在SgNB modification response消息中指示MN激活UL重复机制。进一步地，SN在确定承载的UL的重复机制的激活/去激活状态后，也可以将承载的UL的重复机制的激活/去激活状态通知UE。
步骤四：MN根据收到的SgNB modification response消息中的信息，向UE发起RRC Connection reconfiguration过程。
本公开的上述实施例中，对于基于CA的PDCP重复机制，在CU/DU分离的场景下，提供了如下两种方法在配置承载的重复机制时激活/去激活UL重复机制：
方法1：根据DU上报的辅助信息，CU在为某个承载配置重复机制的时候同时通知DU该承载的UL重复机制是激活/去激活状态，后续DU可以通过MAC信令改变该承载的激活/去激活状态并根据激活状态为该承载提供相应的优先级的服务。
方法2：CU仅通知DU某个承载配置了重复机制，DU判断该承载目前需要激活UL重复机制，在给CU的响应消息中携带激活UL重复机制的指示，CU通过RRC消息通知UE某个承载(bearer)配置了重复机制并且以及激活UL的重复机制。
本公开给出了在CU/DU分离的场景下，如何在配置基于CA的PDCP重复机制的同时指示当前PDCP重复机制的状态(即激活或者去激活)以及后续DU的行为。同时，利用和上述方法1和方法2类似的方法，也给出了在MR-DC的场景下，如何在配置基于DC的PDCP重复机制的同时指示当前PDCP重复机制的状态，即激活或者去激活以及后续SN的行为。
如图5所示，本公开的实施例还提供一种节点设备50，包括：
收发机51，用于接收第一节点为承载配置PDCP重复机制时发送的通知消息；
处理器52，用于在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
该实施例中，收发机与处理器可通过总线或者接口通信连接，该节点设备还可以包括存储上述收发机或者处理器在处理数据过程中的相应数据的存储器53等，该存储器与收发机和处理器均可通过总线接口或者接口通信连接。
本公开的一具体实施例中，基于载波聚合CA的分组数据汇聚协议PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
进一步地，所述处理器在所述收发机接收到所述通知消息携带的激活/去激活所述承载的上行链路的PDCP重复机制的指示信息后，更改所述承载的上行链路的PDCP重复机制的激活/去激活状态。
进一步地，所述收发机还用于通过介质访问控制控制单元MAC CE信令，更改所述承载的上行链路的激活/去激活状态。
进一步地，所述处理器还用于根据所述承载的上行链路的激活状态，为所述承载提供相应优先级的服务。
本公开的一具体实施例中，基于双连接DC的分组数据汇聚协议PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN；所述通知消息携带有所述承载被配置PDCP重复机制的指示信息。
进一步地，所述收发机在接收到所述通知消息后，在确定激活所述承载的上行链路的PDCP重复机制时，向所述第一节点发送响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。该实施例是与上述第二节点侧的方法对应的第二节点的设备，上述第二节点侧的方法所有实现方式均适用于该实施例中，也能达到相同的技术效果。
本公开的实施例还提供一种节点设备，包括：
收发机，用于为承载配置PDCP重复机制时，向第二节点发送通知消息； 使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
该实施例中，节点设备还可以包括处理数据的处理器，以及存储数据的存储器，处理器与存储器均可通过总线或者接口与收发机通信连接；
本公开一具体实施例中，基于载波聚合CA的PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；
所述收发机根据所述第二节点上报的辅助信息，为承载配置PDCP重复机制。所述辅助信息包括：第二节点是否支持载波聚合CA场景、高可靠超低时延通信URLLC业务、所述第二节点当前支持的信道的情况信息中的至少一项。
进一步地，所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
本公开的另一具体实施例中，基于双连接DC的PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。所述通知消息携带有所述承载被配置PDCP重复机制的指示信息。
进一步地，所述收发机还用于，接收所述第二节点根据所述通知消息，在确定激活所述承载的上行链路的PDCP重复机制时，发送的响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
该实施例是与上述第一节点侧的方法对应的第一节点的设备，上述第一节点侧的方法所有实现方式均适用于该实施例中，也能达到相同的技术效果。
如图6所示，本公开的实施例还提供一种PDCP重复机制的激活装置60，应用于第二节点，包括：
收发模块61，用于接收第一节点为承载配置PDCP重复机制时发送的通知消息；
处理模块62，用于在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
需要说明的是，该实施例是与上述第二节点侧的方法对应的第二节点的设备，上述第二节点侧的方法所有实现方式均适用于该实施例中，也能达到 相同的技术效果。
本公开的实施例还提供一种分组数据汇聚协议PDCP重复机制的激活装置，应用于第一节点，包括：
收发模块，用于为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
需要说明的是，该实施例是与上述第一节点侧的方法对应的第一节点的设备，上述第一节点侧的方法所有实现方式均适用于该实施例中，也能达到相同的技术效果。
本公开的实施例还提供一种通信设备，包括：
处理器，被配置为执行如下功能：接收第一节点为承载配置分组数据汇聚协议PDCP重复机制时发送的通知消息；并在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
本公开的实施例还提供一种通信设备，包括：
处理器，被配置为执行如下功能：为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
本公开的实施例还提供一种计算机存储介质，包括指令，当所述指令在计算机运行时，使得计算机执行如上所述的第一节点或者第二节点侧的方法。
本公开的上述实施例中，通过第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态；基于CA的PDCP重复机制，在CU/DU分离的场景下，第一节点为CU，第二节点为DU，本公开的实施例给出了如何在配置基于CA的PDCP重复机制的同时，指示当前承载的UL的PDCP重复机制的状态(即激活或者去激活)以及后续DU的行为。同时，在MR-DC的场景下，第一节点为MN，第二节点为SN，本公开的实施例给出了如何在配置基于DC的PDCP重复机制的同时指示该承载的UL的PDCP重复机制的状态，即激活或者去激活以及后续SN的行为。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存 储程序代码的介质。
此外，需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行，某些步骤可以并行或彼此独立地执行。对本领域的普通技术人员而言，能够理解本公开的方法和装置的全部或者任何步骤或者部件，可以在任何计算装置(包括处理器、存储介质等)或者计算装置的网络中，以硬件、固件、软件或者它们的组合加以实现，这是本领域普通技术人员在阅读了本公开的说明的情况下运用他们的基本编程技能就能实现的。
因此，本公开的目的还可以通过在任何计算装置上运行一个程序或者一组程序来实现。所述计算装置可以是公知的通用装置。因此，本公开的目的也可以仅仅通过提供包含实现所述方法或者装置的程序代码的程序产品来实现。也就是说，这样的程序产品也构成本公开，并且存储有这样的程序产品的存储介质也构成本公开。显然，所述存储介质可以是任何公知的存储介质或者将来所开发出来的任何存储介质。还需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行。某些步骤可以并行或彼此独立地执行。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (25)

  1. 一种分组数据汇聚协议PDCP重复机制的激活方法，包括：
    第二节点接收第一节点为承载配置PDCP重复机制时发送的通知消息；
    所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
  2. 根据权利要求1所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
  3. 根据权利要求2所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，所述第二节点在接收到所述通知消息后，更改所述承载的上行链路的PDCP重复机制的激活或者去激活状态，包括：
    所述第二节点接收到所述通知消息携带的激活/去激活所述承载的上行链路的PDCP重复机制的指示信息后，更改所述承载的上行链路的PDCP重复机制的激活/去激活状态。
  4. 根据权利要求3所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，所述第二节点更改所述承载的上行链路的PDCP重复机制的激活/去激活状态，包括：
    所述第二节点通过介质访问控制控制单元MAC CE信令，更改所述承载的上行链路的激活/去激活状态。
  5. 根据权利要求4所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，所述第二节点接收到所述通知消息携带的激活所述承载的上行链路的PDCP重复机制的指示信息后，或者所述第二节点更改所述承载的上行链路的去激活状态为激活状态后，还包括：
    所述第二节点根据所述承载的上行链路的激活状态，为所述承载提供相应优先级的服务。
  6. 根据权利要求1所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息；
    其中，所述第二节点在接收到所述通知消息后，确定所述承载的上行链 路的PDCP重复机制的激活或者去激活状态，包括：
    所述第二节点在接收到所述通知消息后，在确定激活所述承载的上行链路的PDCP重复机制时，向所述第一节点发送响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
  7. 根据权利要求1-6任一项所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，
    基于载波聚合CA的PDCP重复机制，在中心节点CU/分布DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
    基于双连接DC的PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。
  8. 一种分组数据汇聚协议PDCP重复机制的激活方法，包括：第一节点为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
  9. 根据权利要求8述的分组数据汇聚协议PDCP重复机制的激活方法，其中，所述第一节点根据所述第二节点上报的辅助信息，为承载配置PDCP重复机制；
    其中，所述辅助信息包括：第二节点是否支持载波聚合CA场景、高可靠超低时延通信URLLC业务、所述第二节点当前支持的信道的情况信息中的至少一项。
  10. 根据权利要求8所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，
    所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
  11. 根据权利要求8所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息；
    其中，第一节点向第二节点发送通知消息后还包括：
    所述第一节点接收所述第二节点根据所述通知消息，在确定激活所述承载的上行链路的PDCP重复机制时，发送的响应消息，所述响应消息中携带 有激活所述承载的上行链路的PDCP重复机制的指示信息。
  12. 根据权利要求8-11任一项所述的分组数据汇聚协议PDCP重复机制的激活方法，其中，
    基于载波聚合CA的PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
    基于双连接DC的PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。
  13. 一种节点设备，包括：
    收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，
    所述收发机，用于接收第一节点为承载配置PDCP重复机制时发送的通知消息；
    所述处理器，用于在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
  14. 根据权利要求13所述的节点设备，其中，所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息；
    其中，所述处理器在所述收发机接收到所述通知消息携带的激活/去激活所述承载的上行链路的PDCP重复机制的指示信息后，更改所述承载的上行链路的PDCP重复机制的激活/去激活状态；
    其中，所述收发机还用于通过介质访问控制控制单元MAC CE信令，更改所述承载的上行链路的激活/去激活状态；
    其中，所述处理器还用于根据所述承载的上行链路的激活状态，为所述承载提供相应优先级的服务。
  15. 根据权利要求13所述的节点设备，其中，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息；
    其中，所述收发机在接收到所述通知消息后，在确定激活所述承载的上行链路的PDCP重复机制时，向所述第一节点发送响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
  16. 根据权利要求13-15任一项所述的节点设备，其中，
    基于载波聚合CA的分组数据汇聚协议PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
    基于双连接DC的分组数据汇聚协议PDCP重复机制，所述第一节点为主节点MN时，所述第二节点为辅节点SN。
  17. 一种节点设备，包括：
    收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，
    所述收发机，用于为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
  18. 根据权利要求17述的节点设备，其中，所述收发机根据所述第二节点上报的辅助信息，为承载配置PDCP重复机制。
  19. 根据权利要求17所述的节点设备，其中，所述辅助信息包括：第二节点是否支持载波聚合CA场景、高可靠超低时延通信URLLC业务、所述第二节点当前支持的信道的情况信息中的至少一项。
  20. 根据权利要求17所述的节点设备，其中，
    所述通知消息携带有所述承载被配置PDCP重复机制以及激活/去激活所述承载的上行链路的PDCP重复机制的指示信息。
  21. 根据权利要求17所述的节点设备，其特征在于，所述通知消息携带有所述承载被配置PDCP重复机制的指示信息；
    其中，所述收发机还用于，接收所述第二节点根据所述通知消息，在确定激活所述承载的上行链路的PDCP重复机制时，发送的响应消息，所述响应消息中携带有激活所述承载的上行链路的PDCP重复机制的指示信息。
  22. 根据权利要求17-21任一项所述的节点设备，其中，
    基于载波聚合CA的PDCP重复机制，在中心节点CU/分布节点DU分离的场景下，所述第一节点为中心节点时，所述第二节点为分布节点；或者
    基于双连接DC的PDCP重复机制，所述第一节点为主节点MN时，所 述第二节点为辅节点SN。
  23. 一种PDCP重复机制的激活装置，包括：
    收发模块，用于接收第一节点为承载配置PDCP重复机制时发送的通知消息；
    处理模块，用于在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
  24. 一种分组数据汇聚协议PDCP重复机制的激活装置，包括：
    收发模块，用于为承载配置PDCP重复机制时，向第二节点发送通知消息；使所述第二节点在接收到所述通知消息后，更改或者确定所述承载的上行链路的PDCP重复机制的激活或者去激活状态。
  25. 一种计算机存储介质，包括指令，当所述指令在计算机运行时，使得计算机执行如权利要求1-7任一项所述的方法，或者使得计算机执行如权利要求8-12任一项所述的方法。
PCT/CN2019/074403 2018-02-09 2019-02-01 分组数据汇聚协议pdcp重复机制的激活方法及节点设备 WO2019154317A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP19751843.4A EP3751955B1 (en) 2018-02-09 2019-02-01 Methods for activating packet data convergence protocol (pdcp) repetition mechanism and node devices
US16/967,669 US11729846B2 (en) 2018-02-09 2019-02-01 Method for activating packet data convergence protocol duplication and node device
KR1020207025703A KR102389742B1 (ko) 2018-02-09 2019-02-01 Pdcp 중복 메커니즘의 활성화 방법 및 노드 기기

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810133812.1 2018-02-09
CN201810133812.1A CN110139397B (zh) 2018-02-09 2018-02-09 一种分组数据汇聚协议pdcp重复机制的激活方法及节点设备

Publications (1)

Publication Number Publication Date
WO2019154317A1 true WO2019154317A1 (zh) 2019-08-15

Family

ID=67547847

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074403 WO2019154317A1 (zh) 2018-02-09 2019-02-01 分组数据汇聚协议pdcp重复机制的激活方法及节点设备

Country Status (5)

Country Link
US (1) US11729846B2 (zh)
EP (1) EP3751955B1 (zh)
KR (1) KR102389742B1 (zh)
CN (1) CN110139397B (zh)
WO (1) WO2019154317A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11212695B2 (en) * 2018-02-15 2021-12-28 Qualcomm Incorporated Configuration, activation and deactivation of packet duplication
WO2019245339A1 (ko) * 2018-06-21 2019-12-26 삼성전자주식회사 이동 통신 시스템에서 기지국 노드 간 패킷 복제 동작 동기화 방법 및 장치
KR20190143789A (ko) * 2018-06-21 2019-12-31 삼성전자주식회사 이동 통신 시스템에서 기지국 노드 간 패킷 복제 동작 동기화 방법 및 장치
CN110971351B (zh) * 2018-09-28 2021-12-14 华为技术有限公司 一种协调重复传输的方法
CN112583530B (zh) * 2019-09-27 2022-04-15 大唐移动通信设备有限公司 一种数据传输方法、装置及设备
CA3153036A1 (en) * 2019-09-30 2021-04-08 Qiang Fan Communication method, apparatus, and system
CN110519307A (zh) * 2019-10-10 2019-11-29 重庆邮电大学 一种基于分组数据汇聚协议复制的数据发送方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107241164A (zh) * 2017-05-05 2017-10-10 电信科学技术研究院 一种无线承载重复传输的处理方法及装置
CN107342851A (zh) * 2017-06-15 2017-11-10 电信科学技术研究院 一种重复传输的配置及重复传输方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1503606B1 (en) * 2003-07-31 2008-03-26 Nokia Siemens Networks Gmbh & Co. Kg Common radio resource management method in a multi-rat cellular telephone network
CN103796287B (zh) * 2012-11-02 2019-09-10 北京三星通信技术研究有限公司 一种异构网络下的数据传输方法及系统
US10039086B2 (en) * 2013-11-11 2018-07-31 Electronics And Telecommunications Research Institute Communication method and apparatus in network environment where terminal may have dual connectivity to multiple base stations
KR102669847B1 (ko) * 2017-01-13 2024-05-28 삼성전자 주식회사 무선 통신 시스템에서 데이터 패킷을 전송하는 방법 및 장치
US10805836B2 (en) * 2017-05-05 2020-10-13 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (PDCP) entity
CN108401484B (zh) * 2017-08-21 2023-02-17 北京小米移动软件有限公司 数据传输方法及装置
US10687248B2 (en) * 2017-09-25 2020-06-16 Ofinno, Llc Packet duplication activation and deactivation
EP3536021B1 (en) 2017-09-28 2020-08-05 Ofinno, LLC Packet duplication activation signaling
US20200382240A1 (en) * 2018-01-09 2020-12-03 Telefonaktiebolaget Lm Ericsson (Publ) PDCP Duplication Configuration Over E1
EP3512140A1 (en) 2018-01-11 2019-07-17 Comcast Cable Communications LLC Cell configuration for packet duplication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107241164A (zh) * 2017-05-05 2017-10-10 电信科学技术研究院 一种无线承载重复传输的处理方法及装置
CN107342851A (zh) * 2017-06-15 2017-11-10 电信科学技术研究院 一种重复传输的配置及重复传输方法及装置

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CATT: "Discussion on CA Based PDCP Duplication", 3GPP TSG-RAN WG3 MEETING #97BIS R3-173593, 13 October 2017 (2017-10-13), XP051344018 *
CATT: "Discussion on CA Based PDCP Duplication", 3GPP TSG-RAN WG3#98 R3-174533, 1 December 2017 (2017-12-01), XP051373144 *
HUAWEI.: "PDCP Duplication for CU-DU", 3GPP TSG RAN WG3 MEETING #97 R3-173128, 25 August 2017 (2017-08-25), XP051319959 *
HUAWEI: "Email Discussion Summary on Control of UL PDCP Duplication", 3GPP TSG-RAN2#98 R2-1704834, 19 May 2017 (2017-05-19), XP051285817 *
ZTE: "Consideration on the Activation/Deactivation of Data Duplication for CA", 3GPP TSG-RAN WG2 MEETING #98 R2-1704660, 19 May 2017 (2017-05-19), XP051275205 *

Also Published As

Publication number Publication date
CN110139397B (zh) 2021-04-06
US20210227606A1 (en) 2021-07-22
EP3751955A1 (en) 2020-12-16
US11729846B2 (en) 2023-08-15
CN110139397A (zh) 2019-08-16
KR20200117005A (ko) 2020-10-13
KR102389742B1 (ko) 2022-04-21
EP3751955A4 (en) 2021-03-17
EP3751955B1 (en) 2024-07-24

Similar Documents

Publication Publication Date Title
WO2019154317A1 (zh) 分组数据汇聚协议pdcp重复机制的激活方法及节点设备
KR102345654B1 (ko) 이중 접속 수립 방법 및 디바이스
CN108924871B (zh) 无线配置方法、用户设备和基站
US9313820B2 (en) Link failure recovery method and apparatus
CN111278167B (zh) 无线链路失败处理方法及相关产品
RU2763776C1 (ru) Способ, устройство и средство получения информации и компьютерный носитель для хранения информации
US20230180338A1 (en) Communication control method
CN113170416A (zh) 一种数据传输方法及装置
US11963248B2 (en) Small data transmission (SDT) procedures and failure recovery during an inactive state
US11601954B2 (en) Data sending method and apparatus, storage medium, and sending end
CN112073998A (zh) 提高无线通信系统中的服务可靠性的方法和装置
EP3103307A1 (en) Methods, apparatus and computer programs for performing radio bearer mapping in dual connectivity
WO2019153928A1 (zh) Rrc状态转换方法、终端、cu、du和计算机可读存储介质
WO2019140955A1 (zh) 地址发送的方法、装置及存储介质
TWI736263B (zh) 通訊設備、方法及電腦程式
CN114303441A (zh) 5g中的rrc非活动的高效上下文处理
US11601841B2 (en) Radio station, radio communication method, non-transitory computer readable medium, and radio communication system
CN109716855A (zh) 信令控制传输方法及相关产品
JP6341519B2 (ja) セカンダリセルを構成するための方法および装置、ならびにホスト
WO2021169412A1 (zh) 信息同步方法和装置、电子设备、计算机可读存储介质
US11265730B2 (en) Data processing method adapted to access network architecture, access network architecture system and storage medium
TW201834496A (zh) 處理網路端切片資訊的裝置及方法
JP6247767B2 (ja) サービス先取り方法、装置および基地局
CN111418229B (zh) 数据复制传输功能的配置方法、网络设备及终端设备
CN109644101B (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: 19751843

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207025703

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019751843

Country of ref document: EP

Effective date: 20200909