CN112789839B - A data packet processing method, device and storage medium - Google Patents

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

A data packet processing method, device and storage medium

technical field

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

Background technique

In related technologies, when transmitting Packet Data Convergence Protocol (PDCP) data packets, the PDCP data packets received by the receiving electronic device may come from different PDCP entities of the sending electronic device; for example, the receiving electronic device receives the source network PDCP packets sent by the PDCP entity of the device and the PDCP entity of the target network device. In order to realize effective management of PDCP data packets, there is currently no effective solution on how to set the PDCP serial number (Serial Number, SN) on the sending electronic device, and how to process the received PDCP data packets on the basis of the PDCP SN on the receiving electronic device.

Contents of the invention

In order to solve the above technical problems, embodiments of the present invention provide a data packet processing method, device, and storage medium, which can realize effective management of PDCP data packets.

In the 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 state variable of the PDCP data packet based on the first information; the first information is a pre-agreed PDCP SN and/or PDCP SN assignment rule; or, the first information is the PDCP SN and/or PDCP SN assignment rule sent by the first sending electronic device to the second sending electronic device and/or receiving electronic device.

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

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

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

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

In a fifth aspect, an embodiment of the present invention provides a sending electronic device, including a processor and a memory for storing a computer program that can run on the processor, wherein, when the processor is used to run the computer program, execute the above-mentioned The steps of the data packet processing method performed by the sending electronic device.

In a sixth aspect, an embodiment of the present invention provides a receiving electronic device, including a processor and a memory for storing a computer program that can run on the processor, wherein, when the processor is used to run the computer program, execute the above-mentioned The steps of the data packet processing method executed by the receiving electronic device.

In a seventh aspect, an embodiment of the present invention provides a storage medium storing an executable program, and when the executable program is executed by a processor, implements the data packet processing method executed by the sending electronic device.

In an eighth aspect, an embodiment of the present invention provides a storage medium storing an executable program, and when the executable program is executed by a processor, implements the data packet processing method performed by the above receiving electronic device.

In the data packet processing method provided by the embodiment of the present invention, the sending electronic device sets the PDCP SN and/or state variable of the PDCP data packet based on the first information; wherein, the first information is the pre-agreed PDCP SN and/or PDCP SN allocation A rule; or, the first information is the PDCP SN and/or PDCP SN allocation rule sent by the first sending electronic device to the second sending electronic device and/or receiving electronic device. In this way, when the terminal device and the source network device and the target network device perform data transmission at the same time, the sending electronic device can set the PDCP SN and/or state variables of the PDCP data packet in a reasonable and orderly manner, avoiding the terminal device, the source network device and the target network device. Inconsistent understanding of the target network device on the PDCP SN causes the problem of incorrect processing of the PDCP data packet. The receiving electronic device performs redundant sorting, detection, deletion, and redundancy detection on the PDCP data packets according to the PDCP SN and/or PDCP SN allocation rules, which avoids the problem of delaying delivery to the upper layer after receiving the PDCP data packets, and improves the network efficiency. The overall data transfer rate of the system.

Description of drawings

FIG. 1 is a schematic flow diagram of cell handover in the NR system of the present invention;

Fig. 2 is a schematic flow chart of conditional switching in the present invention;

Fig. 3 is a schematic diagram of the present invention's sending and receiving process for PDCP packets;

Fig. 4 is the format diagram of COUNT of the present invention;

FIG. 5 is a schematic diagram of the composition and structure of a communication system according to an embodiment of the present invention;

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

7 is a schematic diagram of a PDCP controlPDU type and type indication according to an embodiment of the present invention;

8 is a schematic diagram of a processing flow for setting the PDCP SN and/or state variable of the PDCP data packet by the first sending electronic device according to an embodiment of the present invention;

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

10 is a schematic diagram of a detailed processing flow of a PDCP data packet processing method according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of a PDCP SN or a PDCP SN assignment rule between a source network device and a target network device according to an embodiment of the present invention;

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

FIG. 13 is a schematic diagram of the 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 of another detailed processing flow of a PDCP packet processing method according to an embodiment of the present invention;

Figure 15a is a schematic diagram of the format of a PDCP PDU carrying an actual PDCP SN and a virtual PDCP SN;

Figure 15b is a second schematic diagram of the format of the PDCP PDU carrying the actual PDCP SN and the virtual PDCP SN;

Figure 15c is a schematic diagram of the third format of the PDCP PDU carrying the actual PDCP SN and the virtual PDCP SN;

FIG. 16 is a schematic diagram of the PDCP PDU sent by the source network device and the target network device to the terminal device's PDCP entity according to the embodiment of the present invention, both carrying the actual PDCP SN and the virtual PDCP SN;

FIG. 17 is a schematic diagram of the composition and structure of the sending electronic device according to the embodiment of the present invention;

FIG. 18 is a schematic diagram of the composition and structure of receiving electronic equipment according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of a hardware composition structure of an electronic device according to an embodiment of the present invention.

Detailed ways

In order to understand the characteristics and technical contents of the embodiments of the present invention in more detail, the implementation of the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. The attached drawings are only for reference and description, and are not intended to limit the embodiments of the present invention.

Before the data processing method provided by the embodiment of the present invention is described in detail, a brief description of the data processing process in the related technology is given first.

The new radio (New Radio, NR) system supports the handover process of the terminal equipment in the connected state. When a terminal device using network services moves from one cell to another, or due to wireless transmission business load adjustment, activation operation maintenance, equipment failure, etc., in order to ensure the continuity of communication and the quality of service, the system will The communication link between the terminal equipment and the original cell is transferred to the new cell, that is, the handover process is performed.

Taking the Xn interface handover process as an example, it is suitable for the long term evolution (Long Term Evolution, LTE) system and the cell handover process of the NR system. As shown in Figure 1, it is divided into the following three stages:

Phase 1 (including steps 1 to 5), handover preparation: including measurement control and reporting, handover request and confirmation

Phase 2 (including steps 6 to 8), handover execution: the terminal device immediately executes the handover process after receiving the handover command, that is, the terminal device disconnects the source cell and connects with the target cell (such as performing random access, sending radio resource control (RadioResource Control, RRC) switching completion message to the target network device, etc.); secondary node (Secondary Node, SN) state transfer, data forwarding.

Phase 3 (including steps 9 to 12), the handover is completed: the target cell performs path switching (PathSwitch) with (Acess and MobilityManagement Function, AMF) and user plane function (User Port Function, UPF), and releases the terminal device context of the source network device .

The following is a brief description of conditional handover.

For high-speed mobile scenarios and high-frequency deployment scenarios, there are frequent handovers and handovers that are prone to failure. 3GPP is currently discussing the introduction of conditional handover for LTE and NR systems. As shown in Figure 2, the terminal device and the source network device perform cell measurement, configuration and reporting; the source network device and the target network device prepare for handover; when the terminal device meets the trigger conditions, it switches to the target network device. In the Conditional handover, by configuring a handover (Handover, HO) command (command) for the terminal device in advance, it avoids the problem that the terminal device is too late when the handover preparation time is too long. Moreover, for the high-speed rail scenario, the running 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 include the conditions used to trigger the terminal device to switch in the HO command. condition, the terminal device initiates an access request to the target network device.

The 3GPP RAN2#104 meeting has agreed on conditional handover, and supports the configuration of multiple target cells in the handover command of conditional handover, and the terminal device judges which target cell to access based on the configured conditions.

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

1) When performing cell switching, first add the target network device as a secondary node, then use role change signaling to change the secondary node into a primary node, and finally release the source network device; thus achieving the effect of reducing the interruption time during cell switching .

2) Based on the existing handover process, when the terminal equipment (User Equipment, UE) receives the conditional handover command, it continues to maintain the connection with the source network equipment, and at the same time initiates random access to the target network equipment until the terminal equipment and the target network The connection to the source base station is released only after the device access is completed.

For the sending and receiving processing flow of PDCP data packets, as shown in Figure 3, taking the terminal device as an example, after receiving a PDCP SDU from the upper layer, the PDCP entity sender associates the count value (COUNT) of the received PDCP SDU with TX_NEXT, Set the PDCP SN corresponding to the PDCP SDU to TX_NEXT modulo 2 ^{[pdcp-SN-SizeUL]} , and add 1 to TX_NEXT.

The receiving end of the PDCP entity reorders the received PDCP PDUs based on the t-reordering timer, and when the t-reordering times out or the state variable meets the conditions (such as when RCVD_COUNT=RX_DELIV), the PDCP SDUs are sequentially delivered to the upper layer. Specifically, when a PDCP PDU is received and RX_DELIV<RX_NEXT and t-reordering is not running, enable t-reordering and set RX_REOERD to RX_NEXT. When t-reordering times out, sequence PDCP SDUs to the upper layer.

Among them, TX_NEXT indicates the COUNT value of the next PDCP SDU to be sent; RX_REOERD indicates the COUNT value corresponding to the PDCP data PDU that triggers t-reordering; RX_NEXT indicates the COUNT value of the next PDCP SDU to be received; RX_DELIV indicates the COUNT value of the next PDCP SDU to be received; A COUNT value that is still waiting for confirmation and has not been submitted to the upper layer; RCVD_COUNT, which identifies the COUNT value of the currently received PDCP data PDU. The length of COUNT is 32 bits, and the schematic diagram of the format of COUNT, as shown in FIG. 4 , is composed of Hyper Frame Number (Hyper Frame Number, HFN) and PDCP SN, which is [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, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), LTE system, LTE Frequency Division Duplex (Frequency Division Duplex, FDD) system, LTE Time Division Duplex (Time Division Duplex, TDD ), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, 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 for communicating with a terminal device 120 (or called a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area, and can communicate with terminal devices located in the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station ( Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CloudRadio Access Network, CRAN), or the network device can be a mobile switching center, relay station, access point, vehicle equipment, wearable Devices, hubs, switches, bridges, routers, network-side devices in the 5G network or network devices in the future evolved Public Land Mobile Network (PLMN), etc.

The communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110 . As used herein, "terminal equipment" includes, but is not limited to, a connection via a wired line, such as via a Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for cellular networks, wireless local area networks (Wireless Local Area Network, WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or an apparatus of another terminal device configured to receive/send communication signals; and/or an Internet of Things (Internet of Things, IoT) device. 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 System (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data communication capabilities; may include radiotelephones, pagers, Internet/Internet PDAs with network access, Web browsers, organizers, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices including radiotelephone transceivers device. The terminal equipment may refer to an access terminal, a user equipment (User Equipment, UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or user device. The access terminal can be a cellular phone, a cordless phone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolved PLMNs, etc.

Optionally, direct device to device (Device to Device, D2D) communication may be performed between terminal devices 120 .

Optionally, a 5G system or a 5G network may also be called a New Radio (New Radio, NR) system or an NR network.

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

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

It should be understood that a device with a communication function in the network/system in the embodiment 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 with communication functions, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.

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

Step S201, the first sending electronic device sets the PDCP SN and/or state variable of the PDCP data packet based on the first information.

In the embodiment of the present invention, the first information is the pre-agreed PDCP SN and/or PDCP SN allocation rules, that is, the PDCP SN and/or PDCP SN allocation rules may be predefined; or, the first information is the The PDCP SN and/or PDCP SN assignment rules sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device. During specific implementation, the first sending electronic device periodically sends the PDCP SN and/or PDCP SN allocation rules sent to the second sending electronic device and/or receiving electronic device; or, the first sending electronic device sends the second sending electronic device based on an event. The electronic device and/or the PDCP SN sent by the receiving electronic device and/or the PDCP SN allocation rule. Wherein, the event includes at least one of the following: notification of subsequent shared PDCP SN list/PDCP SN identity/PDCP SN bitmap (bitmap)/PDCP SN pattern (pattern), PDCP SN pattern change and PDCP SN allocation rules 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 receiving electronic device includes at least one of the following: PDCP SN, PDCP SN list, PDCP SNBitmap , PDCP SN pattern. The PDCP SN assignment rule refers to how to assign a PDCP SN to a PDCP data packet.

During specific implementation, the PDCP SN and/or PDCP SN allocation rules are sent through at least one of the following: RRC signaling, MAC CE, physical layer signaling bearer, and PDCP packets; wherein, the PDCP packets include: PDCP control At least one of packets and PDCP packets. That is, the first sending electronic device sends the PDCP SN and/or to the second sending 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 Or PDCP SN allocation rules. Optionally, the PDCP SN interacted between the first sending electronic device, the second sending electronic device, and the receiving electronic device may also be replaced by the COUNT corresponding to the PDCP SN; that is, the first sending electronic device sends the second sending electronic device or The receiving electronic device sends COUTN corresponding to the PDCP SN.

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. Alternatively, the first sending electronic device is a source network device, and the receiving electronic device is a target network device. Alternatively, 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. Alternatively, the first sending electronic device is a target network device, and the receiving electronic device is a terminal device. Alternatively, 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. Alternatively, the first sending electronic device is a target network device, and the receiving electronic device is a source network device. Alternatively, 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. Alternatively, the first sending electronic device is the first sending entity in the terminal device, and the receiving electronic device is the first receiving entity in the terminal device. Alternatively, 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 A source 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 first receiving entity and/or a second receiving entity in the terminal device 2. The receiving entity. Alternatively, 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 functional modules in the terminal device.

In some embodiments, the PDCP SN and/or PDCP SN assignment rules are determined by the first sending electronic device, or the PDCP SN is determined by the second sending electronic device, or the PDCP SN is determined by the The first sending electronic device and the second sending electronic device are jointly determined. During specific implementation, the PDCP SN and/or PDCP SN allocation rules are determined according to at least one of the following: service characteristics, Quality of Service (Quality of Service, QoS) requirements, scheduling conditions, semi-persistent scheduling (Semi-Persistent Scheduling, SPS) configuration information, configured authorization (Configured Grant, CG) configuration information, activated carrier information, activated SPS information, activated CG information, traffic size, business 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 an indication of the type of control information contained in the PDCP SN information. Wherein, the PDCP control PDU is a new PDCP control PDU type different from existing PDCP control PDU types. Optionally, the new PDCP control PDU type is a type other than ROHC feedback and PDCP status report; optionally, the role of the new PDCP control PDU type is to indicate that the PDU carries PDCP SN information; such as PDCP control Included in the PDU is the indication of the control information type of the PDCP SN information. A schematic diagram of the PDCP control PDU type and type indication, as shown in Figure 7, when the bit value of the type indication is 000, the corresponding PDCP control PDU type is PDCP status report; when the bit value of the type indication is 001, the corresponding PDCP control PDU type It is ROHC feedback; when the bit value indicated by the type is 010, the corresponding PDCP control PDU type is PDCP SN; when the bit value indicated by the type is 011-111, the corresponding PDCP control PDU type is a reserved value.

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 SN in the PDCP data packet, for example, the PDCP SN is located in the header of the PDCP data packet or in the data packet.

2) The commonly maintained PDCP SN is carried in the PDCP control PDU.

3) At least one of the PDCP SN Bitmap, the start SN corresponding to the PDCP SN Bitmap, and the termination SN corresponding to the PDCP SN Bitmap is carried in the PDCP control PDU.

4) At least one of the PDCP SN pattern, the start SN corresponding to the PDCP SN pattern, and the termination SN corresponding to the PDCP SN pattern is carried in the PDCP control PDU.

5) The PDCP control PDU carries the start SN and the end SN of the commonly maintained PDCP SNs.

6) carrying the number of commonly maintained PDCP SNs in the PDCP control PDU;

7) carrying the length of the commonly maintained PDCP SN Bitmap in the PDCP control PDU;

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

9) The commonly maintained PDCP SN list is carried in the PDCP control PDU.

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

Wherein, the PDCP SN/PDCP SN Bitmap/PDCP SN pattern/PDCP SN list assigned to the first sending electronic device, 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 SNpattern/PDCP SN list allocated for the second electronic device, or the PDCP SN/PDCP SN Bitmap/PDCP SN pattern/PDCP SN list used by the second sending electronic device belongs to the jointly maintained PDCP SN/ PDCP SN Bitmap/PDCP SN pattern/PDCP SN list. For example, the PDCP SN list assigned to the first sending electronic device is 1, 3, 5, and/or the PDCP SN list assigned to the second sending electronic device is 0, 2, 4; then 0, 2, 4, Or, 1, 3, 5, or 0, 1, 2, 3, 4, 5 belong to the commonly maintained PDCP SN list.

In the embodiment of the present invention, the PDCP SN sent by the first sending electronic device to the second sending electronic device and/or receiving electronic device includes two types: the first is the actual PDCP SN, and the second is the actual PDCP SN and virtual PDCPSN. The actual PDCP SN is also called the second PDCP SN in this embodiment, and the virtual PDCP SN is also called the first PDCP SN in this embodiment. Wherein, the first PDCP SN of the first sending electronic device refers to the PDCP SN maintained by the first sending electronic device itself, and has no association relationship with the first PDCP SN of the second sending 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 first sending electronic device sets the PDCP SN and/or state variable of the PDCP data packet The processing flow, as shown in Figure 8, includes:

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

Here, the initial value of TX-NEXT is not necessarily 0; the initial value of TX-NEXT is related to the pre-agreed PDCP SN and/or PDCP SN allocation rules; or, the initial value of TX-NEXT is related to the first sending electronic device The PDCP SN sent to the second sending electronic device and/or the receiving electronic device and/or the PDCP SN allocation rules are related.

Step 1b, associating the COUNT of the PDCP data packet with the value of TX-NEXT.

Step 1c, setting the PDCP SN of the PDCP data packet as a value obtained by moduloing the function of the size of the PDCP SN by using TX-NEXT.

In some embodiments, the PDCP SN of the PDCP data packet can be set as TX-NEXT modulo 2 ^{[PDCP SN -SizeDL]} .

In some other embodiments, the PDCP SN of the PDCP data packet may be set as TX-NEXT modulo 2 ^{[PDCP SN -SizeUL]} .

Step 1d: Set the value of TX-NEXT to the next PDCPSN adjacent to the current PDCP SN based on the first information.

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

When the PDCP SN sent by the first sending electronic device to the second sending electronic device and the receiving electronic device is the first PDCP SN and the second PDCP SN, the receiving electronic device uses the second PDCP SN to perform PDCP packet processing between PDCP entities; The first sending electronic device and the second sending electronic device use their own first PDCP SN to group PDCP data packets, transmit PDCP data packets, set PDCP SNs, maintain state variables of PDCP data packets, and perform PDCP entity internal At least one of the PDCP data packet processing; wherein, 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 only considers its own PDCP SN, and is not affected by other Impact of PDCP entities. Even if both the first sending electronic device and the second sending electronic device send PDCP SN to the receiving electronic device, the first PDCP SN of the first sending electronic device is a continuous integer starting from 0, and the initial value of TX-NEXT is 0, Every time a PDCP PDU is generated, the value of TX-NEXT is incremented by 1.

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 first PDCP SN and the second PDCP SN, the sending method of the first PDCP SN and the second PDCP SN Including any 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 the 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;

The second PDCP SN is carried in the 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;

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

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

The first PDCP SN and the second PDCP SN are sent through dedicated signaling.

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 first PDCP SN and the second PDCP SN, or when there is only one PDCP SN, the PDCP data packet also includes the first Indication information, the first indication information is used to indicate at least one of the following: the type of the PDCP data packet, the format of the PDCP data packet, and the PDCP SN information carried in 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 a new The format is still the original format, which PDCP SN is included, and at least one of several PDCP SNs is included; the PDCP SN information carried by the PDCP data packet refers to the PDCP SN carried by the PDCP data packet, such as the PDCP SN The data packet carries the first PDCP SN, or the second PDCP SN, or carries the first PDCP SN and the second PDCP SN. When the PDCP SN information carried in the PDCP data packet is that the PDCP data packet carries the first PDCP SN or the second PDCP SN, another PDCP SN not carried in the PDCP data packet may be sent by dedicated signaling, or may be Another PDCP SN does not exist or is not used. Here, the R bit in the PDCP data packet may be used to identify the first indication information.

In some embodiments, the PDCP data packet further includes second indication information, and 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 header of the PDCP data packet or in the data packet, the second Whether the two PDCP SNs are in the packet header of the PDCP data packet or in the data packet, the order of the second PDCP SN and the first PDCP SN. Wherein, the order of the second PDCP SN and the first PDCP SN means that when the second PDCP SN and the first PDCP SN both carry one of the following, they are both in the PDCP data packet, and both are in the data packet In the header of the data packet, one is in the header of the data packet and the other is in the data packet, the first PDCP SN is in the front, and the second PDCP SN is in the back; or, the first PDCP SN is in the back, and the second PDCP SN is in the back PDCP SN is in front.

During 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. That is, the network device sends the content indicated by the first indication information and/or the second indication information to the first sending device and/or the second sending device; or, the first sending electronic device determines the first indication information and/or the first indication information according to predefined information or the content indicated by the second indication information.

When the PDCP SN sent by the first sending electronic device to the second sending electronic device and/or the receiving electronic device includes the actual PDCP SN and the virtual PDCP SN, the first sending electronic device sets the state of the PDCP packet according to the virtual PDCP SN Another optional processing procedure for variables includes at least one of the following: the source network device sets the initial value of TX-NEXT to 0, and when the source network device generates the first PDCP SDU, sets the PDCP SN corresponding to the first PDCP SDU is 0, that is, TX-NEXT modulo 2 ^[12] ; suppose PDCP-SN-SizeDL=12, COUNT is 1, HFN=0, and TX-NEXT=0+1=1. When the source network device generates the second PDCP SDU, according to the current TX-NEXT value of 1, determine that the COUNT value of the PDCP PDU corresponding to the second PDCP SDU is 1, and the PDCP SN is 1; the value of TX-NEXT Add 1 to the current 1, that is, the value of TX-NEXT is 2; and so on.

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 first PDCP SN and the second PDCP SN, the first sending electronic device sets another possible state variable of the PDCP data packet. The optional processing flow is as follows, including:

Step 2a, set the value of TX-NEXT based on the first PDCP SN.

In step 2b, an initial value of TX-NEXT is set based on the first PDCP SN.

Here, the initial value of TX-NEXT is not necessarily 0; the initial value of TX-NEXT is related to the pre-agreed first PDCPSN and/or PDCP SN allocation rules; or, the initial value of TX-NEXT is related to the first sending electronic The first PDCP SN and/or PDCP SN assignment rules sent by the device to the second sending electronic device and/or the receiving electronic device are related.

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

Step 2d, setting the PDCP SN of the PDCP data packet as a value obtained by moduloing the function of the size of the PDCP SN by using TX-NEXT.

In some embodiments, the PDCP SN of the PDCP data packet can be set as TX-NEXT modulo 2 ^{[PDCP SN -SizeDL]} .

In some other embodiments, the PDCP SN of the PDCP data packet may be set as TX-NEXT modulo 2 ^{[PDCP SN -SizeUL]} .

Step 2e, based on the first PDCP SN, set the value of TX-NEXT to the next PDCP SN adjacent to the current PDCP SN.

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

Another optional processing flow of the data packet processing method provided by the embodiment of the present invention, as shown in FIG. 9 , includes the following steps:

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

In the embodiment of the present invention, the PDCP SNs and/or PDCP SN allocation rules of the at least two sending electronic devices may be sent by any sending electronic device to the receiving electronic device.

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

Alternatively, the PDCP SN and/or PDCP SN assignment rules of the at least two sending electronic devices may be sent by each sending electronic device to the receiving electronic device; and/or the PDCP SN allocation rules are sent to the receiving electronic device, and the second sending electronic device also sends the PDCP SNs and/or PDCP SN allocation rules of at least two sending electronic devices to the receiving electronic device.

Alternatively, the PDCP SN and/or PDCP SN allocation rule of each sending electronic device is sent to the receiving electronic device by the sending electronic device itself and/or other sending electronic devices; that is, the first sending electronic device sends the first The PDCP SN and/or PDCP SN allocation rule of the electronic device is sent to the receiving electronic device, and the second electronic device sends the PDCP SN and/or PDCP SN allocation rule of the second electronic device to the receiving electronic device. Alternatively, in addition to sending the PDCP SN and/or PDCP SN allocation rules of the first electronic device to the receiving electronic device, the first sending electronic device also sends the PDCP SN and/or PDCP SN allocation rules of the second electronic device to the receiving electronic device ; and the second electronic device not only sends the PDCP SN and/or PDCP SN allocation rules of the second electronic device to the receiving electronic device, but also sends the PDCP SN and/or PDCP SN allocation rules of the first electronic device to the receiving electronic device. Alternatively, the first sending electronic device sends the PDCP SN and/or PDCP SN allocation rules of the second electronic device to the receiving electronic device, and the second sending electronic device sends the PDCP SN and/or PDCP SN allocation rules of the first electronic device to Receive electronic equipment.

It should be noted that the description of the PDCP SN and the PDCP SN allocation rule in the embodiment of the present invention is the same as that of the above step S201, and will not be repeated here. Among them, the description of PDCP SN and PDCP SN allocation rules can at least include one or more of the following: who determines the PDCP SN and PDCP SN allocation rules, what parameters are used to determine the PDCP SN and PDCP SN allocation rules, PDCP SN and the form and content of 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 assignment 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 within a PDCP entity and processing the PDCP data packet between PDCP entities. Wherein, the processing includes at least one of the following: reordering of PDCP data packets, redundancy detection of PDCP data packets, and deletion of PDCP data packets. For example, if the receiving electronic device receives the first PDCP data packet sent by the first sending electronic device and the second PDCP data packet sent by the second sending electronic device; The PDCP data packet is processed within the entity, and the receiving electronic device processes the second PDCP data packet as processing the PDCP data packet within the PDCP entity; the receiving electronic device processes the first PDCP data packet and the second PDCP data packet To process PDCP packets between PDCP entities. Correspondingly, before processing the PDCP data packet, the receiving electronic device needs to receive the PDCP data packet and/or PDCP control PDU first.

When the PDCP SN includes the first PDCP SN and the second PDCP SN, the receiving electronic device processes the PDCP data packet according to the PDCPSN, including:

The receiving electronic device performs processing in the PDCP entity on the PDCP data packet according to the first PDCP SN; and/or, the receiving electronic device performs processing on the PDCP data packet according to the second PDCP SN Processing between PDCP entities.

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

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

During specific implementation, whether the receiving electronic device processes the PDCP data packet within the PDCP entity and/or between PDCP entities is determined by preset or network device configuration, or by the receiving electronic device according to the PDCP SN and at least one of the state variables. For example, the network device configures the receiving electronic device to deliver PDCP data packets in order to the upper layer. If the in-order delivery in the PDCP entity is configured, when the t-reordering timer expires, the PDCP entity of the receiving electronic device sends The higher layer delivers the PDCP data packets sequentially; and/or, in the case of RCVD-COUNT=RX-DELIV, the PDCP entity of the receiving electronic device delivers the PDCP data packets sequentially to the higher layer.

Among them, the processing of the receiving electronic device for the PDCP data packet sent by the first sending electronic device, or the processing of the receiving electronic device for the PDCP data packet sent by the first sending entity of the sending electronic device belongs to the processing of the PDCP data packet in the PDCP entity . Similarly, the receiving electronic device's processing of the PDCP data packet sent by the second sending electronic device, or the receiving electronic device's processing of the PDCP data packet sent by the second sending entity of the sending electronic device belongs to the PDCP data packet within the PDCP entity. deal with. After the receiving electronic device performs intra-entity processing on the PDCP data packets sent by the first sending electronic device and the second sending electronic device, or the receiving electronic device separately sends the PDCP data sent by the first sending entity and the second sending entity of the sending electronic device After the packet is processed within the entity, uniformly process the PDCP data packets sent by the first sending electronic device and the second sending electronic device, or uniformly process the PDCP data packets sent by the first sending entity and the second sending entity of the sending electronic device The processing is called the processing of PDCP data packets between PDCP entities. Optionally, processing within PDCP entities may not be performed, and only processing between PDCP entities may be performed, or, processing between PDCP entities may not be performed, and only processing within PDCP entities 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 the first PDCP entity of the terminal device and/or the second PDCP entity of the terminal device; or, the receiving entity in the terminal device may also be It is the first functional module in the PDCP entity of the terminal device and/or the 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 It may be the first functional module in the PDCP entity in the terminal device and/or the second functional module in the PDCP entity in the terminal device.

In this 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 a terminal device, and the 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, 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 The device is the first sending entity and/or the second sending entity in the terminal device; or, the receiving electronic device is a target network device, and the sending electronic device is the first sending entity and/or the second sending entity in the terminal device entity.

For the DRB bearer or SRB bearer, the terminal device supports two paths of transmission with the source network device and the target network device at the same time. The source network device sends a DRB bearer or SRB bearer to the terminal device, and the target network device also sends a DRB bearer to the terminal device. Or the scenario of SRB bearer, the PDCP data packet processing method in the embodiment of the present invention will be described in detail.

Taking the PDCP SN interacted between the source network device and the target network device as the actual PDCP SN as an example, a detailed processing flow of the PDCP packet processing method is shown in Figure 10, including:

In step S401, the source network device exchanges PDCP SN or PDCP SN assignment rules with the target network device.

In the embodiment of the present invention, it may be considered that the source network device is the first sending electronic device, and the target network device is the second sending electronic device. Through the exchange of PDCP SN or PDCP SN allocation rules between the source network device and the target network device, determine the PDCP SN used by the source network device when the source network device and the terminal device perform DRB bearer or SRB bearer transmission; and determine the target network device and the terminal device. PDCP SN used by the target network device when DRB bearer or SRB bearer is transmitted. Wherein, the source network device and the target network device exchange PDCP SN and/or PDCP SN allocation rules, which refers to the PDCP SN and/or PDCP SN and/or PDCP SN that the source network device will determine when the target network device and the terminal device perform DRB bearer or SRB bearer transmission. or the PDCP SN allocation rule sent to the target network device; or, the PDCP SN and/or PDCP SN allocation rule adopted by the source network device when it performs DRB bearer or SRB bearer transmission with the terminal device, and the determined by the target network device and The PDCP SN and/or PDCP SN allocation rules adopted by the terminal device for DRB bearer or SRB bearer transmission are sent to the target network device; or the source network device performs data bearer (Data Resource Bearer, DRB) or signaling between itself and the terminal device Send the PDCP SN and/or PDCP SN allocation rules used for the bearer (Signal Resource Bearer, SRB) transmission to the target network device; and the PDCP used by the target network device for DRB bearer or SRB bearer transmission between itself and the terminal device The SN and/or PDCP SN allocation rules are sent to the source network device. As shown in FIG. 11 , the exchange of PDCP SN or PDCP SN allocation rules between the source network device and the target network device may be the exchange of PDCP SN or PDCP SN allocation rules between the PDCP entity of the source network device and the PDCP entity of the target network device.

For example, in the handover process, the source network device determines to perform a handover process 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 device determines to use the bearer split method to transmit the source network device, target network device and terminal device; as shown in Figure 12, according to the order of PDCP SDUs, the first, third, fifth, seventh... A PDCP SDU is transmitted from the source network device, and the corresponding PDCP SN list is 1, 3, 5, 7... or the PDCP SN pattern is {010101..}; the 0th, 2, 4, 6.. PDCP SDUs are sent from the target For network device transmission, the corresponding PDCP SN list is 0, 2, 4, 6... or PDCP SN pattern is {101010..}. The source target network exchanges the determined PDCP SN list or PDCP SN pattern transmitted by the target target network, and the PDCP SDU to the target network device.

Wherein, the interactive PDCP SN and/or PDCP SN assignment rule may be determined by the source network device, may also be determined by the target network device, or may be jointly determined by the source network device and the target network device. Optionally, it can be based on 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, and cell interference , cell channel quality, etc., determine the respective PDCP SN and/or PDCP SN of the source network device and the target network device.

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

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

Taking the source network device as an example, when the source network device generates the first PDCP SDU, it will determine that the PDCP SN of the PDCP packet corresponding to the first PDCP SDU is 1 and TX_NEXT is 1 according to the determined PDCP SNlist or PDCP SN pattern , COUNT is 1 (assuming HFN=0). When the source network device generates the second PDCP SDU, according to the determined PDCP SNlist or PDCP SN pattern, it will be determined that the PDCP SN of the PDCP packet corresponding to the second PDCP SDU is 3, TX_NEXT is 3, and COUNT is 3 (assuming HFN = 0), and so on.

Step S403, the source network device sends the interactive PDCP SN or PDCP SN assignment 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 by using a PDCP control PDU. Optionally, at least one PDCPSN is included in the PDCP control PDU. Correspondingly, the terminal device determines the PDCP SN used by the target network device according to the PDCP SN pattern or PDCPSN bitmap or PDCP SN list sent by the source network device; if the continuous PDCPSN starting from 0 removes the PDCP SN used by the source network device, it is PDCP SN used by the target network device.

In some 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, at least one PDCP SN is included in the PDCP control PDU. Correspondingly, the terminal device determines the PDCP SN used by the source network device and/or the target network device according to the PDCP SN pattern or PDCP SN bitmap or PDCP SN list sent by the source network device. Specifically, the source network device may also send the PDCP SN pattern or PDCP SN bitmap or PDCP SN list to the terminal device through RRC signaling, MAC CE, physical layer signaling bearer, or PDCP data packet.

During specific implementation, a schematic diagram of the format of the PDCP control PDU carrying the PDCP SN bitmap indication is shown in FIG. 13 . Among them, the value of D/C is 1, which means that the PDCP PDU is a PDCP control PDU, and the value of PDU type is SN interaction type or PDCP SN type; Start FMC, which represents the COUNT corresponding to the starting SN of the interaction; PDCP SN bitmap indicates from Whether each SN starting from the original SN is used by the source network device.

Step S404, the terminal device determines whether to submit the PDCP data packet to the upper layer according to the interactive PDCP SN or the PDCP SN allocation rule.

In some embodiments, the terminal device determines the PDCP SN information of the PDCP data packet transmitted between the terminal device and the source network device, and the PDCP SN information between the terminal device and the target network device according to the received PDCP SN bitmap, PDCP SN list or PDCPSN pattern. PDCP SN information of the PDCP packets transmitted between them. 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 device determines whether the conditions for submitting the PDCP data packet to the upper layer are satisfied according to the state variable of the receiving end, the PDCP SN list or PDCP SN pattern or PDCP SN bitmap, and the PDCP SN of the PDCP data packet. If t-reordering=10ms at this time, which is earlier than t-reordering timeout, the condition of RCVD_COUNT=RX_EDLIV is met. For example, when RCVD_COUNT=RX_DELIV=7, the PDCP entity of the terminal device, such as the terminal device PDCP entity of the corresponding source network device Or the function module triggers delivery of PDCP data packets to the upper layer in the order of PDCP SNs. In the embodiment of the present invention, before the terminal device submits the PDCP data packets, it needs to perform reordering processing, redundancy detection processing and deletion processing on the received PDCP data packets.

For the DRB bearer or SRB bearer, the terminal device supports two paths of transmission with the source network device and the target network device at the same time. The source network device sends a DRB bearer or SRB bearer to the terminal device, and the target network device also sends a DRB bearer to the terminal device. Or the scenario of SRB bearer, the PDCP data packet processing method in the embodiment of the present invention will be described in detail.

Take the PDCP SN that the source network device interacts with the target network device as the first PDCP SN and the second PDCP SN as an example, the first PDCP SN is a virtual PDCP SN, and the second PDCP SN is an actual PDCP SN; PDCP packet processing method Another detailed processing flow of , as shown in Figure 14, includes:

In step S501, the source network device exchanges PDCP SN or PDCP SN allocation rules with the target network device.

In the embodiment of the present invention, it may be considered that the source network device is the first sending electronic device, and the target network device is the second sending electronic device. Through the exchange of PDCP SN or PDCP SN allocation rules between the source network device and the target network device, determine the PDCP SN used by the source network device when the source network device and the terminal device perform DRB bearer or SRB bearer transmission; and determine the target network device and the terminal device. PDCP SN used by the target network device when DRB bearer or SRB bearer is transmitted. Wherein, the source network device and the target network device exchange PDCP SN and/or PDCP SN allocation rules, which refers to the PDCP SN and/or PDCP SN and/or PDCP SN that the source network device will determine when the target network device and the terminal device perform DRB bearer or SRB bearer transmission. or the PDCP SN allocation rule sent to the target network device; or, the PDCP SN and/or PDCP SN allocation rule adopted by the source network device when it performs DRB bearer or SRB bearer transmission with the terminal device, and the determined by the target network device and The PDCP SN and/or PDCP SN allocation rules used by the terminal device for DRB bearer or SRB bearer transmission are sent to the target network device; or the PDCP SN used by the source network device for DRB bearer or SRB bearer transmission between itself and the terminal device and/or send the PDCP SN allocation rule to the target network device; and, the target network device sends the PDCP SN and/or the PDCP SN allocation rule used when the target network device performs DRB bearer or SRB bearer transmission with the terminal device to the source network device.

In step S502, the source network device and the target network device use the virtual PDCP SN and the actual PDCP SN to group and transmit PDCP data packets, and maintain the PDCPSN at the sending end and/or state variables.

The source network device is used as an example for illustration below, and the operation performed by the target network device is the same as that of the source network device.

The source network device uses the virtual PDCP SN to group PDCP data packets, transmit PDCP PDUs, and maintain the PDCP SN and/or state variables at the sending end. For example, the source network device sets the initial value of TX_NEXT to 0; when the source network device generates the first PDCP SDU, set the PDCP SN corresponding to the first PDCP SDU to 0, that is, TX_NEXT modulo 2 ^[12] , assuming that PDCP - SN-SizeDL=12, COUNT is 1 (assuming HFN=0); then, another TX_NEXT=0+1=1. When the source network device generates the second PDCP SDU, it determines that the COUNT of the second PDCP PDU is 1 and the SN is 1 according to the current value of TX_NEXT (1). Then, the value of TX_NEXT is increased by 1 to become 2, and so on.

The virtual PDCP SN value can be carried in the PDCP PDU. For example, the virtual PDCP SN value carried in the PDCP PDU sent by the source network device is 1', 2', 3', 4'..., which is a set of ordered arrangement Numerical or alphabetic or logo, etc.

The actual PDCP SN value can also be carried in the PDCP PDU. For example, the actual PDCP SN value carried in the PDCP PDU sent by the source network device is 1, 3, 5, 7..., and the PDCP PDU sent by the target network device carries The actual PDCPSN values are 2, 4, 6, 8....

The schematic diagrams 1, 2 and 3 of the format of the PDCP PDU carrying the actual PDCP SN and the virtual PDCP SN are shown in Fig. 15a, Fig. 15b and Fig. 15c respectively. In Figure 15a and Figure 15b, the virtual PDCP SN is located in the first byte and the second byte, and the actual PDCP SN is located in the third byte and the fourth byte. In Figure 15c, the virtual PDCP SN is located in the first byte, the second byte and the third byte, and the actual PDCP SN is located in the fourth byte, fifth byte and sixth byte , or the virtual PDCP SN is located in the first byte and the second byte, the actual PDCP SN is located in the fifth byte and the sixth byte, and the third byte has both the actual PDCP SN and the virtual The PDCP SN. Optionally, the virtual PDCP SN precedes the temporal PDCP SN; of course, the virtual PDCP SN can also precede the temporal PDCP SN.

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

In the embodiment of the present invention, the terminal device performs operations such as reordering within the entity and sequential delivery within the entity according to the virtual PDCP SN. Wherein, whether to perform the reordering within the entity and the sequential delivery within the entity may be predefined or configured by the network device.

The processing of the PDCP PDU includes: the terminal device performs t-reordering maintenance based on the virtual PDCP SN, and intra-entity reordering. Set RX_COUNT based on the virtual PDCP SN. Based on virtual PDCP SN maintenance state variables, such as RX_NEXT, RX_REORD, RX_DELIV. Execute redundant packet deletion within the entity based on the virtual PDCP SN, that is, delete received data packets with the same virtual PDCP SN. Intra-entity in-order delivery is performed based on the virtual PDCP SN. When submitting in sequence within the execution entity, or submitting the PDCP data packet to the upper layer, optionally, the virtual PDCP SN is replaced with the actual PDCP SN. The PDCP packet is decompressed according to the virtual PDCP SN. The PDCP packet is decrypted according to the virtual PDCP SN. The integrity protection verification of the PDCP data packet is performed according to the virtual PDCP SN.

During specific implementation, set initial RX_NEXT=0.RX_DELIV=0. Assume that the virtual PDCP SN of the PDCP packet to be received is 0.1.2.3.4. The virtual PDCP SN of the currently received PDCP PDU is 4, COUNT=RCVD_COUNT=4, and since RCVD_COUNT>=RX_NEXT, set RX_NEXT=4+1=5. Since t-Reordering is not running, and RX_DELIV<RX_NEXT, enable reordering Sort timer, set RX_REORD=RX_NEXT=5. Then, the terminal device receives the PDCP PDU with SN=2. Then the corresponding COUNT=RCVD_COUNT=2 is put into the reordering buffer queue, and RX_NEXT is not updated; at this time, RCVD_COUNT<RX_NEXT. When the timer expires, deliver the PDCP PDUs with COUNT=2 and 5 to the upper layer in ascending order.

In step S504, the terminal device performs inter-entity processing on the PDCP PDU based on the actual PDCP SN.

In the embodiment of the present invention, the processing between PDCP entities includes operations such as reordering between entities, sequential delivery between entities, and deletion of redundant packets between entities.

As shown in FIG. 16 , the PDCP PDU of the PDCP entity sent by the source network device and the target network device to the terminal device, such as the PDCP data PDU, both carry the actual PDCP SN and the virtual PDCP SN. Both the source network device and the target network device perform PDCP PDU sorting within the entity based on the virtual PDCP SN, and a specific network entity or layer (such as a layer above the source network device PDCP and the target network device PDCP) is based on the actual PDCP SN performs PDCP PDU ordering among entities.

It should be noted that, the above is for the DRB bearer or SRB bearer, the terminal device supports two transmission paths with the source network device and the target network device at the same time, the source network device sends the DRB bearer or SRB bearer to the terminal device, and the target network device The scenario of sending the DRB bearer or the SRB bearer to the terminal device is also described in detail for the PDCP data packet processing method in the embodiment of the present invention. In practical applications, the embodiment of the present invention is also applicable to the case where the terminal device supports two paths of transmission with the source network device and the target network device at the same time. The terminal device sends a DRB bearer or an SRB bearer to the source network device, and the terminal device also sends a The device also sends the DRB bearer or SRB bearer scenario; in this scenario, the terminal device can exchange PDCP SN and/or PDCP SN allocation rules with the network device. Specifically, the PDCP SN (such as PDCP SN pattern or PDCP SN bitmap or PDCP SN list) and/or PDCP SN allocation rules can be sent through RRC signaling, MAC CE, physical layer signaling bearer, PDCP control PDU, and PDCP data packets to the network device.

In each of the above scenarios, the sending electronic device may be a PDCP entity inside the terminal device, and the receiving electronic device may be another PDCP entity inside the terminal device. During specific implementation, when transmitting uplink data, a PDCP entity or PDCP functional module of the terminal device sends a PDCP data packet to the source network device, and another PDCP entity or PDCP functional module of the terminal device sends a PDCP data packet to the target network device; In addition, one PDCP entity or PDCP function module of the terminal device may perform PDCP SN and/or PDCPSN allocation rule interaction with another PDCP entity or PDCP function module of the terminal device. For downlink data transmission, the source network device sends a PDCP data packet to a PDCP entity or PDCP functional module of the terminal device, and the target network device sends a PDCP data packet to another PDCP entity or PDCP functional module of the terminal device; in addition, the terminal device's One PDCP entity or PDCP function module can also perform PDCP SN and/or PDCP SN assignment rule interaction with another PDCP entity or PDCP function module of the terminal device.

The data packet processing method provided by the embodiment of the present invention clarifies that the terminal device performs data transmission with the source network device and the target network device at the same time, especially how to process the PDCP data packet when there are two corresponding PDCP entity transmission buffers and/or receiving buffers. The PDCP SN and the state variables of PDCP packets are managed. The problem of inconsistent understanding of PDCP SN by the terminal device, the source network device and the target network device caused by the PDCP SN and/or state variable setting of the PDCP data packet is avoided, and the problem of incorrect processing of the received PDCP data packet is avoided. At the same time, it avoids the problem of submitting the delay to the upper layer after receiving the PDCP data packet, and ensures the overall data transmission rate of the system.

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

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

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

The first sending unit 602 is configured to send the PDCP SN and/or the PDCP SN assignment rule to the second sending electronic device.

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

The second sending unit 603 is 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 are determined by the sending electronic device, or the PDCP SN is determined by the second sending electronic device, or the PDCP SN is determined by the sending electronic device. The device and the second sending electronic device are jointly determined.

In the embodiment of the present invention, the PDCP SN and/or PDCP SN allocation rules are determined according to at least one of the following: 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, and cell channel quality.

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

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

The PDCP control PDU carries the information of the PDCP SN, and/or carries an indication of the type of control information contained in the PDCP SN information;

And/or, carrying a commonly maintained PDCP SN in the PDCP control PDU;

And/or, at least one of the PDCP SN Bitmap, the start SN corresponding to the PDCP SN Bitmap, and the termination SN corresponding to the PDCP SN Bitmap are carried in the PDCP control PDU;

And/or, at least one of the PDCP SN pattern, the start SN corresponding to the PDCP SN pattern, and the termination SN corresponding to the PDCP SN pattern are carried in the PDCP control PDU;

And/or, the PDCP control PDU carries the start SN and the end SN of the commonly maintained PDCP SN;

And/or, carrying the number of commonly maintained PDCP SNs in the PDCP control PDU;

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

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

And/or, the commonly maintained PDCP SN list is carried in the PDCP control PDU.

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

Setting the value of TX-NEXT and/or the initial value of TX-NEXT based on the first information;

Associating the count value COUNT of the PDCP data packet with the value of TX-NEXT;

Setting the PDCP SN of the PDCP data packet is a value obtained by moduloing the function of the size of the PDCP SN by using TX-NEXT;

Set the value of TX-NEXT to the next PDCP SN adjacent to the 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 following: the first sending electronic device packs and transmits PDCP data packets, sets the PDCP SN and/or state variables of the PDCP data packets, and the receiving electronic device performs PDCP packet processing within the PDCP entity;

The second PDCP SN is used for receiving electronic equipment to process PDCP data packets between PDCP entities.

In the embodiment of the present 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 the 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;

Or, the second PDCP SN is carried in the 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;

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

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

Or, the first PDCP SN and the second PDCP SN are sent through dedicated signaling.

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

In the embodiment of the present invention, the PDCP data packet further includes second indication information, and 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 header of the PDCP data packet or in the data packet, the second Whether the two PDCP SNs are in the packet header of the PDCP data packet or in the data packet, the order of the second PDCP SN and the first PDCP SN.

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

The type of the PDCP data packet, the format of the PDCP data packet, the PDCPSN information carried in the PDCP data packet, whether the PDCP data packet contains the first PDCP SN, whether the PDCP data packet contains the The second PDCP SN, the first PDCP SN is in the header of the PDCP data packet or in the data packet, the second PDCP SN is in the header of the PDCP data packet or in the data packet, the second PDCP SN and The sequence of the first PDCP SNs.

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

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

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

Associating the count value COUNT of the PDCP data packet with the value of TX-NEXT;

Setting the PDCP SN of the PDCP data packet is a value obtained by moduloing the size of the PDCP SN by using TX-NEXT;

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

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

In the 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;

Alternatively, 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;

Alternatively, 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;

Alternatively, 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 device is a target network device and a source network equipment.

In the embodiment of the present invention, the pre-agreed PDCP SN, or the PDCP SN sent by the first sending electronic device to the second sending electronic device and/or receiving electronic device includes at least one of the following: 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. The composition structure of the receiving electronic device 800, as shown in FIG. 18 , includes:

The receiving unit 801 is configured to receive PDCP serial numbers SN and/or PDCP SN allocation rules of at least two sending electronic devices;

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

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

The first PDCP SN is used for at least one of the following: the sending electronic device packs and transmits PDCP data packets, sets the PDCP SN and/or state variables of the PDCP data packets, and the receiving electronic device performs PDCP PDCP packet processing within the entity;

The second PDCP SN is used for the receiving electronic device to process PDCP data packets between PDCP entities.

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

And/or, perform inter-PDCP entity processing on the PDCP data packet according to the second PDCP SN.

In the embodiment of the present 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 the 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;

Or, the second PDCP SN is carried in the 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;

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

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

Or, the first PDCP SN and the second PDCP SN are sent through dedicated signaling.

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

The type of the PDCP data packet, the format of the PDCP data packet, and the PDCPSN information carried in the PDCP data packet.

In the embodiment of the present invention, the PDCP data packet further includes second indication information, and 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 header of the PDCP data packet or in the data packet, the second Whether the two PDCP SNs are in the packet header of the PDCP data packet or in the data packet, the order of the second PDCP SN and the first PDCP SN.

In the 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 the 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 within the PDCP entity and/or between PDCP entities is determined by preset or network device configuration, or by the second processing unit according to determined by at least one of the PDCPSN and state variables.

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

And/or, in the case of RCVD-COUNT=RX-DELIV, the second processing unit is configured to determine to deliver the PDCP data packets sequentially to a higher layer.

In the embodiment of the present invention, the PDCP SN and/or PDCP SN allocation rules of the at least two sending electronic devices are sent to the receiving electronic device by any sending electronic device;

Or, the PDCP SN and/or PDCP SN allocation rules of the at least two sending electronic devices are sent to the receiving electronic device by a designated sending electronic device;

Or, the PDCP SN and/or PDCP SN allocation rules of the at least two sending electronic devices are sent to the receiving electronic device by each sending electronic device;

Or, the PDCP SN and/or PDCP SN assignment rule of each sending electronic device is sent to the receiving electronic device by the sending electronic device itself and/or other sending electronic devices.

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

Or, the PDCP SN and/or PDCP SN allocation rules of the at least two sending electronic devices are determined by a designated sending electronic device;

Alternatively, the PDCP SNs and/or PDCP SN allocation rules of the at least two sending electronic devices are jointly determined by the at least two sending electronic devices.

In the embodiment of the present invention, the PDCP SN and/or PDCP SN allocation rules are determined according to at least one of the following: 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, and cell channel quality.

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

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

The PDCP control PDU carries the information of the PDCP SN, and/or carries an indication of the type of control information contained in the PDCP SN information;

And/or, carrying a commonly maintained PDCP SN in the PDCP control PDU;

And/or, at least one of the PDCP SN Bitmap, the start SN corresponding to the PDCP SN Bitmap, and the termination SN corresponding to the PDCP SN Bitmap are carried in the PDCP control PDU;

And/or, at least one of the PDCP SN pattern, the start SN corresponding to the PDCP SN pattern, and the termination SN corresponding to the PDCP SN pattern are carried in the PDCP control PDU;

And/or, the PDCP control PDU carries the start SN and the end SN of the commonly maintained PDCP SN;

And/or, carrying the number of commonly maintained PDCP SNs in the PDCP control PDU;

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

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

And/or, the commonly maintained PDCP SN list is carried 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;

Alternatively, 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 a terminal device;

Alternatively, 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 a terminal device.

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

An embodiment of the present invention also provides a sending electronic device, including a processor and a memory for storing a computer program that can run on the processor, wherein, when the processor is used to run the computer program, execute the above-mentioned terminal device to execute The steps of the packet processing method.

An embodiment of the present invention also provides a receiving electronic device, including a processor and a memory for storing a computer program that can run on the processor, wherein, when the processor is used to run the computer program, execute the above-mentioned network device to execute The steps of the packet processing method.

FIG. 19 is a schematic diagram of the hardware composition structure of an electronic device (sending electronic device and receiving electronic device) according to an embodiment of the present invention. The electronic device 700 includes: at least one processor 701 , memory 702 and at least one network interface 704 . Various components in the electronic device 700 are coupled together through a bus system 705 . It can be understood that the bus system 705 is used to realize connection and communication between these components. In addition to the data bus, the bus system 705 also includes a power bus, a control bus and a status signal bus. However, the various buses are labeled as bus system 705 in FIG. 19 for clarity of illustration.

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

The memory 702 in the embodiment of the present invention is used to store various types of data to support the operation of the electronic device 700 . Examples of such data include: any computer programs for operating on electronic device 700 , such as application programs 7022 . The program for realizing the method of the embodiment of the present invention may be included in the application program 7022 .

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

In an exemplary embodiment, the electronic device 700 may be implemented by one or more Application Specific Integrated Circuit (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, ProgrammableLogic Device), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), FPGA, general-purpose processor, controller, MCU, MPU, or other electronic components to implement the aforementioned method.

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

Optionally, the storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process in each method of the embodiment of the present application, for the sake of brevity, details are not repeated here.

Optionally, the storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes in the methods of the embodiments of the present application, and details are not repeated here 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 should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

The above description is only a preferred embodiment of the present invention, and is not used to limit the protection scope of the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included in the within the protection scope of the present invention.

Claims (72)

1. 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.

2. The method of claim 1, wherein the method further comprises:

the first transmitting electronic device transmits PDCP SNs and/or PDCP SN allocation rules to the second transmitting electronic device.

3. 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.

4. The method of claim 1 or 2, 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.

5. The method according to claim 1 or 2, 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 (quality of service) requirements, scheduling conditions, SPS (semi-persistent scheduling) configuration information, CG configuration information, activated carrier information, activated SPS information, activated CG information, traffic volume, service type, cell load, cell interference and cell channel quality.

6. The method according to claim 1 or 2, 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.

7. 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 jointly maintained 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.

8. The method according to claim 1 or 2, 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.

9. The method according to claim 1 or 2, 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 the grouping and transmission of PDCP data packets, sets the PDCP SN and/or state variable of the PDCP data packets, and the receiving electronic equipment carries out the PDCP data packet processing in the PDCP entity;

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

10. 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 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;

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 sent 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 sent through a dedicated signaling;

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

11. The method as claimed in claim 9, wherein 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.

12. The method as claimed in claim 9, 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.

13. The method of claim 9, 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 carried PDCP SN information of 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 header or the data packet of the PDCP data packet, whether the second PDCP SN is in the header or the data packet of the PDCP data packet, and the sequence of the second PDCP SN and the first PDCP SN.

14. The method as claimed in claim 9, wherein the setting of the state variable of the PDCP 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, wherein the initial value can 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.

15. The method according to claim 1 or 2, wherein the first transmitting electronic device periodically transmits PDCP SNs and/or PDCP SN allocation rules;

alternatively, the first transmitting electronic device transmits the PDCP SNs and/or PDCP SN allocation rules based on an event.

16. The method of claim 15, wherein the event comprises at least one of:

PDCP SN pattern change and PDCP SN allocation rule change.

17. The method of claim 1 or 2,

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.

18. The method of claim 1 or 2, 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。

19. a method of packet processing, the method comprising:

receiving packet data convergence protocol sequence numbers (PDCP SN) and/or PDCP SN allocation rules of at least two sending electronic devices by a receiving electronic device;

the receiving electronic equipment processes the PDCP data packet according to the PDCP SN and/or the PDCP SN distribution rule;

wherein the PDCP SN and/or PDCP SN assignment rule of the transmitting electronic device comprises: a first PDCP SN and a second PDCP SN;

the first PDCP SN is used 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.

20. The method of claim 19, wherein the receiving electronic device processes 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 PDCP entities on the PDCP data packet according to the second PDCP SN.

21. The method of claim 20, 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 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;

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 sent through a dedicated signaling;

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

22. The method as claimed in claim 20 or 21, 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.

23. The method as claimed in claim 20 or 21, 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.

24. The method of any of claims 19 to 21, wherein the method further comprises:

the receiving electronic device replaces the first PDCP SN with the second PDCP SN.

25. The method of any of claims 19 to 21, wherein the method further comprises:

the receiving electronic device receives PDCP data packets and/or PDCP control PDUs.

26. The method according to any of claims 19 to 21, 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.

27. The method as claimed in claim 26, wherein in case that the t-reordering timer expires, the receiving electronic device determines that the PDCP data packets are delivered in-order to a higher layer;

and/or, in the case of RCVD-COUNT = RX-DELIV, the receiving electronics determines in-order delivery of the PDCP packets to higher layers.

28. The method according to any of claims 19 to 21, 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 said at least two sending electronic devices are sent by a designated sending electronic device to said receiving electronic device;

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

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

29. The method according to any of claims 19 to 21, 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 said at least two transmitting electronic devices are jointly determined by said at least two transmitting electronic devices.

30. The method according to any of claims 19 to 21, 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.

31. The method according to any of claims 19 to 21, 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.

32. The method according to claim 31, 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.

33. The method of any one of claims 19 to 21,

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.

34. The method according to any of claims 19 to 21, 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。

35. 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.

36. The transmitting electronic device of claim 35, wherein the transmitting electronic device further comprises:

a first sending unit configured to send PDCP SNs and/or PDCP SN allocation rules to said second sending electronic device.

37. The transmitting electronic device of claim 35 or 36, 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.

38. The transmitting electronic device of claim 35 or 36, 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.

39. The transmitting electronic device of claim 35 or 36, 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.

40. The transmitting electronic device of claim 35 or 36, wherein the PDCP SNs and/or PDCP SN assignment 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.

41. The transmitting electronic device of claim 40, 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.

42. The transmitting electronic device of claim 35 or 36, 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 to be a value obtained by utilizing TX-NEXT to perform modulus on a function of the PDCP SN size;

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

43. The transmitting electronic device of claim 35 or 36, 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 sending electronic equipment performs packet packing and transmission of PDCP data packets, sets PDCP SNs and/or state variables of the PDCP data packets, and the receiving electronic equipment performs 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.

44. The transmitting electronic device of claim 43,

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 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;

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.

45. The transmitting electronic device as claimed in claim 43, wherein the PDCP 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.

46. The transmitting electronic device as claimed in claim 43, 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.

47. The transmitting electronic device of claim 43, wherein the first processing unit is further configured to determine, from the indication of the 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.

48. The transmitting electronic device of claim 43, 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.

49. The transmitting electronic device of claim 35 or 36, wherein the PDCP SNs and/or PDCP SN allocation rules are transmitted periodically or based on an event.

50. The transmitting electronic device of claim 49, wherein the event comprises at least one of:

PDCP SN pattern change and PDCP SN allocation rule change.

51. The transmitting electronic device of claim 35 or 36, 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 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 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.

52. The transmitting electronic device of claim 35 or 36, wherein the pre-agreed PDCP SNs, or PDCP SNs transmitted by the 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。

53. 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;

a second processing unit, configured to process PDCP data packet according to the PDCP SN and/or PDCP SN allocation rule;

wherein the PDCP SN and/or PDCP SN assignment rule of the transmitting electronic device comprises: a first PDCP SN and a second PDCP SN;

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

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

54. The receiving electronic device of claim 53, wherein the second processing unit is configured to perform intra-PDCP entity processing on the PDCP data packets 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.

55. The receiving electronic device as in claim 54, 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 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;

or 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;

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 sent 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 sent through a dedicated signaling;

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

56. The receiving electronic device of claim 54 or 55, 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.

57. The receiving electronic device as in claim 54 or 55, 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.

58. The receiving electronic device of any of claims 53 to 55, wherein the second processing unit is further configured to replace the first PDCP SN with the second PDCP SN.

59. The receiving electronic device according to any of claims 53 to 55, wherein the receiving unit is further configured to receive PDCP data packets and/or PDCP control PDUs.

60. The receiving electronic device of any of claims 53-55, 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.

61. The receiving electronic device of claim 60, 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 higher layers;

and/or, in case RCVD-COUNT = RX-DELIV, the second processing unit is configured to determine in-order delivery of the PDCP packet to a higher layer.

62. The receiving electronic device according to any of claims 53 to 55, 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 said at least two sending electronic devices are sent by a designated sending electronic device to said 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.

63. The receiving electronic device according to any of claims 53 to 55, wherein the PDCP SNs and/or PDCP SN assignment rules of the at least two transmitting electronic devices are determined by any one of the transmitting electronic devices;

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.

64. The receiving electronic device according to any of claims 53 to 55, wherein the PDCP SN and/or PDCP SN allocation rule is determined according to at least one of:

traffic characteristics, qoS requirements, scheduling conditions, SPS configuration information, configuration authorization CG configuration information, activated carrier information, activated SPS information, activated CG information, traffic size, traffic type, cell load, cell interference and cell channel quality.

65. The receiving electronic device of any of claims 53 to 55, 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.

66. The receiving electronic device as claimed in claim 65, 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, carrying 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 in the PDCP control PDU;

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 jointly maintained 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.

67. The receiving electronic device of any of claims 53 to 55, wherein 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.

68. The receiving electronic device of any of claims 53 to 55, 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。

69. 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.

70. 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 34 when running the computer program.

71. 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.

72. 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 34.

Images