WO2024022198A1 - Procédé de distribution de données et dispositif de communication - Google Patents

Procédé de distribution de données et dispositif de communication Download PDF

Info

Publication number
WO2024022198A1
WO2024022198A1 PCT/CN2023/108176 CN2023108176W WO2024022198A1 WO 2024022198 A1 WO2024022198 A1 WO 2024022198A1 CN 2023108176 W CN2023108176 W CN 2023108176W WO 2024022198 A1 WO2024022198 A1 WO 2024022198A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
pdcp
pdus
received
pdcp entity
Prior art date
Application number
PCT/CN2023/108176
Other languages
English (en)
Chinese (zh)
Inventor
胡少领
徐海博
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024022198A1 publication Critical patent/WO2024022198A1/fr

Links

Classifications

    • 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
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • 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

Definitions

  • the present application relates to the field of wireless communications, and in particular, to a data delivery (deliver) method and communication equipment.
  • Extended reality refers to combining reality and virtuality through computers to create a virtual environment that allows human-computer interaction.
  • XR includes augmented reality (AR), virtual reality (VR), mixed reality (MR) and other technologies.
  • PDU set is a payload used to carry an information unit generated by the application layer.
  • a PDU set includes one or more PDUs.
  • a PDU set can refer to a frame of data, or a slice of data obtained by decomposing a frame of data.
  • the delay requirement for PDU can be described by the packet delay budget (PDB).
  • PDB represents the maximum transmission delay allowed for a PDU between the terminal device and the N6 interface.
  • the N6 interface is the access network device and the user. Interfaces between user plane functions (UPF).
  • PDU set delay budget PSDB
  • PSDB PDU set delay budget
  • the packet data convergence protocol (PDCP) entity inside the communication device will deliver the PDU to the upper layer in the order of the PDCP sequence number of the PDU, such as delivery to the service data adaptation. Protocol (service data adaptation protocol, SDAP) layer. If a data burst is encountered, for example, the application layer generates and sends multiple PDUs in a short period of time. Since the time is very short, it can be considered that multiple PDUs arrive at the gNB or terminal device almost at the same time. Then the PDCP entity inside the gNB or terminal device A large number of PDUs may be received in a short period of time.
  • SDAP service data adaptation protocol
  • Embodiments of the present application provide a data delivery method and communication equipment, which are used to provide a delivery method suitable for PDU sets within the communication equipment, so as to improve the delivery delay performance of the PDU set.
  • embodiments of the present application provide a data delivery method.
  • the method includes: the PDCP entity of the communication device receives the first PDU and the second PDU, the first PDU is the PDU that the PDCP entity has received and delivered to the upper layer, the upper layer is the upper layer of the PDCP entity, and the second PDU is received by the PDCP entity.
  • the PDCP sequence number of the first PDU is the first PDCP sequence number
  • the PDCP sequence number of the second PDU is the second PDCP sequence number
  • start the reordering timer where the PDCP sequence number of the third PDU is the third PDCP sequence number, and the third PDCP sequence number is greater than the first PDCP sequence number and less than the second PDCP sequence number
  • the reordering timer is running , if the number of PDUs associated with the second PDU received by the PDCP entity is greater than or equal to the first preset value, the PDCP entity delivers the received PDU associated with the second PDU to the upper layer, and the associated PDU has PDUs with the same identity.
  • the received PDU is not associated with the unreceived PDU. Failure to deliver PDUs in time will cause additional delivery delays for PDUs that are not associated with unreceived PDUs.
  • the PDCP entity at the receiving end starts the reordering timer, it will not just wait to receive the PDU that has been received but has not been received. Instead, while waiting, it will judge the received PDU associated with the second PDU.
  • the received PDUs will be compared with the second PDUs.
  • the associated PDU is delivered to the upper layer regardless of whether the reordering timer is currently running or expired. Therefore, after adopting the above method, the delivery delay of PDUs not associated with the third PDU will not increase due to the delay of the third PDU, thereby improving the delivery efficiency of the receiving end and reducing the loss caused by the sorting waiting delay. package, thereby improving user experience.
  • the identification includes a sequence number, the sequence number is different from the PDCP sequence number, and the sequence number is used to indicate the PDU set PDU set.
  • the PDU associated with the second PDU is a PDU that belongs to the same PDU set as the second PDU.
  • the upper layer includes the SDAP layer, PDUs with the same identification belong to the first PDU set, and the first preset value is less than or equal to the total number of PDUs included in the first PDU set.
  • the PDCP entity delivers the received PDU associated with the second PDU to The upper layer includes: when the number of PDUs in the first PDU set received by the PDCP entity is greater than or equal to the first preset value, and the first PDU set and the second PDU set are different PDU sets, the PDCP entity will receive the third PDU set.
  • the PDUs contained in one PDU set are delivered to the upper layer, where the second PDU set is the PDU set to which the third PDU belongs.
  • the headers of PDUs in PDUs with the same identification include: the identification of the PDU set to which the PDU belongs, the location information of the PDU in the PDU set to which it belongs, and the corresponding PDCP sequence number.
  • the location information indicates that the PDU is in the PDU set to which it belongs. Whether the set is the first PDU, the last PDU or the middle PDU; the first default value is the total number of PDUs included in the first PDU set; the PDCP entity determines that the PDCP sequence number is between the third PDCP sequence number and the third PDCP sequence number based on the PDU header.
  • the number of PDUs in the received first PDU set is greater than or equal to the first preset value, where the third PDCP sequence number is the first PDU in the first PDU set.
  • the PDCP sequence number of the first PDU, and the fourth PDCP sequence number is the PDCP sequence number of the last PDU in the first PDU set.
  • the headers of PDUs in PDUs with the same identification include: the identification of the PDU set to which the PDU belongs and the total number of PDUs included in the PDU set to which the PDU belongs; the first default value is the PDU included in the first PDU set Total quantity; if the PDCP entity determines that the number of PDUs belonging to the first PDU set received is greater than or equal to the total number of PDUs contained in the first PDU set, it determines that the number of PDUs in the first PDU set received is greater than or equal to equal to the first preset value.
  • the PDU among the PDUs with the same identifier is any PDU among the PDUs with the same identifier.
  • the headers of the PDUs in the PDUs with the same identification include a type identifier.
  • the type identifier is used to indicate whether the header of the PDU is a header of the first type.
  • the PDCP entity Identify the first target field in the header of the first type.
  • the first target field includes a first field and a second field; the first field includes the field where the identifier of the PDU set to which the PDU belongs, and the second field includes the field where the PDU belongs to the PDU set.
  • the upper layer includes a radio resource control RRC layer, and the RRC layer indicates first PDCP configuration information.
  • the first PDCP configuration information is used to instruct the PDCP entity to identify the second target field in the first header.
  • the first header is the header in the received PDU, and the second target field is used to indicate the type identification.
  • the PDU received by the PDCP entity is carried in the first wireless data bearer DRB.
  • the header of the PDU is a second type of header
  • the second type of header includes the identifier of the PDU set to which the PDU belongs and The location information of the PDU in the PDU set to which it belongs, or the identification of the PDU set to which the PDU belongs and the total number of PDUs contained in the PDU set to which the PDU belongs.
  • the upper layer includes an RRC layer.
  • the RRC layer indicates second PDCP configuration information.
  • the second PDCP configuration information is used to instruct the PDCP entity to map the first type PDU to the first DRB.
  • the first Type PDU is the PDU to be sent and having the second type header.
  • the header of the first PDU contains a first preset value; alternatively, the method further includes: the PDCP entity determines the first preset value based on the total number of PDUs included in the first PDU set and the preset proportion. value.
  • the header of the first PDU contains the total number of PDUs included in the first PDU set; and/or, the preset proportion is sent to the communication device through RRC signaling or application layer signaling, or, the first The PDU header contains a preset ratio.
  • the PDCP entity when the PDCP entity receives a data packet contained in the third PDU set that is greater than or equal to the second preset value, it delivers the PDU contained in the third PDU set to the upper layer and terminates the reordering timer.
  • the third PDU set is the PDU set to which the third PDU belongs
  • the third PDU set and the first PDU set are the same PDU set or different PDU sets
  • the header of the PDU included in the third PDU set contains the second default value
  • the PDCP entity determines the second preset value based on the total number of PDUs included in the third PDU set and the preset proportion.
  • the method further includes: the PDCP entity updating the to-be-delivered identification of the PDCP entity.
  • the identifier indicates that when the PDCP entity delivers PDUs to the upper layer sequentially according to the PDCP sequence number of the PDU, the identifier of the PDU that has not yet been delivered should be delivered.
  • the updated to-be-delivered identifier is used to indicate the identifier of the fourth PDU that should be delivered but has not yet been delivered.
  • the PDCP sequence number of the fourth PDU is after the PDCP sequence number of the third PDU, and the fourth PDU does not belong to the third PDU set.
  • the upper layer includes an RRC layer.
  • the RRC layer indicates the third PDCP configuration information.
  • the third PDCP configuration information is used to indicate the PDCP entity.
  • the communication device is an access network device or a terminal device.
  • inventions of the present application provide a data delivery method.
  • the method includes: the first communication device establishes L wireless data bearer DRBs, where L is an integer greater than 1.
  • the method includes: the SDAP entity of the first communication device obtains N protocol data unit PDUs, where N is an integer greater than 1; when the N PDUs have not yet been delivered to the PDCP layer and the N PDUs belong to M PDU sets, the SDAP entity will M PDU sets are mapped to L DRBs, where M is less than or equal to N and greater than 1; the first communication device sends M PDU sets to the second communication device through L DRBs.
  • M PDU sets are mapped to M DRBs included in L DRBs; or, when M is greater than L, the PDU set mapped by each DRB in L DRBs
  • the quantity does not exceed the integer obtained by rounding up M/L, and is not less than the integer obtained by rounding down M/L.
  • inventions of the present application provide a communication device.
  • the communication device includes a module/unit that performs the method of the above-mentioned first aspect and any possible implementation of the first aspect.
  • These modules/units can be implemented by hardware, or they can be implemented by hardware executing corresponding software.
  • the communication device may include a receiving module, a starting module and a delivering module.
  • the receiving module is configured to receive the PDU and the second PDU.
  • the first PDU is a PDU that has been received by the PDCP entity and has been delivered to the upper layer.
  • the upper layer is the upper layer of the PDCP entity.
  • the second PDU is received by the PDCP entity and has not yet been delivered to the
  • the PDCP sequence number of the first PDU is the first PDCP sequence number
  • the PDCP sequence number of the second PDU is the second PDCP sequence number.
  • the starting module is configured to start the reordering timer when the receiving module receives the second PDU but does not receive the third PDU.
  • the PDCP sequence number of the third PDU is the third PDCP sequence number, and the third PDCP sequence number is greater than the first PDCP sequence number and less than the second PDCP sequence number.
  • the delivery module is configured to deliver the received PDU associated with the second PDU to At the upper layer, the associated PDUs are PDUs with the same identifier.
  • inventions of the present application provide a communication device.
  • the communication device includes a module/unit that performs the method of any possible implementation of the above-mentioned second aspect and the first aspect.
  • These modules/units can be implemented by hardware, or they can be implemented by hardware executing corresponding software.
  • the communication device may include an acquisition module, a mapping module and a sending module.
  • the acquisition module is used to acquire N protocol data units PDU, where N is an integer greater than 1.
  • the mapping module is used to map M PDU sets to L DRBs when N PDUs have not yet been delivered to the PDCP layer and the N PDUs belong to M PDU sets, where M is less than or equal to N and greater than 1.
  • the sending module is used to send M PDU sets to the second communication device through L DRBs.
  • inventions of the present application provide a communication device.
  • the communication device includes: a processor, a memory and a communication interface respectively coupled to the processor.
  • the communication interface is used to communicate with other devices.
  • the processor is configured to run instructions or programs in the memory, and execute the method of the first aspect and any possible implementation of the first aspect through the communication interface.
  • inventions of the present application provide a communication device.
  • the communication device includes: a processor, a memory and a communication interface respectively coupled to the processor.
  • the communication interface is used to communicate with other devices.
  • the processor is configured to run instructions or programs in the memory, and execute the method of the second aspect and any possible implementation of the second aspect through the communication interface.
  • embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores instructions that, when run on a computer, cause the computer to perform the method described in the first aspect and any of its implementations, or to perform the method as described in the second aspect and any of its implementations. the method described.
  • embodiments of the present application provide a computer program product including instructions. When it is run on a computer, the computer is caused to perform the method described in the first aspect and any implementation thereof, or to perform the method described in the second aspect and any implementation thereof.
  • Figure 1(a) and Figure 1(b) are schematic diagrams of the situation where PDUs are received out of sequence according to the embodiment of the present application;
  • FIG. 2 is a schematic diagram of the network architecture provided by the embodiment of this application.
  • Figure 3 is a schematic flow chart of a data delivery method provided by an embodiment of the present application.
  • Figure 4(a) and Figure 4(b) are schematic diagrams of the situation where PDUs are not received in order during the PDU set delivery process provided by the embodiment of the present application;
  • Figure 5(a) to Figure 5(e) are schematic diagrams of the header of the PDU provided by the embodiment of the present application.
  • Figure 6(a) and Figure 6(b) are schematic diagrams of the situation where PDUs are not received in order during the PDU set delivery process provided by the embodiment of the present application;
  • Figure 7 is a schematic flow chart of another data delivery method provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the data sending end can be an access network device or a terminal device.
  • the PDCP entity is the data packet.
  • the data receiving end it can be an access network device or a terminal device.
  • the PDCP entity reads the PDCP SN from the PDU header of the received data packet.
  • the PDCP entity also needs to maintain the following three status variables:
  • (1)RX_DELIV used to indicate the count value of the first PDU in the PDU that needs to be delivered to the upper layer but has not yet been delivered to the upper layer.
  • the count value consists of the PDU's superframe number (hyperframenumber, HFN) and PDCP SN; HFN is calculated by the receiving end and the transmitting end respectively, without air interface transmission; PDCP SN is obtained from the header of the PDU.
  • (2)RX_NEXT Used to indicate the count value of the next PDU that the PDCP entity expects to receive.
  • (3)RX_REORD Used to indicate the count value of the next PDU of the PDU that triggers the reordering timer t-Reordering.
  • the PDCP entity at the receiving end receives PDU1 and PDU2, and delivers PDU1 and PDU2 to the upper layer.
  • the first PDU that currently needs to be delivered to the upper layer is PDU3, and RX_DELIV is PDU3.
  • the PDCP entity did not receive PDU3, but received PDU4 to PDU7.
  • the next PDU expected to be received by the PDCP entity is PDU8, that is, RX_NEXT is the count value of PDU8.
  • RX_DELIV When RX_DELIV ⁇ RX_NEXT, it means that the PDUs received by the PDCP entity are out of order, resulting in a vacancy in the PDCP SN.
  • RX_REORD is updated to the current RX_NEXT value, and the reordering timer t-Reordering is started at the same time.
  • the PDCP entity receives the PDU corresponding to the vacant PDCP SN, it will deliver the PDU to the upper layer and update RX_DELIV. If the updated RX_DELIV is greater than or equal to RX_REORD, the reordering timer t-Reordering is terminated.
  • the data packet between the current RX_DELIV and the current RX_REORD will be delivered upward, and the PDU after the received RX_REORD will be delivered upwards. Delivered to the upper layer in sequence until the PDCP SN of the PDU is vacant again or until the received PDU is sent, and then RX_DELIV is updated. If the updated RX_DELIV ⁇ RX_NEXT, it means that there is still a PDCP SN vacancy, update RX_REORD to the current RX_NEXT again, and start the reordering timer t-Reordering.
  • the receiving PDCP entity received PDU4 without receiving PDU3 (it has not received PDU5 to PDU7).
  • RX_DELIV is the count value of PDU3
  • RX_NEXT is the count value of PDU5. Since RX_DELIV ⁇ RX_NEXT, the PDCP entity Update RX_REORD to RX_NEXT and start the reordering timer t-Reordering. During the reordering timer t-Reordering, the receiving end PDCP entity received PDU5 to PDU7 again.
  • PDU3 has not been received when the reordering timer t-Reordering expires, it will give up receiving, upload PDU3, reset RX_REORD, deliver PDU4 to PDU7 in the cache to the upper layer, and update RX_DELIV to the count value of PDU8.
  • the receiving PDCP entity receives PDU3 before the reordering timer t-Reordering expires, it will deliver the received PDU3 and PDU4 to PDU7 to the upper layer in order, and update RX_DELIV to the count value of PDU8. Since the updated RX_DELIV >RX_REORD, terminate the reordering timer t-Reordering.
  • the PDCP entity will wait for the PDU corresponding to the vacant PDCP SN.
  • the setting of the reordering timer t-reordering needs to cover the time of several retransmissions. For example, if the round-trip time (RTT) of the hybrid automatic repeat request (HARQ) is 2.5ms, then the time of 10ms The delay can be retransmitted about 4 times. Assuming that the reordering timer t-Reordering is 10ms, the subsequent PDU received, such as PDU4 to PDU7 in Figure 1(a) may also cause an additional 10ms sequencing delay.
  • XR services have high requirements on delay performance, and most data transmission adopts unacknowledged mode (UM mode). At the same time, the reliability requirements of XR services are not low. In UM mode, improving reliability depends on increasing the number of HARQ retransmissions. Therefore, the timing duration of the reordering timer t-reordering may be set to 10ms or even 15ms.
  • a frame of image can be divided into multiple slices, and each slice serves as an information unit and can be encoded into a PDU set.
  • a frame image can be divided into 4 slices, then the frame image corresponds to 4 PDU sets.
  • These 4 PDU sets can be regarded as a data burst. In the downlink transmission, these 4 PDU sets arrive at the access network almost simultaneously. equipment. Since the data in a data burst may be large, each slice can be further divided into several transport blocks (TB) and sent separately.
  • TB transport blocks
  • the TB is delivered to the PDCP layer through the physical (PHY) layer, media access control (MAC) layer, and radio link control (RLC) layer, as shown in Figure 1
  • PHY physical
  • MAC media access control
  • RLC radio link control
  • the transmission of PDU2 in PDU set#1 fails, even if the PDUs in PDU set#2, PDU set#3, and PDU set#4 are all successfully received, PDU set#2, PDU set #3.
  • the PDU in PDU set #4 can only wait in the cache of the PDCP entity until the PDU2 that failed to be transmitted in PDU set #1 is retransmitted successfully, or until the reordering timer t-reordering expires. It can be seen that waiting for the missing PDUs in PDU set #1 may cause PDU set #2, PDU set #3, and PDU set #4 to exceed the preset PSDB and be discarded by the application layer.
  • the application layer's decoding process of the PDUs in PDU set#2, PDU set#3, and PDU set#4 does not rely on the decoding process of the PDU in PDU set#1. For example, if an image is divided into 4 slices, each slice corresponds to a PDU set, then the application layer can decode the 4 PDU sets independently.
  • the application layer can independently decode the PDU set
  • the PDCP entity encounters a PDCP SN vacancy
  • it still waits for the PDU corresponding to the vacant PDCP SN so that other PDU sets can be independently decoded by the application layer.
  • Decoding must wait for the PDU corresponding to the vacant PDCP SN to be retransmitted, which may cause other PDU sets to time out and be discarded by the application layer, or deteriorate the user experience at the application layer.
  • embodiments of the present application provide a data delivery method, which can be applied to the PDU set delivery process within the communication device, and helps to improve the delivery delay performance of the PDU set.
  • the data delivery method provided by the embodiment of this application can be applied to the network architecture as shown in Figure 2.
  • the network architecture can include the following units or devices:
  • Terminal equipment The terminal equipment involved in this application may include handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of user equipment (user equipment). , UE), mobile station (MS), terminal equipment (terminal equipment), etc.
  • UE user equipment
  • MS mobile station
  • terminal equipment terminal equipment
  • a UE is used as an example.
  • the terminal device in the embodiment of the present application can also be equipped with sensors such as gyroscope samplers that can monitor the user's posture and movements, a GPS sensor, and multimedia playback devices such as speakers and display screens.
  • the gyroscope is used to collect the user's attitude and action information; the sampler is used to collect the attitude and action information provided by the gyroscope, as well as the device timing information; the GPS sensor is used to provide millisecond-level absolute time.
  • Radio access network is used to implement wireless-related functions.
  • Wireless access network can also be called access network equipment or base station, which is used to connect terminal equipment to the wireless network.
  • the wireless access network may be a base station, an LTE system or an evolved base station (evolved NodeB, eNodeB) in an evolved LTE system (LTE-Advanced, LTE-A), or a next-generation base station in a 5G communication system. (next generation NodeB, gNB), transmission reception point (TRP), base band unit (BBU), WiFi access point (access point, AP), base station or WiFi system in future mobile communication systems access nodes, etc.
  • the wireless access network can also be a module or unit that completes some functions of the base station.
  • the radio access network may be a CU node, a DU node, or a radio access network including a CU node and a DU node.
  • UPF The main functions of UPF include: data packet routing and transmission, packet detection, business usage reporting, QoS processing, uplink packet detection, downlink data packet storage and other user plane related functions.
  • Access and mobility management function the main functions include: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management, etc. Access and mobility Related functions, etc.
  • Session Management function its main functions include: session management (such as session establishment, Modification and release, including tunnel maintenance between UPF and AN), UPF selection and control, SSC (Service and Session Continuity, service and session continuity) mode selection, roaming and other session-related functions, etc.
  • session management such as session establishment, Modification and release, including tunnel maintenance between UPF and AN
  • Modification and release including tunnel maintenance between UPF and AN
  • UPF selection and control UPF selection and control
  • SSC Service and Session Continuity, service and session continuity
  • PCF Policy Control Function
  • main functions include: unified policy formulation, provision of policy control, and acquisition of policy decision-related contracting information from UDR and other policy-related functions.
  • Data network provides data transmission services for terminals. It can be a public data network (PDN) network, such as the Internet, or a local access data network (local access data network). , LADN), such as campus DN, etc.
  • PDN public data network
  • LADN local access data network
  • network element can also be called “entity” or “device”, which is not limited by this application.
  • network elements can be co-located. When two network elements are co-located, the interaction between the two network elements provided by the embodiments of this application becomes the internal operation of the co-located network element or can be omitted.
  • FIG. 2 only provides an exemplary network architecture that can be applied to the embodiments of the present application. In actual application, it may include more or fewer network elements than in FIG. 2 .
  • FIG. 3 is a schematic flow chart of a data delivery method provided by an embodiment of the present application. As shown in the figure, the method may include the following steps:
  • Step 301 The PDCP entity of the communication device receives the first PDU and the second PDU.
  • the communication device used to execute the data delivery method shown in Figure 3 is the receiving end of the data, and may be the terminal device shown in Figure 2 or the wireless access device shown in Figure 2.
  • the UE sends uplink data
  • the PDCP entity of the gNB can perform the data delivery method as shown in Figure 3.
  • the PDCP entity of the UE can perform the data delivery method as shown in Figure 3.
  • the above-mentioned first PDU is a PDU that has been received by the PDCP entity and has been delivered to the upper layer; the second PDU is a PDU that has been received by the PDCP entity and has not yet been delivered to the upper layer.
  • the upper layer represents the upper layer of the PDCP entity, which may include the service data adaptation protocol (service data adaptation protocol, SDAP) layer or the radio resource control (radio resource control, RRC) layer.
  • the PDCP sequence number of the first PDU can be referred to as the first PDCP sequence number
  • the PDCP sequence number of the second PDU can be referred to as the second PDCP sequence number.
  • the sequence number of the second PDCP is after the sequence number of the first PDCP.
  • the sequence number of the second PDCP is greater than the sequence number of the first PDCP.
  • the PDCP sequence numbers since the number of PDCP sequence numbers is limited, the PDCP sequence numbers will be used cyclically, and the second PDCP sequence number may be smaller than the first PDCP sequence number.
  • the PDCP sequence number can be represented as 0 ⁇ 232-1, a total of 232 PDCP sequence numbers.
  • These 232 PDCP sequence numbers will be assigned to the PDU in ascending order; in After all PDCP sequence numbers are allocated to 232 PDUs, PDCP sequence number 0 is assigned to the 232+1 PDU.
  • the second PDCP sequence number may appear after the first PDCP sequence number, but the second PDCP sequence number is less than the first PDCP sequence number.
  • Step 302 When the PDCP entity receives the second PDU and does not receive the third PDU, start the reordering timer, wherein the PDCP sequence number of the third PDU is the third PDCP sequence number, and the third PDCP sequence number is greater than the first The PDCP sequence number is smaller than the second PDCP sequence number.
  • the first PDCP sequence number and the second PDCP sequence number are not consecutive.
  • the order in which a PDCP entity receives PDUs is consistent with the order of the PDCP sequence numbers of the PDUs, and the order in which the PDCP entity delivers PDUs to the upper layer is also consistent with the order of the PDCP sequence numbers of the PDUs.
  • the PDCP entity can act as a reordering timer.
  • Step 303 When the reordering timer is running, if the number of PDUs associated with the second PDU received by the PDCP entity is greater than or equal to the first preset value, the PDCP entity will reorder the PDUs associated with the second PDU received by the PDCP entity. Delivered to the upper layer, where the associated PDUs are PDUs with the same identification.
  • the above expression includes a sequence number, which is different from the traditional PDCP sequence number and is used to indicate The PDU set to which the PDU belongs.
  • the above-mentioned associated PDUs have the same PDU set sequence number and belong to the same PDU set.
  • the PDCP entity when the PDCP entity performs the above step 303, if the number of PDUs contained in the first PDU set received by the PDCP entity is greater than or equal to the first preset value, then the PDUs contained in the received first PDU set will be Delivered to the upper level.
  • the first PDU set is the PDU set to which the second PDU belongs.
  • the decoding end can decode according to the number of PDUs greater than or equal to the first preset value and obtain the required data. Therefore, when the PDCP entity receives a PDU belonging to the first PDU set that is greater than or equal to the first preset value, it can deliver the received PDU belonging to the first PDU set to the upper layer without caring that the reordering timer is currently running. It is still in the cut-off state, and it does not matter whether the PDU corresponding to the vacant PDCP sequence number (that is, the above-mentioned third PDCP sequence number) that triggers the reordering timer is received or not is received.
  • the vacant PDCP sequence number that is, the above-mentioned third PDCP sequence number
  • the above-mentioned first preset value may be the total number of PDUs included in the first PDU set (hereinafter referred to as the first total number for convenience of description), or the first preset value may also be a value smaller than the first total number.
  • the two situations are introduced below:
  • the first preset value is the first total quantity.
  • the PDCP entity needs to receive all the PDUs included in the first PDU set before it can deliver the PDUs included in the first PDU set to the upper layer. .
  • both PDU1 and PDU2 have been delivered to the upper layer.
  • the PDCP entity In the case of delivery in order according to the PDCP sequence number, the PDCP entity should currently deliver PDU3, but the PDCP entity has not yet delivered PDU3 (the third PDU mentioned above) is not received, and PDU4 to PDU8 are received without receiving PDU3 (PDU4 can be used as the second PDU mentioned above according to the PDCP sequence number), then the PDCP entity can start the reordering timing. device.
  • the PDCP entity can determine whether it has received all PDUs included in PDU set #2 (i.e., the first PDU set mentioned above) to which PDU4 belongs. Since the PDCP entity has received PDU set #2 including all PDUs, that is, PDU4 to PDU6, then the PDCP entity delivers all PDUs included in PDU set#2 to the upper layer.
  • PDU set #2 i.e., the first PDU set mentioned above
  • the PDCP entity can further determine Whether all PDUs included in PDU set#3 to which PDU7 belongs are received. Since the PDCP entity has not yet received PDU9 belonging to PDU set#3, the PDCP entity has not yet received all the PDUs contained in PDU set#3, that is, the number of PDUs belonging to PDU set#3 received by the PDCP entity has not reached the corresponding number of PDU set#3.
  • the PDCP entity will not deliver the PDU included in PDU set #3 to the upper layer for the time being. If the PDCP entity receives PDU9 before the reordering timer expires, then the PDCP entity can deliver all PDUs included in PDU set #3, that is, PDU7 to PDU9, to the upper layer.
  • the PDCP entity delivers the PDU contained in the first received PDU set (PDU set #2 in Figure 4(a)) to the upper layer, or even delivers a larger number of PDUs contained in the PDU set to the upper layer, if it is repeated
  • the sorting calculator has not yet ended, so the PDCP entity does not need to modify the to-be-delivered flag RX_DELIV because the PDCP entity has not given up waiting for the third PDU (PDU3 in Figure 4(a)).
  • Case 2 The second PDU and the third PDU belong to the same PDU set.
  • PDU1 and PDU2 have been delivered to the upper layer.
  • the PDCP entity should currently deliver PDU3, but the PDCP entity has not yet After receiving PDU3 (that is, the third PDU above), and receiving PDU4 to PDU8 without receiving PDU3 (PDU4 can be used as the above-mentioned second PDU according to the sequence number first), then the PDCP entity can start the reordering timer.
  • the PDCP entity can determine whether it has received all the PDUs included in PDU set #1 (that is, the first PDU set mentioned above) to which PDU4 belongs. Since the PDCP entity has not yet received PDU3 included in PDU set #1, it The PDCP entity has not received all PDUs included in PDU set #1, that is, PDU1 to PDU4, so the PDCP entity cannot deliver the PDU (ie, PDU4) that belongs to PDU set #1 and has not yet been delivered to the upper layer.
  • the PDCP entity can further determine whether it has received all PDUs included in PDU set #2 to which PDU5 belongs. Since the PDCP entity has received all PDUs included in PDU set #2, namely PDU5 to PDU8, the PDCP entity can deliver all PDUs included in the received PDU set #2 to the upper layer.
  • the PDCP entity delivers the PDUs contained in other PDU sets to the upper layer, if the reordering calculator has not yet ended, the PDCP entity does not need to modify the to-be-delivered flag RX_DELIV, because the PDCP entity does not give up waiting for the third PDU.
  • the PDCP entity determines whether it has received all the PDUs included in the first PDU set can also be implemented in multiple ways.
  • the first preset value is the first total number
  • the above-mentioned PDUs with the same identifier may include the header shown in Figure 5(a).
  • the PDCP entity may determine whether to receive the header contained in the first PDU set based on the information in the header shown in Figure 5(a). All PDUs.
  • the header shown in FIG. 5(a) includes a first field, a second field, and a third field.
  • the first field is used to indicate the identifier of the PDU set to which the PDU belongs.
  • the PDU set can be identified by the serial number of the PDU set, that is, the "PDU set SN" shown in Figure 5(a).
  • the first field occupies 8 bits. Of course, in actual applications, more or less bits can be set for the first field according to requirements.
  • the second field is used to indicate the position information of the PDU in the PDU set to which it belongs. Specifically, it can be used to indicate whether the PDU is the first PDU, the last PDU or the middle PDU in the PDU set to which it belongs. As shown in the two bits "B" and "E" in Figure 5(a), for example, when the value of these two bits is 00, it can indicate that the PDU is the first PDU in the PDU set to which it belongs; When the value of these two bits is 01, it can indicate that the PDU is the last PDU in the PDU set to which it belongs; when the value of these two bits is 10, it can indicate that the PDU is the middle PDU of the PDU set to which it belongs.
  • the third field is used to represent the PDCP sequence number of the PDU, which can be "PDCP SN" as shown in Figure 5(a).
  • the third field occupies 12 bits.
  • the third field can continue to use the existing "PDCP SN" field, or it can use an improved field used to represent the PDCP sequence number.
  • the first field and the second field are new concepts introduced in Mode 1 in the embodiment of this application.
  • the second field can be implemented using reserved bits in the header.
  • the PDCP entity may determine whether the fourth PDCP sequence number corresponding to the header of the received one or more PDUs is received. PDU, whether the PDU corresponding to the fifth PDCP sequence number is received, and whether all PDUs with PDCP sequence numbers between the fourth PDCP sequence number and the fifth PDCP sequence number are received.
  • the fourth PDCP sequence number is the PDCP sequence number of the first PDU in the first PDU set
  • the fifth PDCP sequence number is the PDCP sequence number of the last PDU in the first PDU set.
  • the PDCP entity determines whether the first PDU in the first PDU set is received, determines whether the last PDU in the first PDU set is received, determines whether the PDCP sequence number of the first PDU and the PDCP of the last PDU are received. All PDUs corresponding to PDCP sequence numbers between sequence numbers. If all are received, the PDCP entity determines that the number of PDUs contained in the received first PDU set reaches the first total number, and can deliver the PDUs contained in the received first PDU set to the upper layer.
  • the PDCP entity determines that PDU4 belongs to PDU set #2 based on the first field, second field and third field in the received header of PDU4, and PDU4 is the first field in PDU set #2.
  • PDU the PDCP sequence number of PDU4 is 4.
  • PDCP can also determine that the last PDU in PDU set #2, that is, PDU6, has been received based on the received headers of PDU5 and PDU6, and the PDCP sequence number between the PDCP sequence number of PDU4 and the PDCP sequence number of PDU6 corresponds to All PDUs (that is, the PDU with PDCP sequence number 5) have also been received. Therefore, the PDCP entity can determine that the number of PDUs contained in the received PDU set #2 has reached the total number of PDUs contained in the PDU set #2, and can deliver the PDUs contained in the received PDU set #2 to the upper layer.
  • the header may also include a type identifier for indicating whether the header is a header of the first type, that is, a header that includes the above-mentioned first field, second field, and third field.
  • the first type of header may also refer to a header newly added with the above-mentioned first field and second field.
  • the PDCP entity can determine, based on the type identifier, whether to identify the header of the received PDU according to the format of the first type header. For example, the "F" bit shown in Figure 5(b) is the above-mentioned type identifier, and whether the header is a header of the first type can be indicated by a bit value of 0 or 1.
  • the PDCP entity identifies the first target field in the first type header, that is, identifies the first field and the second field.
  • type identification can also be implemented using reserved bits in the header.
  • the RRC layer may indicate the first PDCP configuration information.
  • the first PDCP configuration information is used to instruct the PDCP entity to identify the second target field in the header of the PDU.
  • the second target field is The field where the above type identification is located. For example, under normal circumstances, the PDCP entity will not identify the information on the reserved bits. If the field where the type identifier is located and the second field are implemented using the reserved bits in the traditional header, and the first field is a newly added field, then the PDCP entity will not identify the information in the reserved bits, and will also regard the newly added first field as other fields in the traditional header, thus failing to correctly identify the first type of header provided by the embodiment of this application. . Through the first PDCP configuration information indicated by the RRC, the PDCP entity can determine whether to identify the header of the received PDU according to the format of the first type header.
  • the above first PDCP configuration information in addition to instructing the PDCP entity to identify the second target field in the header of the PDU, can also be used to instruct the PDCP entity when the reordering timer is running, if the received PDU is related to the first PDU.
  • the number of associated PDUs is greater than or Equal to the first preset value, the received PDU associated with the first PDU is delivered to the upper layer (SDAP layer). That is to say, the PDCP entity determines to execute the data delivery method provided by the embodiment of the present application based on the first PDCP configuration information, and identifies the second target field in the header of the received PDU.
  • the RRC layer can also separately indicate the third PDCP configuration information.
  • the third configuration PDCP configuration information is used to instruct the PDCP entity when the reordering timer is running. If the PDU associated with the first PDU is received If the quantity is greater than or equal to the first preset value, the received PDU associated with the first PDU is delivered to the upper layer (SDAP layer). That is to say, the PDCP entity determines to execute the data delivery method provided by the embodiment of the present application based on the third PDCP configuration information.
  • the PDCP entity can also be instructed to identify the first field and the second field in the header of the PDU through other methods.
  • the PDU received by the PDCP entity in the above step 301 is carried in the first wireless data bearer (DRB).
  • DRB first wireless data bearer
  • the PDCP entity determines that the header of the PDU is the above-mentioned first type header. .
  • the upper layer of the PDCP entity includes the RRC layer, and the RRC layer can indicate the second PDCP configuration information.
  • the second PDCP configuration information is used to instruct the PDCP entity to map the first type PDU to the first DRB.
  • the first type PDU is a PDU to be sent and having the above-mentioned first type header.
  • the above-mentioned PDUs with the same identifier may include the header shown in Figure 5(c).
  • the PDCP entity may determine whether to receive the header contained in the first PDU set based on the information in the header shown in Figure 5(c). All PDUs.
  • the header shown in FIG. 5(c) also includes a fourth field, a fifth field, and a sixth field.
  • the fourth field is similar to the first field in method 1 and is used to indicate the identifier of the PDU set to which the PDU belongs.
  • the PDU set can be identified by the serial number of the PDU set, such as "PDU set SN" as shown in Figure 5(c).
  • PDU set SN occupies 8 bits.
  • more or fewer bits can be set for "PDU set SN" according to requirements. .
  • the fifth field is used to indicate the total number of PDUs contained in the PDU set to which the PDU belongs, as shown in Figure 5(c) as the "number of PDUs within the PDU set".
  • "number of PDUs within the PDU set" occupies 8 bits.
  • the header of each PDU included in the PDU set may contain the fifth field mentioned above, or the fifth field may only be carried in the header of some PDUs included in the PDU set, or other controls may be used.
  • Information is indicated, for example, the fifth field mentioned above can be carried in the control PDU (PDCP control PDU).
  • the sixth field is similar to the third field in method 1 and is used to represent the PDCP sequence number of the PDU, such as "PDCP SN" as shown in Figure 5(c).
  • the sixth field can continue to use the existing "PDCP SN" field, or it can use an improved field used to represent the PDCP sequence number.
  • the PDCP entity may determine that the received PDU belongs to the first PDU set based on the headers of one or more PDUs received. The number of PDUs reaches the first total number. If the PDCP entity determines that the number of PDUs included in the received first PDU set reaches the first total number, it may deliver the PDUs included in the received first PDU set to the upper layer.
  • the PDCP entity determines that PDU4 belongs to PDU set #2 based on the fourth and fifth fields in the received header of PDU4, and the total number of PDUs contained in PDU set #2 is 3.
  • the PDCP entity can also determine that PDU5 and PDU6 also belong to PDU set #2 based on the received headers of PDU5 and PDU6. Then the PDCP entity can determine that the number of received PDUs belonging to PDU set #2 is 3, reaching the total number of PDUs contained in PDU set #2, and can deliver the PDUs contained in the received PDU set #2 to the upper layer.
  • the header may also include a type identifier, used to indicate whether the header is a second type of header, that is, a header that includes the foregoing fourth field and fifth field.
  • the PDCP entity can determine, based on the type identifier, whether to identify the header of the received PDU according to the format of the second type header.
  • the "F" bit shown in Figure 5(d) is the above-mentioned type identifier, and whether the header is a second type header can be indicated by a bit value of 0 or 1.
  • the PDCP entity identifies the third target field in the second type header, that is, identifies the above-mentioned fourth field and fifth field.
  • type identification can be implemented using reserved bits in the header.
  • the second type of header may also include a seventh field.
  • the seventh field is similar to the second field in Mode 1 and is used to indicate the location information of the PDU in the PDU set to which it belongs, so that the PDCP entity can more clearly understand the received PDU.
  • the position in the corresponding PDU set Specifically, it can be used to indicate whether the PDU is the first PDU, the last PDU, or the middle PDU in the PDU set to which it belongs. PDU, two bits "B" and "E” as shown in Figure 5(e). Then, when the PDCP entity determines that the header of the received PDU is the second type header according to the type identifier, it can also identify the seventh field in the second type header.
  • the RRC layer may indicate fourth PDCP configuration information.
  • the fourth PDCP configuration information is used to instruct the PDCP entity to identify the fourth target field in the header of the PDU.
  • the fourth target field is The field where the above type identification is located. For example, under normal circumstances, the PDCP entity will not identify the information on the reserved bits. If the field where the type identifier is located is implemented using the reserved bits in the traditional header, the fourth field and the fifth field are newly added. field, then the PDCP entity will not identify the information in the reserved bits, and may regard the newly added fourth and fifth fields as other fields in the traditional header, thereby failing to correctly identify the third field provided by the embodiment of the present application. Type 2 header. Through the second PDCP configuration information indicated by the RRC, the PDCP entity can determine whether to identify the header of the received PDU according to the format of the second type header.
  • the PDCP entity may also be instructed to identify the fourth field and the fifth field in the header of the PDU in other ways.
  • the PDU received by the PDCP entity in the above step 301 is carried in the second DRB.
  • the PDCP entity determines that the header of the PDU is the above-mentioned second type header.
  • the upper layer of the PDCP entity includes an RRC layer, and the RRC layer can indicate the fifth PDCP configuration information.
  • the fifth PDCP configuration information is used to instruct the PDCP entity to map the second type PDU to the second DRB.
  • the second type PDU is a PDU to be sent and has the above-mentioned second type header.
  • the first preset value is less than the first total quantity.
  • the original data will generate 4 PDUs after being encoded with non-redundant encoding, and 5 PDUs will be generated after being encoded with redundant encoding, and the receiving end can generate Any 4 PDUs among the 5 PDUs get the original data.
  • the first preset value may be less than the first total number; the value of the first preset value needs to ensure that the receiving end can receive PDUs based on the number of the first preset value. Successfully decoded to get the required data.
  • the PDCP entity may deliver the received PDUs associated with the second PDU to The upper layer does not have to wait until all the PDUs contained in the first PDU set are received before it can be delivered to the upper layer.
  • the PDCP entity can obtain the value of the first default value in the following two ways:
  • the PDCP entity can determine the first preset value based on the total number of PDUs included in the first PDU set (i.e., the first total number) and the preset ratio.
  • the first total quantity may be carried in the header of the second PDU.
  • the header of the second PDU may be as shown in Figure 5(c).
  • the PDCP entity can then retrieve the first total number from the header of the second PDU.
  • the preset ratio can be sent to the communication device through RRC layer signaling or application layer signaling, and the PDCP entity in the communication device can determine the preset ratio according to instructions from the RRC layer.
  • the application function (AF) network element can send the preset ratio to the access network device through control plane signaling, and the access network device can send the preset ratio to the terminal device through RRC signaling; then in the downlink
  • the PDCP entity of the terminal device can determine the first preset value based on the first total quantity and the preset ratio, and determine the received first PDU set
  • the included PDU is greater than or equal to the first preset value
  • the PDU included in the received first PDU set is sent to the upper layer of the terminal device; during the uplink transmission process, when the access network device receives the PDU sent by the terminal device,
  • the PDCP entity of the network access device can also determine the first preset value based on the first total quantity and the preset ratio, and
  • the preset ratio can also be carried in the header of the second PDU, and then the PDCP entity at the receiving end can obtain the first total quantity and the preset ratio from the header of the received second PDU, thereby determining the first preset ratio. Set value.
  • the preset ratio can also be carried in the PDCP control PDU.
  • the preset values corresponding to different PDU sets may be the same or different.
  • the preset proportions corresponding to different PDU sets are the same, but because the total number of PDUs contained in different PDU sets is different, the preset values corresponding to different PDU sets are also different, then The PDCP entity needs to determine its corresponding default value for each PDU set.
  • the preset proportions corresponding to different PDU sets may also be different.
  • the header of the second PDU contains the first preset value, and the PDCP entity can directly read the first preset value from the header of the second PDU.
  • the reserved bits in the traditional header can be used to indicate the default value corresponding to the PDU set to which the PDU belongs; a new field can also be added to indicate the default value corresponding to the PDU set to which the PDU belongs.
  • a field used to represent the default value corresponding to the PDU set to which the PDU belongs can be further added.
  • the header only needs to include a field used to represent the identifier of the PDU set to which the PDU belongs, and a field used to represent the default value corresponding to the PDU set to which the PDU belongs.
  • the above fifth field does not need to be included, that is, it does not include the field used to represent the PDU.
  • Field containing the total number of PDUs set contains.
  • the PDCP entity can determine the PDU set to which each received PDU belongs and the preset value corresponding to each PDU set based on the headers of multiple received PDUs; the PDCP entity determines the number of received PDUs belonging to the first PDU set. When the first preset value corresponding to the first PDU set is reached, the PDU included in the received first PDU set can be delivered to the upper layer.
  • the PDCP entity can determine whether the number of received PDUs belonging to the first PDU set reaches the first preset value corresponding to the first PDU set, and when the first preset value is reached, When the value is reached, the PDU contained in the first PDU set received is delivered to the upper layer. At this time, there may be a situation where the second PDU and the third PDU belong to different PDU sets, or there may be a situation where the second PDU and the third PDU belong to the same PDU set.
  • Case 3 The second PDU and the third PDU belong to different PDU sets.
  • PDU1 to PDU4 (PDU4 can be used as the first PDU mentioned above) have all been delivered to the upper layer.
  • the PDCP entity should currently deliver PDU5, but the PDCP entity has not yet PDU5 (ie, the above-mentioned third PDU) is received, and PDU6 to PDU10 are received without PDU5 (PDU6 can be used as the first DPU).
  • the PDCP entity can start the reordering timer first. Then the PDCP entity can determine the PDU set to which the unreceived PDU5 belongs. Specifically, when the PDU header contains the location information of the PDU in the PDU set to which it belongs, the PDCP entity can determine whether PDU5 belongs to PDU set #1 based on the location information of PDU4 in PDU set #1. If PDU4 is in PDU set #1 The last PDU of PDU set #2, then PDU5 belongs to PDU set #2.
  • PDU4 is the middle PDU of PDU set #1
  • PDU5 belongs to PDU set #1; when the PDU header contains the total number of PDUs included in the PDU set to which the PDU belongs, PDCP
  • the entity can determine whether the total number of received PDUs included in PDU set#1 reaches the total number of PDUs included in PDU set#1. If it reaches the total number of PDUs included in PDU set#1, then PDU5 belongs to PDU set#2. Otherwise, PDU5 is considered to belong to PDU set#1.
  • the PDCP entity can determine that the unreceived PDU5 belongs to PDU set #1, and the received PDU6 belongs to PDU set #2.
  • the PDCP entity determines that the received PDUs belonging to PDU set #2 include PDU6 to PDU10, reaching the preset value 4, then the PDCP entity delivers the PDUs belonging to PDU set #2 (i.e., PDU6 to PDU10) to the upper layer.
  • the PDCP entity can also determine whether the number of delivered PDUs belonging to PDU set #1 reaches the preset value corresponding to PDU set #1.
  • the PDCP entity has not delivered PDU6 to PDU10 to the upper layer at this time, update the to-be-delivered identifier to the identifier of PDU6 (such as the count value of PDU6). If the PDCP entity has delivered PDU6 to PDU10 to the upper layer at this time, then the to-be-delivered identifier can be updated. The delivery identifier is updated to the identifier of PDU11 (such as the count value of PDU11).
  • the PDCP entity may not start the reordering timer immediately, but first determines that the last delivered PDU4 belongs to PDU set#1, and the PDCP entity delivers to the upper layer belongs to PDU set#. Whether the number of PDUs of 1 reaches the preset value corresponding to PDU set #1. If it does, the reordering timer will not be started and the to-be-delivered identifier RX_DELIV will be updated; if it has not been reached, the reordering timer will be started and while waiting to receive PDU5 , and determine whether the number of received PDUs belonging to PDU set#2 reaches the preset value corresponding to PDU set#2.
  • Case 4 The second PDU and the third PDU belong to the same PDU set.
  • PDU1 to PDU3 (PDU3 can be used as the first PDU mentioned above) have all been delivered to the upper layer.
  • the PDCP entity should currently deliver PDU4, but the PDCP entity has not yet PDU4 is received (i.e. the above third PDU), and received PDU5 to PDU10 without receiving PDU4 (PDU5 can be used as the above-mentioned second DPU).
  • the PDCP entity can start the reordering timer first. Then the PDCP entity can determine the PDU set to which the unreceived PDU4 belongs. Specifically, when the PDU header contains the location information of the PDU in the PDU set to which it belongs, the PDCP entity can determine whether PDU4 belongs to PDU set #1 based on the location information of PDU3 in PDU set #1, because PDU3 is a member of PDU set #1. The last PDU, then PDU4 belongs to PDU set#2.
  • PDU4 belongs to PDU set#1; when the PDU header contains the total number of PDUs included in the PDU set to which the PDU belongs, the PDCP entity It can be determined whether the total number of received PDUs included in PDU set#1 reaches the total number of PDUs included in PDU set#1. If so, PDU4 belongs to PDU set#2. Otherwise, PDU4 is considered to belong to PDU set#1.
  • the PDCP entity can determine that the unreceived PDU4 belongs to PDU set #1, and the received PDU5 also belongs to PDU set #1.
  • the PDCP entity determines that the received PDUs belonging to PDU set #1 include PDU1 to PDU3, and PDU5, reaching the preset value 4, then the PDCP entity delivers the undelivered PDU (i.e. PDU5) belonging to PDU set #1 to the upper layer; Since PDU5 is delivered to the upper layer, the delivered PDU belonging to PDU set #1 reaches the preset value 4, and the PDCP entity can no longer wait for PDU4 and terminate the reordering timer.
  • the PDCP entity can also update the to-be-delivered identifier RX_DELIV and update the to-be-delivered identifier to the identifier of PDU6 (such as the count value of PDU6).
  • the updated PDU to be delivered identification is used to indicate that it belongs to a different PDU set than the delivered PDU5.
  • the PDCP entity may not start the reordering timer immediately, but first determines that the unreceived PDU4 belongs to PDU set#1, and the one received by the PDCP entity belongs to PDU set#.
  • the reordering timer will not be started, and the received PDUs belonging to PDU set#1 will be delivered to the upper layer, that is, the undelivered PDU5 Deliver it to the upper layer, and update the to-be-delivered flag RX_DELIV; if it has not been reached, start the reordering timer, wait for the reception of PDU4, and determine whether the number of received PDUs belonging to PDU set#2 reaches the preset value corresponding to PDU set#2 Set value.
  • the received and unreceived PDUs are not associated.
  • the PDU cannot be delivered in time, which will cause additional delivery delays for PDUs that are not associated with the unreceived PDU.
  • the data delivery method provided by the embodiment of the present application, even if the PDCP entity at the receiving end starts the reordering timer, it will not only wait to receive the PDU that has been received but has not been received, but will judge the difference between the received PDU and the first PDU while waiting.
  • the received PDU associated with the second PDU will be delivered to the upper layer, regardless of whether the reordering timer is currently running or expired. status, and it does not matter whether the PDU corresponding to the vacant PDCP sequence number (that is, the above-mentioned third PDCP sequence number) that triggers the reordering timer is received or not is received. Therefore, after adopting the above method, the delivery delay of PDUs not associated with the third PDU will not increase due to the delay of the third PDU, thereby improving the delivery efficiency of the receiving end and reducing the loss caused by the sorting waiting delay. package, thereby improving user experience.
  • the embodiment of the present application also provides a data delivery method, which is also applicable to the PDU set delivery process within the communication device, and improves the delivery delay performance of the PDU set.
  • This method can be applied to the data sending end.
  • a first communication device and a second communication device have established L DRBs, where L is an integer greater than 1.
  • L is an integer greater than 1.
  • the first communication device can perform the steps shown in Figure 7:
  • Step 701 The SDAP entity of the first communication device obtains N PDUs.
  • the N PDUs obtained by the SDAP entity of the first communication device are data to be sent by the first communication device, where N is an integer greater than 1.
  • the N PDUs may be generated by the application layer of the first communication device, and the SDAP entity of the first communication device may obtain the N PDUs to be sent from the application layer of the first communication device.
  • Step 702 When the N PDUs have not yet been delivered to the PDCP layer and the N PDUs belong to M PDU sets, the SDAP entity of the first communication device maps the M PDU sets to L DRBs.
  • M is an integer less than or equal to N and greater than 1.
  • the SDAP entity of the first communication device maps M PDU sets to M DRBs included in L DRBs; or, when M is greater than L, the number of PDU sets mapped by each DRB in L DRBs does not exceed the integer obtained by rounding up M/L, and is not less than the integer obtained by rounding up M/L.
  • the integer obtained by rounding down is to map the PDU set to L DRBs as evenly as possible.
  • Step 703 The first communication device sends the above-mentioned M PDU sets to the second communication device through L DRBs.
  • the SDAP entity of the first communication device when performing DRB mapping, performs mapping with PDU set as the granularity, that is, PDUs belonging to the same PDU set are mapped to the same DRB. Since each DRB corresponds to a PDCP entity, the SDAP entity will deliver the PDU to the corresponding PDCP entity using PDU set as the granularity.
  • the PDCP sequence number configured for PDU by each PDCP entity is performed independently.
  • PDU set#1 contains 10 PDUs, and PDU set#1 is mapped to DRB1, then PDCP entity 1 corresponding to DRB1 will be PDU set#1
  • the 10 PDUs contained are assigned PDCP sequence numbers, such as 1 to 10;
  • PDU set#2 contains 8 PDUs, and PDU set#2 is mapped to DRB2, then the 8 contained in PDU set#2 will be assigned by PDCP entity 2 corresponding to DRB2
  • Each PDU is assigned a PDCP sequence number, such as 1 to 8.
  • PDUs included in PDU set #1 will be delivered to the PDCP entity 1' corresponding to DRB1, and 8 PDUs included in PDU set #2 will be delivered.
  • the PDUs transmitted on different PDCP entities belong to different PDU sets, or in other words, PDUs belonging to the same PDU set will not be transmitted on different PDCP entities.
  • PDCP entity 1' starts the reordering timer, but it will not affect PDCP entity 2' delivery of the PDU contained in PDU set #2; similarly Yes, if a PDU in PDU set #2 is not successfully received, PDCP entity 2' starts the reordering timer, and it will not affect PDCP entity 1''s delivery of the PDU included in PDU set #1. Therefore, using the above method can reduce the occurrence of an increase in the delivery delay of other PDU sets due to the delay of a certain PDU, thereby improving the delivery efficiency of the PDU at the receiving end, reducing packet loss due to the sorting waiting delay, and thus Improve user experience.
  • embodiments of the present application also provide a communication device.
  • This device can be the PDCP entity of the communication device in the method shown in Figure 3 and any of its implementations, and is used to implement the communication device in the above method embodiment.
  • the device may include modules/units that execute any of the possible implementation methods in the above method embodiments; these modules/units may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the communication device may include a receiving module 801, a starting module 802 and a delivery module 803 as shown in Figure 8 .
  • the receiving module 801 is configured to receive the PDU and the second PDU.
  • the first PDU is the PDU that has been received by the device and delivered to the upper layer.
  • the upper layer is the upper layer of the device.
  • the second PDU is the PDU that has been delivered to the upper layer.
  • the device receives a PDU that has not yet been delivered to the upper layer, the PDCP sequence number of the first PDU is the first PDCP sequence number, and the PDCP sequence number of the second PDU is the second PDCP sequence number; start module 802, with When the receiving module receives the second PDU and does not receive the third PDU, the reordering timer is started, wherein the PDCP sequence number of the third PDU is the third PDCP sequence number, and the third PDU is The PDCP sequence number is greater than the first PDCP sequence number and less than the second PDCP sequence number; delivery module 803 is configured to, when the reordering timer is running, if the received PDU is associated with the second PDU If the number of PDUs is greater than or equal to the first preset value, the received PDU associated with the second PDU is delivered to the upper layer, and the associated PDU is a PDU with the same identification.
  • each of the above modules can also be used to support other processes performed by the PDCP entity of the communication device in the method described in Figure 3 and any of its implementations.
  • the beneficial effects can be referred to the previous description and will not be repeated here.
  • embodiments of the present application also provide a communication device.
  • This device may be the first communication device in the method shown in Figure 7 and any of its implementations, and is used to implement the first communication in the above method embodiment.
  • the device may include modules/units that execute any of the possible implementation methods in the above method embodiments; these modules/units may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the communication device may include an acquisition module 901, used to acquire N protocol data units PDU, where N is an integer greater than 1; a mapping module 902, used when the N PDUs have not yet been sent to When the PDCP layer is delivered and the N PDUs belong to M PDU sets, the M PDU sets are mapped to the L DRBs, where M is less than or equal to N and greater than 1; the sending module 903 is used to pass all The L DRBs are used to send the M PDU sets to the second communication device.
  • N an integer greater than 1
  • a mapping module 902 used when the N PDUs have not yet been sent to When the PDCP layer is delivered and the N PDUs belong to M PDU sets, the M PDU sets are mapped to the L DRBs, where M is less than or equal to N and greater than 1; the sending module 903 is used to pass all The L DRBs are used to send the M PDU sets to the second communication device.
  • each of the above modules can also be used to support other processes performed by the first communication device in the method described in Figure 7 and any implementation thereof.
  • the beneficial effects can be referred to the previous description and will not be repeated here.
  • An embodiment of the present application also provides a communication device.
  • the communication device includes a processor 1001 as shown in Figure 10, and a memory 1002 connected to the processor 1001. Further, the communication device may also include a communication interface 1003 and a communication bus 1004.
  • the processor 1001 may be a general processor, a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or one or more integrated circuits used to control the execution of the program of this application, etc.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc.
  • the memory 1002 is used to store program instructions and/or data, so that the processor 1001 calls the instructions and/or data stored in the memory 1002 to implement the above functions of the processor 1001.
  • Memory 1002 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory (RAM)) or other type that can store information and instructions.
  • a dynamic storage device that can also be an electrically erasable programmable read-only memory (EEPROM) or can be used to carry or store desired program code in the form of instructions or data structures and can be stored by a computer. any other medium, but not limited to this.
  • the memory 1002 may exist independently, such as an off-chip memory, and is connected to the processor 1001 through the communication bus 1004. Memory 1002 may also be integrated with processor 1001.
  • Storage 1002 may include internal memory and external memory (such as hard disk, etc.).
  • Communication interface 1003 is used to communicate with other devices, such as PCI bus interface, network card, wireless access network (radio access network, RAN), wireless local area networks (WLAN), etc.
  • PCI bus interface for communicating with other devices, such as PCI bus interface, network card, wireless access network (radio access network, RAN), wireless local area networks (WLAN), etc.
  • WLAN wireless local area networks
  • Communication bus 1004 may include a path for communicating information between the components described above.
  • the device may be a communication device in the method shown in FIG. 3 and any implementation thereof, or may be a communication device in the method shown in FIG. 7 and any implementation thereof.
  • the processor 1001 can call instructions in the memory 1002 to perform the following steps through the communication interface 1003:
  • a first PDU and a second PDU are received.
  • the first PDU is a PDU that has been received by the PDCP entity in the communication device and delivered to an upper layer.
  • the upper layer is an upper layer of the PDCP entity.
  • the second PDU is received by the PDCP entity in the communication device and delivered to an upper layer.
  • the PDU is a PDU received by the PDCP entity and not yet delivered to the upper layer, the PDCP sequence number of the first PDU is the first PDCP sequence number, and the PDCP sequence number of the second PDU is the second PDCP sequence number; when When the second PDU is received and the third PDU is not received, a reordering timer is started, wherein the PDCP sequence number of the third PDU is a third PDCP sequence number, and the third PDCP sequence number is greater than the The first PDCP sequence number is less than the second PDCP sequence number; when the reordering timer is running, if the number of PDUs associated with the second PDU received by the PDCP entity is greater than or equal to the At a preset value, the PDCP entity delivers the received PDU associated with the second PDU to the upper layer, and the associated PDU is a PDU with the same identity.
  • each of the above modules can also be used to support other processes performed by the communication device in the method described in Figure 3 and any implementation thereof.
  • the beneficial effects can be referred to the previous description and will not be repeated here.
  • the processor 1001 can call instructions in the memory 1002 to perform the following steps through the communication interface 1003:
  • N is an integer greater than 1; when the N PDUs have not yet been delivered to the PDCP layer, and the N PDUs belong to M PDU sets, map the M PDU sets to all The L DRBs, where M is less than or equal to N and greater than 1; through the L DRBs, the M PDU sets are sent to the second communication device.
  • each of the above modules can also be used to support other processes performed by the first communication device in the method described in Figure 7 and any implementation thereof.
  • the beneficial effects can be referred to the previous description and will not be repeated here.
  • embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores computer-readable instructions. When the computer-readable instructions are run on a computer, such that: The method described in any of the aforementioned possible implementations is executed.
  • Embodiments of the present application provide a computer program product containing instructions, which when run on a computer causes the above method embodiments to be executed.
  • the method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory In memory, register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage media may be located in an ASIC. Additionally, the ASIC can be located in the base station or terminal. Of course, the processor and the storage medium may also exist as discrete components in the base station or terminal.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user equipment, or other programmable device.
  • the computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
  • the computer program or instructions may be transmitted from a website, computer, A server or data center transmits via wired or wireless means to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media.
  • the available media may be magnetic media, such as floppy disks, hard disks, and tapes; optical media, such as digital video optical disks; or semiconductor media, such as solid-state hard drives.
  • the computer-readable storage medium may be volatile or nonvolatile storage media, or may include both volatile and nonvolatile types of storage media.

Landscapes

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

Abstract

L'invention concerne un procédé de distribution de données et un dispositif de communication. Le procédé comprend les étapes suivantes : une entité PDCP d'un dispositif de communication reçoit une première PDU et une deuxième PDU, la première PDU étant une PDU qui a été reçue et fournie à une couche supérieure de l'entité PDCP, et la deuxième PDU étant une PDU qui a été reçue et n'a pas encore été fournie à la couche supérieure ; lorsqu'une troisième PDU n'a pas été reçue, démarrer un temporisateur de réordonnancement, le numéro de série PDCP de la troisième PDU étant supérieur au numéro de série PDCP de la première PDU et inférieur au numéro de série PDCP de la deuxième PDU ; et lorsque le temporisateur de réordonnancement s'exécute, si le nombre de PDU reçues par l'entité PDCP et associées à la seconde PDU est supérieur ou égal à une première valeur prédéfinie, fournir à la couche supérieure les PDU reçues et associées à la seconde PDU, les PDU associées étant des PDU ayant le même identifiant. Ce procédé permet d'éviter les retards de livraison prolongés d'autres ensembles PDU provoqués par le retard d'une certaine PDU, et de réduire la perte de paquets provoquée par un retard de livraison commandée.
PCT/CN2023/108176 2022-07-26 2023-07-19 Procédé de distribution de données et dispositif de communication WO2024022198A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210895203 2022-07-26
CN202210895203.6 2022-07-26
CN202210977604.6A CN117499991A (zh) 2022-07-26 2022-08-15 一种数据交付方法及通信设备
CN202210977604.6 2022-08-15

Publications (1)

Publication Number Publication Date
WO2024022198A1 true WO2024022198A1 (fr) 2024-02-01

Family

ID=89669609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/108176 WO2024022198A1 (fr) 2022-07-26 2023-07-19 Procédé de distribution de données et dispositif de communication

Country Status (2)

Country Link
CN (1) CN117499991A (fr)
WO (1) WO2024022198A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170085492A1 (en) * 2014-03-19 2017-03-23 Sharp Kabushiki Kaisha Packet data convergence protocol (pdcp) entity and method performed by the same
CN110679105A (zh) * 2017-05-24 2020-01-10 Oppo广东移动通信有限公司 无线链路控制传输方法及相关产品
CN114514776A (zh) * 2019-08-07 2022-05-17 日本电气株式会社 基于同时连接的切换

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170085492A1 (en) * 2014-03-19 2017-03-23 Sharp Kabushiki Kaisha Packet data convergence protocol (pdcp) entity and method performed by the same
CN110679105A (zh) * 2017-05-24 2020-01-10 Oppo广东移动通信有限公司 无线链路控制传输方法及相关产品
CN114514776A (zh) * 2019-08-07 2022-05-17 日本电气株式会社 基于同时连接的切换

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC. (PDCP RAPPORTEUR): "Draft 38.323v0.0.5 NR PDCP specification", 3GPP DRAFT; R2-1704076 38323-005 NR PDCP SPECIFICATION - COVER, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Hangzhou, China; 20170515 - 20170519, 6 May 2017 (2017-05-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051264259 *

Also Published As

Publication number Publication date
CN117499991A (zh) 2024-02-02

Similar Documents

Publication Publication Date Title
JP4318733B2 (ja) 処理時間情報を含む制御プロトコルデータユニットの送受信方法
US10602400B2 (en) Enhancement of PDCP status report
JP4437128B2 (ja) 無線通信システムにおける受信側の再確立時に制御ｐｄｕを処理する方法及び装置
US20170085492A1 (en) Packet data convergence protocol (pdcp) entity and method performed by the same
JP7376363B2 (ja) 無線リンク制御ステータスのレポーティング
US8179812B2 (en) System and method for providing status reports of transmitted data packets in a data communications system
CN111148163B (zh) 通信方法及装置
WO2017049647A1 (fr) Procédé d'envoi de données, procédé de réception de données et dispositif approprié
JP5677438B2 (ja) 媒体アクセス制御順序配送のための方法および装置
KR20160073227A (ko) 무선 통신 시스템에서 기지국과 단말 간 통신 방법을 결정하는 방법 및 장치
US20210007008A1 (en) Method and apparatus for data segmentation and reassembly over multiple wireless links
US20200077300A1 (en) Data transmission method, apparatus, and system, and device
WO2021056589A1 (fr) Procédé et appareil de transmission de données
WO2019029350A1 (fr) Procédé de traitement de données, et dispositif associé
EP3790213B1 (fr) Demande de répétition automatique hybride basée sur mac (harq)
CN113938431A (zh) 突发数据包传输方法、装置和电子设备
WO2024028277A1 (fr) Équipement, dispositifs et procédés de communication d'infrastructure
CN113316922B (zh) 用于传输数据分组的设备、方法、装置以及计算机可读存储介质
WO2024022198A1 (fr) Procédé de distribution de données et dispositif de communication
EP4258731A1 (fr) Procédé de traitement de transmission de données et appareil associé
WO2021087729A1 (fr) Procédé et appareil pour indiquer un objet décompressé, et dispositif de communication
WO2023010254A1 (fr) Procédé et appareil de transmission de données, dispositif, et support de stockage
US11202226B2 (en) Uplink data transmission method, timer configuration method, and related device
WO2017140277A1 (fr) Entité de fonction de commande de liaison radio, et procédé de traitement de données et support de stockage associé
CN116156560A (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: 23845409

Country of ref document: EP

Kind code of ref document: A1