Information sending method and apparatus, information receiving method and apparatus, communication device and storage medium

Abstract

The present disclosure relates to the technical field of communications, and in particular to an information sending method and apparatus, an information receiving method and apparatus, a communication device, and a storage medium. The information sending method comprises: according to an indication of a network device or a predefined rule, jointly processing a plurality of packet data convergence protocol service data units (PDCP SDUs) into a PDCP protocol data unit (PDCP PDU); and sending the PDCP PDU to a receiving end. In the present disclosure, upon receiving a plurality of PDCP SDUs from a higher layer, a sending end may jointly process the plurality of PDCP SDUs into one PDCP PDU during the generation of the PDCP PDU. Accordingly, the processing of a plurality of PDCP SDUs can be completed during a single generation of PDCP PDU, without separately processing each PDCP SDU during a plurality of generations of the PDCP PDU, thereby facilitating reducing signaling overhead and increasing a processing speed of a PDCP layer.

Description

Information transmission and reception methods and apparatus, communication equipment and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to information transmission methods, information reception methods, information transmission devices, information reception devices, communication equipment, and storage media. Background Technology

[0002] The receiving and sending ends can communicate based on the Packet Data Convergence Protocol (PDCP). The sending end can process the PDCP SDU (Service Data Unit) received from the higher layer into PDCP PDU (Protocol Data Unit) and then send the PDCP PDU to the receiving end. However, some technical problems still need to be solved in this process. Summary of the Invention

[0003] The embodiments of this disclosure provide methods and apparatus for sending and receiving information, communication devices, and storage media to solve technical problems in the related art.

[0004] According to a first aspect of the present disclosure, an information transmission method is proposed, executed by a sending end, the method comprising: jointly processing multiple Data Convergence Protocol Service Data Units (PDCP SDUs) into a Data Convergence Protocol Protocol Data Unit (PDCP PDU); and transmitting the PDCP PDU to a receiving end.

[0005] According to a second aspect of the present disclosure, an information receiving method is proposed, which is executed by a receiving end. The method includes: receiving a Data Convergence Protocol Protocol Data Unit (PDCP PDU) sent by a sending end, wherein the PDCP PDU is obtained by joint processing of multiple Data Convergence Protocol Service Data Units (PDCP SDUs).

[0006] According to a third aspect of the present disclosure, an information transmission apparatus is provided, the apparatus comprising: a processing module configured to jointly process multiple Data Convergence Protocol Service Data Units (PDCP SDUs) into a Data Convergence Protocol Protocol Data Unit (PDCP PDU); and a transmission module configured to transmit the PDCP PDU to a receiving end.

[0007] According to a fourth aspect of the present disclosure, an information receiving apparatus is provided, the apparatus comprising: a receiving module configured to receive a Data Convergence Protocol Protocol Data Unit (PDCP PDU) sent by a sending end, wherein the PDCP PDU is obtained by joint processing of multiple Data Convergence Protocol Service Data Units (PDCP SDUs).

[0008] According to a fifth aspect of the present disclosure, a communication device is provided, comprising: one or more processors; wherein the communication device is configured to perform the information transmission method described in the first aspect, and / or the information reception method described in the second aspect.

[0009] According to a sixth aspect of the present disclosure, a communication system is proposed, including a transmitting end and a receiving end, wherein the transmitting end is configured to implement the information transmitting method described in the first aspect, and the receiving end is configured to implement the information receiving method described in the second aspect.

[0010] According to a seventh aspect of the present disclosure, a storage medium is provided that stores instructions, which, when executed on a communication device, cause the communication device to perform the information sending method described in the first aspect and / or the information receiving method described in the second aspect.

[0011] According to an eighth aspect of the present disclosure, a program product is provided that, when executed by a communication device, causes the communication device to perform the information sending method described in the first aspect and / or the information receiving method described in the second aspect.

[0012] According to embodiments of this disclosure, after receiving multiple PDCP SDUs from a higher layer, the transmitting end can combine the multiple PDCP SDUs into a single PDCP PDU during the PDCP PDU generation process. This allows for the processing of multiple PDCP SDUs—such as adding headers, performing integrity protection, and encryption—in a single PDCP PDU generation process, instead of processing each PDCP SDU separately in multiple PDCP PDU generation processes. This reduces signaling overhead and improves the processing speed of the PDCP layer. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

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

[0015] Figure 1B is a schematic diagram of the interaction of a PDCP entity according to an embodiment of the present disclosure.

[0016] Figure 2 is an interactive schematic diagram of an information sending method according to an embodiment of the present disclosure.

[0017] Figure 3A is a schematic diagram of a first format PDCP PDU according to an embodiment of the present disclosure.

[0018] Figure 3B is a schematic diagram of a second-format PDCP PDU according to an embodiment of the present disclosure.

[0019] Figure 3C is a schematic diagram of a third-format PDCP PDU according to an embodiment of the present disclosure.

[0020] Figure 4 is a schematic block diagram of an information transmission device according to an embodiment of the present disclosure.

[0021] Figure 5 is a schematic block diagram of an information receiving device according to an embodiment of the present disclosure.

[0022] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure.

[0023] Figure 6B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0024] The embodiments of this disclosure provide methods and apparatus for sending and receiving information, communication devices, and storage media.

[0025] In a first aspect, embodiments of this disclosure propose an information transmission method, executed by a sending end, the method comprising: jointly processing multiple Data Convergence Protocol Service Data Units (PDCP SDUs) into a Data Convergence Protocol Protocol Data Unit (PDCP PDU); and transmitting the PDCP PDU to a receiving end.

[0026] In the above embodiments, after receiving multiple PDCP SDUs from the higher layer, the transmitting end can combine the multiple PDCP SDUs into a single PDCP PDU during the PDCP PDU generation process. Therefore, processing of multiple PDCP SDUs can be completed in a single PDCP PDU generation process, such as adding headers, integrity protection, and encryption, instead of processing each PDCP SDU separately in multiple PDCP PDU generation processes. This helps reduce signaling overhead and improves the processing speed of the PDCP layer.

[0027] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: obtaining configuration information for jointly processing multiple PDCP SDUs into a PDCP PDU.

[0028] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration information includes at least one of the following: the format information of the PDCP PDU; the identifier of the bearer corresponding to the PDCP SDU; the identifier of the entity corresponding to the PDCP SDU; the identifier of the data stream corresponding to the PDCP SDU; the identifier of the session corresponding to the PDCP SDU; the identifier of the cell corresponding to the PDCP SDU; the identifier of the channel corresponding to the PDCP SDU; and the identifier of the resource corresponding to the PDCP SDU.

[0029] In conjunction with some embodiments of the first aspect, in some embodiments, the identifier of the resource corresponding to the PDCP SDU includes at least one of the following: an identifier of the uplink authorization corresponding to the PDCP SDU; an identifier of the downlink allocation corresponding to the PDCP SDU.

[0030] In conjunction with some embodiments of the first aspect, in some embodiments, the format information includes one of the following:

[0031] In the first format, the PDCP subheader corresponding to the plurality of PDCP SDUs precedes the plurality of PDCP SDUs, the plurality of PDCP subheaders are arranged in a first order, and the plurality of PDCP SDUs are arranged in the first order.

[0032] The second format, wherein the PDCP PDU of the second format contains a plurality of sub-PDUs, the sub-PDUs including the PDCP SDU and the PDCP sub-header corresponding to the PDCP SDU, and the plurality of sub-PDUs are arranged in the first order;

[0033] The third format, wherein in the PDCP PDU of the third format, the PDCP subheaders corresponding to the plurality of PDCP SDUs are after the plurality of PDCP SDUs, the plurality of PDCP SDUs are arranged in a first order, and the plurality of PDCP subheaders are arranged in the first order.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the PDCP subheader includes a length field and / or an extension field; wherein the length field of the PDCP subheader is used to indicate the length of the PDCP SDU corresponding to the PDCP subheader; in the first format PDCP PDU and / or the third format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes an additional PDCP subheader and / or PDCP SDU after the PDCP subheader; in the second format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the PDCP PDU further includes a PDCP header containing a sequence number and an extension field, the extension field of which is used to indicate whether the PDCP PDU includes a PDCP subheader and / or multiple PDCP SDUs after the PDCP header.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the PDCP PDU further includes one or more integrity verification fields.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, when the PDCP PDU includes a MAC-I field, the MAC-I field is generated according to at least one of the following: the PDCP header, the plurality of PDCP subheaders, and the plurality of PDCP SDUs; or, when the PDCP PDU includes a plurality of MAC-I fields, the first MAC-I field among the plurality of MAC-I fields is generated according to at least one of the following: the PDCP header, the PDCP subheader corresponding to the first MAC-I, and the PDCP SDU corresponding to the first MAC-I.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: encrypting the PDCP PDU; wherein the object of encryption for encrypting the PDCP PDU includes at least one of the following: the PDCP subheader; the PDCP SDU; the MAC-I field; and / or, the encryption method for encrypting the PDCP PDU includes at least one of the following: encrypting each PDCP SDU separately; or jointly encrypting multiple PDCP SDUs.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the sending end includes a terminal, and the method preferably includes: receiving processing indication information sent by a network device, wherein the processing indication information is used to indicate whether the sending end should jointly process multiple PDCP SDUs into a PDCP PDU.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: obtaining constraints on configuration information for jointly processing multiple PDCP SDUs into a PDCP PDU; wherein, if the constraints are satisfied, the multiple PDCP SDUs are jointly processed into a PDCP PDU.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the limiting conditions include at least one of the following: a length threshold for the PDCP PDU; a number threshold for the plurality of PDCP SDUs in the PDCP PDU; the length and threshold of the plurality of PDCP SDUs in the PDCP PDU; and a length threshold for a single PDCP SDU in the PDCP PDU.

[0042] Secondly, embodiments of this disclosure propose an information receiving method executed by a receiving end. The method includes: receiving a Data Convergence Protocol Protocol Data Unit (PDCP PDU) sent by a sending end, wherein the PDCP PDU is obtained by joint processing of multiple Data Convergence Protocol Service Data Units (PDCP SDUs).

[0043] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: obtaining configuration information for jointly processing multiple PDCP SDUs into a PDCP PDU.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information includes at least one of the following: the format information of the PDCP PDU; the identifier of the bearer corresponding to the PDCP SDU; the identifier of the entity corresponding to the PDCP SDU; the identifier of the data stream corresponding to the PDCP SDU; the identifier of the session corresponding to the PDCP SDU; the identifier of the cell corresponding to the PDCP SDU; the identifier of the channel corresponding to the PDCP SDU; and the identifier of the resource corresponding to the PDCP SDU.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the identifier of the resource corresponding to the PDCP SDU includes at least one of the following: an identifier of the uplink authorization corresponding to the PDCP SDU; and an identifier of the downlink allocation corresponding to the PDCP SDU.

[0046] In conjunction with some embodiments of the second aspect, in some embodiments, the format information includes one of the following:

[0047] In the first format, the PDCP subheader corresponding to the plurality of PDCP SDUs precedes the plurality of PDCP SDUs, the plurality of PDCP subheaders are arranged in a first order, and the plurality of PDCP SDUs are arranged in the first order.

[0048] The second format, wherein the PDCP PDU of the second format contains a plurality of sub-PDUs, the sub-PDUs including the PDCP SDU and the PDCP sub-header corresponding to the PDCP SDU, and the plurality of sub-PDUs are arranged in the first order;

[0049] The third format, wherein in the PDCP PDU of the third format, the PDCP subheaders corresponding to the plurality of PDCP SDUs are after the plurality of PDCP SDUs, the plurality of PDCP SDUs are arranged in a first order, and the plurality of PDCP subheaders are arranged in the first order.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the PDCP subheader includes a length field and / or an extension field; wherein the length field of the PDCP subheader is used to indicate the length of the PDCP SDU corresponding to the PDCP subheader; in the first format PDCP PDU and / or the third format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes an additional PDCP subheader and / or PDCP SDU after the PDCP subheader; in the second format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the PDCP PDU further includes a PDCP header containing a sequence number and an extension field, wherein the extension field of the PDCP header is used to indicate whether the PDCP PDU includes a PDCP subheader and / or multiple PDCP SDUs after the PDCP header.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the PDCP PDU further includes one or more integrity verification fields.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, when the PDCP PDU includes a MAC-I field, the MAC-I field is generated according to at least one of the following: the PDCP header, the plurality of PDCP sub-headers, and the plurality of PDCP SDUs; or, when the PDCP PDU includes a plurality of MAC-I fields, the first MAC-I field among the plurality of MAC-I fields is generated according to at least one of the following: the PDCP header, the PDCP sub-header corresponding to the first MAC-I, and the PDCP SDU corresponding to the first MAC-I.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: decrypting the PDCP PDU; wherein the decryption object of the PDCP PDU includes at least one of the following: the PDCP subheader; the PDCP SDU; the MAC-I field; and / or, the decryption method of the PDCP PDU includes at least one of the following: decrypting each PDCP SDU separately; or jointly decrypting multiple PDCP SDUs.

[0055] Thirdly, embodiments of this disclosure provide an information transmission apparatus, the apparatus comprising: a processing module configured to jointly process multiple Data Convergence Protocol Service Data Units (PDCP SDUs) into a Data Convergence Protocol Protocol Data Unit (PDCP PDU); and a transmission module configured to transmit the PDCP PDU to a receiving end.

[0056] Fourthly, embodiments of this disclosure provide an information receiving device, the device comprising: a receiving module configured to receive a Data Convergence Protocol Protocol Data Unit (PDCP PDU) sent by a sending end, wherein the PDCP PDU is obtained by joint processing of multiple Data Convergence Protocol Service Data Units (PDCP SDUs).

[0057] Fifthly, embodiments of this disclosure provide a communication device (e.g., a transmitter, a receiver) comprising: one or more processors; wherein the communication device is configured to perform an information transmission method according to any one of the first aspect and optional embodiments of the first aspect, and / or an information reception method according to any one of the second aspect and optional embodiments of the second aspect.

[0058] In a sixth aspect, embodiments of this disclosure provide a communication system including a transmitter and a receiver, wherein the transmitter is configured to implement the information transmission method of any one of the first aspect and optional embodiments thereof, and the receiver is configured to implement the information reception method of any one of the second aspect and optional embodiments thereof.

[0059] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform an information transmission method according to any one of the first aspect and optional embodiments of the first aspect, and / or an information reception method according to any one of the second aspect and optional embodiments of the second aspect.

[0060] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the information transmission method described in any one of the first aspect and optional embodiments of the first aspect, and / or the information reception method described in any one of the second aspect and optional embodiments of the second aspect.

[0061] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the information sending method described in any one of the first aspect and optional embodiments of the first aspect, and / or the information receiving method described in any one of the second aspect and optional embodiments of the second aspect.

[0062] It is understood that the aforementioned information sending and receiving devices, communication equipment, communication systems, storage media, program products, and computer programs are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0063] This disclosure provides methods and apparatus for transmitting and receiving information, communication devices, and storage media. In some embodiments, the terms "information transmitting and receiving method" and "information transmitting method," "communication method," etc., can be used interchangeably; the terms "information transmitting and receiving apparatus" and "information transmitting apparatus," "communication apparatus," etc., can be used interchangeably; and the terms "information processing system," "communication system," etc., can be used interchangeably.

[0064] 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.

[0065] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0066] 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.

[0067] In the embodiments of this disclosure, unless otherwise stated, elements expressed in the singular, such as “a,” “an,” “the,” “the,” “the,” “the,” “the,” “the,” “this,” etc., may mean “one and only one,” or “one or more,” “at least one,” etc.

[0068] For example, when using articles such as "a", "an", and "the" in translation, the noun following the article can be understood as either a singular or a plural form.

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

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

[0071] 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 B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0072] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); 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, C, etc.

[0073] The prefixes such as "first" and "second" in the embodiments of this disclosure are only for distinguishing different descriptive objects and do not constitute restrictions on the position, order, priority, number or content of the descriptive objects. For the description of the descriptive objects, please refer to the description in the claims or the context of the embodiments. The use of prefixes should not constitute unnecessary restrictions.

[0074] For example, if the descriptive object is "field," then 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 "level," then 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; there can be one or more. For example, in "first device," the number of "devices" can be one or more. In addition, objects modified by different prefixes can be the same or different. For example, if the descriptive object 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 descriptive object 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.

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

[0076] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0077] 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”.

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

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

[0080] 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.

[0081] 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.

[0082] 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.

[0083] 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.

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

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

[0086] 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.

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

[0088] As shown in Figure 1A, the communication system 100 includes a transmitter 101 and a receiver 102. For example, the transmitter may be a network device and the receiver may be a terminal; or the transmitter may be a terminal and the receiver may be a network device. The network device includes at least one of the following: an access network device and a core network device.

[0089] In some embodiments, terminal 101 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.

[0090] 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, but is not limited to, 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.

[0091] 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 the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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).

[0097] In some embodiments, the receiver and sender may communicate based on the Packet Data Convergence Protocol (PDCP).

[0098] For example, the receiving end can be a terminal, and the sending end can be a network device; for example, the receiving end can be a network device, and the sending end can be a terminal.

[0099] In some embodiments, for a radio bearer (RB) used for data transmission, a corresponding transmission control entity, such as a PDCP entity and an RLC (Radio Link Control) entity, can be configured (e.g., configured by a network device or by a terminal).

[0100] For example, one PDCP entity can be associated with one or more RLC entities.

[0101] For example, a PDCP entity may include at least one of the following: a transmitting PDCP entity and a receiving PDCP entity. For example, the sending end may include a transmitting PDCP entity, and the receiving end may include a receiving PDCP entity.

[0102] For example, the supported functions of a PDCP entity include at least one of the following:

[0103] Header compression;

[0104] Integrity Protection;

[0105] Encryption and decryption (Ciphering / Deciphering).

[0106] Figure 1B is a schematic diagram of the interaction of a PDCP entity according to an embodiment of the present disclosure.

[0107] In some embodiments, in order to ensure that the functions supported by a PDCP entity can work together within a valid PDCP entity, the PDCP entity needs to process the receive and send operations according to a specific processing flow.

[0108] For example, data packets received by the PDCP layer from or sent to higher layers (also known as upper layers) can be called PDCP SDU (Service Data Unit), while data packets received by the PDCP layer from or sent to lower layers (e.g., RLC layer) are called PDCP PDU (Protocol Data Unit).

[0109] As shown in Figure 1B, in some embodiments, on the sending PDCP entity side, the processing flow may include the following steps:

[0110] Step 1A (Transmission buffer: Sequence numbering): For example, numbering the packets received from higher layers from the transmission buffer (e.g., assigning PDCP SN numbers). Higher layers include, but are not limited to, the SDAP (Service Data Adaptation Protocol) layer and the IP (Internet Protocol) layer.

[0111] Step 2A (Header Compression): If header compression is configured (e.g., ROHC (Robust Header Compression) or EHC (Ethernet Header Compression)), compress the header of the PDCP SDU packet.

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

[0113] Step 4A (Ciphering): Encrypt the data portion of the PDCP PDU, such as the PDCP SDU (and MAC-I if integrity protection is configured). The encryption process does not process the SDAP header, SDAP Control PDU, or PDCP Control PDU.

[0114] Step 5A (Add PDCP Header): Add the PDCP header to generate the PDCP PDU.

[0115] Step 6A (Routing / Duplication): Send the PDCP PDU to the RLC entity corresponding to the PDCP entity. Specifically, 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.

[0116] As shown in Figure 1B, the sending PDCP entity and the receiving PDCP entity can communicate through a radio interface, such as the Uu port. For example, the sending PDCP entity can send the PDCP PDU to the receiving PDCP entity.

[0117] As shown in Figure 1B, in some embodiments, on the receiving PDCP entity side, the processing flow may include the following steps:

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

[0119] Step 2B (Deciphering): Decrypt the data portion of the PDCP PDU, such as the PDCP SDU (and MAC-I if integrity protection is configured).

[0120] Step 3B (Integrity Verification): Generate a MAC-I for the PDCP PDU header and PDCP SDU based on the integrity protection key and algorithm. Compare the generated MAC-I with the MAC-I carried in the received PDCP PDU. If the contents are the same, the verification is successful.

[0121] Step 4B (Reception buffer: Reordering / Duplicate discarding): The received data packets are stored in the reception 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.

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

[0123] As can be seen, the sending end (e.g., the sending PDCP entity) needs to perform operations according to the process shown in Figure 1B for data packets from higher layers. In this case, when a large number of data packets are received, the above process needs to be performed on each data packet, such as adding packet headers, integrity protection, encryption, etc., which will cause a lot of signaling overhead and reduce the processing speed of the PDCP layer.

[0124] Figure 2 is an interactive schematic diagram of an information sending method according to an embodiment of the present disclosure.

[0125] As shown in Figure 2, the information sending method may include the following steps:

[0126] In step S201, the transmitting end processes multiple PDCP SDUs together into a PDCP PDU.

[0127] For example, when the sending end is a network device, the sending end can combine multiple PDCP SDUs into a PDCP PDU based on the implementation or predefined rules (such as protocol agreements).

[0128] For example, when the sender is a terminal, the sender can combine multiple PDCP SDUs into a PDCP PDU according to the instructions of the network device or predefined rules.

[0129] In some embodiments, the sender (e.g., the sending PDCP entity) may receive data packets from higher layers, such as PDCP SDUs.

[0130] One of the reasons for the technical problems described in the previous embodiments is that a PDCP PDU contains only one PDCP SDU, which leads to the need to generate a PDCP PDU separately for each PDCP SDU when generating a PDCP PDU.

[0131] According to the embodiments of this disclosure, after receiving multiple PDCP SDUs from a higher layer, the transmitting end can combine the multiple PDCP SDUs into a single PDCP PDU during the PDCP PDU generation process. Therefore, processing of multiple PDCP SDUs can be completed in a single PDCP PDU generation process, such as adding headers, integrity protection, and encryption, instead of processing each PDCP SDU separately in multiple PDCP PDU generation processes. This helps reduce signaling overhead and improves the processing speed of the PDCP layer.

[0132] For example, in the process of generating PDCP PDUs from PDCP SDUs, the operations involved in each PDCP SDU can be executed centrally. Taking the operation of adding headers to multiple PDCP SDUs as an example, it can be completed in one PDCP PDU generation process, instead of being spread across multiple PDCP PDU generation processes. Therefore, when calling the header-adding algorithm, headers can be added to multiple PDCP SDUs in one algorithm call, instead of calling the header-adding algorithm separately in multiple PDCP PDU generation processes. This is beneficial for improving the processing speed of the PDCP layer.

[0133] Furthermore, multiple PDCP SDUs can be processed together into a single PDCP PDU. During the communication process between the sender and receiver, the sender only needs to transmit the PDCP PDU containing multiple PDCP SDUs to the receiver in a single transmission. Compared to processing a single PDCP SDU into a single PDCP PDU, it is not necessary to transmit the PDCP PDU containing the PDCP SDU separately in multiple transmissions, which helps to reduce signaling overhead.

[0134] It should be noted that processing multiple PDCP SDUs together into a PDCP PDU can mean including multiple PDCP SDUs in one PDCP PDU according to the process of generating a PDCP PDU.

[0135] In step S202, the transmitting end sends the PDCP PDU to the receiving end.

[0136] In some embodiments, the receiving end can receive a PDCP PDU sent by the sending end and unpack the PDCP PDU according to the PDCP entity receiving process flow shown in FIG1B to obtain the PDCP SDU therein. However, when a PDCP PDU contains multiple PDCP SDUs, the process of unpacking the PDCP PDU by the receiving end includes some additional operations compared to FIG1B, which are described in subsequent embodiments.

[0137] In some embodiments, the information transmission method further includes: the sending end obtaining configuration information for jointly processing multiple PDCP SDUs into a PDCP PDU, wherein the sending end can jointly process multiple PDCP SDUs into a PDCP PDU based on the configuration information. For example, the indication of the network device may include configuration information, or a predefined rule may include configuration information, or, if the sending end is a network device, the sending end may determine the configuration information based on the implementation.

[0138] In some embodiments, the configuration information includes at least one of the following:

[0139] The format information of the PDCP PDU;

[0140] The identifier of the bearer corresponding to the PDCP SDU;

[0141] The identifier of the entity corresponding to the PDCP SDU;

[0142] The identifier of the data stream corresponding to the PDCP SDU;

[0143] The identifier of the session corresponding to the PDCP SDU;

[0144] The identifier of the cell (or cell group) corresponding to the PDCP SDU;

[0145] The identifier of the channel corresponding to the PDCP SDU;

[0146] The identifier of the resource corresponding to the PDCP SDU.

[0147] The following examples illustrate how the sending end processes multiple PDCP SDUs into a PDCP PDU based on the above configuration information.

[0148] In some embodiments, the configuration information includes the identifier of the bearer corresponding to the PDCP SDU.

[0149] For example, the bearer includes at least one of the following: Data Radio Bearer (DRB) and Signalling Radio Bearer (SRB).

[0150] For data received from higher layers (such as PDCP SDUs), the sender can determine the identifier of the bearer used to send the PDCP SDU. For example, if the identifier of the bearer corresponding to the PDCP SDU in the configuration information includes RB#1, then the sender will process the PDCP SDU into a PDCP PDU only when the identifier of the bearer used to send the PDCP SDU is also RB#1. For PDCP SDUs in bearers corresponding to identifiers other than RB#1, it is not necessary to process them into PDCP PDUs.

[0151] In some embodiments, the configuration information includes the identifier of the entity corresponding to the PDCP SDU.

[0152] For data received from higher layers (such as PDCP SDUs), the sender can determine the identifier of the entity used to send the PDCP SDU. For example, if the identifier of the entity corresponding to the PDCP SDU in the configuration information includes entity#1, then the sender will process the PDCP SDU into a PDCP PDU only if the identifier of the entity used to send the PDCP SDU is also entity#1. For PDCP SDUs in entities with identifiers other than entity#1, it is not necessary to process them into a PDCP PDU.

[0153] For example, the entity corresponding to a PDCP SDU may include at least one of the following: a PDCP entity for sending PDCP SDUs, and an RLC entity corresponding to the PDCP entity for sending PDCP SDUs.

[0154] In some embodiments, the configuration information includes the identifier of the data flow corresponding to the PDCP SDU. For example, the data flow may also be referred to as a Quality of Service (QoS) flow.

[0155] For data received from higher layers (e.g., PDCP SDUs), the sender can determine the identifier of the data stream used to send the PDCP SDU. For example, if the identifier of the data stream corresponding to the PDCP SDU in the configuration information includes QoS flow#1, then the sender will process the PDCP SDU into a PDCP PDU only when the identifier of the data stream used to send the PDCP SDU is also QoS flow#1. However, for PDCP SDUs in data streams corresponding to identifiers other than QoS flow#1, it is not necessary to process them into a PDCP PDU.

[0156] In some embodiments, the configuration information includes the identifier of the session corresponding to the PDCP SDU.

[0157] For data received from a higher layer (e.g., PDCP SDU), the sender can determine the identifier of the session (e.g., PDU session) used to send the PDCP SDU. For example, if the identifier of the session corresponding to the PDCP SDU in the configuration information includes PDU session#1, then the sender will process the PDCP SDU into a PDCP PDU only if the identifier of the session used to send the PDCP SDU is also PDU session#1. For PDCP SDUs in sessions corresponding to identifiers other than PDU session#1, it is not necessary to process them into PDCP PDUs.

[0158] In some embodiments, the configuration information includes the identifier of the cell corresponding to the PDCP SDU.

[0159] For data received from higher layers (such as PDCP SDUs), the sender can determine the identifier of the cell used to send the PDCP SDU. For example, if the identifier of the cell corresponding to the PDCP SDU in the configuration information includes cell#1, then the sender will process the PDCP SDU into a PDCP PDU only when the identifier of the cell used to send the PDCP SDU is also cell#1. For PDCP SDUs in cells corresponding to identifiers other than cell#1, it is not necessary to process them into a PDCP PDU.

[0160] In some embodiments, the configuration information includes the identifier of the cell group corresponding to the PDCP SDU.

[0161] For data received from higher layers (such as PDCP SDUs), the sender can determine the identifier of the cell group to which the cell used to send the PDCP SDU belongs. For example, the cell group may include at least one of the following: Master Cell Group (MCG) and Secondary Cell Group (SCG).

[0162] Taking MCG as an example, if the identifier of the cell group corresponding to the PDCP SDU in the configuration information includes MCG#1, then the sending end will process the PDCP SDU into a PDCP PDU only when the identifier of the cell group to which the cell used to send the PDCP SDU belongs is also MCG#1. However, for PDCP SDUs sent by cells in cell groups corresponding to identifiers other than MCG#1, it is not necessary to process them into a PDCP PDU.

[0163] In some embodiments, the configuration information includes the identifier of the channel corresponding to the PDCP SDU. For example, the channel may include a physical channel or a logical channel (LCH).

[0164] Taking a logical channel as an example, for data received from a higher layer (such as a PDCP SDU), the transmitter can determine the identifier of the LCH used to transmit the PDCP SDU. For example, if the identifier of the channel corresponding to the PDCP SDU in the configuration information includes LCH#1, then the transmitter will process the PDCP SDU into a PDCP PDU only when the identifier of the channel used to transmit the PDCP SDU is also LCH#1. For PDCP SDUs in channels corresponding to identifiers other than LCH#1, it is not necessary to process them into a PDCP PDU.

[0165] The following examples illustrate the situation where the configuration information includes the identifier of the resource corresponding to the PDCP SDU.

[0166] In some embodiments, the identifier of the resource corresponding to the PDCP SDU includes at least one of the following:

[0167] The identifier of the uplink authorization corresponding to the PDCP SDU;

[0168] The identifier of the downlink allocation corresponding to the PDCP SDU.

[0169] In some embodiments, when the sender is a terminal, the PDCP sending entity in the terminal can use the uplink authorization identifier corresponding to the PDCP SDU as configuration information.

[0170] For example, uplink authorization can include at least one of the following: configured uplink authorization, dynamic uplink authorization.

[0171] For example, a configured uplink grant may include a configured grant (CG), and a dynamic uplink grant may include a dynamic grant (DG). For example, a dynamic grant may correspond to a subcarrier spacing (SCS), such as 15kHz, 30kHz, etc. This disclosure does not limit this.

[0172] Taking uplink authorization including CG as an example, for data received from a higher layer (such as PDCP SDU), the sending end can determine the identifier of the resource corresponding to the PDCP SDU. For example, if the identifier of the resource corresponding to the PDCP SDU in the configuration information includes CG#1, then the sending end will process the PDCP SDU into a PDCP PDU only when the identifier of the resource used to send the PDCP SDU is also CG#1. However, for PDCP SDUs in resources corresponding to identifiers other than CG#1, it is not necessary to process them into a PDCP PDU.

[0173] In some embodiments, when the sender is a network device, the PDCP sending entity in the network device can use the identifier of the downlink allocation corresponding to the PDCP SDU as configuration information.

[0174] For example, downlink assignment can include at least one of the following: configured semi-persistent downlink assignment, dynamic downlink assignment.

[0175] For example, the configured semi-persistent downlink allocation may include semi-persistent scheduling (SPS). The dynamic downlink allocation may correspond to the subcarrier spacing (SCS), for example, the subcarrier spacing may be 15 kHz, 30 kHz, etc., and this disclosure is not limited thereto.

[0176] Taking the following allocation as an example, for data received from a higher layer (e.g., PDCP SDU), the sender can determine the identifier of the resource corresponding to the PDCP SDU. For example, if the identifier of the resource corresponding to the PDCP SDU in the configuration information includes SPS#1, then the sender will only process the PDCP SDU into a PDCP PDU if the identifier of the resource used to send the PDCP SDU is also SPS#1. However, for PDCP SDUs in resources corresponding to identifiers other than SPS#1, it is not necessary to process them into a PDCP PDU.

[0177] The following examples illustrate the format information of PDCP PDU in the configuration information.

[0178] In some embodiments, when a PDCP SDU is processed into a PDCP PDU, the PDCP PDU may include a PDCP header and a PDCP SDU. If integrity verification is configured, the PDCP PDU may also include a MAC-I. When multiple PDCP SDUs are processed together into a PDCP PDU, the format of the PDCP PDU needs to be adapted so that the multiple PDCP SDUs in the PDCP PDU can be transmitted smoothly.

[0179] In some embodiments, the receiving end (e.g., receiving a PDCP entity) may also determine the configuration information of the PDCP PDU, for example, based on predefined rules or according to instructions from the network device, and this disclosure is not limited thereto.

[0180] Furthermore, the receiving end can unpack the PDCP PDU according to its configuration information to obtain the PDCP SDU within it. For example, the receiving end can unpack the PDCP PDU according to its format to ensure that each PDCP SDU can be correctly obtained.

[0181] In some embodiments, the format information of the PDCP PDU includes one or more of the following:

[0182] In the first format, the PDCP subheader corresponding to the plurality of PDCP SDUs precedes the plurality of PDCP SDUs, the plurality of PDCP subheaders are arranged in a first order, and the plurality of PDCP SDUs are arranged in the first order.

[0183] The second format, wherein the PDCP PDU of the second format contains a plurality of sub-PDUs, the sub-PDUs including the PDCP SDU and the PDCP sub-header corresponding to the PDCP SDU, and the plurality of sub-PDUs are arranged in the first order;

[0184] The third format, wherein in the PDCP PDU of the third format, the PDCP subheaders corresponding to the plurality of PDCP SDUs are after the plurality of PDCP SDUs, the plurality of PDCP SDUs are arranged in a first order, and the plurality of PDCP subheaders are arranged in the first order.

[0185] In some embodiments, the PDCP subheader includes a length field and / or an extension field;

[0186] The length field of the PDCP subheader is used to indicate the length of the PDCP SDU corresponding to the PDCP subheader.

[0187] In the first format PDCP PDU and / or the third format PDCP PDU, the extended field of the PDCP subheader is used to indicate whether the PDCP PDU contains an additional PDCP subheader and / or PDCP SDU after the PDCP subheader;

[0188] In the second format PDCP PDU, the extended field of the PDCP subheader is used to indicate whether the PDCP PDU contains a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU.

[0189] In some embodiments, for any format of PDCP PDU, the PDCP PDU further includes a PDCP header, the PDCP header containing a sequence number and an extension field, the extension field of the PDCP header being used to indicate whether the PDCP PDU contains a PDCP subheader and / or multiple PDCP SDUs after the PDCP header.

[0190] Figure 3A is a schematic diagram of a first format PDCP PDU according to an embodiment of the present disclosure.

[0191] In some embodiments, as shown in FIG3A, in a PDCP PDU of the first format, there may be a PDCP header, multiple PDCP SDUs, and PDCP subheaders corresponding to the multiple PDCP SDUs, and the multiple PDCP subheaders are located before the multiple PDCP SDUs and after the PDCP header in the PDCP PDU.

[0192] For example, the PDCP header may include at least one of the following fields: sequence number (e.g., PDCP SN (Sequence Number) field) and extension (E, Extend) field.

[0193] The extension field in the PDCP header can be one bit or more bits. Taking a one-bit extension field in the PDCP header as an example, the extension field in the PDCP header can indicate whether the PDCP PDU contains a PDCP subheader after the PDCP header, or it can indicate whether the PDCP PDU contains multiple PDCP SDUs after the PDCP header.

[0194] In some embodiments, when a PDCP PDU contains multiple PDCP SDUs, each PDCP SDU can correspond to a PDCP subheader. For example, if a PDCP PDU contains n PDCP SDUs, then the PDCP PDU also contains n PDCP subheaders, with the i-th PDCP SDU corresponding to the i-th PDCP subheader. The i-th PDCP subheader can be used to indicate relevant information about the i-th PDCP SDU, where i and n are integers, and i is less than or equal to n.

[0195] For example, a PDCP subheader may include at least one of the following fields: length field, extension field.

[0196] For example, the length field in the PDCP subheader can be used to indicate the length of the PDCP SDU corresponding to the PDCP subheader.

[0197] As shown in Figure 3A, in the first format PDCP SDU, since multiple PDCP subheaders are arranged consecutively, multiple PDCP SDUs are also arranged consecutively, and the multiple PDCP subheaders precede the multiple PDCP SDUs. In this case, the extension field in the PDCP subheader can indicate whether the PDCP PDU contains any additional PDCP subheaders after the PDCP subheader containing the extension field, or indicate whether the PDCP PDU contains any PDCP SDUs after the PDCP subheader containing the extension field.

[0198] It should be noted that the extended field in the PDCP subheader indicates whether the PDCP PDU contains any additional PDCP subheaders after the PDCP subheader containing the extended field. These additional PDCP subheaders refer to other PDCP subheaders besides the one containing the extended field. For example, in the embodiments described later, the extended field in PDCP subheader #1 indicates whether the PDCP PDU contains any additional PDCP subheaders after PDCP subheader #1. These additional PDCP subheaders refer to PDCP subheaders other than PDCP subheader #1.

[0199] Taking a PDCP PDU containing two PDCP SDUs as an example, namely PDCP SDU#1 and PDCP SDU#2, the PDCP subheader corresponding to PDCP SDU#1 is denoted as PDCP subheader #1, and the PDCP subheader corresponding to PDCP SDU#2 is denoted as PDCP subheader #2.

[0200] The length field in PDCP subheader #1 can indicate the length of PDCP SDU #1 (e.g., the number of percentages), and the extension field in PDCP subheader #1 can indicate whether there are additional PDCP subheaders after PDCP subheader #1, or whether there are additional PDCP SDUs after PDCP subheader #1.

[0201] Since there are PDCP subheader #2 and PDCP SDU #1 and PDCP SDU #2 after PDCP subheader #1, the extended field in PDCP subheader #1 can indicate that there are additional PDCP subheaders after PDCP subheader #1, or indicate that the PDCP PDU contains PDCP SDUs after PDCP subheader #1.

[0202] The length field in PDCP subheader #2 can indicate the length of PDCP SDU #2 (e.g., the number of percentages). The extension field in PDCP subheader #2 can indicate whether there are any additional PDCP subheaders after PDCP subheader #2, or whether there are any additional PDCP SDUs after PDCP subheader #2.

[0203] Since there is no additional PDCP subheader after PDCP subheader #2, but there are PDCP SDU #1 and PDCP SDU #2, the extended field in PDCP subheader #2 can indicate that there is no additional PDCP subheader after PDCP subheader #2, or indicate that the PDCP PDU contains a PDCP SDU after PDCP subheader #2.

[0204] In some embodiments, in a PDCP PDU of the first format, multiple PDCP subheaders and multiple PDCP SDUs can be arranged in a first order. For example, the first order can be a predefined order, either from smallest to largest index or from largest to smallest index. For instance, the first order can be the order in which the transmitter receives the PDCP SDUs from the higher layer.

[0205] Alternatively, in a PDCP PDU of the first format, multiple PDCP subheaders are arranged in a first order, while multiple PDCP SDUs can be arranged according to the order of their corresponding PDCP subheaders.

[0206] Figure 3B is a schematic diagram of a second-format PDCP PDU according to an embodiment of the present disclosure.

[0207] In some embodiments, as shown in FIG3B, a PDCP PDU in the first format may contain a PDCP header and multiple sub-PDUs, each sub-PDU containing a PDCP SDU and a corresponding PDCP sub-header. The content of the PDCP header can be referred to the previous embodiments and will not be repeated here.

[0208] In a sub-PDU, the PDCP SDU can be located after the PDCP sub-header as shown in Figure 3B, or it can be adjusted so that the PDCP SDU is located before the PDCP sub-header; this disclosure does not limit this. The following examples mainly use the case shown in Figure 3B (i.e., the PDCP SDU is located after the PDCP sub-header) as an example for illustrative purposes.

[0209] In some embodiments, when a PDCP PDU contains multiple PDCP SDUs, each PDCP SDU may correspond to a PDCP subheader, and the PDCP SDU and the corresponding PDCP subheader may be located in the corresponding subPDU.

[0210] It should be noted that the sub-PDU is only a conceptual description introduced for the convenience of explaining the PDCP PDU format, and can also be replaced by other words (such as unit, module).

[0211] For example, if a PDCP PDU contains n PDCP SDUs, then the PDCP PDU also contains n PDCP subheaders. The i-th PDCP SDU corresponds to the i-th PDCP subheader. The i-th PDCP subheader can be used to indicate relevant information of the i-th PDCP SDU. The i-th PDCP subheader and the i-th PDCP SDU are located in the i-th subPDU, where i and n are integers, and i is less than or equal to n.

[0212] For example, a PDCP subheader may include at least one of the following fields: length field, extension field.

[0213] For example, the length field in the PDCP subheader can be used to indicate the length of the PDCP SDU corresponding to the PDCP subheader.

[0214] As shown in Figure 3B, in the second format PDCP SDU, since the multiple PDCP subheaders are not arranged consecutively, and the multiple PDCP SDUs are not arranged consecutively either, the PDCP subheader precedes the PDCP SDU in a sub-PDU. In this case, the extended field in the PDCP subheader can indicate whether the PDCP PDU contains another PDCP subheader after the sub-PDU containing the extended field, or whether the PDCP PDU contains another PDCP SDU after the sub-PDU containing the extended field, or whether the PDCP PDU contains another sub-PDU after the sub-PDU containing the extended field.

[0215] Taking a PDCP PDU containing two PDCP SDUs as an example, namely PDCP SDU#1 and PDCP SDU#2, the PDCP subheader corresponding to PDCP SDU#1 is denoted as PDCP subheader #1, and the PDCP subheader corresponding to PDCP SDU#1 is denoted as PDCP subheader #2. PDCP SDU#1 and PDCP subheader #1 are in subPDU#1, and PDCP SDU#2 and PDCP subheader #2 are in subPDU#2.

[0216] The length field in PDCP subheader #1 can indicate the length of PDCP SDU #1 (e.g., the number of percentages). The extension field in PDCP subheader #1 can indicate whether there is another PDCP subheader after subPDU #1, or whether there is another PDCP SDU after PDU #1, or whether there is another subPDU after subPDU #1.

[0217] Since there is a PDCP subheader #2 and PDCP SDU #1 and PDCP SDU #2 after PDCP subheader #1, the extended field in PDCP subheader #1 can indicate that a PDCP subheader is included after subPDU #1, or indicate that a PDCP PDU is included after subPDU #1, or indicate that a PDCP PDU is included after subPDU #1.

[0218] The length field in PDCP subheader #2 can indicate the length of PDCP SDU #2 (e.g., the number of percentages). The extension field in PDCP subheader #2 can indicate whether there is another PDCP subheader after subPDU #2, or whether there is another PDCP SDU after subPDU #1, or whether there is another subPDU after subPDU #2.

[0219] Since there is no PDCP subheader after PDCP subheader #2, but there is PDCP SDU #2, the extended field in PDCP subheader #2 can indicate that there is no PDCP subheader after subPDU #2, or indicate that the PDCP PDU contains a PDCP SDU after subPDU #2, or indicate that the PDCP PDU does not contain any additional subPDUs after subPDU #2.

[0220] In some embodiments, in a second-format PDCP PDU, multiple sub-PDUs are arranged in a first order. For example, the first order can be a predefined order, ordered from smallest to largest index or from largest to smallest index. For instance, the first order can be the order in which the transmitter receives the PDCP SDU from a higher layer.

[0221] Figure 3C is a schematic diagram of a third-format PDCP PDU according to an embodiment of the present disclosure.

[0222] In some embodiments, as shown in FIG3C, a third-format PDCP PDU may contain a PDCP header, multiple PDCP SDUs, and PDCP sub-headers corresponding to the multiple PDCP SDUs, with the multiple PDCP sub-headers located after the multiple PDCP SDUs in the PDCP PDU. The content of the PDCP header can be referred to the previous embodiments, and will not be repeated here.

[0223] In some embodiments, when a PDCP PDU contains multiple PDCP SDUs, each PDCP SDU can correspond to a PDCP subheader. For example, if a PDCP PDU contains n PDCP SDUs, then the PDCP PDU also contains n PDCP subheaders, with the i-th PDCP SDU corresponding to the i-th PDCP subheader. The i-th PDCP subheader can be used to indicate relevant information about the i-th PDCP SDU, where i and n are integers, and i is less than or equal to n.

[0224] For example, a PDCP subheader may include at least one of the following fields: length field, extension field.

[0225] For example, the length field in the PDCP subheader can be used to indicate the length of the PDCP SDU corresponding to the PDCP subheader.

[0226] As shown in Figure 3C, in the third format PDCP SDU, since multiple PDCP subheaders are arranged consecutively, multiple PDCP SDUs are also arranged consecutively, and multiple PDCP subheaders follow multiple PDCP SDUs. In this case, the extension field in the PDCP subheader can indicate whether the PDCP PDU contains any additional PDCP subheaders after the PDCP subheader containing the extension field, or whether the PDCP PDU contains any additional PDCP SDUs after the PDCP SDU corresponding to the PDCP subheader containing the extension field.

[0227] Taking a PDCP PDU containing two PDCP SDUs as an example, namely PDCP SDU#1 and PDCP SDU#2, the PDCP subheader corresponding to PDCP SDU#1 is denoted as PDCP subheader #1, and the PDCP subheader corresponding to PDCP SDU#1 is denoted as PDCP subheader #2.

[0228] The length field in PDCP subheader #1 can indicate the length of PDCP SDU #1 (e.g., the number of percentages), and the extension field in PDCP subheader #1 can indicate whether there are additional PDCP subheaders after PDCP subheader #1, or whether there are additional PDCP SDUs after PDCP subheader #1.

[0229] Since there is a PDCP subheader #2 after PDCP subheader #1 and a PDCP SDU #2 after PDCP SDU #1, the extended field in PDCP subheader #1 can indicate that there is an additional PDCP subheader after PDCP subheader #1, or indicate that the PDCP PDU contains a PDCP SDU after PDCP SDU #1.

[0230] The length field in PDCP subheader #2 can indicate the length of PDCP SDU #2 (e.g., the number of percentages). The extension field in PDCP subheader #2 can indicate whether there are additional PDCP subheaders after PDCP subheader #2, or whether there are additional PDCP SDUs after PDCP SDU #2.

[0231] Since there are no additional PDCP subheaders after PDCP subheader #2, and no additional PDCP SDUs after PDCP SDU #2, the extended field in PDCP subheader #2 can indicate that there are no additional PDCP subheaders after PDCP subheader #2, or indicate that there are no additional PDCP SDUs after PDCP SDU #2.

[0232] In some embodiments, in a third-format PDCP PDU, multiple PDCP subheaders and multiple PDCP SDUs can be arranged in a first order. For example, the first order can be a predefined order, either from smallest to largest index or from largest to smallest index. For instance, the first order can be the order in which the transmitter receives the PDCP SDUs from a higher layer.

[0233] Alternatively, in the third format PDCP PDU, multiple PDCP SDUs are arranged in the first order, while multiple PDCP subheaders can be arranged according to the order of their corresponding PDCP SDUs.

[0234] It should be noted that in some embodiments, when the protocol stipulates packet header compression, or when the network device is configured to compress packet headers, for example, when packet header compression compresses the packet header of the PDCP SDU, the value of the length field in the PDCP subheader can indicate the length of the PDCP SDU after the packet header of the PDCP SDU is compressed, for any of the three formats of PDCP SDU mentioned above.

[0235] In some embodiments, the PDCP PDU further includes one or more integrity verification (e.g., MAC-I) fields. For example, the MAC-I field can be used for integrity verification of the PDCP SDU (e.g., it can also be referred to as integrity protection).

[0236] For example, if the protocol specifies an integrity verification function, or if the network device is configured with an integrity verification function, the PDCP SDU may include a MAC-I domain.

[0237] In some embodiments, when the PDCP PDU includes a MAC-I field, the MAC-I field is generated based on at least one of the following: the PDCP header, the plurality of PDCP sub-headers, and the plurality of PDCP SDUs; or,

[0238] When the PDCP PDU includes multiple MAC-I fields, the first MAC-I field among the multiple MAC-I fields is generated according to at least one of the following: the PDCP header, the PDCP subheader corresponding to the first MAC-I, and the PDCP SDU corresponding to the first MAC-I.

[0239] For example, for any of the three formats of PDCP PDU, if the PDCP PDU contains a MAC-I field, the MAC-I field can be generated based on the PDCP packet header, all PDCP subheaders, and all PDCP SDUs (for example, it can be generated based on the integrity protection key and algorithm).

[0240] For example, for any of the three formats of a PDCP PDU, if the PDCP PDU contains multiple MAC-I fields, the MAC-I fields can correspond to the PDCP SDUs and can be generated based on the PDCP header, the corresponding PDCP SDU, and the PDCP subheader of the PDCP SDU (e.g., generated based on the integrity protection key and algorithm). For example, if a PDCP PDU contains n MAC-I fields, n PDCP SDUs, and n PDCP subheaders, where the i-th MAC-I field corresponds to the i-th PDCP SDU, then the i-th MAC-I field can be generated based on the i-th PDCP SDU and the i-th PDCP subheader.

[0241] In some embodiments, the information transmission method further includes encrypting the PDCP PDU.

[0242] In some embodiments, the encrypted object of the PDCP PDU includes at least one of the following:

[0243] The PDCP subheader;

[0244] The PDCP SDU;

[0245] The MAC-I domain.

[0246] In some embodiments, the encryption method for encrypting the PDCP PDU includes at least one of the following:

[0247] Each of the PDCP SDUs is encrypted separately;

[0248] Multiple PDCP SDUs are jointly encrypted.

[0249] In some embodiments, if the encryption function is agreed upon in the protocol, or if the network device is configured with encryption function, PDCP PDUs in any of the three formats mentioned above can be encrypted.

[0250] For example, the object of the encryption operation may include at least one of the following: PDCP subheader, PDCP SDU, and integrity verification field.

[0251] For example, the encryption operation can ignore the PDCP subheader, in which case encryption can be performed only for multiple PDCP SDUs.

[0252] For example, when encrypting multiple PDCP SDUs, the encryption operation can be performed separately for each PDCP SDU. For instance, encrypting multiple PDCP SDUs separately can be applied to PDCP SDUs of a specific format, such as a second format.

[0253] For example, when encrypting multiple PDCP SDUs, the encryption operation can be performed on multiple PDCP SDUs jointly. For example, the method of jointly encrypting multiple PDCP SDUs can be applied to PDCP SDUs of a specific format, such as including at least one of a first format and a third format.

[0254] In some embodiments, the PDCP subheader corresponding to the PDCP SDU in the PDCP PDU can be generated by the sending end (e.g., the receiving PDCP entity) after receiving the PDCP SDU, or it can be generated after compressing the PDCP SDU (e.g., packet header compression).

[0255] In some embodiments, the sequence number, such as PDCP SN, in the PDCP header of the PDCP PDU can be generated after determining the number of PDCP SDUs that the PDCP PDU can contain.

[0256] In some embodiments, for example, the sending end includes a terminal, and the information sending method may include: receiving processing indication information sent by a network device, wherein the processing indication information is used to indicate whether the sending end will process multiple PDCP SDUs together into a PDCP PDU.

[0257] For example, network devices can send processing instruction information to the sending end, which can then determine whether to process multiple PDCP SDUs together into a PDCP PDU based on the processing instruction information.

[0258] For example, when the processing instruction information indicates that multiple PDCP SDUs are processed together into a PDCP PDU, the sending end can process multiple PDCP SDUs together into a PDCP PDU based on any of the embodiments described above.

[0259] For example, if the processing instruction indicates that multiple PDCP SDUs should not be processed together into a PDCP PDU, the sending end can process each PDCP SDU into a PDCP PDU separately, for example, based on the process shown in Figure 1B.

[0260] For example, when the sending end is a network device, the network device can determine whether to process multiple PDCP SDUs together into a PDCP PDU based on implementation or predefined rules (such as protocol agreements).

[0261] In some embodiments, the information sending method further includes: obtaining constraints on configuration information for jointly processing multiple PDCP SDUs into a PDCP PDU; wherein, if the constraints are met, the multiple PDCP SDUs are jointly processed into a PDCP PDU. For example, the constraints may be included in the instructions of the network device, or may be defined by predefined rules.

[0262] For example, when the network device's instructions or predefined rules contain restrictions, for multiple PDCP SDUs received from the higher layer, the sending end can determine whether the restrictions are met. If the restrictions are met, the multiple PDCP SDUs can be processed together into a PDCP PDU based on any of the embodiments described above. If the restrictions are not met, the sending end can process each PDCP SDU into a PDCP PDU separately, for example, based on the process shown in Figure 1B.

[0263] In some embodiments, the limiting conditions include at least one of the following:

[0264] PDCP PDU length threshold;

[0265] The threshold for the number of multiple PDCP SDUs in a PDCP PDU;

[0266] The length and threshold of multiple PDCP SDUs in a PDCP PDU;

[0267] The length threshold of a single PDCP SDU in a PDCP PDU.

[0268] In some embodiments, the limiting conditions include a length threshold for the PDCP PDU.

[0269] For example, the sum of the lengths of multiple PDCP SDUs processed together, and / or the sum of the lengths of the PDCP subheaders corresponding to multiple PDCP SDUs, and / or the sum of the lengths of the MAC-I fields, need to be less than or equal to the length threshold of the PDCP SDU. Accordingly, the length threshold of the PDCP SDU can limit the number of PDCP SDUs processed together.

[0270] For example, if the length threshold of a PDCP PDU is 9000 bytes, then when multiple PDCP SDUs are processed together into a PDCP PDU, the sum of the lengths of the multiple PDCP SDUs, and / or the sum of the lengths of the PDCP subheaders corresponding to the multiple PDCP SDUs, and / or the sum of the lengths of the MAC-I fields, must be less than or equal to 9000 bytes.

[0271] For example, in multiple PDSC SDUs, each PDCP SDU is 1000 bytes long, the PDCP subheader corresponding to each PDCP SDU is 2 bytes long, and the MAC-I field is 4 bytes long. Therefore, to ensure that the sum of the lengths of the multiple PDCP SDUs, their corresponding PDCP subheaders, and the MAC-I field is less than or equal to 9000 bytes, the number of multiple PDCP SDUs needs to be less than or equal to 8.

[0272] It should be noted that the length threshold of the PDCP PDU obtained by processing multiple PDSC SDUs together can be the same as or different from the length threshold of the PDCP PDU obtained by processing one PDSC SDU. This disclosure does not limit this.

[0273] In some embodiments, the limiting conditions include a threshold number of multiple PDCP SDUs in a PDCP PDU.

[0274] For example, when the sending end processes multiple PDCP SDUs together into a PDCP PDU, it needs to ensure that the number of multiple PDCP SDUs is less than or equal to the PDCP SDU number threshold.

[0275] For example, the threshold for the number of PDCP SDUs is 3. When the transmitter receives 2 PDCP SDUs from the higher layer, these 2 PDCP SDUs can be combined into 1 PDCP PDU; when the transmitter receives 4 PDCP SDUs from the higher layer, only 3 of these 4 PDCP SDUs (e.g., the first 3 PDCP SDUs received) can be combined into 1 PDCP PDU, and the other PDCP SDU can be processed into another PDCP PDU.

[0276] In some embodiments, the constraints include the length and threshold of multiple PDCP SDUs in the PDCP PDU.

[0277] For example, when the sending end processes multiple PDCP SDUs together into a PDCP PDU, it needs to ensure that the sum of the lengths of the multiple PDCP SDUs is less than or equal to the sum of the lengths and thresholds of the PDCP SDUs.

[0278] For example, the length and threshold of a PDCP SDU are 1000 bytes. When the transmitter receives 9 PDCP SDUs from the higher layer, each PDCP SDU being 100 bytes long, the sum of the lengths of the 9 PDCP SDUs is 900 bytes, which is less than 1000 bytes. Therefore, these 9 PDCP SDUs can be combined into 1 PDCP PDU. When the transmitter receives 11 PDCP SDUs from the higher layer, where the length of the first 10 PDCP SDUs is 99 bytes each and the length of the 11th PDCP SDU is 110 bytes, the sum of the lengths of the first 10 PDCP SDUs is 990 bytes, which is less than 1000 bytes. However, the sum of the lengths of the 11 PDCP SDUs is 1100 bytes, which is greater than 1000 bytes. Therefore, only the first 10 PDCP SDUs (e.g., the first 10 received) can be combined into 1 PDCP PDU, and the 11th PDCP SDU can be processed into another PDCP PDU.

[0279] In some embodiments, the limiting conditions include a length threshold for a single PDCP SDU in a PDCP PDU.

[0280] For example, when the sending end processes multiple PDCP SDUs together into a PDCP PDU, it needs to ensure that the sum of the lengths of each PDCP SDU in the multiple PDCP SDUs is less than or equal to the length threshold of a single PDCP SDU.

[0281] For example, the length threshold for a single PDCP SDU is 1000 bytes. When the transmitter receives three PDCP SDUs from a higher layer, each 900 bytes long (less than 1000 bytes), these three PDCP SDUs can be combined into one PDCP PDU. Conversely, if the transmitter receives three PDCP SDUs from a higher layer, with the first two 900 bytes long and the third 1100 bytes long, only the first two are less than 1000 bytes long. Therefore, the first two PDCP SDUs can be combined into one PDCP PDU, and the third PDCP SDU can be discarded or processed into another PDCP PDU.

[0282] It should be noted that when the sending end processes multiple PDCP SDUs into a single PDCP PDU, it can add the PDCP SDUs one by one into the same PDCP SDU according to the receiving order of the PDCP SDUs.

[0283] In the embodiments with the aforementioned limiting conditions, if the limiting conditions are not met, the transmitting end can stop adding PDCP SDUs to the same PDCP SDU according to the receiving order of the PDCP SDU.

[0284] For example, in the process of adding three PDCP SDUs to one PDCP PDU, the three PDCP SDUs are PDCP SDU#1, PDCP SDU#2, and PDCP SDU#3, and the receiving order is PDCP SDU#1, PDCP SDU#2, and PDCP SDU#3. The sending end can first check whether PDCP SDU#1 meets the restrictions. If it does, PDCP SDU#1 is added to PDCP SDU#n. Then, it checks whether PDCP SDU#2 meets the restrictions. If it does, PDCP SDU#2 is added to PDCP SDU#n. Then, it checks whether PDCP SDU#3 meets the restrictions. If it does not meet the restrictions, PDCP SDU#3 is not added to PDCP SDU#n. For example, PDCP SDU#3 can be discarded or added to PDCP#n+1. In this case, it can be ensured that PDCP SDU#n contains only two PDCP SDUs (PDCP SDU#1 and PDCP SDU#2) that satisfy the constraints.

[0285] In some embodiments, the receiver may receive a PDCP PDU sent by the sender.

[0286] In some embodiments, the receiving end can obtain configuration information for processing multiple PDCP SDUs together into a PDCP PDU, and then unpack the PDCP SDU according to the configuration information.

[0287] For example, configuration information can be sent from the sending end to the receiving end, or the receiving end can determine the configuration information based on predefined rules, or receive the configuration information from the network device. This disclosure does not limit the way the receiving end obtains the configuration information.

[0288] For example, the receiving end can determine whether the PDCP PDU contains a PDCP subheader after the PDCP header, or whether the PDCP PDU contains multiple PDCP SDUs, based on the extended field in the PDCP header of the PDCP PDU.

[0289] For example, if the configuration information includes the format information of the PDCP PDU, the receiving end can determine which of the three formats the PDCP PDU belongs to, so that the receiving end can determine what each part of the information in the PDCP PDU represents based on the format of the PDCP PDU.

[0290] For example, after determining the format information of the PDCP PDU, the receiving end can determine the length of the corresponding PDCP SDU based on the length field in the PDCP subheader.

[0291] For example, after determining the format information of the PDCP PDU, the receiving end can determine whether the PDCP PDU contains an additional PDCP subheader and / or PDCP SDU after the PDCP subheader, based on the extended field of the PDCP subheader, for the first and third format PDCP PDUs.

[0292] For example, after determining the format information of the PDCP PDU, the receiving end can determine, for the second format PDCP PDU, whether the PDCP PDU contains a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU, based on the extended field of the PDCP subheader.

[0293] For example, if the configuration information includes the identifier of the bearer corresponding to the PDCP SDU, the receiving end can determine the bearer used to send multiple PDCP SDUs in the PDCP PDU.

[0294] For example, if the configuration information includes the identifier of the entity corresponding to the PDCP SDU, the receiving end can determine the entity used to send multiple PDCP SDUs in the PDCP PDU.

[0295] For example, if the configuration information includes the identifier of the data stream corresponding to the PDCP SDU, the receiving end can determine the data stream used to send multiple PDCP SDUs in the PDCP PDU.

[0296] For example, if the configuration information includes the identifier of the session corresponding to the PDCP SDU, the receiving end can determine the session used to send multiple PDCP SDUs in the PDCP PDU.

[0297] For example, if the configuration information includes the identifier of the cell corresponding to the PDCP SDU, the receiving end can determine the cell used to send multiple PDCP SDUs in the PDCP PDU.

[0298] For example, if the configuration information includes the identifier of the cell group corresponding to the PDCP SDU, the receiving end can determine the cell group to which the cell used to send multiple PDCP SDUs in the PDCP PDU belongs.

[0299] For example, if the configuration information includes the identifier of the channel corresponding to the PDCP SDU, the receiver can determine the channel used to transmit multiple PDCP SDUs in the PDCP PDU.

[0300] For example, if the configuration information includes the identifier of the resource corresponding to the PDCP SDU, the receiving end can determine the resource used to send multiple PDCP SDUs in the PDCP PDU.

[0301] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S202. For example, step S201 may be implemented as a standalone embodiment, step S202 may be implemented as a standalone embodiment, and step S201+S202 may be implemented as a standalone embodiment, but is not limited thereto.

[0302] In some embodiments, steps S201 and S202 may be performed in an alternate order or simultaneously.

[0303] In some embodiments, step S201 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0304] In some embodiments, step S202 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0305] In some embodiments, other optional implementations described before or after the specification corresponding to FIG2 may be referred to.

[0306] 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.

[0307] 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".

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

[0309] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0310] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

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

[0312] 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.

[0313] Corresponding to the aforementioned embodiments of the information sending method and information receiving method, this disclosure also provides embodiments of the information sending device and the information receiving device.

[0314] Figure 4 is a schematic block diagram illustrating an information sending device according to an embodiment of the present disclosure. For example, the information sending device can be applied to a sending end. As shown in Figure 4, the information sending device includes: a processing module 401, a sending module 402, and a receiving module 403.

[0315] In some embodiments, the processing module is configured to process multiple Data Convergence Protocol Service Data Units (PDCP SDUs) into a Data Convergence Protocol Protocol Data Unit (PDCP PDU); the sending module is configured to send the PDCP PDU to the receiving end.

[0316] In some embodiments, the receiving module is configured to process multiple PDCP SDUs together into configuration information for a PDCP PDU.

[0317] In some embodiments, the configuration information includes at least one of the following: the format information of the PDCP PDU; the identifier of the bearer corresponding to the PDCP SDU; the identifier of the entity corresponding to the PDCP SDU; the identifier of the data stream corresponding to the PDCP SDU; the identifier of the session corresponding to the PDCP SDU; the identifier of the cell corresponding to the PDCP SDU; the identifier of the channel corresponding to the PDCP SDU; and the identifier of the resource corresponding to the PDCP SDU.

[0318] In some embodiments, the identifier of the resource corresponding to the PDCP SDU includes at least one of the following: the identifier of the uplink authorization corresponding to the PDCP SDU; the identifier of the downlink allocation corresponding to the PDCP SDU.

[0319] In some embodiments, the format information includes one of the following:

[0320] In the first format, the PDCP subheader corresponding to the plurality of PDCP SDUs precedes the plurality of PDCP SDUs, the plurality of PDCP subheaders are arranged in a first order, and the plurality of PDCP SDUs are arranged in the first order.

[0321] The second format, wherein the PDCP PDU of the second format contains a plurality of sub-PDUs, the sub-PDUs including the PDCP SDU and the PDCP sub-header corresponding to the PDCP SDU, and the plurality of sub-PDUs are arranged in the first order;

[0322] The third format, wherein in the PDCP PDU of the third format, the PDCP subheaders corresponding to the plurality of PDCP SDUs are after the plurality of PDCP SDUs, the plurality of PDCP SDUs are arranged in a first order, and the plurality of PDCP subheaders are arranged in the first order.

[0323] In some embodiments, the PDCP subheader includes a length field and / or an extension field; wherein the length field of the PDCP subheader is used to indicate the length of the PDCP SDU corresponding to the PDCP subheader; in the first format PDCP PDU and / or the third format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes an additional PDCP subheader and / or PDCP SDU after the PDCP subheader; in the second format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU.

[0324] In some embodiments, the PDCP PDU further includes a PDCP header, which contains a sequence number and an extension field. The extension field of the PDCP header is used to indicate whether the PDCP PDU contains a PDCP subheader and / or multiple PDCP SDUs after the PDCP header.

[0325] In some embodiments, the PDCP PDU further includes one or more integrity verification fields.

[0326] In some embodiments, when the PDCP PDU includes a MAC-I field, the MAC-I field is generated according to at least one of the following: the PDCP header, the plurality of PDCP subheaders, and the plurality of PDCP SDUs; or, when the PDCP PDU includes a plurality of MAC-I fields, the first MAC-I field among the plurality of MAC-I fields is generated according to at least one of the following: the PDCP header, the PDCP subheader corresponding to the first MAC-I, and the PDCP SDU corresponding to the first MAC-I.

[0327] In some embodiments, the processing module is further configured to encrypt the PDCP PDU; wherein the encryption object of encrypting the PDCP PDU includes at least one of the following: the PDCP subheader; the PDCP SDU; the MAC-I field; and / or, the encryption method of encrypting the PDCP PDU includes at least one of the following: encrypting each PDCP SDU separately; or jointly encrypting multiple PDCP SDUs.

[0328] In some embodiments, the sending end includes a terminal, and the receiving module is configured to receive processing indication information sent by a network device, wherein the processing indication information is used to indicate whether the sending end will process multiple PDCP SDUs together into a PDCP PDU.

[0329] In some embodiments, the receiving module is configured to obtain constraints on configuration information for jointly processing multiple PDCP SDUs into a PDCP PDU; wherein the processing module is configured to jointly process multiple PDCP SDUs into a PDCP PDU when the constraints are met.

[0330] In some embodiments, the limiting conditions include at least one of the following: a length threshold for a PDCP PDU; a number threshold for multiple PDCP SDUs in a PDCP PDU; the length and threshold of multiple PDCP SDUs in a PDCP PDU; and a length threshold for a single PDCP SDU in a PDCP PDU.

[0331] Figure 5 is a schematic block diagram illustrating an information receiving device according to an embodiment of the present disclosure. For example, the information receiving device can be applied to a receiving end. As shown in Figure 5, the information receiving device includes: a receiving module 501 and a processing module 502.

[0332] In some embodiments, the receiving module is configured to receive a Data Convergence Protocol Protocol Data Unit (PDCP PDU) sent by the sending end, wherein the PDCP PDU is obtained by joint processing of multiple Data Convergence Protocol Service Data Units (PDCP SDUs).

[0333] In some embodiments, the receiving module is configured to acquire configuration information for jointly processing multiple PDCP SDUs into a PDCP PDU.

[0334] In some embodiments, the configuration information includes at least one of the following: the format information of the PDCP PDU; the identifier of the bearer corresponding to the PDCP SDU; the identifier of the entity corresponding to the PDCP SDU; the identifier of the data stream corresponding to the PDCP SDU; the identifier of the session corresponding to the PDCP SDU; the identifier of the cell corresponding to the PDCP SDU; the identifier of the channel corresponding to the PDCP SDU; and the identifier of the resource corresponding to the PDCP SDU.

[0335] In some embodiments, the identifier of the resource corresponding to the PDCP SDU includes at least one of the following: the identifier of the uplink authorization corresponding to the PDCP SDU; the identifier of the downlink allocation corresponding to the PDCP SDU.

[0336] In some embodiments, the format information includes one of the following:

[0337] In the first format, the PDCP subheader corresponding to the plurality of PDCP SDUs precedes the plurality of PDCP SDUs, the plurality of PDCP subheaders are arranged in a first order, and the plurality of PDCP SDUs are arranged in the first order.

[0338] The second format, wherein the PDCP PDU of the second format contains a plurality of sub-PDUs, the sub-PDUs including the PDCP SDU and the PDCP sub-header corresponding to the PDCP SDU, and the plurality of sub-PDUs are arranged in the first order;

[0339] The third format, wherein in the PDCP PDU of the third format, the PDCP subheaders corresponding to the plurality of PDCP SDUs are after the plurality of PDCP SDUs, the plurality of PDCP SDUs are arranged in a first order, and the plurality of PDCP subheaders are arranged in the first order.

[0340] In some embodiments, the PDCP subheader includes a length field and / or an extension field; wherein the length field of the PDCP subheader is used to indicate the length of the PDCP SDU corresponding to the PDCP subheader; in the first format PDCP PDU and / or the third format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes an additional PDCP subheader and / or PDCP SDU after the PDCP subheader; in the second format PDCP PDU, the extension field of the PDCP subheader is used to indicate whether the PDCP PDU includes a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU.

[0341] In some embodiments, the PDCP PDU further includes a PDCP header, which contains a sequence number and an extension field. The extension field of the PDCP header is used to indicate whether the PDCP PDU contains a PDCP subheader and / or multiple PDCP SDUs after the PDCP header.

[0342] In some embodiments, the PDCP PDU further includes one or more integrity verification fields.

[0343] In some embodiments, when the PDCP PDU includes a MAC-I field, the MAC-I field is generated according to at least one of the following: the PDCP header, the plurality of PDCP subheaders, and the plurality of PDCP SDUs; or, when the PDCP PDU includes a plurality of MAC-I fields, the first MAC-I field among the plurality of MAC-I fields is generated according to at least one of the following: the PDCP header, the PDCP subheader corresponding to the first MAC-I, and the PDCP SDU corresponding to the first MAC-I.

[0344] In some embodiments, the apparatus further includes: a processing module configured to decrypt the PDCP PDU; wherein the decryption object of the PDCP PDU includes at least one of the following: the PDCP subheader; the PDCP SDU; the MAC-I field; and / or, the decryption method of the PDCP PDU includes at least one of the following: decrypting each PDCP SDU separately; or decrypting multiple PDCP SDUs together.

[0345] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0346] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided 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.

[0347] 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.

[0348] 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).

[0349] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 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 6100 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.

[0350] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can 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 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0351] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., steps S201, S202, but not limited thereto) in the above method, such as sending and / or receiving, while the processor 6101 performs at least one of other steps (e.g., steps S201, S202, but not limited thereto). 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, sending unit, transmitter, sending circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0352] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6102 and can be used to receive data from the memories 6102 or other devices, and to send data to the memories 6102 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6102 and send the data to the processor 6101.

[0353] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. 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 and programs; (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.

[0354] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0355] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

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

[0357] In some embodiments, the interface circuit 6202 performs at least one of the communication steps (e.g., steps S201, S202, but not limited thereto) in the above-described method, such as sending and / or receiving. For example, the interface circuit 6202 performing the communication steps (e.g., sending and / or receiving) in the above-described method means that the interface circuit 6202 performs data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S201, S202, but not limited thereto).

[0358] 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.

[0359] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 6100, cause the communication device 6100 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.

[0360] This disclosure also provides a program product that, when executed by the communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

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

Claims

1. A method for sending information, characterized in that, The method, executed by the sending end, includes: Multiple Data Convergence Protocol Service Data Units (PDCP SDUs) are combined into a Data Convergence Protocol Protocol Data Unit (PDCP PDU). The PDCP PDU is sent to the receiving end.

2. The method according to claim 1, characterized in that, The method further includes: Obtain the configuration information for combining multiple PDCP SDUs into a PDCP PDU.

3. The method according to claim 2, characterized in that, The configuration information includes at least one of the following: The format information of the PDCP PDU; The identifier of the bearer corresponding to the PDCP SDU; The identifier of the entity corresponding to the PDCP SDU; The identifier of the data stream corresponding to the PDCP SDU; The identifier of the session corresponding to the PDCP SDU; The identifier of the cell corresponding to the PDCP SDU; The identifier of the channel corresponding to the PDCP SDU; The identifier of the resource corresponding to the PDCP SDU.

4. The method according to claim 3, characterized in that, The identifier of the resource corresponding to the PDCP SDU includes at least one of the following: The identifier of the uplink authorization corresponding to the PDCP SDU; The identifier of the downlink allocation corresponding to the PDCP SDU.

5. The method according to claim 3, characterized in that, The format information includes one or more of the following: In the first format, the PDCP subheader corresponding to the plurality of PDCP SDUs precedes the plurality of PDCP SDUs, the plurality of PDCP subheaders are arranged in a first order, and the plurality of PDCP SDUs are arranged in the first order. The second format, wherein the PDCP PDU of the second format contains a plurality of sub-PDUs, the sub-PDUs including the PDCP SDU and the PDCP sub-header corresponding to the PDCP SDU, and the plurality of sub-PDUs are arranged in the first order; The third format, wherein in the PDCP PDU of the third format, the PDCP subheaders corresponding to the plurality of PDCP SDUs are after the plurality of PDCP SDUs, the plurality of PDCP SDUs are arranged in a first order, and the plurality of PDCP subheaders are arranged in the first order.

6. The method according to claim 5, characterized in that, The PDCP subheader includes a length field and / or an extension field; The length field of the PDCP subheader is used to indicate the length of the PDCP SDU corresponding to the PDCP subheader. In the first format PDCP PDU and / or the third format PDCP PDU, the extended field of the PDCP subheader is used to indicate whether the PDCP PDU contains an additional PDCP subheader and / or PDCP SDU after the PDCP subheader; In the second format PDCP PDU, the extended field of the PDCP subheader is used to indicate whether the PDCP PDU contains a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU.

7. The method according to claim 5 or 6, characterized in that, The PDCP PDU also includes a PDCP header, which contains a sequence number and an extension field. The extension field of the PDCP header is used to indicate whether the PDCP PDU contains a PDCP subheader and / or multiple PDCP SDUs after the PDCP header.

8. The method according to any one of claims 5 to 7, characterized in that, The PDCP PDU also includes one or more integrity verification fields.

9. The method according to claim 8, characterized in that, When the PDCP PDU includes a MAC-I field, the MAC-I field is generated based on at least one of the following: the PDCP header, the plurality of PDCP subheaders, and the plurality of PDCP SDUs; or, When the PDCP PDU includes multiple MAC-I fields, the first MAC-I field among the multiple MAC-I fields is generated according to at least one of the following: the PDCP header, the PDCP subheader corresponding to the first MAC-I, and the PDCP SDU corresponding to the first MAC-I.

10. The method according to any one of claims 5 to 9, characterized in that, The method further includes: Encrypt the PDCP PDU; The encrypted object of the PDCP PDU includes at least one of the following: The PDCP subheader; The PDCP SDU; The MAC-I domain; And / or, the encryption method for encrypting the PDCP PDU includes at least one of the following: Each of the PDCP SDUs is encrypted separately; Multiple PDCP SDUs are jointly encrypted.

11. The method according to any one of claims 1 to 10, characterized in that, The sending end is a terminal, and the method further includes: The system receives processing instruction information sent by a network device, wherein the processing instruction information is used to instruct the sending end whether to process multiple PDCP SDUs together into a PDCP PDU.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: Restrictions on obtaining configuration information for combining multiple PDCP SDUs into a PDCP PDU; Among them, under the condition that the above-mentioned restrictions are met, multiple PDCP SDUs are processed together into a PDCP PDU.

13. The method according to claim 12, characterized in that, The limiting conditions include at least one of the following: PDCP PDU length threshold; The threshold for the number of multiple PDCP SDUs in a PDCP PDU; The length and threshold of multiple PDCP SDUs in a PDCP PDU; The length threshold of a single PDCP SDU in a PDCP PDU.

14. An information receiving method, characterized in that, The method, executed by the receiving end, includes: The receiver receives a Data Convergence Protocol Protocol Data Unit (PDCP PDU) sent by the sending end, wherein the PDCP PDU is obtained by joint processing of multiple Data Convergence Protocol Service Data Units (PDCP SDUs).

15. The method according to claim 14, characterized in that, The method further includes: Obtain the configuration information for combining multiple PDCP SDUs into a PDCP PDU.

16. The method according to claim 15, characterized in that, The configuration information includes at least one of the following: The format information of the PDCP PDU; The identifier of the bearer corresponding to the PDCP SDU; The identifier of the entity corresponding to the PDCP SDU; The identifier of the data stream corresponding to the PDCP SDU; The identifier of the session corresponding to the PDCP SDU; The identifier of the cell corresponding to the PDCP SDU; The identifier of the channel corresponding to the PDCP SDU; The identifier of the resource corresponding to the PDCP SDU.

17. The method according to claim 16, characterized in that, The identifier of the resource corresponding to the PDCP SDU includes at least one of the following: The identifier of the uplink authorization corresponding to the PDCP SDU; The identifier of the downlink allocation corresponding to the PDCP SDU.

18. The method according to claim 16, characterized in that, The format information includes one or more of the following: In the first format, the PDCP subheader corresponding to the plurality of PDCP SDUs precedes the plurality of PDCP SDUs, the plurality of PDCP subheaders are arranged in a first order, and the plurality of PDCP SDUs are arranged in the first order. The second format, wherein the PDCP PDU of the second format contains a plurality of sub-PDUs, the sub-PDUs including the PDCP SDU and the PDCP sub-header corresponding to the PDCP SDU, and the plurality of sub-PDUs are arranged in the first order; The third format, wherein in the PDCP PDU of the third format, the PDCP subheaders corresponding to the plurality of PDCP SDUs are after the plurality of PDCP SDUs, the plurality of PDCP SDUs are arranged in a first order, and the plurality of PDCP subheaders are arranged in the first order.

19. The method according to claim 18, characterized in that, The PDCP subheader includes a length field and / or an extension field; The length field of the PDCP subheader is used to indicate the length of the PDCP SDU corresponding to the PDCP subheader. In the first format PDCP PDU and / or the third format PDCP PDU, the extended field of the PDCP subheader is used to indicate whether the PDCP PDU contains an additional PDCP subheader and / or PDCP SDU after the PDCP subheader; In the second format PDCP PDU, the extended field of the PDCP subheader is used to indicate whether the PDCP PDU contains a PDCP subheader, and / or a PDCP SDU, and / or an additional subPDU after the subPDU.

20. The method according to claim 18 or 19, characterized in that, The PDCP PDU also includes a PDCP header, which contains a sequence number and an extension field. The extension field of the PDCP header is used to indicate whether the PDCP PDU contains a PDCP subheader and / or multiple PDCP SDUs after the PDCP header.

21. The method according to any one of claims 18 to 20, characterized in that, The PDCP PDU also includes one or more integrity verification fields.

22. The method according to claim 21, characterized in that, When the PDCP PDU includes a MAC-I field, the MAC-I field is generated based on at least one of the following: the PDCP header, the plurality of PDCP subheaders, and the plurality of PDCP SDUs; or, When the PDCP PDU includes multiple MAC-I fields, the first MAC-I field among the multiple MAC-I fields is generated according to at least one of the following: the PDCP header, the PDCP subheader corresponding to the first MAC-I, and the PDCP SDU corresponding to the first MAC-I.

23. The method according to any one of claims 18 to 22, characterized in that, The method further includes: Decrypt the PDCP PDU; The decryption target for the PDCP PDU includes at least one of the following: The PDCP subheader; The PDCP SDU; The MAC-I domain; And / or, the decryption method for the PDCP PDU includes at least one of the following: Decrypt each of the PDCP SDUs separately; Decrypt multiple PDCP SDUs together.

24. An information transmitting device, characterized in that, The device includes: The processing module is configured to jointly process multiple Data Convergence Protocol Service Data Units (PDCP SDUs) into a Data Convergence Protocol Protocol Data Unit (PDCP PDU). The transmitting module is configured to transmit the PDCP PDU to the receiving end.

25. An information receiving device, characterized in that, The device includes: The receiving module is configured to receive Data Convergence Protocol Protocol Data Unit (PDCP PDU) sent by the sending end, wherein the PDCP PDU is obtained by joint processing of multiple Data Convergence Protocol Service Data Units (PDCP SDU).

26. A communication device, characterized in that, include: One or more processors; The communication device is used to perform the information transmission method according to any one of claims 1 to 13, and / or the information reception method according to any one of claims 14 to 23.

27. A communication system, characterized in that, It includes a sending end and a receiving end, wherein the sending end is configured to implement the information sending method according to any one of claims 1 to 13, and the receiving end is configured to implement the information receiving method according to any one of claims 14 to 23.

28. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the information transmission method of any one of claims 1 to 13, and / or the information reception method of any one of claims 14 to 23.

29. A program product, characterized in that, When the above-mentioned program product is executed by a communication device, the communication device performs the information transmission method according to any one of claims 1 to 13, and / or the information reception method according to any one of claims 14 to 23.

Images