Data transmission method, apparatus, terminal and network side device

Abstract

The present application belongs to the technical field of communications. Disclosed are data transmission methods, an apparatus, a terminal and a network side device. A data transmission method in the embodiments of the present application comprises: a terminal receives first configuration information from a network side device, the first configuration information being used for configuring a target protocol stack communication mode; and, in the target protocol stack communication mode, the terminal executes at least one of a first sending operation and a first receiving operation on the basis of a serial number (SN) of a data packet, the SN being used for a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of the same L2 protocol layer of L2, the processing operation of the L2 protocol layer comprising at least two operation sets, and each operation set comprising at least one L2 operation.

Description

Data transmission method and apparatus, terminal, and network-side device

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to Chinese Patent Application No. 202410648929.9, filed on May 23, 2024, the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0003] The present application belongs to the technical field of communication, and specifically relates to a data transmission method, device, terminal and network-side equipment. BACKGROUND

[0004] In a communication system, Layer 2 (L2) usually includes four L2 protocol layers, such as a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Service Data Adaptation Protocol (SDAP) layer, and a Medium Access Control (MAC) layer. In order to cope with general transmission requirements, the PDCP layer maintains a serial number (SN) and a COUNT value, which are mainly used for security operations and reordering in the case of multi-flow switching, and the RLC layer also needs an SN, which is used for segmentation and recombination of unacknowledged mode (UM) data packets, segmentation (or re-segmentation) and retransmission of acknowledged mode (AM) data packets, and other operations, wherein the SN and other information of the two layers need to be carried in the data packet header and sent to the opposite end. The SDAP and MAC sub-layers also increase the sub-header operation. The addition of the header of each layer of data packet will bring additional overhead to data packet transmission. Therefore, there is a problem of large packet header overhead of Layer 2 processed data packets in the related art. SUMMARY

[0005] Embodiments of the present application provide a data transmission method, device, terminal and network-side equipment, which can solve the problem of large packet header overhead of Layer 2 processed data packets.

[0006] In a first aspect, a data transmission method is provided, comprising:

[0007] The terminal receives first configuration information from the network-side equipment, wherein the first configuration information is used to configure a target protocol stack communication mode.

[0008] In the target protocol stack communication mode, the terminal performs at least one of a first sending operation and a first receiving operation based on a sequence number SN of a data packet.

[0009] The SN is used for performing a layer 2 (L2) processing operation, the L2 processing operation is a processing operation of a same L2 protocol layer of the L2, and the processing operation of the L2 protocol layer includes at least two operation sets, and each operation set includes at least one L2 operation.

[0010] In a second aspect, a data transmission method is provided, including:

[0011] The network-side device sends first configuration information to the terminal, and the first configuration information is used for configuring a target protocol stack communication mode.

[0012] In the target protocol stack communication mode, the network-side device performs at least one of a second sending operation and a second receiving operation based on a sequence number SN of a data packet.

[0013] The SN is used for performing a layer 2 (L2) processing operation, the L2 processing operation is a processing operation of a same L2 protocol layer of the L2, and the processing operation of the L2 protocol layer includes at least two operation sets, and each operation set includes at least one L2 operation.

[0014] In a third aspect, a data transmission apparatus is provided, including:

[0015] The first transmission module is configured to receive first configuration information from a network-side device, the first configuration information is used for configuring a target protocol stack communication mode, and in the target protocol stack communication mode, at least one of a first sending operation and a first receiving operation is performed based on a sequence number SN of a data packet.

[0016] The SN is used for performing a layer 2 (L2) processing operation, the L2 processing operation is a processing operation of a same L2 protocol layer of the L2, and the processing operation of the L2 protocol layer includes at least two operation sets, and each operation set includes at least one L2 operation.

[0017] In a fourth aspect, a data transmission apparatus is provided, including:

[0018] The second transmission module is configured to send first configuration information to a terminal, the first configuration information is used for configuring a target protocol stack communication mode, and in the target protocol stack communication mode, at least one of a second sending operation and a second receiving operation is performed based on a sequence number SN of a data packet.

[0019] The SN is configured to perform a Layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer including at least two operation sets, the operation sets including at least one L2 operation.

[0020] In a fifth aspect, a data transmission apparatus is provided, which is configured to perform the steps of the method according to the first aspect, or implement the steps of the method according to the second aspect.

[0021] In a sixth aspect, a terminal is provided, which includes a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the first aspect.

[0022] In a seventh aspect, a terminal is provided, which includes a processor and a communication interface, wherein the communication interface is configured to receive first configuration information from a network-side device, the first configuration information being used to configure a target protocol stack communication mode; and perform at least one of a first sending operation and a first receiving operation based on a sequence number (SN) of a data packet in the target protocol stack communication mode.

[0023] The SN is configured to perform a Layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer including at least two operation sets, the operation sets including at least one L2 operation.

[0024] In an eighth aspect, a network-side device is provided, which includes a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the second aspect.

[0025] In a ninth aspect, a network-side device is provided, which includes a processor and a communication interface, wherein the communication interface is configured to send first configuration information to a terminal, the first configuration information being used to configure a target protocol stack communication mode; and perform at least one of a second sending operation and a second receiving operation based on a sequence number (SN) of a data packet in the target protocol stack communication mode.

[0026] The SN is configured to perform a Layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer including at least two operation sets, the operation sets including at least one L2 operation.

[0027] In a tenth aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions, which, when executed by a processor, implement the steps of the method according to the first aspect or implement the steps of the method according to the second aspect.

[0028] In an eleventh aspect, a wireless communication system is provided, and the wireless communication system includes a terminal and a network-side device, the terminal is configured to implement the steps of the method according to the first aspect, and the network-side device is configured to implement the steps of the method according to the second aspect.

[0029] In a twelfth aspect, a chip is provided, and the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or instructions to implement the method according to the first aspect or implement the method according to the second aspect.

[0030] In a thirteenth aspect, a computer program / program product is provided, and the computer program / program product is stored in a storage medium, and the computer program / program product is executed by at least one processor to implement the steps of the method according to the first aspect or implement the steps of the method according to the second aspect.

[0031] In the embodiments of the present application, a terminal receives first configuration information from a network-side device, and the first configuration information is used to configure a target protocol stack communication mode. Under the target protocol stack communication mode, the terminal performs at least one of a first sending operation and a first receiving operation based on a sequence number (SN) of a data packet. The SN is used for a layer 2 (L2) processing operation, the L2 processing operation is a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer includes at least two operation sets, and the operation set includes at least one L2 operation. In this way, the L2 processing of one data packet is implemented by using one SN, so that the overhead of the SN in the data packet can be reduced. Therefore, the embodiments of the present application reduce the overhead of the packet header of the data packet subjected to the L2 processing. BRIEF DESCRIPTION OF DRAWINGS

[0032] FIG. 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0033] FIG. 2 is a schematic diagram of a conventional user plane protocol stack;

[0034] FIG. 3 is a schematic diagram of a header structure of each L2 sublayer;

[0035] FIG. 4 is a flowchart of a data transmission method according to an embodiment of the present application;

[0036] FIG. 5 is a schematic diagram of a packet header structure of a data packet in a data transmission method according to an embodiment of the present application;

[0037] FIG. 6 is a processing flow diagram of a data transmission method according to an embodiment of the present application;

[0038] FIG. 7a is a structure diagram of a user plane protocol stack to which the data transmission method according to an embodiment of the present application can be applied;

[0039] FIG. 7b is another structure diagram of a user plane protocol stack to which the data transmission method according to an embodiment of the present application can be applied;

[0040] FIG. 8 is a flow diagram of another data transmission method according to an embodiment of the present application;

[0041] FIG. 9 is a structure diagram of a data transmission apparatus according to an embodiment of the present application;

[0042] FIG. 10 is a structure diagram of another data transmission apparatus according to an embodiment of the present application;

[0043] FIG. 11 is a structure diagram of a communication device according to an embodiment of the present application;

[0044] FIG. 12 is a structure diagram of a terminal according to an embodiment of the present application;

[0045] FIG. 13 is a structure diagram of a network-side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a particular order or sequence. It should be understood that the terms used in this way can be interchanged, so that the embodiments of the present application can be implemented in an order other than that illustrated or described herein, and the objects distinguished by "first", "second" are generally of a kind, and are not limited in number. For example, the first object can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, the protection scope of "A or B" at least covers three schemes, i.e. scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and B. In addition, the terms "A and / or B", "at least one of A and B", "at least one of A or B" also at least cover the above three schemes, respectively. The character " / " generally means that the objects before and after are in an "or" relationship.

[0047] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). The direct indication can be understood as that the sender explicitly informs the receiver of specific information, operations to be performed or requested results, etc. in the sent indication. The indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or judges and determines the operations to be performed or the requested results according to the judgment result.

[0048] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than the NR system, such as 6th Generation (6G) communication systems. th Generation,6G) communication systems.

[0049] FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a terminal-side device such as a mobile phone, a Tablet Personal Computer, a Laptop Computer, a notebook computer, a Personal Digital Assistant (PDA), a palmtop computer, a netbook, an Ultra-mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR) device, a Virtual Reality (VR) device, a robot, a wearable device, a flight vehicle, a Vehicle User Equipment (VUE), a shipboard device, a Pedestrian User Equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture), a game console, a Personal Computer (PC), a kiosk, or a self-service machine. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, smart clothes, etc. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. The access network device can also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device can include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc.The base station can be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmit / receive point (TRP), or some other suitable terminology in the art, so long as 5 the context of the term permits, and the base station is not limited to a particular terminology. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0050] For the convenience of understanding, some contents related to the embodiments of the present application are described as follows:

[0051] As shown in FIG. 2, in the NR network, the user plane protocol stack mainly includes MAC, RLC, PDCP, SDAP and physical (Physical, PHY) layer.

[0052] Of these, the PHY layer, which is the L1 protocol stack, and the other four layers constitute the L2 protocol stack. The MAC layer is primarily responsible for mapping between logical channels and transport channels, handling logical channel priorities, multiplexing and demultiplexing MAC Service Data Units (SDUs), scheduling, and Hybrid Automatic Repeat reQuest (HARQ) operations. The RLC layer provides data transmission in Transparent Mode (TM), UM, and AM modes, segmentation and reassembly, Automatic Repeat reQuest (ARQ), and independent sequence numbers. The PDCP layer provides header compression and decompression, secure operation, separate bearer routing, and replication. The SDAP layer provides the mapping of Quality of Service (QoS) flow to radio bearers and identifies uplink and downlink packets with QoS flow IDs (QFIs).

[0053] An example of an L2 data stream is shown in Figure 3. A transport block generated by the MAC layer consists of concatenated RLC Protocol Data Units (PDUs) from two radio bearers, RBx and RBy. The two RLC PDUs of RBx are obtained by adding headers to two complete IP packets at each level, while one RLC PDU of RBy is a segment from an IP packet.

[0054] 5th generation (5) th In the later stages of 5G (Generation 5G) communication systems, including the 6G era, business demands have further expanded. For example, in some satellite transmission scenarios with extremely limited bandwidth, the goal is to transmit as much effective data as possible while minimizing additional packet overhead. Similarly, some Internet of Things (IoT) devices communicate with the network using small data packets, and their capabilities are extremely limited, sometimes even lacking battery power. Therefore, reducing additional packet overhead and simplifying processes are also primary requirements for these scenarios. To address these needs, the data processing method described in this application is proposed.

[0055] The data transmission method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0056] Referring to FIG4, an embodiment of this application provides a data transmission method, as shown in FIG4, the data transmission method includes:

[0057] At step 401, a terminal receives first configuration information from a network side device, the first configuration information being used for configuring a target protocol stack communication mode;

[0058] At step 402, under the target protocol stack communication mode, the terminal performs at least one of a first sending operation and a first receiving operation based on a sequence number SN of a data packet;

[0059] The SN is used for a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer including at least two operation sets, and the operation sets including at least one L2 operation.

[0060] In the embodiments of the present application, the target protocol stack communication mode can be understood as a communication mode based on a new protocol version, which can be understood as a new L2 protocol version, or referred to as a minimalist protocol stack.

[0061] Optionally, in some embodiments, different operation sets in the at least two operation sets can be operation sets of different sub-layers of L2. For example, the at least two operation sets can include an operation set of a first sub-layer and an operation set of a second sub-layer. The first sub-layer can include PDCP, and the second sub-layer can include RLC. Further, the first sub-layer and the second sub-layer can include at least one of the following sub-layers: PDCP and SDAP.

[0062] For example, in some embodiments, the new protocol stack version includes a first L2 protocol layer, which can be understood as a protocol layer integrating the functions of MAC, RLC, PDCP and SDAP.

[0063] For example, in some embodiments, the new protocol stack version includes a second L2 protocol layer, which can be understood as a protocol layer integrating the functions of RLC, PDCP and SDAP.

[0064] For example, in some embodiments, the new protocol stack version includes a third L2 protocol layer, which can be understood as a protocol layer integrating the functions of RLC and PDCP.

[0065] For example, in some embodiments, the new protocol stack version includes a fourth L2 protocol layer, which can be understood as a protocol layer integrating the functions of MAC, RLC and PDCP.

[0066] Optionally, the SN being used for the L2 processing operation can be understood as the SN being used for related processing of layer 2, i.e., the SN used for L2 processing operation of a data packet is one SN.

[0067] It should be understood that the specific operations included in the L2 processing operation are associated with the actual operations performed by Layer 2.

[0068] For the sending operation, the L2 processing operation can include at least one of the following according to actual operation needs: identifying segmentation or resegmentation; security operation; processing reception status feedback of the data packet. For example, when the data packet is small and does not need to be segmented or resegmented, the L2 processing operation can not include identifying segmentation or resegmentation.

[0069] For the receiving operation, the L2 processing operation can include at least one of the following according to actual operation needs: data packet reassembly operation; data packet duplication detection; data packet reordering; data packet decryption; data packet integrity verification; and reception status feedback. For example, in the case of a segmented data packet, the L2 processing operation includes the data packet reassembly operation; in the case of a complete data packet, the L2 processing operation does not include the data packet reassembly operation. For example, in the case of an encrypted data packet at the sending end, the L2 processing operation includes data packet decryption; in the case of an unencrypted data packet at the sending end, the L2 processing operation does not include data packet decryption.

[0070] Optionally, for the reception status feedback, ACK or NACK feedback can be performed at the receiving end according to the SN, and the feedback can be received at the sending end, and retransmission can be performed in the case of receiving NACK feedback.

[0071] In the embodiments of the present application, a terminal receives first configuration information from a network side device, the first configuration information being used to configure a target protocol stack communication mode; under the target protocol stack communication mode, the terminal performs at least one of a first sending operation and a first receiving operation based on a sequence number SN of a data packet; the SN is used to perform a Layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer including at least two operation sets, and the operation set including at least one L2 operation. In this way, the L2 processing is implemented by using one SN for one data packet, thereby reducing the overhead of the SN in the data packet. Therefore, the embodiments of the present application reduce the overhead of the packet header of the data packet subjected to the L2 processing.

[0072] Optionally, in some embodiments, the at least two operation sets include a first operation set and a second operation set.

[0073] The first operation set includes at least one L2 operation: identifying segmentation or resegmentation; data packet reassembly operation; data packet duplication detection; data packet reordering; processing reception status feedback of the data packet; and performing reception status feedback of the data packet.

[0074] Or, the second operation set includes at least one L2 operation of: a security operation, the security operation including at least one of integrity protection and encryption; decryption of a data packet; integrity verification of a data packet.

[0075] Optionally, in some embodiments, the at least two operation sets further include at least one of a third operation set and a fourth operation set;

[0076] The third operation set includes at least one L2 operation of: mapping between a logical channel and a transport channel; logical channel priority processing; multiplexing or demultiplexing of a medium access control (MAC) service data unit (SDU); scheduling; hybrid automatic repeat request (HARQ);

[0077] The fourth operation set includes at least one L2 operation of: mapping of a quality of service (QoS) flow to a radio bearer; marking of a QoS flow.

[0078] In the embodiments of the present application, the first operation set can be understood as an operation set of RLC, the second operation set can be understood as an operation set of PDCP, the third operation set can be understood as an operation set of MAC, and the fourth operation set can be understood as an operation set of SDAP.

[0079] For example, in some embodiments, the new protocol version includes a first protocol version, in which the SN is used to perform one L2 processing operation, which can include the first operation set, the second operation set and the third operation set; or, the new protocol version includes a second protocol version, in which the SN is used to perform one L2 processing operation, which can include the first operation set, the second operation set, the third operation set and the fourth operation set; or, the new protocol version includes a third protocol version, in which the SN is used to perform one L2 processing operation, which can include the second operation set, the third operation set and the fourth operation set.

[0080] Optionally, in some embodiments, the first sending operation includes:

[0081] The terminal performs first processing on the first data packet to be transmitted in the buffer, to obtain a second data packet, the second data packet including a first SN;

[0082] The terminal sends the second data packet;

[0083] The first processing includes at least one of:

[0084] Header compression is performed on the first data packet;

[0085] allocate the first SN to the first data packet; or, in a case where the terminal is configured with a pre-concatenation function, concatenate at least two first data packets, and allocate the first SN to the concatenated data packet;

[0086] perform a security operation on the first data packet based on the first SN, the security operation including at least one of integrity protection and encryption;

[0087] identify segmenting or re-segmenting the first data packet based on the first SN;

[0088] add a first packet header to the first data packet based on the first SN.

[0089] In the embodiments of the present application, each of the processing steps in the first processing can be performed according to actual needs. For example, when header compression is needed, the processing of header compression on the first data packet can be performed.

[0090] Optionally, in some embodiments, in a case where the terminal is not configured with a pre-concatenation function, the first SN can be allocated to the first data packet before header compression is performed on the first data packet; and in a case where the terminal is configured with a pre-concatenation function, the first SN can be allocated to the concatenated data packet.

[0091] Optionally, the security operation can be performed before the concatenation of the at least two fourth data packets, so as to reduce the processing overhead such as the number and complexity of the security operation. Of course, in some embodiments, the security operation can also be performed before the concatenation of the at least two fourth data packets.

[0092] Optionally, in some embodiments, the first packet header includes at least one of the following:

[0093] a first indication field for indicating a data packet type;

[0094] a second indication field for indicating a sequence number;

[0095] a third indication field for indicating a type of control PDU;

[0096] a fourth indication field for indicating a message integrity authentication code;

[0097] a fifth indication field for indicating a segment identifier;

[0098] a sixth indication field for indicating a segment offset;

[0099] a seventh indication field for indicating a sub-segment sequence number.

[0100] In the embodiments of the present application, the first indication field can be understood or replaced by a D / C field, and the length thereof can be 1 bit (bit), which is used for indicating the display of a data PDU or a control PDU.

[0101] The second indication field can be understood or replaced by an SN field, and the length thereof can be configured as 6 bits, 7 bits, 12 bits, and the like.

[0102] The third indication field can be understood or replaced by a PDU type field, which is carried when the D / C field indicates a control PDU, and can be used to distinguish and indicate RObust Header Compression (ROHC) feedback, status report, EHC feedback, UDC feedback, and the like; each control PDU can have an independent format, and after the PDU type indicates the type, different formats are read according to the type; wherein, the PDCP status report or the RLC status report is indicated respectively, or is combined into one.

[0103] The fourth indication field can be understood or replaced by a message integrity authentication code (Message Authentication Code for Integrity, MAC-I) field, the MAC-I is dedicated to integrity protection, and the length thereof can be generally set as 4 bytes; in the case that integrity protection is configured, the suffix is at the end of the data packet.

[0104] The fifth indication field can be understood or replaced by a segment indication (Segment Indicator) field, and 2 bits can be set to mark segmentation, and 4 values can respectively represent: no segmentation, first segment, intermediate segment, and last segment.

[0105] The sixth indication field can be understood or replaced by a segment offset (Segment Offset, SO) field, the segment offset indicates the starting position of the segment in the original SDU, and is mainly used to support the AM data of re-segmentation.

[0106] The seventh indication field can be understood or replaced by a sub-segment sequence number (Seg_Num) field, and is mainly used for UM data without re-segmentation.

[0107] It should be noted that the processing modes for different segments are as follows:

[0108] When the data is AM data, because retransmission and resegmentation need to be supported, the SO field is needed to flexibly indicate the relationship between the segment and the original SDU, for example, the segment of packet SN = 1, SO = 100, Length = 200 is confirmed by the state feedback NACK, when the retransmission of the segment is arranged, the retransmission resource is insufficient, and finally the resegmentation is performed to retransmit two segments of SO = 100, Length = 150 and SO = 250, Length = 50.

[0109] When the data is UM data, because retransmission and resegmentation do not need to be supported, only the first segmentation is needed, an SN can be allocated to the entire SDU, and a subsegment sequence number is additionally carried by each segment, the receiving end can recombine the subsegments of the same SN in sequence, and the SI marks the end.

[0110] Alternatively, when the data is UM data, because retransmission and resegmentation do not need to be supported, only the first segmentation is needed, the SN can be used to expand to indicate the subsegment sequence number, for example, SN = 0, SI indicates the first segment, SN = 1, SI indicates the middle segment, SN = 2, SI indicates the middle segment, SN = 3, SI indicates the last segment, so the four segments can be recombined in sequence into a complete SDU at the receiving end; of course, this method is only suitable for data that does not need security operation, that is, data that does not have encryption function enabled and does not have integrity protection function enabled, and the SN can be expanded for use, because the encryption of the entire SDU needs a unique COUNT value; when security operation is needed, the Seg_Num mode can be adopted, the unique SN participates in the security operation, and the Seg_Num is used for segment recombination indication.

[0111] That is, in some embodiments, different segment data packets of the same data packet carry the same SN and different subsegment sequence numbers. Alternatively, different segment data packets of the same data packet carry different SNs, and the SI in the segment data packet is used to indicate the segment type corresponding to the data packet, wherein the SN of the segment data is associated with the segment order corresponding to the segment data packet, and the segment type includes unsegmented, first segment, middle segment and last segment.

[0112] Optionally, in some embodiments, the first packet header further includes at least one of the following:

[0113] An eighth indication field, used to indicate whether a ninth indication field exists;

[0114] A ninth indication field, used to indicate the data length.

[0115] In the embodiments of the present application, the target protocol stack communication mode is a protocol stack communication mode corresponding to a first protocol version, and the second data packet obtained after the first data is processed by layer 2 can be understood as including a packet header, i.e., a first packet header. In this way, since MAC, RLC, PDCP and SDAP are combined into one protocol layer, the whole byte arrangement can be performed together, avoiding reserved (R), and the header overhead can be further reduced. For example, in the embodiments of the present application, the packet header of the data packet is designed as shown in FIG. 5. The D / C field indicates that this is a data, the SI field is a segment indication, and the SN field indicates a sequence number. If it is UM data, not segmented, security not enabled, and not required to be delivered in order, the SN can also be omitted.

[0116] Optionally, the eighth indication field can be understood or replaced as a P field, and the ninth indication field can be understood or replaced as an L field.

[0117] Optionally, in some embodiments, the first processing further includes: after adding the first packet header to the first data packet, adding a second packet header, the second packet header including at least one of the following:

[0118] An eighth indication field for indicating whether a ninth indication field exists;

[0119] A ninth indication field for indicating a data length;

[0120] A tenth indication field for indicating a data packet type.

[0121] In the embodiments of the present application, the target protocol stack communication mode is a protocol stack communication mode corresponding to a second protocol version, and the second data packet obtained after the first data is processed by layer 2 can be understood as including two packet headers, i.e., a first packet header and a second packet header. At this time, two L2 protocol layers need to be designed respectively, and each performs whole byte arrangement.

[0122] Optionally, in some embodiments, in the case that the target protocol stack communication mode supports a split bearer, when a target bearer corresponding transmission resource block arrives, the first processing is performed to obtain a size of the target bearer corresponding transmission resource block matching the second data packet.

[0123] In the embodiments of the present application, the arrival of the transmission resource block can be understood as receiving an uplink grant (UL grant). For example, on a target bearer, a resource block obtains an authorization and can be packaged and sent, at this time, it can be understood as that the target bearer corresponding transmission resource block arrives.

[0124] It should be understood that each target bearer corresponds to a MAC layer, which can be understood or replaced as an L2 lower layer, and the protocol layer combined by the above RLC, PDCP and SDAP can be understood or replaced as an L2 higher layer.

[0125] Optionally, in some embodiments, the first receiving operation includes:

[0126] The terminal identifies the data packet type of the received third data packet, and the data packet type includes a control protocol data unit (PDU) or a data PDU.

[0127] In the case where the third data packet is a data PDU, the terminal performs a second processing based on a second SN;

[0128] The second SN is a SN contained in the third data packet, and the second processing includes at least one of the following:

[0129] Decrypting the third data packet based on the second SN;

[0130] Performing integrity verification on the third data packet based on the second SN;

[0131] Performing reassembly operation on the third data packet based on the second SN;

[0132] Performing repetition detection on the third data packet based on the second SN;

[0133] Performing reordering on the third data packet based on the second SN;

[0134] Performing reception status feedback of the third data packet based on the second SN.

[0135] Optionally, in some embodiments, the second processing further includes any of the following:

[0136] Performing deheader operation;

[0137] Performing deheader operation after deconcatenating the third data packet.

[0138] Optionally, in some embodiments, the method further includes:

[0139] The terminal sends capability information to a network side device, and the capability information includes at least one of the following:

[0140] Target indication information, the target indication information being used to indicate whether to support an L2 protocol layer;

[0141] Supported L2 protocol layer;

[0142] a parameter configuration of each supported L2 protocol layer.

[0143] In the embodiments of the present application, the terminal reports the capability information to the network side device, so that the network side device can know whether the terminal has the capability to support the new protocol version, thereby avoiding the network side device from making invalid configuration through the first configuration information, and ensuring the reliability of communication.

[0144] Optionally, in some embodiments, the first configuration information comprises at least one of the following: an L2 protocol layer; and a parameter configuration of the L2 protocol layer.

[0145] In the embodiments of the present application, the first configuration information can comprise an L2 protocol layer in the new protocol version and a parameter configuration of the L2 protocol layer in the new protocol version.

[0146] Optionally, in some embodiments, the method further comprises:

[0147] The terminal receives second configuration information from the network side device, wherein the second configuration information is used for reconfiguring or switching to a legacy protocol stack communication mode.

[0148] Optionally, in some embodiments, after the terminal receives the second configuration information from the network side device, the method further comprises:

[0149] When there is data forwarding in switching, the data forwarding is performed in a manner of a packet data convergence protocol service data unit (PDCP SDU) in the legacy protocol stack.

[0150] In the embodiments of the present application, the above-mentioned legacy protocol stack can be understood as a protocol stack designed in layers of MAC, RLC, PDCP and SDAP. Since the data forwarding is performed in a manner of a packet data convergence protocol service data unit (PDCP SDU) in the legacy protocol stack, it can ensure that the terminal and the network side device can understand correctly, and reduce packet loss to a certain extent.

[0151] It should be noted that the data forwarding can be understood as, in the process of switching, since the source base station of the UE needs to be changed to the target base station, the UE data that is not sent or not successfully sent by the source base station needs to be forwarded to the target base station for sending. Since one of the source base station and the target base station is a legacy base station type, it can only read PDCP SDU or PDCP PDU two forwarding formats, and the other base station is a minimalist protocol stack design without PDCP PDU data format, therefore, the PDCP SDU, i.e. IP packet (packet) is adopted for data forwarding.

[0152] In order to better understand the present application, some examples are described below.

[0153] Example 1: L2 higher layer.

[0154] The L2 higher layer involves the functional fusion of the SDAP sublayer, PDCP sublayer, and RLC sublayer.

[0155] First, the SDAP sublayer, which is primarily responsible for mapping QoS flows to DRBs. Generation 4 (4 th The evolution from 4G to 5G communication systems has brought about a change in the granularity of data transmission between the core network and the access network. It has evolved from 4G's EPS bearer to 5G's QoS flow. While 4G's EPS bearer had a one-to-one relationship with the air interface DRB, 5G's QoS flow adopts a finer granularity, essentially further subdividing QoS flows beneath the bearer. Each QoS flow has its own QoS requirements and parameters, providing ample space for the base station. The base station can use its own algorithms to map QoS flows with similar or identical QoS requirements to the same Data Radio Bearer (DRB) for transmission. The introduction of this 5G QoS structure undoubtedly provides base stations with more flexibility, allowing for more optimized and targeted transmission of different QoS flows to achieve a combined optimal user experience and system efficiency.

[0156] However, in the case of extremely narrow bandwidth or extremely simple design, it is equivalent to simplifying the requirements as well. Although the architecture of 5G QoS flow can be maintained or inherited, the number of QoS flows supported at the same time will obviously be greatly limited. There is no need to consider the situation of many QoS flows running concurrently. Bandwidth or device capabilities also limit the number of QoS flows supported at the same time. Therefore, it is advisable to support only one QoS flow or a small number of QoS flows. In semi-static configuration, the one-to-one mapping between QoS flow and DRB can be configured by relying on the RRC process. In this way, different QoS flows can be identified by the DRB identifier, avoiding the use of SDAP header to carry information fields such as QFI.

[0157] In addition, since the downlink does not need to distinguish QoS flows for UE reception, even if there are multiple QoS flows in the downlink, they can be mapped on the same DRB for transmission, further saving overhead and complexity. For uplink transmission, since the N3 interface (user plane interface between the base station and the UPF) needs to distinguish different QoS flows for data forwarding from the base station to the UPF, the base station needs to know which QoS flow the uplink data belongs to. One way is to map different QoS flows to different DRBs, one-to-one mapping. In this way, even if the SDAP header is not carried, the QoS flow can be distinguished by the DRB. This way is the most flexible. For example, a video call can be mapped to three QoS flows / DRBs, corresponding to voice, video and control, with different transmission requirements such as reliability and latency requirements. Another way is to map all IP data streams to the same QoS flow in the core network. In this way, the air interface DRB is also only one, which can further simplify the design of logical channels, etc. But its disadvantage is that it can only support simple IP stream services such as voice or text and cannot be distinguished for transmission. The third way is a variant of the second way, that is, the core network can support multiple QoS flows, but the RAN side maps multiple QoS flows to the same DRB for simplicity, and the RAN node maps the data IP stream to the QoS flow (the mapping rule can be issued by the core network node such as AMF to the base station, or reported by the UE to the base station, or based on the base station implementation, etc.), and sends it to the UPF node in different QoS flows at the N3 interface. This way is the same as the second way, only avoids the limitation of the number of QoS flows in the core network.

[0158] In summary, the header of the SDAP sublayer can be removed in the minimalist L2 design, and the mapping and identification of QoS flows and DRBs can be solved by radio resource control (RRC) semi-static configuration or base station implementation.

[0159] Optionally, the joint design of PDCP and RLC will be the focus of simplification, because the traditional PDCP and RLC have double SN and some redundant functions, and the header overhead of these two layers is the largest in the entire L2.

[0160] The basic design principle is to meet all transmission requirements with the smallest overhead and cost.

[0161] The main functions of PDCP layer are header compression, security operation, and solving the problems of reordering and duplicate detection caused by duplication and split functions. The main functions of RLC are AM and UM mode transmission, segmenting, re-segmenting (AM only), recombining, state feedback, and retransmission (AM only). In the traditional design, PDCP needs SN, and the COUNT value composed of SN is an important input parameter for security operation, and SN is the basis for reordering and duplicate detection. The SN of RLC is mainly used for segmenting and recombining, state feedback, and retransmission.

[0162] A feasible simplification is to combine the functions of PDCP and RLC, for example, to combine them into one layer, named L2 higher layer, or even two sub-layers, but they can flexibly operate with each other. FIG. 6 shows a simple functional and processing flow diagram of L2 higher layer.

[0163] Among them, from the perspective of the sending end, the steps performed include at least one of the following:

[0164] Step 1: The data is stored in the sending buffer, and each data packet can be assigned an SN first. If the pre-cascading function is supported, the SN is assigned again in step 3. The SN is generally incremented in order, and the initial value is 0.

[0165] Step 2: Perform header compression on the data, for example, according to the respective header compression algorithms of IP / Transmission Control Protocol (TCP) / User Datagram Protocol (UDP), and Ethernet Header Compression (EHC), or Uplink Data Compression (UDC), etc., to perform header compression or data compression.

[0166] Step 3: If the pre-cascading function is configured (if not, it can be skipped), that is, the SDU needs to be cascaded first and then security operation is performed to reduce the number of security operations and processing overheads such as complexity, SDU cascading can be performed here, and SN is assigned to the data after cascading.

[0167] Fourth step: integrity protection operation on data, if enabled, otherwise skip, important input parameters include but not limited to (key, bearer ID, direction UL / DL, data unique COUNT value), COUNT value one to one corresponding to SN value of the data, COUNT value 32 bits, split into high bit as hyper frame number (HFN, Hyper Frame Number) (transceiver self-stored), low bit as SN (carried with the package in the air interface package header), for example, 20bit HFN+12bit SN, of course, considering that the data volume is relatively small, and the arrival is not dense, the size of SN can also be reduced as much as possible to reduce the air interface header overhead, for example, 25bit HFN+7bit SN, or 26bit HFN+6bit SN, the length of air interface SN is directly related to the header overhead on the one hand, and also related to the air interface data out of order on the other hand, for example, HARQ different process retransmission causes first arrival and then arrival, late arrival first, or two different path transmission causes out of order, and even RLC AM state feedback and retransmission delay, because the SN length is n bit, the SN space (or range) is [0, 2 n-1 ], the length of the receiving window is generally 2 n-1 , the length of the window needs to be determined according to the maximum out of order situation, so the longer the out of order is, the larger the window needs to be, and the longer the SN length needs to be, generally, the SN size of RLC AM data is larger than that of RLC UM data, and the SN size of the more intensive data package needs to be larger;

[0168] Fifth step: encryption operation on data, if enabled, otherwise skip, encryption parameters are similar to integrity protection, also including (key, bearer ID, direction uplink (UL) / downlink (DL), data unique COUNT value) and the like, SN configuration is also the same as above;

[0169] Sixth step: routing or copy transmission of data package, the purpose of routing is to select the appropriate path when there is more than one path, for example, split is configured, and copy transmission is to copy all data packages and transmit them simultaneously in two or more paths when copy function is enabled; This step is not optional, for satellite transmission or IoT devices, there may be only one path and no copy function is supported; This step can be skipped;

[0170] Seventh step: segment or re-segment (AM only) of data according to the size of transmission resource, to adapt to the size of the resource, and form the corresponding header, add header to data package, and send out;

[0171] It should be noted that high-layer service data packets (SDUs) generally require security operations, thus performing the left-hand operation of SN allocation, integrity protection, and encryption. However, PDCP layer control PDUs or merged RLC control PDUs do not have SNs and do not perform security operations, including retransmission data packets of RLC AMs. The left-hand operation has already been performed the first time, so these data packets can directly enter step six, routing operations. If control PDUs require security operations or certain sequential operations, the control PDUs can also allocate SNs to them or perform the necessary security operations.

[0172] From the receiving end's perspective, the execution steps include at least one of the following:

[0173] Step 1: Differentiate between control PDUs and data PDUs, and process them separately. Control PDUs are processed based on whether they are ROHC feedback, PDCP status report, RLC status report, etc. Data PDUs proceed to the next step. If a control PDU is segmented, steps 2 and 3 are required for reassembly, and segmentation requires a SN. If a control PDU has been allocated a SN, it needs to participate in the reordering stage to avoid incorrect waiting for that SN.

[0174] Step 2: Buffer the data on the receiving side. Optional: Remove the header. If the pre-concatenation function is not configured, the header can be removed here. Otherwise, the header needs to be removed in step 7 later.

[0175] Step 3: If the data is segmented, then reorganize the segmented data;

[0176] Step 4: Decrypt as needed. If encryption is configured, decryption is performed here. Decryption also requires (key, bearer ID, direction UL / DL, unique COUNT value of the data) as input parameters. The COUNT value is composed of the SN carried by the data packet itself and the HFN maintained locally on the receiving side.

[0177] Step 5: Perform integrity verification as needed. If integrity protection is configured, verification is required here. Verification also requires the key, bearer ID, direction UL / DL, and unique COUNT value of the data as input parameters. If the verification is successful, continue with the subsequent operations. If the verification fails, it proves that there is an abnormality in the transmission process and it needs to be reported to the higher layer, such as the RRC layer, and wait for the higher layer or the network side to release, reset, or rebuild the data.

[0178] The sixth step: repeated detection according to the SN value of the data packet, and reordering operation as needed, which is configurable. If configured in order delivery, the data needs to be delivered in ascending order. If configured to be delivered out of order, the data can be delivered in any order without sorting. The important reference for repeated detection and reordering is the SN value. In simple terms, SN repeated data packets are determined to be repeated, and the received repeated data is deleted. Reordering is sorted in ascending order of SN. When a gap appears in the middle, a reordering timer is started. If the gap is filled correctly before the timer expires, the timer is canceled. If the gap is still not filled when the timer expires, the UM data gives up waiting and moves the receive window, while the AM data needs to send an RLC status report and wait for the peer to retransmit;

[0179] The seventh step: if cascading is configured, the data packet is recovered to a single SDU, and the header is removed. The reason why the header of the cascaded data packet can be removed at the seventh step is that the header also contains cascading information for de-cascading.

[0180] The eighth step: header compression, and then deliver to the upper layer.

[0181] Embodiment two: L2 lower layer, which involves the functions of the MAC layer.

[0182] Simplification of the MAC header, mainly in two directions: one is to reduce the type indication length of the logical channel identifier (Logical Channel ID, LCID), and the other is to reduce the L field overhead.

[0183] In the traditional LCID field, the length is 6 bits. In addition to being used to distinguish between 32 DRB IDs, it also defines a lot of MAC CEs, such as downlink control and uplink reporting of various types, and even extends the 1-byte and 2-type length eLCID when the LCID is not enough. In the minimalist design, all of these can be simplified. First, the DRB ID does not need to be 32, but can be a smaller value, such as 1 or 4. Second, the MAC CE does not need to be so many, but only the necessary and appropriate extension bits can be retained, such as reducing the LCID length to 2 bits, 3 bits, or 4 bits; or introducing a D / C field. When data, because there is only one DRB, the L field indication length can be directly carried. When control PDU, there is a further type indication field to distinguish between control and data.

[0184] The traditional L field and F field cooperation is to indicate the length of the MAC subPDU. The F field is 1 bit long, and corresponds to the 1-byte length L field and the 2-byte length L field, respectively, to cope with different packet sizes. In addition, it is stipulated that all MAC SDUs and variable length MAC CEs must carry the L field to indicate the length. In the minimalist design, it can also be reduced. First, the L field does not always exist. There is a high probability that a data packet occupies the entire transmission resource, so a new P (Present) field is introduced to indicate whether there is an L field. In addition, the length of the L field does not need to be very large. It can be RRC configured with a value or a small value, 7 bits or 8 bits or 10 bits, to directly indicate the length of the data packet.

[0185] If there are two layers, MAC layer (or L2 lower layer) and L2 higher layer, respectively design the header, each whole byte arrangement, and the two layers may have reserved (R) bits. If the whole joint design is performed, for example, combined into one layer (which can be called L2 sublayer), the R reserved can be avoided, and the header overhead can be further reduced.

[0186] Embodiment three: configuration, reconfiguration, switching process and different architecture.

[0187] Embodiment one and embodiment two list different minimalist design schemes. These schemes can be independently executed or jointly executed.

[0188] Because there are different terminal types and base station versions in the market or system, even if the ordinary UE and the minimalist UE work in different bandwidths or coexist in the same bandwidth, there may be different UE capability reporting, and different base station capability and version information to support different protocol stack versions. Therefore, a signaling process needs to be introduced to report the related capability and the corresponding configuration process.

[0189] First of all, the minimalist design is definitely for special scenarios or special terminals, so the support of such scenarios and terminals needs the network and UE to intercommunicate the capabilities. In simple terms, one feasible way is for the terminal to report its capability information of supporting at least one of minimalist design 1 (as shown in FIG. 7a) and minimalist design 2 (as shown in FIG. 7b) to the network side device through UE capability reporting in a coexisting system, and the network side device configures according to the need; this way, the UE needs to support multiple protocol stack functions and can be configured for use;

[0190] Or, since the minimalist design and the general protocol stack are completely incompatible, two systems can also be completely independent, that is, system 1 supports general UE access and communication, and system 2 only supports communication of minimalist UEs. Then, the network side device needs to explicitly inform the UEs which version of the protocol stack is indicated. A feasible way is to use explicit signaling in the system message or broadcast message to inform the type of the protocol stack supported by the device. When the minimalist UE obtains that the system supports the minimalist design, it can access and perform data transmission operation according to the protocol stack of the minimalist design. In this way, the UE can only support the minimalist protocol stack design, and it can find the corresponding network to operate.

[0191] After the network side device and the UE obtain consistent information about the protocol stack capabilities supported by each other, the network side device can subsequently configure the UE according to the needs of the minimalist protocol stack. In some embodiments, the capability information sent by the terminal and the network side device can include at least one of the following:

[0192] Target indication information for indicating whether the L2 protocol layer is supported;

[0193] Supported L2 protocol layer;

[0194] Parameter configuration of each layer of the supported L2 protocol layer.

[0195] Optionally, the above parameter configuration can include at least one of the following: SN length; RLC AM or RLC UM; whether to enable perfect protection; whether to enable encryption; length of L field; number of HARQ processes; whether to support HARQ feedback, etc.

[0196] Optionally, the UE obtains the related configuration of the minimalist protocol stack (i.e., the first protocol stack (such as the protocol stack corresponding to the minimalist design 1 shown in FIG. 7a) or the second protocol stack (such as the protocol stack corresponding to the minimalist design 1 shown in FIG. 7b)), and performs the establishment and initialization operation of each layer according to the configuration, and then communicates with the network side device.

[0197] Optionally, the minimalist protocol stack can also be reconfigured, for example, some parameter information is reconfigured or the parameter value is changed. Some parameter changes can be modified in the on-going protocol stack running, and other parameter changes need to be released and added. The initialization protocol stack can apply new parameters. According to the characteristics of the modified parameters, the UE can be instructed to perform different change operations.

[0198] Optionally, in a handover scenario or a transition of a large reconfiguration scenario, typically, such as UE handover between a base station supporting a minimal protocol stack function and another base station not supporting the minimal protocol stack function, or UE handover between a satellite coverage path and a terrestrial network coverage path, since this involves switching or reconfiguration between a minimal protocol stack and a traditional protocol stack, which is a major change, the old protocol stack is generally released and a new protocol stack is re-established, that is, release+add or full-configuration operation, which is a simple operation, but because the state is not maintained, it will cause a certain degree of packet loss and data interruption. If the data forwarding involved in the handover is performed in the traditional PDCP SDU manner, the data forwarding can be performed in the traditional PDCP SDU manner to ensure that both sides can understand correctly and to reduce packet loss to a certain extent.

[0199] In addition, if it is a two-layer L2 architecture, it can still support split bearer, which is applied to scenarios such as dual connectivity (DC) or carrier aggregation (CA), or centralized unit (CU)-distributed unit (DU) split, as shown in FIGS. 7a and 7b.

[0200] Among them, the protocol stack on the terminal side is relatively simple, and the L2 higher layer is divided into two MAC legs, or in the case of CA, it is different carrier processing of one MAC entity. When the transmission resource block of one leg arrives, the corresponding size of data can be sent through the L2 higher layer organization, and when the transmission resource block of the other leg arrives, the corresponding size of data can be sent through the L2 higher layer organization, and the transmission of the two legs can even send different segments of one data. On the receiving side, it is all processed to the L2 higher layer.

[0201] The network side device is relatively complex, and since the two legs can be different sites, the L2 higher layer needs to distribute some data to different legs in advance, and perform segmentation, re-segmentation, final determination, and header addition operations according to their respective scheduling resources.

[0202] Referring to FIG. 8, the embodiment of the present application further provides a data transmission method, as shown in FIG. 8, the data transmission method comprises:

[0203] Step 801, the network side device sends first configuration information to the terminal, the first configuration information is used for configuring a target protocol stack communication mode;

[0204] At step 802, the network-side device performs at least one of a second sending operation and a second receiving operation based on a sequence number (SN) of a data packet in the target protocol stack communication mode.

[0205] The SN is used for a layer 2 (L2) processing operation, the L2 processing operation is a processing operation of a same L2 protocol layer of the L2, the processing operation of the L2 protocol layer includes at least two operation sets, and the operation set includes at least one L2 operation.

[0206] Optionally, the at least two operation sets include a first operation set and a second operation set.

[0207] The first operation set includes at least one L2 operation of the following: identification of segmentation or resegmentation, a data packet reassembly operation, data packet duplication detection, data packet reordering, processing of reception status feedback of a data packet, and performing of reception status feedback of a data packet.

[0208] Or, the second operation set includes at least one L2 operation of the following: a security operation including at least one of integrity protection and encryption, decryption of a data packet, and integrity verification of a data packet.

[0209] Optionally, the at least two operation sets further include at least one of a third operation set and a fourth operation set.

[0210] The third operation set includes at least one L2 operation of the following: mapping between a logical channel and a transport channel, logical channel priority processing, multiplexing or demultiplexing of a medium access control (MAC) service data unit (SDU), scheduling, and hybrid automatic repeat request (HARQ).

[0211] The fourth operation set includes at least one L2 operation of the following: mapping of a quality of service (QoS) flow to a radio bearer, and marking of a QoS flow.

[0212] Optionally, the second sending operation includes:

[0213] The network-side device performs third processing on a fourth data packet to be transmitted in a cache to obtain a third data packet, and the third data packet includes a second SN.

[0214] The network-side device sends the third data packet.

[0215] The third processing includes at least one of the following:

[0216] Header compression is performed on the fourth data packet.

[0217] allocating the second sequence number to the fourth data packet; or, in the case that the network-side device supports a pre-concatenation function, concatenating at least two of the fourth data packets and allocating the second sequence number to the concatenated data packet;

[0218] performing a security operation on the fourth data packet based on the second sequence number, the security operation including at least one of integrity protection and encryption;

[0219] identifying a segment or re-segmenting the fourth data packet based on the second sequence number;

[0220] adding the first packet header to the fourth data packet based on the second sequence number.

[0221] Optionally, the first packet header includes at least one of:

[0222] a first indication field for indicating a data packet type;

[0223] a second indication field for indicating a sequence number;

[0224] a third indication field for indicating a type of control PDU;

[0225] a fourth indication field for indicating a message integrity authentication code;

[0226] a fifth indication field for indicating a segment identification;

[0227] a sixth indication field for indicating a segment offset;

[0228] a seventh indication field for indicating a sub-segment sequence number.

[0229] Optionally, the first packet header further includes at least one of:

[0230] an eighth indication field for indicating whether a ninth indication field exists;

[0231] a ninth indication field for indicating a data length.

[0232] Optionally, the third processing further includes, after adding the first packet header to the fourth data packet, adding a second packet header, the second packet header including at least one of:

[0233] an eighth indication field for indicating whether a ninth indication field exists;

[0234] a ninth indication field for indicating a data length;

[0235] a tenth indication field for indicating a data packet type.

[0236] Optionally, when the target protocol stack communication mode supports split bearer, the third processing is performed before the target bearer corresponding transmission resource block arrives, so as to obtain a size of the target bearer corresponding transmission resource block matching the third data packet.

[0237] Optionally, the second receiving operation comprises:

[0238] The network side device identifies a data packet type of the received second data packet, wherein the data packet type comprises a control protocol data unit (PDU) or a data PDU.

[0239] When the second data packet is a data PDU, the network side device performs fourth processing based on a first SN.

[0240] The first SN is a SN contained in the second data packet, and the fourth processing comprises at least one of the following:

[0241] Decryption of the second data packet based on the first SN;

[0242] Integrity verification of the second data packet based on the first SN;

[0243] Reassembly operation of the second data packet based on the first SN;

[0244] Duplicate detection of the second data packet based on the first SN;

[0245] Reordering of the second data packet based on the first SN;

[0246] Processing of a receiving state feedback of the second data packet based on the first SN.

[0247] Optionally, the fourth processing further comprises any one of the following:

[0248] Deheader operation;

[0249] Deheader operation after deconcatenation of the second data packet.

[0250] Optionally, the method further comprises:

[0251] The network side device sends feedback information based on the first SN to the terminal, wherein the feedback information is used to indicate a receiving state of the second data packet.

[0252] Optionally, the method further comprises:

[0253] The network side device receives capability information from the terminal, wherein the capability information comprises at least one of the following:

[0254] Target indication information, the target indication information being used for indicating whether the L2 protocol layer is supported or not;

[0255] Supported L2 protocol layer;

[0256] Parameter configuration of each layer L2 protocol layer supported.

[0257] Optionally, the first configuration information comprises at least one of the following: L2 protocol layer; parameter configuration of the L2 protocol layer.

[0258] Optionally, the method further comprises:

[0259] The network side device sends second configuration information to the terminal, the second configuration information being used for reconfiguring or switching to a traditional protocol stack communication mode.

[0260] The data transmission method provided in the embodiments of the present application can be executed by a data transmission device. In the embodiments of the present application, the data transmission method executed by the data transmission device is taken as an example to illustrate the data transmission device provided in the embodiments of the present application.

[0261] The embodiments of the present application provide a data transmission device. As an example, the data transmission device can be a communication device or a component in the communication device, such as a chip. The communication device can be a terminal, a network side device, a server or the like. For example, the terminal can include but is not limited to the types of the terminal 11 listed above, the network side device can include but is not limited to the types of the network side device 12 listed above, and the embodiments of the present application are not limited specifically.

[0262] The data transmission apparatus comprises a receiving module, a sending module and a processing module. The receiving module, the sending module and the processing module can be implemented by software or by hardware. When implemented by hardware, the processing module can be implemented by a processor, which can include a general-purpose processor, a special-purpose processor, etc., such as a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), an artificial intelligent (AI) processor, a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a network processor (NP), a field programmable gate array (FPGA) or other programmable logic devices, a gate circuit, a transistor, a discrete hardware component, etc. The receiving module and the sending module can be implemented by a communication interface, which can include one or more of a transceiver, a pin, a circuit, a bus, a radio frequency unit, etc.

[0263] Specifically, referring to FIG. 9, when the data transmission apparatus is a terminal or a component in the terminal, the data transmission apparatus 900 comprises:

[0264] A first transmission module 901 is configured to receive first configuration information from a network-side device, the first configuration information being used to configure a target protocol stack communication mode; and perform at least one of a first sending operation and a first receiving operation based on a sequence number (SN) of a data packet in the target protocol stack communication mode.

[0265] The SN is used to perform a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of the L2, the processing operation of the L2 protocol layer comprising at least two operation sets, and each operation set comprising at least one L2 operation.

[0266] Optionally, the at least two operation sets comprise a first operation set and a second operation set.

[0267] The first operation set comprises at least one L2 operation of the following: identifying segmentation or re-segmentation; data packet reassembly; data packet duplication detection; data packet reordering; processing of data packet reception status feedback; and data packet reception status feedback.

[0268] Or, the second operation set includes at least one L2 operation of: a security operation, the security operation including at least one of integrity protection and encryption; decryption of a data packet; integrity verification of a data packet.

[0269] Optionally, the at least two operation sets further include at least one of a third operation set and a fourth operation set.

[0270] The third operation set includes at least one L2 operation of: mapping between a logical channel and a transport channel; logical channel priority processing; multiplexing or demultiplexing of a media access control (MAC) service data unit (SDU); scheduling; hybrid automatic repeat request (HARQ);

[0271] The fourth operation set includes at least one L2 operation of: mapping of a quality of service (QoS) flow to a radio bearer; marking of a QoS flow.

[0272] Optionally, the first sending operation includes:

[0273] First processing of a first data packet to be transmitted in a buffer, obtaining a second data packet, the second data packet including a first SN;

[0274] Sending the second data packet;

[0275] The first processing includes at least one of:

[0276] Header compression of the first data packet;

[0277] Allocating the first SN to the first data packet; or, in the case where the terminal is configured with a pre-concatenation function, concatenating at least two first data packets and allocating the first SN to the concatenated data packet;

[0278] Security operation on the first data packet based on the first SN, the security operation including at least one of integrity protection and encryption;

[0279] Identifying segmentation or re-segmentation of the first data packet based on the first SN;

[0280] Adding a first packet header to the first data packet based on the first SN.

[0281] Optionally, the first packet header includes at least one of:

[0282] A first indication field for indicating a data packet type;

[0283] A second indication field for indicating a sequence number;

[0284] A third indication field for indicating a type of control PDU;

[0285] a fourth indication field, used for indicating a message integrity authentication code;

[0286] a fifth indication field, used for indicating a segment identifier;

[0287] a sixth indication field, used for indicating a segment offset;

[0288] a seventh indication field, used for indicating a sub-segment serial number.

[0289] Optionally, the first packet header further comprises at least one of the following:

[0290] an eighth indication field, used for indicating whether a ninth indication field exists;

[0291] the ninth indication field, used for indicating a data length.

[0292] Optionally, the first processing further comprises: after adding the first packet header to the first data packet, adding a second packet header, the second packet header comprising at least one of the following:

[0293] the eighth indication field, used for indicating whether the ninth indication field exists;

[0294] the ninth indication field, used for indicating the data length;

[0295] a tenth indication field, used for indicating a data packet type.

[0296] Optionally, in the case that the target protocol stack communication mode supports split bearing, when a target bearing corresponding transmission resource block arrives, the first processing is performed to obtain a size of the target bearing corresponding transmission resource block matching the second data packet.

[0297] Optionally, the first receiving operation comprises:

[0298] identifying a data packet type of the received third data packet, the data packet type comprising a control protocol data unit (PDU) or a data PDU;

[0299] in the case that the third data packet is a data PDU, performing a second processing based on a second SN;

[0300] wherein the second SN is a SN contained in the third data packet, and the second processing comprises at least one of the following:

[0301] decrypting the third data packet based on the second SN;

[0302] performing integrity verification on the third data packet based on the second SN;

[0303] performing recombination operation on the third data packet based on the second SN;

[0304] performing repeated detection on the third data packet based on the second SN;

[0305] performing reordering on the third data packet based on the second SN;

[0306] performing receiving status feedback of the third data packet based on the second SN.

[0307] Optionally, the second processing further includes any one of the following:

[0308] performing a de-header operation;

[0309] performing a de-header operation after de-cascading the third data packet.

[0310] Optionally, the first transmission module 901 is further configured to send feedback information to the network side device based on the second SN, wherein the feedback information is used to indicate the receiving status of the third data packet.

[0311] Optionally, the first transmission module 901 is further configured to send capability information to the network side device, wherein the capability information includes at least one of the following:

[0312] target indication information, wherein the target indication information is used to indicate whether the L2 protocol layer is supported;

[0313] the supported L2 protocol layer;

[0314] a parameter configuration of each supported L2 protocol layer.

[0315] Optionally, the first configuration information includes at least one of the following: an L2 protocol layer; and a parameter configuration of the L2 protocol layer.

[0316] Optionally, the first transmission module 901 is further configured to receive second configuration information from the network side device, wherein the second configuration information is used to reconfigure or switch to a traditional protocol stack communication mode.

[0317] Optionally, the first transmission module 901 is further configured to, when there is data forwarding of switching, perform data forwarding by using a packet data convergence protocol service data unit (PDCP SDU) in a traditional protocol stack.

[0318] Referring to FIG. 10, when the data transmission apparatus is a network side device or a component in the network side device, the data transmission apparatus 1000 includes:

[0319] The second transmission module 1001 is configured to send first configuration information to a terminal, the first configuration information being used for configuring a target protocol stack communication mode; and perform at least one of a second sending operation and a second receiving operation based on a sequence number (SN) of a data packet in the target protocol stack communication mode.

[0320] The SN is used for performing a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of the L2, the processing operation of the L2 protocol layer including at least two operation sets, and the operation set including at least one L2 operation.

[0321] Optionally, the at least two operation sets include a first operation set and a second operation set.

[0322] The first operation set includes at least one L2 operation of the following: identifying segmentation or re-segmentation; a data packet reassembly operation; data packet duplication detection; data packet reordering; processing of a reception status feedback of a data packet; and performing a reception status feedback of a data packet.

[0323] Or, the second operation set includes at least one L2 operation of the following: a security operation including at least one of integrity protection and encryption; data packet decryption; and data packet integrity verification.

[0324] Optionally, the at least two operation sets further include at least one of a third operation set and a fourth operation set.

[0325] The third operation set includes at least one L2 operation of the following: mapping between a logical channel and a transport channel; logical channel priority processing; multiplexing or demultiplexing of a medium access control (MAC) service data unit (SDU); scheduling; and hybrid automatic repeat request (HARQ).

[0326] The fourth operation set includes at least one L2 operation of the following: mapping of a quality of service (QoS) flow to a radio bearer; and marking of a QoS flow.

[0327] Optionally, the second sending operation includes:

[0328] performing third processing on a fourth data packet to be transmitted in a buffer to obtain a third data packet, the third data packet including a second SN; and sending the third data packet.

[0329] The third processing includes at least one of the following:

[0330] performing header compression on the fourth data packet.

[0331] allocating the second sequence number to the fourth data packet; or, in the case that the terminal is configured with a pre-concatenation function, concatenating at least two of the fourth data packets and allocating the second sequence number to the concatenated data packet;

[0332] performing a security operation on the fourth data packet based on the second sequence number, the security operation comprising at least one of integrity protection and encryption;

[0333] identifying segmenting or re-segmenting the fourth data packet based on the second sequence number;

[0334] adding the first packet header to the fourth data packet based on the second sequence number.

[0335] Optionally, the first packet header comprises at least one of:

[0336] a first indication field for indicating a data packet type;

[0337] a second indication field for indicating a sequence number;

[0338] a third indication field for indicating a type of control PDU;

[0339] a fourth indication field for indicating a message integrity authentication code;

[0340] a fifth indication field for indicating a segment identification;

[0341] a sixth indication field for indicating a segment offset;

[0342] a seventh indication field for indicating a sub-segment sequence number.

[0343] Optionally, the first packet header further comprises at least one of:

[0344] an eighth indication field for indicating whether a ninth indication field exists;

[0345] a ninth indication field for indicating a data length.

[0346] Optionally, the third processing further comprises, after adding the first packet header to the fourth data packet, adding a second packet header, the second packet header comprising at least one of:

[0347] an eighth indication field for indicating whether a ninth indication field exists;

[0348] a ninth indication field for indicating a data length;

[0349] a tenth indication field for indicating a data packet type.

[0350] Optionally, when the target protocol stack communication mode supports split bearer, the third processing is performed before the target bearer corresponding transmission resource block arrives, so as to obtain a size of the target bearer corresponding transmission resource block matching the third data packet.

[0351] Optionally, the second receiving operation comprises:

[0352] identifying a data packet type of the received second data packet, the data packet type comprising a control protocol data unit (PDU) or a data PDU;

[0353] when the second data packet is a data PDU, performing fourth processing based on a first SN;

[0354] wherein the first SN is a SN contained in the second data packet, and the fourth processing comprises at least one of:

[0355] decrypting the second data packet based on the first SN;

[0356] performing integrity verification on the second data packet based on the first SN;

[0357] performing reassembly operation on the second data packet based on the first SN;

[0358] performing duplicate detection on the second data packet based on the first SN;

[0359] performing reordering on the second data packet based on the first SN;

[0360] processing a receiving state feedback of the second data packet based on the first SN.

[0361] Optionally, the fourth processing further comprises any one of:

[0362] performing deheader operation;

[0363] performing deheader operation after de-cascading the second data packet.

[0364] Optionally, the second transmission module 1001 is further configured to send feedback information to the terminal based on the first SN, wherein the feedback information is used to indicate a receiving state of the second data packet.

[0365] Optionally, the second transmission module 1001 is further configured to receive capability information from the terminal, wherein the capability information comprises at least one of:

[0366] target indication information, wherein the target indication information is used to indicate whether L2 protocol layer is supported;

[0367] supported L2 protocol layer.

[0368] a parameter configuration of each supported L2 protocol layer.

[0369] Optionally, the first configuration information comprises at least one of the following: an L2 protocol layer; and a parameter configuration of the L2 protocol layer.

[0370] Optionally, the second transmission module 1001 is further configured to send second configuration information to the terminal, the second configuration information being used to reconfigure or switch to a legacy protocol stack communication mode.

[0371] Optionally, the second transmission module 1001 is further configured to, when there is data forwarding of switching, perform data forwarding in a manner of a packet data convergence protocol service data unit (PDCP SDU) in a legacy protocol stack.

[0372] The data transmission apparatus provided by the embodiments of the present application can implement each process of the method embodiments of FIG. 4 or 8, and achieve the same technical effects. To avoid repetition, details are not described herein.

[0373] As shown in FIG. 11, the embodiments of the present application further provide a communication device 1100, which comprises a processor 1101 and a memory 1102, and the memory 1102 stores programs or instructions executable on the processor 1101. When the programs or instructions are executed by the processor 1101, each step of the above data transmission method embodiments is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described herein.

[0374] The embodiments of the present application further provide a terminal, which comprises a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run programs or instructions to implement the steps in the method embodiments shown in FIG. 4. The terminal embodiments correspond to the above terminal-side method embodiments, and each implementation process and implementation manner of the above method embodiments can be applied to the terminal embodiments, and the same technical effects can be achieved. The terminal can be the data transmission apparatus shown in FIG. 9. Specifically, FIG. 12 is a schematic diagram of a hardware structure of a terminal according to an embodiment of the present application.

[0375] The terminal 1200 includes, but is not limited to, at least part of the following components: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209, and a processor 1210, etc.

[0376] Those skilled in the art can understand that the terminal 1200 can further include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1210 through a power management system, so that the power management system can realize the functions of managing charging, discharging and power consumption management. The terminal structure shown in FIG. 12 does not constitute a limitation on the terminal, and the terminal can include more or fewer components than those shown, or combine certain components, or different component arrangements, which are not described here.

[0377] It should be understood that in the embodiments of the present application, the input unit 1204 can include a graphics processor 12041 and a microphone 12042. The graphics processor 12041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1206 can include a display panel 12061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 1207 includes at least one of a touch panel 12071 and other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 can include two parts of a touch detection device and a touch controller. The other input devices 12072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), trackballs, mice, joysticks, which are not described here.

[0378] In the embodiments of the present application, after the radio frequency unit 1201 receives the downlink data from the network side device, it can be transmitted to the processor 1210 for processing. In addition, the radio frequency unit 1201 can send uplink data to the network side device. Generally, the radio frequency unit 1201 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0379] The memory 1209 can be used to store software programs or instructions and various data. The memory 1209 can mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.), and the like. In addition, the memory 1209 can include a volatile memory or a non-volatile memory. The non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 1209 in the embodiments of the present application includes but is not limited to these and any other suitable type of memory.

[0380] The processor 1210 can include one or more processing units; optionally, the processor 1210 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and an application program, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 1210.

[0381] The radio frequency unit 1201 is configured to receive first configuration information from a network side device, wherein the first configuration information is used to configure a target protocol stack communication mode; and perform at least one of a first sending operation and a first receiving operation based on a sequence number (SN) of a data packet in the target protocol stack communication mode.

[0382] The SN is configured to perform a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of the L2, the processing operation of the L2 protocol layer including at least two operation sets, the operation sets including at least one L2 operation.

[0383] It can be understood that the implementation processes of the implementation manners mentioned in the embodiments can refer to the related descriptions of the terminal side method embodiments and achieve the same or corresponding technical effects. To avoid repetition, they will not be described here again.

[0384] The embodiments of the present application also provide a network side device, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is configured to run programs or instructions to implement the steps of the method embodiments shown in FIG. 8. The network side device embodiments correspond to the network side device method embodiments described above. The various implementation processes and implementation manners of the method embodiments described above can be applied to the network side device embodiments and achieve the same technical effects.

[0385] Specifically, the embodiments of the present application also provide a network side device, which can be a data transmission apparatus shown in FIG. 10. As shown in FIG. 13, the network side device 1300 includes an antenna 1301, a radio frequency device 1302, a baseband device 1303, a processor 1304 and a memory 1305. The antenna 1301 is connected with the radio frequency device 1302. In the uplink direction, the radio frequency device 1302 receives information through the antenna 1301 and sends the received information to the baseband device 1303 for processing. In the downlink direction, the baseband device 1303 processes the information to be sent and sends it to the radio frequency device 1302. The radio frequency device 1302 processes the received information and sends it out through the antenna 1301.

[0386] The method performed by the network side device in the above embodiments can be implemented in the baseband device 1303, which includes a baseband processor.

[0387] The baseband device 1303 may, for example, include at least one baseband board on which a plurality of chips are arranged, as shown in FIG. 13. One of the chips is, for example, a baseband processor connected with the memory 1305 through a bus interface to call programs in the memory 1305 and perform the network side device operations shown in the above method embodiments.

[0388] The network side device may, for example, also include a network interface 1306, which is, for example, a common public radio interface (CPRI).

[0389] Specifically, the network side device 1300 in the embodiments of the present application further includes instructions or programs stored in the storage 1305 and executable on the processor 1304, the processor 1304 invokes the instructions or programs in the storage 1305 to perform the method executed by each module shown in FIG. 10 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0390] The embodiments of the present application further provide a readable storage medium, which stores programs or instructions, and the programs or instructions are executed by a processor to implement each process of the above-mentioned data transmission method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein.

[0391] The processor is the processor in the terminal in the above-mentioned embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (ROM), a random access memory (RAM), a magnetic disc or an optical disc, etc. In some examples, the readable storage medium can be a non-transient readable storage medium.

[0392] The embodiments of the present application further provide a chip, which includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run programs or instructions to implement each process of the above-mentioned data transmission method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein.

[0393] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system chip, a system on chip, a chip system or a system on chip, etc.

[0394] The embodiments of the present application further provide a computer program / program product, which includes computer instructions, and the computer program / program product is executed by at least one processor to implement each process of the above-mentioned data transmission method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein.

[0395] The embodiments of the present application further provide a wireless communication system, which includes a terminal and a network side device, the terminal can be used to execute the steps of the above-mentioned data transmission method, and the network side device can be used to execute the steps of the above-mentioned data transmission method.

[0396] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises a", "comprising", or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the methods and apparatuses of the present application can be carried out by specific hardware, by software, or by a combination of hardware and software. It is therefore, contemplated to this patent to cover any and all modifications, variations, or equivalents that fall within the scope of the present application. Accordingly, where a concept can have been illustrated in only one of the exemplary embodiments, various aspects of the concept can be modified and / or combined to produce a variety of other embodiments that are not specifically illustrated. Thus, for purposes of describing particular embodiments, reference has been made to orientations. However, it should be understood that the described embodiments can be carried out in other orientations than those explicitly described without departing from the scope of the present application.

[0397] From the above description of the embodiments, it is apparent that the above-mentioned method can be realized by means of a computer software product and a general hardware platform, of course, it can also be realized by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disc, optical disc, etc.), and includes a plurality of instructions for making the terminal or network side device execute the method described in each embodiment of the present application.

[0398] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, the above-mentioned specific embodiments are only illustrative, but not restrictive, and those skilled in the art can make many forms of embodiments under the inspiration of the present application without departing from the scope of the present application and the protection scope of the claims.

Claims

1. A data transmission method, comprising: receiving, by a terminal, first configuration information from a network side device, the first configuration information being used to configure a target protocol stack communication mode; performing, by the terminal, at least one of a first sending operation and a first receiving operation based on a sequence number (SN) of a data packet in the target protocol stack communication mode; wherein the SN is used for a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer comprising at least two operation sets, the operation set comprising at least one L2 operation.

2. The method of claim 1, wherein, the at least two operation sets comprising a first operation set and a second operation set; the first operation set comprising at least one L2 operation of: identifying segmentation or re-segmentation; data packet reassembly operation; data packet duplication detection; data packet reordering; processing reception status feedback of the data packet; performing reception status feedback of the data packet; or, the second operation set comprising at least one L2 operation of: security operation, the security operation comprising at least one of integrity protection and encryption; data packet decryption; data packet integrity verification.

3. The method of claim 1 or 2, wherein, the at least two operation sets further comprising at least one of a third operation set and a fourth operation set; the third operation set comprising at least one L2 operation of: mapping between a logical channel and a transport channel; logical channel priority processing; multiplexing or demultiplexing of a medium access control (MAC) service data unit (SDU); scheduling; hybrid automatic repeat request (HARQ); the fourth operation set comprising at least one L2 operation of: mapping of a quality of service (QoS) flow to a radio bearer; marking a QoS flow.

4. The method according to any one of claims 1 to 3, wherein, the first sending operation comprising: performing, by the terminal, first processing on a first data packet to be transmitted in a buffer to obtain a second data packet, the second data packet comprising a first SN; sending, by the terminal, the second data packet; wherein the first processing comprises at least one of: performing header compression on the first data packet; allocating the first SN to the first data packet; or, in a case where the terminal is configured with a pre-concatenation function, concatenating at least two first data packets and allocating the first SN to the concatenated data packet; performing security operation on the first data packet based on the first SN, the security operation comprising at least one of integrity protection and encryption; identifying segmentation or re-segmentation of the first data packet based on the first SN; adding a first packet header to the first data packet based on the first SN.

5. The method of claim 4, wherein, the first packet header comprising at least one of: a first indication field used to indicate a data packet type; a second indication field used to indicate a sequence number; a third indication field used to indicate a type of control PDU; a fourth indication field used to indicate a message integrity authentication code; a fifth indication field used to indicate a segmentation identifier; a sixth indication field used to indicate a segmentation offset; a seventh indication field used to indicate a sub-segmentation sequence number.

6. The method of claim 5, wherein, the first packet header further comprising at least one of: an eighth indication field used to indicate whether a ninth indication field exists; the ninth indication field used to indicate a data length.

7. The method of claim 4 or 5, wherein, The first processing further comprises: adding a second packet header after adding the first packet header, the second packet header comprising at least one of the following: an eighth indication field, used to indicate whether a ninth indication field exists; a ninth indication field, used to indicate a data length; a tenth indication field, used to indicate a data packet type.

8. The method of claim 4 or 7, wherein, In a case where the target protocol stack communication mode supports split bearer, when a target bearer corresponding transport resource block arrives, the first processing is performed to obtain a size of the target bearer corresponding transport resource block matching the second data packet.

9. The method according to any one of claims 1 to 8, wherein, The first receiving operation comprises: The terminal identifies a data packet type of the received third data packet, the data packet type comprising a control protocol data unit (PDU) or a data PDU; In a case where the third data packet is a data PDU, the terminal performs a second processing based on a second SN; The second SN is a SN contained in the third data packet, and the second processing comprises at least one of the following: decrypting the third data packet based on the second SN; performing integrity verification on the third data packet based on the second SN; performing a reassembly operation on the third data packet based on the second SN; performing duplicate detection on the third data packet based on the second SN; performing reordering on the third data packet based on the second SN; performing reception status feedback of the third data packet based on the second SN.

10. The method of claim 9, wherein, The second processing further comprises any one of the following: performing a deheader operation; performing a deheader operation after deconcatenating the third data packet.

11. The method according to any one of claims 1 to 10, wherein, The method further comprises: The terminal sends capability information to a network side device, the capability information comprising at least one of the following: target indication information, used to indicate whether the L2 protocol layer is supported; supported L2 protocol layers; parameter configurations of each layer L2 protocol layer supported.

12. The method according to any one of claims 1 to 11, wherein, The first configuration information comprises at least one of the following: an L2 protocol layer; and a parameter configuration of the L2 protocol layer.

13. The method of any one of claims 1 to 12, wherein, The method further comprises: The terminal receives second configuration information from a network side device, the second configuration information being used to reconfigure or switch to a traditional protocol stack communication mode.

14. The method of claim 13, wherein, After the terminal receives the second configuration information from the network side device, the method further comprises: In a case where data forwarding exists after switching, the terminal performs data forwarding in a manner of a packet data convergence protocol (PDCP) service data unit (SDU) in a traditional protocol stack.

15. A data transmission method, comprising: a network side device sending first configuration information to a terminal, the first configuration information being used to configure a target protocol stack communication mode; under the target protocol stack communication mode, the network side device performing at least one of a second sending operation and a second receiving operation based on a sequence number (SN) of a data packet; The SN is used to perform a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer comprising at least two operation sets, and the operation set comprising at least one L2 operation.

16. The method of claim 14 or 15, wherein, The at least two operation sets comprise a first operation set and a second operation set; The first operation set comprises at least one L2 operation of the following: segment identification or re-segmentation; packet reassembly operation; packet duplication detection; packet reordering; processing of reception status feedback of a packet; performing reception status feedback of a packet; Or, the second operation set comprises at least one L2 operation of the following: security operation, the security operation comprising at least one of integrity protection and encryption; decryption of a packet; integrity verification of a packet.

17. The method of claim 16, wherein, The at least two operation sets further comprise at least one of a third operation set and a fourth operation set; The third operation set comprises at least one L2 operation of the following: mapping between a logical channel and a transport channel; logical channel priority processing; multiplexing or demultiplexing of a medium access control (MAC) service data unit (SDU); scheduling; hybrid automatic repeat request (HARQ); The fourth operation set comprises at least one L2 operation of the following: mapping of a quality of service (QoS) flow to a radio bearer; marking of a QoS flow.

18. The method of any one of claims 15 to 17, wherein, The second sending operation comprises: The network-side device performs third processing on the fourth data packets in the buffer to obtain third data packets, the third data packets comprising a second sequence number; The network-side device sends the third data packets; The third processing comprises at least one of the following: Header compression on the fourth data packets; Allocation of the second sequence number to the fourth data packets; or, in the case that the network-side device supports pre-concatenation, concatenation of at least two of the fourth data packets and allocation of the second sequence number to the concatenated data packets; Security operation on the fourth data packets based on the second sequence number, the security operation comprising at least one of integrity protection and encryption; Segment identification or re-segmentation of the fourth data packets based on the second sequence number; Addition of a first packet header to the fourth data packets based on the second sequence number.

19. The method of claim 18, wherein, The first packet header comprises at least one of the following: A first indication field for indicating a packet type; A second indication field for indicating a sequence number; A third indication field for indicating a type of control PDU; A fourth indication field for indicating a message integrity authentication code; A fifth indication field for indicating a segment identification; A sixth indication field for indicating a segment offset; A seventh indication field for indicating a sub-segment sequence number.

20. The method of claim 18, wherein, The first packet header further comprises at least one of the following: An eighth indication field for indicating whether a ninth indication field exists; A ninth indication field for indicating a data length.

21. The method of claim 18 or 19, wherein, The third processing further comprises, after adding the first packet header to the fourth data packets, adding a second packet header, the second packet header comprising at least one of the following: An eighth indication field for indicating whether a ninth indication field exists; A ninth indication field for indicating a data length; A tenth indication field for indicating a packet type.

22. The method of claim 18 or 21, wherein, In the case that the target protocol stack communication mode supports split bearers, the third processing is performed before the arrival of a transmission resource block corresponding to a target bearer, to obtain a third data packet whose size matches that of the transmission resource block corresponding to the target bearer.

23. The method of any one of claims 15 to 22, wherein, The second receiving operation comprises: The network-side device identifies a data packet type of the received second data packet, the data packet type including a control protocol data unit (PDU) or a data PDU; In a case where the second data packet is a data PDU, the network-side device performs fourth processing based on a first SN; The first SN is a SN included in the second data packet, and the fourth processing includes at least one of the following: decrypting the second data packet based on the first SN; performing integrity verification on the second data packet based on the first SN; performing reassembly operation on the second data packet based on the first SN; performing repetition detection on the second data packet based on the first SN; performing reordering on the second data packet based on the first SN; processing a receiving status feedback of the second data packet based on the first SN.

24. The method of claim 23, wherein, The fourth processing further includes any one of the following: performing deheader operation; performing deheader operation after deconcatenating the second data packet.

25. The method of any one of claims 15 to 24, wherein, The method further includes: The network-side device receives capability information from the terminal, and the capability information includes at least one of the following: target indication information, the target indication information being used to indicate whether L2 protocol layer is supported; supported L2 protocol layer; parameter configuration of each L2 protocol layer supported.

26. The method of any one of claims 15 to 25, wherein, The first configuration information includes at least one of the following: L2 protocol layer; and parameter configuration of L2 protocol layer.

27. The method of any one of claims 15 to 26, wherein, The method further includes: The network-side device sends second configuration information to the terminal, the second configuration information being used to reconfigure or switch to a traditional protocol stack communication mode.

28. The method of claim 27, wherein, After the network-side device sends the second configuration information to the terminal, the method further includes: When there is data forwarding of switching, the network-side device performs data forwarding in a manner of packet data convergence protocol (PDCP) service data unit (SDU) in the traditional protocol stack.

29. A data transmission apparatus, comprising: a first transmission module configured to receive first configuration information from a network-side device, the first configuration information being used to configure a target protocol stack communication mode; under the target protocol stack communication mode, performing at least one of first sending operation and first receiving operation based on a sequence number (SN) of a data packet; The SN is used for layer 2 (L2) processing operation, the L2 processing operation is processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer includes at least two operation sets, and the operation set includes at least one L2 operation.

30. The apparatus of claim 29, wherein, The first sending operation includes: performing first processing on a first data packet to be transmitted in a buffer to obtain a second data packet, the second data packet including a first SN; sending the second data packet; The first processing includes at least one of the following: header compression on the first data packet; allocating the first SN to the first data packet; or, in a case where a terminal is configured with pre-concatenation function, concatenating at least two first data packets and allocating the first SN to the concatenated data packet; performing a security operation on the first data packet based on the first SN, the security operation comprising at least one of integrity protection and encryption; identifying segmenting or re-segmenting the first data packet based on the first SN; adding a first packet header to the first data packet based on the first SN.

31. The apparatus of claim 29 or 30, wherein, The first receiving operation comprises: identifying a data packet type of a received third data packet, the data packet type comprising a control protocol data unit (PDU) or a data PDU; in a case where the third data packet is a data PDU, performing a second processing based on a second SN; wherein the second SN is a SN contained in the third data packet, and the second processing comprises at least one of: decrypting the third data packet based on the second SN; performing integrity verification on the third data packet based on the second SN; performing reassembly operation on the third data packet based on the second SN; performing duplicate detection on the third data packet based on the second SN; performing reordering on the third data packet based on the second SN; performing reception status feedback of the third data packet based on the second SN.

32. A data transmission apparatus, comprising: a second transmission module configured to send first configuration information to a terminal, the first configuration information being used to configure a target protocol stack communication mode; in the target protocol stack communication mode, performing at least one of a second transmission operation and a second receiving operation based on a sequence number (SN) of a data packet; wherein the SN is used to perform a layer 2 (L2) processing operation, the L2 processing operation being a processing operation of a same L2 protocol layer of L2, the processing operation of the L2 protocol layer comprising at least two operation sets, and each operation set comprising at least one L2 operation.

33. The apparatus of claim 32, wherein, The second transmission operation comprises: performing a third processing on a fourth data packet to be transmitted in a buffer to obtain a third data packet, the third data packet comprising a second SN; and transmitting the third data packet; wherein the third processing comprises at least one of: performing header compression on the fourth data packet; allocating the second SN to the fourth data packet; or, in a case where the terminal is configured with a pre-concatenation function, concatenating at least two fourth data packets and allocating the second SN to the concatenated data packet; performing a security operation on the fourth data packet based on the second SN, the security operation comprising at least one of integrity protection and encryption; identifying segmenting or re-segmenting the fourth data packet based on the second SN; adding the first packet header to the fourth data packet based on the second SN.

34. The apparatus of claim 32 or 33, wherein, The second receiving operation comprises: identifying a data packet type of a received second data packet, the data packet type comprising a control protocol data unit (PDU) or a data PDU; in a case where the second data packet is a data PDU, performing a fourth processing based on a first SN; wherein the first SN is a SN contained in the second data packet, and the fourth processing comprises at least one of: decrypting the second data packet based on the first SN; performing integrity verification on the second data packet based on the first SN; performing reassembly operation on the second data packet based on the first SN; performing duplicate detection on the second data packet based on the first SN; performing reordering on the second data packet based on the first SN; handling reception status feedback of the second data packet based on the first SN. 35.A terminal comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement steps of the data transmission method according to any one of claims 1 to 14. 36.A network side device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement steps of the data transmission method according to any one of claims 15 to 28. 37.A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions, when executed by a processor, implement steps of the data transmission method according to any one of claims 1 to 28. 38.A computer program product comprising computer instructions, the computer instructions, when executed by a processor, implement steps of the data transmission method according to any one of claims 1 to 28.

Images