CN112789839A

CN112789839A - Data packet processing method, device and storage medium

Info

Publication number: CN112789839A
Application number: CN201980064919.8A
Authority: CN
Inventors: 唐海
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-06-25
Filing date: 2019-06-25
Publication date: 2021-05-11
Anticipated expiration: 2039-06-25
Also published as: WO2020258018A1; CN112789839B

Abstract

The invention discloses a data packet processing method, which comprises the following steps: the first transmitting electronic device sets a Packet Data Convergence Protocol (PDCP) Sequence Number (SN) and/or a state variable of a PDCP data packet based on the first information; the first information is a pre-agreed PDCP SN and/or a PDCP SN distribution rule; or, the first information is a PDCP SN and/or a PDCP SN allocation rule sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device. The invention also discloses another data packet processing method, another data packet processing device and another storage medium.

Description

Data packet processing method, device and storage medium

Technical Field

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

Background

In the related art, when a Packet Data Convergence Protocol (PDCP) Data Packet is transmitted, a PDCP Data Packet received by a receiving electronic device may come from PDCP entities of different transmitting electronic devices; for example, the receiving electronic device receives PDCP data packets sent by the PDCP entity of the source network device and the PDCP entity of the target network device. In order to achieve effective management of PDCP data packets, how a sending electronic device sets a PDCP Sequence Number (SN), and how a receiving electronic device processes received PDCP data packets based on the PDCP SN, there is no effective solution at present.

Disclosure of Invention

To solve the foregoing technical problem, embodiments of the present invention provide a data packet processing method, device and storage medium, which can implement effective management of PDCP data packets.

In a first aspect, an embodiment of the present invention provides a data packet processing method, including: the first sending electronic device sets the PDCP SN and/or the state variable of the PDCP data packet based on the first information; the first information is a pre-agreed PDCP SN and/or a PDCP SN distribution rule; or, the first information is a PDCP SN and/or a PDCP SN allocation rule sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device.

In a second aspect, an embodiment of the present invention provides a data packet processing method, including: the receiving electronic equipment receives the PDCP SNs and/or PDCP SN distribution rules of at least two sending electronic equipment; and the receiving electronic equipment processes the PDCP data packet according to the PDCP SN and/or the PDCP SN distribution rule.

In a third aspect, an embodiment of the present invention provides a transmitting electronic device, where the transmitting electronic device includes: a first processing unit configured to set a PDCP SN and/or a state variable of the PDCP data packet based on the first information; the first information is a pre-agreed PDCP SN and/or a PDCP SN distribution rule; or, the first information is the PDCP SN and/or the PDCP SN assignment rule sent by the sending electronic device to the second sending electronic device and/or the receiving electronic device.

In a fourth aspect, an embodiment of the present invention provides a receiving electronic device, where the receiving electronic device includes: a receiving unit configured to receive PDCP SNs and/or PDCP SN allocation rules of at least two transmitting electronic devices;

and the second processing unit is configured to process the PDCP data packet according to the PDCP SN and/or the PDCP SN distribution rule.

In a fifth aspect, an embodiment of the present invention provides a transmitting electronic device, including a processor and a memory, where the memory is used for storing a computer program that can be executed on the processor, and the processor is configured to execute the steps of the packet processing method executed by the transmitting electronic device when the processor executes the computer program.

In a sixth aspect, an embodiment of the present invention provides a receiving electronic device, including a processor and a memory, where the memory is used for storing a computer program that can be executed on the processor, and the processor is configured to execute the steps of the packet processing method executed by the receiving electronic device when the processor executes 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 executed by the sending electronic 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 packet processing method executed by the receiving electronic device.

In the data packet processing method provided by the embodiment of the invention, the sending electronic equipment sets the PDCP SN and/or the state variable of the PDCP data packet based on the first information; wherein, the first information is a PDCP SN and/or a PDCP SN distribution rule agreed in advance; or, the first information is a PDCP SN and/or a PDCP SN allocation rule sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device. Therefore, when the terminal device performs data transmission with the source network device and the target network device simultaneously, the sending electronic device can reasonably and orderly set the PDCP SN and/or the state variable of the PDCP data packet, and the problem of error processing of the PDCP data packet caused by inconsistent understanding of the PDCP SN by the terminal device, the source network device and the target network device is avoided. The receiving electronic equipment performs redundancy sequencing, detection, deletion and redundancy detection on the PDCP data packets according to the PDCP SN and/or the PDCP SN distribution rule, so that the problem of delay of delivery to a high layer after the PDCP data packets are received is solved, and the overall data transmission rate of a network system is improved.

Drawings

FIG. 1 is a schematic flow chart of cell handover in an NR system according to the present invention;

FIG. 2 is a schematic flow chart of conditional switch according to the present invention;

FIG. 3 is a schematic diagram illustrating a process of transmitting and receiving PDCP data packets according to the present invention;

FIG. 4 is a diagram illustrating the format of the COUNT of the present invention;

FIG. 5 is a block diagram of a communication system according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an alternative processing flow of a data packet processing method according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating a PDCP control PDU type and type indication according to an embodiment of the present invention;

fig. 8 is a schematic diagram illustrating a processing flow of the first transmitting electronic device setting the PDCP SN and/or the status variable of the PDCP data packet according to the embodiment of the present invention;

FIG. 9 is a schematic view of an alternative processing flow of a data packet processing method according to an embodiment of the present invention;

FIG. 10 is a detailed flowchart illustrating a PDCP packet processing method according to an embodiment of the present invention;

fig. 11 is a schematic diagram illustrating that a source network device interacts with a target network device according to a PDCP SN or PDCP SN distribution rule according to an embodiment of the present invention;

fig. 12 is a transmission diagram of a source network device, a target network device and a terminal device according to an embodiment of the present invention;

FIG. 13 is a diagram illustrating a format of a PDCP control PDU carrying a PDCP SN bitmap indication according to an embodiment of the present invention;

FIG. 14 is a schematic diagram illustrating another detailed processing flow of a PDCP data packet processing method according to an embodiment of the present invention;

FIG. 15a is a schematic diagram showing a format I of a PDCP PDU carrying an actual PDCP SN and a virtual PDCP SN;

FIG. 15b is a schematic diagram showing a format II of a PDCP PDU carrying an actual PDCP SN and a virtual PDCP SN;

FIG. 15c is a schematic diagram showing a third format of a PDCP PDU carrying an actual PDCP SN and a virtual PDCP SN;

fig. 16 is a schematic diagram illustrating that PDCP PDUs of PDCP entities sent by a source network device and a target network device to a terminal device both carry actual PDCP SNs and virtual PDCP SNs in the embodiment of the present invention;

FIG. 17 is a schematic diagram of a component structure of a transmitting electronic device according to an embodiment of the present invention;

FIG. 18 is a schematic diagram of a component structure of a receiving electronic device according to an embodiment of the present invention;

fig. 19 is a schematic diagram of a hardware component structure of an electronic device 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 describing the data processing method provided by the embodiment of the present invention in detail, a brief description will be given to a data processing procedure in the related art.

A New Radio (NR) system supports a handover procedure of a connected terminal device. When a terminal device using network service moves from one cell to another cell, or due to reasons such as adjustment of wireless transmission service load, activation of operation maintenance, device failure, etc., in order to ensure communication continuity and service quality, the system needs to transfer a communication link between the terminal device and an original cell to a new cell, i.e., to perform a handover procedure.

Taking an Xn interface handover process as an example, the method is suitable for a cell handover process of a Long Term Evolution (LTE) system and an NR system, and as shown in fig. 1, the method is divided into the following three stages:

phase 1 (including steps 1 to 5), handover preparation: including measurement control and reporting, handover requests and acknowledgements

Stage 2 (comprising steps 6 to 8), the handover is performed: the terminal device immediately executes a handover process after receiving the handover command, that is, the terminal device disconnects the source cell and connects with the target cell (for example, executes random access, and sends a Radio Resource Control (RRC) handover completion message to the target network device, etc.); and (4) state transfer and data forwarding of a Secondary Node (SN).

Stage 3 (including steps 9 to 12), handover complete: the target cell and (AMF) and the User Plane Function (UPF) perform Path switching (Path Switch), releasing the terminal device context of the source network device.

A brief description of the conditional handle follows.

Aiming at the problems of frequent switching and easy failure of switching in a high-speed mobile scene and a high-frequency deployment scene, 3GPP is currently discussing the introduction of a conditional handover to LTE and NR systems. As shown in fig. 2, the terminal device performs cell measurement, configuration and reporting with the source network device; switching preparation is carried out on source network equipment and target network equipment; and when the terminal equipment meets the triggering condition, switching to the target network equipment. In the Conditional Handover, a Handover (HO) command (command) is configured in advance for the terminal device, so that the problem that the terminal device is late when to be handed over due to too long Handover preparation time is avoided. And for a high-speed rail scene, the operation track of the terminal device is specific, so the source network device can allocate the target network device to the terminal device in advance, and the HO command includes a condition for triggering the terminal device to perform handover, and when the allocated condition is satisfied, the terminal device initiates an access request to the target network device.

The 3GPP RAN2#104 has agreed conditional handover from the conference and supports configuration of a plurality of target cells in a handover command for conditional handover, and the terminal device determines which target cell to access based on the configured conditions.

In the 3GPP mobility enhancement subject, an optimization method for reducing the interruption time during cell handover is proposed, which includes the following two architectures:

1) when cell switching is carried out, target network equipment is added as an auxiliary node, then the auxiliary node is changed into a main node through role change signaling, and finally source network equipment is released; therefore, the effect of reducing the interruption time during cell switching is achieved.

2) Based on the existing handover flow, when receiving a conditional handover command, a terminal device (User Equipment, UE) continues to maintain connection with a source network device, and simultaneously initiates random access to a target network device, until the terminal device and the target network device complete access, the connection of a source base station is released.

For the process flow of sending and receiving PDCP data packets, as shown in fig. 3, for example, a terminal device is used, after a sending end of a PDCP entity receives a PDCP SDU from an upper layer, the sending end of the PDCP entity associates a COUNT value (COUNT) of the received PDCP SDU with TX _ NEXT, and sets a PDCP SN corresponding to the PDCP SDU to be TX _ NEXT module 2^{[pdcp-SN-SizeUL]}TX _ NEXT plus 1.

The receiving end of the PDCP entity reorders the received PDCP PDUs based on the t-reordering timer, and delivers the PDCP SDUs to a higher layer in sequence when the t-reordering times out or a state variable meets a condition (for example, when RCVD _ COUNT is RX _ DELIV). Specifically, when the PDCP PDU is received and RX _ DELIV < RX _ NEXT and t-reordering is not running, the t-reordering is turned on and RX _ REOERD is set to RX _ NEXT. And when the t-reordering times out, PDCP SDUs are sequenced to a higher layer.

Wherein, TX _ NEXT indicates the COUNT value of the NEXT PDCP SDU to be sent; RX _ REOERD, which represents the COUNT value corresponding to the PDCP data PDU triggering t-reordering; RX _ NEXT indicating the COUNT value of the NEXT PDCP SDU to be received; RX _ DELIV, indicating the first COUNT value, still in a wait for acknowledgement state, not submitted to the upper layer; RCVD _ COUNT, the COUNT value of the PDCP data PDU which is received currently is identified. The length of the COUNT is 32 bits, and the format diagram of the COUNT is shown in fig. 4, and is composed of Hyper Frame Number (HFN) and PDCP SN, which are [ HFN, SN ]. The HFN length is 32-PDCP SN length.

The data packet processing method of the embodiment of the present application 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), an 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.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 5. 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. Optionally, the Network device 110 may be a Base Transceiver 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 may be a Network device in a Mobile switching center, a relay Station, 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., to 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. 5 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. 5 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. 6, 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 transmitting electronic device sets the PDCP SN and/or the state variable of the PDCP data packet based on the first information.

In the embodiment of the present invention, the first information is a pre-agreed PDCP SN and/or PDCP SN allocation rule, that is, the PDCP SN and/or PDCP SN allocation rule may be predefined; or, the first information is a PDCP SN and/or a PDCP SN allocation rule sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device. When the method is implemented, the first sending electronic device periodically sends the PDCP SN and/or the PDCP SN distribution rule to the second sending electronic device and/or the receiving electronic device; alternatively, the first transmitting electronic device may assign a PDCP SN and/or a PDCP SN assignment rule to the second transmitting electronic device and/or the receiving electronic device based on an event. Wherein the event comprises at least one of: notifying the subsequent shared PDCP SN list/PDCP SN identification/PDCP SN bitmap/PDCP SN pattern (pattern), PDCP SN pattern change and PDCP SN allocation rule change.

Wherein the pre-agreed PDCP SN or the PDCP SN sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device includes at least one of: PDCP SN, PDCP SN list, PDCP SN Bitmap, PDCP SN pattern. The PDCP SN assignment rule refers to how to assign PDCP SNs to PDCP data packets.

In particular implementation, the PDCP SN and/or PDCP SN assignment rule is sent via at least one of: RRC signaling, MAC CE, physical layer signaling bearer and PDCP packets; wherein, the PDCP packet includes: at least one of a PDCP control packet and a PDCP data packet. That is, the first transmitting electronic device transmits the PDCP SN and/or the PDCP SN allocation rule to the second transmitting electronic device and/or the receiving electronic device through any one of RRC signaling, MAC CE, physical layer signaling bearer, PDCP control packet, and PDCP data packet. Optionally, the PDCP SNs interacted between the first transmitting electronic device and the second transmitting electronic device and between the first transmitting electronic device and the receiving electronic devices may also be replaced with COUNTs corresponding to the PDCP SNs; that is, the first sending electronic device sends the COUTN corresponding to the PDCP SN to the second sending electronic device or the receiving electronic device.

In this embodiment of the present invention, the first sending electronic device is a source network device, and the receiving electronic device is a terminal device. Or, the first sending electronic device is a source network device, and the receiving electronic device is a target network device. Or, the first sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a terminal device. Or, the first sending electronic device is a target network device, and the receiving electronic device is a terminal device. Or, the first sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a terminal device. Or, the first sending electronic device is a target network device, and the receiving electronic device is a source network device. Or, the first sending electronic device is a terminal device, and the receiving electronic device is a target network device and/or a source network device. Or, the first sending electronic device is a first sending entity in a terminal device, and the receiving electronic device is a first receiving entity in the terminal device. Or the first sending electronic device is a first sending entity in the terminal device, the second sending electronic device is a second sending entity in the terminal device, and the receiving electronic devices are target network devices and source network devices; or, the first sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device. Or, the first sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device.

It should be noted that the functions implemented by the first receiving entity and the second receiving entity in the terminal device may also be implemented by a function module in the terminal device.

In some embodiments, the PDCP SN and/or PDCP SN allocation rule is determined by the first transmitting electronic device, or the PDCP SN is determined by the second transmitting electronic device, or the PDCP SN is determined by both the first transmitting electronic device and the second transmitting electronic device. In particular implementation, the PDCP SN and/or PDCP SN assignment rule is determined according to at least one of: traffic characteristics, Quality of Service (QoS) requirements, Scheduling conditions, Semi-Persistent Scheduling (SPS) configuration information, Configuration Grant (CG) configuration information, activated carrier information, activated SPS information, activated CG information, traffic volume size, traffic type, cell load, cell interference, and cell channel Quality.

In the embodiment of the present invention, when the PDCP packet is a PDCP control PDU, the PDCP control PDU has at least one of the following attributes:

1) the PDCP control PDU carries the information of the PDCP SN and/or carries the indication of the control information type of the contained PDCP SN information. Wherein the PDCP control PDU is a new PDCP control PDU type different from the existing PDCP control PDU type. Optionally, the new PDCP control PDU type is a type other than ROHC feedback and PDCP status report; optionally, the new PDCP control PDU type is used to indicate that the PDU carries PDCP SN information; included in the PDCP control PDU is an indication of the control information type of the PDCP SN information. Fig. 7 shows a schematic diagram of a PDCP control PDU type and type indication, where when a bit value of the type indication is 000, the corresponding PDCP control PDU type is a PDCP status report; when the bit value indicated by the type is 001, the corresponding PDCP control PDU type is ROHC feedback; when the bit value of the type indication is 010, the corresponding PDCP control PDU type is a PDCP SN; and when the bit value of the type indication is 011-111, the corresponding PDCP control PDU type is a reserved value.

And the new PDCP control PDU carries the information of the PDCP SN. Wherein, the PDCP control PDU may include at least one of the following information: the position of the PDCP SNs in the PDCP data packets, such as the PDCP SNs, are located in the header of the PDCP data packets or within the data packets.

2) And carrying the commonly maintained PDCP SN in the PDCP control PDU.

3) And carrying at least one of a PDCP SN Bitmap in the PDCP control PDU, a starting SN corresponding to the PDCP SN Bitmap and a termination SN corresponding to the PDCP SN Bitmap.

4) And carrying at least one of a PDCP SN pattern in the PDCP control PDU, a starting SN corresponding to the PDCP SN pattern, and a terminating SN corresponding to the PDCP SN pattern.

5) And carrying the starting SN and the terminating SN in the PDCP SN commonly maintained in the PDCP control PDU.

6) Carrying the number of the PDCP SNs which are maintained together in the PDCP control PDU;

7) carrying the length of the PDCP SN Bitmap which is maintained together in the PDCP control PDU;

8) carrying the length or period of the PDCP SN pattern which is commonly maintained in the PDCP control PDU;

9) and carrying the commonly maintained PDCP SN list in the PDCP control PDU.

Optionally, the PDCP control PDU includes at least one PDCP SN.

The first sending electronic device is allocated with a PDCP SN/PDCP SN Bitmap/PDCP SN pattern/PDCP SN list, or the PDCP SN/PDCP SN Bitmap/PDCP SN pattern/PDCP SN list used by the first sending electronic device; and/or the PDCP SN/PDCP SN Bitmap/PDCP SN pattern/PDCP SN list distributed for the second electronic equipment, or the PDCP SN/PDCP SN Bitmap/PDCP SN pattern/PDCP SN list used by the second sending electronic equipment belongs to the PDCP SN/PDCP SN Bitmap/PDCP SN list commonly maintained. For example, the PDCP SN list allocated to the first transmitting electronic device is 1,3, or 5, and/or the PDCP SN list allocated to the second transmitting electronic device is 0,2, or 4; then 0,2,4, or, 1,3,5, or 0, 1, 2, 3, 4, 5 belongs to the commonly maintained PDCP SN list.

In this embodiment of the present invention, the PDCP SNs sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device include two types: the first is an actual PDCP SN, and the second is an actual PDCP SN and a virtual PDCP SN. The actual PDCP SN is also referred to as a second PDCP SN in this embodiment, and the virtual PDCP SN is also referred to as a first PDCP SN in this embodiment. The first PDCP SN of the first transmitting electronic device is a PDCP SN maintained by the first transmitting electronic device itself, and has no association with the first PDCP SN of the second transmitting electronic device.

When the PDCP SN sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device is the actual PDCP SN, the process flow of setting the PDCP SN and/or the state variable of the PDCP data packet by the first sending electronic device, as shown in fig. 8, includes:

step 1a, setting a value of TX-NEXT and/or an initial value of TX-NEXT based on the first information.

Here, the initial value of the TX-NEXT is not necessarily 0; the initial value of TX-NEXT is related to the PDCP SN and/or PDCP SN distribution rule agreed in advance; alternatively, the initial value of TX-NEXT is related to the PDCP SN and/or PDCP SN allocation rule that the first transmitting electronic device transmits to the second transmitting electronic device and/or receiving electronic device.

And step 1b, correlating the COUNT of the PDCP data packet with the TX-NEXT value.

And step 1c, setting the PDCP SN of the PDCP data packet as a value obtained by taking a module of a function of the size of the PDCP SN by utilizing TX-NEXT.

In some embodiments, the PDCP SN of a PDCP packet can be set to TX-NEXT module 2^{[PDCPSN-SizeDL]}。

In other embodiments, the PDCP SN of the PDCP data packet can be set to TX-NEXT module 2^{[PDCPSN-SizeUL]}。

And step 1d, setting the value of TX-NEXT as the NEXT PDCP SN adjacent to the current PDCP SN based on the first information.

Optionally, any one of the steps 1a to 1d is optional.

When the PDCP SNs sent by the first sending electronic equipment to the second sending electronic equipment and the receiving electronic equipment are the first PDCP SN and the second PDCP SN, the receiving electronic equipment utilizes the second PDCP SN to process the PDCP data packets between the PDCP entities; the first sending electronic device and the second sending electronic device use the first PDCP SN of the first sending electronic device to perform at least one of packet packing of the PDCP data packets, transmission of the PDCP data packets, setting of the PDCP SNs, maintenance of state variables of the PDCP data packets and PDCP data packet processing in the PDCP entity; the first sending electronic device sets the PDCP SN of the PDCP data packet according to the first PDCP SN, which means that the first sending electronic device considers only the PDCP SN of itself and is not affected by other PDCP entities. Even if the first transmitting electronic device and the second transmitting electronic device both transmit PDCP SNs to the receiving electronic device, the first PDCP SN of the first transmitting electronic device is a consecutive integer starting from 0, an initial value of TX-NEXT is 0, and the value of TX-NEXT is incremented by 1 every time a PDCP PDU is generated.

When the PDCP SNs sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device are the first PDCP SN and the second PDCP SN, the sending modes of the first PDCP SN and the second PDCP SN include any one of the following:

the first PDCP SN and the second PDCP SN are carried in the PDCP data packet;

the first PDCP SN is carried in a packet header of the PDCP data packet, and the second PDCP SN is carried in the packet header of the PDCP data packet or in the PDCP data packet;

the second PDCP SN is carried in a packet header of the PDCP data packet, and the first PDCP SN is carried in the packet header of the PDCP data packet or in the PDCP data packet;

the first PDCP SN is carried in a packet header of the PDCP data packet or in a data packet, and the second PDCP SN is sent through special signaling;

the second PDCP SN is carried in a packet header of the PDCP data packet or in a data packet, and the first PDCP SN is sent through special signaling;

the first PDCP SN and the second PDCP SN are transmitted through dedicated signaling.

When the PDCP SNs sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device are the first PDCP SN and the second PDCP SN, or only one PDCP SN, the PDCP data packet further includes first indication information indicating at least one of: the type of the PDCP data packet, the format of the PDCP data packet and PDCP SN information carried by the PDCP data packet. Wherein, the type of the PDCP data packet refers to whether the PDCP data packet is an existing PDCP data packet type or a new PDCP data packet type; the format of the PDCP data packet refers to whether the PDCP data packet is in a new format or an original format, and comprises which PDCP SN, including at least one of several PDCP SNs; the PDCP SN information carried by the PDCP data packet refers to the PDCP SN carried by the PDCP data packet, for example, the PDCP data packet carries a first PDCP SN, or a second PDCP SN, or carries a first PDCP SN and a second PDCP SN. When the PDCP SN information carried by the PDCP data packet is the first PDCP SN or the second PDCP SN carried by the PDCP data packet, another PDCP SN not carried by the PDCP data packet may be sent by a dedicated signaling, or another PDCP SN may not exist or be used. Here, the first indication information may be identified by an R bit in a PDCP data packet.

In some embodiments, the PDCP data packet further comprises second indication information indicating at least one of:

whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN. Wherein, the precedence order of the second PDCP SN and the first PDCP SN means that when both the second PDCP SN and the first PDCP SN carry one of the following, both the second PDCP SN and the first PDCP SN are in a PDCP data packet, both the header of the data packet, one in the header of the data packet, and one in the data packet, the first PDCP SN is in front, and the second PDCP SN is in back; alternatively, the first PDCP SN is behind and the second PDCP SN is in front.

In a specific implementation, the content indicated by the first indication information and/or the second indication information may be determined by an indication of a network device or determined according to predefined information. The network equipment sends the content indicated by the first indication information and/or the second indication information to the first sending equipment and/or the second sending equipment; alternatively, the first transmitting electronic device determines the content indicated by the first indication information and/or the second indication information according to predefined information.

When the PDCP SNs sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device include an actual PDCP SN and a virtual PDCP SN, the first sending electronic device sets another optional process flow of the state variables of the PDCP data packet according to the virtual PDCP SN, including at least one of: the source network device sets the initial value of TX-NEXT to 0, and when the source network device generates the first PDCP SDU, the PDCP SN corresponding to the first PDCP SDU is set to 0, namely TX-NEXT module 2^[12](ii) a Suppose PDCP-SN-SizeDL is 12, COUNT is 1, HFN is 0, and TX-NEXT is 0+1 is 1. When the source network equipment generates a second PDCP SDU, determining the corresponding TX-NEXT according to the current value 1 of TX-NEXTThe COUNT value of the PDCP PDU of the second PDCP SDU is 1, and the PDCP SN is 1; the value of TX-NEXT is 1 on the basis of the current value of 1, namely the value of TX-NEXT is 2; and so on.

Another optional processing flow for the first sending electronic device to set the status variable of the PDCP data packet when the PDCP SNs sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device are the first PDCP SN and the second PDCP SN, is as follows:

step 2a, setting a value of TX-NEXT based on the first PDCP SN.

And step 2b, setting an initial value of TX-NEXT based on the first PDCP SN.

Here, the initial value of the TX-NEXT is not necessarily 0; the initial value of TX-NEXT is related to the pre-agreed first PDCP SN and/or PDCP SN distribution rule; alternatively, the initial value of TX-NEXT is related to the first PDCP SN and/or PDCP SN assignment rule that the first transmitting electronic device transmits to the second transmitting electronic device and/or receiving electronic device.

Step 2c, associating the COUNT value COUNT of the PDCP data packet with the value of TX-NEXT;

and step 2d, setting the PDCP SN of the PDCP data packet as a value obtained by taking a module of a function of the size of the PDCP SN by utilizing TX-NEXT.

And step 2e, setting the value of TX-NEXT as the NEXT PDCP SN adjacent to the current PDCP SN based on the first PDCP SN.

Optionally, any of the above steps 2a to 2d is optional.

As shown in fig. 9, another optional processing flow of the data packet processing method provided in the embodiment of the present invention includes the following steps:

step S301, the receiving electronic device receives PDCP SNs and/or PDCP SN assignment rules of at least two transmitting electronic devices.

In the embodiment of the present invention, the PDCP SNs and/or the PDCP SN assignment rules of the at least two transmitting electronic devices may be transmitted from any transmitting electronic device to a receiving electronic device.

Alternatively, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices may be transmitted by a specific one of the transmitting electronic devices to the receiving electronic device.

Alternatively, the PDCP SNs and/or PDCP SN assignment rules of said at least two transmitting electronic devices may be transmitted by each transmitting electronic device to a receiving electronic device; i.e. the first transmitting electronic device transmits PDCP SNs and/or PDCP SN allocation rules of the at least two transmitting electronic devices to the receiving electronic device, the second transmitting electronic device also transmits PDCP SNs and/or PDCP SN allocation rules of the at least two transmitting electronic devices to the receiving electronic device.

Or, the PDCP SN and/or PDCP SN assignment rule of each transmitting electronic device is transmitted to the receiving electronic device by the transmitting electronic device itself and/or by another transmitting electronic device; that is, the first transmitting electronic device transmits the PDCP SN and/or PDCP SN allocation rule of the first electronic device to the receiving electronic device, and the second electronic device transmits the PDCP SN and/or PDCP SN allocation rule of the second electronic device to the receiving electronic device. Or, the first transmitting electronic device transmits the PDCP SN and/or the PDCP SN allocation rule of the second electronic device to the receiving electronic device in addition to the PDCP SN and/or the PDCP SN allocation rule of the first electronic device to the receiving electronic device; and the second electronic device transmits the PDCP SN and/or PDCP SN allocation rule of the first electronic device to the receiving electronic device in addition to the PDCP SN and/or PDCP SN allocation rule of the second electronic device. Alternatively, the first transmitting electronic device transmits the PDCP SN and/or PDCP SN allocation rule of the second electronic device to the receiving electronic device, and the second transmitting electronic device transmits the PDCP SN and/or PDCP SN allocation rule of the first electronic device to the receiving electronic device.

It should be noted that, the descriptions for the PDCP SNs and the PDCP SN allocation rules in the embodiment of the present invention are the same as the step S201, and are not described herein again. Wherein the specification for the PDCP SNs and the PDCP SN allocation rules may include at least one or more of: the PDCP SNs and the PDCP SN allocation rules are determined by who, according to what parameters, the PDCP SNs and the PDCP SN allocation rules are determined, and the forms and contents of the PDCP SNs and the PDCP SN allocation rules.

Step S302, the receiving electronic device processes the PDCP data packet according to the PDCP SN and/or the PDCP SN distribution rule.

In the embodiment of the present invention, the processing of the PDCP data packet includes at least one of processing the PDCP data packet in the PDCP entity and processing the PDCP data packet between the PDCP entities. Wherein the processing comprises at least one of: reordering PDCP data packets, detecting redundancy of the PDCP data packets, and deleting the PDCP data packets. For example, if the receiving electronic device receives a first PDCP data packet sent by the first sending electronic device and a second PDCP data packet sent by the second sending electronic device; the receiving electronic equipment processes the first PDCP data packet in a PDCP entity, and processes the second PDCP data packet in the PDCP entity; the processing of the receiving electronic device for the first PDCP data packet and the second PDCP data packet is processing PDCP data packets between PDCP entities. Accordingly, the receiving electronic device needs to receive the PDCP data packet and/or the PDCP control PDU before processing the PDCP data packet.

When the PDCP SNs include a first PDCP SN and a second PDCP SN, the receiving electronic device processes PDCP data packets according to the PDCP SNs, including:

the receiving electronic equipment carries out the treatment in a PDCP entity on the PDCP data packet according to the first PDCP SN; and/or the receiving electronic equipment carries out the treatment among the PDCP entities on the PDCP data packet according to the second PDCP SN.

In some embodiments, the receiving electronic device replaces the first PDCP SN with a second PDCP SN corresponding to the first PDCP SN after completing the PDCP entity processing on the PDCP data packet.

In the embodiment of the present invention, the description of performing the inter-entity PDCP processing and the intra-entity PDCP processing on the PDCP data packet is the same as the related description in the step S201, and is not repeated here.

In particular, whether the receiving electronic device processes the PDCP data packet in and/or among PDCP entities is determined by a preset or network device configuration or by the receiving electronic device according to at least one of the PDCP SN and a status variable. For example, the network device configures the receiving electronic device to deliver the PDCP data packets to the higher layer in sequence, and if the t-reordering timer expires, the PDCP entity of the receiving electronic device delivers the PDCP data packets to the higher layer in sequence if the in-sequence delivery in the PDCP entity is configured; and/or, in the case of RCVD-COUNT ═ RX-DELIV, the PDCP entity of the receiving electronic device delivers the PDCP packets in order to the higher layers.

The processing of the PDCP data packet sent by the receiving electronic device to the first sending electronic device or the processing of the PDCP data packet sent by the receiving electronic device to the first sending entity of the sending electronic device belongs to the processing of the PDCP data packet in the PDCP entity. Similarly, the processing of the PDCP data packet sent by the receiving electronic device for the second sending electronic device, or the processing of the PDCP data packet sent by the receiving electronic device for the second sending entity of the sending electronic device, belongs to the processing of the PDCP data packet in the PDCP entity. After the receiving electronic device performs entity processing on the PDCP data packets sent by the first sending electronic device and the second sending electronic device, or after the receiving electronic device performs entity processing on the PDCP data packets sent by the first sending entity and the second sending entity of the sending electronic device, the receiving electronic device performs unified processing on the PDCP data packets sent by the first sending electronic device and the second sending electronic device, or performs unified processing on the PDCP data packets sent by the first sending entity and the second sending entity of the sending electronic device is called as PDCP data packet processing between PDCP entities. Optionally, the processing in the PDCP entity may not be performed, and only the processing between the PDCP entities may be performed, or the processing in the PDCP entity may not be performed, and only the processing in the PDCP entity may be performed.

It should be noted that, when the receiving electronic device is a terminal device, the receiving entity in the terminal device may be a first PDCP entity of the terminal device and/or a second PDCP entity of the terminal device; alternatively, the receiving entity in the terminal device may also be a first functional module in the PDCP entity of the terminal device and/or a second functional module in the PDCP entity of the terminal device. Correspondingly, when the sending electronic device is a terminal device, the sending entity in the terminal device may be a first PDCP entity in the terminal device and/or a second PDCP entity in the terminal device, or the sending entity in the terminal device may also be a first function module in the PDCP entity in the terminal device and/or a second function module in the PDCP entity in the terminal device.

In the embodiment of the present invention, the receiving electronic device is a terminal device, and the sending electronic device is a source network device and/or a target network device; or, the receiving electronic device is a first receiving entity in the terminal device, and the sending electronic device is a first sending entity in the terminal device; or, the receiving electronic device is a source network device and/or a target network device, and the sending electronic device is a terminal device; or, the receiving electronic device is a target network device, and the sending electronic device is a source network device; or, the receiving electronic device is a source network device, and the sending electronic device is a target network device; or, the receiving electronic device is a source network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device; or, the receiving electronic device is a target network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device.

The PDCP packet processing method according to the embodiment of the present invention is described in detail below for a situation in which a DRB bearer or an SRB bearer is supported by a terminal device and is transmitted through two paths, namely, a source network device and a target network device, at the same time, the source network device sends the DRB bearer or the SRB bearer to the terminal device, and the target network device also sends the DRB bearer or the SRB bearer to the terminal device.

Taking the PDCP SN interacted between the source network device and the target network device as the actual PDCP SN, a detailed processing flow of the PDCP data packet processing method is shown in fig. 10, and includes:

step S401, the source network device and the target network device interact PDCP SN or PDCP SN distribution rules.

In this embodiment of the present invention, a source network device may be considered as a first sending electronic device, and a target network device may be considered as a second sending electronic device. The source network equipment and the target network equipment interact PDCP SN or PDCP SN distribution rules to determine the PDCP SN used by the source network equipment when the source network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission; and determining the PDCP SN used by the target network equipment when the target network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission. Wherein, the source network device and the target network device interact PDCP SN and/or PDCP SN allocation rules, which means that the source network device sends the determined PDCP SN and/or PDCP SN allocation rules adopted when the target network device and the terminal device carry out DRB bearing or SRB bearing transmission to the target network device; or the source network equipment sends the PDCP SN and/or the PDCP SN distribution rule adopted by the source network equipment when the source network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission and the determined PDCP SN and/or the PDCP SN distribution rule adopted by the target network equipment and the terminal equipment when the target network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission to the target network equipment; or the source network equipment sends the PDCP SN and/or the PDCP SN distribution rule adopted when the source network equipment and the terminal equipment carry out Data Resource Bearer (DRB) or signaling Bearer (SRB) transmission to the target network equipment; and the target network equipment sends the PDCP SN and/or the PDCP SN distribution rule adopted by the target network equipment and the terminal equipment when the target network equipment carries out DRB bearing or SRB bearing transmission to the source network equipment. As shown in fig. 11, the source network device interacts with the target network device for PDCP SN or PDCP SN allocation rule, which may be an interaction between the PDCP entity of the source network device and the PDCP entity of the target network device.

For example, in the handover procedure, the source network device determines to perform a handover procedure in which the terminal device and two network devices perform simultaneous transmission, such as Enhanced mobile broadband (eMBB) based on conditional handover. For DRB 1, the source network equipment determines to adopt a bearing split mode to carry out transmission between the source network equipment and the target network equipment and between the target network equipment and the terminal equipment; as shown in fig. 12, according to the sequence of PDCP SDUs, the 1 st, 3 rd, 5 th, 7 th PDCP SDU is transmitted from the source network device, and the corresponding PDCP SN list is 1,3,5,7 th or PDCP SN pattern is {010101. }; a 0,2,4,6.. PDCP SDU is transmitted from the target network device with a corresponding PDCP SN list of 0,2,4,6.. or PDCP SN pattern of {101010. }. And the source target network interacts the determined PDCP SN list or PDCP SN pattern transmitted by the target network and the PDCP SDU to the target network equipment.

The interactive PDCP SNs and/or PDCP SN assignment rules may be determined by the source network device, determined by the target network device, or determined by both the source network device and the target network device. Optionally, the PDCP SNs and/or the PDCP SNs of the source network device and the target network device may be determined according to service characteristics, QoS requirements, scheduling conditions, SPS configuration information, CG configuration information, activated carrier information, activated SPS information, activated CG information, traffic volume, service type, cell load, cell interference, cell channel quality, etc.

It should be noted that the interactive SN may be replaced by a COUNT corresponding to the SN.

Step S402, the source network device and the target network device set the PDCP SN and/or the state variable of the PDCP data packet according to the PDCP SN or the PDCP SN distribution rule.

Taking the source network device as an example, when the source network device generates the first PDCP SDU, it is determined that the PDCP SN of the PDCP data packet corresponding to the first PDCP SDU is 1, TX _ NEXT is 1, and COUNT is 1 according to the determined PDCP SN list or PDCP SN pattern (assuming that HFN is 0). When the source network device generates the second PDCP SDU, it determines, according to the determined PDCP SN list or PDCP SN pattern, that the PDCP SN of the PDCP data packet corresponding to the second PDCP SDU is 3, TX _ NEXT is 3, COUNT is 3 (assuming that HFN is 0), and so on.

Step S403, the source network device sends the interactive PDCP SN or PDCP SN allocation rule to the terminal device.

In some embodiments, the source network device sends the PDCP SN pattern or PDCP SN bitmap or PDCP SN list used by the source network device to the terminal device using the PDCP control PDU. Optionally, the PDCP control PDU includes at least one PDCP sn. Correspondingly, the terminal equipment determines the PDCP SN used by the target network equipment according to the PDCP SN pattern or the PDCP SN bitmap or the PDCP SN list sent by the source network equipment; for example, the consecutive PDCP SNs starting from 0 are removed from the PDCP SN used by the source network device, i.e., the PDCP SN used by the target network device.

In other embodiments, the source network device uses different PDCP control PDUs to send the PDCP SN pattern or PDCP SN bitmap or PDCP SN list used by the source network device or the target network device to the terminal device. Optionally, the PDCP control PDU includes at least one PDCP SN. Correspondingly, the terminal equipment determines the PDCP SN used by the source network equipment and/or the target network equipment according to the PDCP SN pattern or the PDCP SN bitmap or the PDCP SN list sent by the source network equipment. Specifically, the source network device may further send the PDCP SN pattern, or the PDCP SN bitmap, or the PDCP SN list to the terminal device through RRC signaling, MAC CE, physical layer signaling bearer, or PDCP data packet.

In specific implementation, a format schematic diagram of the PDCP control PDU carrying the PDCP SN bitmap indication is shown in fig. 13. Wherein, the D/C value is 1, which represents that the PDCP PDU is a PDCP control PDU, and the PDU type value is an SN interactive type or a PDCP SN type; start FMC, representing COUNT corresponding to the initial SN of the interaction; the PDCP SN bitmap indicates whether each SN from the starting SN is used by the source network device.

Step S404, the terminal device determines whether to deliver PDCP data packet to the higher layer according to the interactive PDCP SN or PDCP SN distribution rule.

In some embodiments, the terminal device determines PDCP SN information of PDCP data packets transmitted between the terminal device and the source network device and PDCP SN information of PDCP data packets transmitted between the terminal device and the target network device according to the received PDCP SN bitmap, PDCP SN list, or PDCP SN pattern. For example, the terminal device determines that the PDCP SNs used by the source network device are 1,3,5,7 … and the PDCP SNs used by the target network device are 0,2,4,6, 8 ….

The terminal equipment determines whether the condition of delivering the PDCP data packet to the high layer is met according to the state variable of the receiving end, the PDCP SN list or the PDCP SN pattern or the PDCP SN bitmap and the PDCP SN of the PDCP data packet. If t-reordering is 10ms and earlier than t-reordering timeout, the condition of RCVD _ COUNT-RX _ EDLIV is satisfied, for example, when RCVD _ COUNT-RX _ DELIV-7, the PDCP entity of the terminal device, for example, the PDCP entity or the functional module of the terminal device corresponding to the source network device triggers the delivery of PDCP data packets to the higher layer in the order of PDCP SNs. In the embodiment of the invention, before delivering the PDCP data packet, the terminal equipment needs to carry out reordering processing, redundancy detection processing and deletion processing on the received PDCP data packet.

Taking the PDCP SNs interacted between the source network device and the target network device as a first PDCP SN and a second PDCP SN as examples, the first PDCP SN being a virtual PDCP SN, the second PDCP SN being an actual PDCP SN; another detailed processing flow of the PDCP data packet processing method, as shown in fig. 14, includes:

step S501, the source network device and the target network device interact PDCP SN or PDCP SN distribution rules.

In this embodiment of the present invention, a source network device may be considered as a first sending electronic device, and a target network device may be considered as a second sending electronic device. The source network equipment and the target network equipment interact PDCP SN or PDCP SN distribution rules to determine the PDCP SN used by the source network equipment when the source network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission; and determining the PDCP SN used by the target network equipment when the target network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission. Wherein, the source network device and the target network device interact PDCP SN and/or PDCP SN allocation rules, which means that the source network device sends the determined PDCP SN and/or PDCP SN allocation rules adopted when the target network device and the terminal device carry out DRB bearing or SRB bearing transmission to the target network device; or the source network equipment sends the PDCP SN and/or the PDCP SN distribution rule adopted by the source network equipment when the source network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission and the determined PDCP SN and/or the PDCP SN distribution rule adopted by the target network equipment and the terminal equipment when the target network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission to the target network equipment; or the source network equipment sends the PDCP SN and/or the PDCP SN distribution rule adopted when the source network equipment and the terminal equipment carry out DRB bearing or SRB bearing transmission to the target network equipment; and the target network equipment sends the PDCP SN and/or the PDCP SN distribution rule adopted by the target network equipment and the terminal equipment when the target network equipment carries out DRB bearing or SRB bearing transmission to the source network equipment.

Step S502, the source network device and the target network device use the virtual PDCP SN and the actual PDCP SN to perform packet packing and transmission of PDCP data packets, and maintain the sending-end PDCP SN and/or state variables.

In the following, the source network device is taken as an example, and the target network device performs the same operation as the source network device.

The source network device uses the virtual PDCP SNs to perform packet packing of PDCP data packets, transmission of PDCP PDUs, maintenance of the PDCP SNs and/or state variables of the sending end. For example, the source network device sets the TX _ NEXT initial value to 0; when the source network device generates the first PDCP SDU, the PDCP SN corresponding to the first PDCP SDU is set to 0, namely TX _ NEXT module 2^[12]Assuming that PDCP-SN-sizeddl is 12 and COUNT is 1 (HFN is 0); then, another TX _ NEXT is 0+1 is 1. When the source network device generates a second PDCP SDU, it determines that the COUNT of the second PDCP PDU is 1 and the SN is 1 according to the current TX _ NEXT value (1). Then, the value of TX _ NEXT is incremented by 1 to 2, and so on.

The PDCP PDUs may carry virtual PDCP SN values, for example, the virtual PDCP SN values carried in the PDCP PDUs sent by the source network device are 1 ', 2', 3 ', 4' …, a group of ordered numerical values or letters or identifiers, and the like.

The PDCP PDUs may also carry actual PDCP SN values, for example, the actual PDCP SN values carried in the PDCP PDUs transmitted by the source network device are 1,3,5, and 7 …, and the actual PDCP SN values carried in the PDCP PDUs transmitted by the target network device are 2,4,6, and 8 ….

The format diagrams of the PDCP PDUs carrying the actual PDCP SNs and the virtual PDCP SNs are shown in fig. 15a, fig. 15b, and fig. 15c, respectively. In fig. 15a and 15b, the virtual PDCP SNs are located in the first byte and the second byte, and the actual PDCP SNs are located in the third byte and the fourth byte. In fig. 15c, the virtual PDCP SNs are located in the first, second and third bytes, and the actual PDCP SNs are located in the fourth, fifth and sixth bytes, or the virtual PDCP SNs are located in the first and second bytes, and the actual PDCP SNs are located in the fifth and sixth bytes, and the third byte has both the actual PDCP SN and the virtual PDCP SN. Optionally, the virtual PDCP SN is before and the temporal PDCP SN is after; of course, the virtual PDCP SN can also be followed, and the actual PDCP SN can be preceded.

Step S503, the terminal device receives the PDCP PDUs from the source network device and the target network device, and performs in-entity processing on the PDCP PDUs based on the virtual PDCP SNs.

In the embodiment of the invention, the terminal equipment executes operations such as reordering in an entity, sequential delivery in the entity and the like according to the virtual PDCP SN. Whether to perform reordering within an entity and in-order delivery within an entity may be predefined or may be configured by a network device.

The processing of the PDCP PDU includes: and the terminal equipment maintains t-reordering based on the virtual PDCP SN and reorders in the entity. The RX _ COUNT is set based on the virtual PDCP SN. The virtual PDCP SN based maintenance state variables such as RX _ NEXT, RX _ REORD, RX _ DELIV. And performing redundant packet deletion in the entity based on the virtual PDCP SN, namely deleting the data packets which are received and have the same virtual PDCP SN. In-order delivery within the entity is performed based on the virtual PDCP SN. Optionally, the virtual PDCP SN is replaced with the actual PDCP SN when in-sequence delivery is performed in the entity or when PDCP packets are delivered to an upper layer. And decompressing the PDCP data packet according to the virtual PDCP SN. And decrypting the PDCP data packet according to the virtual PDCP SN. And performing integrity protection verification of the PDCP data packet according to the virtual PDCP SN.

In implementation, the initial RX _ NEXT is set to 0.RX _ DELIV is set to 0. Assume that the virtual PDCP SN of the PDCP packet that should be received is 0.1.2.3.4. The virtual PDCP SN of the currently received PDCP PDU is 4, COUNT _ COUNT is 4, and RX _ NEXT is set to 4+ 1-5 since RCVD _ COUNT > is RX _ NEXT, since t-Reordering is not running and RX _ DELIV < RX _ NEXT, a Reordering timer is started, and RX _ REORD is set to RX _ NEXT 5. Then, the terminal device receives the PDCP PDU with SN 2 again. Then the corresponding COUNT is RCVD _ COUNT 2, and put into the reordering buffer queue, and do not update RX _ NEXT; at this time, RCVD _ COUNT < RX _ NEXT. When the timer expires, PDCP PDUs with COUNT 2 and COUNT 5 are delivered to the upper layer in ascending order.

Step S504, the terminal device processes the PDCP PDU according to the actual PDCP SN among the entities.

In the embodiment of the invention, the processing among the PDCP entities comprises operations of reordering among the entities, delivering in sequence among the entities, deleting redundant packets among the entities and the like.

As shown in fig. 16, the PDCP PDUs, such as PDCP data PDUs, of the PDCP entities sent by the source network device and the target network device to the terminal device both carry the actual PDCP SN and the virtual PDCP SN. Both the source network device and the target network device perform intra-entity PDCP PDU ordering based on the virtual PDCP SNs, and a particular network entity or layer (e.g., a layer above the source network device PDCP and the target network device PDCP) performs inter-entity PDCP PDU ordering based on the actual PDCP SNs.

It should be noted that, in the following description, for a scenario that a DRB bearer or an SRB bearer is supported by a terminal device to simultaneously transmit with two paths of a source network device and a target network device, the source network device sends the DRB bearer or the SRB bearer to the terminal device, and the target network device also sends the DRB bearer or the SRB bearer to the terminal device, the PDCP data packet processing method according to the embodiment of the present invention is described in detail. In practical application, the embodiment of the present invention is also applicable to a situation that the terminal device supports simultaneous transmission with two paths, namely, a source network device and a target network device, the terminal device sends a DRB bearer or an SRB bearer to the source network device, and the terminal device also sends a DRB bearer or an SRB bearer to the target network device; in such a scenario, the terminal device may interact with the network device for PDCP SN and/or PDCP SN assignment rules. Specifically, the PDCP SN (e.g., PDCP SN pattern, PDCP SN bitmap, or PDCP SN list) and/or the PDCP SN allocation rule may be sent to the network device by RRC signaling, MAC CE, physical layer signaling bearer, or PDCP control PDU, PDCP data packet.

In each of the above scenarios, the transmitting electronic device may be one PDCP entity in the terminal device, and the receiving electronic device may be another PDCP entity in the terminal device. In specific implementation, when transmitting uplink data, one PDCP entity or PDCP function module of the terminal device sends a PDCP data packet to the source network device, and the other PDCP entity or PDCP function module of the terminal device sends a PDCP data packet to the target network device; furthermore, one PDCP entity or PDCP function of the terminal device may interact with another PDCP entity or PDCP function of the terminal device for PDCP SNs and/or PDCP SN assignment rules. When downlink data is transmitted, the source network equipment sends a PDCP data packet to one PDCP entity or PDCP functional module of the terminal equipment, and the target network equipment sends the PDCP data packet to the other PDCP entity or PDCP functional module of the terminal equipment; in addition, one PDCP entity or PDCP function of the terminal device may also interact with another PDCP entity or PDCP function of the terminal device for PDCP SN and/or PDCP SN assignment rules.

The data packet processing method provided by the embodiment of the invention makes clear how the terminal device performs data transmission simultaneously with the source network device and the target network device, and especially manages the PDCP SNs of the PDCP data packets and the state variables of the PDCP data packets when two corresponding PDCP entity transmission buffers and/or receiving buffers exist. The method and the device avoid the problems that the terminal equipment, the source network equipment and the target network equipment have inconsistent understanding of the PDCP SN due to wrong setting of the PDCP SN and/or the state variable of the PDCP data packet, and the received PDCP data packet is processed wrongly. Meanwhile, the problem of delay of delivery to a high layer after receiving the PDCP data packet is avoided, and the overall data transmission rate of the system is ensured.

In order to implement the above data packet processing method, an embodiment of the present invention provides a transmitting electronic device, where a structure of the transmitting electronic device 600, as shown in fig. 17, includes:

a first processing unit 601 configured to set a PDCP SN and/or a status variable of the PDCP data packet based on the first information; the first information is a pre-agreed PDCP SN and/or a PDCP SN distribution rule; or, the first information is the PDCP SN and/or the PDCP SN assignment rule sent by the sending electronic device to the second sending electronic device and/or the receiving electronic device.

In this embodiment of the present invention, the sending electronic device 600 further includes:

a first sending unit 602 configured to send the PDCP SN and/or the PDCP SN allocation rule to the second sending electronic device.

a second sending unit 603 configured to send the PDCP SN and/or the PDCP SN assignment rule to the receiving electronic device.

In the embodiment of the present invention, the PDCP SN and/or the PDCP SN allocation rule is determined by the transmitting electronic device, or the PDCP SN is determined by the second transmitting electronic device, or the PDCP SN is determined by both the transmitting electronic device and the second transmitting electronic device.

In the embodiment of the invention, the PDCP SN and/or the PDCP SN allocation rule is determined according to at least one of the following conditions: traffic characteristics, QoS requirements, scheduling conditions, SPS configuration information, CG configuration information, activated carrier information, activated SPS information, activated CG information, traffic size, traffic type, cell load, cell interference, and cell channel quality.

In the embodiment of the present invention, the PDCP SN and/or the PDCP SN allocation rule is sent by at least one of the following: RRC signaling, MAC CE, physical layer signaling bearer, and PDCP packets.

In the embodiment of the invention, when the PDCP packet is a PDCP control PDU,

the PDCP control PDU carries the information of the PDCP SN and/or carries the indication of the control information type of the contained PDCP SN information;

and/or, carrying the PDCP SN maintained together in the PDCP control PDU;

and/or, carrying at least one of a PDCP SN Bitmap in the PDCP control PDU, a starting SN corresponding to the PDCP SN Bitmap, and a terminating SN corresponding to the PDCP SN Bitmap;

and/or, the PDCP control PDU carries at least one of a PDCP SN pattern, a starting SN corresponding to the PDCP SN pattern, and a terminating SN corresponding to the PDCP SN pattern;

and/or, carrying a starting SN and a terminating SN in the PDCP SN commonly maintained in the PDCP control PDU;

and/or, carrying the number of the PDCP SNs which are maintained together in the PDCP control PDU;

and/or, carrying the length of the PDCP SN Bitmap which is commonly maintained in the PDCP control PDU;

and/or, carrying the length or period of the PDCP SN pattern which is commonly maintained in the PDCP control PDU;

and/or, carrying the jointly maintained PDCP SN list in the PDCP control PDU.

In this embodiment of the present invention, the first processing unit 601 is configured to execute at least one of the following:

setting a value of TX-NEXT and/or an initial value of TX-NEXT based on the first information;

associating a COUNT value COUNT of the PDCP data packet with a value of TX-NEXT;

setting the PDCP SN of the PDCP data packet as a value obtained by utilizing the function of TX-NEXT to the PDCP SN size to perform modular operation;

setting a value of TX-NEXT to a NEXT PDCP SN adjacent to a current PDCP SN based on the first information.

In the embodiment of the present invention, the PDCP SN includes: a first PDCP SN and a second PDCP SN;

the first PDCP SN is used for at least one of: the first sending electronic equipment carries out grouping and transmission of PDCP data packets, sets PDCP SNs and/or state variables of the PDCP data packets, and the receiving electronic equipment carries out PDCP data packet processing in a PDCP entity;

the second PDCP SN is used for receiving the PDCP data packet processing between the PDCP entities of the electronic equipment.

In the embodiment of the invention, the first PDCP SN and the second PDCP SN are carried in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet, and the second PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the second PDCP SN is carried in a header of the PDCP data packet, and the first PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the second PDCP SN is transmitted through a dedicated signaling;

or, the second PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the first PDCP SN is transmitted through a dedicated signaling;

alternatively, the first PDCP SN and the second PDCP SN are transmitted through dedicated signaling.

In this embodiment of the present invention, the PDCP data packet further includes first indication information, where the first indication information is used to indicate at least one of: the type of the PDCP data packet, the format of the PDCP data packet and PDCP SN information carried by the PDCP data packet.

In this embodiment of the present invention, the PDCP data packet further includes second indication information, where the second indication information is used to indicate at least one of the following:

whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.

In this embodiment of the present invention, the first processing unit 601 is further configured to determine, according to an indication or predefined information of a network device, at least one of the following information:

the type of the PDCP data packet, the format of the PDCP data packet, the PDCP SN information carried by the PDCP data packet, whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.

setting a value of TX-NEXT based on the first PDCP SN;

setting an initial value of TX-NEXT based on the first PDCP SN, the initial value may be 0;

setting the PDCP SN of the PDCP data packet as a value obtained by utilizing TX-NEXT to perform modulus on the size of the PDCP SN;

setting a value of TX-NEXT to TX-NEXT plus 1 based on the first PDCP SN.

In the embodiment of the invention, the PDCP SN and/or the PDCP SN allocation rule are sent periodically or based on an event.

In an embodiment of the present invention, the event includes at least one of the following: PDCP SN pattern change and PDCP SN allocation rule change.

In the embodiment of the present invention, the sending electronic device is a source network device, and the receiving electronic device is a terminal device;

or, the first sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device;

or, the sending electronic device is a source network device, and the receiving electronic device is a target network device;

or, the sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a terminal device;

or, the sending electronic device is a target network device, and the receiving electronic device is a terminal device;

or, the first sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device;

or, the sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a terminal device;

or, the sending electronic device is a target network device, and the receiving electronic device is a source network device; or, the sending electronic device is a terminal device, and the receiving electronic device is a target network device and/or a source network device;

or, the sending electronic device is a first sending entity in the terminal device, and the receiving electronic device is a first receiving entity in the terminal device;

or, the sending electronic device is a first sending entity in the terminal device, the second sending electronic device is a second sending entity in the terminal device, and the receiving electronic devices are a target network device and a source network device.

In this embodiment of the present invention, the pre-agreed PDCP SNs or the PDCP SNs sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device include at least one of: PDCP SN, PDCP SN list, PDCP SN Bitmap, PDCP SN pattern.

In order to implement the above data packet processing method, an embodiment of the present invention provides a receiving electronic device, where a structure of the receiving electronic device 800 is as shown in fig. 18, and includes:

a receiving unit 801 configured to receive PDCP sequence numbers, SNs, and/or PDCP SN assignment rules of at least two transmitting electronic devices;

a second processing unit 802 configured to process PDCP data packets according to the PDCP SNs and/or PDCP SN allocation rules.

In the embodiment of the present invention, the PDCP SN and/or the PDCP SN allocation rule of the sending electronic device includes: a first PDCP SN and a second PDCP SN;

the first PDCP SN is for at least one of: the sending electronic equipment performs packet packing and transmission of the PDCP data packet, sets the PDCP SN and/or state variable of the PDCP data packet, and the receiving electronic equipment performs PDCP data packet processing in the PDCP entity;

the second PDCP SN is used for the receiving electronic device to perform PDCP packet processing between PDCP entities.

In this embodiment of the present invention, the second processing unit 802 is configured to perform PDCP in-entity processing on the PDCP data packet according to the first PDCP SN;

and/or, according to the second PDCP SN, processing between PDCP entities is carried out on the PDCP data packet.

In this embodiment of the present invention, the PDCP data packet further includes first indication information, where the first indication information is used to indicate at least one of:

the type of the PDCP data packet, the format of the PDCP data packet and PDCP SN information carried by the PDCP data packet.

In this embodiment of the present invention, the second processing unit 802 is further configured to replace the first PDCP SN with the second PDCP SN.

In this embodiment of the present invention, the receiving unit 801 is further configured to receive a PDCP data packet and/or a PDCP control PDU.

In the embodiment of the present invention, whether the receiving electronic device processes the PDCP data packet in the PDCP entity and/or between PDCP entities is determined by presetting, or network device configuration, or by the second processing unit according to at least one of the PDCP SN and a state variable.

In this embodiment of the present invention, when the t-reordering timer expires, the second processing unit is configured to determine to deliver the PDCP data packet to the higher layer in sequence;

and/or in case of RCVD-COUNT ═ RX-DELIV, the second processing unit is configured to determine in-order delivery of the PDCP packets to higher layers.

In the embodiment of the present invention, the PDCP SNs and/or the PDCP SN allocation rules of the at least two transmitting electronic devices are transmitted from any one of the transmitting electronic devices to the receiving electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are transmitted by a designated one of the transmitting electronic devices to the receiving electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are both transmitted by each transmitting electronic device to the receiving electronic device;

alternatively, the PDCP SN and/or PDCP SN assignment rule of each transmitting electronic device is transmitted by the transmitting electronic device itself and/or other transmitting electronic devices to the receiving electronic device.

In the embodiment of the invention, the PDCP SN and/or PDCP SN distribution rule of the at least two sending electronic devices are determined by any sending electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of said at least two transmitting electronic devices are determined by a designated one of the transmitting electronic devices;

alternatively, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are jointly determined by the at least two transmitting electronic devices.

In the embodiment of the present invention, the PDCP SN and/or the PDCP SN allocation rule is received through at least one of the following: RRC signaling, MAC CE, physical layer signaling bearer, and PDCP packets.

In the embodiment of the invention, when the PDCP packet is a PDCP control PDU,

and/or, carrying the PDCP SN maintained together in the PDCP control PDU;

and/or, carrying the jointly maintained PDCP SN list in the PDCP control PDU.

In the embodiment of the present invention, the receiving electronic device is a terminal device, and the sending electronic device is a source network device and/or a target network device;

or, the receiving electronic device is a first receiving entity in the terminal device, and the sending electronic device is a first sending entity in the terminal device;

or, the receiving electronic device is a source network device and/or a target network device, and the sending electronic device is a terminal device;

or, the receiving electronic device is a target network device, and the sending electronic device is a source network device;

or, the receiving electronic device is a source network device, and the sending electronic device is a target network device;

or, the receiving electronic device is a source network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device;

or, the receiving electronic device is a target network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device.

In this embodiment of the present invention, the PDCP sequence numbers SN of the at least two sending electronic devices include at least one of: PDCP SN, PDCP SN list, PDCP SN Bitmap, PDCP SN pattern.

The embodiment of the present invention further provides a transmitting electronic device, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the data packet processing method executed by the terminal device when running the computer program.

The embodiment of the present invention further provides a receiving electronic device, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the data packet processing method executed by the network device when running the computer program.

Fig. 19 is a schematic diagram of a hardware configuration of electronic devices (a transmitting electronic device and a receiving electronic device) according to an embodiment of the present invention, where the electronic device 700 includes: at least one processor 701, a memory 702, and at least one network interface 704. The various components in the electronic device 700 are coupled together by a bus system 705. It is understood that the bus system 705 is used to enable communications among the 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 19 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 disk, 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 embodiments of the present invention is used to store various types of data in support of the operation of the electronic device 700. Examples of such data include: any computer program for operating on electronic device 700, such as application 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. A 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 electronic Device 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 foregoing methods.

The embodiment of the application also provides a storage medium for storing the computer program.

Optionally, the 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 corresponding processes in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the storage medium may be applied to a network device in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes in each method in the embodiment of the present application, which is not described herein again for brevity.

The present invention is 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

A method of packet processing, the method comprising:

the first sending electronic device sets a PDCP sequence number SN and/or a state variable of a PDCP data packet based on the first information;

the first information is a pre-agreed PDCP SN and/or a PDCP SN distribution rule; or, the first information is a PDCP SN and/or a PDCP SN allocation rule sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device.
The method of claim 1, wherein the method further comprises:

the first transmitting electronic device transmits PDCP SNs and/or PDCP SN assignment rules to the second transmitting electronic device.
The method according to claim 1 or 2, wherein the method further comprises:

the first transmitting electronic device transmits PDCP SNs and/or PDCP SN assignment rules to the receiving electronic device.
A method according to any of claims 1 to 3, wherein the PDCP SN and/or PDCP SN allocation rule is determined by the first transmitting electronic device, or the PDCP SN is determined by the second transmitting electronic device, or the PDCP SN is determined by both the first transmitting electronic device and the second transmitting electronic device.
The method according to any of claims 1 to 4, wherein the PDCP SN and/or PDCP SN allocation rule is determined according to at least one of:

the method comprises the following steps of service characteristics, quality of service (QoS) requirements, scheduling conditions, semi-persistent scheduling (SPS) configuration information, configuration authorization (CG) configuration information, activated carrier information, activated SPS information, activated CG information, traffic volume, traffic type, cell load, cell interference and cell channel quality.
The method according to any of claims 1 to 5, wherein the PDCP SN and/or PDCP SN allocation rule is sent by at least one of:

radio Resource Control (RRC) signaling, a Media Access Control (MAC) control unit (CE), a physical layer signaling bearer and a PDCP packet.
The method according to claim 6, wherein, when the PDCP packet is a PDCP control PDU,

the PDCP control PDU carries the information of the PDCP SN and/or carries the indication of the control information type of the contained PDCP SN information;

and/or, carrying the PDCP SN maintained together in the PDCP control PDU;

and/or, carrying at least one of a PDCP SN Bitmap in the PDCP control PDU, a starting SN corresponding to the PDCP SN Bitmap, and a terminating SN corresponding to the PDCP SN Bitmap;

and/or, the PDCP control PDU carries at least one of a PDCP SN pattern, a starting SN corresponding to the PDCP SN pattern, and a terminating SN corresponding to the PDCP SN pattern;

and/or, carrying a starting SN and a terminating SN in the PDCP SN commonly maintained in the PDCP control PDU;

and/or, carrying the number of the PDCP SNs which are maintained together in the PDCP control PDU;

and/or, carrying the length of the PDCP SN Bitmap which is commonly maintained in the PDCP control PDU;

and/or, carrying the length or period of the PDCP SN pattern which is commonly maintained in the PDCP control PDU;

and/or, carrying the jointly maintained PDCP SN list in the PDCP control PDU.
The method according to any one of claims 1 to 7, wherein the setting of the PDCP SN and/or the status variable of the PDCP data packet comprises at least one of:

setting a value of TX-NEXT and/or an initial value of TX-NEXT based on the first information;

associating a COUNT value COUNT of the PDCP data packet with a value of TX-NEXT;

setting the PDCP SN of the PDCP data packet as a value obtained by utilizing the function of TX-NEXT to the PDCP SN size to perform modular operation;

setting a value of TX-NEXT to a NEXT PDCP SN adjacent to a current PDCP SN based on the first information.
The method according to any one of claims 1 to 7, wherein the PDCP SN comprises: a first PDCP SN and a second PDCP SN;

the first PDCP SN is used for at least one of: the first sending electronic equipment carries out grouping and transmission of PDCP data packets, sets PDCP SNs and/or state variables of the PDCP data packets, and the receiving electronic equipment carries out PDCP data packet processing in a PDCP entity;

the second PDCP SN is used for receiving the PDCP data packet processing between the PDCP entities of the electronic equipment.
The method of claim 9, wherein,

the first PDCP SN and the second PDCP SN are carried in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet, and the second PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the second PDCP SN is carried in a header of the PDCP data packet, and the first PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the second PDCP SN is transmitted through a dedicated signaling;

or, the second PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the first PDCP SN is transmitted through a dedicated signaling;

alternatively, the first PDCP SN and the second PDCP SN are transmitted through dedicated signaling.
The method as claimed in claim 9 or 10, wherein the PDCP data packet further comprises first indication information indicating at least one of:

the type of the PDCP data packet, the format of the PDCP data packet and PDCP SN information carried by the PDCP data packet.
The method as in any one of claims 9 to 11, wherein the PDCP data packet further comprises second indication information indicating at least one of:

whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.
The method of any of claims 9 to 12, wherein the method further comprises: the first sending electronic device determines at least one of the following information according to the indication or predefined information of the network device:

the type of the PDCP data packet, the format of the PDCP data packet, the PDCP SN information carried by the PDCP data packet, whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.
The method according to any one of claims 9 to 13, wherein the setting of the state variable of the PDCP data packet comprises at least one of:

setting a value of TX-NEXT based on the first PDCP SN;

setting an initial value of TX-NEXT based on the first PDCP SN, the initial value may be 0;

associating a COUNT value COUNT of the PDCP data packet with a value of TX-NEXT;

setting the PDCP SN of the PDCP data packet as a value obtained by utilizing TX-NEXT to perform modulus on the size of the PDCP SN;

setting a value of TX-NEXT to TX-NEXT plus 1 based on the first PDCP SN.
The method according to any of claims 1 to 14, wherein the first transmitting electronic device periodically transmits PDCP SNs and/or PDCP SN assignment rules;

alternatively, the first transmitting electronic device transmits the PDCP SN and/or the PDCP SN allocation rule based on an event.
The method of claim 15, wherein the event comprises at least one of:

PDCP SN pattern change and PDCP SN allocation rule change.
The method of any one of claims 1 to 16,

the first sending electronic device is a source network device, and the receiving electronic device is a terminal device;

or, the first sending electronic device is a source network device, and the receiving electronic device is a target network device;

or the first sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a terminal device;

or, the first sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device;

or, the first sending electronic device is a target network device, and the receiving electronic device is a terminal device;

or the first sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a terminal device;

or, the first sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device;

or, the first sending electronic device is a target network device, and the receiving electronic device is a source network device;

or, the first sending electronic device is a terminal device, and the receiving electronic device is a target network device and/or a source network device;

or the first sending electronic device is a first sending entity in the terminal device, and the receiving electronic device is a first receiving entity in the terminal device;

or, the first sending electronic device is a first sending entity in the terminal device, the second sending electronic device is a second sending entity in the terminal device, and the receiving electronic device is a target network device and/or a source network device.
The method of any of claims 1 to 17, wherein the pre-agreed PDCP SNs, or PDCP SNs sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device, comprise at least one of:

PDCP SN、PDCP SN list、PDCP SN Bitmap、PDCP SN pattern。
a method of packet processing, the method comprising:

the receiving electronic equipment receives packet data convergence protocol sequence numbers PDCP SN and/or PDCP SN distribution rules of at least two sending electronic equipment;

and the receiving electronic equipment processes the PDCP data packet according to the PDCP SN and/or the PDCP SN distribution rule.
The method of claim 19, wherein the PDCP SN and/or PDCP SN allocation rule of the transmitting electronic device comprises: a first PDCP SN and a second PDCP SN;

the first PDCP SN is for at least one of: the sending electronic equipment performs packet packing and transmission of the PDCP data packet, sets the PDCP SN and/or state variable of the PDCP data packet, and the receiving electronic equipment performs PDCP data packet processing in the PDCP entity;

the second PDCP SN is used for the receiving electronic device to perform PDCP packet processing between PDCP entities.
The method of claim 19 or 20, wherein the receiving electronic device processing PDCP data packets according to the PDCP SN, comprising:

the receiving electronic equipment carries out the treatment in a PDCP entity on the PDCP data packet according to the first PDCP SN;

and/or the receiving electronic equipment carries out the treatment among the PDCP entities on the PDCP data packet according to the second PDCP SN.
The method of claim 21, wherein the first PDCP SN and the second PDCP SN are carried within the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet, and the second PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the second PDCP SN is carried in a header of the PDCP data packet, and the first PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the second PDCP SN is transmitted through a dedicated signaling;

or, the second PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the first PDCP SN is transmitted through a dedicated signaling;

alternatively, the first PDCP SN and the second PDCP SN are transmitted through dedicated signaling.
The method as claimed in claim 21 or 22, wherein the PDCP data packet further comprises first indication information indicating at least one of:

the type of the PDCP data packet, the format of the PDCP data packet and PDCP SN information carried by the PDCP data packet.
The method as in any one of claims 21 to 23, wherein the PDCP data packet further comprises second indication information indicating at least one of:

whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.
The method of any of claims 19 to 24, wherein the method further comprises:

the receiving electronic device replaces the first PDCP SN with the second PDCP SN.
The method of any of claims 19 to 25, wherein the method further comprises:

the receiving electronic device receives PDCP data packets and/or PDCP control PDUs.
The method of any of claims 19 to 26, wherein whether the receiving electronic device handles the PDCP data packet within and/or between PDCP entities is determined by a pre-set, or a network device configuration, or by the receiving electronic device based on at least one of the PDCP SNs and a status variable.
The method as in claim 27, wherein in the event that a t-reordering timer expires, the receiving electronic device determines in-order delivery of the PDCP data packets to higher layers;

and/or, in the case of RCVD-COUNT ═ RX-DELIV, the receiving electronics determine in-order delivery of the PDCP packets to higher layers.
The method according to any of claims 19 to 28, wherein the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are transmitted by any one transmitting electronic device to the receiving electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are transmitted by a designated one of the transmitting electronic devices to the receiving electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are both transmitted by each transmitting electronic device to the receiving electronic device;

alternatively, the PDCP SN and/or PDCP SN assignment rule of each transmitting electronic device is transmitted by the transmitting electronic device itself and/or other transmitting electronic devices to the receiving electronic device.
The method according to any of claims 19 to 29, wherein the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are determined by any one transmitting electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of said at least two transmitting electronic devices are determined by a designated one of the transmitting electronic devices;

alternatively, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are jointly determined by the at least two transmitting electronic devices.
The method according to any of claims 19 to 30, wherein the PDCP SN and/or PDCP SN allocation rule is determined according to at least one of:

the method comprises the following steps of service characteristics, QoS requirements, scheduling conditions, SPS configuration information, configuration authorization CG configuration information, activated carrier information, activated SPS information, activated CG information, traffic volume size, service type, cell load, cell interference and cell channel quality.
The method according to any of claims 19 to 31, wherein the PDCP SN and/or PDCP SN allocation rule is received by at least one of:

radio Resource Control (RRC) signaling, a Media Access Control (MAC) control unit (CE), physical layer signaling bearer and a Packet Data Convergence Protocol (PDCP) packet.
The method as claimed in claim 32, wherein, when the PDCP packet is a PDCP control PDU,

the PDCP control PDU carries the information of the PDCP SN and/or carries the indication of the control information type of the contained PDCP SN information;

and/or, carrying the PDCP SN maintained together in the PDCP control PDU;

and/or, carrying at least one of a PDCP SN Bitmap in the PDCP control PDU, a starting SN corresponding to the PDCP SN Bitmap, and a terminating SN corresponding to the PDCP SN Bitmap;

and/or, the PDCP control PDU carries at least one of a PDCP SN pattern, a starting SN corresponding to the PDCP SN pattern, and a terminating SN corresponding to the PDCP SN pattern;

and/or, carrying a starting SN and a terminating SN in the PDCP SN commonly maintained in the PDCP control PDU;

and/or, carrying the number of the PDCP SNs which are maintained together in the PDCP control PDU;

and/or, carrying the length of the PDCP SN Bitmap which is commonly maintained in the PDCP control PDU;

and/or, carrying the length or period of the PDCP SN pattern which is commonly maintained in the PDCP control PDU;

and/or, carrying the jointly maintained PDCP SN list in the PDCP control PDU.
The method of any one of claims 19 to 33,

the receiving electronic equipment is terminal equipment, and the sending electronic equipment is source network equipment and/or target network equipment;

or, the receiving electronic device is a first receiving entity in the terminal device, and the sending electronic device is a first sending entity in the terminal device;

or, the receiving electronic device is a source network device and/or a target network device, and the sending electronic device is a terminal device;

or, the receiving electronic device is a target network device, and the sending electronic device is a source network device;

or, the receiving electronic device is a source network device, and the sending electronic device is a target network device;

or, the receiving electronic device is a source network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device;

or, the receiving electronic device is a target network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device.
The method according to any of claims 19 to 34, wherein the PDCP sequence numbers, SN, of the at least two transmitting electronic devices comprise at least one of:

PDCP SN、PDCP SN list、PDCP SN Bitmap、PDCP SN pattern。
a transmitting electronic device, the transmitting electronic device comprising:

the first processing unit is configured to set a PDCP Sequence Number (SN) and/or a state variable of a PDCP data packet based on the first information;

the first information is a pre-agreed PDCP SN and/or a PDCP SN distribution rule; or, the first information is the PDCP SN and/or the PDCP SN assignment rule sent by the sending electronic device to the second sending electronic device and/or the receiving electronic device.
The transmitting electronic device of claim 36, wherein the transmitting electronic device further comprises:

a first sending unit configured to send PDCP SNs and/or PDCP SN assignment rules to the second sending electronic device.
The transmitting electronic device of claim 36 or 37, wherein the transmitting electronic device further comprises:

a second sending unit configured to send PDCP SNs and/or PDCP SN assignment rules to the receiving electronic device.
The transmitting electronic device of any of claims 36-38, wherein the PDCP SN and/or PDCP SN allocation rule is determined by the transmitting electronic device, or the PDCP SN is determined by the second transmitting electronic device, or the PDCP SN is determined by both the transmitting electronic device and the second transmitting electronic device.
The transmitting electronic device of any of claims 36-39, wherein the PDCP SN and/or PDCP SN allocation rule is determined from at least one of:

the method comprises the following steps of service characteristics, QoS requirements, scheduling conditions, SPS configuration information, configuration authorization CG configuration information, activated carrier information, activated SPS information, activated CG information, traffic volume size, service type, cell load, cell interference and cell channel quality.
The transmitting electronic device of any of claims 36-40, wherein the PDCP SNs and/or PDCP SN allocation rules are transmitted by at least one of:

radio Resource Control (RRC) signaling, a Media Access Control (MAC) control unit (CE), a physical layer signaling bearer and a PDCP packet.
The transmitting electronic device as claimed in claim 41, wherein when the PDCP packet is a PDCP control PDU, the PDCP control PDU carries information of the PDCP SN and/or an indication of a control information type carrying the included PDCP SN information;

and/or, carrying the PDCP SN maintained together in the PDCP control PDU;

and/or, carrying at least one of a PDCP SN Bitmap in the PDCP control PDU, a starting SN corresponding to the PDCP SN Bitmap, and a terminating SN corresponding to the PDCP SN Bitmap;

and/or, the PDCP control PDU carries at least one of a PDCP SN pattern, a starting SN corresponding to the PDCP SN pattern, and a terminating SN corresponding to the PDCP SN pattern;

and/or, carrying a starting SN and a terminating SN in the PDCP SN commonly maintained in the PDCP control PDU;

and/or, carrying the number of the PDCP SNs which are maintained together in the PDCP control PDU;

and/or, carrying the length of the PDCP SN Bitmap which is commonly maintained in the PDCP control PDU;

and/or, carrying the length or period of the PDCP SN pattern which is commonly maintained in the PDCP control PDU;

and/or, carrying the jointly maintained PDCP SN list in the PDCP control PDU.
The transmitting electronic device of any of claims 36-42, wherein the first processing unit is configured to perform at least one of:

setting a value of TX-NEXT and/or an initial value of TX-NEXT based on the first information;

associating a COUNT value COUNT of the PDCP data packet with a value of TX-NEXT;

setting the PDCP SN of the PDCP data packet as a value obtained by utilizing the function of TX-NEXT to the PDCP SN size to perform modular operation;

setting a value of TX-NEXT to a NEXT PDCP SN adjacent to a current PDCP SN based on the first information.
The transmitting electronic device as in any of claims 36-42, wherein the PDCP SN comprises: a first PDCP SN and a second PDCP SN;

the first PDCP SN is used for at least one of: the first sending electronic equipment carries out grouping and transmission of PDCP data packets, sets PDCP SNs and/or state variables of the PDCP data packets, and the receiving electronic equipment carries out PDCP data packet processing in a PDCP entity;

the second PDCP SN is used for receiving the PDCP data packet processing between the PDCP entities of the electronic equipment.
The transmitting electronic device of claim 44,

the first PDCP SN and the second PDCP SN are carried in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet, and the second PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the second PDCP SN is carried in a header of the PDCP data packet, and the first PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the second PDCP SN is transmitted through a dedicated signaling;

or, the second PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the first PDCP SN is transmitted through a dedicated signaling;

alternatively, the first PDCP SN and the second PDCP SN are transmitted through dedicated signaling.
The transmitting electronic device as in claim 44 or 45, wherein the PDCP packet further comprises a first indication information indicating at least one of:

the type of the PDCP data packet, the format of the PDCP data packet and PDCP SN information carried by the PDCP data packet.
The transmitting electronic device of any of claims 44-46, wherein the PDCP packet further comprises second indication information indicating at least one of:

whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.
The transmitting electronic device of any of claims 44-47, wherein the first processing unit is further configured to determine, from an indication of a network device or predefined information, at least one of:

the type of the PDCP data packet, the format of the PDCP data packet, the PDCP SN information carried by the PDCP data packet, whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.
The transmitting electronic device of any of claims 44-48, wherein the first processing unit is configured to perform at least one of:

setting a value of TX-NEXT based on the first PDCP SN;

setting an initial value of TX-NEXT based on the first PDCP SN, the initial value may be 0;

associating a COUNT value COUNT of the PDCP data packet with a value of TX-NEXT;

setting the PDCP SN of the PDCP data packet as a value obtained by utilizing TX-NEXT to perform modulus on the size of the PDCP SN;

setting a value of TX-NEXT to TX-NEXT plus 1 based on the first PDCP SN.
The transmitting electronic device of any of claims 36-49, wherein the PDCP SNs and/or PDCP SN allocation rules are transmitted periodically or based on an event.
The transmitting electronic device of claim 50, wherein the event comprises at least one of:

PDCP SN pattern change and PDCP SN allocation rule change.
The transmitting electronic device of any of claims 36-51, wherein the transmitting electronic device is a source network device and the receiving electronic device is a terminal device;

or, the sending electronic device is a source network device, and the receiving electronic device is a target network device;

or, the sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a terminal device;

or, the first sending electronic device is a source network device, the second sending electronic device is a target network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device;

or, the sending electronic device is a target network device, and the receiving electronic device is a terminal device;

or, the sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a terminal device;

or, the first sending electronic device is a target network device, the second sending electronic device is a source network device, and the receiving electronic device is a first receiving entity and/or a second receiving entity in the terminal device;

or, the sending electronic device is a target network device, and the receiving electronic device is a source network device;

or, the sending electronic device is a terminal device, and the receiving electronic device is a target network device and/or a source network device;

or, the sending electronic device is a first sending entity in the terminal device, and the receiving electronic device is a first receiving entity in the terminal device;

or, the sending electronic device is a first sending entity in the terminal device, the second sending electronic device is a second sending entity in the terminal device, and the receiving electronic devices are a target network device and a source network device.
The transmitting electronic device of any of claims 36-52, wherein the pre-agreed PDCP SNs, or PDCP SNs transmitted by the first transmitting electronic device to the second transmitting electronic device and/or the receiving electronic device, comprise at least one of:

PDCP SN、PDCP SN list、PDCP SN Bitmap、PDCP SN pattern。
a receiving electronic device, the receiving electronic device comprising:

a receiving unit configured to receive packet data convergence protocol sequence numbers, PDCP SNs, and/or PDCP SN assignment rules of at least two transmitting electronic devices;

and the second processing unit is configured to process the PDCP data packet according to the PDCP SN and/or the PDCP SN distribution rule.
The receiving electronic device of claim 54, wherein the PDCP SN and/or PDCP SN allocation rule of the transmitting electronic device comprises: a first PDCP SN and a second PDCP SN;

the first PDCP SN is for at least one of: the sending electronic equipment performs packet packing and transmission of the PDCP data packet, sets the PDCP SN and/or state variable of the PDCP data packet, and the receiving electronic equipment performs PDCP data packet processing in the PDCP entity;

the second PDCP SN is used for the receiving electronic device to perform PDCP packet processing between PDCP entities.
The receiving electronic device according to claim 54 or 55, wherein the second processing unit is configured to perform intra-PDCP entity processing on the PDCP data packet according to the first PDCP SN;

and/or, according to the second PDCP SN, processing between PDCP entities is carried out on the PDCP data packet.
The receiving electronic device as in claim 56, wherein the first PDCP SN and the second PDCP SN are carried within the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet, and the second PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the second PDCP SN is carried in a header of the PDCP data packet, and the first PDCP SN is carried in the header of the PDCP data packet or in the PDCP data packet;

or, the first PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the second PDCP SN is transmitted through a dedicated signaling;

or, the second PDCP SN is carried in a header of the PDCP data packet or in a data packet, and the first PDCP SN is transmitted through a dedicated signaling;

alternatively, the first PDCP SN and the second PDCP SN are transmitted through dedicated signaling.
The receiving electronic device as in claim 56 or 57, wherein the PDCP packet further comprises a first indication information indicating at least one of:

the type of the PDCP data packet, the format of the PDCP data packet and PDCP SN information carried by the PDCP data packet.
The receiving electronic device of any of claims 56-58, wherein the PDCP data packet further comprises second indication information indicating at least one of:

whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the second PDCP SN, whether the first PDCP SN is in the packet head or the data packet of the PDCP data packet, whether the second PDCP SN is in the packet head or the data packet of the PDCP data packet, and the precedence order of the second PDCP SN and the first PDCP SN.
The receiving electronic device of any of claims 54-59, wherein the second processing unit is further configured to replace the first PDCP SN with the second PDCP SN.
The receiving electronic device according to any of claims 54 to 60, wherein the receiving unit is further configured to receive PDCP data packets and/or PDCP control PDUs.
The receiving electronic device of any of claims 54-61, wherein whether the receiving electronic device processes the PDCP data packets within and/or between PDCP entities is determined by a pre-set, or a network device configuration, or by the second processing unit based on at least one of the PDCP SNs and a status variable.
The receiving electronic device of claim 62, wherein, in case of a t-reordering timer expiring, the second processing unit is configured to determine in-order delivery of the PDCP data packets to a higher layer;

and/or in case of RCVD-COUNT ═ RX-DELIV, the second processing unit is configured to determine in-order delivery of the PDCP packets to higher layers.
The receiving electronic device according to any of claims 54 to 63, wherein the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are transmitted by any one transmitting electronic device to the receiving electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are transmitted by a designated one of the transmitting electronic devices to the receiving electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are both transmitted by each transmitting electronic device to the receiving electronic device;

alternatively, the PDCP SN and/or PDCP SN assignment rule of each transmitting electronic device is transmitted by the transmitting electronic device itself and/or other transmitting electronic devices to the receiving electronic device.
The receiving electronic device of any of claims 54-64, wherein the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are determined by either transmitting electronic device;

or, the PDCP SNs and/or PDCP SN assignment rules of said at least two transmitting electronic devices are determined by a designated one of the transmitting electronic devices;

alternatively, the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are jointly determined by the at least two transmitting electronic devices.
The receiving electronic device of any of claims 54-65, wherein the PDCP SN and/or PDCP SN allocation rule is determined according to at least one of:

the method comprises the following steps of service characteristics, QoS requirements, scheduling conditions, SPS configuration information, configuration authorization CG configuration information, activated carrier information, activated SPS information, activated CG information, traffic volume size, service type, cell load, cell interference and cell channel quality.
The receiving electronic device of any of claims 54-66, wherein the PDCP SN and/or PDCP SN allocation rule is received by at least one of:

radio Resource Control (RRC) signaling, a Media Access Control (MAC) control unit (CE), a physical layer signaling bearer and a PDCP packet.
The receiving electronic device as claimed in claim 67, wherein when the PDCP packet is a PDCP control PDU, the PDCP control PDU carries information of the PDCP SN and/or an indication of a control information type carrying the included PDCP SN information;

and/or, carrying the PDCP SN maintained together in the PDCP control PDU;

and/or, carrying at least one of a PDCP SN Bitmap in the PDCP control PDU, a starting SN corresponding to the PDCP SN Bitmap, and a terminating SN corresponding to the PDCP SN Bitmap;

and/or, the PDCP control PDU carries at least one of a PDCP SN pattern, a starting SN corresponding to the PDCP SN pattern, and a terminating SN corresponding to the PDCP SN pattern;

and/or, carrying a starting SN and a terminating SN in the PDCP SN commonly maintained in the PDCP control PDU;

and/or, carrying the number of the PDCP SNs which are maintained together in the PDCP control PDU;

and/or, carrying the length of the PDCP SN Bitmap which is commonly maintained in the PDCP control PDU;

and/or, carrying the length or period of the PDCP SN pattern which is commonly maintained in the PDCP control PDU;

and/or, carrying the jointly maintained PDCP SN list in the PDCP control PDU.
The receiving electronic device of any of claims 54-68, wherein the receiving electronic device is a terminal device and the transmitting electronic device is a source network device and/or a target network device;

or, the receiving electronic device is a first receiving entity in the terminal device, and the sending electronic device is a first sending entity in the terminal device;

or, the receiving electronic device is a source network device and/or a target network device, and the sending electronic device is a terminal device;

or, the receiving electronic device is a target network device, and the sending electronic device is a source network device;

or, the receiving electronic device is a source network device, and the sending electronic device is a target network device;

or, the receiving electronic device is a source network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device;

or, the receiving electronic device is a target network device, and the sending electronic device is a first sending entity and/or a second sending entity in the terminal device.
The receiving electronic device of any of claims 54-69, wherein the PDCP sequence numbers, SNs, of the at least two transmitting electronic devices comprise at least one of:

PDCP SN、PDCP SN list、PDCP SN Bitmap、PDCP SN pattern。
a transmitting electronic device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor is configured to execute the steps of the data packet processing method according to any one of claims 1 to 18 when running the computer program.
A receiving electronic device 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 of any of claims 19 to 35 when running the computer program.
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 18.
A storage medium storing an executable program which, when executed by a processor, implements the packet processing method of any one of claims 19 to 35.