WO2020164556A1 - 一种实体建立的处理方法及装置 - Google Patents

一种实体建立的处理方法及装置 Download PDF

Info

Publication number
WO2020164556A1
WO2020164556A1 PCT/CN2020/075144 CN2020075144W WO2020164556A1 WO 2020164556 A1 WO2020164556 A1 WO 2020164556A1 CN 2020075144 W CN2020075144 W CN 2020075144W WO 2020164556 A1 WO2020164556 A1 WO 2020164556A1
Authority
WO
WIPO (PCT)
Prior art keywords
side device
terminal
pdcp
pdcp entity
network
Prior art date
Application number
PCT/CN2020/075144
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 EP20756624.1A priority Critical patent/EP3913840B1/en
Publication of WO2020164556A1 publication Critical patent/WO2020164556A1/zh
Priority to US17/401,963 priority patent/US12082305B2/en

Links

Images

Classifications

    • 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/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • 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
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H04L1/0018—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement based on latency requirement
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1832—Details of sliding window management
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/187—Details of sliding window management
    • 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
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • 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/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a processing method and device for entity establishment.
  • the Packet Data Convergence Protocol is an important protocol in the protocol stack of the Long Term Evolution (LTE) system.
  • the terminal-side device and the network-side device can perform header compression/decompression, encryption/decryption, and integrity protection operations on the received data packet through the PDCP layer.
  • the PDCP SDU can be delivered in order according to the serial number (SN) of the PDCP SDU.
  • the terminal-side device or the network-side device as the sending end maintains a state variable TX_NEXT: this state variable indicates the PDCP SN of the next PDCP SDU to be sent.
  • TX_NEXT this state variable indicates the PDCP SN of the next PDCP SDU to be sent.
  • Second PDCP SDU and then submit the second PDCP SDU first.
  • a state variable RX_NEXT will be maintained, which indicates the PDCP SN of the next PDCP SDU expected to be received.
  • the PDCP SN in the PDCP SDU sent by the terminal side device to the network side device is maintained by the terminal side device; the PDCP SN in the PDCP SDU sent by the network side device to the terminal side device is performed by the network side The equipment is maintained.
  • the terminal-side device triggers the re-establishment of the PDCP entity in the terminal-side device.
  • the state variables TX_NEXT and RX_NEXT are reset to the initial value 0.
  • the terminal-side device starts the reordering timer and waits until the reordering timer The received PDCP SDU can be delivered to the upper layer of the PDCP layer only after the timeout, which adds additional delay.
  • the PDCP SN of the PDCP SDU received by the network side device is not 0, and the reordering timer is also turned on, which also increases the delay.
  • the embodiments of the present application provide a processing method and device for entity establishment to solve the problem of how to reduce the transmission delay of data when the PDCP entity is re-established.
  • an embodiment of the present application provides a processing method for entity establishment, the method includes: a terminal side device receives first indication information from a first network side device, and the first indication information triggers re-establishment of the terminal side
  • the first packet data aggregation protocol PDCP entity of the device in the case that the first bearer corresponding to the first PDCP entity is not a radio bearer that repeats transmission between the terminal side device and the core network side device, and in the case of In the process of re-establishing the first PDCP entity by the terminal-side device, the parameters of the first PDCP entity are set to initial values; wherein, the parameters of the first PDCP include a first parameter, a second parameter, and a third parameter.
  • the first parameter is used to indicate the sequence number or count value of the next PDCP service data unit SDU that the first PDCP entity expects to receive;
  • the second parameter is used to indicate the first PDCP entity The sequence number or count value of the next PDCP SDU to be sent by a PDCP entity;
  • the third parameter is used to indicate the sequence number or count value of the first PDCP SDU that is not submitted to the upper layer by the first PDCP entity.
  • the terminal-side device may not completely set the first parameter, the second parameter, and the third parameter of the first PDCP entity to initial values, but may set some parameters to Initial value.
  • the first parameter when the serial number of the PDCP SDU received by the terminal-side device through the first PDCP entity is the value indicated by the first parameter, the first parameter before the re-establishment of the first PDCP entity can be used to continue Receive the PDCP SDU from the core network device, so as to maintain the continuity of the received PDCP SDU sequence number, and prevent the terminal side device from resetting the first parameter, but the first network side device continues to start with the PDCP SDU sequence number before resetting
  • the PDCP SDU is sent by numbering, causing the terminal-side device to mistakenly believe that the PDCP SDU has packet loss, and repeatedly starting the reordering timer, which delays the delivery of data packets to the upper layer and increases the transmission delay
  • the terminal-side device can continue to use the second parameter before the first PDCP entity to re-establish the PDCP SDU, so as to maintain the continuity of the PDCP SDU sequence number sent and received, and reduce the PDCP SDU Transmission delay; when the third parameter is not set to the initial value, the terminal-side device determines the sequence number or count value of the first PDCP SDU that is not submitted to the upper layer according to the third parameter as soon as possible, thereby reducing the processing time of PDCP SDU Extension.
  • the terminal-side device In the process of re-establishing the first PDCP entity, the parameters of the first PDCP entity are kept unchanged.
  • the method further includes: the terminal-side device receives second indication information from the first network-side device, the second indication information indicating that the parameters of the first PDCP entity Set to the initial value.
  • the method further includes: the terminal-side device receives third indication information from the first network-side device, the third indication information indicating that the first bearer is not used for A radio bearer for repeated transmission between the terminal side device and the core network side device.
  • the terminal-side device can accurately determine whether the first bearer is a radio bearer that performs repeated transmission.
  • the first bearer is an unacknowledged mode UM bearer.
  • an embodiment of the present application provides a processing method for entity establishment, including: a terminal-side device receives first information, and the first information triggers the establishment of a first packet data aggregation protocol PDCP entity; The first PDCP entity is described, and second information is sent to the first network side device, where the second information is used to indicate the sequence number or count value of the next PDCP service data unit SDU to be sent by the first PDCP entity.
  • the terminal side device sends the second information to the first network side device, so that when the first network side device receives the PDCP SDU of the terminal side device, it can use the PDCP SDU sequence number or count value indicated by the second information
  • the first network-side device mistakenly believes that the PDCP SDU has packet loss, and repeatedly starts the reordering timer, which causes delay in delivering data packets to the upper layer and increases transmission delay.
  • the first bearer corresponding to the first PDCP entity is a radio bearer that performs repeated transmission between the terminal side device and the core network side device.
  • the method further includes: the terminal-side device sends third information to the first network-side device, the third information indicating that the first PDCP entity expects to receive the next PDCP SDU serial number or count value.
  • the method further includes: the terminal side device sending fourth information to the first network side device, the fourth information instructing the terminal side device to send the second information.
  • the terminal-side device further includes a second PDCP entity, and the first bearer corresponding to the first PDCP entity and the second bearer corresponding to the second PDCP entity are a pair for repeating Transmission bearer; the method further includes: the terminal-side device determines the next PDCP service data unit SDU to be sent by the first PDCP entity of the terminal-side device according to the first variable of the second PDCP entity Sequence number or count value; wherein, the first variable of the second PDCP entity is used to indicate the sequence number or count value of the next PDCP SDU to be sent by the second PDCP entity.
  • the method further includes: the terminal side device determines the sequence number or count of the next PDCP SDU that the first PDCP entity expects to receive according to the second variable of the second PDCP entity value;
  • the second variable of the second PDCP entity is used to indicate the sequence number or the count value of the next PDCP SDU that the second PDCP entity expects to receive.
  • the terminal side device is connected to the first network side device and the second network side device in a dual connection manner, and the terminal side device receives the first information, including: the terminal side device Receiving the first information from the first network side device; or, the terminal side device receives the first information from the second network side device.
  • an embodiment of the present application provides a processing method for entity establishment, including: a first network side device sends first information, and the first information triggers the terminal side device to establish a first packet data aggregation protocol PDCP entity; The first network side device receives second information, where the second information indicates the sequence number or count value of the next PDCP service data unit SDU to be sent by the first PDCP entity.
  • the first network side device when it receives the PDCP SDU of the terminal side device, it can use the PDCP SDU sequence number or count value indicated by the second information, so as to prevent the terminal side device from following the PDCP sent by the second PDCP entity
  • the sequence number of the SDU sends the PDCP SDU to the first network-side device, but the first network-side device receives the PDCP SDU according to the PDCP SDU sequence number starting from 0, which causes the first network-side device to mistakenly believe that the PDCP SDU has packet loss, and restarts repeatedly.
  • the sequencing timer causes the delay in delivering data packets to the upper layer and increases the transmission delay.
  • the method further includes: the first network side device receives third information, where the third information is used to indicate the sequence of the next PDCP SDU that the first PDCP entity expects to receive Number or count value.
  • the first network side device determines the sequence number of the next PDCP SDU to be sent to the terminal side device by the PDCP entity corresponding to the first PDCP entity according to the third information Or count value.
  • this application provides a device.
  • the apparatus has the function of implementing the terminal-side equipment involved in the first aspect to the second aspect.
  • the apparatus includes the terminal-side equipment executing the module or unit corresponding to the steps involved in the first aspect to the second aspect.
  • Means, the functions or units or means can be implemented by software, or by hardware, or by hardware executing corresponding software.
  • the device includes a processing unit and a transceiving unit, and the functions performed by the processing unit and the transceiving unit may correspond to the steps performed by the terminal-side equipment involved in the first to second aspects.
  • the device includes a processor, and may also include a transceiver.
  • the transceiver is used to send and receive signals, and the processor executes program instructions to accomplish any of the above-mentioned first to second aspects. The method executed by the terminal-side device in the design or implementation of the.
  • the apparatus may further include one or more memories, and the memories are used for coupling with the processor.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory stores necessary computer program instructions and/or data for realizing the functions of the terminal-side device involved in the first aspect to the second aspect.
  • the processor can execute the computer program instructions stored in the memory to complete the method executed by the terminal-side device in any possible design or implementation of the first aspect to the second aspect.
  • this application provides a device.
  • the device has the function of implementing the first network side device involved in the third aspect.
  • the device includes a module or unit or means corresponding to the first network side device to execute the steps involved in the third aspect.
  • the functions or units or means can be implemented by software, or by hardware, or by hardware executing corresponding software.
  • the device includes a processing unit and a transceiving unit.
  • the functions performed by the processing unit and the transceiving unit may correspond to the steps performed by the first network side device involved in the third aspect.
  • the communication device includes a processor, and may also include a transceiver.
  • the transceiver is used to send and receive signals, and the processor executes program instructions to complete any possible design in the third aspect. Or the method executed by the network side device in the implementation mode.
  • the apparatus may further include one or more memories, and the memories are used for coupling with the processor.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory stores necessary computer program instructions and/or data for realizing the functions of the first network side device involved in the third aspect.
  • the processor can execute the computer program instructions stored in the memory to complete the method executed by the first network side device in any possible design or implementation of the third aspect.
  • the present application provides a chip that can communicate with a memory, or the chip can include a memory, and the chip executes the program instructions stored in the memory to implement the first aspect to the first aspect.
  • the present application provides a computer storage medium that stores computer-readable instructions, and when the computer-readable instructions are executed, the terminal-side devices involved in the first to third aspects are realized Or the corresponding function of the first network side device.
  • this application also provides a computer program product containing a software program, which when running on a computer, enables the corresponding functions of the terminal side device or the first network side device designed in the first to third aspects to be realized .
  • the present application also provides a communication system, which includes the terminal-side device and/or the first network-side device involved in the above-mentioned first aspect to the third aspect.
  • FIG. 1(a) is a schematic diagram of the architecture of a communication system applicable to the method provided by the embodiment of the present application;
  • FIG. 1(b) is a schematic diagram of the architecture of a communication system applicable to the method provided by the embodiment of the present application;
  • Figure 2 is a schematic diagram of a network connection provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram of a network connection provided by an embodiment of this application.
  • FIG. 4 is a schematic flowchart of a processing method for entity establishment according to an embodiment of the application.
  • FIG. 5 is a schematic flowchart of a method for processing entity establishment according to an embodiment of the application.
  • FIG. 6 is a schematic flowchart of a method for processing entity establishment according to an embodiment of the application.
  • FIG. 7 is a schematic flowchart of an entity re-establishment provided by an embodiment of this application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of a terminal-side device provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a network side device provided by an embodiment of this application.
  • the embodiments of this application can be applied to various mobile communication systems, such as: new radio (NR) system, code division multiple access (CDMA) system, wideband code division multiple access (wideband code division multiple access) , WCDMA) system, long term evolution (LTE) system, advanced long term evolution (LTE-A) system, evolved long term evolution (eLTE) system, future communication system, etc.
  • NR new radio
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • LTE long term evolution
  • LTE-A advanced long term evolution
  • eLTE evolved long term evolution
  • future communication system etc.
  • Other communication systems specifically, are not restricted here.
  • the communication system shown in FIG. 1(a) is taken as an example to describe in detail the communication system applicable to the embodiments of the present application.
  • Fig. 1(a) shows a schematic diagram of the architecture of a communication system suitable for the method provided in the embodiments of the present application.
  • the communication system includes a terminal side device 101, a main network side device 102, a secondary network side device 103, a user plane function (UPF) device 104, and a data network (Data Network, DN).
  • DN data network
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Funtion
  • the terminal side device 101 can separately establish a connection with the main network side device 102 or the auxiliary network side device 103; the terminal side device 101 can also be connected with the main network side device 102 and the auxiliary network side device 103 through dual connectivity (DC) .
  • DC dual connectivity
  • the primary network side device 102 or the secondary network side device 103 provides wireless access services for the terminal side device 101, etc.; the UPF device 104 is mainly responsible for forwarding, billing, and other processing of the message of the terminal side device 101.
  • the messages here include but It is not limited to packets such as PDCP and SDU.
  • the DN105 may refer to a network that provides services for the terminal-side device 101, for example, it may provide the terminal-side device 101 with an Internet access function.
  • the terminal-side device is a device with a wireless transceiver function or a chip that can be installed in the device.
  • the device with wireless transceiver function may also be called user equipment (UE), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile equipment, user terminal, user agent Or user device.
  • UE user equipment
  • the terminal-side devices in the embodiments of the present application may be mobile phones, tablets, computers with wireless transceiver functions, virtual reality (VR) terminals, augmented reality (augmented) Reality, AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, and wireless terminals in smart grid (smart grid) , Wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.
  • VR virtual reality
  • AR augmented reality
  • wireless terminals in industrial control wireless terminals in self-driving
  • wireless terminals in remote medical and wireless terminals in smart grid (smart grid)
  • Wireless terminal in transportation safety wireless terminal in smart city, wireless terminal in smart home, etc.
  • the network side device may be a radio access network device under various standards, such as an evolved Node B (eNB), a radio network controller (RNC) or a Node B ( Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit) , BBU), the access point (AP), wireless relay node, wireless backhaul node, transmission and reception point (transmission and reception point, TRP or transmission point, TP) in the wireless fidelity (WIFI) system ), etc., it can also be the gNB or transmission point (TRP or TP) in the 5G (NR) system, one or a group of antenna panels (including multiple antenna panels) of the base station in the 5G system, or it can also constitute a gNB Or a network node of a transmission point, such as a baseband unit, or a DU under a centralized unit
  • eNB evolved No
  • the main functions of the AMF device 106 include the termination point of the control plane of the wireless access network, the termination point of non-access signaling, mobility management, lawful monitoring, access authorization or authentication, and so on.
  • the SMF device 107 is mainly responsible for establishing sessions and managing sessions for the terminal side device 101.
  • the SMF device 107 can select an appropriate UPF device for the terminal-side device 101 according to the location information of the terminal-side device 101.
  • the PCF device 108 is mainly responsible for functions such as establishment, release, and modification of the user plane transmission path.
  • Figure 1(a) also shows possible implementations of the interfaces in each device, such as the N2 interface between the main network side device 102 and the AMF device 106, and the N3 interface between the main network side device 102 and the UPF device 104 Wait, I won't repeat them here.
  • the PDCP layer message replication technology is used to improve transmission reliability, that is, between the terminal side device and the network side device, two identical PDCP layer messages can be transmitted through two independent transmission paths.
  • CA carrier aggregation
  • DC dual connectivity
  • the terminal side device 202 and the network side device 204 include two data radio bears (DRB): DRB1 and DRB2, each DRB corresponds to a PDCP entity (entity) , PDCP layer messages, that is, PDCP SDU are transmitted through the DRB corresponding to the PDCP entity.
  • DRB data radio bears
  • GPRS General Packet Radio Service
  • GTP tunnel protocol
  • tunnel 2 corresponds to DRB2.
  • the network-side device 204 copies the PDCP SDU received through tunnel 1 or tunnel 2 to obtain PDCP SDU1 and PDCP SDU2 which is the same as PDCP SDU1.
  • the two PDCP SDUs have the same serial number; PDCP SDU1 is sent to the terminal side device 202 through DRB1 between the network side device 204 and the terminal side device 202, and PDCP SDU2 is sent through DRB2 between the network side device 204 and the terminal side device 202 Send to the terminal side device 202.
  • the terminal-side device 202 When the terminal-side device 202 receives the PDCP SDU1 and the PDCP SDU2, it may perform deduplication processing on the received PDCP SDU according to the sequence number of the PDCP SDU.
  • the core network side device 206 may be a UPF device.
  • the terminal side device 101 establishes a connection with the network side device 204 and the network side device 208 at the same time, and the network side device 204 is the main access Network equipment, the network side equipment 208 is a secondary access network equipment, where the coverage of the primary access network equipment is the primary cell group, and the coverage of the secondary access network equipment is the secondary cell group.
  • the terminal side device 202 and the network side device 204 include DRB1; the terminal side device 202 and the network side device 208 include DRB2.
  • DRB1 and DRB2 may share one PDCP entity in the terminal side device 202, and DRB1 and DRB2 may also have different PDCP entities in the terminal side device 202.
  • the network-side device 204 copies the PDCP SDU received through tunnel 1 or tunnel 2 to obtain PDCP SDU1 and PDCP SDU2.
  • the two PDCP SDUs have the same sequence number; PDCP SDU1 communicates with the terminal through the network-side device 204
  • the DRB1 between the side device 202 is sent to the terminal side device 202; the network side device 204 sends the PDCP SDU2 to the network side device 208, and the PDCP SDU2 is sent to the terminal side device through the DRB2 between the network side device 208 and the terminal side device 202 202.
  • the terminal-side device 202 receives the PDCP SDU1 and the PDCP SDU2, it may perform deduplication processing on the received PDCP SDU according to the sequence number of the PDCP SDU.
  • For the uplink direction please refer to the description in the downlink direction, which will not be repeated here.
  • the terminal-side device To prevent out-of-sequence of messages, take the terminal-side device as an example.
  • the terminal-side device delivers the received PDCP SDUs to the upper layer in the order of the sequence number of the PDCPSDU; accordingly, in the upstream direction, the terminal-side device will send The PDCP SDUs are delivered to the lower layer in the order of the sequence numbers of the PDCP SDUs.
  • the radio access network equipment will also be submitted in the order of the PDCP and SDU serial numbers, which will not be repeated here.
  • the terminal-side device maintains at least one PDCP entity parameter.
  • the parameters maintained by the terminal-side device include: sending-side variable TX_NEXT, first receiving-side variable RX_NEXT, second The receiving side variable RX_DELIV, the third receiving side variable RX_REORD, etc.
  • TX_NEXT is used to indicate the count (COUNT) value of the next PDCP SDU to be sent, the initial value of this parameter is 0;
  • RX_NEXT is used to indicate the count value of the next PDCP SDU expected to be received, the initial value of this parameter 0;
  • RX_DELIV is used to indicate the count value of the first PDCP SDU that is not delivered to the upper layer, and the initial value of this parameter is 0;
  • the third receiving-side variable RX_REORD is used to indicate the count value of the PDCP PDU that triggers the reordering timer.
  • the count value of PDCP SDU is composed of a hyperframe number (HFN) and a sequence number of PDCPSDU.
  • HFN is a value determined by the terminal side device and the radio access network device in the same way. For example, at the beginning, the serial number of PDCP SDU and the value of HFN are both 0.
  • the terminal side device sends a PDCP SDU
  • the serial number of PDCP SDU is increased by 1.
  • the serial number of PDCP SDU reaches the preset maximum value, For example, at 1024, the value of the serial number of the PDCP SDU is set to 0, and the value of HFN is increased by 1.
  • the radio access network equipment also determines the HFN in the same way.
  • the terminal side equipment and the radio access network equipment determine the same HFN. Since the HFN determined by the terminal-side device and the radio access network device is the same, the count value of the PDCPSDU can be determined by determining the sequence number of the PDCPSDU. It can be understood that the PDCPSDU and PDCP SN form a PDCP Data PDU, so the PDCP SN is also referred to as the PDCP SN number of the PDCP data PDU (Protocol Data Unit, protocol data unit).
  • the term "exemplary” is used as an example, illustration, or illustration. Any embodiment or design solution described as an "example” in this application should not be construed as being more preferable or advantageous than other embodiments or design solutions. Rather, the term example is used to present the concept in a concrete way.
  • the terminal-side device may establish a connection with the first network-side device alone, or may establish a connection with the first network-side device and the second network-side device in a dual connection manner.
  • the first network-side device can be the primary network-side device or the auxiliary network-side device. This is the case in this application. Not limited.
  • the terminal-side device and the first network-side device have established a first bearer, and the first bearer corresponds to the first PDCP entity of the terminal-side device.
  • the method includes:
  • Step 401 The terminal side device receives the first indication information from the first network side device.
  • the first indication information triggers the re-establishment of the first PDCP entity of the terminal side device.
  • the first indication information may be carried in a message sent by the first network side device, and the first indication information itself may also be the first indication information.
  • a message sent by the network-side device, for example, the first indication information may be a radio resource control (radio resource control, RRC) reconfiguration message, etc., which will not be described one by one here.
  • RRC radio resource control
  • the first indication information triggers the re-establishment of the first PDCP entity.
  • the first indication information is used to determine certain information established by the first PDCP entity, and may include multiple Kind of realization.
  • the first indication information may directly instruct the terminal-side device to re-establish the first PDCP entity of the terminal-side device; in another possible implementation manner, the first indication information may not directly indicate the terminal The side device re-establishes the first PDCP entity, but indirectly instructs the terminal side device to re-establish the first PDCP entity.
  • the first indication information may be used to notify the terminal-side device to change the encryption key used by the first PDCP entity, and the terminal-side device determines to change the encryption key according to the first indication information.
  • the first indication information can be used to notify the terminal-side device to perform full configuration reconfiguration.
  • the terminal-side device determines to perform the full configuration reconfiguration according to the first indication information.
  • the full configuration reconfiguration refers to the reconfiguration of the dedicated wireless parameter configuration except for the user identification and encryption key.
  • the first indication information can be used to notify the terminal-side device to add a bearer corresponding to the first PDCP entity, so that the terminal-side device is in the process of switching from the first network-side device to the second network-side device ,
  • the added bearer can be used to transmit and receive data through the core network side device.
  • the terminal side device can determine to re-establish the first PDCP entity at the same time according to the first indication information.
  • the core network side device refers to a UPF device. It should be noted that in the handover process, both the added bearer and the original bearer can send and receive repeated data through the core network device.
  • Step 402 In the case that the first bearer corresponding to the first PDCP entity is not a radio bearer for repeated transmission between the terminal-side device and the core network-side device, and the terminal-side device is based on the first bearer
  • the parameters of the first PDCP entity are set to initial values (for example, 0).
  • the terminal-side device includes only one PDCP entity (the first PDCP entity) in the PDCP layer, and the terminal-side device sets the parameters of the first PDCP entity to initial values in step 402.
  • the terminal-side device includes at least two PDCP entities in the PDCP layer, without loss of generality, taking the first PDCP entity and the second PDCP entity as examples.
  • the terminal-side device may set the parameters of the first PDCP entity to initial values.
  • the first PDCP entity and the second PDCP entity each maintain the parameters of their respective PDCP entities, then the two PDCP entities are both set to initial values during the process of being re-established.
  • the first bearer may be an unacknowledged mode (Unacknowledged Mode, UM) bearer.
  • UM Unacknowledged Mode
  • the first bearer corresponding to the first PDCP entity is a radio bearer that performs repeated transmissions between the terminal-side device and the core network-side device
  • the terminal-side device In a process in which the terminal-side device re-establishes the first PDCP entity according to the first indication information, the terminal-side device keeps the parameters of the first PDCP entity unchanged.
  • the first bearer may be an acknowledged mode (AM) bearer or an unacknowledged mode (UM) bearer.
  • the data transmitted in the AM bearer supports automatic repeat-reQuest (ARQ) at the radio link control protocol (Radio Link Control, RLC) layer; the data transmitted in the UM bearer does not support the RLC layer Automatic Repeat-reQuest (ARQ).
  • ARQ automatic repeat-reQuest
  • RLC Radio Link Control
  • the parameters of the first PDCP include at least one of a first parameter, a second parameter, and a third parameter
  • the first parameter is used to indicate the sequence of the next PDCPSDU that the first PDCP entity expects to receive Number or count value
  • the second parameter is used to indicate the sequence number or count value of the next PDCP SDU to be sent by the first PDCP entity
  • the third parameter is used to indicate the first PDCP entity The serial number or count value of the PDCP SDU that has not been submitted to the upper layer.
  • the count value of PDCP SDU includes the serial numbers of HFN and PDCP SDU.
  • HFN is a known value for the terminal side device and the first network side device, and the HFN determination method can refer to the previous description .
  • the serial number of the PDCP SDU sent by the terminal-side device is maintained by the terminal-side device.
  • the terminal-side device newly establishes the first PDCP entity, the serial number of the PDCP SDU sent by the terminal-side device starts from 0, according to The sequence is increasing. For example, the terminal-side device sends 3 PDCP SDUs, and the sequence numbers of the above 3 PDCP SDUs are 0, 1, 2 in sequence.
  • the serial number of the PDCP SDU received by the terminal-side device is maintained by the network-side device.
  • the network-side device determines the sequence number in the downlink data packet received by the core network device, and the network-side device can Directly use the sequence number or part of the sequence number in the general packet radio service (General Packet Radio Service, GPRS) tunneling protocol user plane (GPRS Tunnelling Protocol User Plane, GTP-U) header field in the downlink data packet as the PDCP SDU sequence
  • the serial number of the PDCP SDU can also be derived from the serial number in the GTP-U header field.
  • the core network device may be a UPF device.
  • the sequence number of the PDCP SDU currently received by the terminal-side device is N
  • the sequence number of the next PDCPSDU expected to be received indicated by the first parameter is N+1
  • N is an integer greater than or equal to 0
  • the sequence number of the PDCP SDU currently sent by the terminal-side device is M
  • the sequence number of the next PDCP SDU to be sent indicated by the second parameter is M+1, and M is an integer greater than or equal to 0
  • the terminal-side device Currently, the serial number of the first PDCP SDU that is not delivered to the upper layer is K, and the serial number of the first PDCP SDU that is not delivered to the upper layer indicated by the third parameter is K, and K is an integer greater than or equal to 0.
  • the first parameter, the second parameter, and the third parameter indicate the count value of the PDCP SDU, reference may be made to the above description, which is not repeated here.
  • the initial value of the first parameter, the initial value of the second parameter, and the initial value of the third parameter may all be zero.
  • the first network side device forwards the uplink data sent by the terminal side device to the core network side device; correspondingly, the downlink data sent by the first network side device to the terminal side device
  • the data comes from the core network side device, that is, the first network side device is equivalent to the forwarding device between the terminal side device and the core network side device.
  • the terminal-side device can use the PDCP layer message replication technology to transmit PDCP SDUs.
  • the terminal-side device establishes two radio bearers.
  • the two radio bearers transmit the same PDCP SDU.
  • the radio bearer may be referred to as a radio bearer used for repeated transmission between the terminal side device and the core network side device.
  • DRB1 and DRB2 in Figure 2 are radio bearers used for repeated transmission between the terminal side device and the core network side device;
  • DRB1 and DRB2 in Figure 3 are also used for the terminal side device and the core network side. Radio bearer for repeated transmission between devices. It can be understood that DRB1 and DRB2 can use the same RB identifier but different logical channel identifiers.
  • DRB1 and DRB2 can use different RB identifiers. It should be noted that when DRB1 and DRB2 use the same RB identifier, DRB1 and DRB2 share a PDCP entity in the terminal side device; when DRB1 and DRB2 use different RB identifiers, DRB1 and DRB2 correspond to different PDCPs in the terminal side device. entity. Further, DRB1 and DRB2 transmit repeated data packets, and the repeated data packets belong to the same Quality of Service (QoS) flow.
  • QoS Quality of Service
  • a certain PDCP SDU sent by the terminal-side device to the core network device is only transmitted through one radio bearer or one of at least two logical channels.
  • the PDCP SDU sent by the core network device to the terminal-side device is only transmitted through one radio bearer or one of at least two logical channels, so the radio bearer is not between the terminal-side device and the core network-side device.
  • the upper layer of the PDCP entity may refer to the protocol layer located above the PDCP layer in the protocol stack.
  • it may be an application layer or a service data adaptation protocol (Service Data Adaptation Protocol, SDAP) layer.
  • SDAP Service Data Adaptation Protocol
  • the terminal-side device may not completely set the first parameter, the second parameter, and the third parameter of the first PDCP entity to initial values, but may set some parameters to Initial value.
  • the first parameter when the serial number of the PDCP SDU received by the terminal-side device through the first PDCP entity is the value indicated by the first parameter, the first parameter before the re-establishment of the first PDCP entity can be used to continue Receive the PDCP SDU from the core network device, so as to maintain the continuity of the received PDCP SDU sequence number, and prevent the terminal side device from resetting the first parameter, but the first network side device continues to start with the PDCP SDU sequence number before resetting
  • the PDCP SDU is sent by numbering, causing the terminal-side device to mistakenly believe that the PDCP SDU has packet loss, and repeatedly starting the reordering timer, which delays the delivery of data packets to the upper layer and increases the transmission delay
  • the terminal-side device can continue to use the second parameter before the first PDCP entity to re-establish the PDCP SDU, so as to maintain the continuity of the PDCP SDU sequence number sent and received, and reduce the PDCP SDU Transmission delay; when the third parameter is not set to the initial value, the terminal-side device determines the sequence number or count value of the first PDCP SDU that is not submitted to the upper layer according to the third parameter as soon as possible, thereby reducing the processing time of PDCP SDU Extension.
  • the terminal-side device may also receive second indication information from the first network-side device, where the second indication information indicates to set the parameters of the first PDCP entity to the initial value.
  • the terminal-side device receives the second indication information, it can re-establish the first PDCP entity according to the first indication information, and in the process of re-establishing the first PDCP entity, re-establish the first PDCP entity according to the second indication information.
  • the parameters of the first PDCP entity are set to initial values.
  • the first bearer corresponding to the first PDCP entity may be a radio bearer that performs repeated transmissions between the terminal side device and the core network side device, or may not be between the terminal side device and the core network side device.
  • the second indication information may also indicate a bearer identifier or logical channel identifier corresponding to the first bearer, and the second indication information indicates to set the parameter of the first PDCP entity corresponding to the bearer identifier or logical channel identifier to an initial value.
  • the second indication information may be carried in a message sent by the first network side device, or may be an independent message.
  • the first indication information and the second indication information may be sent through the same message, or may be sent sequentially through different messages, which is not limited in the embodiment of the present application.
  • the terminal-side device may determine whether to set the parameter of the first PDCP entity to an initial value according to whether the second indication information exists. For example, when the terminal-side device does not receive the second indication information, it sets the parameters of the first PDCP entity to the initial value; when the terminal-side device receives the second indication information, it sets the parameters of the first PDCP entity Not set to the initial value.
  • the terminal-side device may determine whether to set the parameter of the first PDCP entity to the initial value according to the value indicated by the second indication information. For example, the value indicated by the second indication information is true and is not set to the initial value. The value indicated by the second indication information is false, which is set to the initial value.
  • the terminal-side device may determine whether the first bearer is a radio bearer used for repeated transmission between the terminal-side device and the core network-side device in multiple ways.
  • the terminal-side device may also receive third indication information from the first network-side device, where the third indication information indicates that the first bearer is not used for A radio bearer for repeated transmission between the terminal side device and the core network side device.
  • the terminal-side device may determine whether the first bearer is a radio bearer that performs repeated transmission according to the third indication information.
  • the terminal-side device and the first network-side device may pre-arranged when the first network-side device does not send the fourth instruction information or the terminal-side device does not receive the fourth instruction information When, it means that the first bearer is not a radio bearer used for repeated transmission between the terminal-side device and the UPF device.
  • the fourth indication information indicates that the first bearer is a radio bearer used for repeated transmission between the terminal-side device and the UPF device.
  • the terminal-side device may establish a connection with the first network-side device alone, or may establish a connection with the first network-side device and the second network-side device in a dual connection manner.
  • the first network-side device can be the primary network-side device or the auxiliary network-side device. This is the case in this application. Not limited.
  • the terminal-side device and the first network-side device have established a first bearer, and the first bearer corresponds to the first PDCP entity of the terminal-side device.
  • the method includes:
  • Step 501 The terminal-side device determines to set the parameters of the first PDCP entity to initial values.
  • the first PDCP parameter includes at least one of a first parameter, a second parameter, and a third parameter
  • the first parameter is used to indicate the next PDCP SDU that the first PDCP entity expects to receive Sequence number or count value
  • the second parameter is used to indicate the sequence number or count value of the next PDCP SDU to be sent by the first PDCP entity
  • the third parameter is used to indicate that the first PDCP entity is first The serial number or count value of a PDCP SDU that has not been submitted to the upper layer.
  • the terminal-side device may determine whether to set the parameter of the first PDCP entity to the initial value in various ways.
  • the terminal-side device may determine that the first bearer corresponding to the first PDCP entity is not a radio bearer used for repeated transmission between the terminal-side device and the core network-side device, it may It is determined to set the parameters of the first PDCP entity to initial values.
  • the terminal-side device specifically determines whether the first bearer is a radio bearer used for repeated transmission between the terminal-side device and the core network-side device may refer to the foregoing description, and will not be repeated here.
  • the terminal-side device may also receive second indication information from the first network-side device, where the second indication information indicates that the parameter of the first PDCP entity is set to an initial value.
  • the terminal-side device may receive the second indication information, it may be determined that in the process of re-establishing the first PDCP entity, the parameters of the first PDCP entity are set to initial values according to the second indication information.
  • the first bearer corresponding to the first PDCP entity may be a radio bearer that performs repeated transmissions between the terminal side device and the core network side device, or may not be between the terminal side device and the core network side device. A radio bearer with repeated transmissions between.
  • the second indication information may also indicate a bearer identifier or logical channel identifier corresponding to the first bearer, and the second indication information indicates to set the parameter of the first PDCP entity corresponding to the bearer identifier or logical channel identifier to an initial value. It should be noted that the second indication information may be carried by a message sent by the first network-side device, or may be an independent message, which is not limited in this embodiment of the application.
  • the terminal-side device may determine whether to set the parameter of the first PDCP entity to an initial value according to whether the second indication information exists. For example, when the terminal-side device does not receive the second indication information, it sets the parameters of the first PDCP entity to the initial value; when the terminal-side device receives the second indication information, it sets the parameters of the first PDCP entity Not set to the initial value.
  • the terminal-side device may determine whether to set the parameter of the first PDCP entity to the initial value according to the value in the second indication information. For example, the value in the second indication information is true and is not set as the initial value. The value in the second indication information is false, which is set to the initial value.
  • Step 502 The terminal-side device sets the parameters of the first PDCP entity to initial values during the process of re-establishing the first PDCP entity.
  • initial value of the first parameter, the initial value of the second parameter, and the initial value of the third parameter are all zero.
  • step 501 and step 502 For other content of step 501 and step 502, reference may be made to the description in step 401 to step 402, which will not be repeated here.
  • the network-side device when the terminal-side device re-establishes the PDCP entity, the network-side device also re-establishes the PDCP entity.
  • the terminal side device when the terminal side device establishes a connection with the first network side device and the second network side device, if only one of the first network side device or the second network side device re-establishes the PDCP entity , Will cause the maintenance state variables TX_NEXT and RX_NEXT in the network side device of the PDCP entity to be set to 0, but the PDCP SN of the PDCP SDU sent by the terminal side device may not be 0.
  • the network side device of the PDCP entity is re-established
  • the reordering timer is turned on, and the received PDCP SDU can not be delivered to the upper layer of the PDCP layer until the reordering timer expires, which adds additional delay.
  • the terminal side device when the terminal side device only establishes a connection with the second network side device, if the terminal side device establishes a connection with the first network side device again, the first network side device newly established
  • the state variables TX_NEXT and RX_NEXT of the PDCP entity are 0.
  • the sequence number of the PDCP SDU of the PDCP SDU sent by the terminal side device is not from 0
  • the first network side device receives the PDCP SDU sent by the terminal side device, and determines that the sequence number of the PDCP SDU is not 0, it starts the reordering timer and waits until the reordering timer expires before submitting the received PDCP SDU To the upper layer of the PDCP layer, additional delay is added.
  • FIG. 6 it is a schematic flowchart of a method for processing entity establishment according to an embodiment of this application.
  • the method flow shown in FIG. 6 can be applied to the network shown in FIG. 1.
  • the method includes:
  • Step 601 The first network side device sends first information, and the first information triggers the terminal side device to establish a first PDCP entity.
  • the first information triggers the terminal-side device to establish the first PDCP entity, which may refer to triggering the terminal-side device to re-establish the first PDCP entity, or it may refer to triggering the terminal-side device to newly establish the first PDCP entity.
  • the terminal side device before step 601, the terminal side device currently only establishes a connection with the second network side device.
  • the first information refers to triggering the terminal side device to newly establish a first PDCP entity. After the terminal-side device establishes a connection with the first network-side device, it can continue to maintain the connection with the second network-side device to achieve dual connections with the first network-side device and the second network-side device.
  • the terminal-side device newly establishes the first PDCP entity according to the first information.
  • the terminal-side device may only establish a connection with the second network-side device, and the first PDCP entity already exists.
  • the first information refers to triggering the terminal-side device to re-establish the first A PDCP entity
  • the first PDCP entity is used for the radio bearer established by the first network side device and the second network side device at the same time.
  • the terminal-side device can also disconnect from the second network-side device, which is equivalent to switching the terminal-side device from the second network-side device to the first network-side device. For example, after the terminal-side device sends a reconfiguration complete message (handover complete), the transmission on the bearer established with the second network-side device is stopped.
  • the terminal-side device may have established a connection with the first network-side device and the second network-side device in a dual-connection manner. At this time, the first PDCP entity already exists, and the terminal-side device re-establishes the first PDCP entity according to the first information.
  • the terminal-side device when the terminal-side device establishes a connection with the first network-side device and the second network-side device through dual connections, the first network-side device can be the main network-side device or the auxiliary network-side device.
  • the application embodiment does not limit this.
  • the embodiment of the application does not limit the name and implementation form of the first information.
  • the first information can be carried by a message sent by the first network side device, and the first information itself can also be a message sent by the first network side device, for example
  • the first information may be an RRC reconfiguration message, etc., which will not be illustrated one by one here.
  • the first information may directly instruct the terminal-side device to establish the first PDCP entity; in another possible implementation manner, the first information may not directly instruct the terminal-side device to establish The first PDCP entity instead indirectly instructs the terminal-side device to establish the first PDCP entity.
  • the first information can be used to notify the terminal-side device to change or increase the encryption key used by the first PDCP entity, and the terminal-side device determines to change or add the encryption key according to the first information. When encrypting the key, it is determined to establish the first PDCP entity at the same time.
  • the first PDCP entity already exists, and "establishing the first PDCP entity" can be understood as “reestablishing the first PDCP entity”.
  • the first information can be used to notify the terminal side device to perform full configuration reconfiguration. At this time, when the terminal side device determines to perform full configuration reconfiguration according to the first information, then It is determined that the first PDCP entity is established at the same time. In this case, the first PDCP entity already exists, and "establishing the first PDCP entity" can be understood as "reestablishing the first PDCP entity”.
  • the first information may be used to notify the terminal side device to add a first PDCP entity, so that the terminal side device can use the bearer corresponding to the first PDCP entity to transmit and receive data through the core network side device.
  • the terminal-side device can determine to establish the first PDCP entity at the same time according to the first information.
  • the first PDCP entity does not exist before, and "establishing the first PDCP entity" can be understood as “newly establishing the first PDCP entity" ".
  • the core network side device may refer to a UPF device.
  • Step 602 The terminal side device receives the first information.
  • the first information is sent by the first network-side device, that is, the first information received by the terminal-side device is from the first network-side device.
  • a network side device in another possible implementation manner, the first information is sent by a second network side device, that is, the first information received by the terminal side device comes from the second network side device.
  • the first network-side device can instruct the second network-side device to send the first information.
  • the first information may instruct the terminal-side device to send the second information. Further, the first information may also include second information indicating which bearer or logical channel to report by the terminal-side device, the protocol data unit session identifier, and the quality of service flow identifier.
  • Step 603 The terminal side device establishes the first PDCP entity according to the first information, and sends second information to the first network side device.
  • the second information is used to indicate the sequence number or count value of the next PDCP SDU to be sent by the first PDCP entity.
  • the second information may be used to indicate the sequence number or count value of the next PDCP SDU that the PDCP entity carrying on the first network device where the first PDCP entity is located expects to receive.
  • the first network side device determines the sequence number or count value of the next PDCPSDU expected to be received in the uplink according to the second information. For example, use the value in the second information to set the sequence number or count value of the next PDCP SDU expected to be received.
  • the second information may be carried by a message sent by the terminal side device, or may be an independent message. Further, in a possible implementation manner, the second information may also indicate which radio bearer or logical channel the second information is for, that is, indicate the radio bearer or logical channel corresponding to the first PDCP entity.
  • the terminal-side device has established a connection with the second network-side device, and the terminal-side device further includes a second PDCP entity, and the second PDCP entity corresponds to the second bearer.
  • the first bearer corresponding to the first PDCP entity and the second bearer corresponding to the second PDCP entity are a pair of bearers used for repeated transmission.
  • the terminal-side device can use the PDCP layer message replication technology to transmit PDCP SDU.
  • the terminal-side device establishes two radio bearers, and the two radio bearers transmit the same PDCP SDU. These two radio bearers can be referred to as radio bearers used for repeated transmission between the terminal side device and the core network side device.
  • DRB1 and DRB2 in Fig. 2 are radio bearers used for repeated transmission between the terminal side device and the core network side device.
  • the terminal-side device may determine the sequence number or count value of the next PDCPSDU to be sent by the first PDCP entity of the terminal-side device according to the first variable of the second PDCP entity; wherein, The first variable of the second PDCP entity may refer to the sending-side variable TX_NEXT, which is used to indicate the sequence number or count value of the next PDCP SDU to be sent by the second PDCP entity.
  • TX_NEXT the sending-side variable
  • the terminal-side device may use the value indicated by the first variable as the second information, that is, the sequence number or count value of the next PDCPSDU to be sent by the first PDCP entity as the terminal-side device. For example, when the terminal-side device newly establishes the first PDCP entity, the sequence number of the next PDCP SDU to be sent by the first PDCP entity starts from 0, but the sequence number of the next PDCP SDU to be sent by the second PDCP entity of the terminal-side device The sequence number is 100. At this time, the terminal-side device sends 100 as the second information to the first network-side device, and the sequence number of the PDCP PDU sent through the first PDCP entity starts from 100.
  • the terminal-side device may also send third information to the first network-side device, where the third information indicates the sequence number or sequence number of the next PDCP SDU that the first PDCP entity expects to receive Count value.
  • the terminal-side device may determine the sequence number or count value of the next PDCP SDU that the first PDCP entity of the terminal-side device expects to receive according to the second variable of the second PDCP entity; wherein, The second variable of the second PDCP entity may refer to the first receiving-side variable RX_NEXT, which is used to indicate the sequence number or count value of the next PDCP SDU that the second PDCP entity expects to receive.
  • the terminal side device when the terminal side device newly establishes the first PDCP entity, the sequence number of the next PDCP SDU that the first PDCP entity expects to receive is 0, but the second PDCP entity of the terminal side device expects the sequence of the next PDCP SDU to receive The number is 150. At this time, the terminal-side device sends 150 as the second information to the first network-side device, and the sequence number of the PDCP PDU sent by the first PDCP entity starts from 150.
  • first information, the second information, and the third information may be sent through the same message, or may be sent sequentially through different messages, which is not limited in the embodiment of the present application.
  • the terminal-side device may notify the first network-side device whether to send the second information and/or the third information. For example, the terminal-side device may send the fourth information to the first network-side device. The information instructs the terminal-side device to send the second information, or the fourth information instructs the terminal-side device to send the second information and the third information.
  • the terminal-side device may also send other information to the first network-side device, such as fifth information and sixth information.
  • the fifth information indicates that the first PDCP entity does not The sequence number or count value of the PDCP SDU delivered to the upper layer; the sixth information indicates the sequence number or count value of the PDCP PDU for which the first PDCP entity of the terminal side device triggers the reordering timer.
  • the fifth information can be determined according to the third variable of the second PDCP entity.
  • the third variable is the serial number or count value of the first PDCP SDU of the second PDCP entity of the terminal side device that has not been submitted to the upper layer; the sixth information can be determined according to The fourth variable of the second PDCP entity is determined.
  • the fourth variable is the sequence number or count value of the PDCP PDU that the second PDCP entity of the terminal side device triggers the reordering timer.
  • the second or third information The description is not repeated here.
  • the terminal-side device may first determine whether the first bearer corresponding to the first PDCP entity is performed between the terminal-side device and the core network-side device. Repeatedly transmitted radio bearer.
  • the first bearer corresponding to the first PDCP entity is a radio bearer that performs repeated transmission between the terminal side device and the core network side device
  • the second information is sent to the first network side device.
  • the terminal-side device may determine whether the first bearer is a radio bearer used for repeated transmission between the terminal-side device and the core network-side device in multiple ways. For details, refer to FIG. 4 The description in the shown process will not be repeated here.
  • Step 604 The first network side device receives second information.
  • the first network-side device may receive the second information from the terminal-side device; or, the first network-side device may also receive the second information from the second network-side device, that is, the terminal-side device will The second information is sent to the second network side device, and the second network side device forwards the second information to the first network side device.
  • the first network-side device may set the first receiving-side variable RX_NEXT of the PDCP entity corresponding to the first PDCP entity in the first network-side device to the count value indicated by the second information. For example, if the serial number of the PDCP SDU indicated by the second information is 100, the first receiving-side variable RX_NEXT of the PDCP entity corresponding to the first PDCP entity in the first network-side device may be set to a count value corresponding to 100; second The count value of the PDCP SDU indicated by the information is 100, and the first receiving side variable RX_NEXT of the PDCP entity corresponding to the first PDCP entity in the first network side device may be set to 100.
  • the first network-side device when it receives the PDCP SDU of the terminal-side device, it can use the PDCP SDU sequence number or count value indicated by the second information, so as to avoid the terminal-side device from following the data sent by the second PDCP entity.
  • the sequence number of the PDCP SDU sends the PDCP SDU to the first network side device, but the first network side device receives the PDCP SDU according to the PDCP SDU sequence number starting from 0, which causes the first network side device to mistakenly believe that the PDCP SDU has packet loss and restarts repeatedly Reordering the timer causes a delay in delivering data packets to the upper layer and increases the transmission delay.
  • the transmitting-side variable TX_NEXT of the PDCP entity corresponding to the first PDCP entity in the first network-side device may be set to the count value indicated by the third information. For example, if the serial number of the PDCP SDU indicated by the third information is 150, the transmitting side variable TX_NEXT of the PDCP entity corresponding to the first PDCP entity in the first network side device can be set to a count value corresponding to 150; the second information indicates If the count value of the PDCP SDU is 150, the sending side variable TX_NEXT of the PDCP entity corresponding to the first PDCP entity in the first network side device can be set to 150.
  • the first network side device when the terminal side device sends a sequence number, the first network side device only receives the sequence number, and the count value can be determined based on the HFN before the re-established first PDCP and the sequence number received from the terminal side device.
  • the first network-side device receives the HFN that can be used for the first PDCP entity from the second network-side device.
  • the first network side device may also receive a bearer identifier or GTP tunnel identifier associated with the HFN from the second network side device.
  • the first network side device determines that the HFN is an HFN that can be used for the first PDCP, it determines the PDCP SDU count based on the HFN received from the second network side device and the sequence number of the PDCP SDU received from the terminal side device value.
  • the first network side device requests the second network side device to send the HFN.
  • FIG. 7 a schematic diagram of a PDCP entity re-establishment process provided by an embodiment of this application.
  • the terminal-side device establishes a connection with the network-side device A and the network-side device B in a dual connection manner.
  • the terminal-side device can apply the method of the terminal-side device in the process shown in FIG.
  • the device A may apply the method of the first network side device in the process shown in FIG. 6, and the network device B may apply the method of the second network side device in the process shown in FIG. 6.
  • the terminal-side equipment includes PDCP entity 1 and PDCP entity 2.
  • PDCP entity 1 corresponds to radio bearer 1
  • PDCP entity 2 corresponds to radio bearer 2
  • radio bearer 1 and radio bearer 2 are a pair of bearers used for repeated transmission, namely radio bearers
  • the content of the PDCP SDU transmitted in radio bearer 1 and radio bearer 2 is the same.
  • the UPF device receives the PDCP SDU transmitted through radio bearer 1 and radio bearer 2, it can perform deduplication processing according to the sequence number of the PDCP SDU.
  • Step 701 The network side device A sends an RRC reconfiguration message to the terminal side device.
  • the RRC reconfiguration message may be the first information in the process shown in FIG. 6, and may also include the first information in the process shown in FIG. 6.
  • the RRC reconfiguration message can be used to notify the terminal-side device to change or increase the encryption key used by PDCP entity 1, or to notify the terminal-side device to perform full configuration reconfiguration, or to notify the handover process When the terminal device switches to a cell, it can also be used to create a new bearer for repeated data transmission between the terminal-side device and the UPF device.
  • the PDCP entity 1 is equivalent to the first PDCP entity in the process shown in FIG. 6.
  • Step 702 The terminal side device sends an RRC reconfiguration complete message to the network side device A.
  • the RRC reconfiguration complete message may be the second information in the process shown in FIG. 6, and may also include the second information in the process shown in FIG. 6.
  • the terminal-side device When the terminal-side device receives the RRC reconfiguration message, it can determine to re-establish PDCP entity 1 in addition to changing or adding the encryption key used by PDCP entity 1 or performing full configuration reconfiguration, new bearer creation, and handover to the target cell. .
  • the PDCP entity 3 corresponding to the PDCP entity 1 in the network side device A is also re-established. Since the contents of the PDCP SDUs transmitted in radio bearer 1 and radio bearer 2 are the same, the sequence numbers of the PDCP SDUs transmitted in radio bearer 1 and radio bearer 2 are the same.
  • the sending side variable TX_NEXT, the first receiving side variable RX_NEXT, the second receiving side variable RX_DELIV, and the third receiving side variable RX_REORD of PDCP entity 3 are all set to 0, but the network side
  • the PDCP entity 4 corresponding to the PDCP entity 2 in the device B is not re-established, and the sequence number of the PDCP SDU sent by the PDCP entity 2 of the terminal side device to the network side device B is not 0.
  • the terminal side device sends the sequence number or count value of the next PDCP SDU to be sent in the PDCP entity 2 as the second information to the network side device A.
  • the network side device A can determine the sequence number or count value of the next PDCP SDU expected to be received in the PDCP entity 3 according to the second information, so that it will not receive PDCP SDUs according to the PDCP SDU sequence number starting from 0, avoiding repeated start Reordering the timer causes the delay in delivering data packets to the upper layer, reducing the transmission delay.
  • the terminal side device may also send the third information, the fourth information, the fifth information, and the sixth information to the network side device A, which will not be repeated here.
  • the second information, the third information, and the fourth information are optionally sent to the network side device A.
  • step 703 the network side device A sends the second information to the network side device B.
  • the network side device A may use the count value before the re-established first PDCP by default.
  • the network side device B receives from the network side device A at least one of the HFN, the sequence number, and the count value that can be used for the first PDCP entity.
  • the network-side device B may also receive the HFN, a bearer identifier or a GTP tunnel identifier associated with the serial number or count value from the network-side device A.
  • the network-side device B determines that the HFN can be used for the HFN of the first PDCP.
  • the network side device B determines that the sequence number can be used for the sequence number of the first PDCP.
  • the network side device B determines that the count value can be used for the count value of the first PDCP.
  • the part that the network side device B did not receive from the network side device A can be 0 by default.
  • the network side device B may also request the network side device A to send the HFN, sequence number or count value.
  • each network element and device such as the above-mentioned wireless access network device, access and mobility management function network element, user equipment, data management function network element, and network slice selection function network element, in order to realize the above functions, Contains the corresponding hardware structure and/or software modules that perform each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • FIG. 8 a schematic structural diagram of a communication device provided in an embodiment of this application.
  • the communication device may be used to perform actions of the terminal-side device or the first network-side device in the foregoing method embodiments.
  • the communication device 800 includes: a transceiver unit 801 and a processing unit 802.
  • the transceiver unit 801 and the processing unit 802 execute the following steps respectively:
  • the transceiving unit 801 is configured to receive first indication information from a first network side device, where the first indication information triggers the re-establishment of the first PDCP entity of the terminal side device;
  • the processing unit 802 is configured to, when the first bearer corresponding to the first PDCP entity is not a radio bearer that performs repeated transmissions between the terminal-side device and the core network-side device, and re-establish all data on the terminal-side device
  • the parameters of the first PDCP entity are set to initial values; wherein, the parameters of the first PDCP include at least one of a first parameter, a second parameter, and a third parameter,
  • the first parameter is used to indicate the sequence number or the count value of the next PDCP service data unit SDU that the first PDCP entity expects to receive;
  • the second parameter is used to indicate the next PDCP entity to send A sequence number or count value of a PDCP SDU;
  • the third parameter is used to indicate the sequence number or count value of the first PDCP SDU that is not submitted to the upper layer by the first PDCP entity.
  • the terminal-side device In the process of re-establishing the first PDCP entity, the parameters of the first PDCP entity are kept unchanged.
  • the transceiver unit 801 is further configured to: receive second indication information from the first network-side device, where the second indication information indicates to set the parameter of the first PDCP entity to Initial value.
  • the transceiving unit 801 is further configured to: receive third indication information from the first network side device, where the third indication information indicates that the first bearer is not used in the A radio bearer for repeated transmission between the terminal side device and the core network side device.
  • the first bearer is an unacknowledged mode UM bearer.
  • the transceiver unit 801 and the processing unit 802 execute the following steps respectively:
  • the transceiver unit 801 is configured to receive first information that triggers the establishment of a first packet data aggregation protocol PDCP entity;
  • the processing unit 802 is configured to establish the first PDCP entity and send second information to the first network side device, where the second information is used to indicate the next PDCP service data unit SDU to be sent by the first PDCP entity The serial number or count value.
  • the first bearer corresponding to the first PDCP entity is a radio bearer that performs repeated transmission between the terminal side device and the core network side device.
  • the transceiving unit 801 is further configured to send third information to the first network side device, the third information indicating the next PDCP SDU that the first PDCP entity expects to receive The serial number or count value.
  • the transceiving unit 801 is further configured to send fourth information to the first network side device, where the fourth information instructs the terminal side device to send the second information.
  • the terminal-side device further includes a second PDCP entity, and the first bearer corresponding to the first PDCP entity and the second bearer corresponding to the second PDCP entity are a pair for repeating The transmission bearer; the processing unit 802 is further configured to determine the sequence number of the next PDCP service data unit SDU to be sent by the first PDCP entity of the terminal side device according to the first variable of the second PDCP entity Or a count value; wherein the first variable of the second PDCP entity is used to indicate the sequence number or count value of the next PDCP SDU to be sent by the second PDCP entity.
  • the processing unit 802 is further configured to determine the sequence number or count value of the next PDCP SDU that the first PDCP entity expects to receive according to the second variable of the second PDCP entity;
  • the second variable of the second PDCP entity is used to indicate the sequence number or the count value of the next PDCP SDU that the second PDCP entity expects to receive.
  • the terminal-side device is connected to the first network-side device and the second network-side device in a dual connection manner, and the transceiving unit 801 is specifically configured to: slave the first network-side device Receiving the first information; or, the terminal side device receives the first information from the second network side device.
  • the transceiver unit 801 and the processing unit 802 execute the following steps respectively:
  • the transceiver unit 801 is configured to send first information that triggers the terminal-side device to establish a first packet data aggregation protocol PDCP entity; and receives second information that indicates what the first PDCP entity wants to send The sequence number or count value of the next PDCP service data unit SDU.
  • the transceiver unit 801 is further configured to: receive third information, the third information being used to indicate the sequence number or count value of the next PDCP SDU that the first PDCP entity expects to receive .
  • the processing unit 802 is configured to determine, according to the third information, the sequence of the next PDCP SDU to be sent by the PDCP entity corresponding to the first PDCP entity to the terminal side device Number or count value.
  • FIG. 9 is a schematic structural diagram of a terminal-side device provided by an embodiment of the present application.
  • the communication device shown in FIG. 9 may be a hardware circuit implementation of the communication device shown in FIG. 8.
  • the terminal-side device may be suitable for implementing the functions of the terminal-side device in the foregoing method.
  • FIG. 9 only shows the main components of the terminal-side device 900.
  • the terminal-side device 900 includes a processor 901, a memory 902, a transceiver 903, an antenna 904, and an input and output device 905.
  • the memory 902 is configured to be coupled with the processor 901, and it stores necessary computer programs for the terminal device 900.
  • the processor 901 is mainly used to process communication protocols and communication data, and to control the entire wireless communication device, execute software programs, and process data of the software programs, for example, to support the wireless communication device to execute the methods described in the above method embodiments Action etc.
  • the transceiver 903 is mainly used for conversion of baseband signals and radio frequency signals and processing of radio frequency signals.
  • the antenna 904 is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves.
  • the input and output device 905, such as a touch screen, a display screen, a keyboard, etc., is mainly used to receive data input by the user and output data to the user.
  • terminal-side device 900 executes the actions of the terminal-side device in the process shown in FIG. 4, the following steps are performed:
  • the transceiver 903 is configured to receive first indication information from a first network side device, where the first indication information triggers the re-establishment of the first PDCP entity of the terminal side device;
  • the processor 901 is configured to, when the first bearer corresponding to the first PDCP entity is not a radio bearer that performs repeated transmissions between the terminal-side device and the core network-side device, and re-establish all data on the terminal-side device
  • the parameters of the first PDCP entity are set to initial values; wherein, the parameters of the first PDCP include at least one of a first parameter, a second parameter, and a third parameter
  • the first parameter is used to indicate the sequence number or the count value of the next PDCP service data unit SDU that the first PDCP entity expects to receive;
  • the second parameter is used to indicate the next PDCP entity to send A sequence number or count value of a PDCP SDU;
  • the third parameter is used to indicate the sequence number or count value of the first PDCP SDU that is not submitted to the upper layer by the first PDCP entity.
  • the terminal-side device In the process of re-establishing the first PDCP entity, the parameters of the first PDCP entity are kept unchanged.
  • the transceiver 903 is further configured to: receive second indication information from the first network-side device, where the second indication information indicates to set the parameter of the first PDCP entity to Initial value.
  • the transceiver 903 is further configured to: receive third indication information from the first network-side device, where the third indication information indicates that the first bearer is not used in the A radio bearer for repeated transmission between the terminal side device and the core network side device.
  • the first bearer is an unacknowledged mode UM bearer.
  • terminal-side device 900 executes the actions of the terminal-side device in the process shown in FIG. 6, the following steps are performed:
  • the transceiver 903 is configured to receive first information, which triggers the establishment of a first packet data aggregation protocol PDCP entity;
  • the processor 901 is configured to establish the first PDCP entity and send second information to the first network side device, where the second information is used to indicate the next PDCP service data unit SDU to be sent by the first PDCP entity The serial number or count value.
  • the first bearer corresponding to the first PDCP entity is a radio bearer that performs repeated transmission between the terminal side device and the core network side device.
  • the transceiver 903 is further configured to send third information to the first network side device, the third information indicating the next PDCP SDU that the first PDCP entity expects to receive The serial number or count value.
  • the transceiver 903 is further configured to send fourth information to the first network side device, where the fourth information instructs the terminal side device to send the second information.
  • the terminal-side device further includes a second PDCP entity, and the first bearer corresponding to the first PDCP entity and the second bearer corresponding to the second PDCP entity are a pair for repeating Transmission bearer;
  • the processor 901 is further configured to: determine the sequence number of the next PDCP service data unit SDU to be sent by the first PDCP entity of the terminal side device according to the first variable of the second PDCP entity Or a count value; wherein the first variable of the second PDCP entity is used to indicate the sequence number or count value of the next PDCP SDU to be sent by the second PDCP entity.
  • the processor 901 is further configured to determine, according to a second variable of the second PDCP entity, the sequence number or count value of the next PDCP SDU that the first PDCP entity expects to receive;
  • the second variable of the second PDCP entity is used to indicate the sequence number or the count value of the next PDCP SDU that the second PDCP entity expects to receive.
  • the terminal-side device is connected to the first network-side device and the second network-side device in a dual-connection manner, and the transceiver 903 is specifically configured to: slave the first network-side device Receiving the first information; or, the terminal side device receives the first information from the second network side device.
  • FIG. 10 is a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • the network side device shown in FIG. 10 may be a hardware circuit implementation of the communication device shown in FIG. 8.
  • the network side device can be applied to the flowchart shown in FIG. 6 to perform the function of the first network side device in the foregoing method embodiment.
  • FIG. 10 only shows the main components of the network side device.
  • the network side device 1000 includes a processor 1001, a memory 1002, a radio frequency module 1003, an antenna 1004, and the like.
  • the radio frequency module 1003 is configured to send first information, the first information triggers the terminal side device to establish a first packet data aggregation protocol PDCP entity; receive second information, the second information indicates the first PDCP entity to send The sequence number or count value of the next PDCP service data unit SDU.
  • the radio frequency module 1003 is further configured to: receive third information, and the third information is used to indicate the sequence number or count value of the next PDCP SDU that the first PDCP entity expects to receive .
  • the processor 1001 is configured to determine, according to the third information, the sequence of the next PDCP SDU to be sent by the PDCP entity corresponding to the first PDCP entity to the terminal side device Number or count value.
  • the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

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

Abstract

一种实体建立的处理方法及装置。该处理方法包括：终端侧设备接收来自第一网络侧设备的第一指示信息，所述第一指示信息触发重建立所述终端侧设备的第一PDCP实体；在所述第一PDCP实体对应的第一承载不是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，且在所述终端侧设备根据所述第一指示信息重建立所述第一PDCP实体的过程中，将所述第一PDCP实体的参数置为初始值。

Description

一种实体建立的处理方法及装置
相关申请的交叉引用
本申请要求在2019年02月15日提交中国专利局、申请号为201910117738.9、申请名称为“一种实体建立的处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种实体建立的处理方法及装置。
背景技术
分组数据聚合协议(packet data convergence protocol，PDCP)是长期演进(Long Term Evolution，LTE)系统的协议栈中的一种重要协议。终端侧设备以及网络侧设备可以通过PDCP层对接收到的数据包进行头压缩/解头压缩、加密/解密和完整性保护等操作。
为了提高传输的可靠性，终端侧设备或网络侧设备接收到PDCP服务数据单元(service data unit，SDU)之后，可以根据PDCP SDU的序列号(serial number，SN)实现PDCP SDU按序递交。例如，终端侧设备或网络侧设备作为发送端，维持一个状态变量TX_NEXT：这个状态变量指示下一个要发送的PDCP SDU的PDCP SN。当接收到的第一PDCP SDU的PDCP SN，与状态变量TX_NEXT指示的PDCP SN不一致，则不处理第一PDCP SDU，而是等待预设时长，直到接收到包括状态变量TX_NEXT指示的PDCP SN的第二PDCP SDU，再优先递交第二PDCP SDU。相应的，在接收端，会维持一个状态变量RX_NEXT，这个状态变量指示期望要接收的下一个PDCP SDU的PDCP SN。需要说明的是，终端侧设备发送给网络侧设备的PDCP SDU中的PDCP SN，是由终端侧设备进行维护的；网络侧设备发送给终端侧设备的PDCP SDU中的PDCP SN，是由网络侧设备进行维护的。
由于密钥更改等原因，终端侧设备触发终端侧设备中的PDCP实体重建立。PDCP实体重建立时，重置状态变量TX_NEXT以及RX_NEXT为初始值0。在PDCP实体重建立之后，由于状态变量TX_NEXT以及RX_NEXT重置为0，但是终端侧设备接收到的PDCP SDU的PDCP SN不为0，此时终端侧设备开启重排序定时器，等到重排序定时器超时才能将接收到的PDCP SDU递交给PDCP层的上层，额外增加了时延。同样，网络侧设备收到的PDCP SDU的PDCP SN不为0，也开启重排序定时器，也增加时延。
因此，如何在PDCP实体重建立时，降低数据的传输时延，是一个亟待解决的问题。
发明内容
本申请实施例提供一种实体建立的处理方法及装置，用以解决在PDCP实体重建立时，如何降低数据的传输时延的问题。
第一方面，本申请实施例提供一种实体建立的处理方法，该方法包括：终端侧设备接收来自第一网络侧设备的第一指示信息，所述第一指示信息触发重建立所述终端侧设备的第一分组数据聚合协议PDCP实体；在所述第一PDCP实体对应的第一承载不是在所述终 端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，且在所述终端侧设备重建立所述第一PDCP实体的过程中，将所述第一PDCP实体的参数置为初始值；其中，所述第一PDCP的参数包括第一参数、第二参数以及第三参数中的至少一项，所述第一参数用于指示所述第一PDCP实体期望要接收的下一个PDCP服务数据单元SDU的序列号或计数值；所述第二参数用于指示所述第一PDCP实体要发送的下一个PDCP SDU的序列号或计数值；所述第三参数用于指示没有被所述第一PDCP实体向上层递交的第一个PDCP SDU的序列号或计数值。
通过上面的方法，终端侧设备在重建第一PDCP实体时，可以不完全将第一PDCP实体的第一参数、第二参数以及第三参数全部置为初始值，而是可以将部分参数置为初始值。当第一参数未置为初始值时，终端侧设备通过第一PDCP实体接收到的PDCP SDU的序列号为第一参数指示的值时，可以使用第一PDCP实体重建立之前的第一参数继续接收来自核心网设备的PDCP SDU，从而可以保持接收到的PDCP SDU的序列号的连续性，避免终端侧设备复位了第一参数，但是第一网络侧设备继续以复位之前的PDCP SDU序列号开始编号进行发送PDCP SDU，导致终端侧设备误以为PDCP SDU出现丢包，重复启动重排序定时器，导致延迟向上层递交数据包，增加传输时延。当第二参数未置为初始值时，终端侧设备可以继续使用第一PDCP实体重建立之前的第二参数发送PDCP SDU，从而可以保持接发送的PDCP SDU序列号的连续性，降低PDCP SDU的发送时延；当第三参数未置为初始值时，终端侧设备根据第三参数，尽快确定第一个没有被递交到上层的PDCP SDU的序列号或计数值，从而降低PDCP SDU的处理时延。
在一种可能的设计中，在所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，在所述终端侧设备重建立所述第一PDCP实体的过程中，保持所述第一PDCP实体的参数不变。
在一种可能的设计中，所述方法还包括：所述终端侧设备接收来自所述第一网络侧设备的第二指示信息，所述第二指示信息指示将所述第一PDCP实体的参数置为初始值。
在一种可能的设计中，所述方法还包括：所述终端侧设备接收来自所述第一网络侧设备的第三指示信息，所述第三指示信息指示所述第一承载不是用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载。
通过第三指示信息，终端侧设备可以准确的确定第一承载是否为进行重复传输的无线承载。
在一种可能的设计中，所述第一承载为非确认模式UM承载。
第二方面，本申请实施例提供一种实体建立的处理方法，包括：终端侧设备接收第一信息，所述第一信息触发建立第一分组数据聚合协议PDCP实体；所述终端侧设备建立所述第一PDCP实体，并向第一网络侧设备发送第二信息，所述第二信息用于指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
通过上述方法，终端侧设备通过向第一网络侧设备发送第二信息，使得第一网络侧设备接收到终端侧设备的PDCP SDU时，可以使用第二信息指示的PDCP SDU的序列号或计数值，从而可以避免终端侧设备按照第二PDCP实体中发送的PDCP SDU的序列号向第一网络侧设备发送PDCP SDU，但是第一网络侧设备按照从0开始的PDCP SDU序列号接收PDCP SDU，导致第一网络侧设备误以为PDCP SDU出现丢包，重复启动重排序定时器，导致延迟向上层递交数据包，增加传输时延。
在一种可能的设计中，所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。
在一种可能的设计中，所述方法还包括：所述终端侧设备向所述第一网络侧设备发送第三信息，所述第三信息指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述方法还包括：所述终端侧设备向所述第一网络侧设备发送第四信息，所述第四信息指示所述终端侧设备发送所述第二信息。
在一种可能的设计中，所述终端侧设备还包括第二PDCP实体，所述第一PDCP实体对应的第一承载与所述第二PDCP实体对应的第二承载是一对用于进行重复传输的承载；所述方法还包括：所述终端侧设备根据所述第二PDCP实体的第一变量确定所述终端侧设备的所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值；其中，所述第二PDCP实体的所述第一变量，用于指示所述第二PDCP实体要发送的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述方法还包括：所述终端侧设备根据所述第二PDCP实体的第二变量确定所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值；
其中，所述第二PDCP实体的所述第二变量，用于指示所述第二PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述终端侧设备通过双连接方式与所述第一网络侧设备以及第二网络侧设备连接，所述终端侧设备接收第一信息，包括：所述终端侧设备从所述第一网络侧设备接收所述第一信息；或者，所述终端侧设备从所述第二网络侧设备接收所述第一信息。
第三方面，本申请实施例提供一种实体建立的处理方法，包括：第一网络侧设备发送第一信息，所述第一信息触发终端侧设备建立第一分组数据聚合协议PDCP实体；所述第一网络侧设备接收第二信息，所述第二信息指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
通过上述方法，第一网络侧设备接收到终端侧设备的PDCP SDU时，可以使用第二信息指示的PDCP SDU的序列号或计数值，从而可以避免终端侧设备按照第二PDCP实体中发送的PDCP SDU的序列号向第一网络侧设备发送PDCP SDU，但是第一网络侧设备按照从0开始的PDCP SDU序列号接收PDCP SDU，导致第一网络侧设备误以为PDCP SDU出现丢包，重复启动重排序定时器，导致延迟向上层递交数据包，增加传输时延。
在一种可能的设计中，所述方法还包括：所述第一网络侧设备接收第三信息，所述第三信息用于指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述第一网络侧设备根据所述第三信息，确定与所述第一PDCP实体对应的PDCP实体要向所述终端侧设备发送的下一个PDCP SDU的序列号或计数值。
第四方面，本申请提供一种装置。所述装置具备实现上述第一方面至第二方面涉及的终端侧设备的功能，比如，所述装置包括所述终端侧设备执行上述第一方面至第二方面涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段(means)可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述装置包括处理单元、收发单元，处理单元、收发单元执行的功能可以和上述第一方面至第二方面涉及的终端侧设备执行的步骤相对应。
在一种可能的设计中，所述装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面至第二方面中任意可能的设计或实现方式中终端侧设备执行的方法。
其中，所述装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置，本申请并不限定。
一种可能的方式，存储器保存实现上述第一方面至第二方面涉及的终端侧设备的功能的必要计算机程序指令和/或数据。所述处理器可执行所述存储器存储的计算机程序指令，完成上述第一方面至第二方面任意可能的设计或实现方式中终端侧设备执行的方法。
第五方面，本申请提供一种装置。所述装置具备实现上述第三方面涉及的第一网络侧设备的功能，比如，所述装置包括所述第一网络侧设备执行上述第三方面涉及步骤所对应的模块或单元或手段(means)。所述功能或单元或手段(means)可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述装置包括处理单元、收发单元，处理单元、收发单元执行的功能可以和上述第三方面涉及的第一网络侧设备执行的步骤相对应。
在另一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第三方面中任意可能的设计或实现方式中网络侧设备执行的方法。
其中，所述装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置，本申请并不限定。
一种可能的方式，存储器保存实现上述第三方面涉及的第一网络侧设备的功能的必要计算机程序指令和/或数据。所述处理器可执行所述存储器存储的计算机程序指令，完成上述第三方面任意可能的设计或实现方式中第一网络侧设备执行的方法。
第六方面，本申请提供一种芯片，所述芯片可以与存储器相通信，或者所述芯片中可以包括存储器，所述芯片执行所述存储器中存储的程序指令，以实现上述第一方面至第三方面中涉及的终端侧设备或者第一网络侧设备的相应功能。
第七方面，本申请提供一种计算机存储介质，所述计算机存储介质存储有计算机可读指令，所述计算机可读指令被执行时，使得实现第一方面至第三方面中涉及的终端侧设备或者第一网络侧设备的相应功能。
第八方面，本申请还提供一种包含软件程序的计算机程序产品，当其在计算机上运行时，使得实现第一方面至第三方面中设计的终端侧设备或者第一网络侧设备的相应功能。
第九方面，本申请还提供一种通信系统，在所述通信系统中包括上述第一方面至第三方面中所涉及的终端侧设备，和/或，第一网络侧设备。
附图说明
图1(a)为适用于本申请实施例提供的方法的通信系统的架构示意图；
图1(b)为适用于本申请实施例提供的方法的通信系统的架构示意图；
图2为本申请实施例提供的一种网络连接示意图；
图3为本申请实施例提供的一种网络连接示意图；
图4为本申请实施例提供的一种实体建立的处理方法流程示意图；
图5为本申请实施例提供的一种实体建立的处理方法流程示意图；
图6为本申请实施例提供的一种实体建立的处理方法流程示意图；
图7为本申请实施例提供的一种实体重建立的流程示意图；
图8为本申请实施例提供的一种通信装置结构示意图；
图9为本申请实施例提供的一种终端侧设备结构示意图；
图10为本申请实施例提供的一种网络侧设备结构示意图。
具体实施方式
下面结合说明书附图对本申请实施例做详细描述。
本申请实施例可以应用于各种移动通信系统，例如：新无线(new radio，NR)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、长期演进(long term evolution，LTE)系统、先进的长期演进(advanced long term evolution，LTE-A)系统、演进的长期演进(evolved long term evolution，eLTE)系统、未来通信系统等其它通信系统，具体的，在此不做限制。
为便于理解本申请实施例，首先以图1(a)中示出的通信系统为例详细说明适用于本申请实施例的通信系统。图1(a)示出了适用于本申请实施例提供的方法的通信系统的架构示意图。如图1(a)所示，该通信系统包括终端侧设备101、主网络侧设备102、辅网络侧设备103、用户面功能(user plane function，UPF)设备104、数据网络(Data Network，DN)105、接入和移动性管理(Access and Mobility Management Function,AMF)设备106、会话管理功能(Session Management Function，SMF)设备107以及策略控制功能(Policy Control Funtion，PCF)设备108。终端侧设备101可以单独与主网络侧设备102或辅网络侧设备103建立连接；终端侧设备101也可以通过双连接(dual connectivity，DC)方式与主网络侧设备102以及辅网络侧设备103连接。
主网络侧设备102或辅网络侧设备103为终端侧设备101等提供无线接入服务；UPF设备104主要负责对终端侧设备101的报文进行转发、计费等处理，这里的报文包括但不限于PDCP SDU等报文。
DN105可以是指为终端侧设备101提供服务的网络，比如可以为终端侧设备101提供上网功能。
在本申请实施例中，终端侧设备，为具有无线收发功能的设备或可设置于该设备的芯片。其中，所述具有无线收发功能的设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、用户终端、用户代理或用户装置。在实际应用中，本申请的实施例中的终端侧设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。本申请中将前述具有无线收发功能的设备及可设置于该设备中的芯片统称为终端侧设备。
在本申请实施例中，网络侧设备可以为各种制式下无线接入网设备，例如演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)或节点B(Node  B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission and reception point，TRP或者transmission point，TP)等，还可以为5G(NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元，或在集中式-分布式(central unit-distributed,CU-DU)架构下的DU等。
AMF设备106，主要功能包括无线接入网络控制平面的终结点，非接入信令的终结点，移动性管理，合法监听，接入授权或鉴权等等。SMF设备107，主要负责为终端侧设备101建立会话、管理会话等。SMF设备107可以根据终端侧设备101的位置信息为终端侧设备101选择合适的UPF设备。PCF设备108，主要负责用户面传输路径的建立、释放和更改等功能。
图1(a)中还示出了各个设备中的接口的可能实现方式，比如主网络侧设备102和AMF设备106之间的N2接口，主网络侧设备102与UPF设备104之间的N3接口等等，在此不再一一赘述。
传统技术中，通过PDCP层报文复制技术提高传输的可靠性，即终端侧设备与网络侧设备之间，可以通过两条独立的传输路径传输两个相同的PDCP层报文。PDCP层报文复制技术存在两个重要的应用场景：网络侧设备内载波聚合(carrier aggregation，CA)和双连接(dual connectivity，DC)。
举例来说，结合图1(a)，如图1(b)所示，为本申请实施例提供的一种简化的网络架构示意图。在CA场景下，如图2所示，终端侧设备202与网络侧设备204之间包括两个数据无线承载(data radio bear，DRB)：DRB1和DRB2，每个DRB对应一个PDCP实体(entity)，PDCP层报文，即PDCP SDU通过PDCP实体对应的DRB传输。相应的，网络侧设备204与核心网侧设备206之间存在采用通用分组无线服务(General Packet Radio Service，GPRS)隧道协议(GTP)建立的两个隧道(tunnel)：隧道1和隧道2，隧道1对应DRB1，隧道2对应DRB2。在下行方向上，网络侧设备204对通过隧道1或隧道2接收到的PDCP SDU进行复制，得到PDCP SDU1和与PDCP SDU 1相同的PDCP SDU2。这两个PDCP SDU具有相同的序列号；PDCP SDU1通过网络侧设备204与终端侧设备202之间的DRB1发送至终端侧设备202，PDCP SDU2通过网络侧设备204与终端侧设备202之间的DRB2发送至终端侧设备202。终端侧设备202接收到PDCP SDU1和PDCP SDU2时，可以根据PDCP SDU的序列号对接收到的PDCP SDU进行去重处理。上行方向可以参考下行方向中的描述，在此不再赘述。其中，核心网侧设备206可以为UPF设备。
再举例来说，结合图1(b)所示，DC场景下，如图3所示，终端侧设备101同时与网络侧设备204以及网络侧设备208建立连接，网络侧设备204为主接入网设备，网络侧设备208为辅接入网设备，其中，主接入网设备的覆盖范围为主小区组，辅接入网设备的覆盖范围为辅小区组。终端侧设备202与网络侧设备204之间包括DRB1；终端侧设备202与网络侧设备208之间包括DRB2。需要说明的是，在DC场景下，DRB1与DRB2可以共享终端侧设备202中的一个PDCP实体，DRB1与DRB2也可以在终端侧设备202中拥 有不同的PDCP实体。在下行方向上，网络侧设备204对通过隧道1或隧道2接收到的PDCP SDU进行复制，得到PDCP SDU1和PDCP SDU2，这两个PDCP SDU具有相同的序列号；PDCP SDU1通过网络侧设备204与终端侧设备202之间的DRB1发送至终端侧设备202；网络侧设备204将PDCP SDU2发送至网络侧设备208，PDCP SDU2再通过网络侧设备208与终端侧设备202之间的DRB2发送至终端侧设备202。终端侧设备202接收到PDCP SDU1和PDCP SDU2时，可以根据PDCP SDU的序列号对接收到的PDCP SDU进行去重处理。上行方向可以参考下行方向中的描述，在此不再赘述。
为防止报文乱序，以终端侧设备为例，下行方向上，终端侧设备将接收到的PDCP SDU按照PDCPSDU的序列号的顺序递交到上层；相应的，上行方向上，终端侧设备将要发送的PDCP SDU按照PDCP SDU的序列号的顺序递交给下层。基于同样的理由，无线接入网设备也会按照PDCP SDU的序列号的顺序递交，在此不再赘述。
为了实现按顺序递交报文，以终端侧设备为例，终端侧设备会维护至少一个PDCP实体的参数，例如终端侧设备维护的参数包括：发送侧变量TX_NEXT，第一接收侧变量RX_NEXT，第二接收侧变量RX_DELIV，第三接收侧变量RX_REORD等。其中，TX_NEXT用于指示下一个要发送的PDCP SDU的计数(COUNT)值，该参数的初始值为0；RX_NEXT用于指示期望要接收的下一个PDCP SDU的计数值，该参数的初始值为0；RX_DELIV用于指示没有被递交到上层的第一个PDCP SDU的计数值，该参数的初始值为0；第三接收侧变量RX_REORD用于指示触发重排序定时器的PDCP PDU的计数值。
需要说明的是，PDCP SDU的计数值，是由超帧号(hyper frame number，HFN)和PDCPSDU的序列号组成，HFN是终端侧设备与无线接入网设备分别通过同样的方式确定的值，例如，初始时，PDCP SDU的序列号以及HFN的值均为0，当终端侧设备每发送一个PDCP SDU，将PDCP SDU的序列号加1，当PDCP SDU的序列号达到预设的最大值，例如1024时，将PDCP SDU的序列号的值置0，并将HFN的值加1。无线接入网设备也按照相同的方式确定HFN，通过这样的方法，终端侧设备与无线接入网设备确定出的HFN相同。由于终端侧设备与无线接入网设备确定出的HFN相同，因此确定了PDCPSDU的序列号就可以确定PDCPSDU的计数值。可以理解，PDCPSDU和PDCP SN等组成一个PDCP Data PDU，因此PDCP SN也称为PDCP数据PDU(Protocol Data Unit,协议数据单元)的PDCP SN号。
另外，在本申请实施例中，“示例性的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例中部分场景以无线通信网络中NR网络的场景为例进行说明，应当指出的是，本申请实施例中的方案还可以应用于其他无线通信网络中，相应的名称也可以用其他无线通信网络中的对应功能的名称进行替代。
如图4所示，为本申请实施例提供的一种实体建立的处理方法流程示意图，图4所示 的方法流程可以应用于图1(a)或图1(b)所示的网络。图4所示的方法流程中，终端侧设备可以单独与第一网络侧设备建立连接，也可以通过双连接的方式与第一网络侧设备以及第二网络侧设备建立连接。终端侧设备通过双连接的方式与第一网络侧设备以及第二网络侧设备建立连接时，第一网络侧设备可以为主网络侧设备，也可以为辅网络侧设备，本申请实施例对此并不限定。在图4的步骤401之前，终端侧设备与第一网络侧设备已经建立了第一承载，该第一承载对应终端侧设备的第一PDCP实体。
参见图4，该方法包括：
步骤401：终端侧设备接收来自第一网络侧设备的第一指示信息。
其中，所述第一指示信息触发重建立所述终端侧设备的第一PDCP实体。
需要说明的是，本申请实施例对第一指示信息的名称以及实现形式并不限定，第一指示信息可以携带在第一网络侧设备发送的消息中，第一指示信息本身也可以为第一网络侧设备发送的一个消息，例如第一指示信息可以为无线资源控制(radio resource control，RRC)重配置消息等，在此不再逐一举例说明。
本申请实施例中，所述第一指示信息触发所述第一PDCP实体的重建立，也可以理解为所述第一指示信息用于确定所述第一PDCP实体建立的某信息，可包括多种实现方式。一种可能的实现方式中，第一指示信息可以直接指示终端侧设备重建立所述终端侧设备的第一PDCP实体；另一种可能的实现方式中，第一指示信息可能并不直接指示终端侧设备重建立第一PDCP实体，而是间接指示终端侧设备重建立第一PDCP实体。举例来说，在第一种可能的场景下，第一指示信息可以用于通知终端侧设备更改第一PDCP实体所使用的加密密钥，终端侧设备根据第一指示信息确定更改所述加密密钥时，则确定重建立第一PDCP实体。在第二种可能的场景下，第一指示信息可以用于通知终端侧设备进行全配置(full configuration)的重配置，此时，终端侧设备根据第一指示信息确定进行全配置的重配置时，则确定重建立第一PDCP实体。可以理解，全配置的重配置，是指对除了用户标识和加密密钥外的专用无线参数配置，进行重新配置。在第三种可能的场景下，第一指示信息可以用于通知终端侧设备增加一个第一PDCP实体对应的承载，使得终端侧设备从第一网络侧设备切换到第二网络侧设备的过程中，能够使用增加的承载通过核心网侧设备进行数据收发，此时，终端侧设备可以根据第一指示信息，确定同时重建立第一PDCP实体。可选地，所述核心网侧设备指UPF设备。需要说明的是，在切换过程中，可以通过增加的承载和原承载都能通过核心网设备进行重复数据的收发。
步骤402：在所述第一PDCP实体对应的第一承载不是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，且在所述终端侧设备根据所述第一指示信息重建立所述第一PDCP实体的过程中，将所述第一PDCP实体的参数置为初始值(例如0)。
在第一种可能的场景下，终端侧设备在PDCP层只包括一个PDCP实体(第一PDCP实体)，终端侧设备在步骤402中，将所述第一PDCP实体的参数置为初始值。
在第二种可能的场景下，终端侧设备在PDCP层包括至少两个PDCP实体，不失去一般性，以第一PDCP实体和第二PDCP实体为例。可选地，至少两个PDCP实体中只有第一PDCP实体是来维护PDCP实体的参数的实体，终端侧设备可将第一PDCP实体的参数置为初始值即可。可选地，第一PDCP实体和第二PDCP实体都各自维护各自的PDCP实体的参数，那么所述两个PDCP实体在被重建立的过程中时都置为初始值。
进一步的，在该情况下，所述第一承载可以为非确认模式(Unacknowledged Mode，UM)承载。
示例性的，在另一种可能的情况中，在所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，在所述终端侧设备根据所述第一指示信息重建立所述第一PDCP实体的过程中，所述终端侧设备保持所述第一PDCP实体的参数不变。进一步的，在该情况下，所述第一承载可以为确认模式(acknowledged Mode，AM)承载或非确认模式(Unacknowledged Mode，UM)承载。其中，AM承载中传输的数据，在无线链路层控制协议(Radio Link Control，RLC)层支持自动重传请求(Automatic Repeat-reQuest，ARQ)；UM承载中传输的数据，在RLC层不支持自动重传请求(Automatic Repeat-reQuest，ARQ)。
其中，所述第一PDCP的参数包括第一参数、第二参数以及第三参数中的至少一项，所述第一参数用于指示所述第一PDCP实体期望要接收的下一个PDCPSDU的序列号或计数值；所述第二参数用于指示所述第一PDCP实体要发送的下一个PDCP SDU的序列号或计数值；所述第三参数用于指示所述第一PDCP实体第一个没有被递交到上层的PDCP SDU的序列号或计数值。
示例性的，本申请实施例中，PDCP SDU的计数值包括HFN和PDCP SDU的序列号，HFN对于终端侧设备以及第一网络侧设备是已知的值，HFN的确定方式可以参考前面的描述。对于上行方向，终端侧设备发送的PDCP SDU的序列号，是由终端侧设备维护的，当终端侧设备新建立第一PDCP实体时，终端侧设备发送的PDCP SDU的序列号从0开始，按照顺序递增，例如，终端侧设备发送3个PDCP SDU，上述3个PDCP SDU的序列号依次为0、1、2。对于下行方向，终端侧设备接收到的PDCP SDU的序列号，是由网络侧设备维护的，例如，网络侧设备根据核心网设备收到的下行数据包中的序号来确定的，网络侧设备可以直接使用下行数据包中的通用分组无线服务(General Packet Radio Service，GPRS)隧道协议用户面(GPRS Tunnelling ProtocolUser Plane，GTP-U)头字段中的序列号或序列号中的一部分作为PDCP SDU的序列号，也可以根据GTP-U头字段中的序列号推导获得PDCP SDU的序列号。
如前所述，核心网设备可以为UPF设备。结合上面的描述，当终端侧设备当前接收到的PDCP SDU的序列号为N，则第一参数指示的期望要接收的下一个PDCPSDU的序列号为N+1，N为大于或等于0的整数；当终端侧设备当前发送的PDCP SDU的序列号为M，则第二参数指示的要发送的下一个PDCP SDU的序列号为M+1，M为大于或等于0的整数；当终端侧设备当前第一个没有被递交到上层的PDCP SDU的序列号为K，则第三参数指示的第一个没有被递交到上层的PDCP SDU的序列号为K，K为大于或等于0的整数。相应的，第一参数、第二参数以及第三参数指示PDCP SDU的计数值时，可以参考上面的描述，在此不再赘述。
需要说明的是，第一参数的初始值、第二参数的初始值以及第三参数的初始值可以均为0。终端侧设备向第一网络侧设备发送的上行数据，第一网络侧设备再将终端侧设备发送的上行数据转发至核心网侧设备；相应的，第一网络侧设备向终端侧设备发送的下行数据，是来自核心网侧设备的，即第一网络侧设备相当于终端侧设备与核心网侧设备之间的转发设备。
如图1至图3所述，终端侧设备可以采用PDCP层报文复制技术传输PDCP SDU，为 此终端侧设备建立两个无线承载，所述两个无线承载传输相同的PDCP SDU，这两个无线承载可以称为用于在终端侧设备和核心网侧设备之间进行重复传输的无线承载。举例来说，图2中的DRB1和DRB2就是用于在终端侧设备和核心网侧设备之间进行重复传输的无线承载；图3中的DRB1和DRB2也是用于在终端侧设备和核心网侧设备之间进行重复传输的无线承载。可以理解，DRB1和DRB2可以使用相同的RB标识，不同的逻辑信道标识。或者，DRB1和DRB2可以使用不同的RB标识。需要说明的是，DRB1和DRB2使用相同的RB标识时，DRB1和DRB2共享终端侧设备中的一个PDCP实体；DRB1和DRB2使用不同的RB标识时，DRB1和DRB2在终端侧设备中对应不同的PDCP实体。进一步的，DRB1和DRB2传输重复的数据包，且所述重复的数据包属于相同的服务质量(Quality of Service，QoS)流。
如果终端侧设备未采用PDCP层报文复制技术，那么终端侧设备发送至核心网设备的某一个PDCP SDU只通过一个无线承载传输或至少两个逻辑信道中一个逻辑信道传输。相应的，核心网设备发送至终端侧设备的PDCP SDU只通过一个无线承载传输或至少两个逻辑信道中一个逻辑信道传输，那么该无线承载就不是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。
示例性的，PDCP实体的上层，可以是指协议栈中，位于PDCP层之上的协议层，例如可以为应用层(application layer)或者服务数据适应协议(Service Data Adaptation Protocol，SDAP)层，也可以指其它位于PDCP层之上的协议层。
通过上面的方法，终端侧设备在重建第一PDCP实体时，可以不完全将第一PDCP实体的第一参数、第二参数以及第三参数全部置为初始值，而是可以将部分参数置为初始值。当第一参数未置为初始值时，终端侧设备通过第一PDCP实体接收到的PDCP SDU的序列号为第一参数指示的值时，可以使用第一PDCP实体重建立之前的第一参数继续接收来自核心网设备的PDCP SDU，从而可以保持接收到的PDCP SDU的序列号的连续性，避免终端侧设备复位了第一参数，但是第一网络侧设备继续以复位之前的PDCP SDU序列号开始编号进行发送PDCP SDU，导致终端侧设备误以为PDCP SDU出现丢包，重复启动重排序定时器，导致延迟向上层递交数据包，增加传输时延。当第二参数未置为初始值时，终端侧设备可以继续使用第一PDCP实体重建立之前的第二参数发送PDCP SDU，从而可以保持接发送的PDCP SDU序列号的连续性，降低PDCP SDU的发送时延；当第三参数未置为初始值时，终端侧设备根据第三参数，尽快确定第一个没有被递交到上层的PDCP SDU的序列号或计数值，从而降低PDCP SDU的处理时延。
示例性的，在一种可能的实现方式中，终端侧设备还可以接收来自第一网络侧设备的第二指示信息，所述第二指示信息指示将所述第一PDCP实体的参数置为初始值。当终端侧设备接收到第二指示信息时，可以根据第一指示信息对第一PDCP实体进行重建立，并在重建立所述第一PDCP实体的过程中，根据所述第二指示信息将所述第一PDCP实体的参数置为初始值。此时，所述第一PDCP实体对应的第一承载可以是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载，也可以不是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。第二指示信息还可以指示出第一承载对应的承载标识或逻辑信道标识，所述第二指示信息指示将与所述承载标识或逻辑信道标识对应的第一 PDCP实体的参数置为初始值。
需要说明的是，第二指示信息可以通过第一网络侧设备发送的消息携带，也可以为一个独立的消息。第一指示信息与第二指示信息可以通过同一个消息发送，也可以通过不同的消息先后发送，本申请实施例对此并不限定。
可以理解，终端侧设备可以根据第二指示信息是否存在来确定是否将所述第一PDCP实体的参数置为初始值。例如，当终端侧设备未接收到第二指示信息，则将所述第一PDCP实体的参数置为初始值；当终端侧设备接收到第二指示信息，则将所述第一PDCP实体的参数不置为初始值。终端侧设备可以根据第二指示信息指示的值来确定是否将所述第一PDCP实体的参数置为初始值。例如，第二指示信息指示的值为true，不置为初始值。第二指示信息指示的值为false，置为初始值。
本申请实施例中，终端侧设备可以通过多种方式确定第一承载是否为用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载。示例性的，在一种可能的实现方式中，所述终端侧设备还可以接收来自所述第一网络侧设备的第三指示信息，所述第三指示信息指示所述第一承载不是用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载。在该实现方式下，终端侧设备可以根据第三指示信息确定第一承载是否为进行重复传输的无线承载。
示例性的，在另一种可能的实现方式中，终端侧设备与第一网络侧设备可以预先约定，当第一网络侧设备不发送第四指示信息或者终端侧设备未接收到第四指示信息时，表示第一承载不是用于在所述终端侧设备和所述UPF设备之间进行重复传输的无线承载。其中，所述第四指示信息指示所述第一承载是用于在所述终端侧设备和所述UPF设备之间进行重复传输的无线承载。
如图5所示，为本申请实施例提供的一种实体建立的处理方法流程示意图，图5所示的方法流程可以应用于图1(a)或图1(b)所示的网络。图5所示的方法流程中，终端侧设备可以单独与第一网络侧设备建立连接，也可以通过双连接的方式与第一网络侧设备以及第二网络侧设备建立连接。终端侧设备通过双连接的方式与第一网络侧设备以及第二网络侧设备建立连接时，第一网络侧设备可以为主网络侧设备，也可以为辅网络侧设备，本申请实施例对此并不限定。在图5的步骤501之前，终端侧设备与第一网络侧设备已经建立了第一承载，该第一承载对应终端侧设备的第一PDCP实体。
参见图5，该方法包括：
步骤501：终端侧设备确定将第一PDCP实体的参数置为初始值。
其中，所述第一PDCP的参数包括第一参数、第二参数以及第三参数中的至少一项，所述第一参数用于指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值；所述第二参数用于指示所述第一PDCP实体要发送的下一个PDCP SDU的序列号或计数值；所述第三参数用于指示所述第一PDCP实体第一个没有被递交到上层的PDCP SDU的序列号或计数值。
本申请实施例中，终端侧设备可以通过多种方式确定是否将第一PDCP实体的参数置为初始值。第一种可能的实现方式中，当终端侧设备确定第一PDCP实体对应的第一承载不是用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载时，可以确定将第一PDCP实体的参数置为初始值。终端侧设备具体如何确定第一承载是否为用于在 所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载，可以参考前面的描述，在此不再赘述。
在第二种可能的实现方式中，终端侧设备还可以接收来自第一网络侧设备的第二指示信息，所述第二指示信息指示将所述第一PDCP实体的参数置为初始值。当终端侧设备接收到第二指示信息时，可以确定在重建立所述第一PDCP实体的过程中，根据所述第二指示信息将所述第一PDCP实体的参数置为初始值。此时，所述第一PDCP实体对应的第一承载可以是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载，也可以不是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。第二指示信息还可以指示出第一承载对应的承载标识或逻辑信道标识，所述第二指示信息指示将与所述承载标识或逻辑信道标识对应的第一PDCP实体的参数置为初始值。需要说明的是，第二指示信息可以通过第一网络侧设备发送的消息携带，也可以为一个独立的消息，本申请实施例对此并不限定。
可以理解，终端侧设备可以根据第二指示信息是否存在来确定是否将所述第一PDCP实体的参数置为初始值。例如，当终端侧设备未接收到第二指示信息，则将所述第一PDCP实体的参数置为初始值；当终端侧设备接收到第二指示信息，则将所述第一PDCP实体的参数不置为初始值。终端侧设备可以根据第二指示信息中的值来确定是否将所述第一PDCP实体的参数置为初始值。例如，第二指示信息中的值为true，不置为初始值。第二指示信息中的值为false，置为初始值。
步骤502：所述终端侧设备在重建立所述第一PDCP实体的过程中，将所述第一PDCP实体的参数置为初始值。
需要说明的是，第一参数的初始值、第二参数的初始值以及第三参数的初始值均为0。
步骤501和步骤502的其它内容可以参考步骤401至步骤402中的描述，在此不再赘述。
按照传统技术的流程，终端侧设备重建立PDCP实体时，网络侧设备也重建立PDCP实体。一种可能的场景中，当终端侧设备通过与第一网络侧设备以及第二网络侧设备建立连接时，如果第一网络侧设备或者第二网络侧设备中只有一个网络侧设备重建立PDCP实体，会导致重建立PDCP实体的网络侧设备中的维护的状态变量TX_NEXT以及RX_NEXT置为0，但是终端侧设备发送的PDCP SDU的PDCP SN可能不为0，此时重建立PDCP实体的网络侧设备开启重排序定时器，等到重排序定时器超时才能将接收到的PDCP SDU递交给PDCP层的上层，额外增加了时延。
进一步的，另一种可能的场景中，当终端侧设备只与第二网络侧设备建立连接时，如果终端侧设备又通过与第一网络侧设备建立连接，因此第一网络侧设备新建立的PDCP实体的状态变量TX_NEXT以及RX_NEXT为0，由于终端侧设备向第一网络侧设备与第二网络侧设备发送的PDCP SDU相同，因此终端侧设备发送的PDCP SDU的PDCP SDU的序列号不是从0开始，此时第一网络侧设备接收到终端侧设备发送的PDCP SDU后，确定PDCP SDU的序列号不是0，则开启重排序定时器，等到重排序定时器超时才能将接收到的PDCP SDU递交给PDCP层的上层，额外增加了时延。
为此，本申请实施例中，还提供一种方法以解决上述问题。如图6所示，为本申请实施例提供的一种实体建立的处理方法流程示意图，图6所示的方法流程可以应用于图1所示的网络。参见图6，该方法包括：
步骤601：第一网络侧设备发送第一信息，所述第一信息触发终端侧设备建立第一PDCP实体。
第一信息触发终端侧设备建立第一PDCP实体，可以是指触发终端侧设备重建立第一PDCP实体，也可以是指触发终端侧设备新建立第一PDCP实体。一种可能的场景中，步骤601之前，终端侧设备当前只与第二网络侧设备建立连接，在该场景下，第一信息，是指触发终端侧设备新建立第一PDCP实体。终端侧设备与第一网络侧设备建立连接之后，可以继续保持与第二网络侧设备的连接，实现与第一网络侧设备以及第二网络侧设备的双连接。此时，终端侧设备根据第一信息新建立第一PDCP实体。一种可能的场景中，步骤601之前，终端侧设备可以只与第二网络侧设备建立连接，第一PDCP实体已经存在，在该场景下，第一信息，是指触发终端侧设备重建立第一PDCP实体，所述第一PDCP实体同时用于第一网络侧设备和第二网络侧设备建立的无线承载。当然终端侧设备也可以断开与第二网络侧设备的连接，此时相当于终端侧设备从第二网络侧设备切换到第一网络侧设备。例如，在终端侧设备发送重配置完成消息(切换完成)后，停止和第二网络侧设备建立的承载上的传输。
另一种可能的场景中，步骤601之前，终端侧设备也可以已经通过双连接的方式与第一网络侧设备以及第二网络侧设备建立连接。此时，第一PDCP实体已经存在，终端侧设备根据第一信息重建立第一PDCP实体。
需要说明的是，终端侧设备通过双连接的方式与第一网络侧设备以及第二网络侧设备建立连接时，第一网络侧设备可以为主网络侧设备，也可以为辅网络侧设备，本申请实施例对此并不限定。
本申请实施例对第一信息的名称以及实现形式并不限定，第一信息可以通过第一网络侧设备发送的消息携带，第一信息本身也可以为第一网络侧设备发送的一个消息，例如第一信息可以为RRC重配置消息等，在此不再逐一举例说明。
本申请实施例中，一种可能的实现方式中，第一信息可以直接指示终端侧设备建立第一PDCP实体；另一种可能的实现方式中，第一信息可能并不直接指示终端侧设备建立第一PDCP实体，而是间接指示终端侧设备建立第一PDCP实体。举例来说，在第一种可能的场景下，第一信息可以用于通知终端侧设备更改或增加第一PDCP实体所使用的加密密钥，终端侧设备根据第一信息确定更改或增加所述加密密钥时，则确定同时建立第一PDCP实体，在该情况下，第一PDCP实体已经存在，“建立第一PDCP实体”可以理解为“重建立第一PDCP实体”。在第二种可能的场景下，第一信息可以用于通知终端侧设备进行全配置(full configuration)的重配置，此时，终端侧设备根据第一信息确定进行全配置的重配置时，则确定同时建立第一PDCP实体，在该情况下，第一PDCP实体已经存在，“建立第一PDCP实体”可以理解为“重建立第一PDCP实体”。在第三种可能的场景下，第一信息可以用于通知终端侧设备增加一个第一PDCP实体，使得终端侧设备能够使用第一PDCP实体对应的承载通过核心网侧设备进行数据收发。此时，终端侧设备可以根据第一信息，确定同时建立第一PDCP实体，在该情况下，第一PDCP实体原先不存在，“建立第一PDCP实体”可以理解为“新建立第一PDCP实体”。其中，所述核心网侧设备可以是指UPF设备。
步骤602：终端侧设备接收第一信息。
步骤602之前，若终端侧设备与第二网络侧设备建立了连接，一种可能的实现方式中， 第一信息是由第一网络侧设备发送的，即终端侧设备接收的第一信息来自第一网络侧设备；另一种可能的实现方式中，第一信息是由第二网络侧设备发送的，即终端侧设备接收的第一信息来自第二网络侧设备。第一信息是由第二网络侧设备发送的情况下，第一网络侧设备可以指示第二网络侧设备发送第一信息，具体如何指示，本申请实施例对此并不限定，在此不再赘述。
可以理解，第一信息可以指示终端侧设备发送第二信息。进一步的，第一信息还可包含指示终端侧设备上报哪个承载或逻辑信道的第二信息、协议数据单元会话标识、业务质量流标识。
步骤603：所述终端侧设备根据所述第一信息建立所述第一PDCP实体，并向第一网络侧设备发送第二信息。
所述第二信息用于指示所述第一PDCP实体要发送的下一个PDCP SDU的序列号或计数值。另一种描述方式，所述第二信息可用于指示所述第一PDCP实体所在承载在第一网络设备侧的PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。第一网络侧设备接收第二信息后，根据所述第二信息确定上行期望要接收的下一个PDCPSDU的序列号或计数值。例如，用第二信息中的值设置期望要接收的下一个PDCP SDU的序列号或计数值。第二信息可以通过终端侧设备发送的消息携带，也可以为一个独立的消息。进一步的，一种可能的实现方式中，第二信息还可以指示第二信息是给哪个无线承载或哪个逻辑信道用的，即指示第一PDCP实体所对应的无线承载或逻辑信道。
如前所述，步骤601之前，所述终端侧设备已经与第二网络侧设备建立了连接，终端侧设备还包括第二PDCP实体，所述第二PDCP实体对应第二承载。所述第一PDCP实体对应的第一承载与所述第二PDCP实体对应的第二承载是一对用于进行重复传输的承载。如图1(a)至图3所述，终端侧设备可以采用PDCP层报文复制技术传输PDCP SDU，为此终端侧设备建立两个无线承载，所述两个无线承载传输相同的PDCP SDU，这两个无线承载可以称为用于在终端侧设备和核心网侧设备之间进行重复传输的无线承载。举例来说，图2中的DRB1和DRB2就是用于在终端侧设备和核心网侧设备之间进行重复传输的无线承载。结合上面的描述，终端侧设备可以根据所述第二PDCP实体的第一变量确定所述终端侧设备的所述第一PDCP实体要发送的下一个PDCPSDU的序列号或计数值；其中，所述第二PDCP实体的第一变量，可以是指发送侧变量TX_NEXT，用于指示所述第二PDCP实体要发送的下一个PDCP SDU的序列号或计数值，为了进行区分，命名为第一变量，以下不再赘述。在该实现方式下，终端侧设备可以将第一变量指示的值作为第二信息，即作为终端侧设备的第一PDCP实体要发送的下一个PDCPSDU的序列号或计数值。例如，终端侧设备新建立第一PDCP实体时，第一PDCP实体要发送的下一个PDCP SDU的序列号从0开始取值，但是终端侧设备的第二PDCP实体要发送的下一个PDCP SDU的序列号为100，此时终端侧设备将100作为第二信息，发送至第一网络侧设备，并将通过第一PDCP实体发送的PDCP PDU的序列号从100开始取值。
本申请实施例中，所述终端侧设备还可以向所述第一网络侧设备发送第三信息，所述第三信息指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。结合上面的描述，终端侧设备可以根据第二PDCP实体的第二变量确定所述终端侧设备的所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值；其中，所述第二 PDCP实体的所述第二变量，可以是指第一接收侧变量RX_NEXT，用于指示所述第二PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值，为了进行区分，命名为第二变量，以下不再赘述。例如，终端侧设备新建立第一PDCP实体时，第一PDCP实体期望要接收的下一个PDCP SDU的序列号为0，但是终端侧设备的第二PDCP实体期望要接收的下一个PDCP SDU的序列号为150，此时终端侧设备将150作为第二信息，发送至第一网络侧设备，并将通过第一PDCP实体发送的PDCP PDU的序列号从150开始取值。
需要说明的是，第一信息、第二信息与第三信息可以通过同一个消息发送，也可以通过不同的消息先后发送，本申请实施例对此并不限定。
一种可能的实现方式中，终端侧设备可以通知第一网络侧设备是否发送第二信息和/或第三信息，例如终端侧设备可以向第一网络侧设备发送第四信息，所述第四信息指示所述终端侧设备发送所述第二信息，或者，所述第四信息指示所述终端侧设备发送所述第二信息以及所述第三信息。
需要说明的是，以上只是示例，终端侧设备还可以向第一网络侧设备发送其它信息，例如第五信息、第六信息等，所述第五信息指示所述第一PDCP实体第一个没有被递交到上层的PDCP SDU的序列号或计数值；第六信息指示终端侧设备的第一PDCP实体触发重排序定时器的PDCP PDU的序列号或计数值。第五信息可以根据第二PDCP实体的第三变量确定，第三变量为终端侧设备的第二PDCP实体第一个没有被递交到上层的PDCP SDU的序列号或计数值；第六信息可以根据第二PDCP实体的第四变量确定，第四变量为终端侧设备的第二PDCP实体触发重排序定时器的PDCP PDU的序列号或计数值，具体内容可以参考第二信息或第三信息中的描述，在此不再赘述。
可选的，一种可能的实现方式中，终端侧设备在发送第二信息之前，可以先判断第一PDCP实体对应的第一承载是否为在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。当所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载时，向第一网络侧设备发送第二信息。本申请实施例中，终端侧设备可以通过多种方式确定第一承载是否为用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载，具体可以参考图4所示的流程中的描述，在此不再赘述。
步骤604：所述第一网络侧设备接收第二信息。
所述第一网络侧设备可以从所述终端侧设备接收所述第二信息；或者，所述第一网络侧设备也可以从第二网络侧设备接收所述第二信息，即终端侧设备将第二信息发送至第二网络侧设备，第二网络侧设备将第二信息转发至第一网络侧设备。
第一网络侧设备接收到第二信息之后，可以将第一网络侧设备中与第一PDCP实体对应的PDCP实体的第一接收侧变量RX_NEXT，置为第二信息指示的计数值。例如，第二信息指示的PDCP SDU的序列号为100，则第一网络侧设备中与第一PDCP实体对应的PDCP实体的第一接收侧变量RX_NEXT可以置为与100对应的计数值；第二信息指示的PDCP SDU的计数值为100，则第一网络侧设备中与第一PDCP实体对应的PDCP实体的第一接收侧变量RX_NEXT可以置为100。通过这种方法，第一网络侧设备接收到终端侧设备的PDCP SDU时，可以使用第二信息指示的PDCP SDU的序列号或计数值，从而可以避免终端侧设备按照第二PDCP实体中发送的PDCP SDU的序列号向第一网络侧设备发送 PDCP SDU，但是第一网络侧设备按照从0开始的PDCP SDU序列号接收PDCP SDU，导致第一网络侧设备误以为PDCP SDU出现丢包，重复启动重排序定时器，导致延迟向上层递交数据包，增加传输时延。
相应的，当第一网络侧设备接收到第三信息之后，可以将第一网络侧设备中与第一PDCP实体对应的PDCP实体的发送侧变量TX_NEXT，置为第三信息指示的计数值。例如，第三信息指示的PDCP SDU的序列号为150，则第一网络侧设备中与第一PDCP实体对应的PDCP实体的发送侧变量TX_NEXT可以置为与150对应的计数值；第二信息指示的PDCP SDU的计数值为150，则第一网络侧设备中与第一PDCP实体对应的PDCP实体的发送侧变量TX_NEXT可以置为150。
可以理解，当终端侧设备发送序列号的场景，第一网络侧设备只收到序列号，可根据这个重建立的第一PDCP之前的HFN和从终端侧设备收到的序列号确定计数值。
可以理解，当终端侧设备发送序列号的场景，第一网络侧设备从第二网络侧设备接收可用于第一PDCP实体的HFN。第一网络侧设备还可从第二网络侧设备接收该HFN所关联的一个承载标识或GTP隧道标识等。第一网络侧设备确定所述HFN为可用于第一PDCP的HFN时，根据从第二网络侧设备收到的所述HFN和从终端侧设备收到的PDCP SDU的序列号确定PDCP SDU的计数值。可选的，第一网络侧设备请求第二网络侧设备发送所述HFN。
下面通过一个具体的实施例描述图6所示的过程。如图7所示，为本申请实施例提供的一种PDCP实体重建立流程示意图。
图7所示的流程中，终端侧设备通过双连接的方式与网络侧设备A以及网络侧设备B建立连接，终端侧设备可以应用图6所示的流程中的终端侧设备的方法，网络侧设备A可以应用图6所示的流程中的第一网络侧设备的方法，网络侧设备B可以应用图6所示的流程中的第二网络侧设备的方法。终端侧设备中包括PDCP实体1和PDCP实体2，PDCP实体1对应无线承载1，PDCP实体2对应无线承载2，无线承载1和无线承载2是一对用于进行重复传输的承载，即无线承载1和无线承载2中传输的PDCP SDU的内容相同，UPF设备接收到通过无线承载1和无线承载2传输的PDCP SDU时，可以根据PDCP SDU的序列号进行去重处理。
步骤701：网络侧设备A向终端侧设备发送RRC重配置消息。
RRC重配置消息可以为图6所示的流程中的第一信息，也可以包括图6所示的流程中的第一信息。RRC重配置消息可以用于通知终端侧设备更改或增加PDCP实体1所使用的加密密钥，也可以用于通知终端侧设备进行全配置(full configuration)的重配置，也可以用于切换过程通知终端设备切换到一个小区，也可以用于新建一个承载用于终端侧设备和UPF设备间进行重复数据传输。PDCP实体1相当于图6所示的流程中的第一PDCP实体。
步骤702：终端侧设备向网络侧设备A发送RRC重配置完成消息。
RRC重配置完成消息可以为图6所示的流程中的第二信息，也可以包括图6所示的流程中的第二信息。
终端侧设备接收到RRC重配置消息时，可以确定除了更改或增加PDCP实体1所使用的加密密钥或者进行全配置的重配置、新建承载、切换到目标小区之外，还重建立PDCP实体1。
当PDCP实体1重建立时，网络侧设备A中与PDCP实体1对应的PDCP实体3也重 建立。由于无线承载1和无线承载2中传输的PDCP SDU的内容相同，因此无线承载1和无线承载2中传输的PDCP SDU的序列号相同。网络侧设备A中PDCP实体3重建立之后，PDCP实体3的发送侧变量TX_NEXT、第一接收侧变量RX_NEXT，第二接收侧变量RX_DELIV，第三接收侧变量RX_REORD等都置为0，但是网络侧设备B中与PDCP实体2对应的PDCP实体4并没有重建立，终端侧设备的PDCP实体2向网络侧设备B发送的PDCP SDU的序列号并不为0。为此，终端侧设备将PDCP实体2中下一个要发送的PDCP SDU的序列号或计数值，作为第二信息发送至网络侧设备A。网络侧设备A根据第二信息，可以确定在PDCP实体3中期望要接收的下一个PDCP SDU的序列号或计数值，从而不会按照从0开始的PDCP SDU序列号接收PDCP SDU，避免重复启动重排序定时器，导致的延迟向上层递交数据包，降低传输时延。
终端侧设备还可以向网络侧设备A发送第三信息、第四信息、第五信息以及第六信息等，在此不再赘述。
可以理解，第二信息、第三信息、第四信息是可选发送到网络侧设备A。
可选的，步骤703：网络侧设备A向网络侧设备B发送第二信息。
若第二信息、第三信息、第四信息没有发送到网络侧设备A。
可以理解，网络侧设备A可默认使用这个重建立的第一PDCP之前的计数值。
可以理解，网络侧设备B从网络侧设备A接收可用于第一PDCP实体的HFN、序列号和计数值中的至少一个。网络侧设备B还可从网络侧设备A接收该HFN、序列号或计数值所关联的一个承载标识或GTP隧道标识等。网络侧设备B确定所述HFN可用于第一PDCP的HFN。网络侧设备B确定所述序列号可用于第一PDCP的序列号。网络侧设备B确定所述计数值可用于第一PDCP的计数值。网络侧设备B没有从网络侧设备A收到的部分，可默认为0。可选的，网络侧设备B也可以请求网络侧设备A发送所述HFN、序列号或计数值。
上述本申请提供的实施例中，分别从各个网元本身、以及从各个网元之间交互的角度对本申请实施例提供的通信方法的各方案进行了介绍。可以理解的是，各个网元和设备，例如上述无线接入网设备、接入及移动性管理功能网元、用户设备、数据管理功能网元和网络切片选择功能网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
当上述网元通过软件模块来实现相应的功能时，可以参考图8所示。如图8所示，为本申请实施例提供一种通信装置的结构示意图。该通信装置可以用于执行上述各方法实施例中终端侧设备或者第一网络侧设备的动作，该通信装置800包括：收发单元801和处理单元802。
通信装置800执行图4所示的流程中的终端侧设备的动作时，收发单元801和处理单元802分别执行以下步骤：
收发单元801，用于接收来自第一网络侧设备的第一指示信息，所述第一指示信息触发重建立所述终端侧设备的第一PDCP实体；
处理单元802，用于在所述第一PDCP实体对应的第一承载不是在终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，且在所述终端侧设备重建立所述第一PDCP实体的过程中，将所述第一PDCP实体的参数置为初始值；其中，所述第一PDCP的参数包括第一参数、第二参数以及第三参数中的至少一项，所述第一参数用于指示所述第一PDCP实体期望要接收的下一个PDCP服务数据单元SDU的序列号或计数值；所述第二参数用于指示所述第一PDCP实体要发送的下一个PDCP SDU的序列号或计数值；所述第三参数用于指示没有被所述第一PDCP实体向上层递交的第一个PDCP SDU的序列号或计数值。
在一种可能的设计中，在所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，在所述终端侧设备重建立所述第一PDCP实体的过程中，保持所述第一PDCP实体的参数不变。
在一种可能的设计中，所述收发单元801还用于：接收来自所述第一网络侧设备的第二指示信息，所述第二指示信息指示将所述第一PDCP实体的参数置为初始值。
在一种可能的设计中，所述收发单元801还用于：接收来自所述第一网络侧设备的第三指示信息，所述第三指示信息指示所述第一承载不是用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载。
在一种可能的设计中，所述第一承载为非确认模式UM承载。
通信装置800执行图6所示的流程中的终端侧设备的动作时，收发单元801和处理单元802分别执行以下步骤：
收发单元801，用于接收第一信息，所述第一信息触发建立第一分组数据聚合协议PDCP实体；
处理单元802，用于建立所述第一PDCP实体，并向第一网络侧设备发送第二信息，所述第二信息用于指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
在一种可能的设计中，所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。
在一种可能的设计中，所述收发单元801还用于：向所述第一网络侧设备发送第三信息，所述第三信息指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述收发单元801还用于：向所述第一网络侧设备发送第四信息，所述第四信息指示所述终端侧设备发送所述第二信息。
在一种可能的设计中，所述终端侧设备还包括第二PDCP实体，所述第一PDCP实体对应的第一承载与所述第二PDCP实体对应的第二承载是一对用于进行重复传输的承载；所述处理单元802还用于：根据所述第二PDCP实体的第一变量确定所述终端侧设备的所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值；其中，所述第二PDCP实体的所述第一变量，用于指示所述第二PDCP实体要发送的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述处理单元802还用于：根据所述第二PDCP实体的第二变量确定所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值；
其中，所述第二PDCP实体的所述第二变量，用于指示所述第二PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述终端侧设备通过双连接方式与所述第一网络侧设备以及第二网络侧设备连接，所述收发单元801具体用于：从所述第一网络侧设备接收所述第一信息；或者，所述终端侧设备从所述第二网络侧设备接收所述第一信息。
通信装置800执行图6所示的流程中的第一网络侧设备的动作时，收发单元801和处理单元802分别执行以下步骤：
收发单元801，用于发送第一信息，所述第一信息触发终端侧设备建立第一分组数据聚合协议PDCP实体；接收第二信息，所述第二信息指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
在一种可能的设计中，所述收发单元801还用于：接收第三信息，所述第三信息用于指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述处理单元802，用于根据所述第三信息，确定与所述第一PDCP实体对应的PDCP实体要向所述终端侧设备发送的下一个PDCP SDU的序列号或计数值。
图9是本申请实施例提供的一种终端侧设备的结构示意图。图9所示的通信装置可以为图8所示的通信装置的一种硬件电路的实现方式。该终端侧设备可适用于实现上述方法中终端侧设备的功能。为了便于说明，图9仅示出了终端侧设备900的主要部件。该终端侧设备900包括处理器901、存储器902、收发机903、天线904以及输入输出装置905。所述存储器902用于与处理器901耦合，其保存该终端侧设备900必要的计算机程序。处理器901主要用于对通信协议以及通信数据进行处理，以及对整个无线通信装置进行控制，执行软件程序，处理软件程序的数据，例如用于支持无线通信装置执行上述方法实施例中所描述的动作等。收发机903主要用于基带信号与射频信号的转换以及对射频信号的处理。天线904主要用于收发电磁波形式的射频信号。输入输出装置905，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
该终端侧设备900执行图4所示的流程中的终端侧设备的动作时，执行以下步骤：
收发机903，用于接收来自第一网络侧设备的第一指示信息，所述第一指示信息触发重建立所述终端侧设备的第一PDCP实体；
处理器901，用于在所述第一PDCP实体对应的第一承载不是在终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，且在所述终端侧设备重建立所述第一PDCP实体的过程中，将所述第一PDCP实体的参数置为初始值；其中，所述第一PDCP的参数包括第一参数、第二参数以及第三参数中的至少一项，所述第一参数用于指示所述第一PDCP实体期望要接收的下一个PDCP服务数据单元SDU的序列号或计数值；所述第二参数用于指示所述第一PDCP实体要发送的下一个PDCP SDU的序列号或计数值；所述第三参数用于指示没有被所述第一PDCP实体向上层递交的第一个PDCP SDU的序列号或计数值。
在一种可能的设计中，在所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，在所述终端侧设备重建立所述第一 PDCP实体的过程中，保持所述第一PDCP实体的参数不变。
在一种可能的设计中，所述收发机903还用于：接收来自所述第一网络侧设备的第二指示信息，所述第二指示信息指示将所述第一PDCP实体的参数置为初始值。
在一种可能的设计中，所述收发机903还用于：接收来自所述第一网络侧设备的第三指示信息，所述第三指示信息指示所述第一承载不是用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载。
在一种可能的设计中，所述第一承载为非确认模式UM承载。
该终端侧设备900执行图6所示的流程中的终端侧设备的动作时，执行以下步骤：
收发机903，用于接收第一信息，所述第一信息触发建立第一分组数据聚合协议PDCP实体；
处理器901，用于建立所述第一PDCP实体，并向第一网络侧设备发送第二信息，所述第二信息用于指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
在一种可能的设计中，所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。
在一种可能的设计中，所述收发机903还用于：向所述第一网络侧设备发送第三信息，所述第三信息指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述收发机903还用于：向所述第一网络侧设备发送第四信息，所述第四信息指示所述终端侧设备发送所述第二信息。
在一种可能的设计中，所述终端侧设备还包括第二PDCP实体，所述第一PDCP实体对应的第一承载与所述第二PDCP实体对应的第二承载是一对用于进行重复传输的承载；所述处理器901还用于：根据所述第二PDCP实体的第一变量确定所述终端侧设备的所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值；其中，所述第二PDCP实体的所述第一变量，用于指示所述第二PDCP实体要发送的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述处理器901还用于：根据所述第二PDCP实体的第二变量确定所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值；
其中，所述第二PDCP实体的所述第二变量，用于指示所述第二PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述终端侧设备通过双连接方式与所述第一网络侧设备以及第二网络侧设备连接，所述收发机903具体用于：从所述第一网络侧设备接收所述第一信息；或者，所述终端侧设备从所述第二网络侧设备接收所述第一信息。
图10是本申请实施例提供的一种网络侧设备的结构示意图。图10所示的网络侧设备可以为图8所示的通信装置的一种硬件电路的实现方式。该网络侧设备可适用于图6所示出的流程图中，执行上述方法实施例中第一网络侧设备的功能。为了便于说明，图10仅示出了网络侧设备的主要部件。如图10所示，网络侧设备1000包括处理器1001、存储器1002、射频模块1003、天线1004等。
射频模块1003，用于发送第一信息，所述第一信息触发终端侧设备建立第一分组数据 聚合协议PDCP实体；接收第二信息，所述第二信息指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
在一种可能的设计中，所述射频模块1003还用于：接收第三信息，所述第三信息用于指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
在一种可能的设计中，所述处理器1001，用于根据所述第三信息，确定与所述第一PDCP实体对应的PDCP实体要向所述终端侧设备发送的下一个PDCP SDU的序列号或计数值。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (22)

  1. 一种实体建立的处理方法，其特征在于，包括：
    终端侧设备接收来自第一网络侧设备的第一指示信息，所述第一指示信息触发重建立所述终端侧设备的第一分组数据聚合协议PDCP实体；
    在所述第一PDCP实体对应的第一承载不是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，且在所述终端侧设备重建立所述第一PDCP实体的过程中，将所述第一PDCP实体的参数置为初始值；
    其中，所述第一PDCP的参数包括第一参数、第二参数以及第三参数中的至少一项，所述第一参数用于指示所述第一PDCP实体期望要接收的下一个PDCP服务数据单元SDU的序列号或计数值；所述第二参数用于指示所述第一PDCP实体要发送的下一个PDCP SDU的序列号或计数值；所述第三参数用于指示没有被所述第一PDCP实体向上层递交的第一个PDCP SDU的序列号或计数值。
  2. 根据权利要求1所述的方法，其特征在于，在所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载的情况下，在所述终端侧设备重建立所述第一PDCP实体的过程中，保持所述第一PDCP实体的参数不变。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述终端侧设备接收来自所述第一网络侧设备的第二指示信息，所述第二指示信息指示将所述第一PDCP实体的参数置为初始值。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    所述终端侧设备接收来自所述第一网络侧设备的第三指示信息，所述第三指示信息指示所述第一承载不是用于在所述终端侧设备和所述核心网侧设备之间进行重复传输的无线承载。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述第一承载为非确认模式UM承载。
  6. 一种实体建立的处理方法，其特征在于，包括：
    终端侧设备接收第一信息，所述第一信息触发建立第一分组数据聚合协议PDCP实体；
    所述终端侧设备建立所述第一PDCP实体，并向第一网络侧设备发送第二信息，所述第二信息用于指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
  7. 根据权利要求6所述的方法，其特征在于，所述第一PDCP实体对应的第一承载是在所述终端侧设备和核心网侧设备之间进行重复传输的无线承载。
  8. 根据权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述终端侧设备向所述第一网络侧设备发送第三信息，所述第三信息指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
  9. 根据权利要求6至8任一所述的方法，其特征在于，所述方法还包括：所述终端侧设备向所述第一网络侧设备发送第四信息，所述第四信息指示所述终端侧设备发送所述第二信息。
  10. 根据权利要求6至9任一所述的方法，其特征在于，所述终端侧设备还包括第二PDCP实体，所述第一PDCP实体对应的第一承载与所述第二PDCP实体对应的第二承载 是一对用于进行重复传输的承载；所述方法还包括：
    所述终端侧设备根据所述第二PDCP实体的第一变量确定所述终端侧设备的所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值；
    其中，所述第二PDCP实体的所述第一变量，用于指示所述第二PDCP实体要发送的下一个PDCP SDU的序列号或计数值。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述终端侧设备根据所述第二PDCP实体的第二变量确定所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值；
    其中，所述第二PDCP实体的所述第二变量，用于指示所述第二PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
  12. 根据权利要求6至11任一所述的方法，所述终端侧设备通过双连接方式与所述第一网络侧设备以及第二网络侧设备连接，其特征在于，所述终端侧设备接收第一信息，包括：
    所述终端侧设备从所述第一网络侧设备接收所述第一信息；
    或者，所述终端侧设备从所述第二网络侧设备接收所述第一信息。
  13. 一种实体建立的处理方法，其特征在于，包括：
    第一网络侧设备发送第一信息，所述第一信息触发终端侧设备建立第一分组数据聚合协议PDCP实体；
    所述第一网络侧设备接收第二信息，所述第二信息指示所述第一PDCP实体要发送的下一个PDCP服务数据单元SDU的序列号或计数值。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第一网络侧设备接收第三信息，所述第三信息用于指示所述第一PDCP实体期望要接收的下一个PDCP SDU的序列号或计数值。
  15. 根据权利要求14所述的方法，其特征在于，所述第一网络侧设备根据所述第三信息，确定与所述第一PDCP实体对应的PDCP实体要向所述终端侧设备发送的下一个PDCP SDU的序列号或计数值。
  16. 一种装置，其特征在于，用于执行如权利要求1-5中任一项所述的方法。
  17. 一种装置，其特征在于，用于执行如权利要求6-12中任一项所述的方法。
  18. 一种装置，其特征在于，用于执行如权利要求13-15中任一项所述的方法。
  19. 一种装置，其特征在于，包括：处理器，所述处理器与存储器耦合；
    存储器，用于存储计算机程序；
    处理器，用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求1-5中任一项所述的方法。
  20. 一种装置，其特征在于，包括：处理器，所述处理器与存储器耦合；
    存储器，用于存储计算机程序；
    处理器，用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求6-12中任一项所述的方法。
  21. 一种装置，其特征在于，包括：处理器，所述处理器与存储器耦合；
    存储器，用于存储计算机程序；
    处理器，用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求 13-15中任一项所述的方法。
  22. 一种可读存储介质，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，如权利要求1-15中任一项所述的方法被执行。
PCT/CN2020/075144 2019-02-15 2020-02-13 一种实体建立的处理方法及装置 WO2020164556A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20756624.1A EP3913840B1 (en) 2019-02-15 2020-02-13 Method and apparatus for processing establishment of entities
US17/401,963 US12082305B2 (en) 2019-02-15 2021-08-13 Entity establishment processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910117738.9A CN111585721B (zh) 2019-02-15 2019-02-15 一种实体建立的处理方法及装置
CN201910117738.9 2019-02-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/401,963 Continuation US12082305B2 (en) 2019-02-15 2021-08-13 Entity establishment processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2020164556A1 true WO2020164556A1 (zh) 2020-08-20

Family

ID=72045117

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075144 WO2020164556A1 (zh) 2019-02-15 2020-02-13 一种实体建立的处理方法及装置

Country Status (4)

Country Link
US (1) US12082305B2 (zh)
EP (1) EP3913840B1 (zh)
CN (1) CN111585721B (zh)
WO (1) WO2020164556A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114390619B (zh) * 2020-10-21 2024-02-09 大唐移动通信设备有限公司 传输方法及设备
CN112929297B (zh) * 2021-01-21 2023-12-29 北京小米移动软件有限公司 一种资源分配方法、资源分配装置及存储介质
CN117395611A (zh) * 2022-07-05 2024-01-12 华为技术有限公司 通信方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106134099A (zh) * 2014-01-29 2016-11-16 三星电子株式会社 用于在移动通信系统中使用多个载波来发送和接收数据的方法和设备
CN107079516A (zh) * 2014-03-31 2017-08-18 阿尔卡特朗讯 承载释放

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030177437A1 (en) * 2002-03-18 2003-09-18 Wu Frank Chih-Hsiang Erroneous packet data convergence protocol data unit handling scheme in a wireless communication system
KR101525252B1 (ko) * 2007-12-31 2015-06-02 삼성전자주식회사 무선 통신 시스템에서의 하이퍼 프레임 넘버 비동기 방지 방법
CN101841853A (zh) * 2009-03-17 2010-09-22 中兴通讯股份有限公司 一种用户设备以及用户设备接收下行数据的方法
GB2513313A (en) * 2013-04-22 2014-10-29 Sony Corp Infrastructure equipment, mobile communications network and method
CN114885375B (zh) * 2016-08-09 2024-08-09 三星电子株式会社 无线通信系统中管理用户平面操作的方法和装置
CN109691159B (zh) * 2016-09-13 2024-01-12 诺基亚技术有限公司 Rrc连接恢复中的pdcp count处理
WO2018085118A1 (en) * 2016-11-01 2018-05-11 Intel IP Corporation Downlink control information design with shorter tti
CN108347727B (zh) * 2017-01-24 2023-04-07 中兴通讯股份有限公司 一种数据传输方法及装置
CN108366369B (zh) * 2017-01-26 2021-02-12 华为技术有限公司 一种数据安全传输的方法及接入网、终端、核心网设备
CN108924964B (zh) * 2017-04-07 2023-05-23 中兴通讯股份有限公司 保证通信连续性的方法和用户设备
CN107094142B (zh) * 2017-04-28 2020-11-27 电信科学技术研究院 一种上行数据解压缩、压缩的方法和装置
BR112019000694B1 (pt) * 2017-08-10 2022-10-18 Lg Electronics Inc. Método executado por um dispositivo de recebimento operando em um sistema de comunicação sem fio e dispositivo de recebimento configurado para operar em um sistema de comunicação sem fio
US10582556B2 (en) * 2017-08-11 2020-03-03 Htc Corporation Device and method for handling a bearer type change
CN109803331B (zh) * 2017-11-16 2021-05-18 华为技术有限公司 数据处理方法、装置以及计算机存储介质
CN110012454B (zh) * 2018-01-05 2023-07-14 夏普株式会社 用户设备和相关方法
US10912031B2 (en) * 2018-04-05 2021-02-02 Samsung Electronics Co., Ltd. Method and apparatus for operating protocol layer of terminal in inactive mode in next-generation mobile communication system
US11388768B2 (en) * 2018-05-18 2022-07-12 Lg Electronics Inc. Method and apparatus for performing a connection re-establishment and retransmission of packets by user equipment in wireless communication system
WO2019245443A2 (en) * 2018-06-21 2019-12-26 Telefonaktiebolaget Lm Ericsson (Publ) Preventing/mitigating packet loss in iab systems
WO2020029414A1 (zh) * 2018-08-07 2020-02-13 Oppo广东移动通信有限公司 无线通信方法、通信设备、芯片和通信系统
AU2018448123B2 (en) * 2018-10-30 2023-01-19 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for indicating state of PDCP duplicate data, terminal device, and network device
WO2020150997A1 (en) * 2019-01-25 2020-07-30 Mediatek Singapore Pte. Ltd. Apparatus and methods to support dual-protocol for mobility enhancement
WO2020165278A1 (en) * 2019-02-13 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Using alternative paths of descendant nodes for backhaul-link failure reporting in integrated access
WO2020165280A1 (en) * 2019-02-13 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Alternate path information exchange for better scheduling and backhaul failure recovery in integrated access backhaul networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106134099A (zh) * 2014-01-29 2016-11-16 三星电子株式会社 用于在移动通信系统中使用多个载波来发送和接收数据的方法和设备
CN107079516A (zh) * 2014-03-31 2017-08-18 阿尔卡特朗讯 承载释放

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI; HISILICON: "RLC behaviors upon duplicate deactivation", 3GPP DRAFT; R2-1712735, 1 December 2017 (2017-12-01), Reno, Nevada, USA, pages 1 - 2, XP051371641 *
See also references of EP3913840A4 *
VIVO: "Layer-2 behaviors of PDCP duplication activation deactivation", 3GPP DRAFT; R2-1708508, 25 August 2017 (2017-08-25), pages 1 - 3, XP051318363 *

Also Published As

Publication number Publication date
US20210385905A1 (en) 2021-12-09
EP3913840A1 (en) 2021-11-24
CN111585721B (zh) 2022-08-19
CN111585721A (zh) 2020-08-25
EP3913840A4 (en) 2022-03-16
EP3913840B1 (en) 2024-06-19
US12082305B2 (en) 2024-09-03

Similar Documents

Publication Publication Date Title
EP3634036B1 (en) Dc-based handover method and device
US11751112B2 (en) Handover method and device
EP3014944B1 (en) Master base station-controlled response to detected failure of radio link between secondary base station and mobile station in dual connectivity wireless networks
EP3048845B1 (en) Device and method for data transmission
US10863569B2 (en) RRC connection re-establishment method for data transmission
WO2020164556A1 (zh) 一种实体建立的处理方法及装置
WO2019059836A1 (en) METHODS AND UNITS IN A NETWORK NODE FOR PROCESSING COMMUNICATION WITH A WIRELESS DEVICE
WO2018127219A1 (zh) 一种减少中断时延的方法、装置及用户设备
WO2019095974A1 (zh) 数据处理方法、装置以及计算机存储介质
WO2014023269A1 (zh) 一种切换控制方法及装置
WO2022110168A1 (zh) 通信配置的方法和通信装置
US20200322094A1 (en) Submitting a PDCP PDU for Transmission
WO2014166053A1 (zh) 一种通讯方法和终端
KR101739679B1 (ko) 통신 모드 전환 방법 및 장치와, 시스템
CN104429109B (zh) 一种通信方法及装置
WO2020164620A1 (zh) 一种终端信息的通信处理方法和相关设备
WO2020258018A1 (zh) 一种数据包处理方法、设备及存储介质
WO2022151297A1 (zh) 数据传输方法及装置
WO2023045173A1 (zh) 一种小区切换方法及通信装置
WO2023005919A1 (zh) 分组数据汇聚协议状态报告发送方法、设备及装置
WO2022204999A1 (zh) 存活时间的处理方法和终端设备
US20240031065A1 (en) Communication method and communication apparatus
WO2020124540A1 (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: 20756624

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

Country of ref document: EP

Effective date: 20210816