CN112469080B - Data packet processing method and related device - Google Patents
Data packet processing method and related device Download PDFInfo
- Publication number
- CN112469080B CN112469080B CN202011360890.9A CN202011360890A CN112469080B CN 112469080 B CN112469080 B CN 112469080B CN 202011360890 A CN202011360890 A CN 202011360890A CN 112469080 B CN112469080 B CN 112469080B
- Authority
- CN
- China
- Prior art keywords
- pdcp
- pdcp pdu
- pdu
- entity
- sequence number
- 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
Links
- 238000003672 processing method Methods 0.000 title description 6
- 238000000034 method Methods 0.000 claims abstract description 47
- 238000012545 processing Methods 0.000 claims abstract description 19
- 238000004891 communication Methods 0.000 claims description 35
- 230000006835 compression Effects 0.000 claims description 16
- 238000007906 compression Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 5
- 230000015654 memory Effects 0.000 claims description 5
- 238000004458 analytical method Methods 0.000 claims description 2
- 230000005540 biological transmission Effects 0.000 abstract description 22
- 238000012946 outsourcing Methods 0.000 description 26
- 230000006870 function Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 8
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000006837 decompression Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0205—Traffic management, e.g. flow control or congestion control at the air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the application discloses a method for processing a data packet and a related device, wherein the method comprises the following steps: a packet data convergence protocol PDCP entity receives a PDCP protocol data unit PDU sent by a radio link layer control protocol RLC entity; the PDCP entity analyzes the PDCP PDU and judges whether the PDCP PDU is an out-of-window data packet; and if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer and does not update a state variable corresponding to the PDCP entity. The invention can improve the transmission rate of the service data.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and a related apparatus for processing a data packet.
Background
In an existing communication system, Data transmission between a User Equipment (UE) and an evolved Node B (eNB) generally passes through a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer and a physical layer. Each layer performs a different data processing. The packet data convergence protocol has the main functions of: header compression of Internet Protocol (IP) data packets, encryption and decryption of data, timer discard, retransmission during reconstruction, and reordering processing.
At this stage, when the terminal device moves at a high speed, the signal will be weakened, which easily causes the PDCP entity to be reestablished. When the PDCP entity is re-established, a situation may occur in which the receiving window of the PDCP entity has already received data but the feedback acknowledgement packet is not successfully transmitted, so that the PDCP transmitting window and the PDCP receiving window are not aligned. The transmission window retransmits the packets of the PDCP that have not been previously acknowledged, as specified by the protocol, but the base station transmits new packets in some cases. Due to the PDCP window misalignment, these new packets will be dropped, which will result in a decrease in the traffic transmission rate over time.
Disclosure of Invention
The embodiment of the application provides a data packet processing method and a related device, which can improve the transmission rate of data services.
In a first aspect, an embodiment of the present application provides a method for processing a data packet, where the method includes: a packet data convergence protocol PDCP entity receives a PDCP protocol data unit PDU sent by a radio link layer control protocol RLC entity; the PDCP entity analyzes the PDCP PDU and judges whether the PDCP PDU is an out-of-window data packet; and if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer and does not update a state variable corresponding to the PDCP entity. By the method, the transmission rate of the data service can be improved.
With reference to the first aspect, in one possible implementation manner, the PDCP entity is in an acknowledged AM mode.
With reference to the first aspect, in a possible implementation manner, if the PDCP PDU is an out-of-window data packet, the specific step of submitting the PDCP PDU to an upper layer by the PDCP entity without updating a state variable corresponding to the PDCP entity includes: if the PDCP PDU is an out-of-window packet and header compression is not configured for the PDCP PDU, the PDCP entity submits the PDCP PDU to an upper layer without updating a state variable corresponding to the PDCP entity.
With reference to the first aspect, in a possible implementation manner, the status variables corresponding to the PDCP entity include one or more of a PDCP sequence number Next _ PDCP _ RX _ SN of a Next to-be-received PDCP PDU, a receiver sequence number rollover counter RX _ HFN, and a Last PDCP sequence number Last _ Submitted _ PDCP _ RX _ SN of a PDCP PDU delivered to an upper layer.
With reference to the first aspect, in a possible implementation manner, if the PDCP PDU is an out-of-window data packet, the specific step of submitting the PDCP PDU to an upper layer by the PDCP entity without updating a state variable corresponding to the PDCP entity includes: if the PDCP PDU is an out-of-window data packet and the PDCP sequence number of the PDCP PDU is the same as any one of the recorded PDCP sequence numbers, the PDCP PDU is discarded by the PDCP entity, and the recorded PDCP sequence number is the sequence number of the PDCP PDU which is submitted to an upper layer by the PDCP entity and is the out-of-window data packet.
In a second aspect, an embodiment of the present application provides a communication apparatus, where the communication apparatus includes a receiving unit, a parsing unit, and a sending unit, where: the receiving unit is configured to receive a PDCP PDU sent by an RLC entity; the analysis unit is configured to analyze the PDCP PDU and determine whether the PDCP PDU is an out-of-window data packet; the sending unit is configured to submit the PDCP PDU to an upper layer if the PDCP PDU is an out-of-window packet, and not update a state variable corresponding to the PDCP entity.
With reference to the second aspect, in one possible implementation manner, the PDCP entity is in an acknowledged AM mode.
With reference to the second aspect, in a possible implementation manner, if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer without updating a state variable corresponding to the PDCP entity, and the sending unit is further configured to: and if the PDCP PDU is an out-of-window data packet and the PDCP PDU is not configured with header compression, submitting the PDCP PDU to an upper layer and not updating a state variable corresponding to the PDCP entity.
With reference to the second aspect, in a possible implementation manner, the state variables corresponding to the PDCP entity include one or more of a PDCP sequence number Next _ PDCP _ RX _ SN of a Next to-be-received PDCP PDU, a receiver sequence number rollover counter RX _ HFN, and a PDCP sequence number Last _ Submitted to an upper layer Last PDCP PDU.
With reference to the second aspect, in a possible implementation manner, if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer without updating a state variable corresponding to the PDCP entity, and the sending unit is further configured to: if the PDCP PDU is an out-of-window data packet and the PDCP sequence number of the PDCP PDU is the same as any one of the recorded PDCP sequence numbers, the PDCP PDU is discarded by the PDCP entity, and the recorded PDCP sequence number is the sequence number of the PDCP PDU which is submitted to an upper layer by the PDCP entity and is the out-of-window data packet.
In a third aspect, the present application provides a computer-readable storage medium for storing a computer program, the computer program causing a computer to perform the method of the first aspect and any possible implementation manner thereof.
In the embodiment of the application, the PDCP entity receives a PDCP PDU sent by the RLC entity, analyzes the PDCP PDU, and determines whether the PDCP PDU is an out-of-window data packet, and if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer without updating a state variable corresponding to the PDCP entity. The method provided by the embodiment of the application can improve the transmission rate of the data service.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic diagram of a network architecture provided in an embodiment of the present application;
fig. 2 is a protocol architecture for transmitting data according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram illustrating a procedure for transmitting PDCP PDUs by a PDCP entity according to an embodiment of the present application;
fig. 4 is a flowchart of a data packet processing method according to an embodiment of the present application.
Fig. 5 is a flowchart of a specific data packet processing method according to an embodiment of the present application
Fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another communication device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terminology used in the following embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in the specification of the present application and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the listed items.
It should be noted that the terms "first," "second," "third," and the like in the description and claims of this application and in the accompanying drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in other sequences than described or illustrated herein. Furthermore, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The embodiment of the present application may be applied to the network architecture schematic diagram shown in fig. 1, where the network architecture shown in fig. 1 is a network architecture of a wireless communication system, the network architecture generally includes a terminal device and a network device, and the number and the form of each device do not constitute a limitation to the embodiment of the present application. The network device may be a Base Station (BS), and the BS may provide communication services to multiple terminal devices, and multiple Base stations may also provide communication services to the same terminal device.
It should be noted that, the wireless communication system in the embodiment of the present application includes, but is not limited to: narrowband band-internet of things (NB-IoT), Enhanced Machine Communication (eMTC), global system for mobile communications (GSM), Enhanced data rate for GSM Evolution (EDGE), Wideband Code Division Multiple Access (WCDMA), code division multiple access (code division multiple access, CDMA2000), time division-synchronous code division multiple access (time division-synchronization code division multiple access, TD-SCDMA), Long Term Evolution (LTE), Long Term Evolution (Long Term Evolution) cable 1, fifth generation mobile Communication (5G-5), and future mobile Communication systems.
The terminal device related to the embodiment of the present application may also be referred to as a terminal, and may be a device with a wireless transceiving function, which may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a User Equipment (UE), wherein the UE includes a handheld device, an in-vehicle device, a wearable device, or a computing device having wireless communication functionality. Illustratively, the UE may be a mobile phone (mobile phone), a tablet computer, or a computer with wireless transceiving function. The terminal device may also be a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and so on. In the embodiment of the present application, the apparatus for implementing the function of the terminal may be a terminal; it may also be a device, such as a system-on-chip, capable of supporting the terminal to implement the function, which may be installed in the terminal. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.
The network device related to the embodiment of the present application includes a Base Station (BS), which may be a device deployed in a radio access network and capable of performing wireless communication with a terminal. The base station may have various forms, such as a macro base station, a micro base station, a relay station, an access point, and the like. For example, the base station related to the embodiment of the present application may be an evolved Node B (eNB). In the embodiment of the present application, the apparatus for implementing the function of the network device may be a network device; or may be a device, such as a system-on-chip, capable of supporting the network device to implement the function, and the device may be installed in the network device.
Referring to fig. 2, fig. 2 is a protocol architecture for transmitting data according to an embodiment of the present disclosure. The output transmission Protocol architecture between the network device and the terminal device shown in fig. 2 mainly includes a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a physical layer. Different data processing functions exist between each layer of protocol, and the PDCP layer mainly performs security operation and header compression and decompression processing, such as encryption and integrity protection; the RLC layer mainly completes the segmented concatenation and sequential delivery of data and the data transmission guarantee of Automatic Repeat Request (ARQ); the MAC layer mainly completes scheduling, cascade processing of different logical channels, and Hybrid Automatic Repeat Request (HARQ) operation; the physical layer completes transmission block packetization and air interface transmission.
When the terminal equipment moves at a high speed, the signal will be weakened, and the PDCP entity is easy to rebuild. When the PDCP entity is re-established, a situation may occur in which the receiving window of the PDCP entity has already received data but the feedback acknowledgement packet is not successfully transmitted, so that the PDCP transmitting window and the PDCP receiving window are not aligned. The transmission window retransmits the packets of the PDCP that have not been previously acknowledged, as specified by the protocol, but the base station transmits new packets in some cases. Due to the PDCP window misalignment, these new packets will be dropped, which will result in a decrease in the traffic transmission rate over time.
For example, as shown in fig. 3, fig. 3 is a schematic diagram illustrating a procedure for sending PDCP PDUs by a PDCP entity according to an embodiment of the present application. Fig. 3 schematically shows a procedure in which a network device transmits PDCP PDUs to a terminal device, wherein a PDCP transmission window corresponds to a PDCP entity of the network device and a PDCP reception window corresponds to a PDCP entity of the terminal device. In fig. 3, for example, the PDCP receiving window has received PDCP PDUs with sequence numbers of 0-4, but the acknowledgement packet of the PDCP PDUs with sequence numbers of 0-2 is not fed back successfully, and the PDCP entity of the network device defaults that the PDCP entity of the terminal device has not received PDCP PDUs with sequence numbers of 0-2. According to the protocol, the sending window can retransmit PDCP PDU with a PDCP sequence number of 0-2. At this time, the PDCP sending window is located at the position of the original sequence number 0, but the PDCP receiving window is located at the position of the original sequence number 3, the PDCP sending window and the PDCP receiving window are not aligned, and the PDCP receiving window will discard the received out-of-window data packet. In some cases, the network device may also send new packets, which are discarded due to the misaligned PDCP window, which may result in a reduced traffic transmission rate for a period of time.
A method for processing a data packet according to the embodiment of the present application is described below based on the network architecture and the device described in the foregoing, and referring to fig. 4, fig. 4 is a flowchart of a method for processing a data packet according to the embodiment of the present application.
S101, the PDCP entity receives the PDCP PDU sent by the RLC entity.
In the embodiment of the present application, the PDCP entity is in an Acknowledged Mode (AM). The AM mode is a standard mode of packet data transmission, and a transmitting side transmits data after adding necessary control protocol overhead on higher layer data and guarantees delivery to a peer entity. Data in the AM mode has a very high requirement on accuracy, so that data information is transmitted in the AM mode and needs to be sent in a window order, and when data is sent, a peer entity needs to feed back an acknowledgement packet to confirm that the data has been sent. The PDCP entity, for a Data Radio Bearer (DRB) mapped to the RLC AM, upon receiving a PDCP PDU of a lower layer, satisfies that a PDCP sequence number of the PDU is equal to a PDCP sequence number (Next _ PDCP _ RX _ SN) of a PDU to be received Next.
S102, the PDCP entity analyzes the PDCP PDU and judges whether the PDCP PDU is an out-of-window data packet.
In the embodiment of the present application, the specific steps of determining whether the PDCP PDU is outsourcing the window are as follows: the PDCP entity analyzes a PDCP head of the PDCP PDU and acquires a sequence number of the PDCP PDU; the PDCP entity judges whether the PDCP PDU meets a first preset condition or a second preset condition, wherein the first preset condition is that the value obtained by subtracting the sequence number of the PDCP PDU submitted to the high layer last time from the sequence number of the PDCP PDU is larger than the number of PDCP reordering windows, and the second preset condition is that the value obtained by subtracting the sequence number of the PDCP PDU submitted to the high layer last time from the sequence number of the PDCP PDU is larger than or equal to 0 and smaller than the number of the PDCP reordering windows; and if the PDCP PDU meets the first preset condition or the second preset condition, determining the PDCP PDU as an out-of-window data packet.
For example, the PDCP entity re-establishes, and needs to re-send 3 PDCP PDUs, at this time, the number of PDCP reordering windows is 3, the sequence number of the PDCP PDU that the PDCP entity last submitted to the higher layer is 0, and at this time, the PDCP entity receives the PDCP PDU with sequence number 5. The value obtained by subtracting the sequence number of the PDCP PDU submitted to the upper layer last time by the PDCP entity from the sequence number of the PDCP PDU is 5, which is greater than the PDCP reordering window number, and meets a first preset condition, so that the PDCP is determined to be an out-of-window data packet. If other conditions are not changed, when the sequence number of the received PDCP PDU is 2, the value obtained by subtracting the sequence number of the PDCP PDU submitted to the high layer by the PDCP entity last time is 2, the value is smaller than the PDCP reordering window number, and the first preset condition is not met; the value obtained by subtracting the sequence number of the PDCP PDU from the sequence number of the PDCP PDU which is last submitted to the higher layer by the PDCP entity is-2, and the second preset condition is not met. Therefore, the PDCP PDU with sequence number 2 is not out-of-window.
S103, if the PDCP PDU is the outsourcing of the window, the PDCP entity submits the PDCP PDU to an upper layer and does not update the state variable corresponding to the PDCP entity.
In the embodiment of the present application, the status variable corresponding to the PDCP entity includes one or more of a PDCP sequence number (Next _ PDCP _ RX _ SN) of a Next to-be-received PDCP PDU, a receiver sequence number rollover counter (RX _ HFN), and a PDCP sequence number (Last _ committed _ PDCP _ RX _ SN) of a Last PDCP PDU delivered to an upper layer.
In this embodiment of the present application, step S103 specifically includes: and if the PDCP PDU is an out-of-window data packet and the PDCP PDU is not configured with header compression, submitting the PDCP PDU to an upper layer by the PDCP entity and not updating a state variable corresponding to the PDCP entity. If header compression is configured for the PDCP PDU, the PDCP entity discards the PDCP PDU. In order to provide voice service in a Packet Switching domain (PS) with efficiency close to that of a conventional circuit Switching domain, the PDCP entity may compress an Internet Protocol (IP)/User Datagram Protocol (UDP)/Real-time Transport Protocol (RTP) header. Under a normal condition, the requirement on the time delay of the data service applied to a non-header compression scene is higher, so that the PDCP entity can increase the sending rate of a data packet by submitting the PDCP PDU to an upper layer after judging and confirming that the PDCP PDU is not configured with header compression, thereby avoiding the loss of the data packet and reducing the time delay.
In this embodiment of the present application, step S103 further includes: if the PDCP PDU is an out-of-window packet and the PDCP sequence number of the PDCP PDU is the same as any one of the recorded PDCP sequence numbers, the PDCP PDU is discarded by the PDCP entity, and the recorded PDCP sequence number is the sequence number of the PDCP PDU which is submitted to an upper layer by the PDCP entity and is the out-of-window packet. When the PDCP entity is outsourced to an upper layer transmission window, the PDCP sequence number outsourced to each window is recorded. After receiving the window outsourcing, whether the window outsourcing is received before is confirmed by comparing the PDCP sequence number of the window outsourcing with the recorded PDCP sequence number, and if the window outsourcing is received before, the window outsourcing is discarded. By the mode, repeated window outsourcing of uploading can be effectively avoided, and the burden of a network is lightened.
In a possible implementation manner, step S103 further includes: if the PDCP PDU is an out-of-window packet, the PDCP entity determines whether the out-of-window packet is received or not based on a PDCP sequence number and a preset variable of the PDCP PDU, and if so, discards the out-of-window packet. The size of the preset variable is larger than the number of the windows of the PDCP entity, for example, the number of the windows of the PDCP entity is 8, and the size of the preset variable may be 16 bits. The preset variable is represented in a binary manner, each window position of the PDCP entity corresponds to a bit number of a preset variable value, for example, a second window position of the PDCP entity may correspond to a second bit of the variable value. When the PDCP entity receives a window outsourcing, the preset variable changes from 0 to 1 or from 1 to 0 according to the number of bits corresponding to the sequence number of the window outsourcing, which is not limited in this embodiment. When receiving the window outsourcing, the PDCP entity reads the variable to determine whether the packet is a previously received packet, and if the packet is a previously received packet, discards the previously received packet.
In the following, a specific example is used to specifically describe the scheme, and it is assumed that the window number of the PDCP entity is 4, the size of the preset variable is 8 bits, and the initial preset variable is 00000000. The 3 rd bit to the 6 th bit of the corresponding preset variable in the window. When the PDCP entity receives a sequence number 2 window outsourcing (for example, the number of bits corresponding to the window outsourcing is 2 nd bit), the value of the preset variable will become 01000000. If the PDCP entity receives an out-of-window packet with sequence number 2 again, based on the predetermined variable, the PDCP entity determines that the out-of-window packet has been received, and discards the out-of-window packet with sequence number 2.
In a possible implementation manner, if the PDCP PDU is configured for ciphering, determining whether the sequence number of the PDCP PDU is greater than the sequence number of the PDCP PDU expected to be received; if the sequence number of the PDCP PDU is larger than the sequence number of the expected received PDCP PDU, calculating a difference value obtained by subtracting 1 from the sequence number of the PDCP PDU and a sequence number rollover counter (HFN), and decrypting the PDCP PDU; if the sequence number of the PDCP PDU is less than or equal to the sequence number of the expected received PDCP PDU, the sequence number of the PDCP PDU and the value of the HFN are used for calculation, and the PDCP PDU is decrypted. By means of encrypting and decrypting the data, the data can be protected more effectively, and the safety of the data is improved.
In a possible implementation manner, if the PDCP PDU is not an out-of-window packet, it is determined whether ciphering and header compression are configured for the PDCP PDU, and if ciphering is configured, the data packet is decrypted, and if header compression is configured, the data packet is decompressed. And updating the state variable of the PDCP entity and submitting the upper layer of the PDCP PDU.
Based on the above-described packet processing method, an embodiment of the present application further provides a specific packet processing scheme, please refer to fig. 5. The specific flow of the data packet sending method is as follows: the PDCP entity receives PDCP PDUs transmitted by the RLC entity. Then the PDCP entity judges that the PDCP PDU is outsourcing of the window. Next, the PDCP entity judges whether the PDCP PDU is configured with encryption or not, and if the PDCP PDU is configured with encryption, the PDCP entity decrypts the PDCP PDU; if the ciphering is not configured or the PDCP entity decrypts the PDCP PDU configured with the ciphering, the PDCP entity judges whether the PDCP PDU is configured with the header compression. If the PDCP PDU is configured with header compression, the PDCP PDU carries out decompression and then discards the PDCP PDU; if the PDCP PDU has no configuration header compression, the PDCP entity judges whether the PDCP sequence number of the PDCP PDU is the same as any one of the recorded PDCP sequence numbers. If the two are the same, the PDCP entity discards the PDCP PDU; and if not, submitting the PDCP PDU to an upper layer by the PDCP entity, and not updating the state variable corresponding to the PDCP entity.
It can be seen that, based on the methods described in steps S101 to S103, after receiving the window outsourcing, the PDCP entity does not adopt the processing mode of discarding the window outsourcing, but continues to transmit to the upper layer after processing the window outsourcing, and does not change the state variable of the PDCP entity. By the method, the terminal equipment can acquire the data in the window outsourcing, thereby being beneficial to reducing the time delay of the service and improving the transmission rate of the data service.
In order to implement the functions in the method provided by the embodiment of the present application, the terminal device may include a hardware structure and a software module, and implement the functions in the form of a hardware structure, a software module, or a hardware structure and a software module. Some of the above functions may be implemented by a hardware structure, a software module, or a hardware structure plus a software module.
Fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device 60 comprises a receiving unit 601, an analyzing unit 602 and a transmitting unit 603, wherein:
the receiving unit 601 is configured to receive a PDCP PDU sent by a PDCP entity. Specifically, the operation performed by the receiving unit 601 may refer to the description in step S101 in the method shown in fig. 4.
The parsing unit 602 is configured to parse the PDCP PDU, and determine whether the PDCP PDU is an out-of-window data packet. Specifically, the operation performed by the parsing unit 602 may refer to the description in step S102 in the method shown in fig. 4.
The sending unit 603 is configured to submit the PDCP PDU to an upper layer if the PDCP PDU is an out-of-window data packet, and not update the state variable corresponding to the PDCP entity. Specifically, the operation performed by the sending unit 603 may refer to the description in step S103 in the method shown in fig. 4.
In this embodiment of the application, if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer, and does not update a state variable corresponding to the PDCP entity, and the sending unit 603 is further configured to: and if the PDCP PDU is an out-of-window data packet and the PDCP PDU is not configured with header compression, submitting the PDCP PDU to an upper layer and not updating a state variable corresponding to the PDCP entity.
In this embodiment of the application, if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer, and does not update a state variable corresponding to the PDCP entity, and the sending unit 603 is further configured to: if the PDCP PDU is an out-of-window data packet and the PDCP sequence number of the PDCP PDU is the same as any one of the recorded PDCP sequence numbers, the PDCP PDU is discarded by the PDCP entity, and the recorded PDCP sequence number is the sequence number of the PDCP PDU which is submitted to an upper layer by the PDCP entity and is the out-of-window data packet.
It should be noted that the operations performed by the units of the communication apparatus shown in fig. 6 may be related to the method embodiment described above. And will not be described in detail herein. The above units can be realized by hardware, software or a combination of hardware and software.
With the communications apparatus shown in fig. 6, after receiving the window outsourcing, the PDCP entity does not take a processing mode of discarding the window outsourcing, but continues to transmit to an upper layer after processing the window outsourcing, and does not change the state variable of the PDCP entity. By the method, the terminal equipment can acquire the data in the window outsourcing, thereby being beneficial to reducing the time delay of the service and improving the transmission rate of the data service.
Fig. 7 is a schematic structural diagram of another communication device according to an embodiment of the present application. The communication device 70 is a PDCP entity. The communication device 70 may be used to implement the method described in the above method embodiment, and specific reference may be made to the description in the above method embodiment.
The communication device 70 may include one or more processors 701. The processor 701 may be a general-purpose processor or a special-purpose processor, etc. The processor 701 may be configured to control the communication device, execute a software program, and process data of the software program.
Optionally, the communication device 70 may include one or more memories 702, on which instructions 704 may be stored, and the instructions may be executed on the processor 701, so that the communication device 70 performs the method described in the above method embodiment. Optionally, the memory 702 may further store data therein. The processor 701 and the memory 702 may be provided separately or integrated together.
Optionally, the communication device 70 may further include a transceiver 705 and an antenna 707. The transceiver 705 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc. for implementing a transceiving function. The transceiver 705 may include a receiver and a transmitter, and the receiver may be referred to as a receiver or a receiving circuit, etc. for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmission circuit, etc. for implementing the transmission function.
In one implementation, the processor 701 is configured to receive PDCP PDUs transmitted by an RLC entity through the transceiver 705. The processor 701 is further configured to parse the PDCP PDU, and determine whether the PDCP PDU is an out-of-window packet. The processor 701 is further configured to submit the PDCP PDU to an upper layer through the transceiver 705 when the PDCP PDU is an out-of-window packet, and not update a state variable corresponding to the PDCP entity.
The operations performed by the processor 701 may be related to the method embodiments described above. And will not be described in detail herein.
In another possible design, the transceiver may be a transceiver circuit, or an interface circuit. The transceiver circuitry, interface or interface circuitry for implementing the receive and transmit functions may be separate or integrated. The transceiver circuit, the interface circuit or the interface circuit may be used for reading and writing code/data, or the transceiver circuit, the interface circuit or the interface circuit may be used for transmitting or transferring signals.
In yet another possible design, the processor 701 may optionally have instructions 703 stored therein, and the instructions 703 may be executed on the processor 701, so that the communication device 70 may execute the method described in the above method embodiment. The instructions 703 may be solidified in the processor 701, in which case the processor 701 may be implemented in hardware.
In yet another possible design, the communication device 70 may include circuitry that may implement the functionality of transmitting or receiving or communicating in the foregoing method embodiments.
The processors and transceivers described herein may be implemented on Integrated Circuits (ICs), analog ICs, Radio Frequency Integrated Circuits (RFICs), mixed signal ICs, Application Specific Integrated Circuits (ASICs), Printed Circuit Boards (PCBs), electronic devices, and the like.
With the communications apparatus shown in fig. 7, after receiving the window outsourcing, the PDCP entity does not take a processing mode of discarding the window outsourcing, but continues to transmit to an upper layer after processing the window outsourcing, and does not change a state variable of the PDCP entity. By the method, the terminal equipment can acquire the data in the window outsourcing, thereby being beneficial to reducing the time delay of the service and improving the transmission rate of the data service. The present application also provides a computer-readable storage medium, which includes a computer program or instructions, when the computer program or instructions runs on a computer, the computer can execute the corresponding procedures executed by the PDCP entity in the method of the embodiment shown in fig. 3.
While only some embodiments of the invention have been described in detail, it will be understood that the invention is not limited thereto, and that the invention is capable of other embodiments and modifications, which will be apparent to those skilled in the art, and which will be within the scope of the invention as defined by the appended claims.
Claims (12)
1. A method of packet processing, the method comprising:
a packet data convergence protocol PDCP entity receives a PDCP protocol data unit PDU sent by a radio link layer control protocol RLC entity;
the PDCP entity analyzes the PDCP PDU and judges whether the PDCP PDU is an out-of-window data packet;
if the PDCP PDU is an out-of-window data packet, the PDCP entity submits the PDCP PDU to an upper layer and does not update a state variable corresponding to the PDCP entity;
if the PDCP PDU meets a first preset condition or a second preset condition, the PDCP PDU is an out-of-window data packet;
the first preset condition is that the value of the sequence number of the PDCP PDU minus the sequence number of the PDCP PDU submitted to a higher layer by the PDCP entity last time is larger than the number of PDCP reordering windows;
the second preset condition is that the value of the sequence number of the PDCP PDU which is submitted to a high layer by the PDCP entity last time minus the sequence number of the PDCP PDU is more than or equal to 0 and less than the PDCP reordering window number.
2. The method of claim 1, wherein the PDCP entity is in acknowledged AM mode.
3. The method according to claim 1 or 2, wherein if the PDCP PDU is an out-of-window packet, the PDCP entity submitting the PDCP PDU to an upper layer without updating a state variable corresponding to the PDCP entity comprises:
and if the PDCP PDU is an out-of-window data packet and header compression is not configured to the PDCP PDU, submitting the PDCP PDU to an upper layer by the PDCP entity and not updating a state variable corresponding to the PDCP entity.
4. The method as claimed in claim 3, wherein the status variables corresponding to the PDCP entities include one or more of a PDCP sequence number Next _ PDCP _ RX _ SN of a Next PDCP PDU to be received, a receiver sequence number rollover counter RX _ HFN, and a PDCP sequence number Last _ Submitted _ PDCP _ RX _ SN of a PDCP PDU Last Submitted to an upper layer.
5. The method according to claim 1 or 2, wherein if the PDCP PDU is an out-of-window packet, the PDCP entity submitting the PDCP PDU to an upper layer without updating a state variable corresponding to the PDCP entity comprises:
and if the PDCP PDU is an out-of-window data packet and the PDCP sequence number of the PDCP PDU is the same as any one of the recorded PDCP sequence numbers, the PDCP PDU is discarded by the PDCP entity, and the recorded PDCP sequence number is the sequence number of the PDCP PDU which is submitted to an upper layer by the PDCP entity and is the out-of-window data packet.
6. A communication apparatus is characterized by comprising a receiving unit, a parsing unit and a transmitting unit:
the receiving unit is used for receiving a packet data convergence protocol PDCP protocol data unit PDU sent by a radio link layer control protocol RLC entity;
the analysis unit is used for analyzing the PDCP PDU and judging whether the PDCP PDU is an out-of-window data packet;
the sending unit is configured to submit the PDCP PDU to an upper layer if the PDCP PDU is an out-of-window packet, and not update a state variable corresponding to the PDCP entity;
if the PDCP PDU meets a first preset condition or a second preset condition, the PDCP PDU is an out-of-window data packet;
the first preset condition is that the value of the sequence number of the PDCP PDU minus the sequence number of the PDCP PDU submitted to a higher layer by the PDCP entity last time is larger than the number of PDCP reordering windows;
the second preset condition is that the value of the sequence number of the PDCP PDU which is submitted to a high layer by the PDCP entity last time minus the sequence number of the PDCP PDU is more than or equal to 0 and less than the PDCP reordering window number.
7. The communications apparatus of claim 6, wherein the PDCP entity is in acknowledged AM mode.
8. The communications apparatus as claimed in claim 6 or 7, wherein if the PDCP PDU is an out-of-window packet, the PDCP PDU is submitted to an upper layer, and the state variable corresponding to the PDCP entity is not updated, the sending unit is further configured to:
and if the PDCP PDU is an out-of-window data packet and the PDCP PDU is not configured with header compression, submitting the PDCP PDU to an upper layer and not updating a state variable corresponding to the PDCP entity.
9. The communications apparatus of claim 8, wherein the status variables corresponding to the PDCP entity include one or more of a PDCP sequence number Next _ PDCP _ RX _ SN of a Next PDCP PDU to be received, a receiver sequence number rollover counter RX _ HFN, and a PDCP sequence number Last _ committed _ PDCP _ RX _ SN of a Last PDCP PDU delivered to an upper layer.
10. The communications apparatus as claimed in claim 6 or 7, wherein if the PDCP PDU is an out-of-window packet, the PDCP PDU is submitted to an upper layer, and the state variable corresponding to the PDCP entity is not updated, the sending unit is further configured to:
and if the PDCP PDU is an out-of-window data packet and the PDCP sequence number of the PDCP PDU is the same as any one of the recorded PDCP sequence numbers, discarding the PDCP PDU, wherein the recorded PDCP sequence number is the sequence number of the PDCP PDU which is submitted to an upper layer and is the out-of-window data packet.
11. A communications apparatus, comprising a memory and a processor, the memory to store instructions executable on the processor to cause the communications apparatus to perform the method of any of claims 1-5.
12. A computer-readable storage medium for storing a computer program for causing a computer to execute the method for packet processing according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011360890.9A CN112469080B (en) | 2020-11-27 | 2020-11-27 | Data packet processing method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011360890.9A CN112469080B (en) | 2020-11-27 | 2020-11-27 | Data packet processing method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112469080A CN112469080A (en) | 2021-03-09 |
| CN112469080B true CN112469080B (en) | 2022-08-02 |
Family
ID=74808100
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011360890.9A Active CN112469080B (en) | 2020-11-27 | 2020-11-27 | Data packet processing method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112469080B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114449371B (en) * | 2022-02-16 | 2024-08-23 | 上海数果科技有限公司 | An OMA intercom system based on Cat1 |
| CN116156560B (en) * | 2023-02-21 | 2025-08-08 | 上海移远通信技术股份有限公司 | Wireless communication method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102123520A (en) * | 2010-01-07 | 2011-07-13 | Lg电子株式会社 | Method for processing MAC protocol data unit in a wireless communication system |
| CN105229961A (en) * | 2013-04-04 | 2016-01-06 | 诺基亚通信公司 | Sending of protocol Data Unit |
| WO2018030798A1 (en) * | 2016-08-09 | 2018-02-15 | Samsung Electronics Co., Ltd. | Method and apparatus for managing user plane operation in wireless communication system |
| CN107852768A (en) * | 2015-08-06 | 2018-03-27 | 高通股份有限公司 | The method, apparatus and computer-readable medium to be reordered for the PDCP (PDCP) under enhanced component carrier |
| CN107920036A (en) * | 2016-10-09 | 2018-04-17 | 大唐移动通信设备有限公司 | One kind reorders window regulation method and device |
| CN110431876A (en) * | 2017-08-10 | 2019-11-08 | Lg电子株式会社 | Method of performing re-establishment of PDCP entity associated with UM RLC entity in wireless communication system and apparatus therefor |
| CN110546985A (en) * | 2017-03-24 | 2019-12-06 | 捷开通讯(深圳)有限公司 | layer two architecture in the field of cellular radio systems |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8694869B2 (en) * | 2003-08-21 | 2014-04-08 | QUALCIMM Incorporated | Methods for forward error correction coding above a radio link control layer and related apparatus |
| KR101084135B1 (en) * | 2005-05-04 | 2011-11-17 | 엘지전자 주식회사 | Status PD Transmitting and Receiving Method in Transceiver of Wireless Communication System |
| CN101686494B (en) * | 2008-09-22 | 2012-07-04 | 电信科学技术研究院 | Method and device for processing packets by packet data convergence protocol (PDCP) layer |
| CN102104535B (en) * | 2009-12-18 | 2013-12-18 | 华为技术有限公司 | Method, device and system for transmitting PDCP data |
| US8958422B2 (en) * | 2012-03-17 | 2015-02-17 | Blackberry Limited | Handling packet data convergence protocol data units |
| US9998434B2 (en) * | 2015-01-26 | 2018-06-12 | Listat Ltd. | Secure dynamic communication network and protocol |
| CN106357548B (en) * | 2016-09-18 | 2019-06-11 | 京信通信系统（中国）有限公司 | Method and system for receiving PDCP data packets |
| WO2018187212A1 (en) * | 2017-04-03 | 2018-10-11 | Listat Ltd. | Methods and apparatus for hypersecure last mile communication |
| CA3072168C (en) * | 2017-08-11 | 2022-06-28 | Lg Electronics Inc. | Methods and devices for transmitting data units, with selective radio link control (rlc) service data unit (sdu) discarding |
| CN110324851B (en) * | 2018-03-30 | 2021-08-24 | 维沃移动通信有限公司 | A receiving method and communication device |
-
2020
- 2020-11-27 CN CN202011360890.9A patent/CN112469080B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102123520A (en) * | 2010-01-07 | 2011-07-13 | Lg电子株式会社 | Method for processing MAC protocol data unit in a wireless communication system |
| CN105229961A (en) * | 2013-04-04 | 2016-01-06 | 诺基亚通信公司 | Sending of protocol Data Unit |
| CN107852768A (en) * | 2015-08-06 | 2018-03-27 | 高通股份有限公司 | The method, apparatus and computer-readable medium to be reordered for the PDCP (PDCP) under enhanced component carrier |
| WO2018030798A1 (en) * | 2016-08-09 | 2018-02-15 | Samsung Electronics Co., Ltd. | Method and apparatus for managing user plane operation in wireless communication system |
| CN107920036A (en) * | 2016-10-09 | 2018-04-17 | 大唐移动通信设备有限公司 | One kind reorders window regulation method and device |
| CN110546985A (en) * | 2017-03-24 | 2019-12-06 | 捷开通讯(深圳)有限公司 | layer two architecture in the field of cellular radio systems |
| CN110431876A (en) * | 2017-08-10 | 2019-11-08 | Lg电子株式会社 | Method of performing re-establishment of PDCP entity associated with UM RLC entity in wireless communication system and apparatus therefor |
Non-Patent Citations (3)
| Title |
|---|
| "RP_2016".《3GPP tsg_ran\TSG_RAN》.2018, * |
| Advanced_Dynamic_Channel_Access_Strategy_in_Spectrum_Sharing_5G_Systems;Siyu Lin,;《IEEE XPLORE》;20171215;全文 * |
| 基于移动网的传输网络优化方案设计;赵宇;《中国优秀硕士学位论文全文数据库（电子期刊）信息科技辑》;20121208;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112469080A (en) | 2021-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2136501B1 (en) | Method of delivering a PDCP data unit to an upper layer | |
| US8050228B2 (en) | Window control and retransmission control method and transmitting-side apparatus | |
| KR100792586B1 (en) | Method and apparatus for handling control PDXs during re-setting of receivers in wireless communication system | |
| US11159981B2 (en) | Congestion processing method and apparatus | |
| CN107005560B (en) | A data transmission method, data reception method and related equipment | |
| US8917728B2 (en) | Retransmission request transmitting method and receiving-side apparatus | |
| KR20200061405A (en) | Data processing methods and devices, and computer storage media | |
| CN110995750B (en) | Terminal device | |
| US20100110984A1 (en) | Retransmission request transmission method, transmitting- side apparatus and receiving-side apparatus | |
| EP3641258A1 (en) | Data transmission method, related device and communication system | |
| US12309637B2 (en) | Wireless communication method, terminal device and network device | |
| CN112469080B (en) | Data packet processing method and related device | |
| CN111163081A (en) | Data transmission method, device, equipment and storage medium | |
| US20100144364A1 (en) | Retransmission control method and transmitting-side apparatus | |
| US20080137574A1 (en) | Method and apparatus for handling data delivery in a wireless communications system | |
| CN108200605B (en) | A data transmission method and device for a base station | |
| CN106341368A (en) | Data processing method and device | |
| GB2462699A (en) | Delivering PDCP SDUs to an upper layer within a receiving side entity of an E-UMTS | |
| US11296831B2 (en) | Method and apparatus for wireless communication | |
| JP4478180B2 (en) | Wireless communication system | |
| CN109842907A (en) | The method and apparatus for transmitting data | |
| EP4171112A1 (en) | Apparatus and methods to perform uplink data compression in nr | |
| WO2023065114A1 (en) | Apparatus and methods to perform uplinkdata compression in nr | |
| JP4955734B2 (en) | Method of transmitting PDCP data unit to upper level |
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 |