CN111886893B - Data packet processing method, entity and storage medium - Google Patents

Data packet processing method, entity and storage medium Download PDF

Info

Publication number
CN111886893B
CN111886893B CN201880091259.8A CN201880091259A CN111886893B CN 111886893 B CN111886893 B CN 111886893B CN 201880091259 A CN201880091259 A CN 201880091259A CN 111886893 B CN111886893 B CN 111886893B
Authority
CN
China
Prior art keywords
sdu
protocol layer
fragments
layer
protocol
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201880091259.8A
Other languages
Chinese (zh)
Other versions
CN111886893A (en
Inventor
石聪
杨宁
刘建华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN111886893A publication Critical patent/CN111886893A/en
Application granted granted Critical
Publication of CN111886893B publication Critical patent/CN111886893B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control

Landscapes

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

Abstract

The invention discloses a data packet processing method, which comprises the following steps: a first protocol layer entity segments a first SDU into at least two SDU segments based on the size of the received first SDU; the first protocol layer entity indicates the SDU segment as a data segment of the first SDU. The embodiment of the invention also provides 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, an entity, and a storage medium.
Background
In a wireless (New Radio, NR) Rel-15 system, the size of a maximum Service Data Unit (SDU) that a Packet Data Convergence Protocol (PDCP) layer can support is 9 kbytes; therefore, when data transmitted from a Radio Resource Control (RRC) layer or an application layer to the PDCP layer exceeds the size of the maximum SDU supported by the PDCP layer, the data cannot be efficiently transmitted.
Disclosure of Invention
In order to solve the foregoing technical problem, embodiments of the present invention provide a data packet processing method, an entity, and a storage medium, which enable effective transmission of data when the size of data sent from a radio resource control RRC layer or an application layer to a PDCP layer exceeds the maximum SDU size supported by the PDCP layer.
In a first aspect, an embodiment of the present invention provides a data packet processing method, including: a first protocol layer entity segments a first SDU into at least two SDU segments based on the size of the received first SDU; the first protocol layer entity indicates the SDU segment as a data segment of the first SDU.
In a second aspect, an embodiment of the present invention provides a data packet processing method, including: the first protocol layer entity receives at least two SDU fragments which are data fragments obtained by segmentation based on the size of the first SDU.
In a third aspect, an embodiment of the present invention provides a first protocol layer entity, including: the first processing unit is configured to segment the first SDU into at least two SDU segments based on the size of the received first SDU, and indicate that the SDU segment is a data segment of the first SDU.
In a fourth aspect, an embodiment of the present invention provides a first protocol layer entity, including: the receiving unit is configured to receive at least two SDU segments, which are data segments obtained by segmentation based on the size of the first SDU.
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 operable on the processor, wherein the processor is configured to execute the steps of the above-described packet processing method corresponding to the first protocol layer entity of the terminal device when executing the computer program.
In 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 operable on the processor, wherein the processor is configured to execute the steps of the packet processing method described above corresponding to the first protocol layer entity of the network device when executing the computer program.
In a seventh aspect, an embodiment of the present invention provides a storage medium, where an executable program is stored, and when the executable program is executed by a processor, the method for processing a data packet performed by a first protocol layer entity corresponding to a network device is implemented.
In an eighth aspect, an embodiment of the present invention provides a storage medium, which stores an executable program, and when the executable program is executed by a processor, the storage medium implements the above-mentioned packet processing method executed by a first protocol layer entity corresponding to a network device.
In the data packet processing method provided in the embodiment of the present invention, the first conference layer entity corresponding to the terminal device side segments the first SDU into at least two SDU segments based on the size of the received first SDU, and thus, by dividing the SDU into at least two SDU segments, the transmission of data is not limited by the maximum data that can be supported and transmitted by the protocol layer, and effective transmission of data is achieved.
Drawings
FIG. 1 is a diagram illustrating a protocol stack in the related art;
FIG. 2 is a schematic diagram of a communication system according to an embodiment of the present invention;
fig. 3 is a schematic view of an alternative processing flow of a data packet processing method according to an embodiment of the present invention;
fig. 4 is a diagram illustrating a position of an SDU fragment in a first SDU according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an alternative processing flow of another data packet processing method according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a first protocol layer entity according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another first protocol layer entity according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a hardware component structure of a first protocol layer entity according to an embodiment of the present invention.
Detailed Description
So that the manner in which the features and technical contents of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the present invention will be rendered by reference to the appended drawings, which are included for purposes of illustration and not limitation.
Before the embodiments of the present invention are explained in detail, a Protocol stack for Data transmission is briefly explained, as shown in fig. 1, at a terminal device side and at a network device side, the Protocol stack sequentially includes, from top to bottom according to a layer relationship, a Service Data Attachment Protocol (SDAP) layer, a PDCP layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer, where 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, one protocol layer has a corresponding relationship between the network device side and the terminal device side.
In view of the foregoing problems, the present invention provides a data packet processing method, and the data packet processing method according to the embodiment of the present invention can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.
For example, a 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 referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Alternatively, the Network device 110 may be a Base Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or a Network device in a Mobile switching center, a relay, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.
The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., for a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.
Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.
Alternatively, 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, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.
Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that a device having a communication function in a 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 the specific devices described above, which are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
As shown in fig. 3, an optional processing flow of the data packet processing method provided in the embodiment of the present invention includes the following steps:
in step S201, the first protocol layer entity segments the first SDU into at least two SDU segments based on the size of the received first SDU.
In this embodiment of the present invention, the first SDU may be sent from the RRC layer to the first protocol layer entity, or may be sent from the application layer to the first protocol layer entity.
In some embodiments, the first protocol layer entity slices the first SDU into at least two SDU fragments when the size of the first SDU is greater than a first threshold. When segmenting a first SDU, when the size of the first SDU is an integral multiple of a first threshold value, the size of each SDU segment in at least two SDU segments after segmenting the first SDU is equal to the first threshold value. When segmenting a first SDU, when the size of the first SDU is not an integral multiple of a first threshold value, the size of the last SDU segment in the at least two SDU segments is smaller than the first threshold value, and the sizes of the SDU segments except the last SDU segment are equal to the first threshold value. Or when the size of the first SDU is not an integral multiple of a first threshold, performing equivalent segmentation on the first SDU, wherein the size of each SDU fragment obtained by segmentation is equal, and the size of each SDU fragment is smaller than the first threshold.
In this embodiment of the present invention, the first threshold is a maximum value of data that the first protocol layer can support transmission. Optionally, the first threshold is a maximum value of a data size that the PDCP layer can support, such as 9 kbytes.
In some embodiments, the at least two SDU fragments each comprise a corresponding header of a first protocol layer, the header of the first protocol layer comprising: first indication information indicating at least one of:
the position of the SDU fragment in the first SDU, and the first byte of the SDU fragment correspond to the position and Sequence Number (SN) in the first SDU.
Here, the position of the SDU fragment in the first SDU means that the SDU fragment is in the front, middle or rear of the first SDU. Taking the example of segmenting the first SDU into 4 SDU segments, the position of the SDU segment in the first SDU is schematically illustrated, as 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 are located at the middle of the first SDU, and the fourth SDU segment is located at the rear of the first SDU. It is to be understood that the front portion of the first SDU refers to the first byte of the first SDU.
The SN numbers corresponding to each of the at least two SDU fragments into which the first SDU fragment is sliced may be the same or different. When the SN number corresponding to each of the at least two SDU fragments is different, the header of each SDU fragment includes: second indication information, where the second indication information is used to indicate an SDU to which the SDU fragment belongs; i.e. the second indication information indicates from which SDU fragment the SDU fragment was fragmented.
In the embodiment of the invention, the first protocol layer is a PDCP layer, or an SDAP layer, or a third protocol layer positioned above the PDCP layer, below the SDAP layer, or a fourth protocol layer positioned above the SDAP layer. Here, the third protocol layer and the fourth protocol layer may be new protocol layers other than existing protocol layers in the related art.
Based on the first protocol layer being a different layer, the first protocol layer entity in the embodiment of the present invention has different functions. The following description will take the first protocol layer as the PDCP layer and the first protocol layer as a layer above the PDCP layer as examples.
And when the first protocol layer is a PDCP layer, the first protocol layer entity performs header compression processing on an SDU fragment corresponding to the first data fragment of the first SDU. Here, the first data segment of the first SDU is located at the front of the first SDU, and 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 buffers the at least two SDU fragments, receives a discard Timer (discard Timer) configured by a higher layer, and performs packet loss processing on the at least two buffered SDU fragments when the discard Timer reaches a preset time value; optionally, after the first pair of the at least two SDU fragments is buffered, the discard Timer is not started. Here, the discard Timer is a shorter value, and may be different from the existing discard Timer in the related art.
When the first protocol layer is a layer above a PDCP layer, for example, the first protocol layer is an SDAP layer, or a third protocol layer above the PDCP layer, below the SDAP layer, or a fourth protocol layer above the SDAP layer, the first protocol layer entity carries third indication information in a packet header of the first PDU, where the third indication information is used to indicate the PDCP layer to determine whether to perform packet header compression or decompression processing on the first PDU; the first PDU contains a data segment of the first SDU; the first PDU is formed by the first SDU with the header of the first protocol layer added. Here, the first PDU includes one data fragment of the first SDU, and the first PDU is formed by adding the header of the first protocol layer to the first SDU.
In this embodiment of the present invention, the first protocol layer entity further indicates that the SDU fragment is a data fragment of the first SDU. In specific implementation, the indication may be performed in a packet header of a first protocol layer corresponding to the SDU fragment; the indication may also be performed by means of signaling when the first protocol layer entity delivers the SDU fragment to a protocol layer below the first protocol layer.
It should be noted that the first protocol layer entity 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 further provides another data packet processing method, where an optional processing flow of the data packet processing method is shown in fig. 5, and the optional processing flow includes:
step S301, a first protocol layer entity receives at least two SDU segments, where the at least two SDU segments are data segments obtained by segmentation based on the size of a first SDU.
In this embodiment of the present invention, when the size of the first SDU is greater than a first threshold, the first protocol layer entity segments the first SDU into at least two SDU segments. When segmenting a first SDU, when the size of the first SDU is an integral multiple of a first threshold value, the size of each SDU segment in at least two SDU segments after segmenting the first SDU is equal to the first threshold value. When segmenting a first SDU, when the size of the first SDU is not an integral multiple of a first threshold value, the size of the last SDU segment in the at least two SDU segments is smaller than the first threshold value, and the sizes of the SDU segments except the last SDU segment are equal to the first threshold value. Or when the size of the first SDU is not integral multiple of a first threshold, equally segmenting the first SDU, wherein the size of each SDU segment obtained by segmentation is equal, and the size of each SDU segment is smaller than the first threshold.
In this embodiment of the present invention, the first threshold is a maximum value of data that the first protocol layer can support transmission. Optionally, the first threshold is a maximum value of a data size that the PDCP layer can support, such as 9 kbytes.
In some optional embodiments, the method further comprises:
step S302, when the first protocol layer entity determines, based on the packet header of the first protocol layer corresponding to each SDU fragment of the at least two SDU fragments, that a second SDU fragment of the at least two SDU fragments is a first data fragment of the first SDU, the first protocol layer entity performs packet header decompression processing on the second SDU fragment.
Here, the header of the first protocol layer corresponding to each SDU fragment includes: first indication information indicating at least one of: and the position of the SDU fragment in the first SDU, the first bit of the SDU fragment corresponds to the position in the first SDU and the SN number.
In specific implementation, the SN numbers corresponding to each SDU fragment may be the same or different; when the SN number corresponding to each of the at least two SDU fragments is different, the header of each of the at least two SDU fragments includes: second indication information; the second indication information is used for indicating the SDU to which the SDU fragment belongs; through the second indication information, the network device can determine each SDU segment after one SDU is segmented, and obtain the SDU through each SDU segment. Correspondingly, the method further comprises the following steps:
step S303, the first protocol layer entity performs merging processing on the at least two SDU fragments to obtain the first SDU.
It should be noted that the first protocol layer entity 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, where a structure of the first protocol layer entity 400 is as shown in fig. 6, and includes:
the first processing unit 401 is configured to segment the first SDU into at least two SDU segments based on the size of the received first SDU, and indicate that the SDU segment is a data segment of the first SDU.
In some embodiments, the size of each of the at least two SDU fragments is equal to the first threshold;
or, the size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, the sizes of SDU fragments other than the first SDU fragment in the at least two SDU fragments are equal, and the size of each SDU fragment is smaller than or equal to the first threshold.
In some embodiments, each of the at least two SDU fragments comprises a corresponding header of the first protocol layer;
the header of the first protocol layer includes: first indication information indicating at least one of: and the position of the SDU fragment in the first SDU and the first byte of the SDU fragment correspond to the position and the SN number in the first SDU.
In some embodiments, the SN number corresponding to each of the at least two SDU fragments is the same, or the SN number corresponding to each of the at least two SDU fragments is different.
When the SN number corresponding to each of the at least two SDU fragments is different, the header of each of the at least two SDU fragments includes: second indication information; the second indication information is used for indicating the SDU to which the SDU fragment belongs.
In some embodiments, the first protocol layer entity further comprises:
a sending unit 402, configured to submit at least two SDU fragments added with a header of the first protocol layer to the second protocol layer entity; the second protocol layer is a lower layer of the first protocol layer.
In some embodiments, the first protocol layer comprises: a PDCP layer, or 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.
In some embodiments, the first protocol layer is a PDCP layer, and when a second SDU fragment of the at least two SDU fragments is a first data fragment of the first SDU, the first processing unit 401 is configured to perform header compression processing on the second SDU fragment;
when a third SDU fragment of the at least two SDU fragments is not the first data fragment of the first SDU, the processing unit is configured not to perform header compression processing on the third SDU fragment.
In some embodiments, the first processing unit 401 is configured to perform compression processing on the packet header of the second SDU fragment.
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 to perform packet loss processing on the at least two SDU fragments; or the first processing unit 401 is configured to not 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 comprises: a storage unit 403, configured to buffer the at least two SDU fragments.
In some embodiments, when the first protocol layer is a 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,
the first processing unit 401 is further configured to carry third indication information in a packet header of the first PDU, where the third indication information is used to indicate the PDCP layer to determine whether to perform packet header compression or decompression on the first PDU; the first PDU contains a data segment of the first SDU; the first PDU is formed by the first SDU with the header of the first protocol layer added.
In some embodiments, the first SDU is user plane data, or control plane data.
It should be noted that the first protocol layer entity according to the embodiment of the present invention corresponds to the first protocol layer entity on the terminal device side.
An embodiment of the present invention further provides another first protocol layer entity, where a structure of the first protocol layer entity 500 is shown in fig. 7, and includes:
a receiving unit 501, configured to receive at least two SDU segments, where the at least two SDU segments are data segments obtained by segmentation based on the size of the first SDU.
In some embodiments, each of the at least two SDU fragments is equal in size and the size of each SDU fragment is less than or equal to the first threshold;
or, the size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, and the sizes of SDU fragments other than the first SDU fragment in the at least two SDU fragments are both equal to the first threshold.
In some embodiments, the first protocol layer entity further comprises:
the second processing unit 502 is configured to, based on the packet header of the first protocol layer corresponding to each SDU fragment of the at least two SDU fragments, determine that a second SDU fragment of the at least two SDU fragments is a first data fragment of the first SDU, and perform, by the first protocol layer entity, packet header decompression processing on the second SDU fragment.
In some embodiments, the second processing unit is configured to perform merging processing on the at least two SDU fragments to obtain the first SDU.
In some embodiments, the packet header of the first protocol layer corresponding to each of the at least two SDU fragments comprises: first indication information indicating at least one of:
and the position of the SDU fragment in the first SDU, the first bit of the SDU fragment corresponds to the position and the SN number in the first SDU.
In some embodiments, the SN number corresponding to each of the at least two SDU fragments is the same or different.
When the SN number corresponding to each of the at least two SDU fragments is different, the header of each of the at least two SDU fragments includes: second indication information; the second indication information is used for indicating the SDU to which the SDU fragment belongs.
In some embodiments, the first protocol layer comprises: a PDCP layer, or 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.
It should be noted that the first protocol layer entity in the embodiment of the present invention corresponds to the first protocol layer entity on the network device side.
The embodiment of the present invention further provides a first protocol layer entity, which includes a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to execute the steps of the power allocation method executed by the terminal device when running the computer program.
The embodiment of the present invention further provides another first protocol layer entity, which includes a processor and a memory, where the memory is used for storing a computer program capable of running on the processor, and the processor is configured to execute the steps of the power allocation method executed by the network device when running the computer program.
Fig. 8 is a schematic diagram of a hardware component structure of a first protocol layer entity according to an embodiment of the present invention, where the first protocol layer entity 700 includes: at least one processor 701, a memory 702, and at least one network interface 704. The various components in the first protocol layer entity 700 are coupled together by a bus system 705. It is understood that the bus system 705 is used to enable connected communication between these components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to a data bus. But for clarity of illustration the various busses are labeled in figure 8 as the bus system 705.
It will be appreciated that the memory 702 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. The non-volatile Memory may be ROM, programmable Read-Only Memory (PROM), erasable Programmable Read-Only Memory (EPROM), electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic random access Memory (FRAM), flash Memory (Flash Memory), magnetic surface Memory, optical Disc, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), synchronous Static Random Access Memory (SSRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), synchronous Dynamic Random Access Memory (SLDRAM), direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 702 described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.
The memory 702 in an embodiment of the present invention is used 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 for operating on the first protocol layer entity 700, such as the application program 7022. Programs that implement methods in accordance with embodiments of the present invention can be included within application program 7022.
The method disclosed in the above embodiments 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 having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 701. The Processor 701 may be a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 701 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed by the embodiment of the invention can be directly implemented by a hardware decoding processor, or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 702, and the processor 701 may read the information in the memory 702 and perform the steps of the aforementioned methods in conjunction 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 Devices (CPLDs), FPGAs, general purpose processors, controllers, MCUs, MPUs, or other electronic components for performing the aforementioned methods.
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 enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.
Optionally, the computer-readable storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.

Claims (16)

1. A method of packet processing, the method comprising:
a first protocol layer entity sending end segments a first Service Data Unit (SDU) into at least two SDU segments based on the size of the received SDU;
the first protocol layer entity sending end indicates the SDU segment as a data segment of the first SDU;
when the first protocol layer is a service data convergence protocol, SDAP, layer located above a PDCP layer, a third protocol layer below the SDAP layer, or a fourth protocol layer above the SDAP layer, the method further includes:
the first protocol layer entity sending end carries third indication information in the packet header of the first PDU, and the third indication information is used for indicating the packet data convergence protocol PDCP layer sending end to judge whether to carry out packet header compression processing on the first PDU or not; the first PDU contains one data segment of the first SDU.
2. The method of claim 1, wherein the first protocol layer entity transmitting end slicing 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 larger than a first threshold value, the first protocol layer entity sending end segments the first SDU into at least two SDU segments;
each of the at least two SDU fragments has an equal size, and the size of each SDU fragment is smaller than or equal to the first threshold;
or, a size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, and sizes of SDU fragments other than the first SDU fragment in the at least two SDU fragments are all equal to the first threshold.
3. The method according to claim 1 or 2, wherein each of the at least two SDU fragments comprises a header of a corresponding first protocol layer;
the header of the first protocol layer includes: first indication information indicating at least one of:
a position of an SDU fragment in the first SDU;
the first byte of the SDU fragment corresponds to the position in the first SDU;
sequence SN number.
4. The method of claim 3, wherein the SN number corresponding to each of the at least two SDU fragments is the same;
or the corresponding SN numbers of each of the at least two SDU fragments are different.
5. The method of claim 4, wherein, when the SN number corresponding to each of the at least two SDU segments is different,
the header of each of the at least two SDU fragments includes: second indication information;
the second indication information is used for indicating the SDU to which the SDU segment belongs.
6. The method according to claim 1 or 2, wherein the method further comprises:
the first protocol layer entity sending terminal submits the at least two SDU segments added with the packet header of the first protocol layer to a second protocol layer entity sending terminal;
the second protocol layer is a lower layer of the first protocol layer.
7. The method of claim 1 or 2, wherein the first SDU is user plane data;
or, the first SDU is control plane data.
8. A first protocol layer entity sender, comprising: a first processing unit, configured to segment a received first service data unit SDU into at least two SDU segments based on a size of the first SDU, and indicate the SDU segment as one data segment of the first SDU;
when the first protocol layer is a service data convergence protocol (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, the first processing unit is further configured to carry third indication information in a packet header of the first PDU, where the third indication information is used for indicating the Packet Data Convergence Protocol (PDCP) layer to determine whether to perform packet header compression or decompression on the first PDU; the first PDU contains one data segment of the first SDU.
9. The first protocol layer entity sender according to claim 8, wherein the first processing unit is configured to segment the first SDU into at least two SDU segments when the size of the first SDU is larger than a first threshold;
each of the at least two SDU segments has an equal size, and the size of each SDU segment is smaller than or equal to the first threshold;
or, the size of a first SDU fragment in the at least two SDU fragments is smaller than the first threshold, and the sizes of SDU fragments other than the first SDU fragment in the at least two SDU fragments are all equal to the first threshold.
10. The first protocol layer entity sender according to claim 8 or 9, wherein each of the at least two SDU fragments comprises a header of a corresponding first protocol layer;
the header of the first protocol layer includes: first indication information indicating at least one of:
a position of an SDU fragment in the first SDU;
the first byte of the SDU fragment corresponds to the position in the first SDU;
the sequence SN number.
11. The first protocol layer entity transmitter according to claim 10, wherein the SN number corresponding to each of the at least two SDU fragments is the same;
or, the SN numbers corresponding to each of the at least two SDU fragments are different.
12. The first protocol layer entity transmitter of claim 11, wherein when the SN number corresponding to each of the at least two SDU segments is different,
the header of each of the at least two SDU fragments includes: second indication information;
the second indication information is used for indicating the SDU to which the SDU fragment belongs.
13. The first protocol layer entity sender according to claim 8 or 9, wherein the first protocol layer entity further comprises:
a sending unit configured to submit at least two SDU fragments added with a header of a first protocol layer to a second protocol layer entity;
the second protocol layer is a lower layer of the first protocol layer.
14. The first protocol layer entity sender according to claim 8 or 9, wherein the first SDU is user plane data;
or, the first SDU is control plane data.
15. A first protocol layer entity sender comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,
the processor is adapted to perform the steps of the data packet processing method according to any one of claims 1 to 7 when running the computer program.
16. A storage medium storing an executable program which, when executed by a processor, implements the packet processing method of any one of claims 1 to 7.
CN201880091259.8A 2018-09-29 2018-09-29 Data packet processing method, entity and storage medium Active CN111886893B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/108567 WO2020062126A1 (en) 2018-09-29 2018-09-29 Method for processing data packet, entity and storage medium

Publications (2)

Publication Number Publication Date
CN111886893A CN111886893A (en) 2020-11-03
CN111886893B true CN111886893B (en) 2022-10-04

Family

ID=69952689

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201880091259.8A Active CN111886893B (en) 2018-09-29 2018-09-29 Data packet processing method, entity and storage medium

Country Status (3)

Country Link
CN (1) CN111886893B (en)
TW (1) TW202027478A (en)
WO (1) WO2020062126A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822276B (en) * 2021-01-09 2023-05-02 中国电力科学研究院有限公司 Substation control layer communication method and system, electronic equipment and storage medium
KR20220132932A (en) * 2021-03-24 2022-10-04 삼성전자주식회사 Method and apparatus for segmenting data to accelerate data processing and reporting reception status in wireless communication system
CN115694719A (en) * 2021-07-28 2023-02-03 华为技术有限公司 Data forwarding method and device for switching scenes
WO2023240495A1 (en) * 2022-06-15 2023-12-21 Oppo广东移动通信有限公司 Data transmission method and apparatus, and communication device

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017191933A1 (en) * 2016-05-03 2017-11-09 Lg Electronics Inc. Method and device for transmitting data unit
CN107995654A (en) * 2016-10-26 2018-05-04 中兴通讯股份有限公司 Data repeating method and device, MAC equipment
WO2018166042A1 (en) * 2017-03-14 2018-09-20 北京小米移动软件有限公司 Data unit transmission method and apparatus
EP3661138A4 (en) * 2017-07-25 2021-01-06 Beijing Xiaomi Mobile Software Co., Ltd. Method, device and system for discarding data packet

Also Published As

Publication number Publication date
WO2020062126A1 (en) 2020-04-02
TW202027478A (en) 2020-07-16
CN111886893A (en) 2020-11-03

Similar Documents

Publication Publication Date Title
CN111886893B (en) Data packet processing method, entity and storage medium
JP2013546254A (en) Data reprocessing at the wireless protocol layer
CN111787580B (en) Data stream processing method, device and storage medium
EP3651538B1 (en) Data transmission method, transmitting end device, and receiving end device
US20220116910A1 (en) Wireless communication method, terminal device, access network device and core network device
CN113133053B (en) Method and device for indicating data copying mode and storage medium
CN114270935A (en) Cell connection method, electronic equipment and storage medium
CN114710778A (en) Connection release method, data processing method, device and storage medium
CN111935853B (en) Protocol data unit session state indication method, terminal device and storage medium
EP3952596A1 (en) Information transmission method and apparatus, and network device
CN114258715A (en) Switching processing method and network equipment
US11540252B2 (en) Data transmission method, network device
CN112514450B (en) Data processing method, device and storage medium
US20210204174A1 (en) Signaling processing method, device, and storage medium
RU2784559C2 (en) Method and device for configuration of unidirectional channel, as well as network device
CN113260073B (en) Method for indicating stop of transmission, terminal equipment and network equipment
CN112703815B (en) Data packet reordering method, electronic equipment and storage medium
CN113078990B (en) Data processing method, terminal equipment and storage medium
CN112154631B (en) Downlink control signal transmission method, terminal device, network device and storage medium
CN115001642B (en) Physical downlink control channel detection method, equipment and storage medium
CN111989951B (en) Data forwarding method and device, and network equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant