Processing method, communication device, communication system, storage medium, and program product

Abstract

The present disclosure relates to a processing method, a communication device, a communication system, a storage medium, and a program product. The method comprises: in a transmitting packet data convergence protocol (PDCP) entity of a first device, determining a PDCP PDU on the basis of at least one PDCP service data unit (SDU) of one or more PDCP SDUs; and transmitting the PDCP PDU to a second device. In the method of the present disclosure, a PDCP entity can perform concatenation processing on one or more PDCP SDUs among received PDCP SDUs, thereby helping to improve the processing speed of a PDCP layer and reduce signaling overheads.

Description

Processing methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a processing method, communication device, communication system, storage medium, and program product. Background Technology

[0002] In communication between terminals and network devices, the radio bearer (RB) used for data transmission is configured with corresponding transmission control entities, such as the Packet Data Convergence Protocol (PDCP) entity and the Radio Link Control (RLC) entity. The PDCP entity includes a transmitting PDCP entity and a receiving PDCP entity. Summary of the Invention

[0003] When the PDCP layer receives a large number of small data packets, the PDCP entity needs to perform a processing procedure for each small data packet received, which affects the processing speed of the PDCP layer.

[0004] This disclosure provides a processing method, a communication device, a communication system, a storage medium, and a program product.

[0005] In a first aspect, embodiments of this disclosure provide a processing method executed by a first device, the method comprising:

[0006] In the PDCP entity of the first device, a PDCP protocol data unit (PDU) is determined based on at least one PDCP SDU among one or more PDCP protocol data units (SDUs);

[0007] The PDCP PDU is sent to the second device.

[0008] Secondly, embodiments of this disclosure provide a processing method executed by a second device, the method comprising:

[0009] Receive a PDCP PDU sent by a first device, wherein the PDCP PDU is determined by the sending PDCP entity of the first device based on at least one PDCP SDU among one or more PDCP SDUs.

[0010] Thirdly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method described in the first aspect or the second aspect.

[0011] Fourthly, embodiments of this disclosure provide a communication system, including a first device and a second device, wherein,

[0012] The first device is configured to implement the method as described in the first aspect;

[0013] The second device is configured to implement the method as described in the second aspect.

[0014] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0015] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0016] In a sixth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0017] In this embodiment of the disclosure, the PDCP entity can cascade one or more PDCP SDUs in the received PDCP SDU, which helps to improve the processing speed of the PDCP layer and save signaling loss. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0019] Figure 1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0020] Figure 1B is a schematic diagram of a protocol stack provided according to an embodiment of the present disclosure;

[0021] Figure 1C is a schematic diagram of the PDCP entity processing flow according to an embodiment of the present disclosure;

[0022] Figure 1D is a schematic diagram of traffic splitting according to an embodiment of the present disclosure;

[0023] Figure 2A is an exemplary interactive schematic diagram of a method provided according to an embodiment of the present disclosure;

[0024] Figures 2B to 2C are cascade diagrams provided according to embodiments of the present disclosure;

[0025] Figures 3A to 3D are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;

[0026] Figure 4A is a schematic diagram of the structure of a first device according to an embodiment of the present disclosure;

[0027] Figure 4B is a schematic diagram of the structure of a second device according to an embodiment of the present disclosure;

[0028] Figure 5A is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0029] Figure 5B is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0030] This disclosure provides a processing method, a communication device, a communication system, a storage medium, and a program product.

[0031] In a first aspect, embodiments of this disclosure provide a processing method executed by a first device, the method comprising:

[0032] In the PDCP entity of the first device, the PDCP PDU is determined based on at least one PDCP SDU from one or more PDCP SDUs;

[0033] Send PDCP PDU to the second device.

[0034] In the above embodiments, the PDCP entity can cascade one or more PDCP SDUs in the received PDCP SDU, which helps to improve the processing speed of the PDCP layer and save signaling loss.

[0035] In conjunction with the embodiments of the first aspect, in some embodiments, at least one PDCP SDU satisfies a first condition, the first condition including at least one of the following:

[0036] At least one PDCP SDU mapping has the same radio link control RLC bearer;

[0037] At least one PDCP SDU mapping has the same Logical Channel (LCH).

[0038] In conjunction with the embodiments of the first aspect, in some embodiments, the RLC bearer and / or LCH of at least one PDCP SDU mapping is determined based on the PDU Set Importance (PSI) of the data packet.

[0039] In conjunction with the embodiments of the first aspect, in some embodiments, determining the PDCP PDU based on at least one PDCP SDU from the one or more PDCP SDUs includes:

[0040] Based on the receiving order of one or more PDCP SDUs, determine whether each PDCP SDU satisfies the first condition;

[0041] At least one PDCP SDU that satisfies the first condition is cascaded sequentially. If there is a PDCP SDU that does not satisfy the first condition, the cascading is stopped, and a PDCP PDU containing at least one PDCP SDU is determined.

[0042] In conjunction with the embodiments of the first aspect, in some embodiments, at least one PDCP SDU or PDCP PDU satisfies the second condition, which includes at least one of the following:

[0043] The size of the PDCP PDU is less than a first threshold, which is used to indicate the maximum length of the PDCP PDU.

[0044] The number of PDCP SDUs contained in a PDCP PDU is less than a second threshold, which is used to indicate the maximum number of PDCP SDUs contained in a PDCP PDU.

[0045] In conjunction with the embodiments of the first aspect, in some embodiments, the first threshold is configured by the network device or defined by the protocol; and / or, the second threshold is configured by the network device or defined by the protocol.

[0046] In conjunction with the embodiments of the first aspect, in some embodiments, determining the PDCP PDU based on at least one PDCP SDU from the one or more PDCP SDUs includes:

[0047] Based on the receiving order of one or more PDCP SDUs, determine whether each PDCP SDU satisfies the first and second conditions one by one;

[0048] At least one PDCP SDU that satisfies the first condition and the second condition is cascaded in sequence to determine the PDCP PDU.

[0049] In conjunction with the embodiments of the first aspect, in some embodiments, at least one PDCP SDU satisfies a third condition, which includes at least one of the following:

[0050] The reception time of at least one PDCP SDU is during the timer operation;

[0051] At least one PDCP SDU has an interval duration between the first and last PDCP SDU that is less than a third threshold.

[0052] The timer or third threshold is used to indicate the maximum cascading delay.

[0053] In conjunction with the embodiments of the first aspect, in some embodiments, the timer is configured by the network device or defined by the protocol; and / or, the third threshold is configured by the network device or defined by the protocol.

[0054] In conjunction with the embodiments of the first aspect, in some embodiments, determining the PDCP PDU based on at least one PDCP SDU from the one or more PDCP SDUs includes:

[0055] Based on the receiving order of one or more PDCP SDUs, the time when the first PDCP SDU is received is used as the starting point for the timing of the timer or the interval duration, and each PDCP SDU is determined to satisfy the first condition, the second condition, and the third condition.

[0056] At least one PDCP SDU that satisfies the first, second, and third conditions is cascaded in sequence to determine the PDCP PDU.

[0057] In conjunction with embodiments of the first aspect, in some embodiments, cascading at least one PDCP SDU to determine a PDCP PDU includes:

[0058] Based on the receiving order of one or more PDCP SDUs, the time when the first PDCP SDU is received is used as the starting point for the timing of the timer or the interval duration, and each PDCP SDU is determined to satisfy the first and third conditions one by one.

[0059] At least one PDCP SDU that satisfies the first and third conditions is cascaded in sequence.

[0060] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0061] If, after the timing start point, at least one of the first, second, and third conditions is not met, the timer is restarted or the interval duration is re-timing.

[0062] In conjunction with the embodiments of the first aspect, in some embodiments, at least two data packets belong to the same or different application layer PDU sets.

[0063] In conjunction with the embodiments of the first aspect, in some embodiments, the first device is a terminal or a network device.

[0064] Secondly, embodiments of this disclosure provide a processing method executed by a second device, the method comprising:

[0065] Receive a PDCP PDU sent by a first device, wherein the PDCP PDU is determined by the sending PDCP entity of the first device based on at least one PDCP SDU among one or more PDCP SDUs.

[0066] In the above embodiments, the PDCP PDU received by the PDCP receiving entity may include one or more PDCP SDUs, thereby effectively improving the rate at which the PDCP receiving entity processes received data.

[0067] In conjunction with embodiments of the second aspect, in some embodiments, at least one PDCP SDU satisfies a first condition, the first condition including at least one of the following:

[0068] At least one PDCP SDU mapping has the same radio link control RLC bearer;

[0069] At least one PDCP SDU mapping has the same logical channel LCH.

[0070] In conjunction with embodiments of the second aspect, in some embodiments, the RLC bearer and / or LCH of at least one PDCP SDU mapping is determined based on the packet-based PDU set importance PSI.

[0071] In conjunction with embodiments of the second aspect, in some embodiments, at least one PDCP SDU or PDCP PDU satisfies the second condition, which includes at least one of the following:

[0072] The size of the PDCP PDU is less than a first threshold, which is used to indicate the maximum length of the PDCP PDU.

[0073] The number of PDCP SDUs contained in a PDCP PDU is less than a second threshold, which is used to indicate the maximum number of PDCP SDUs contained in a PDCP PDU.

[0074] In conjunction with embodiments of the second aspect, in some embodiments, the first threshold is configured by the network device or defined by the protocol; and / or, the second threshold is configured by the network device or defined by the protocol.

[0075] In conjunction with the embodiments of the second aspect, in some embodiments, at least one PDCP SDU satisfies a third condition, which includes at least one of the following:

[0076] The reception time of at least one PDCP SDU is during the timer operation;

[0077] At least one PDCP SDU has an interval duration between the first and last PDCP SDU that is less than a third threshold.

[0078] The timer or third threshold is used to indicate the maximum cascading delay.

[0079] In conjunction with the embodiments of the second aspect, in some embodiments, the timer is configured by the network device or defined by the protocol; and / or, the third threshold is configured by the network device or defined by the protocol.

[0080] In conjunction with the embodiments of the second aspect, in some embodiments, at least two data packets belong to the same or different application layer PDU sets.

[0081] In conjunction with the embodiments of the second aspect, in some embodiments, the second device is a terminal or a network device.

[0082] Thirdly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method described in the first aspect or the second aspect.

[0083] Fourthly, embodiments of this disclosure provide a communication system, including a first device and a second device, wherein,

[0084] The first device is configured to implement the method as described in the first aspect;

[0085] The second device is configured to implement the method as described in the second aspect.

[0086] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0087] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0088] In a sixth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0089] In a seventh aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0090] Eighthly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0091] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0092] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0093] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0094] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0095] In the embodiments disclosed herein, "multiple" refers to two or more.

[0096] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0097] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0098] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0099] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0100] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0101] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0102] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0103] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0104] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0105] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0106] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0107] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0108] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0109] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0110] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0111] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0112] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0113] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0114] As shown in Figure 1A, the communication system 100 includes a first device 101 and a second device 102.

[0115] In this context, the first device 101 can be a transmitting end or transmitting device in communication, and the second device 102 can be a receiving end or receiving device in communication. For example, in uplink communication, the first device 101 is a terminal, and the second device 102 is a network device. As another example, in downlink communication, the first device 101 is a network device, and the second device 102 is a terminal.

[0116] In some embodiments, the terminal includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0117] In some embodiments, the network device may include at least one of an access network device and a core network device.

[0118] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0119] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0120] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0121] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0122] In some embodiments, core network equipment includes network elements with specific functions, such as Access Management Function (AMF) and Service Management Function (SMF).

[0123] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0124] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0125] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0126] In some implementations, the protocol stack structure shown in FIG1B is applicable to either the first device 101 or the second device 102. During data transmission, data from the higher layers of the first device 101 is transmitted to the lower layers of the second device 102 via the lower layers, and the higher layers of the second device 102 then receive the data transmitted from the lower layers.

[0127] In some embodiments, in each layer of the protocol stack, data packets from or sent to higher layers are called SDUs, and data packets from or sent to lower layers are called PDUs. For example, data packets received by the PDCP layer from or sent to higher layers are called PDCP SDUs, and data packets received by the PDCP layer from or sent to lower layers (e.g., RLC layers) are called PDCP PDUs.

[0128] In some implementations, the PDCP entity supports functions including header compression, integrity protection, and encryption / deciphering. For these functions to work effectively together within the PDCP entity, the PDCP entity needs to process the received and transmitted data according to a specific processing flow.

[0129] In some implementations, as shown in Figure 1C, the processing flow for sending a PDCP entity is as follows:

[0130] Step 1, Transmission buffer sequence numbering: Number the data packets received from higher layers from the transmission buffer, such as assigning PDCP SN numbers.

[0131] Step 2, Header Compression: If header compression is configured, the header of the PDCP SDU data packet is compressed. Header compression can be either Robust Header Compression (ROHC) or Ethernet Header Compression (EHC).

[0132] Step 3, Integrity Protection: If integrity protection is configured, a data integrity verification unit, such as a Message Authentication Code for Integrity (MAC-I), is generated for the PDCP PDU header and PDCP SDU based on the integrity protection key and algorithm. Integrity protection processing is not applied to the PDCP Control PDU.

[0133] Step 4, Encryption: Encrypt the data portion of the PDCP PDU (PDCP SDU, and additionally the Data Integrity Verification Unit MAC-I if integrity protection is configured). The encryption process does not process the Service Data Adaptation Protocol (SDAP), SDAP Control PDU, or PDCP Control PDU.

[0134] Step 5, Add PDCP header: Add PDCP header to generate PDCP PDU.

[0135] Step 6, Routing / Duplication: Send the PDCP PDU to the RLC entity corresponding to the PDCP entity. If the PDCP packet duplication function is configured, the PDCP PDU is copied and then sent to the RLC entity corresponding to the PDCP entity.

[0136] Referring again to Figure 1C, the processing flow for receiving PDCP entities is as follows:

[0137] Step 1, Remove PDCP Header: After receiving the PDCP PDU from the underlying protocol entity, remove the PDCP PDU header.

[0138] Step 2, Decryption: Decrypt the data portion of the PDCP PDU. The data portion includes the PDCP SDU and MACI-I. If integrity protection is configured, the data portion also includes the data integrity verification unit MAC-I.

[0139] Step 3, Integrity Verification: Based on the integrity protection key and algorithm, generate a Data Integrity Verification Unit (MAC-I) for the PDCP PDU header and PDCP SDU. Compare this generated MAC-I with the MAC-I carried in the received PDCP PDU; if they match, the verification is successful.

[0140] Step 4, Reordering or Duplicate Discarding: The received data packets are stored in the receive buffer, reordered according to the PDCP number, and delivered to the higher-level protocol entity in PDCP number order, while duplicate data packets are discarded.

[0141] Step 5, Header Decompression: If header compression (such as ROHC or EHC) is configured, the header of the PDCP SDU data packet is decompressed and then delivered to the higher-level protocol entity.

[0142] In some implementations, a PDCP entity can be associated with one or more RLC entities. The PDCP layer can provide offloading functionality, including in the following scenarios:

[0143] 1) If a PDCP is associated with an RLC entity, then the data packet is delivered to that RLC entity;

[0144] 2) If PDCP is associated with multiple RLC entities:

[0145] Replication scenarios: For data PDUs, replication and sending are performed between two RLC entities; For control data, sending is performed to the primary RLC entity;

[0146] For split bearers, if the data volume exceeds a certain threshold, it can be sent separately to the primary RLC entity and the secondary RLC entity.

[0147] In some implementations of Extended Reality (XR) services, multi-stream transmission and multi-stream modeling are introduced. This involves differentiating data based on its importance, such as modeling I-frames and P-frames. I-frames are more important than P-frames; the terminal needs to decode I-frames, while P-frames cannot be decoded independently. Therefore, different transmission QoS requirements need to be adopted to account for the different importance of data packets in the data stream.

[0148] Optionally, a frame transmission may include the transmission of one or more PDU sets. A PDU set consists of one or more PDUs that carry the payload of an information unit generated at the application layer (e.g., a frame or video clip from an XRM service). In some implementations, the application layer requires all PDUs in a PDU set to use the corresponding information unit. In other implementations, the application layer can still recover some or all of the information units when some PDUs are lost.

[0149] Optionally, PSI can be used as an indicator of the importance of a PDU set. PSI identifies the relative importance of a PDU set compared to other PDU sets in a Quality of Service (QoS) flow. In the event of congestion, the RAN can use it to drop packets at the PDU set level.

[0150] Optionally, since PDU sets with different PSIs have different importance, one approach is for the Non-Access Stratum (NAS) to divide packets into different QoS flows based on packet importance, which are then mapped by the RAN to different data radio bearers (DRBs). Another approach is that the NAS does not perform packet importance-based flow division, but instead includes data of different importance within the same QoS flow. In this case, the RAN side relies on importance-based flow division. For example, different RLC bearers and / or LCHs can be mapped based on PSI, as shown in Figure 1D. If a QoS flow contains both P-frames and I-frames, since the P-frames and I-frames are associated with different PSIs, the I-frames and P-frames are divided on the RAN side according to the PSIs, and the I-frames and P-frames are mapped to different RLC bearers respectively.

[0151] Referring to Figure 1C and the description of the related steps above, when the PDCP layer receives a large number of small data packets (such as PDCP SDUs), the PDCP entity needs to execute the processing flow corresponding to Figure 1C for each small data packet and add the corresponding data packet header. Therefore, each resulting PDCP PDU can only contain one PDCP SDU. This reduces the processing speed of the PDCP layer and leads to additional signaling losses, such as signaling losses in the PDCP header and / or MAC-I.

[0152] Figure 2A is an interactive schematic diagram illustrating a processing method according to an embodiment of the present disclosure. As shown in Figure 2A, this embodiment of the present disclosure relates to a communication method, which includes:

[0153] In step S2101, the transmitting PDCP entity of the first device 101 receives one or more PDCP SDUs.

[0154] In some embodiments, the first device 101 is a communication transmitter, which may be a terminal or a network device.

[0155] Optionally, in uplink communication, the first device 101 is a terminal that sends uplink information; in downlink communication, the first device 101 is a network device that sends downlink information.

[0156] In some embodiments, the PDCP entity in the first device 101 may include a sending PDCP entity and a receiving PDCP entity.

[0157] In some embodiments, in conjunction with the protocol stack shown in FIG1B, the sending PDCP entity can receive one or more PDCP SDUs from a higher layer of the first device 101, such as the SDAP layer.

[0158] In some embodiments, the transmitting PDCP entity of the first device 101 will cascade at least one PDCP SDU, as described in step S2102.

[0159] In step S2102, the sending PDCP entity of the first device 101 cascades at least one PDCP SDU.

[0160] In some embodiments, for one or more received PDCP SDUs, the sending PDCP entity may filter some or all of the PDCP SDUs for cascading processing.

[0161] Optionally, the PDCP entity is sent based on configured or defined conditions, and cascading processing is performed when the conditions are met.

[0162] Optionally, the condition may include at least one of the first condition, the second condition, and the third condition in the following embodiments.

[0163] In some embodiments, concatenation or cascaded processing can refer to combined or combined processing.

[0164] In the first embodiment, step S2102 may include the following steps S2102-11 to S2102-12:

[0165] Step S2102-11: The sending PDCP entity determines whether each PDCP SDU satisfies the first condition according to the receiving order of one or more PDCP SDUs.

[0166] In this embodiment, a constraint in the cascading process is a first condition, such as the cascading PDCP SDU needing to satisfy the first condition.

[0167] In this embodiment, the PDCP sending entity determines whether the PDCP SDUs meet the first condition according to the order of the received PDCP SDUs, for example, according to the order of the PDCP SDUs received from higher-level entities such as the SDAP layer or the IP layer.

[0168] Optionally, the PDCP sending entity can start from the second received PDCP SDU and judge each PDCP SDU one by one, such as judging whether it meets the first condition with the first PDCP SDU.

[0169] Optionally, for a PDCP SDU that satisfies the first condition, steps S2102-12 can be performed.

[0170] In this embodiment, the first condition includes at least one of the following:

[0171] At least one PDCP SDU mapping has the same RLC bearer;

[0172] At least one PDCP SDU mapping has the same LCH.

[0173] Optionally, a PDCP entity can be associated with one or more RLC entities. For example, in conjunction with the description of the foregoing embodiments, in a PSI-based traffic splitting scenario, data from a PDCP can be sent to multiple RLC entities.

[0174] Optionally, the RLC bearer and / or LCH of at least one PDCP SDU mapping is determined based on the PDU set importance PSI of the packet. For example, the RLC bearer and / or LCH of the PDCP SDU mapping are determined based on the PSI of the PDCP SDU.

[0175] Step S2102-12: The PDCP entity sends at least one PDCP SDU that satisfies the first condition in sequence.

[0176] In this embodiment, the sending PDCP entity processes the PDCP SDUs that meet the first condition together according to the receiving order.

[0177] Optionally, at least one PDCP SDU concatenated in this step can be obtained as a concatenated PDCP PDU based on the steps shown in FIG1C or steps S2103 to S2107 below. In this embodiment of the step, for ease of description, the description of the PDCP PDU is directly used to represent the data packet after concatenation of at least one PDCP SDU.

[0178] In this embodiment, the cascaded PDCP SDUs may belong to the same or different application PDU sets. For example, at least one cascaded PDCP SDU may belong to the same application PDU set or different application PDU sets.

[0179] In one example, as shown in Figure 2B, three application layer PDU sets: PDU set1, PDU set2, and PDU set3 are mapped to the same QoS stream, and thus to the same radio bearer (RB). It is assumed that PDU sets associated with different PSIs can be mapped to different RLC bearers and / or LCHs. For example, the PSIs associated with PDU set1 and PDU set2 are both mapped to RLC bearer 1 and / or LCH1, and the PSI associated with PDU set3 is mapped to LCH2.

[0180] In this example, the sending PDCP entity selects PDCP SDUs that meet the first condition for concatenation according to the receiving order. The receiving order could be PDCP SDU#1 belonging to application layer PDU set1, PDCP SDU#2 belonging to application layer PDU set2, and PDCP SDU#3 belonging to application layer PDU set3. PDCP SDU#1 and PDCP SDU#2 can be concatenated if they meet the first condition, while PDCP SDU#3 cannot be concatenated with the aforementioned PDCP SDUs if it does not meet the first condition. Therefore, the concatenated PDCP SDUs can include PDCP SDU#1 and PDCP SDU#2.

[0181] In this embodiment, during the cascading process, cascading is stopped when there is a PDCP SDU that does not meet the first condition. In other words, if there is a PDCP SDU that does not meet the first condition, the addition of that PDCP SDU to the cascaded PDCP SDU is stopped.

[0182] In one example, the sending PDCP entity receives the first PDCP SDU and continues to receive the second PDCP SDU. It then determines whether the second PDCP SDU meets a first condition. If the second PDCP SDU meets the first condition, such as having the same RLC bearer and / or LCH mapped to the first PDCP SDU, then the first and second PDCP SDUs can be concatenated.

[0183] In this example, the sending PDCP entity continues to receive a third PDCP SDU and determines whether the third PDCP SDU meets the first condition. If the third PDCP SDU meets the first condition, such as having the same RLC bearer and / or LCH mapped to the second and first PDCP SDUs, then the first, second, and third PDCP SDUs can be concatenated. The resulting PDCP SDU includes the first, second, and third PDCP SDUs. If the third PDCP SDU does not meet the first condition, concatenation stops, and the resulting PDCP SDU only includes the first and second PDCP SDUs.

[0184] In another example, as shown in Figure 2C, the PDCP sending entity receives four PDCP SDUs, numbered PDCP SDU#1, PDCP SDU#2, PDCP SDU#3, and PDCP SDU#4 in the order of receipt. These four PDCP SDUs arrive at the PDCP layer in the order shown in Figure 2C. These four PDCP SDUs can belong to different application layer PDU sets. When the PDCP layer performs PDCP concatenation, the PDCP sending entity, based on a first condition, assembles the two SDUs (PDCP SDU#1 and PDCP SDU#2) into a PDCP PDU if the first two SDUs satisfy this first condition, such as being mapped to the same RLC bearer and / or LCH.

[0185] In this example, the third SDU does not meet the first condition, such as having a different RLC bearer and / or LCH mapped from the first two SDUs, and therefore cannot be concatenated with the aforementioned two PDCP SDUs. The third and fourth SDUs also do not meet the first condition, such as having different mapped RLC bearers and / or LCHs, and therefore cannot be concatenated together. In this example, the generated PDCP PDU contains only PDCP SDU#1 and PDCP SDU#2. The generated PDCP PDU contains only PDCP SDU#3.

[0186] In the second embodiment, step S2102 may include the following steps S2102-21 to S2102-22:

[0187] Step S2102-21: The sending PDCP entity determines whether each PDCP SDU satisfies the first condition and the second condition according to the receiving order of one or more PDCP SDUs.

[0188] In this embodiment, the description of this step can be found in the implementation of step S2102-11, and will not be repeated here.

[0189] Step S2102-22: The PDCP entity sequentially cascades at least one PDCP SDU that satisfies the first condition and the second condition.

[0190] Optionally, the cascaded PDCP PDU satisfies the second condition.

[0191] Optionally, at least one PDCP SDU concatenated in this step can be obtained as a concatenated PDCP PDU based on the steps shown in FIG1C or steps S2104 to S2108 below. In this embodiment of the step, for ease of description, the description of the PDCP PDU is directly used to represent the data packet after concatenation of at least one PDCP SDU.

[0192] Optionally, at least one PDCP SDU needs to satisfy the second condition during the cascading process, or the PDCP SDU cascaded from the at least one PDCP SDU needs to satisfy the second condition. Optionally, to determine whether a certain PDCP SDU satisfies the second condition, it can be determined by judging whether the size of the PDCP SDU after cascading with other PDCP SDUs satisfies the second condition, or by judging whether the sum of the size of the PDCP SDU and the sizes of the cascadeable PDCP SDUs satisfies the second condition.

[0193] In this embodiment, the second condition includes at least one of the following:

[0194] The size of the PDCP PDU is less than a first threshold, which is used to indicate the maximum length of the PDCP PDU.

[0195] The number of PDCP SDUs contained in a PDCP PDU is less than a second threshold, which is used to indicate the maximum number of PDCP SDUs contained in a PDCP PDU.

[0196] Optionally, the first threshold is configured by the network device or defined by the protocol, and / or the second threshold is configured by the network device or defined by the protocol.

[0197] In one example, the protocol stipulates or network configuration sets the first threshold to 9000 bytes, meaning that the size of at least one cascaded PDCP SDU cannot exceed 9000 bytes, or in other words, the size of the cascaded PDCP SDU cannot exceed 9000 bytes. During the cascading process, if a PDCP SDU meets the first condition, but cascading that PDCP SDU would exceed the first threshold, then that PDCP SDU cannot be cascaded.

[0198] For example, referring to the example shown in Figure 2C, PDCP SDU#1 and PDCP SDU#2 satisfy the first condition and can be cascaded, and the size of the cascaded PDCP PDU is less than the first threshold, that is, PDCP SDU#1 and PDCP SDU#2 satisfy the second condition. Assume PDCP SDU#3 satisfies the first condition, such as having the same RLC bearer and / or LCH mapped to PDCP SDU#1 and PDCP SDU#2. However, cascading PDCP SDU#3 would make the size of the cascaded PDCP PDU greater than the first threshold, that is, PDCP SDU#3 does not satisfy the second condition. Even if PDCP SDU#3 satisfies the first condition, it will not be cascaded to the same PDCP PDU as PDCP SDU#1 and PDCP SDU#2.

[0199] In this example, if PDCP SDU#3 satisfies the first condition and also satisfies the second condition, then PDCP SDU#3 can be cascaded with PDCP SDU#1 and PDCP SDU#2 to the same PDCP PDU. However, if cascading PDCP SDU#3 satisfies the second condition but does not satisfy the first condition (e.g., its RLC bearer and / or LCH mapping is different from PDCP SDU#2), then PDCP SDU#3 cannot be cascaded with PDCP SDU#1 and PDCP SDU#2 to the same PDCP PDU.

[0200] In this embodiment, based on the first condition being met, it can be further determined whether the second condition is met.

[0201] In the third embodiment, step S2102 may include the following steps S2102-31 to S2102-32:

[0202] Step S2102-31: The sending PDCP entity determines whether each PDCP SDU meets the first and third conditions according to the receiving order of one or more PDCP SDUs, using the time of receiving the first PDCP SDU as the starting point for the timer or interval duration.

[0203] In this embodiment, the PDCP sending entity can start a timer or begin timing when it receives the first PDCP SDU, and then determine whether the first and third conditions are met for each PDCP SDU received thereafter.

[0204] Optionally, within the timer's operating range or the interval duration, it can be determined whether the PDCP SDU meets the first condition.

[0205] Optionally, whether the first condition is met can be found in the implementation of step S2102-11, which will not be repeated here.

[0206] In this embodiment, at least one PDCP SDU needs to satisfy a third condition during the cascading process.

[0207] In this embodiment, the third condition includes at least one of the following:

[0208] The reception time of at least one PDCP SDU is during the timer operation;

[0209] At least one PDCP SDU has an interval duration between the first and last PDCP SDU that is less than a third threshold.

[0210] The timer or the third threshold is used to indicate the maximum cascading delay. For example, the runtime of the timer can be equal to the third threshold.

[0211] Optionally, the timer is configured for the network device or defined by the protocol; and / or, the third threshold is configured for the network device or defined by the protocol.

[0212] Optionally, the third condition is used to determine whether the PDCP SDU meets the third condition, such as whether it is within the timer's running period. Here, "during timer running period," "before timer timeout," and "within the timer's running duration" have the same meaning.

[0213] Step S2102-32: The PDCP entity sequentially cascades at least one PDCP SDU that satisfies the first condition and the third condition.

[0214] In this embodiment, at least one PDCP SDU that can be cascaded needs to satisfy both the first condition and the third condition.

[0215] In one example, the sending PDCP entity starts timing from the first PDCP SDU received, for example, by starting a timer. Only PDCP SDUs that arrive before the timer expires can be cascaded together.

[0216] In this example, referring to the example shown in Figure 2C, PDCP starts timing from receiving the first data packet, such as PDCP SDU#1, from SDAP. During the timer's operation, if PDCP SDU#2 is received, meaning PDCP SDU#2 satisfies the third condition, it is determined whether PDCP SDU#2 satisfies the first condition. If PDCP SDU#2 satisfies the first condition, i.e., its RLC bearer and / or LCH mapped to PDCP SDU#1 are the same, then PDCP SDU#1 and PDCP SDU#2 can be cascaded.

[0217] If the timer finishes running at this time and PDCP SDU#3 is received, even if PDCP SDU#3 meets the first condition, such as having the same RLC bearer and / or LCH mapped to PDCP SDU#2, PDCP SDU#3 cannot be cascaded to the same PDCP PDU as PDCP SDU#1 and PDCP SDU#2 because the timer has finished running.

[0218] In this example, for a PDCP SDU that has expired after the timer expires, regardless of whether the first condition is met, it cannot be cascaded with the previous PDCP SDU. That is, only PDCP SDUs that meet the first condition and are received during the timer's operation can be cascaded.

[0219] In this embodiment, if at least one of the first condition and / or the third condition is not met after the timing start point, the timer is restarted or the interval duration is re-timing.

[0220] For example, referring to the example in Figure 2C above, if PDCP SDU#3 is received after the timer expires, i.e., the third condition is not met, the timer can be restarted or the interval duration can be recalculated. This allows a determination of whether the SDUs following PDCP SDU#3 can be cascaded with it.

[0221] For example, suppose PDCP SDU#3 is still running within the timer period that started with PDCP SDU#1, meaning PDCP SDU#3 satisfies the third condition; however, PDCP SDU#3 does not satisfy the first condition, such as if its RLC bearer and / or LCH are different from those mapped to PDCP SDU#2. In this case, the timer can be restarted or the interval duration can be recalculated to determine whether the SDUs following PDCP SDU#3 can be concatenated with it. Furthermore, the data packets after concatenating PDCP SDU#1 and PDCP SDU#2 can be determined.

[0222] In one example, referring to the example in Figure 2C above, assuming that PDCP SDU#3 does not meet the first condition, upon receiving PDCP SDU#3, the timer is restarted, and the data packets after concatenation of PDCP SDU#1 and PDCP SDU#2 are obtained. For the subsequently received PDCP SDU#4, if the first condition is still not met (e.g., the RLC bearer and / or LCH mapped to PDCP SDU#3 are different), upon receiving PDCP SDU#4, the timer will be restarted again to determine whether the SDUs following PDCP SDU#4 can be concatenated with PDCP SDU#4. PDCP SDU#3 itself will correspond to a PDCP PDU.

[0223] In the fourth embodiment, step S2102 may include the following steps S2102-41 to S2102-42:

[0224] Step S2102-41: The sending PDCP entity determines whether each PDCP SDU meets the first condition, the second condition, and the third condition, based on the receiving order of one or more PDCP SDUs, with the time of receiving the first PDCP SDU as the starting point for the timer or interval duration.

[0225] In this embodiment, the description of this step can be found in the implementation of steps S2102-31, and will not be repeated here.

[0226] Step S2102-42: The PDCP entity sequentially cascades at least one PDCP SDU that satisfies the first condition, the second condition, and the third condition.

[0227] In this embodiment, at least one PDCP SDU that satisfies the first and third conditions is cascaded. See the implementation of steps S2102-32 for details, which will not be repeated here.

[0228] In this embodiment, the second condition can be referred to the description of the foregoing embodiment, and will not be repeated here.

[0229] Optionally, at least one PDCP SDU concatenated in this step can be obtained as a concatenated PDCP PDU based on the steps shown in FIG1C or steps S2104 to S2108 below. In this embodiment of the step, for ease of description, the description of the PDCP PDU is directly used to represent the data packet after concatenation of at least one PDCP SDU.

[0230] Optionally, if there is a next PDCP SDU after at least one PDCP SDU that does not satisfy at least one of the first, second, and third conditions, then the next PDCP SDU cannot be cascaded with the aforementioned at least one PDCP SDU.

[0231] In this embodiment, if at least one of the first, second, and third conditions is not met, the timer is restarted or the interval duration is re-timed.

[0232] Step S2103: The first device 101 sends a PDCP entity numbering for at least one PDCP SDU concatenated data packet.

[0233] In some embodiments, the sending PDCP entity may assign a PDCP SN number to at least one cascaded PDCP SDU.

[0234] In step S2104, the first device 101 performs header compression on the PDCP entity it sends.

[0235] In some embodiments, when header compression is configured, the sending PDCP entity can perform header compression on at least one cascaded PDCP SDU.

[0236] In step S2105, the first device 101 sends a PDCP entity for integrity protection.

[0237] In some embodiments, the sending PDCP entity can generate a MAC-I for at least one cascaded PDCP SDU.

[0238] Step S2106: The PDCP entity sent by the first device 101 is encrypted.

[0239] In step S2107, the first device 101 adds a PDCP packet header to the PDCP sending entity and generates a PDCP PDU containing at least one PDCP SDU.

[0240] In some embodiments, the sending PDCP entity adds a PDCP header to at least one cascaded PDCP SDU to determine a PDCP PDU containing at least one PDCP SDU, i.e., the cascaded PDCP PDU.

[0241] In step S2108, the first device 101 sends a PDCP PDU to the second device 102.

[0242] In some embodiments, the PDCP transmitting entity of the first device 101 can send the PDCP PDU to the RLC entity corresponding to the PDCP entity. If the PDCP packet retransmission function is configured, the PDCP PDU is copied and then sent to the RLC entity corresponding to the PDCP entity.

[0243] In some embodiments, based on the protocol stack structure, the PDCP PDU can be sent by the first device 101 to the receiving PDCP entity of the second device 102.

[0244] Optionally, the receiving PDCP entity can perform the processing procedure shown in Figure 1C on the PDCP PDU to obtain at least one PDCP SDU.

[0245] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0246] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0247] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0248] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0249] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0250] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0251] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0252] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0253] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0254] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0255] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0256] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0257] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2108, wherein each step may be implemented as an independent embodiment, or two or more steps may be combined as an independent embodiment. For example, step S2102 may be implemented as an independent embodiment, steps S2101 to S2102 may be implemented as independent embodiments, and steps S2101 to S2102 and S2108 may be implemented as independent embodiments, but are not limited thereto.

[0258] In some embodiments, at least one of steps S2103 to S2108 is optional, and one of them may be selected for execution in different embodiments, or one or more of these steps may be omitted or substituted in different embodiments.

[0259] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0260] In this embodiment, PDCP SDUs can be jointly processed, thereby reducing the processing latency and power consumption of the PDCP layer and saving additional signaling losses of PDCP (such as signaling losses of PDCP header and MAC-I). Simultaneously, PDCP cascading supports scenarios where data of different importance are contained in the same QoS stream and are distributed according to importance on the RAN side.

[0261] Figure 3A is an interactive schematic diagram illustrating a processing method according to an embodiment of the present disclosure. As shown in Figure 3A, this embodiment of the present disclosure relates to a communication method, which includes:

[0262] In step S3101, the transmitting PDCP entity of the first device 101 receives one or more PDCP SDUs and determines the PDCP PDU based on at least one PDCP PDU among the one or more PDCP SDUs.

[0263] In some embodiments, the implementation of step S3101 can be referred to the implementation of steps S2101 to S2102 in FIG2A, and will not be repeated here.

[0264] In step S3102, the first device 101 sends a PDCP PDU to the receiving PDCP entity of the second device 102.

[0265] In some embodiments, the implementation of step S3102 can be referred to the implementation of step S2108 in FIG2A, and will not be repeated here.

[0266] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0267] Figure 3B is an interactive schematic diagram illustrating a processing method according to an embodiment of the present disclosure. As shown in Figure 3B, this embodiment of the present disclosure relates to a communication method, which includes:

[0268] In step S3201, the transmitting PDCP entity of the first device 101 receives one or more PDCP SDUs and determines whether each PDCP SDU meets the first condition according to the receiving order of the one or more PDCP SDUs.

[0269] In some embodiments, the implementation of step S3201 can be found in the implementation of steps S2102-11 in FIG2A, and will not be repeated here.

[0270] Step S3202: Concatenate at least one PDCP SDU that satisfies the first condition in sequence. Stop cascading if there is a PDCP SDU that does not satisfy the first condition. Determine the PDCP PDU that contains at least one PDCP SDU.

[0271] In some embodiments, the implementation of step S3202 can be referred to the implementation of steps S2102-12 in FIG2A, and will not be repeated here.

[0272] In step S3203, the first device 101 sends a PDCP PDU to the receiving PDCP entity of the second device 102.

[0273] In some embodiments, the implementation of step S3203 can be referred to the implementation of step S2108 in FIG2A, and will not be repeated here.

[0274] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0275] Figure 3C is an interactive schematic diagram illustrating a processing method according to an embodiment of the present disclosure. As shown in Figure 3C, this embodiment of the present disclosure relates to a communication method, which includes:

[0276] In step S3301, the transmitting PDCP entity of the first device 101 receives one or more PDCP SDUs and determines whether each PDCP SDU satisfies the first condition and the second condition according to the receiving order of the one or more PDCP SDUs.

[0277] In some embodiments, the implementation of step S3301 can be found in the implementation of steps S2102-21 in FIG2A, and will not be repeated here.

[0278] Step S3302: cascade at least one PDCP SDU that satisfies the first condition and the second condition in sequence.

[0279] In some embodiments, the implementation of step S3302 can be referred to the implementation of steps S2102-22 in FIG2A, and will not be repeated here.

[0280] In step S3303, the first device 101 sends a PDCP PDU to the receiving PDCP entity of the second device 102.

[0281] In some embodiments, the implementation of step S3303 can be referred to the implementation of step S2108 in FIG2A, and will not be repeated here.

[0282] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0283] Figure 3D is an interactive schematic diagram illustrating a processing method according to an embodiment of the present disclosure. As shown in Figure 3D, this disclosure relates to a communication method, which includes:

[0284] In step S3401, the transmitting PDCP entity of the first device 101 receives one or more PDCP SDUs. Based on the receiving order of the one or more PDCP SDUs, the time of receiving the first PDCP SDU is used as the starting point for the timing of the timer or the interval duration. The device then determines whether each PDCP SDU meets the first condition, the second condition, and the third condition.

[0285] In some embodiments, the implementation of step S3401 can be found in the implementation of steps S2102-41 in Figure 2A, and will not be repeated here.

[0286] Step S3402: cascade at least one PDCP SDU that satisfies the first condition, the second condition, and the third condition in sequence.

[0287] In some embodiments, the implementation of step S3402 can be found in the implementation of steps S2102-42 in Figure 2A, and will not be repeated here.

[0288] In step S3403, the first device 101 sends a PDCP PDU to the receiving PDCP entity of the second device 102.

[0289] In some embodiments, the implementation of step S3403 can be referred to the implementation of step S2108 in FIG2A, and will not be repeated here.

[0290] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0291] This disclosure provides a PDCP layer cascading processing method, which can jointly process one or more PDCP received data packets (e.g., PDCP SDUs). To facilitate understanding of this disclosure, some embodiments are listed below:

[0292] Example 1: One limitation on cascading one or more PDCP SDUs into one PDCP PDU is that the one or more PDCP SDUs are mapped to the same RLC bearer and / or logical channel.

[0293] Example 1-1: When a PDCP sending entity includes multiple PDCP SDUs in one PDCP PDU, the PDCP sending entity adds the multiple PDCP SDUs to the same PDCP PDU one by one according to the order of the received PDCP SDUs (e.g., according to the order of the PDCP SDUs received from higher-level protocol entities (e.g., SDAP layer or IP layer)).

[0294] Example 1-2: One condition for consecutive PDCP SDUs to be cascaded to the same PDCP PDU is that these PDCP SDUs are mapped to the same RLC bearer and / or the same LCH. These one or more PDCP SDUs can belong to the same application PDU set or different application PDU sets. For example, the three application PDU sets in the figure below are mapped to the same QoS flow, and thus to the same radio bearer. Assume that PDU sets associated with different PSIs can be mapped to different RLC bearers / LCHs; for example, the PSIs associated with PDU sets 1 and 2 are both mapped to RLC bearer 1 / LCH1, and the PSI associated with PDU set 3 is mapped to LCH2, as shown in Figure 2B.

[0295] Examples 1-3: When the PDCP sending entity adds PDCP SDUs to the same PDCP PDU in the receiving order, if the above-mentioned restriction conditions are not met, the terminal stops adding PDCP SDUs. For example, if the PDCP sending entity receives four PDCP SDUs, numbered 1 / 2 / 3 / 4 in the receiving order, and the terminal assembles PDCP SDU#1 / 2 into a PDCP PDU one by one, the above-mentioned restriction conditions are met. However, when adding PDCP SDU#3 to the PDCP PDU, the above-mentioned restriction conditions are not met. In this case, the generated PDCP PDU only includes PDCP SDU#1 / 2.

[0296] Examples 1-4: As shown in Figure 2C, assuming SDUs belonging to different application PDU sets arrive at the PDCP layer in the following order, the PDCP layer can only concatenate the first two SDUs during PDCP concatenation because they are mapped to the same RLC bearer / LCH. Since the third SDU is mapped to a different RLC bearer / LCH than the first two SDUs, it cannot be concatenated. Similarly, the third and fourth SDUs are also mapped to different RLC bearers / LCHs, therefore they cannot be concatenated together either.

[0297] Examples 1-5: PDCP concatenation may have other limitations, such as a maximum PDCP PDU length, which limits the number of PDCP SDUs that can be concatenated. For instance, the protocol or network configuration may stipulate that the maximum size of a PDCP PDU packet containing multiple PDCP SDUs is 9000 bytes. Therefore, when one or more PDCP SDUs are concatenated to generate one PDCP PDU, the size of that PDCP PDU cannot exceed 9000 bytes. For example, if one or more PDCP SDUs to be concatenated meet the PDCP PDU length limit, even if the next PDCP SDU is mapped to the same RLC bearer / LCH, they cannot be concatenated to the same PDCP PDU. Similarly, if one or more PDCP SDUs to be concatenated do not exceed the PDCP PDU length limit, but the next PDCP SDU is mapped to a different RLC bearer / LCH, they cannot be concatenated to the same PDCP PDU.

[0298] Examples 1-6: The maximum value of PDCP concatenation delay. For example, starting the timer from the first PDCP SDU, only PDCP SDUs arriving before the timer expires can be concatenated. For instance, during timer operation, the PDCP receives one or more PDCP SDUs from the SDAP. These PDCP SDUs map to the same RLC bearer / LCH. Regardless of whether the next PDCP SDU belongs to the same RLC bearer / LCH, only PDCP SDUs received during timer operation are concatenated. For instance, during timer operation, the PDCP receives one or more PDCP SDUs from the SDAP. Assuming the next PDCP SDU maps to a different RLC bearer / LCH, the terminal device restarts the timer and concatenates the previously received PDCP SDUs mapped to the same RLC bearer / LCH. For example, upon receiving the third PDCP SDU in the above diagram, the terminal device restarts the timer and concatenates the first two received PDCP SDUs. Upon receiving the fourth PDCP SDU, the terminal device restarts the timer.

[0299] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0300] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0301] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0302] Figure 4A is a schematic diagram of a first device according to an embodiment of this disclosure. The first device 4100 is used to perform any of the above methods. In some embodiments, as shown in Figure 4A, the first device 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the processing module 4102 is used to determine a PDCP PDU in the Transmit Packet Data Convergence Protocol (PDCP) entity of the first device based on at least one PDCP SDU in one or more PDCP Protocol Data Units (SDUs); the transceiver module 4101 is used to send the PDCP PDU to the second device.

[0303] Optionally, the transceiver module 4101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the first device in any of the above methods, which will not be described in detail here. Optionally, the processing module 4102 is used to perform at least one of the other steps performed by the first device in any of the above methods, which will not be described in detail here.

[0304] Figure 4B is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure. The second device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the second device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to receive a PDCP PDU sent by the first device, wherein the PDCP PDU is determined by the transmitting PDCP entity of the first device based on at least one PDCP SDU among one or more received PDCP SDUs.

[0305] Optionally, the transceiver module 4201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be described in detail here. Optionally, the processing module 4202 is used to perform at least one of the other steps performed by the terminal in any of the above methods, which will not be described in detail here.

[0306] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0307] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0308] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0309] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0310] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0311] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0312] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

[0313] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0314] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, the schematic diagram of chip 5200 shown in Figure 5B can be referred to, but is not limited thereto.

[0315] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0316] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0317] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.

[0318] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0319] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 5100, cause the communication device 5100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0320] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by the communication device 5100, cause the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0321] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0322] The PDCP entity can cascade one or more PDCP SDUs in the received PDCP SDU, which helps to improve the processing speed of the PDCP layer and save signaling loss.

Claims

1. A processing method, performed by a first device, the method comprising: In the PDCP entity of the first device, the PDCP protocol data unit PDU is determined based on at least one PDCP SDU in one or more PDCP protocol data units SDU; The PDCP PDU is sent to the second device.

2. The method as described in claim 1, wherein, The at least one PDCP SDU satisfies a first condition, the first condition comprising at least one of the following: The radio link control (RLC) bearer mapped by at least one PDCP SDU is the same; The logical channel LCH of at least one PDCP SDU mapping is the same.

3. The method as described in claim 2, wherein, The RLC bearer and / or LCH of the at least one PDCP SDU mapping are determined based on the PDU set importance PSI of the data packet.

4. The method of claim 2, wherein, The step of determining the PDCP PDU based on at least one PDCP SDU from the one or more PDCP SDUs includes: Based on the receiving order of the one or more PDCP SDUs, determine whether each PDCP SDU satisfies the first condition; The at least one PDCP SDU that satisfies the first condition is cascaded sequentially. If there is a PDCP SDU that does not satisfy the first condition, the cascading is stopped, and the PDCP PDU containing the at least one PDCP SDU is determined.

5. The method according to any one of claims 1 to 4, wherein, The at least one PDCP SDU or the PDCP PDU satisfies the second condition, which includes at least one of the following: The size of the PDCP PDU is less than a first threshold, which is used to indicate the maximum length of the PDCP PDU. The number of PDCP SDUs contained in the PDCP PDU is less than a second threshold, which is used to indicate the maximum number of PDCP SDUs contained in the PDCP PDU.

6. The method of claim 5, wherein, The first threshold is configured by the network device or defined by the protocol; and / or, the second threshold is configured by the network device or defined by the protocol.

7. The method of claim 5, wherein, The step of determining the PDCP PDU based on at least one PDCP SDU from the one or more PDCP SDUs includes: Based on the receiving order of the one or more PDCP SDUs, determine whether each PDCP SDU satisfies the first condition and the second condition; The PDCP PDU is determined by sequentially cascading at least one PDCP SDU that satisfies the first condition and the second condition.

8. The method according to any one of claims 1 to 7, wherein, The at least one PDCP SDU satisfies a third condition, which includes at least one of the following: The reception time of the at least one PDCP SDU is during the timer operation period; The time interval between the first and last PDCP SDU in at least one PDCP SDU is less than the third threshold. The timer or the third threshold is used to indicate the maximum cascading delay.

9. The method of claim 8, wherein, The timer is configured by the network device or defined by the protocol; and / or, the third threshold is configured by the network device or defined by the protocol.

10. The method of claim 8, wherein, The step of determining the PDCP PDU based on at least one PDCP SDU from the one or more PDCP SDUs includes: Based on the receiving order of the one or more PDCP SDUs, the time when the first PDCP SDU is received is taken as the starting point for the timer or the interval duration, and it is determined one by one whether the PDCP SDUs meet the first condition, the second condition and the third condition; The at least one PDCP SDU that satisfies the first condition, the second condition, and the third condition is cascaded in sequence to determine the PDCP PDU.

11. The method of claim 8, wherein, The step of cascading at least one PDCP SDU to determine a PDCP PDU includes: Based on the receiving order of the one or more PDCP SDUs, the time when the first PDCP SDU is received is used as the starting point for the timer or the interval duration, and it is determined one by one whether the PDCP SDUs meet the first condition and the third condition; At least one PDCP SDU that satisfies the first condition and the third condition is cascaded sequentially.

12. The method of claim 10 or 11, wherein, The method further includes: If, after the timing start point, at least one of the first, second, and third conditions is not met, the timer is restarted or the interval duration is re-timing.

13. The method as claimed in any one of claims 1 to 12, wherein, The at least one PDCP SDU belongs to the same or different application layer PDU sets.

14. The method as claimed in any one of claims 1 to 13, wherein, The first device is a terminal or network device.

15. A processing method performed by a second device, the method comprising: Receive a PDCP PDU sent by a first device, wherein the PDCP PDU is determined by the sending PDCP entity of the first device based on at least one PDCP SDU among one or more PDCP SDUs.

16. The method of claim 15, wherein, The at least one PDCP SDU satisfies a first condition, the first condition including at least one of the following: The radio link control (RLC) bearer mapped by at least one PDCP SDU is the same; The logical channel LCH of at least one PDCP SDU mapping is the same.

17. The method of claim 16, wherein, The RLC bearer and / or LCH of the at least one PDCP SDU mapping are determined based on the PDU set importance PSI of the data packet.

18. The method as claimed in any one of claims 15 to 17, wherein, The at least one PDCP SDU or the PDCP PDU satisfies the second condition, which includes at least one of the following: The size of the PDCP PDU is less than a first threshold, which is used to indicate the maximum length of the PDCP PDU. The number of PDCP SDUs contained in the PDCP PDU is less than a second threshold, which is used to indicate the maximum number of PDCP SDUs contained in the PDCP PDU.

19. The method of claim 18, wherein, The first threshold is configured by the network device or defined by the protocol; and / or, the second threshold is configured by the network device or defined by the protocol.

20. The method according to any one of claims 15 to 19, wherein, The at least one PDCP SDU satisfies a third condition, which includes at least one of the following: The reception time of the at least one PDCP SDU is during the timer operation period; The time interval between the first and last PDCP SDU in at least one PDCP SDU is less than the third threshold. The timer or the third threshold is used to indicate the maximum cascading delay.

21. The method of claim 20, wherein, The timer is configured by the network device or defined by the protocol; and / or, the third threshold is configured by the network device or defined by the protocol.

22. The method according to any one of claims 15 to 21, wherein, The at least one PDCP SDU belongs to the same or different application layer PDU sets.

23. The method as claimed in any one of claims 15 to 22, wherein, The second device is a terminal or network device.

24. A communication device, wherein, The communication device is used to perform the method according to any one of claims 1 to 14 or any one of claims 15 to 23.

25. A communication system, comprising a first device and a second device, wherein, The first device is configured to implement the method as described in any one of claims 1 to 14; The second device is configured to implement the method as described in any one of claims 15 to 23.

26. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1 to 14 or any one of claims 15 to 23.

27. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by a communication device, it implements the method as described in any one of claims 1 to 14 or any one of claims 15 to 23.

Images