A user data processing method and device

Abstract

The embodiment of the present application provides a user data processing method and device, which relates to the field of communications, can reduce the load of data packets, and can reduce user plane delay. The method is as follows: a terminal device receives a first configuration parameter from a network device, the first configuration parameter includes at least one of the number of aggregated data packets N, the size of the aggregated data packet S, and the state of the resource block RB, and the first configuration parameter is used to instruct the terminal device to aggregate data packets through the packet data convergence protocol PDCP layer; the PDCP layer of the terminal device aggregates multiple data packets according to the first configuration parameter to generate an aggregated data packet; the PDCP layer delivers the aggregated data packet to the medium access control MAC layer or the radio link control RLC layer after the data packet aggregation is completed, or the PDCP layer delivers the aggregated data packet to the MAC layer or the RLC layer according to a preset delivery period.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a user data processing method and device. Background Art

[0002] The access network user plane protocol stack of the fifth generation (5G) mobile communication system new radio (NR) is as follows Figure 1 As shown, the transmitting end (e.g., UE) and the receiving end (e.g., gNB) have equivalent protocol layers. Taking the UE side as an example, the user plane protocol stack includes layer 1 and layer 2. Layer 1 includes the physical layer (PHY), and layer 2 includes the following sublayers: medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP).

[0003] In the uplink data packet processing process, the UE's application layer generates an uplink data packet (referred to as data packet), implements the mapping between the data packet's quality of service (QoS) and the bearer (RB) through the SDAP layer, and then sends the data packet to the PDCP layer; the PDCP layer assigns a sequence number (SN) to the data packet, performs header compression and integrity protection, and then delivers the data packet to the RLC layer; the RLC transmits the data packet to the MAC layer based on the time-frequency resource size (size). The MAC layer multiplexes different data packets into transport blocks (TB), and then delivers the data packet to the physical layer, which transmits the data packet through the air interface.

[0004] At present, when integrity protection is performed on a data packet at the PDCP layer, a 32-bit message integrity authentication code (MAC-I) can be added. The frequency of small packet transmission in the existing network is high. For example, when the size of the data packet is 40 bytes, the proportion of adding only MAC-I reaches 10%. The overhead of MAC-I is too high, which increases the load of the data packet. In order to reduce the load of the data packet, multiple small packets can be cascaded into a large packet for transmission (for example, multiple small packets can be cascaded into a large packet for transmission at the PDCP layer). However, data packet cascading introduces new processing delays. In addition, after the data packet is cascaded, the size of the PDCP PDU is increased, causing the probability of data packet segmentation at the RLC layer to increase, resulting in the user plane processing delay (the processing delay from the PDCP layer processing to the physical layer transmission is called the user plane processing delay) may be too large. Summary of the invention

[0005] The present application provides a user data processing method and device, which can reduce the load of data packets and reduce user plane delay.

[0006] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, a user data processing method is provided, including: a terminal device receives a first configuration parameter from a network device, the first configuration parameter includes at least one of the number of aggregated data packets N, the size of the aggregated data packet S, and the state of a resource block RB, the number of aggregated data packets N is used to indicate that a maximum of N data packets are aggregated into one data packet, N is an integer greater than or equal to 2, the size of the aggregated data packet S is used to indicate that the size of the data packet after aggregation does not exceed S, S is greater than 0, the state of the RB is used to indicate whether the RB is allowed to carry the aggregated data packet, the first configuration parameter is used to instruct the terminal device to aggregate the data packet through the packet data convergence protocol PDCP layer; the PDCP layer of the terminal device aggregates multiple data packets according to the first configuration parameter to generate an aggregated data packet; the PDCP layer delivers the aggregated data packet to the medium access control MAC layer or the radio link control RLC layer after the data packet aggregation is completed, or the PDCP layer delivers the aggregated data packet to the MAC layer or the RLC layer according to a preset delivery period.

[0008] Based on the embodiments of the present application, the PDCP layer of the terminal device can aggregate data packets to avoid excessive MAC-I overhead and reduce the load of data packets. In addition, the PDCP layer can deliver the aggregated data packets to the next layer (MAC layer / RLC layer) after the data packet aggregation is completed, or deliver the aggregated data packets to the next layer (MAC layer / RLC layer) according to a preset delivery cycle. In this way, the PDCP layer can aggregate data packets and deliver data packets to the next layer without waiting for the scheduling indication sent by the MAC layer (through the RLC layer) (the scheduling indication sent by the MAC layer is used to trigger the PDCP to process the data packets received from the upper layer), which can save user plane processing delay. Among them, the scheduling indication sent by the MAC layer can be, for example, an uplink scheduling grant (UL Grant).

[0009] In a second aspect, a user data processing method is provided, including: a terminal device receives a first configuration parameter from a network device, the first configuration parameter includes at least one of the number of aggregated data packets N, the size of the aggregated data packet S, and the status of a resource block RB, the number of aggregated data packets N is used to indicate that a maximum of N data packets are aggregated into one data packet, N is an integer greater than or equal to 2, the size of the aggregated data packet S is used to indicate that the size of the data packet after aggregation does not exceed S, S is greater than 0, the status of the RB is used to indicate whether the RB is allowed to carry the aggregated data packet, the first configuration parameter is used to instruct the terminal device to aggregate the data packet through the service data adaptation protocol SDAP layer; the SDAP layer of the terminal device aggregates multiple data packets according to the first configuration parameter to generate an aggregated data packet; the SDAP layer submits the aggregated data packet to the packet data convergence protocol PDCP layer after the data packet aggregation is completed, or the SDAP layer submits the aggregated data packet to the PDCP layer according to a preset submission period.

[0010] Based on the embodiment of the present application, the SDAP layer of the terminal device can perform data packet aggregation to avoid excessive MAC-I overhead and reduce the load of the data packet. Since there is no need for data packet aggregation by the PDCP layer, MAC layer or RLC layer, and the processing delay of the SDAP layer does not belong to the user plane processing delay, the data packet aggregation by the SDAP layer will not cause the user plane processing delay to increase (this is because the MAC layer requests transmission resources only after the data packet reaches the PDCP layer and the RLC layer, and the time from the MAC layer requesting the transmission resources to the MAC layer transmitting the data through the transmission resources belongs to the user plane processing delay, and if the data packet aggregation process is performed at the SDAP layer, it means that the data packet has been aggregated when it reaches the PDCP layer and the RLC layer, and the data packet aggregation process does not belong to the user plane processing delay).

[0011] In one possible design, the method further includes: the terminal device receives first indication information from the network device, the first indication information being used to instruct the MAC layer of the terminal device to perform data packet segmentation processing. In this way, data packet loss caused by the inability of TB resources to carry PDCP PDU can be avoided.

[0012] In a possible design, when the transport block TB resource cannot carry a packet data convergence protocol data unit PDCP PDU, the MAC layer of the terminal device performs data packet segmentation processing on the PDCP PDU; the MAC layer of the terminal device generates a sequence number SN for the segmented message, and the SN generated by the MAC layer and the SN generated by the PDCP layer for the PDCP PDU have a mapping relationship. In this way, the corresponding relationship of the segmented message can be determined based on the SN to avoid message confusion.

[0013] In one possible design, the first configuration parameter is included in a radio resource control RRC message or a cell switching message or a specific media access control element MAC CE.

[0014] In one possible design, the method further includes: the terminal device sends first capability information to the network device, the first capability information is used to indicate the capability of the terminal device to aggregate data packets at the PDCP layer, and the first capability information includes at least one of the number of aggregated data packets N or the size of the aggregated data packets S. In this way, the network device can configure corresponding parameters (first configuration parameters) for the terminal device based on the first capability information, and can ensure that the parameters configured by the network device are adapted to the capabilities of the terminal device.

[0015] In one possible design, the method further includes: the terminal device sends second capability information to the network device, the second capability information is used to indicate the capability of the terminal device to aggregate data packets at the SDAP layer, and the second capability information includes at least one of the number of aggregated data packets N or the size of the aggregated data packets S. In this way, the network device can configure corresponding parameters (first configuration parameters) for the terminal device based on the second capability information, and can ensure that the parameters configured by the network device are adapted to the capabilities of the terminal device.

[0016] In a possible design, the ability of a terminal device to aggregate data packets is related to the type of the terminal device, and the type of the terminal device is related to the uplink rate level UL Category of the terminal device. For example, when the UE UL Category is Category 0, the maximum number of data packets that the SDAP layer can aggregate is 30; when the UE UL Category is Category 3, the maximum number of data packets that the SDAP layer can aggregate is 20; when the UE UL Category is Category 5, the maximum number of data packets that the SDAP layer can aggregate is 10.

[0017] In a possible design, the terminal device receives second indication information from the network device, and the second indication information is used to indicate whether the terminal device starts parallel preprocessing at the PDCP layer; if the second indication information is used to indicate that the terminal device starts parallel preprocessing at the PDCP layer, the PDCP layer delivers the header-compressed message to the RLC layer or the MAC layer, and the header-compressed message reserves an X-bit integrity protection field and a Y-bit data packet sequence number SN field; wherein X and Y are integers greater than 0; when the RLC layer or the MAC layer processes the header-compressed message, the PDCP layer calculates the integrity protection parameters and SN sequence number of the header-compressed message, and fills the integrity protection parameters and SN sequence number into the header-compressed message. This method can realize parallel processing of messages (data packets) at the RLC layer and the PDCP layer, and reduce the user plane processing delay.

[0018] In a possible design, the method further includes: the terminal device sends user data at intervals of n symbols at the time point of sending the physical uplink shared channel PUSCH; n is a value configured by the network device or a fixed value; wherein n symbols are used to send reference signals or high-level control signaling or information indicating the location where the network device sends user data. In this way, the problem of data transmission confusion caused by the terminal device failing to prepare and complete the uplink data packet to be sent at the time point of sending the PUSCH can be avoided.

[0019] In a possible design, the terminal device carries a high-level message or L1 signaling in the physical uplink shared channel PUSCH, and the high-level message or L1 signaling is used to instruct the network device to cancel the PUSCH uplink authorization, and the high-level message or L1 signaling includes at least one of a scheduling request and user cache data. In this way, the problem of data transmission confusion can be avoided.

[0020] In one possible design, the terminal device carries the processing delay caused by data packet aggregation in the first capability information or the second capability information. In this way, the network device (e.g., base station) can take into account the processing delay caused by data packet aggregation when allocating uplink authorization resources, thereby avoiding the problem that data cannot be sent at the start symbol due to insufficient PUSCH preparation time.

[0021] In one possible design, the delay N3 generated by aggregating data packets under different subcarrier spacings is added on the terminal device side. In this way, when allocating uplink authorization resources, the network device (e.g., base station) can determine the location of the time domain when sending uplink PUSCH based on the total processing delay corresponding to different subcarrier spacings, which can avoid the problem that data cannot be sent at the start symbol due to insufficient PUSCH preparation time.

[0022] According to a third aspect, a user data processing method is provided, including: a network device sends a first configuration parameter to a terminal device, the first configuration parameter includes at least one of the number of aggregated data packets N, the size of the aggregated data packet S, and the status of a resource block RB, the number of aggregated data packets N is used to indicate that a maximum of N data packets are aggregated into one data packet, N is an integer greater than or equal to 2, the size of the aggregated data packet S is used to indicate that the size of the data packet after aggregation does not exceed S, S is greater than 0, the status of the RB is used to indicate whether the RB is allowed to carry the aggregated data packet, and the first configuration parameter is used to instruct the terminal device to aggregate the data packet through the Packet Data Convergence Protocol PDCP layer.

[0023] In a fourth aspect, a user data processing method is provided, including: a network device sends a first configuration parameter to a terminal device, the first configuration parameter includes at least one of the number of aggregated data packets N, the size of the aggregated data packet S, and the status of a resource block RB, the number of aggregated data packets N is used to indicate that a maximum of N data packets are aggregated into one data packet, N is an integer greater than or equal to 2, the size of the aggregated data packet S is used to indicate that the size of the data packet after aggregation does not exceed S, S is greater than 0, the status of the RB is used to indicate whether the RB is allowed to carry the aggregated data packet, and the first configuration parameter is used to instruct the terminal device to aggregate the data packet through the service data adaptation protocol SDAP layer.

[0024] In one possible design, the above method also includes: the network device sends first indication information to the terminal device, and the first indication information is used to instruct the MAC layer of the terminal device to perform data packet segmentation processing.

[0025] In one possible design, the first configuration parameter is included in a radio resource control RRC message or a cell switching message or a specific media access control element MAC CE.

[0026] In one possible design, the above method also includes: the network device receives first capability information from the terminal device, the first capability information is used to indicate the PDCP layer aggregation data packet capability of the terminal device, and the first capability information includes at least one of the number of aggregated data packets N or the size of aggregated data packets S.

[0027] In one possible design, the method further includes: the network device receives second capability information from the terminal device, the second capability information is used to indicate the SDAP layer aggregation data packet capability of the terminal device, and the second capability information includes at least one of the number of aggregated data packets N or the size of the aggregated data packets S.

[0028] In one possible design, the ability of a terminal device to aggregate data packets is related to the type of the terminal device, and the type of the terminal device is related to the uplink rate grade UL Category of the terminal device.

[0029] In one possible design, the network device sends second indication information to the terminal device, where the second indication information is used to indicate whether the terminal device starts PDCP layer parallel preprocessing.

[0030] In one possible design, the above method also includes: the network device receives user data at an interval of n symbols when receiving the physical uplink shared channel PUSCH; n is a value configured by the network device or a fixed value; wherein n symbols are used to send reference signals or high-level control signaling or information indicating the location where the network device sends user data.

[0031] In one possible design, the network device receives a high-level message or L1 signaling on a physical uplink shared channel PUSCH, where the high-level message or L1 signaling is used to instruct the network device to cancel PUSCH uplink authorization, and the high-level message or L1 signaling includes at least one of a scheduling request and user cached data.

[0032] In one possible design, the first capability information or the second capability information carries a processing delay caused by data packet aggregation.

[0033] In one possible design, a delay N3 caused by aggregating data packets under different subcarrier spacings is added on the network device side.

[0034] In a fifth aspect, a terminal device is provided, comprising: a memory for storing a computer program; a transceiver for receiving or sending a radio signal; and a processor for executing the computer program, so that the terminal device executes a method in any possible implementation of the first aspect or the second aspect.

[0035] In a sixth aspect, a network device is provided, comprising: a memory for storing a computer program; a transceiver for receiving or sending a radio signal; and a processor for executing the computer program, so that the network device executes a method in any possible implementation of the third aspect or the fourth aspect.

[0036] In a seventh aspect, a communication system is provided, which includes a terminal device as in any possible implementation of the first aspect or the second aspect, and a network device as in any possible implementation of the third aspect or the fourth aspect.

[0037] In an eighth aspect, a computer-readable storage medium is provided, on which a computer program code is stored. When the computer program code is executed by a processor, the processor implements a method in any possible implementation manner of any aspect from the first aspect to the fourth aspect.

[0038] In a ninth aspect, a chip system is provided, the chip system comprising a processor and a memory, wherein a computer program code is stored in the memory; when the computer program code is executed by the processor, the processor implements a method in any possible implementation manner in any aspect of the first aspect to the fourth aspect. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0039] In a tenth aspect, a computer program product is provided, the computer program product comprising computer instructions. When the computer instructions are executed on a computer, the computer implements the method in any possible implementation manner of any aspect from the first aspect to the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 A schematic diagram of the structure of a user plane protocol stack on a UE and a base station side provided in an embodiment of the present application;

[0041] Figure 2 A schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0042] Figure 3A A schematic diagram of the structure of a user plane protocol stack on a UE side provided in an embodiment of the present application;

[0043] Figure 3B A schematic diagram of the processing flow of each sublayer of a UE provided in an embodiment of the present application;

[0044] Figure 4 A schematic diagram of signal interaction of each sub-layer of a UE provided in an embodiment of the present application;

[0045] Figure 5 A schematic diagram of processing a data packet provided in an embodiment of the present application;

[0046] Figure 6 A schematic diagram of processing another data packet provided in an embodiment of the present application;

[0047] Fig. 7A A schematic diagram of the structure of a user plane protocol stack on a UE side provided in another embodiment of the present application;

[0048] Figure 7B A schematic diagram of a processing flow of each sublayer of another UE provided in an embodiment of the present application;

[0049] Figure 8 A schematic diagram of signal interaction of each sublayer of another UE provided in an embodiment of the present application;

[0050] Fig. 9 A schematic diagram of processing another data packet provided in an embodiment of the present application;

[0051] Fig.10 A schematic diagram of processing another data packet provided in an embodiment of the present application;

[0052] Fig.11 A schematic diagram of the structure of a user plane protocol stack on a UE side provided in another embodiment of the present application. DETAILED DESCRIPTION

[0053] The technical solution in the embodiment of the present application will be described below in conjunction with the drawings in the embodiment of the present application. Among them, in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. And, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit the differences. At the same time, in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0054] In order to make the description of the following embodiments clear and concise, a brief introduction to the relevant concepts or technologies is first given:

[0055] Service Data Unit (SDU): corresponds to the data that is not processed in a certain sublayer. For a certain sublayer, the data it receives is SDU.

[0056] Protocol Data Unit (PDU): corresponds to data in a specific format processed by a certain sublayer. For a certain sublayer, the data it sends is PDU.

[0057] It can be understood that the service data unit (SDU) of the Nth protocol layer corresponds one to one with the protocol data unit (PDU) of the upper layer.

[0058] For example, for the SDAP layer, the data received from the upper layer (application layer) is the SDAP SDU, and the data sent to the lower layer (e.g., PDCP layer) is the SDAP PDU. For the PDCP layer, the data received from the upper layer (SDAP layer) is the PDCP SDU, and the data sent to the lower layer (e.g., RLC layer) is the PDCP PDU. Among them, the PDCP SDU is equivalent to the SDAP PDU.

[0059] At present, when integrity protection is performed on user-plane data at the PDCP layer, a 32-bit MAC-I can be added. The frequency of small packet transmission in the existing network is high. For example, when the size of a data packet is 40 bytes, the proportion of adding only MAC-I reaches 10%. The overhead of MAC-I is too high, which increases the load of the data packet.

[0060] In order to reduce the load of data packets, multiple small packets can be cascaded into a large packet for transmission (for example, multiple small packets can be cascaded into a large packet for transmission at the PDCP layer). However, data packet cascading introduces new processing delays. In addition, after data packets are cascaded, the size of the PDCP PDU is increased, causing the probability of data packets being segmented at the RLC layer to increase, resulting in the user plane processing delay (the processing delay from the PDCP layer processing to the physical layer transmission process is called the user plane processing delay) may be too large.

[0061] The embodiment of the present application provides a data packet aggregation method, which can not only reduce the load of data packets, but also reduce user plane delay.

[0062] Figure 2 A schematic diagram of a communication system to which the technical solution provided in an embodiment of the present application is applicable is provided, and the communication system may include a network side device 100 and a terminal side device 200 connected to the network side device 100. Data can be transmitted between the network side device (also referred to as a network device) and the terminal side device (also referred to as a terminal device).

[0063] The network side device 100 may be a device that can communicate with the terminal side device 200. For example, the network side device 100 may be a base station, which may be an evolved NodeB (eNB or eNodeB) in LTE, or a base station in NR, or a relay station or access point, or a base station in a future network, etc., which is not limited in the embodiments of the present application. Among them, the base station in NR may also be referred to as a transmission reception point (TRP) or gNB. In the embodiments of the present application, the network side device may be an independently sold network device, such as a base station, or a chip that implements the corresponding function in the network device. In the embodiments of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In the technical solution provided in the embodiments of the present application, the technical solution provided in the embodiments of the present application is described by taking the device for implementing the functions of the network side device as a network device as an example.

[0064] Among them, the terminal side device 200 in the embodiment of the present application can also be called a terminal, which can be a device with wireless transceiver function. The terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.). The terminal side device can be a user equipment (UE). Among them, the UE includes a handheld device, a vehicle-mounted device, a wearable device or a computing device with wireless communication function. Exemplarily, the UE can be a mobile phone, a tablet computer or a computer with wireless transceiver function. The terminal side device can also be a virtual reality (VR) terminal side device, an augmented reality (AR) terminal side device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city, a wireless terminal in smart home, etc. In the embodiment of the present application, the terminal side device can be a terminal sold independently or a chip in the terminal. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the device for realizing the function of the terminal as a terminal side device as an example.

[0065] Embodiments of the present application Figure 2The network side device 100 or the terminal side device 200 in the embodiment may be implemented by a device or a functional module in a device, and the embodiment of the present application does not specifically limit this. It is understandable that the above functions may be network elements in a hardware device, software functions running on dedicated hardware, virtualization functions instantiated on a platform (e.g., a cloud platform), or a chip system. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0066] The embodiment of the present application provides three different data packet aggregation methods, which are described in detail below with reference to the accompanying drawings.

[0067] The first packet aggregation method is based on the first user plane protocol stack architecture, such as Figure 3A As shown, the first user plane protocol stack may include layer 1 and layer 2. Layer 1 includes a physical layer, and layer 2 includes sublayers such as a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer.

[0068] like Figure 3B As shown, the main functions of each sublayer are as follows:

[0069] SDAP layer: performs QoS flow processing and mapping between data bearers (i.e., data packets can be mapped to corresponding RBs) and header compression and other processing. Among them, header compression can be, for example, robust header compression (Robust Header Compression, ROHC). It should be noted that in the embodiment of the present application, the SDAP layer can also be used for data packet aggregation.

[0070] PDCP layer: used to perform security protection (e.g., encryption, decryption, integrity protection) on data packets, as well as data packet sorting and data packet delivery (in-order / out-of-order delivery).

[0071] RLC layer: used for automatic repeat request (ARQ) error correction, data packet segment assembly and data packet re-segmentation in confirmation mode.

[0072] MAC layer: multiplexes / demultiplexes data packets belonging to one or different logical channels onto the transport channel, maps data packets to TBs, and can also perform scheduling information reporting, hybrid automatic repeat request (HARQ) error correction and resource scheduling priority processing, multiplexing, and data packet segmentation.

[0073] It should be understood that Figure 3BThe main functions of each sublayer are shown. Each sublayer may also include other functions not shown, which are not limited in this application.

[0074] When the UE adopts the first user plane protocol stack architecture, such as Figure 4 As shown in the figure, the processing flow of the uplink data packet is as follows:

[0075] S101. The SDAP layer obtains Internet Protocol Address (IP) data packets from the application layer, and maps IP data packets with different QoS requirements to different RBs.

[0076] The SDAP layer can add different QoS flow identifiers (QoS flowID, QFI) in different IP packets (IP Packets). Different IP packets can be mapped to different RBs according to different QFIs. In the embodiment of the present application, RB may refer to a data radio bearer (Data RB, DRB), that is, a data bearer between a terminal and a base station.

[0077] For example, Figure 5 As shown, the SDAP layer can map IP data packet 1 and IP data packet 2 (IP data packet 1 and IP data packet 2 can be called SDAP SDU in the SDAP layer) to RB1.

[0078] S102: The SDAP layer performs a header compression process on the IP data packet.

[0079] The IP data packet may include an IP packet header (IP header for short) and IP data. The SDAP layer may compress the IP header of the IP data packet, that is, may reduce the size of the IP header including unnecessary control information, so that the IP header may only include necessary information, so as to improve the transmission efficiency of the wireless interface.

[0080] like Figure 6 As shown, the IP headers of IP data packet 1 and IP data packet 2 can be compressed respectively to reduce the load of the IP data packets.

[0081] S103, the SDAP layer aggregates IP data packets.

[0082] The SDAP layer can aggregate the IP data packets compressed by the header according to the relevant configuration parameters of the SDAP layer aggregation data packets. The relevant configuration parameters of the SDAP layer aggregation data packets can be configured by the core network device or by the access network device (eg, base station).

[0083] In one possible design, the UE may send UE capability information (second capability information) to the access network device. The UE capability information may include the capability of SDAP layer aggregation data packets. The capability of SDAP layer aggregation data packets may include the number of aggregated data packets N, the size of aggregated data packets S, etc.

[0084] Different types of UEs may correspond to different data packet aggregation capabilities. Different types of UEs may be distinguished according to the UE uplink rate level (UE ULCategory). As shown in Table 1, when the UE UL Category is Category 0, the maximum number of data packets that the SDAP layer can aggregate is 30; when the UE UL Category is Category 3, the maximum number of data packets that the SDAP layer can aggregate is 20; when the UE UL Category is Category 5, the maximum number of data packets that the SDAP layer can aggregate is 10.

[0085] Table 1

[0086] UE uplink rate level Maximum number of packets aggregated at the SDAP layer Category 0 30 Category 3 20 Category 5 10

[0087] When establishing a bearer between the terminal and the base station, the base station can configure and send down the relevant configuration parameters of the SDAP layer aggregated data packet to the UE according to the UE's capability information. For example, the base station can send down the relevant configuration parameters of the SDAP layer aggregated data packet through a radio resource control (RRC) message. Among them, the relevant configuration parameters of the SDAP layer aggregated data packet may include at least one of the number of aggregated data packets N, the size of the aggregated data packet S, the data packet cascade control flag, and the status of the RB.

[0088] Among them, the number of aggregated data packets can be N, indicating that at most N IP data packets can be aggregated into a large data packet. The size of the aggregated data packet can be S, indicating that the maximum size of the aggregated data packet is allowed to be S bytes. The data packet cascading control flag is used to indicate whether the RB corresponding to the IP data packet is allowed to carry aggregated cascaded data packets. The state of the RB may include an activated state or an inactivated state. Among them, the activated state is used to indicate that the RB is currently allowed to carry aggregated cascaded data packets, that is, the UE can perform aggregation operations on multiple data packets in the RB. The inactivated state is used to indicate that the RB is currently not allowed to carry aggregated cascaded data packets, that is, the UE cannot perform aggregation operations on multiple data packets in the RB. The default configuration of the RB can be an activated state. The base station or core network device can change the state of the RB by sending a high-level message, or an L3 message (L2 message or L1 message), or a MACCE, or a physical layer signaling.

[0089] In the embodiment of the present application, when establishing a bearer between the terminal and the base station, the network can send down the relevant configuration parameters of the SDAP layer aggregation data packet, but is not limited to sending down when establishing the bearer. For example, the relevant configuration parameters of the SDAP layer aggregation data packet can also be sent through a switching message during the switching process, which is not limited in the present application.

[0090] Optionally, after the data packet aggregation is completed, an SDAP header may be added in front of the aggregated IP data packet.

[0091] For example, assuming that the number of aggregated data packets N configured by the core network device or the base station is 2, the SDAP layer can aggregate every two IP data packets of the application layer into a large data packet. Figure 6 As shown, the IP data packet 1 and the IP data packet 2 after header compression can be aggregated to obtain an aggregated data packet, and an SDAP header can be added to the aggregated data packet to obtain an SDAP PDU.

[0092] S104: After the SDAP layer completes the aggregation of the data packets, it delivers the SDAP PDU to the PDCP layer.

[0093] In one possible design, when the aggregated data reaches a control threshold requirement, such as reaching the maximum number of aggregated data packets N allowed, or reaching S bytes, the data packet aggregation is completed, and the SDAP layer delivers the aggregated data packet (SDAP PDU) to the next layer (eg, PDCP layer).

[0094] For example, Figure 5 As shown, assuming that the maximum number of aggregated data packets N allowed is 2, the SDAP layer can aggregate IP data packet 1 and IP data packet 2, and add an SDAP header (ie, H) to the aggregated data packet to obtain an SDAP PDU, and then submit the SDAP PDU to the PDCP layer.

[0095] In another possible design, the SDAP layer may deliver the aggregated data packets to the next layer (e.g., the PDCP layer) according to the delivery cycle. That is, in each delivery cycle, the aggregated data packets within the delivery cycle are delivered to the next layer. The duration of the delivery cycle may be Xms (e.g., 3ms, 5ms, etc.), and this application does not limit the time unit and specific parameter configuration of the delivery cycle.

[0096] S105. The PDCP layer receives the SDAP PDU from the SDAP layer, and performs operations such as integrity protection on the SDAP PDU to obtain the PDCP PDU.

[0097] Exemplarily, the PDCP layer performs the integrity protection operation by adding a MAC-I to each SDAP PDU, and the MAC-I may include 32 bits.

[0098] like Figure 6 As shown, MAC-I may be added to the SDAP PDU (the SDAP PDU may be referred to as a PDCP SDU at the PDCP layer), and then a PDCP header may be added to obtain the PDCP PDU.

[0099] S106. The PDCP layer delivers the PDCP PDU to the RLC layer.

[0100] like Figure 5 As shown, the PDCP layer can deliver the PDCP PDU to the RLC layer. The PDCP PDU includes a PDCP SDU and an H, and the H may include a MAC-I and an SDAP header.

[0101] S107. The RLC layer receives the PDCP PDU from the PDCP layer, and processes the PDCP PDU to obtain an RLC PDU.

[0102] To ensure the QoS requirements of each RB, the RLC layer can provide three operation modes, including transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM). When the RLC layer adopts acknowledged mode (AM), retransmission can be performed through the ARQ function to ensure reliable data transmission.

[0103] The RLC layer can segment / reassemble the PDCP PDU corresponding to each logical channel group to match the size of the MAC PDU allocated by the MAC layer. The RLC layer can add an RLC header to the segmented / reassembled PDCP PDU to encapsulate it into an RLC PDU and deliver it to the MAC layer. The RLC header may include a sequence number (SN), so that the receiving side can know the RLC PDU lost during transmission according to the SN.

[0104] S108. The RLC layer sends RLC PDU to the MAC layer.

[0105] like Figure 5 As shown, the RLC layer receives the PDCP PDU (PDCP PDU is called RLC SDU in the RLC layer) from the PDCP layer, and sends the RLC PDU to the MAC layer. The RLC PDU includes the RLC SDU and H, and the H may include the RLC header.

[0106] S109. The MAC layer receives the RLC PDU (RLC PDU is called MAC SDU in the MAC layer), and processes the RLC PDU to obtain a MAC PDU.

[0107] The MAC layer plays a scheduling role and is responsible for allocating the physical resources (transmission channels) corresponding to this transmission to several logical channel groups according to the preset scheduling strategy (such as priority allocation for long-term non-scheduling (i.e., priority scheduling of data with the longest waiting time in the queue) or scheduling according to the priority of the data). The length of the RLC PDU of each logical channel group can be different. The MAC layer can connect one or more RLC PDUs in series and encapsulate them into a MAC layer protocol data unit (MAC PDU) with a MAC subheader. One MAC PDU can carry data of multiple different logical channel groups.

[0108] A MAC PDU can be carried on a TB, and the size of the TB is determined by the number of physical resources allocated to the TB and the modulation and coding scheme (MCS). That is, the length of the MAC PDU is determined by the number of physical resources and code rate, modulation mode, number of space division multiplexing layers, etc. of the TB. At the same time, when the base station allocates resources to the TB and determines the modulation mode and code rate of the TB, the factors considered include link quality, data size in the buffer (each logical channel group corresponds to a buffer), logical channel group priority, number of users to be scheduled, user priority, etc.

[0109] like Figure 5 As shown, the MAC layer can receive the RLC PDU (ie, MAC SDU) from the RLC layer, and obtain the MAC PDU according to the RLC PDU. The MAC PDU includes the MAC SDU and H, and the H includes the MAC header. The MAC layer can map the MAC PDU to TB1.

[0110] S110. The MAC layer sends a MAC PDU to the physical layer.

[0111] The physical layer receives the MAC PDU from the MAC layer, and matches the MAC PDU with the size of the actual physical resource through rate matching. The remaining processes can refer to the prior art, and this application will not be described in detail here.

[0112] Based on the embodiment of the present application, the SDAP layer can perform data packet aggregation to reduce the load of data packets. Since there is no need for the PDCP layer, MAC layer or RLC layer to perform data packet aggregation, and the processing delay of the SDAP layer does not belong to the user plane processing delay, the data packet aggregation performed by the SDAP layer will not lead to an increase in the user plane processing delay (this is because the MAC layer requests transmission resources only after the data packet reaches the PDCP layer and the RLC layer, and the time from the MAC layer requesting the transmission resources to the MAC layer transmitting the data through the transmission resources belongs to the user plane processing delay. If the data packet aggregation process is performed at the SDAP layer, it means that the data packet has been aggregated when it reaches the PDCP layer and the RLC layer, and the data packet aggregation process does not belong to the user plane processing delay).

[0113] The second packet aggregation method is based on the second user plane protocol stack architecture, such as Fig. 7A As shown, the second user plane protocol stack may include layer 1 and layer 2. Layer 1 includes a physical layer (PHY), and layer 2 includes sublayers such as a MAC layer, a PDCP layer, and a SDAP layer.

[0114] like Figure 7B As shown, the main functions of each sublayer are as follows:

[0115] SDAP layer: performs processing such as mapping between QoS flows and data bearers (ie, data packets can be mapped to corresponding RBs). Optionally, the SDAP layer can be used to perform header compression on data packets (eg, ROHC).

[0116] PDCP layer: used for security protection (e.g., encryption and decryption, integrity protection, etc.), data packet sorting, ARQ and data packet delivery (in-order / out-of-order delivery), etc. Optionally, if the SDAP layer does not perform header compression, the PDCP layer can be used to perform header compression (e.g., ROHC) on the data packet. It should be noted that in the embodiment of the present application, the PDCP layer can also be used for data packet aggregation.

[0117] MAC layer: multiplexes / demultiplexes data packets belonging to one or different logical channels onto the transport channel. The MAC layer can also perform scheduling information reporting, HARQ error correction and resource scheduling priority processing, multiplexing, data packet segmentation, etc.

[0118] When the UE adopts the second user plane protocol stack architecture, such as Figure 8 As shown in the figure, the processing flow of the uplink data packet is as follows:

[0119] S201. The SDAP layer obtains IP data packets from the application layer, and maps IP data packets with different QoS requirements to different RBs.

[0120] The IP data packet can be called SDAP SDU in the SDAP layer. The SDAP layer can add an SDAP header to each SDAP SDU and encapsulate it into an SDAP PDU. The specific process can refer to the description of step S101, which will not be repeated here.

[0121] For example, Fig. 9 As shown, the SDAP layer can map the SDAP PDU corresponding to the IP data packet 1 and the IP data packet 2 to RB1.

[0122] S202: The SDAP layer delivers the SDAP PDU to the PDCP layer.

[0123] S203: The PDCP layer performs a header compression process on the SDAP PDU.

[0124] The PDCP layer may compress the IP header of the SDAP PDU, or the PDCP layer may compress the IP header and the SDAP packet header of the SDAP PDU to reduce the size of unnecessary control information so as to improve the transmission efficiency of the wireless interface.

[0125] like Fig.10 As shown, the PDCP layer can perform header compression on SDAP PDU 1 and SDAP PDU 2 respectively to reduce the size of unnecessary control information.

[0126] S204: The PDCP layer aggregates the compressed data packets.

[0127] The PDCP layer can aggregate the header-compressed data packets. The relevant configuration parameters of the PDCP layer aggregated data packets can be configured by the core network device or by the access network device (eg, base station).

[0128] In one possible design, the UE may send UE capability information (first capability information) to the access network device. The UE capability information may include the capability of aggregating data packets at the PDCP layer. The capability of aggregating data packets at the PDCP layer may include the number of aggregated data packets N, the size of aggregated data packets S, etc.

[0129] Different types of UEs may correspond to different data packet aggregation capabilities. Different UEs may be distinguished according to the UE uplink rate level (UE ULCategory). As shown in Table 2, when the UE UL Category is Category 0, the maximum number of data packets that the PDCP layer can aggregate is 30; when the UE UL Category is Category 3, the maximum number of data packets that the PDCP layer can aggregate is 20; when the UE UL Category is Category 5, the maximum number of data packets that the PDCP layer can aggregate is 10.

[0130] Table 2

[0131] UE uplink rate level Maximum number of packets aggregated at the PDCP layer Category 0 30 Category 3 20 Category 5 10

[0132] When establishing a bearer between the terminal and the base station, the base station can configure and send down relevant configuration parameters of the PDCP layer aggregated data packet to the UE according to the UE's capability information. The relevant configuration parameters of the PDCP layer aggregated data packet may include at least one of the number of aggregated data packets N, the size of the aggregated data packet S, the data packet cascade control flag, and the status of the RB.

[0133] Among them, the number of aggregated data packets can be N, indicating that at most N IP data packets can be aggregated into a large data packet. The size of the aggregated data packet can be S, indicating that the maximum size of the aggregated data packet is allowed to be S bytes. The data packet cascading control flag is used to indicate whether the RB corresponding to the IP data packet is allowed to aggregate cascaded data packets. The state of the RB may include an activated state or an inactivated state. Among them, the activated state is used to indicate that the RB is currently allowed to carry aggregated cascaded data packets, that is, the UE can perform aggregation operations of multiple data packets on the RB. The inactivated state is used to indicate that the RB is currently not allowed to carry aggregated cascaded data packets, that is, the UE cannot perform aggregation operations of multiple data packets on the RB. The default configuration of the RB can be an activated state. The base station or core network device can change the state of the RB by sending a high-level message, or an L3 message (L2 message or L1 message), or a MAC CE, or a physical layer signaling.

[0134] In the embodiment of the present application, when establishing a bearer between the terminal and the base station, the network can send down the relevant configuration parameters of the PDCP layer aggregation data packet, but it is not limited to sending it down when establishing the bearer. For example, the relevant configuration parameters of the PDCP layer aggregation data packet can also be sent through a handover message during the handover process, which is not limited in the present application.

[0135] For example, assuming that the number of aggregated data packets N configured by the core network device or the base station is 2, the PDCP layer can aggregate every two SDAP PDUs of the application layer into a large data packet. Fig.10 As shown, the header-compressed SDAPPDU 1 and SDAP PDU 2 may be aggregated to obtain an aggregated data packet.

[0136] S205: After the PDCP layer completes the aggregation of the data packets, it performs operations such as integrity protection to obtain a PDCP PDU.

[0137] Exemplarily, the PDCP layer performs the integrity protection operation by adding a MAC-I to the aggregated data packet, and the MAC-I may include 32 bits.

[0138] like Fig.10As shown, a MAC-I may be added to the aggregated data packet, and then a PDCP header may be added to obtain a PDCP PDU, wherein the PDCP header may include an SN sequence number.

[0139] To ensure the QoS requirements of each RB, the PDCP layer may provide three operation modes, including a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM).

[0140] When the PDCP layer adopts the acknowledgement mode (AM), the PDCP layer can set a corresponding sending window for each AM bearer (i.e., RB in AM mode), and the sending window includes the sequence number of the frame that has been sent but not yet confirmed by the PDCP layer of the sender. The size of the sending window can be configured by the network. After the data in AM mode is sent, the PDCP layer slides forward after receiving the confirmation message sent by the opposite end. The PDCP layer entity or the MAC layer entity can trigger the opposite end to send a feedback message. For example, the MAC CE can be used to quickly request the opposite end entity to reply whether the AM mode data has been successfully received. If the AM mode data is not received by the opposite end, the PDCP layer entity triggers the ARQ function to perform retransmission. The way in which the PDCP layer determines that the AM mode data has not been successfully received by the opposite end may include but is not limited to the following ways: A. The opposite end entity confirms the NACK reply; B. The local MAC entity confirms the transmission failure; C. The retransmission timer times out.

[0141] S206. The PDCP layer delivers the PDCP PDU to the MAC layer.

[0142] In one possible design, when the aggregated data reaches a control threshold requirement, such as reaching the maximum number of aggregated data packets N allowed, or reaching S bytes, data packet aggregation is completed, and the PDCP layer delivers the aggregated data packet (PDCP PDU) to the next layer (e.g., the MAC layer).

[0143] For example, Fig. 9 As shown, assuming that the maximum number of aggregated data packets N allowed is 2, the PDCP layer can aggregate SDAPPDU1 and SDAP PDU2, and add a PDCP header (ie, H) to the aggregated data packet to obtain a PDCP PDU, and then submit the PDCP PDU to the PDCP layer.

[0144] In another possible design, the PDCP layer may deliver the aggregated data packets to the next layer (e.g., the MAC layer) according to the delivery cycle. That is, in each delivery cycle, the data packets aggregated in the delivery cycle are delivered to the next layer. The duration of the delivery cycle may be Xms (e.g., 3ms, 5ms, etc.), and this application does not limit the time unit and specific parameter configuration of the delivery cycle.

[0145] S207. The MAC layer receives the PDCP PDU (the PDCP PDU is called MAC SDU in the MAC layer), and processes the PDCP PDU to obtain a MAC PDU.

[0146] The MAC layer can cascade or segment the PDCP PDU. For example, the MAC layer receives a data packet (PDCP PDU) from the PDCP layer. Based on the principle of data multiplexing, one or more PDCP PDUs can be connected in series (cascaded) and then encapsulated into a MAC PDU by adding a MAC subheader. That is, the MAC layer can multiplex one or more PDCP PDUs into one MAC PDU. The principle of multiplexing data packets is to avoid the occurrence of segmentation scenarios. The MAC layer can specify an SN for the cascaded message, that is, the cascaded message can correspond to one MAC SN. The MAC SN and PDCP SN (the SN specified by the message at the PDCP layer) can be mapped within the MAC layer. That is, the MAC SN and PDCP SN can be associated and mapped.

[0147] When the current valid TB resources cannot carry any complete PDCP PDU, the MAC layer can determine whether to perform the segmentation function based on the network configuration. When the segmentation function is unavailable / disabled, the MAC layer will ignore the segmentation operation. When the segmentation function is disabled and there are data packets that need to be segmented, the MAC layer can report a resource request message to request the network to allocate resources so that the data can be sent in time. When the segmentation function is available / enabled (for example, a first indication information can be received from a network device, and the first indication information is used to instruct the MAC layer of the terminal device to perform data packet segmentation processing), the MAC layer can specify an SN for the segmented message, that is, the segmented message can correspond to a MAC SN. The MAC SN and the PDCP SN (the SN specified by the message at the PDCP layer) can be mapped inside the MAC layer. That is, the MAC SN and the PDCP SN can be associated and mapped. Based on the effective resource size, the MAC layer performs a segmentation operation on the PDCP PDU. Among them, the segmented MAC PDU can have the highest priority for transmission.

[0148] In addition, for AM mode data, the MAC layer can notify the PDCP layer whether to perform an ARQ retransmission operation based on HARQ feedback information.

[0149] The MAC layer then multiplexes / demultiplexes the data packets belonging to one or different logical channels onto the transport channel and maps the MAC PDU onto the TB.

[0150] like Fig. 9As shown, the MAC layer can receive the PDCP PDU (ie, MAC SDU) from the PDCP layer, and obtain the MAC PDU according to the PDCP PDU. The MAC PDU includes the MAC SDU and H, and the H includes the MAC header. The MAC layer can map the MAC PDU to TB1.

[0151] S208. The MAC layer sends a MAC PDU to the physical layer.

[0152] The physical layer receives the MAC PDU from the MAC layer and matches it with the size of the actual physical resource through rate matching. The remaining processes can refer to the prior art and will not be described in detail in this application.

[0153] Based on the embodiments of the present application, the PDCP layer can aggregate data packets to reduce the load of data packets. Moreover, the PDCP layer can deliver the aggregated data packets to the next layer (e.g., MAC layer) after the data packet aggregation is completed, or deliver the aggregated data packets to the next layer (e.g., MAC layer) according to a preset delivery cycle. In this way, the PDCP layer can aggregate data packets and deliver data packets to the next layer without waiting for the scheduling indication sent by the MAC layer (the scheduling indication sent by the MAC layer is used to trigger the PDCP to process the data packets received from the upper layer), which can save the user plane processing delay. Among them, the scheduling indication sent by the MAC layer can be, for example, an uplink scheduling authorization (UL Grant).

[0154] In some embodiments, based on the above-mentioned first or second user plane protocol stack architecture, the network can also control whether the UE starts parallel preprocessing of the PDCP layer. For example, the base station can instruct the UE to start or not start parallel preprocessing of the PDCP layer through signaling (second indication information). If the base station instructs the UE to start parallel preprocessing of the PDCP layer, the PDCP layer of the UE can perform header compression for each arriving data packet (PDCP SDU). When the PDCP layer needs to deliver the PDU to the lower layer (for example, the RLC layer or the MAC layer), the UE PDCP layer directly submits the header-compressed message to the lower layer. The message includes one or more PDCP SDUs, and the message reserves an X-bit (bit) integrity protection field and a Y-bit data packet SN field. When the RLC layer or the MAC layer processes the message, the PDCP layer simultaneously calculates the integrity protection parameters and fills the SN sequence number into the message. This method can realize parallel processing of messages at the RLC layer and the PDCP layer, reducing the user plane processing delay.

[0155] The third packet aggregation method is based on Fig.11The user plane protocol stack architecture shown can aggregate data packets by the PDCP layer, and the PDCP layer can deliver the aggregated data packets to the next layer (e.g., RLC layer) after the data packet aggregation is completed, or deliver the aggregated data packets (PDCP PDU) to the next layer (e.g., RLC layer) according to a preset delivery cycle, and the RLC layer delivers the PDCP PDU to the MAC layer. In this way, the PDCP layer can start aggregating data packets without waiting for the resource indication sent by the MAC layer, which can save the user plane processing delay. The specific process can refer to the relevant description above, which will not be repeated here.

[0156] Based on the three user plane protocol stack architectures introduced above, in order to prevent the problem that the UE fails to prepare the data packets to be sent within the user plane delay, resulting in the data cannot be sent in the start symbol, the UE can adopt the following solution.

[0157] Solution 1: Take DCI 0_0 as an example for uplink resource allocation. Format DCI 0_0 may include time domain resource assignment (TDRA) information. Of course, Format DCI 0_0 may also include other parameters, which are not described here. Among them, TDRA may be configured by RRC high-level parameters, and TDRA may include the following parameters:

[0158]

[0159] K2 is a slot offset, that is, the time interval between the uplink scheduled DCI and the PUSCH it schedules, and startSymbolAndLength is the symbol position at which the PUSCH starts and the symbol length of the PUSCH.

[0160] After receiving the uplink grant (UL Grant), the UE needs a period of time T to prepare the data to be sent on the PUSCH. If the UE cannot prepare the data to be sent within this period of time, for example, the UE takes too long to process the cascaded data packet (i.e., the aggregated data packet) and other reasons (but not limited to this reason), resulting in the uplink data packet to be sent not being fully prepared at the time point of sending the PUSCH (determined by K2 and startSymbolAndLength), the UE can perform the following operations:

[0161] The UE skips n symbols and sends data on the n+1th symbol, where n can be a value configured by the network for the UE or a fixed value, which is not limited in this application.

[0162] In one possible design, the UE may insert a reference signal into the interval of n symbols, or insert a high-level control signaling, or insert a signaling to notify the base station of a sequence of PUSCH symbol positions to be sent, or the UE may perform a punching process, which is not limited in this application.

[0163] Alternatively, the UE may send a high-level message or L1 (layer 1) signaling on the nearest PUSCH / PUCCH to cancel this scheduling. The high-level message or L1 signaling may include a scheduling request, user cached data, etc., which is not limited in this application. After receiving the high-level message or L1 signaling, the network device (e.g., base station) may cancel this PUSCH uplink grant.

[0164] It should be noted that solution 1 is described by taking the uplink resource allocation mode of DCI 0_0 as an example, and the present application is not limited thereto. For example, uplink resource allocation can also be performed by configuring uplink resources through high-layer signaling or by allocating resources in other DCI formats, and the present application does not limit this.

[0165] Solution 2: After the UE receives the uplink Grant, it takes time T to prepare the data to be sent on the PUSCH. This time T can be called the terminal processing delay T. Among them, T is related to the parameter PUSCH preparation time N2 (unit, symbol). As shown in Table 3, μ represents different subcarrier spacings. The value of μ is 0, corresponding to 15KHz, the value of μ is 1, corresponding to 30kHz, the value of μ is 2, corresponding to 60KHz, and the value of μ is 3, corresponding to 120KHz. The preparation time of PUSCH is different under different subcarrier spacings. For example, when the value of μ is 0, N2 is 10 symbols; when the value of μ is 1, N2 is 12 symbols; when the value of μ is 2, N2 is 23 symbols; when the value of μ is 3, N2 is 36 symbols.

[0166] Table 3

[0167] μ PUSCH preparation time N2 0 10 1 12 2 23 3 36

[0168] If the UE cannot prepare the data to be sent within this period of time, for example, the UE takes too long to process the concatenated data packets (i.e., aggregated data packets) and other reasons (but not limited to this reason), the uplink data packets to be sent cannot be fully prepared at the time of sending the PUSCH. In order to prevent the problem that the data cannot be sent at the start symbol due to insufficient PUSCH preparation time, the following methods can be used to solve the problem:

[0169] A. When the UE reports its capabilities, it reports the post-processing delay caused by the maximum PDCP aggregation, X symbol. The base station takes X symbol delay into account when scheduling and allocating resources.

[0170] B. Add the delay N3 generated by the aggregated data packets under different subcarrier spacings, and calculate the maximum total processing delay N. As shown in Table 4, μ represents different subcarrier spacings, and different subcarrier spacings correspond to different N2s. Different subcarrier spacings can also correspond to different N3s, and N3 can represent the delay generated by the aggregated data packets. For example, when the value of μ is 0, N3 is 5 symbols; when the value of μ is 1, N3 is 6 symbols; when the value of μ is 2, N3 is 12 symbols; when the value of μ is 3, N3 is 18 symbols. The total delay N corresponding to different subcarrier spacings is the sum of the corresponding N2 and N3.

[0171] Table 4

[0172] μ PUSCH preparation time N2 Aggregation message delay N3 Maximum total processing delay N 0 10 5 15 1 12 6 18 2 23 12 35 3 36 18 54

[0173] When PDCP performs data packet aggregation, the network device (eg, base station) may determine the location of the time domain when sending the uplink PUSCH based on the total processing delay corresponding to different subcarrier spacings when allocating uplink grant resources.

[0174] Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0175] In the several embodiments provided in this embodiment, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0176] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0177] In addition, each functional unit in each embodiment of the present embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0178] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment. The aforementioned storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, disk or optical disk and other media that can store program codes.

[0179] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A user data processing method, characterized in that: include: The terminal device receives a first configuration parameter from the network device, where the first configuration parameter includes at least one of the number of aggregated data packets N, the size of the aggregated data packet S, and the state of a resource block RB, where the number of aggregated data packets N is used to indicate that a maximum of N data packets are aggregated into one data packet, where N is an integer greater than or equal to 2, and the size of the aggregated data packet S is used to indicate that the size of the aggregated data packet does not exceed S, where S is greater than 0, and the state of the RB is used to indicate whether the RB is allowed to carry an aggregated data packet, and the first configuration parameter is used to instruct the terminal device to aggregate data packets through a packet data convergence protocol PDCP layer; The PDCP layer of the terminal device performs header compression on the data packet, and aggregates multiple header-compressed data packets according to the first configuration parameter to generate an aggregated data packet; the aggregated data packet reserves an X-bit integrity protection field and a Y-bit data packet sequence number SN field; wherein X and Y are integers greater than 0; The PDCP layer delivers the aggregated data packet to the medium access control MAC layer or the radio link control RLC layer after the data packet aggregation is completed, or The PDCP layer delivers the aggregated data packet to the MAC layer or the RLC layer according to a preset delivery period; When the RLC layer or the MAC layer processes the aggregated data packet, the PDCP layer calculates an integrity protection parameter and a SN sequence number of the aggregated data packet, and fills the integrity protection parameter and the SN sequence number into the aggregated data packet; Alternatively, the terminal device receives a first configuration parameter from the network device, the first configuration parameter including at least one of the number of aggregated data packets N, the size of the aggregated data packet S, and the state of the resource block RB, the number of aggregated data packets N is used to indicate that a maximum of N data packets are aggregated into one data packet, N is an integer greater than or equal to 2, the size of the aggregated data packet S is used to indicate that the size of the data packet after aggregation does not exceed S, S is greater than 0, the state of the RB is used to indicate whether the RB is allowed to carry the aggregated data packet, and the first configuration parameter is used to instruct the terminal device to aggregate the data packet through the service data adaptation protocol SDAP layer; The SDAP layer of the terminal device aggregates the multiple data packets according to the first configuration parameter to generate an aggregated data packet; The SDAP layer delivers the aggregated data packet to the Packet Data Convergence Protocol PDCP layer after the data packet aggregation is completed, or The SDAP layer delivers the aggregated data packet to the PDCP layer according to a preset delivery period; The PDCP layer of the terminal device performs header compression on the aggregated data packet; The PDCP layer delivers the header-compressed message to the RLC layer or the MAC layer, wherein the header-compressed message reserves an X-bit integrity protection field and a Y-bit data packet sequence number SN field; wherein X and Y are integers greater than 0; When the RLC layer or the MAC layer processes the header-compressed message, the PDCP layer calculates the integrity protection parameter and the SN sequence number of the header-compressed message, and fills the integrity protection parameter and the SN sequence number into the header-compressed message.

2. The method according to claim 1, characterized in that: The method further comprises: The terminal device receives first indication information from the network device, where the first indication information is used to instruct the MAC layer of the terminal device to perform data packet segmentation processing.

3. The method according to claim 2, characterized in that When the transport block TB resources cannot carry a packet data convergence protocol data unit PDCP PDU, the MAC layer of the terminal device performs data packet segmentation processing on the PDCP PDU; The MAC layer of the terminal device generates a sequence number SN for the segmented message, and the SN generated by the MAC layer and the SN generated by the PDCP layer for the PDCP PDU have a mapping relationship.

4. The method according to any one of claims 1 to 3, characterized in that: The first configuration parameter is included in a radio resource control RRC message or a cell handover message or a specific medium access control element MAC CE.

5. The method according to claim 1, characterized in that The method further comprises: The terminal device sends first capability information to the network device, where the first capability information is used to indicate the ability of the terminal device to aggregate data packets at the PDCP layer, and the first capability information includes at least one of the number N of aggregated data packets or the size S of the aggregated data packets.

6. The method according to claim 1, characterized in that The method further comprises: The terminal device sends second capability information to the network device, where the second capability information is used to indicate the SDAP layer aggregation data packet capability of the terminal device, and the second capability information includes at least one of the number N of the aggregated data packets or the size S of the aggregated data packets.

7. The method according to any one of claims 1 to 3, characterized in that: The ability of the terminal device to aggregate data packets is related to the type of the terminal device, and the type of the terminal device is related to the uplink rate grade UL Category of the terminal device.

8. The method according to any one of claims 1 to 3, characterized in that: The terminal device receives second indication information from the network device, where the second indication information is used to instruct the terminal device to start PDCP layer parallel preprocessing.

9. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The terminal device sends user data at intervals of n symbols at a time point when sending a physical uplink shared channel PUSCH; n is a value configured by the network device or is a fixed value; The n symbols are used to send a reference signal or a high-level control signal or information indicating a location where the network device sends user data.

10. The method according to claim 9, characterized in that The terminal device carries a high-layer message or L1 signaling on a physical uplink shared channel PUSCH, wherein the high-layer message or L1 signaling is used to instruct the network device to cancel the PUSCH uplink authorization, and the high-layer message or L1 signaling includes at least one of a scheduling request and user cached data.

11. The method according to claim 5 or 6, characterized in that: The terminal device carries the processing delay caused by data packet aggregation in the first capability information or the second capability information.

12. The method according to claim 11, characterized in that The delay N3 caused by aggregating data packets under different subcarrier spacing is increased on the terminal device side.

13. A terminal device, characterized in that: The terminal device comprises: Memory for storing computer programs; transceivers, used to receive or send radio signals; A processor, configured to execute the computer program so that the terminal device implements the method as claimed in any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program codes, and when the computer program codes are executed by a processing circuit, the method according to any one of claims 1 to 12 is implemented.

15. A chip system, characterized in that: The chip system includes a processing circuit and a storage medium, wherein the storage medium stores a computer program code; when the computer program code is executed by the processing circuit, the method according to any one of claims 1 to 12 is implemented.

16. A computer program product, characterized in that The computer program product is used to run on a computer to implement the method according to any one of claims 1 to 12.

Images