WO2020062126A1 - Method for processing data packet, entity and storage medium - Google Patents

Abstract

Disclosed are a method for processing a data packet. The method comprises: a first protocol layer entity dividing a first SDU into at least two SDU segments based on the size of the received first SDU; and the first protocol layer entity indicating that the SDU segment is a data segment of the first SDU. Also provided are another data packet processing method, an entity and a storage medium.

Description

Data packet processing method, entity and storage medium Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a data packet processing method, entity, and storage medium.

Background technique

In a wireless (New Radio, NR) Rel-15 system, the size of the largest Service Data Unit (SDU) supported by the Packet Data Convergence Protocol (PDCP) layer is 9K bytes; therefore, When the data sent from the Radio Resource Control (Radio Resource Control) (RRC) layer or the application layer to the PDCP layer exceeds the maximum SDU size supported by the PDCP layer, the data cannot be effectively transmitted.

Summary of the Invention

In order to solve the foregoing technical problems, embodiments of the present invention provide a data packet processing method, entity, and storage medium, which implements when data sent from a radio resource control RRC layer or an application layer to the PDCP layer exceeds the maximum SDU size supported by the PDCP layer. , Data can be efficiently transmitted.

According to a first aspect, an embodiment of the present invention provides a data packet processing method, including: a first protocol layer entity dividing the first SDU into at least two SDU fragments based on the size of the received first SDU; the The first protocol layer entity indicates that the SDU segment is a data segment of the first SDU.

In a second aspect, an embodiment of the present invention provides a data packet processing method, including: a first protocol layer entity receives at least two SDU fragments, and the at least two SDU fragments are data fragments obtained based on a size of the first SDU. .

According to a third aspect, an embodiment of the present invention provides a first protocol layer entity, including: a first processing unit configured to divide the first SDU into at least two SDU fragments based on a size of the received first SDU, And indicating that the SDU segment is a data segment of the first SDU.

According to a fourth aspect, an embodiment of the present invention provides a first protocol layer entity, including: a receiving unit configured to receive at least two SDU fragments, where the at least two SDU fragments are data obtained based on the size of the first SDU. Fragment.

In a fifth aspect, an embodiment of the present invention provides a first protocol layer entity, including a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to run the computer program when To execute the steps of the data packet processing method performed by the first protocol layer entity corresponding to the terminal device.

According to a sixth aspect, an embodiment of the present invention provides a first protocol layer entity, including a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to run the computer program when To execute the steps of the data packet processing method performed by the first protocol layer entity corresponding to the network device.

According to a seventh aspect, an embodiment of the present invention provides a storage medium that stores an executable program. When the executable program is executed by a processor, the data packet processing method performed by the first protocol layer entity corresponding to the network device is implemented.

According to an eighth aspect, an embodiment of the present invention provides a storage medium that stores an executable program. When the executable program is executed by a processor, the data packet processing method performed by the first protocol layer entity corresponding to the network device is implemented.

In the data packet processing method provided by the embodiment of the present invention, a first negotiation layer entity corresponding to a terminal device side divides the first SDU into at least two SDU fragments based on the size of the received first SDU. The SDU is divided into at least two SDU segments, so that data transmission is not limited by the maximum data that the protocol layer can support for transmission, and effective data transmission is achieved.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a protocol stack in related technologies;

2 is a schematic structural diagram of a communication system according to an embodiment of the present invention;

3 is a schematic diagram of an optional processing flow of a data packet processing method according to an embodiment of the present invention;

4 is a schematic diagram of a position of an SDU fragment on a first SDU according to an embodiment of the present invention;

5 is a schematic diagram of an optional processing flow of another data packet processing method according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a composition structure of a first protocol layer entity according to an embodiment of the present invention; FIG.

FIG. 7 is a schematic diagram of a composition structure of another first protocol layer entity according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic diagram of a hardware composition structure of a first protocol layer entity according to an embodiment of the present invention.

detailed description

In order to understand the features and technical contents of the embodiments of the present invention in more detail, the implementation of the embodiments of the present invention is described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference only and are not intended to limit the embodiments of the present invention.

Before describing the embodiments of the present invention in detail, the protocol stack for data transmission is briefly described. As shown in FIG. 1, on the terminal device side and on the network device side, the protocol stack is business data in order from the top to the bottom according to the layer relationship. Aggregation Protocol (Service Data Adaptation Protocol, SDAP) layer, PDCP layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer and Physical (PHY) layer, The layer relationship is: the SDAP layer is the upper layer of the PDCP layer, the PDCP layer is the upper layer of the RLC layer, the RLC layer is the upper layer of the MAC layer, and the MAC layer is the upper layer of the PHY layer. Correspondingly, a protocol layer has a corresponding relationship between the network device side and the terminal device side.

Based on the above problems, the present invention provides a data packet processing method. The data packet processing method in the embodiment of the present application can be applied to various communication systems, such as a Global System of Mobile (GSM) system and multiple code divisions. Address (Code Division Multiple Access) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system , LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access, WiMAX) communication system or 5G system.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 2. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or a communication terminal or a terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located within the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system. (Evolutional NodeB, eNB or eNodeB), or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switching center, relay station, access point, vehicle equipment, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in public land mobile networks (PLMN) that will evolve in the future.

The communication system 100 further includes at least one terminal device 120 located within a coverage area of the network device 110. As the "terminal equipment" used herein includes, but is not limited to, connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection ; And / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) devices. A terminal device configured to communicate through a wireless interface may be referred to as a “wireless communication terminal”, a “wireless terminal”, or a “mobile terminal”. Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications systems (PCS) terminals that can combine cellular radiotelephones with data processing, facsimile, and data communications capabilities; can include radiotelephones, pagers, Internet / internal PDA with network access, web browser, notepad, calendar, and / or Global Positioning System (GPS) receiver; and conventional laptop and / or palm-type receivers or others including radiotelephone transceivers Electronic device. A terminal device can refer to an access terminal, user equipment (User Equipment), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or User device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Processing (PDA), and wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved PLMNs, etc.

Optionally, terminal devices 120 may perform terminal direct device (D2D) communication.

Optionally, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

FIG. 2 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like in this embodiment of the present application is not limited thereto.

It should be understood that the device having a communication function in the network / system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in FIG. 2 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be specific devices described above, and are not repeated here. The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobile management entity, and the like, which is not limited in the embodiments of the present application.

An optional processing flow of a data packet processing method provided by an embodiment of the present invention, as shown in FIG. 3, includes the following steps:

Step S201: The first protocol layer entity divides the first SDU into at least two SDU fragments based on the size of the received first SDU.

In the embodiment of the present invention, the first SDU may be sent by the RRC layer to the first protocol layer entity, or may be sent by the application layer to the first protocol layer entity.

In some embodiments, when the size of the first SDU is greater than a first threshold, the first protocol layer entity cuts the first SDU into at least two SDU fragments. When the first SDU is segmented, when the size of the first SDU is an integer multiple of the first threshold, the size of each SDU segment in at least two SDU segments after the first SDU is segmented Are both equal to the first threshold. When segmenting the first SDU, when the size of the first SDU is not an integer multiple of the first threshold, the size of the last SDU segment of the at least two SDU segments is smaller than the first threshold, The size of SDU fragments other than the last SDU fragment is equal to the first threshold. Alternatively, when the size of the first SDU is not an integer multiple of the first threshold, the first SDU is equally divided, and the size of each SDU segment obtained by the division is equal, and the size of each SDU segment Less than the first threshold.

In the embodiment of the present invention, the first threshold value is a maximum value of data that the first protocol layer can support for transmission. Optionally, the first threshold value is a maximum value of a data size that can be supported by the PDCP layer, such as 9K bytes.

In some embodiments, the at least two SDU fragments each include a corresponding header of a first protocol layer, and the header of the first protocol layer includes: first indication information, where the first indication information is used to indicate the following At least one of:

The position of the SDU segment in the first SDU, and the first byte of the SDU segment correspond to the position and serial (SN) number in the first SDU.

Here, the position of the SDU segment in the first SDU refers to the SDU segment in the front, middle, or rear of the first SDU. Taking the first SDU segmented into four SDU segments as an example, the position of the SDU segment on the first SDU is shown in FIG. 4. The first SDU segment is located at the front of the first SDU, the second SDU segment and the third SDU segment. The SDU segment is located in the middle of the first SDU, and the fourth SDU segment is located in the rear of the first SDU. It can be understood that the front part of the first SDU refers to the first byte of the first SDU.

The SN number corresponding to each SDU segment in the at least two SDU segments segmented by the first SDU segment may be the same or different. When the SN number corresponding to each SDU segment in at least two SDU segments is different, the header of each SDU segment includes: second indication information, where the second indication information is used to indicate an SDU to which the SDU segment belongs; that is, The second indication information indicates from which SDU the SDU segment is obtained.

In the embodiment of the present invention, the first protocol layer is a PDCP layer or an SDAP layer, or a third protocol layer located above the PDCP layer and below the SDAP layer, or a fourth layer located above the SDAP layer. Protocol layer. Here, the third protocol layer and the fourth protocol layer may be new protocol layers other than the existing protocol layers in the related art.

Based on the fact that the first protocol layer is a different layer, the first protocol layer entities in the embodiments of the present invention have different functions. The following description uses the first protocol layer as the PDCP layer and the first protocol layer as the layers above the PDCP layer as examples for illustration.

When the first protocol layer is the PDCP layer, the first protocol layer entity performs header compression processing on the SDU segment corresponding to the first data segment of the first SDU. Here, the first data segment of the first SDU is located at the front of the first SDU. Taking FIG. 4 as an example, the first SDU segment is the first data segment of the first SDU. Optionally, the first protocol layer entity further caches the at least two SDU fragments, and receives a discard timer configured by a higher layer, and when the discardTimer reaches a preset time value, the cache is cached. The at least two SDU fragments are processed for packet loss; optionally, after the first at least two SDU fragments are buffered, the discardTimer is not started. Here, the discardTimer is a short value, which may be different from the discardTimer existing in the related art.

When the first protocol layer is a layer above the PDCP layer, for example, the first protocol layer is an SDAP layer, or a third protocol layer located above the PDCP layer, below the SDAP layer, or above the SDAP layer The fourth protocol layer of the first protocol layer entity, the first protocol layer entity carries third instruction information in the header of the first PDU, and the third instruction information is used to instruct the PDCP layer to determine whether to perform header compression or decompression of the first PDU. Compression processing; the first PDU includes a data segment of the first SDU; the first PDU is formed by adding a header of the first protocol layer to the first SDU. Here, the first PDU includes a data segment of the first SDU, and the first PDU is formed by adding a header of the first protocol layer to the first SDU.

In the embodiment of the present invention, the first protocol layer entity further indicates that the SDU segment is a data segment of the first SDU. In specific implementation, the instruction can be indicated in the header of the first protocol layer corresponding to the SDU fragment; or when the first protocol layer entity transmits the SDU fragment to the protocol layer below the first protocol layer, it is signaled. Give instructions.

It should be noted that the first protocol layer entity involved in the embodiment of the present invention corresponds to the first protocol layer entity on the terminal device side.

An embodiment of the present invention also provides another data packet processing method. As shown in FIG. 5, the optional processing flow of the data packet processing method includes:

In step S301, the first protocol layer entity receives at least two SDU fragments, where the at least two SDU fragments are data fragments obtained based on the size of the first SDU.

In the embodiment of the present invention, when the size of the first SDU is greater than a first threshold, the first protocol layer entity divides the first SDU into at least two SDU fragments. When the first SDU is segmented, when the size of the first SDU is an integer multiple of the first threshold, the size of each SDU segment in at least two SDU segments after the first SDU is segmented Are both equal to the first threshold. When segmenting the first SDU, when the size of the first SDU is not an integer multiple of the first threshold, the size of the last SDU segment of the at least two SDU segments is smaller than the first threshold, The size of SDU fragments other than the last SDU fragment is equal to the first threshold. Alternatively, when the size of the first SDU is not an integer multiple of the first threshold, the first SDU is equally divided, and the size of each SDU segment obtained by the division is equal, and the size of each SDU segment Less than the first threshold.

In the embodiment of the present invention, the first threshold value is a maximum value of data that the first protocol layer can support for transmission. Optionally, the first threshold value is a maximum value of a data size that can be supported by the PDCP layer, such as 9K bytes.

In some optional embodiments, the method further includes:

Step S302, the first protocol layer entity determines that the second SDU segment in the at least two SDU segments is the first based on the header of the first protocol layer corresponding to each SDU segment in the at least two SDU segments. When the first data segment of the SDU, the first protocol layer entity performs a header decompression process on the second SDU segment.

Here, the header of the first protocol layer corresponding to each SDU segment includes: first indication information, where the first indication information is used to indicate at least one of: a position of an SDU segment in the first SDU, The first bit of the SDU segment corresponds to the position and the SN number in the first SDU.

In specific implementation, the SN numbers corresponding to each SDU segment may be the same or different; when the SN numbers corresponding to each SDU segment in at least two SDU segments are different, each of the at least two SDU segments The header of the SDU segment includes: second indication information; the second indication information is used to indicate the SDU to which the SDU segment belongs; and through the second indication information, the network device can determine each SDU segment after SDU segmentation. Each SDU fragment obtains an SDU. Accordingly, the method further includes:

Step S303: The first protocol layer entity combines the at least two SDU fragments to obtain the first SDU.

It should be noted that the first protocol layer entity involved in the embodiment of the present invention corresponds to the first protocol layer entity on the network device side.

An embodiment of the present invention further provides a first protocol layer entity. The composition structure of the first protocol layer entity 400, as shown in FIG. 6, includes:

The first processing unit 401 is configured to slice the first SDU into at least two SDU segments based on the size of the received first SDU, and instruct the SDU segment to be a data segment of the first SDU.

In some embodiments, a size of each SDU segment in the at least two SDU segments is equal to the first threshold;

Alternatively, a size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, and among the at least two SDU fragments, an SDU fragment other than the first SDU fragment is equal in size, and each The size of each SDU segment is less than or equal to the first threshold.

In some embodiments, each of the at least two SDU fragments includes a header of a corresponding first protocol layer;

The header of the first protocol layer includes: first indication information, where the first indication information is used to indicate at least one of: a position of an SDU segment in the first SDU, and a first of the SDU segment The byte corresponds to the position and the SN number in the first SDU.

In some embodiments, each SDU segment corresponding to the at least two SDU segments has the same SN number, or each SDU segment corresponding to the at least two SDU segments has a different SN number.

When the SN numbers corresponding to each SDU segment in the at least two SDU segments are different, the header of each SDU segment in the at least two SDU segments includes: second indication information; the second indication information is used for To indicate the SDU to which the SDU segment belongs.

In some embodiments, the first protocol layer entity further includes:

The sending unit 402 is configured to deliver at least two SDU fragments with a header of the first protocol layer to a second protocol layer entity; the second protocol layer is a lower layer of the first protocol layer.

In some embodiments, the first protocol layer includes: a PDCP layer, or an SDAP layer, or a third protocol layer located above the PDCP layer and below the SDAP layer, or located between the SDAP layer The fourth protocol layer.

In some embodiments, the first protocol layer is a PDCP layer, and when the second SDU segment of the at least two SDU segments is the first data segment of the first SDU, the first processing unit 401, configured to perform header compression processing on the second SDU segment;

When the third SDU segment of the at least two SDU segments is not the first data segment of the first SDU, the processing unit is configured to not perform header compression processing on the third SDU segment.

In some embodiments, the first processing unit 401 is configured to perform compression processing on a header of the second SDU segment.

In some embodiments, when the first protocol layer is a PDCP layer, the first processing unit 401 is further configured to start a packet loss timer, where the packet loss timer is used by the first protocol entity for the At least two SDU fragments perform packet loss processing; or the first processing unit 401 is configured not to start a packet loss timer.

In some embodiments, the first processing unit 401 is further configured to receive a packet loss timer configured by a higher layer.

In some embodiments, the first protocol layer entity further includes: a storage unit 403 configured to cache the at least two SDU fragments.

In some embodiments, the first protocol layer is an SDAP layer, or a third protocol layer located above the PDCP layer, below the SDAP layer, or a fourth protocol layer located above the SDAP layer Time,

The first processing unit 401 is further configured to carry third instruction information in a header of the first PDU, where the third instruction information is used to instruct a PDCP layer to determine whether to perform header compression or decompression of the first PDU; The first PDU includes a data segment of the first SDU; the first PDU is formed by adding a header of the first protocol layer to the first SDU.

In some embodiments, the first SDU is user plane data or control plane data.

It should be noted that the first protocol layer entity involved in the embodiment of the present invention corresponds to the first protocol layer entity on the terminal device side.

An embodiment of the present invention also provides another first protocol layer entity. The composition structure of the first protocol layer entity 500, as shown in FIG. 7, includes:

The receiving unit 501 is configured to receive at least two SDU fragments, where the at least two SDU fragments are data fragments obtained based on the size of the first SDU.

In some embodiments, the size of each SDU segment in the at least two SDU segments is equal, and the size of each SDU segment is less than or equal to the first threshold;

Alternatively, a size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, and among the at least two SDU fragments, a size of an SDU fragment other than the first SDU fragment is equal to the size First threshold.

In some embodiments, the first protocol layer entity further includes:

The second processing unit 502 is configured to determine, based on a header of a first protocol layer corresponding to each SDU segment of the at least two SDU segments, that the second SDU segment of the at least two SDU segments is the first When the first data segment of the SDU, the first protocol layer entity performs a header decompression process on the second SDU segment.

In some embodiments, the second processing unit is configured to perform a merge process on the at least two SDU fragments to obtain the first SDU.

In some embodiments, the header of the first protocol layer corresponding to each of the at least two SDU fragments includes: first indication information, where the first indication information is used to indicate at least one of the following :

The position of the SDU segment in the first SDU, and the first bit of the SDU segment corresponds to the position and SN number in the first SDU.

In some embodiments, the SN number corresponding to each SDU segment in the at least two SDU segments is the same or different.

When the SN numbers corresponding to each SDU segment in the at least two SDU segments are different, the header of each SDU segment in the at least two SDU segments includes: second indication information; the second indication information is used to indicate The SDU to which the SDU fragment belongs.

In some embodiments, the first protocol layer includes: a PDCP layer, or an SDAP layer, or a third protocol layer located above the PDCP layer and below the SDAP layer, or located between the SDAP layer The fourth protocol layer.

It should be noted that the first protocol layer entity involved in the embodiment of the present invention corresponds to the first protocol layer entity on the network device side.

An embodiment of the invention also provides a first protocol layer entity, including a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the terminal device when the computer program is run. Steps of a power allocation method performed.

An embodiment of the present invention further provides another first protocol layer entity, including a processor and a memory for storing a computer program capable of running on the processor, wherein the processor executes the foregoing when the computer program is run. Steps of a power allocation method performed by a network device.

FIG. 8 is a schematic diagram of a hardware composition structure of a first protocol layer entity according to an embodiment of the present invention. The first protocol layer entity 700 includes: at least one processor 701, a memory 702, and at least one network interface 704. The components in the first protocol layer entity 700 are coupled together through a bus system 705. It can be understood that the bus system 705 is configured to implement connection and communication between these components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are marked as the bus system 705 in FIG. 8.

It can be understood that the memory 702 may be a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. Among them, the non-volatile memory may be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), electrically erasable and programmable memory Programmable read-only memory (EEPROM, Electrically Programmable Read-Only Memory), magnetic random access memory (FRAM, ferromagnetic random access memory), flash memory (Flash memory), magnetic surface memory, optical disc, or read-only disc (CD) -ROM, Compact Disc-Read-Only Memory); magnetic surface storage can be magnetic disk storage or magnetic tape storage. The volatile memory may be random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM, Static Random Access Memory), Synchronous Static Random Access Memory (SSRAM, Static Random Access, Memory), Dynamic Random Access DRAM (Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), enhanced Type Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Random Dynamic Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Access Memory) ). The memory 702 described in embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

The memory 702 in the embodiment of the present invention is configured to store various types of data to support the operation of the first protocol layer entity 700. Examples of such data include: any computer program, such as application program 7022, for operating on the first protocol layer entity 700. A program for implementing the method of the embodiment of the present invention may be included in an application program 7022.

The method disclosed in the foregoing embodiment of the present invention may be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip and has a signal processing capability. In the implementation process, each step of the above method may be completed by using hardware integrated logic circuits or instructions in the form of software in the processor 701. The above-mentioned processor 701 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor 701 may implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in combination with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium. The storage medium is located in the memory 702. The processor 701 reads the information in the memory 702 and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the first protocol layer entity 700 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic A device (CPLD, Complex Programmable Logic Device), FPGA, general-purpose processor, controller, MCU, MPU, or other electronic component is implemented to perform the foregoing method.

An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application. For simplicity, here No longer.

Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the terminal device in each method of the embodiments of the present application. For simplicity, here No longer.

The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, so that the instructions generated by the processor of the computer or other programmable data processing device are used to generate instructions Means for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions The device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

The above description is only the preferred embodiments of the present invention, and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention shall be included in Within the scope of the present invention.

Claims (48)

A data packet processing method, the method includes: The first protocol layer entity divides the first SDU into at least two SDU fragments based on the size of the received first service data unit SDU; The first protocol layer entity indicates that the SDU segment is a data segment of the first SDU. The method according to claim 1, wherein the first protocol layer entity divides the first SDU into at least two SDU fragments based on the size of the received first SDU, comprising: When the size of the first SDU is greater than a first threshold, the first protocol layer entity cuts the first SDU into at least two SDU fragments; The size of each of the at least two SDU fragments is equal, and the size of each SDU fragment is less than or equal to the first threshold; Alternatively, a size of a first SDU fragment of the at least two SDU fragments is smaller than the first threshold, and among the at least two SDU fragments, a size of an SDU fragment other than the first SDU fragment is equal to The first threshold is described. The method according to claim 1 or 2, wherein each of the at least two SDU fragments includes a header of a corresponding first protocol layer; The header of the first protocol layer includes: first indication information, where the first indication information is used to indicate at least one of the following: A position of an SDU fragment in the first SDU; The first byte of the SDU segment corresponds to the position in the first SDU; Serial SN number. The method according to claim 3, wherein each SDU segment in the at least two SDU segments has the same SN number; Or, the SN numbers corresponding to each SDU segment in the at least two SDU segments are different. The method according to claim 4, wherein when the SN numbers corresponding to each of the at least two SDU segments are different, The header of each SDU segment in the at least two SDU segments includes: second indication information; The second indication information is used to indicate an SDU to which the SDU segment belongs. The method according to any one of claims 1 to 5, wherein the method further comprises: The first protocol layer entity submits at least two SDU fragments with the header of the first protocol layer added to the second protocol layer entity; The second protocol layer is a lower layer of the first protocol layer. The method according to any one of claims 1 to 6, wherein the first protocol layer comprises: PDCP layer of packet data convergence protocol; Or, the SDAP layer of the service data convergence protocol; Or a third protocol layer located above the PDCP layer and below the SDAP layer; Or, a fourth protocol layer located above the SDAP layer. The method according to any one of claims 1 to 7, wherein when the first protocol layer is a packet data convergence protocol PDCP layer, the method further comprises: When the second SDU segment of the at least two SDU segments is the first data segment of the first SDU, the first protocol layer entity performs header compression processing on the second SDU segment; When the third SDU segment of the at least two SDU segments is not the first data segment of the first SDU, the first protocol layer entity does not perform header compression processing on the third SDU segment. The method according to claim 8, wherein the first protocol layer entity performing header compression processing on the second SDU segment comprises: The first protocol layer entity performs compression processing on a header of the second SDU fragment. The method according to any one of claims 1 to 9, wherein when the first protocol layer is a packet data convergence protocol PDCP layer, the method further comprises: The first protocol layer entity starts a packet loss timer, and the packet loss timer is used by the first protocol entity to perform packet loss processing on the at least two SDU fragments; Or the first protocol layer entity does not start a packet loss timer. The method according to claim 10, wherein the method further comprises: The first protocol layer entity receives a packet loss timer configured by a higher layer. The method according to claim 10, wherein before the first protocol layer entity starts a packet loss timer, the method further comprises: The first protocol layer entity buffers the at least two SDU fragments. The method according to any one of claims 1 to 7, wherein the first protocol layer is a service data convergence protocol SDAP layer, or a third protocol layer located above the PDCP layer and below the SDAP layer Or when the fourth protocol layer is above the SDAP layer, the method further includes: The first protocol layer entity carries third indication information in a header of the first PDU, and the third indication information is used to instruct a PDCP layer of the packet data convergence protocol to determine whether to perform header compression or decompression processing on the first PDU; The first PDU includes a data segment of the first SDU, and the first PDU is formed by adding a header of the first protocol layer to the first SDU. The method according to any one of claims 1 to 13, wherein the first SDU is user plane data; Alternatively, the first SDU is control plane data. A data packet processing method, the method includes: The first protocol layer entity receives at least two service data unit SDU fragments, and the at least two SDU fragments are data fragments obtained based on the size of the first SDU. The method according to claim 15, wherein the size of each SDU segment in the at least two SDU segments is equal, and the size of each SDU segment is less than or equal to the first threshold; Alternatively, a size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, and among the at least two SDU fragments, a size of an SDU fragment other than the first SDU fragment is equal to the size First threshold. The method according to claim 15 or 16, further comprising: Determining, by the first protocol layer entity, that a second SDU segment in the at least two SDU segments is the first SDU based on a header of a first protocol layer corresponding to each SDU segment in the at least two SDU segments When the first data segment is the first data segment, the first protocol layer entity performs a header decompression process on the second SDU segment. The method according to claim 17, wherein after the header decompression processing is performed on the second SDU segment, the method further comprises: Merging the at least two SDU fragments to obtain the first SDU. The method according to any one of claims 15 to 18, wherein a header of a first protocol layer corresponding to each SDU segment of the at least two SDU segments comprises: first indication information, the first indication information Used to indicate at least one of the following: A position of an SDU fragment in the first SDU; The first bit of the SDU segment corresponds to the position in the first SDU; Serial SN number. The method according to claim 19, wherein each SDU segment in the at least two SDU segments has the same SN number; Or, the SN numbers corresponding to each SDU segment in the at least two SDU segments are different. The method according to claim 20, wherein when each SDU segment corresponding to the at least two SDU segments has a different SN number, The header of each SDU segment in the at least two SDU segments includes: second indication information; The second indication information is used to indicate an SDU to which the SDU segment belongs. The method according to any one of claims 15 to 21, wherein the first protocol layer comprises: PDCP layer of packet data convergence protocol; Or, the SDAP layer of the service data convergence protocol; Or a third protocol layer located above the PDCP layer and below the SDAP layer; Or, a fourth protocol layer located above the SDAP layer. The first protocol layer entity includes a first processing unit configured to divide the first SDU into at least two SDU fragments based on the size of the received first service data unit SDU, and instruct the SDU fragments to be A data segment of the first SDU is described. The first protocol layer entity according to claim 23, wherein the first processing unit is configured to, when the size of the first SDU is greater than a first threshold, the first protocol layer entity SDU is divided into at least two SDU fragments; The size of each of the at least two SDU fragments is equal, and the size of each SDU fragment is less than or equal to the first threshold; Alternatively, a size of a first SDU fragment of the at least two SDU fragments is smaller than the first threshold, and among the at least two SDU fragments, a size of an SDU fragment other than the first SDU fragment is equal to The first threshold is described. The first protocol layer entity according to claim 23 or 24, wherein each of the at least two SDU fragments includes a corresponding first protocol layer header; The header of the first protocol layer includes: first indication information, where the first indication information is used to indicate at least one of the following: A position of an SDU fragment in the first SDU; The first byte of the SDU segment corresponds to the position in the first SDU; Serial SN number. The first protocol layer entity according to claim 25, wherein each SDU segment in the at least two SDU segments has the same SN number; Or, the SN numbers corresponding to each SDU segment in the at least two SDU segments are different. The first protocol layer entity according to claim 26, when the SN numbers corresponding to each of the at least two SDU fragments are different, The header of each SDU segment in the at least two SDU segments includes: second indication information; The second indication information is used to indicate an SDU to which the SDU segment belongs. The first protocol layer entity according to any one of claims 23 to 27, wherein the first protocol layer entity further comprises: A sending unit configured to deliver at least two SDU fragments to which a header of the first protocol layer is added to a second protocol layer entity; The second protocol layer is a lower layer of the first protocol layer. The first protocol layer entity according to any one of claims 23 to 28, wherein the first protocol layer comprises: PDCP layer of packet data convergence protocol; Or, the SDAP layer of the service data convergence protocol; Or a third protocol layer located above the PDCP layer and below the SDAP layer; Or, a fourth protocol layer located above the SDAP layer. The first protocol layer entity according to any one of claims 23 to 29, wherein the first protocol layer is a packet data convergence protocol PDCP layer, and when the second SDU segment of the at least two SDU segments is When the first data segment of the first SDU is described, the first processing unit is configured to perform header compression processing on the second SDU segment; When the third SDU segment of the at least two SDU segments is not the first data segment of the first SDU, the processing unit is configured to not perform header compression processing on the third SDU segment. The first protocol layer entity according to claim 30, wherein the first processing unit is configured to perform compression processing on a header of the second SDU fragment. The first protocol layer entity according to any one of claims 23 to 31, wherein when the first protocol layer is a packet data convergence protocol PDCP layer, the first processing unit is further configured to start a packet loss timer The packet loss timer is used by the first protocol entity to perform packet loss processing on the at least two SDU fragments; Alternatively, the first processing unit is configured not to start a packet loss timer. The first protocol layer entity according to claim 32, wherein the first processing unit is further configured to receive a packet loss timer configured by a higher layer. The first protocol layer entity according to claim 32, wherein the first protocol layer entity further comprises: A storage unit configured to cache the at least two SDU fragments. The first protocol layer entity according to any one of claims 23 to 29, wherein the first protocol layer is a service data convergence protocol (SDAP) layer, or is located above the PDCP layer and below the SDAP layer When the third protocol layer or the fourth protocol layer located above the SDAP layer, The first processing unit is further configured to carry third instruction information in a header of the first PDU, where the third instruction information is used to instruct a PDCP layer of the packet data convergence protocol to determine whether to perform header compression or decompression of the first PDU. Compression; the first PDU includes a data segment of the first SDU; the first PDU is formed by the first SDU adding a header of the first protocol layer. The first protocol layer entity according to any one of claims 23 to 35, wherein the first SDU is user plane data; Alternatively, the first SDU is control plane data. The first protocol layer entity includes: The receiving unit is configured to receive at least two service data unit SDU fragments, where the at least two SDU fragments are data fragments obtained based on the size of the first SDU. The first protocol layer entity according to claim 37, wherein each SDU segment of the at least two SDU segments is equal in size, and the size of each SDU segment is less than or equal to the first threshold; Alternatively, a size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, and among the at least two SDU fragments, a size of an SDU fragment other than the first SDU fragment is equal to the size First threshold. The first protocol layer entity according to claim 37 or 38, wherein the first protocol layer entity further comprises: A second processing unit configured to determine a second SDU segment in the at least two SDU segments as the first SDU based on a header of a first protocol layer corresponding to each SDU segment in the at least two SDU segments When the first data segment is the first data segment, the first protocol layer entity performs a header decompression process on the second SDU segment. The first protocol layer entity according to claim 39, wherein: The second processing unit is configured to perform a merge process on the at least two SDU fragments to obtain the first SDU. The first protocol layer entity according to any one of claims 37 to 40, wherein a header of a first protocol layer corresponding to each SDU segment of the at least two SDU segments includes: first indication information, the The first instruction information is used to indicate at least one of the following: A position of an SDU fragment in the first SDU; The first bit of the SDU segment corresponds to the position in the first SDU; Serial SN number. The first protocol layer entity according to claim 41, wherein each SDU segment corresponding to the at least two SDU segments has the same SN number; Or, the SN numbers corresponding to each SDU segment in the at least two SDU segments are different. The first protocol layer entity according to claim 42, wherein when the SN numbers corresponding to each of the at least two SDU fragments are different, The header of each SDU segment in the at least two SDU segments includes: second indication information; The second indication information is used to indicate an SDU to which the SDU segment belongs. The first protocol layer entity according to any one of claims 37 to 43, wherein the first protocol layer comprises: PDCP layer of packet data convergence protocol; Or, the SDAP layer of the service data convergence protocol; Or a third protocol layer located above the PDCP layer and below the SDAP layer; Or, a fourth protocol layer located above the SDAP layer. The first protocol layer entity includes a processor and a memory for storing a computer program capable of running on the processor, where: When the processor is used to run the computer program, execute the steps of the data packet processing method according to any one of claims 1 to 14. The first protocol layer entity includes a processor and a memory for storing a computer program capable of running on the processor, where: When the processor is used to run the computer program, execute the steps of the data packet processing method according to any one of claims 15 to 22. A storage medium stores an executable program, and when the executable program is executed by a processor, the data packet processing method according to any one of claims 1 to 14 is implemented. A storage medium stores an executable program, and when the executable program is executed by a processor, the data packet processing method according to any one of claims 15 to 22 is implemented.

Images