Data packet transmission method and device, terminal and network side equipment

Abstract

The invention discloses a data packet transmission method and device, a terminal and network side equipment, and belongs to the technical field of communication, the data packet transmission method comprises the steps that the terminal executes a first operation, and the first operation comprises at least one of the following items: sending a first data packet based on a transparent mode TM, the first data packet is a data packet which does not need segmented transmission; and receiving a second data packet based on the TM, wherein the second data packet is a data packet which does not need segmented transmission.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a data packet transmission method, device, terminal and network side equipment. Background Art

[0002] In the related art, since the Radio Link Control (RLC) Acknowledged Mode (AM) transmission mode and the RLC Unacknowledged Mode (UM) transmission mode can generate a transmission block of appropriate size according to the size of the transmission resource block through segment cascading and other methods, the Data Radio Bearer (DRB) only supports two transmission modes, RLC AM and RLC UM. However, when using the RLC AM or RLC UM transmission mode to transmit data packets, it is necessary to add a header to each data packet, resulting in a large header overhead. Summary of the invention

[0003] The embodiments of the present application provide a data packet transmission method, apparatus, terminal and network-side equipment, which can solve the problem of large header overhead.

[0004] In a first aspect, a method for transmitting a data packet is provided, comprising:

[0005] The terminal performs a first operation, where the first operation includes at least one of the following:

[0006] Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments;

[0007] A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

[0008] In a second aspect, a data packet transmission method is provided, comprising:

[0009] The network-side device performs a second operation, where the second operation includes at least one of the following:

[0010] Sending a second data packet based on the transparent mode TM, where the second data packet is a data packet that does not need to be transmitted in segments;

[0011] A first data packet is received based on the TM, where the first data packet is a data packet that does not need to be transmitted in segments.

[0012] According to a third aspect, a data packet transmission device is provided. The terminal includes the data packet transmission device. The device includes:

[0013] The first execution module is configured to execute a first operation, wherein the first operation includes at least one of the following:

[0014] Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments;

[0015] A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

[0016] In a fourth aspect, a data packet transmission device is provided, wherein a network side device includes the data packet transmission device, and the device includes:

[0017] The second execution module is configured to execute a second operation, where the second operation includes at least one of the following:

[0018] Sending a second data packet based on the transparent mode TM, where the second data packet is a data packet that does not need to be transmitted in segments;

[0019] A first data packet is received based on the TM, where the first data packet is a data packet that does not need to be transmitted in segments.

[0020] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0021] In a sixth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0022] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to:

[0023] Perform a first operation, where the first operation includes at least one of the following:

[0024] Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments;

[0025] A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

[0026] In an eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the processor is used to:

[0027] Perform a second operation, where the second operation includes at least one of the following:

[0028] Sending a second data packet based on the transparent mode TM, where the second data packet is a data packet that does not need to be transmitted in segments;

[0029] A first data packet is received based on the TM, where the first data packet is a data packet that does not need to be transmitted in segments.

[0030] In a ninth aspect, a data packet transmission system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0031] In the tenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0032] In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0033] In the twelfth aspect, a computer program / program product is provided, wherein 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 described in the first aspect, or to implement the steps of the method described in the second aspect.

[0034] In the embodiment of the present application, the terminal performs a first operation, and the first operation includes at least one of the following: sending a first data packet based on the transparent mode TM, the first data packet is a data packet that does not need to be transmitted in segments; receiving a second data packet based on the TM, the second data packet is a data packet that does not need to be transmitted in segments. In this way, by receiving or sending a data packet that does not need to be transmitted in segments through the TM, there is no need to add a header to the data packet that does not need to be transmitted in segments, which can reduce header overhead and improve data transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0036] Figure 2 It is a schematic diagram of a user plane protocol stack in the related art;

[0037] Figure 3 It is a schematic diagram of an uplink L2 architecture in the related art;

[0038] Figure 4 It is a L2 data flow diagram in the related art;

[0039] Figure 5 This is one of the flow charts of a data packet transmission method provided in an embodiment of the present application;

[0040] Figure 6 This is the second flowchart of a data packet transmission method provided in an embodiment of the present application;

[0041] Figure 7 This is one of the data transmission schematic diagrams provided in the embodiments of the present application;

[0042] Figure 8 This is a second data transmission schematic diagram provided in an embodiment of the present application;

[0043] Fig. 9 This is one of the schematic diagrams of a UM PDU structure provided in an embodiment of the present application;

[0044] Fig.10 This is a second schematic diagram of a UM PDU structure provided in an embodiment of the present application;

[0045] Fig.11 This is a third data transmission schematic diagram provided in an embodiment of the present application;

[0046] Fig.12 This is one of the structural schematic diagrams of a data packet transmission device provided in an embodiment of the present application;

[0047] Fig.13 This is a second structural diagram of a data packet transmission device provided in an embodiment of the present application;

[0048] Fig.14 It is a structural diagram of a communication device provided in an embodiment of the present application;

[0049] Fig.15 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0050] Fig.16 It is a structural diagram of a network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0052] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, but not to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "or" in the specification and claims represents at least one of the connected objects, for example: "A or B" covers three schemes, namely, scheme one: including A but not including B; scheme two: including B but not including A; scheme three: including both A and B. The term "indication" in the specification and claims of the present application can be either an explicit indication or an implicit indication. Among them, an explicit indication can be understood as the sender explicitly notifying the receiver of the operation or request result to be performed in the indication sent; an implicit indication can be understood as the receiver making a judgment based on the indication sent by the sender and determining the operation or request result to be performed based on the judgment result.

[0053] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, 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) and 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 for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0054] Figure 1A block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), augmented reality (augmentedreality, AR) / virtual reality (virtual reality, VR) equipment, a robot, a wearable device (WearableDevice), a vehicle-mounted equipment (VUE), a pedestrian terminal (PUE), a smart home (home equipment with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (personal computer, PC), a teller machine or a self-service machine and other terminal side devices, and the wearable device includes: a smart watch, a smart bracelet, a smart headset, a smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), a smart wristband, a smart clothing, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (RAN), a radio access network function or a radio access network unit. The access network device 12 may include a base station, a WLAN access point or a WiFi node, etc. The base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home B node, a home evolved B node, a transmitting and receiving point (TRP) or other appropriate terms in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary, it should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0055] For ease of understanding, some contents involved in the embodiments of the present application are described below:

[0056] 1. Data processing in the user plane

[0057] In the existing NR network, the user plane protocol stack mainly includes medium access control (MAC), RLC, packet data convergence protocol (PDCP), service data adaptation protocol (SDAP) and physical layer (PHY), such as Figure 2 shown.

[0058] Among them, except PHY which is the L1 protocol stack, the other four layers of protocols constitute the L2 protocol stack. Figure 3 As shown, the MAC layer is mainly responsible for the mapping between logical channels and transport channels, logical channel priority processing, multiplexing and demultiplexing of MAC service data units (SDUs), scheduling and hybrid automatic repeat request (HARQ) operations, etc. The RLC layer provides functions such as data transmission in multiple modes, segmentation and reassembly, automatic repeat request (ARQ), independent sequence number, etc. The PDCP layer provides functions such as header compression and decompression, security operations, separate bearer routing and replication, etc. The SDAP layer provides functions such as mapping of Quality of Service (QoS) flows to radio bearers, marking QoS flow identifiers (QFI) for uplink and downlink data packets, etc.

[0059] An example of a Layer 2 (L2) data flow is Figure 4 As shown, a transmission block generated by the MAC layer consists of two radio bearers RB x and RB y The RLC PDU cascade consists of RB x The two RLC protocol data units (PDUs) are obtained by adding headers to two complete Internet Protocol (IP) packets at various levels. y An RLC PDU is a segment from an IP datagram.

[0060] The following, in combination with the accompanying drawings, describes in detail the data packet transmission method, apparatus, terminal and network side equipment provided in the embodiments of the present application through some embodiments and their application scenarios.

[0061] See also Figure 5 , Figure 5is a flow chart of a data packet transmission method provided in an embodiment of the present application, such as Figure 5 As shown, the data packet transmission method includes the following steps:

[0062] Step 101: The terminal performs a first operation, where the first operation includes at least one of the following:

[0063] Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments;

[0064] A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

[0065] The first data packet may be a data packet that does not need to be segmented for transmission at the target protocol layer. For example, the first data packet may be a data packet that does not need to be segmented for transmission at the RLC layer, or a data packet that does not need to be segmented for transmission at other protocol layers. The second data packet may be a data packet that does not need to be segmented for transmission at the target protocol layer. For example, the second data packet may be a data packet that does not need to be segmented for transmission at the RLC layer, or a data packet that does not need to be segmented for transmission at other protocol layers. The target protocol layer may be a protocol layer that performs segmentation operations.

[0066] It should be noted that the RLC layer can provide data transmission in three modes: Transparent Mode (TM), UM, and AM.

[0067] It should be noted that in 5G and existing systems, the RLC layer is used as the protocol layer for segmenting data packets in layer 2 processing, while in 6G systems or subsequent evolved systems, the protocol layer for segmentation operations may continue to use the RLC layer protocol name, or may be changed to other protocol layer names. The embodiments of the present application do not limit the specific name of the target protocol layer.

[0068] In one implementation manner, sending the first data packet based on the TM may include: sending the first data packet to the network side device based on the TM.

[0069] In one implementation, receiving the second data packet based on the TM may include: receiving the second data packet sent by the network side device based on the TM.

[0070] In one implementation, the first data packet may be a data packet that does not need to be segmented for transmission at the RLC layer. The first data packet is an RLC SDU at the RLC layer. Sending the first data packet based on TM may include the RLC layer sending the RLC SDU directly to the MAC layer of the terminal, and the MAC layer sending it outward without segmentation processing and adding RLC header processing.

[0071] In one implementation, the second data packet may be a data packet that does not need to be segmented for transmission at the RLC layer. Receiving the second data packet based on TM may include the RLC layer or MAC layer of the terminal delivering the second data packet directly to the PDCP layer without reassembling the data packet or removing the header.

[0072] In one implementation, the first operation may further include at least one of the following:

[0073] Sending a third data packet based on the UM, wherein the third data packet is a data packet that needs to be transmitted in segments;

[0074] A fourth data packet is received based on the UM, where the fourth data packet is a data packet that needs to be transmitted in segments.

[0075] In the related art, since RLC AM and RLC UM can generate a suitable size of transport block by segmentation and concatenation according to the size of the transport resource block, the data bearer DRB only supports the two transmission modes of RLC AM and RLC UM, avoiding the situation of wasting transmission resources such as padding. Because the RLC TM mode does not support any segmentation and other operations, the data packet cannot adapt to the size of the transmission resource, so it is only used in scenarios where the data blocks and resources are relatively certain, such as a small number of broadcast messages.

[0076] The embodiment of the present application provides a method for processing a data packet. When segmentation processing is not required, the TM mode is used. When segmentation processing is required, segmentation and increasing header overhead are performed similar to the UM mode processing. This not only reduces the processing delay and improves the UE processing efficiency, but also reduces the header overhead. On the basis of ensuring the UE experience, the system efficiency is further improved.

[0077] The embodiments of the present application can be applied to 6G and are not limited to Uu, and can be extended to other different versions.

[0078] In one implementation, when the terminal is configured with at least one DRB to support TM transmission, when the terminal acts as a transmitter, the terminal as a transmitter may perform any of the following:

[0079] The sender cache mechanism ensures the first-in-first-out routing mechanism of data packets, or performs special data packet priority processing as needed;

[0080] The sender uses TM transmission for packets that do not need to be segmented;

[0081] The sender adopts UM transmission for the data packets that need to be segmented, for example, adding a data packet header to carry the sequence number (SN), segmentation information, etc.

[0082] The sender uses different indication methods for TM and UM data packets.

[0083] The transmitting end may concatenate or multiplex the data packets transmitted by the TM and the data packets transmitted by the UM.

[0084] In one implementation, when the terminal is configured with at least one DRB to support TM transmission, when the terminal acts as a receiving end, the terminal as a receiving end may perform any of the following:

[0085] The receiving end receives the data block and distinguishes the data packets transmitted by TM from those transmitted by UM according to different indication methods;

[0086] The receiving end directly delivers the data packets transmitted by the TM to the upper layer;

[0087] The receiving end reassembles the data packets transmitted by UM and removes the headers, and then submits the reassembled data packets to the upper layer;

[0088] A unified higher-level entity at the receiving end, such as PDCP, performs reordering between data packets in different modes.

[0089] In the embodiment of the present application, the terminal performs a first operation, and the first operation includes at least one of the following: sending a first data packet based on the transparent mode TM, the first data packet is a data packet that does not need to be transmitted in segments; receiving a second data packet based on the TM, the second data packet is a data packet that does not need to be transmitted in segments. In this way, by receiving or sending a data packet that does not need to be transmitted in segments through the TM, there is no need to add a header to the data packet that does not need to be transmitted in segments, which can reduce header overhead and improve data transmission efficiency.

[0090] Optionally, the first operation further includes at least one of the following:

[0091] Sending a third data packet based on the unacknowledged mode UM, wherein the third data packet is a data packet that needs to be transmitted in segments;

[0092] A fourth data packet is received based on the UM, where the fourth data packet is a data packet that needs to be transmitted in segments.

[0093] The third data packet may be a data packet that needs to be transmitted in segments at the target protocol layer. For example, the third data packet may be a data packet that needs to be transmitted in segments at the RLC layer, or a data packet that needs to be transmitted in segments at other protocol layers. The fourth data packet may be a data packet that needs to be transmitted in segments at the target protocol layer. For example, the fourth data packet may be a data packet that needs to be transmitted in segments at the RLC layer, or a data packet that needs to be transmitted in segments at other protocol layers.

[0094] It should be noted that in 5G and existing systems, the RLC layer is used as the protocol layer for segmenting data packets in layer 2 processing, while in 6G systems or subsequent evolved systems, the protocol layer for segmentation operations may continue to use the RLC layer protocol name, or may be changed to other protocol layer names. The embodiments of the present application do not limit the specific name of the target protocol layer.

[0095] In one implementation manner, sending the third data packet based on the UM may include: sending the third data packet to the network side device based on the UM.

[0096] In one implementation, receiving the fourth data packet based on the UM may include: receiving the fourth data packet sent by the network side device based on the UM.

[0097] In one implementation, the third data packet may be a data packet that needs to be transmitted in segments at the RLC layer. The third data packet is an RLC SDU at the RLC layer. Sending the third data packet based on UM may include the RLC layer segmenting the RLC SDU and adding RLC header processing, and then sending the processed segmented packets to the MAC layer of the terminal, which is then sent outward by the MAC layer.

[0098] In one implementation, the fourth data packet may be a data packet that needs to be transmitted in segments at the RLC layer. Receiving the fourth data packet based on the UM may include the RLC layer of the terminal reassembling the fourth data packet and then delivering the reassembled data packet to the PDCP layer.

[0099] In this implementation, a third data packet is sent based on UM, and the third data packet is a data packet that needs to be transmitted in segments; a fourth data packet is received based on UM, and the fourth data packet is a data packet that needs to be transmitted in segments. In this way, data packets that do not need to be transmitted in segments are received or sent through TM, and data packets that need to be transmitted in segments are received or sent through UM, thereby adding a header to the data packets that need to be transmitted in segments, and not adding a header to the data packets that do not need to be transmitted in segments, which can ensure data transmission effects, reduce header overhead, and improve data transmission efficiency.

[0100] Optionally, the sending the first data packet based on the TM includes: sending the first data packet through a TM module in the RLC entity; or

[0101] The receiving the second data packet based on the TM comprises: receiving the second data packet through a TM module in the RLC entity; or

[0102] The sending of the third data packet based on UM includes: sending the third data packet through a UM module in an RLC entity; or

[0103] The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through a UM module in the RLC entity.

[0104] The TM module in the RLC entity can be used to process data packets transmitted by the TM; and the UM module in the RLC entity can be used to process data packets transmitted by the UM.

[0105] In this implementation, data packets that do not require segmented transmission are sent or received through the TM module in the RLC entity, and data packets that require segmented transmission are sent or received through the UM module in the RLC entity. In this way, data packets that do not require segmented transmission and data packets that require segmented transmission are processed separately by two independent modules in the RLC entity, thereby improving data processing efficiency.

[0106] Optionally, the sending the first data packet based on the TM includes: sending the first data packet through an RLC TM entity; or

[0107] The receiving the second data packet based on the TM comprises: receiving the second data packet through an RLC TM entity; or

[0108] The sending of the third data packet based on UM includes: sending the third data packet through an RLC UM entity; or

[0109] The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through an RLC UM entity.

[0110] Among them, the RLC TM entity can be used to process data packets transmitted by TM; and the RLC UM entity can be used to process data packets transmitted by UM.

[0111] In this implementation, data packets that do not require segmented transmission are sent or received through the RLC TM entity, and data packets that require segmented transmission are sent or received through the RLC UM entity. In this way, the data packets that do not require segmented transmission and the data packets that require segmented transmission are processed by the RLC TM entity and the RLC UM entity respectively, which can improve data processing efficiency.

[0112] Optionally, when the terminal is a transmitting end, before the terminal performs the first operation, the method further includes:

[0113] Determine the resources to be transmitted;

[0114] Determine N data packets to be sent in the sending buffer of the terminal based on a preset sending order and a resource block size of the resource to be transmitted, where N is a positive integer;

[0115] Based on the data packet sizes of the N data packets to be sent and the resource block size of the resources to be transmitted, the first data packet or the third data packet among the N data packets to be sent is determined.

[0116] The resource to be transmitted may be determined by the MAC layer of the terminal. The preset sending order may be a sending order determined according to the order of the data packets in the sending buffer, for example, a first-in-first-out sending order; or a sending order determined according to the priority of the data packets, for example, a sending order in which data packets with high priority are sent first; etc. This embodiment does not limit the preset sending order.

[0117] In addition, the data packet size of the data packet to be sent can be the size of the buffer space occupied by the data packet to be sent in the sending buffer, which does not include the data header size of the data header added due to the need for segmented transmission. Taking the sending buffer as an RLC buffer as an example, the data packet to be sent can be an RLC SDU segmented packet, and the size of the RLC SDU segmented packet is 100 bytes. Due to the segmented transmission, a data header needs to be added to the RLC SDU segmented packet, and the data header is the RLC Header. The added data header is not included in the size of the RLC SDU segmented packet. The size of the RLC SDU segmented packet as the data packet to be sent is 100 bytes.

[0118] It should be noted that the first N-1 data packets to be sent among the determined N data packets to be sent can all be transmitted through the resources to be transmitted, and the last data packet to be sent among the N data packets to be sent can be transmitted through the resources to be transmitted, or its segments can be transmitted through the resources to be transmitted. The first data packet to be sent among the first N-1 data packets to be sent is a segmented packet, or a complete data packet. In the case that the last data packet of the previous transmission is a segmented packet, the first data packet to be sent in this transmission is a segmented packet; in the case that the last data packet of the previous transmission is a complete data packet, the first data packet to be sent in this transmission is a complete data packet.

[0119] Taking the sending order determined according to the sequence of the data packets in the sending cache as an example, the N data packets to be sent may be the first N data packets to be sent in the sending cache of the terminal, the sum of the data packet sizes and the corresponding data header sizes of the first N data packets to be sent is greater than or less than or equal to the resource block size of the resources to be transmitted, and the sum of the data packet sizes and the corresponding data header sizes of the first N-1 data packets to be sent is less than the resource block size of the resources to be transmitted.

[0120] Taking the sending buffer as an RLC buffer as an example, the sizes of the SDUs arriving in the RLC buffer in sequence are: SDU1 100 bytes, SDU2 200 bytes, SDU3 400 bytes, SDU4 100 bytes, and the resource block size of the resource to be transmitted is 600 bytes. The resource to be transmitted can transmit SDU1 and SDU2, and can transmit segments of SDU3, and it is determined that the data packets transmitted by the resource to be transmitted are segments of SDU1, SDU2 and SDU3.

[0121] In this implementation, resources to be transmitted are determined; based on a preset sending order and the resource block size of the resources to be transmitted, N data packets to be sent in the sending cache of the terminal are determined, where N is a positive integer; based on the data packet size of the N data packets to be sent, and the resource block size of the resources to be transmitted, the first data packet or the third data packet among the N data packets to be sent is determined, so that data packets that do not need to be transmitted in segments and data packets that need to be transmitted in segments can be separately determined from the data packets to be sent in the sending cache, and different data transmission methods can be adopted for different types of data packets.

[0122] Optionally, the first data packet to be sent among the N data packets to be sent belongs to the first data packet or the third data packet, wherein:

[0123] In a case where the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resource to be transmitted, the data packets to be sent except the first data packet to be sent among the N data packets to be sent belong to the first data packet;

[0124] or

[0125] When the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted, the Nth data packet to be sent among the N data packets to be sent belongs to the third data packet, and the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent belong to the first data packet.

[0126] The first data packet to be sent among the N data packets to be sent may be a data packet that does not need to be transmitted in segments or a data packet that is transmitted in segments. If the last data packet of the previous transmission is a segmented packet, the first data packet to be sent among the N data packets to be sent is a data packet that is transmitted in segments; if the last data packet of the previous transmission is a data packet that does not need to be transmitted in segments, the first data packet to be sent among the N data packets to be sent is a data packet that does not need to be transmitted in segments.

[0127] It should be noted that the data packet to be sent belongs to the first data packet, which can be understood as the first data packet including the data packet to be sent; the data packet to be sent belongs to the third data packet, which can be understood as the third data packet including the data packet to be sent.

[0128] In one implementation, the data packets to be transmitted by the transmission resource may include the following situations:

[0129] The first type: segmented packet (segment of the first data packet) + N-2 first data packets (N is greater than or equal to 2) + segmented packet (segment of the last data packet);

[0130] The second type: segmented packet (segment of the first data packet) + N-1 first data packets (N is greater than or equal to 1);

[0131] The third type: N-1 first data packets (N is greater than or equal to 1) + segmented packets (the last data packet segment);

[0132] The fourth type: N first data packets (N is greater than or equal to 1).

[0133] Among them, the sum of the data packet sizes and corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resources to be transmitted. Corresponding to the second and fourth cases mentioned above, the first data packet includes the data packets to be sent among the N data packets to be sent except the first data packet to be sent (the second case), and the third data packet includes the first data packet to be sent among the N data packets to be sent; or, the first data packet includes the N data packets to be sent (the fourth case).

[0134] In addition, the sum of the data packet sizes and corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted. Corresponding to the first and third situations mentioned above, the third data packet includes the Nth data packet to be sent among the N data packets to be sent; the first data packet includes the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent, and the third data packet also includes the first data packet to be sent among the N data packets to be sent (the first situation); or, the first data packet includes the data packets to be sent among the N data packets to be sent except the Nth data packet to be sent (the third situation).

[0135] It should be noted that when the remaining resource size of the resources to be transmitted is insufficient to accommodate a new data packet, the data packet needs to be segmented.

[0136] Taking the sending buffer as an RLC buffer as an example, the sizes of the SDUs that arrive in the RLC buffer in order are: SDU1 100 bytes, SDU2 200 bytes, SDU3 400 bytes, SDU4 100 bytes, and the resource block size of the resource to be transmitted is 600 bytes. The resource to be transmitted can transmit SDU1 and SDU2, but cannot accommodate SDU3, and SDU3 needs to be segmented. In the resource to be transmitted, SDU1 occupies 100 bytes, SDU2 occupies 200 bytes, the RLC Header of the SDU3 segment packet occupies 1 byte, and the SDU3 segment occupies 299 bytes.

[0137] It should be noted that in the sending buffer, the priority of the remaining segments of the data packet is higher than the priority of the complete data packet. When there are remaining segments of the data packet in the sending buffer, the remaining segments of the data packet need to be sent first.

[0138] Optionally, the method further comprises:

[0139] The terminal sends target capability information to a network side device, wherein the target capability information is used to indicate whether the terminal supports a data transmission mode corresponding to the first operation.

[0140] In this implementation, the terminal sends target capability information to the network side device, wherein the target capability information is used to indicate whether the terminal supports the data transmission mode corresponding to the first operation, so that the network side device can configure the data transmission mode corresponding to the terminal's capabilities based on the terminal's capabilities, and the network side device can also choose to use a data transmission mode that matches the terminal's capabilities to transmit data with the terminal based on the terminal's capabilities.

[0141] Optionally, the target capability information includes at least one of the following:

[0142] Indication information indicating whether the terminal supports TM data transmission;

[0143] Capability information of TM data transmission supported by the terminal.

[0144] The target capability information may be the relevant capability information transmitted by the TM.

[0145] In one implementation, the terminal may report the relevant capability information of the TM transmission to the network side device, where the relevant capability information of the TM transmission includes at least one of the following:

[0146] Whether the terminal supports TM transmission;

[0147] The terminal supports the specific capability information of TM transmission.

[0148] In one implementation, the target capability information may include at least one of the following:

[0149] Version information of the terminal or capability information bound to the first operation, for example, if the terminal is a 6G version, the function of the first operation is supported by default, or the terminal supports the capability of the 6G enhanced L2 processing method, including the function of supporting the first operation;

[0150] Explicit capability indication information of whether the terminal supports the first operation, for example, by explicitly indicating support for the function through 1-bit indication information; if not carried, it means that the terminal does not support the function;

[0151] The specific capability information of the terminal supporting the first operation, for example, the terminal supports configuring a maximum of N RBs to perform the first operation at the same time, or the maximum value of the data rate that the terminal supports configuring to perform the first operation at the same time, etc.

[0152] Optionally, before the terminal performs the first operation, the method further includes:

[0153] The terminal receives a first configuration sent by a network-side device, where the first configuration is a configuration for performing the first operation.

[0154] In this implementation, the terminal receives a first configuration sent by a network side device, where the first configuration is a configuration for executing the first operation, so that the terminal can perform sending processing corresponding to the first operation or receiving processing corresponding to the first operation based on the first configuration.

[0155] Optionally, the first configuration is used to configure at least one of the following:

[0156] Whether the terminal supports TM data transmission;

[0157] Whether all data radio bearers (DRBs) of the terminal support TM transmission;

[0158] Whether each DRB of the terminal supports TM transmission;

[0159] TM data transmission method.

[0160] Among them, the TM data transmission mode may refer to a specific configuration related to TM data transmission, for example, configuring a logical channel identity (LCID) corresponding to a TM module and a UM module respectively, or configuring an LCID corresponding to an RLCTM entity and an RLC UM entity respectively.

[0161] In one implementation, the network side device may configure uplink or downlink data transmission of the terminal, and the configuration content includes at least one of the following:

[0162] Data transmission of the terminal, whether it supports TM transmission;

[0163] Whether all DRBs of the terminal support TM transmission;

[0164] Whether each DRB of the terminal supports TM transmission;

[0165] Specific configuration related to TM data transmission.

[0166] In one implementation, the first configuration may be used to configure at least one of the following:

[0167] transmission of all radio bearers (RBs) of the terminal that meet the configuration conditions, whether to turn on the target switch, wherein the RBs that meet the configuration conditions can be determined by some default rules or network configuration rules, for example, one rule is that the RBs corresponding to the RLC AM cannot be configured or the target switch can be started, and only the RBs corresponding to the RLC UM can be configured or the target switch can be started, and the target switch is a switch used to control whether the data transmission mode corresponding to the first operation is enabled;

[0168] For the terminal's transmission based on RB granularity, configure whether to turn on the target switch separately;

[0169] For the terminal's RB-based uplink (UL) or downlink (DL) transmission, configure whether to turn on the target switch;

[0170] Parameters related to the first operation, such as additional LCID configuration, configuring two LCIDs to correspond to the TM module and the UM module respectively, or configuring two LCIDs to correspond to the RLC TM entity and the RLC UM entity respectively, etc.

[0171] Optionally, when the terminal is a transmitting end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the terminal performs the first operation, further comprising at least one of the following:

[0172] The terminal executes a first-in-first-out routing mechanism for data packets, or processes data packets according to their priority;

[0173] The terminal uses different target indication information to indicate the first data packet and the third data packet;

[0174] The terminal performs cascade processing on the first data packet and the third data packet through a media access control MAC layer;

[0175] The terminal multiplexes the first data packet and the third data packet through the MAC layer.

[0176] In this implementation, the terminal as a sender executes a first-in-first-out routing mechanism for data packets, or processes data packets according to their priorities, so that routing of data to be sent can be achieved when the terminal acts as a sender.

[0177] In this implementation, the terminal as the sending end uses different target indication information to indicate the first data packet and the third data packet, so that the receiving end can determine based on the target indication information whether the received data packet is a data packet that does not need to be transmitted in segments or a data packet that is transmitted in segments, which facilitates the receiving end to perform different data processing on different types of data packets, thereby improving data processing efficiency.

[0178] In this implementation manner, the terminal as the transmitting end performs cascade processing or multiplexing processing on the first data packet and the third data packet through the MAC layer, so that the cascade or multiplexing of different types of data packets can be achieved at the MAC layer.

[0179] Optionally, when the terminal is a receiving end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the terminal performs the first operation, further comprising at least one of the following:

[0180] The terminal determines, based on the target indication information, that the received data packet is the second data packet or the fourth data packet;

[0181] The terminal directly delivers the second data packet to the Packet Data Convergence Protocol PDCP layer;

[0182] The terminal reassembles the fourth data packet and delivers the reassembled data packet to the PDCP layer;

[0183] The terminal reorders the second data packet and the fourth data packet through the PDCP layer.

[0184] In this implementation, the terminal as the receiving end determines that the received data packet is the second data packet or the fourth data packet based on the target indication information, thereby being able to determine, based on the target indication information, that the received data packet is a data packet that does not require segmented transmission or a data packet that is segmented transmission, and then the terminal can perform different data processing on different types of data packets, thereby improving data processing efficiency.

[0185] In this implementation, the terminal as the receiving end directly submits the second data packet to the PDCP layer, that is, submits the data packet that does not need to be segmented for transmission directly to the PDCP layer, so that the PDCP layer can uniformly reorder and deliver the data in sequence, thereby improving data processing efficiency.

[0186] In this implementation, the terminal as the receiving end reassembles the fourth data packet and submits the reassembled data packet to the PDCP layer, so that the receiving end reassembles the segmented transmitted data packet and submits it to the PDCP layer. The PDCP layer can uniformly reorder and deliver the data in sequence, which can improve data processing efficiency.

[0187] In this implementation, the terminal as the receiving end reorders the second data packet and the fourth data packet through the PDCP layer, that is, the receiving end submits both the data packets that do not require segmented transmission and the data packets that require segmented transmission to the PDCP layer, and the PDCP layer uniformly reorders the data, which can improve data processing efficiency.

[0188] Optionally, the target indication information is 1-bit indication information, or the target indication information is a logical channel identifier LCID.

[0189] It should be noted that the target indication information may be carried in the data packet to be sent.

[0190] Optionally, after the terminal receives the first configuration sent by the network side device, the method further includes:

[0191] The terminal receives a second configuration sent by the network side device, where the second configuration is a reconfiguration of the terminal by the network side device;

[0192] The terminal performs a first operation, including:

[0193] In a case where the first configuration is used to configure turning on or off a target switch, and the second configuration is used to configure turning on the target switch, if the terminal is a transmitting end, the terminal performs an initialization operation on a transmission variable, and the terminal performs a transmission process corresponding to the first operation on a first unsent data packet after the reconfiguration; or

[0194] In a case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a receiving end, the terminal performs an initialization operation on a receiving variable, and the terminal delivers the data packet before reconfiguration to the PDCP layer, and performs reception processing corresponding to the first operation on the data packet after reconfiguration.

[0195] Optionally, the method further comprises at least one of the following:

[0196] In the case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the terminal is a sending end, the terminal performs an initialization operation on a sending variable, and the terminal performs a sending process corresponding to the second configuration on the first unsent data packet after the reconfiguration;

[0197] In a case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the terminal is a receiving end, the terminal performs an initialization operation on a receiving variable, and the terminal delivers a data packet before reconfiguration to the PDCP layer, and performs reception processing corresponding to the second configuration on a data packet after reconfiguration;

[0198] The target switch is a switch used to control whether to enable the data transmission mode corresponding to the first operation.

[0199] Among them, turning on the target switch can be understood as enabling the data transmission mode corresponding to the first operation; not turning on the target switch can be understood as not enabling the data transmission mode corresponding to the first operation.

[0200] It should be noted that, when the network side device is configured to turn on the target switch, the terminal performs sending and receiving processing according to the first operation, otherwise it performs processing in a traditional manner.

[0201] In addition, the reconfiguration on the network side includes both reconfiguration within a cell and reconfiguration in a handover scenario.

[0202] In addition, when the second configuration is used to configure and turn on the target switch, the sending variable is initialized, which may include initializing the PDCP layer and the RLC layer, for example, creating a TM module and a UM module for the RLC layer according to the new configuration, or creating a RLC TM entity and an RLC UM entity.

[0203] In addition, performing the sending process corresponding to the first operation on the first unsent data packet after the reconfiguration may include starting to execute the first operation on the first unsent data packet after the reconfiguration, and sending the data according to the reconfiguration.

[0204] In addition, when the second configuration is used to configure and turn on the target switch, the initialization operation on the receiving variable may include initializing the PDCP layer and the RLC layer, for example, creating a TM module and a UM module for the RLC layer according to the new configuration, or creating a RLC TM entity and an RLC UM entity.

[0205] In addition, performing the receiving processing corresponding to the first operation on the data packet after the reconfiguration may include performing the first operation on the data packet after the reconfiguration at the RLC layer and the PDCP layer.

[0206] In addition, when the second configuration is used to configure not to turn on the target switch, initializing the sending variable may include initializing the PDCP layer and the RLC layer, for example, establishing the RLC layer according to the traditional entity.

[0207] In addition, when the second configuration is used to configure the target switch not to be turned on, the sending processing corresponding to the second configuration for the first unsent data packet after the reconfiguration may include using traditional operations to send data starting from the first unsent data packet after the reconfiguration.

[0208] In addition, when the second configuration is used to configure not to turn on the target switch, the initialization operation of the receiving variable may include initializing the PDCP layer and the RLC layer, for example, establishing the RLC layer according to the traditional entity, and the segments that have not been successfully reassembled in the original RLC UM module or RLC UM entity will be deleted.

[0209] In addition, when the second configuration is used to configure the target switch not to be turned on, the receiving processing corresponding to the second configuration on the data packet after the reconfiguration may include using traditional operations to receive data on the data packet after the reconfiguration at the RLC layer and the PDCP layer.

[0210] It should be noted that the conventional operation in the embodiments of the present application refers to an existing data transmission or data reception method, for example, a data transmission or data reception method for data transmission through two transmission modes, RLC AM and RLC UM. The conventional entity in the embodiments of the present application is an entity that matches the existing data transmission or data reception method.

[0211] In this implementation, when the first configuration is used to configure whether to turn on or off the target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a transmitting end, the terminal performs an initialization operation on the transmission variable, and the terminal performs a transmission process corresponding to the first operation on the first unsent data packet after the reconfiguration; or, when the first configuration is used to configure whether to turn on or off the target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a receiving end, the terminal performs an initialization operation on the reception variable, and the terminal submits the data packet before the reconfiguration to the PDCP layer, and performs a reception process corresponding to the first operation on the data packet after the reconfiguration. Thus, when the data transmission mode corresponding to the first operation is enabled by the reconfiguration, the data transmission of the terminal can be performed according to the reconfiguration of the terminal by the network side device.

[0212] In this implementation, when the first configuration is used to configure the target switch to be turned on, and the second configuration is used to configure the target switch not to be turned on, if the terminal is a transmitting end, the terminal performs an initialization operation on the transmission variable, and the terminal performs a transmission process corresponding to the second configuration on the first unsent data packet after the reconfiguration; or, when the first configuration is used to configure the target switch to be turned on, and the second configuration is used to configure the target switch not to be turned on, if the terminal is a receiving end, the terminal performs an initialization operation on the reception variable, and the terminal submits the data packet before the reconfiguration to the PDCP layer, and performs a reception process corresponding to the second configuration on the data packet after the reconfiguration. Thus, when the reconfiguration does not enable the data transmission mode corresponding to the first operation, the data transmission of the terminal can be performed according to the reconfiguration of the terminal by the network side device.

[0213] See also Figure 6 , Figure 6 is a flow chart of a data packet transmission method provided in an embodiment of the present application, such as Figure 6 As shown, the data packet transmission method includes the following steps:

[0214] Step 201: The network-side device performs a second operation, where the second operation includes at least one of the following:

[0215] Sending a second data packet based on the transparent mode TM, where the second data packet is a data packet that does not need to be transmitted in segments;

[0216] A first data packet is received based on the TM, where the first data packet is a data packet that does not need to be transmitted in segments.

[0217] Optionally, the second operation further includes at least one of the following:

[0218] Sending a fourth data packet based on the unacknowledged mode UM, wherein the fourth data packet is a data packet that needs to be transmitted in segments;

[0219] A third data packet is received based on the UM, where the third data packet is a data packet that needs to be transmitted in segments.

[0220] Optionally, the sending the second data packet based on the TM comprises: sending the second data packet through a TM module in the RLC entity; or,

[0221] The receiving the first data packet based on the TM comprises: receiving the first data packet through a TM module in the RLC entity; or

[0222] The sending of the fourth data packet based on UM includes: sending the fourth data packet through a UM module in an RLC entity; or

[0223] The receiving the third data packet based on the UM includes: receiving the third data packet through a UM module in the RLC entity.

[0224] Optionally, the sending the second data packet based on the TM includes: sending the second data packet through an RLC TM entity; or

[0225] The receiving the first data packet based on the TM comprises: receiving the first data packet through an RLC TM entity; or

[0226] The sending of the fourth data packet based on UM includes: sending the fourth data packet through an RLC UM entity; or

[0227] The receiving the third data packet based on UM includes: receiving the third data packet through an RLC UM entity.

[0228] Optionally, when the network side device is a transmitting end, before the network side device performs the second operation, the method further includes:

[0229] Determine the resources to be transmitted;

[0230] Determine N data packets to be sent in the sending buffer of the network side device based on a preset sending order and a resource block size of the resource to be transmitted, where N is a positive integer;

[0231] The second data packet or the fourth data packet among the N data packets to be sent is determined based on the data packet sizes of the N data packets to be sent and the resource block size of the resources to be transmitted.

[0232] Optionally, the first data packet to be sent among the N data packets to be sent belongs to the second data packet or the fourth data packet, wherein:

[0233] In a case where the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resource to be transmitted, the data packets to be sent among the N data packets to be sent except the first data packet to be sent belong to the second data packet;

[0234] or

[0235] When the sum of the data packet sizes and corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted, the Nth data packet to be sent among the N data packets to be sent belongs to the fourth data packet, and the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent belong to the second data packet.

[0236] Optionally, the method further comprises:

[0237] The network side device receives target capability information sent by the terminal, wherein the target capability information is used to indicate whether the terminal supports a data transmission mode corresponding to the second operation.

[0238] Optionally, the target capability information includes at least one of the following:

[0239] Indication information indicating whether the terminal supports TM data transmission;

[0240] Capability information of TM data transmission supported by the terminal.

[0241] Optionally, before the network side device performs the second operation, the method further includes:

[0242] The network side device sends a first configuration to the terminal, where the first configuration is a configuration for performing the second operation.

[0243] Optionally, the first configuration is used to configure at least one of the following:

[0244] Whether the terminal supports TM data transmission;

[0245] Whether all data radio bearers (DRBs) of the terminal support TM transmission;

[0246] Whether each DRB of the terminal supports TM transmission;

[0247] TM data transmission method.

[0248] Optionally, when the network side device is a transmitting end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the network side device performs the second operation, further comprising at least one of the following:

[0249] The network side device executes a first-in-first-out routing mechanism for data packets, or processes data packets according to their priority;

[0250] The network side device uses different target indication information to indicate the second data packet and the fourth data packet;

[0251] The network side device performs cascade processing on the second data packet and the fourth data packet through the media access control MAC layer;

[0252] The network side device multiplexes the second data packet and the fourth data packet through the MAC layer.

[0253] Optionally, when the network side device is a receiving end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the network side device performs the second operation, further comprising at least one of the following:

[0254] The network side device determines, based on the target indication information, that the received data packet is the first data packet or the third data packet;

[0255] The network side device directly delivers the first data packet to the Packet Data Convergence Protocol PDCP layer;

[0256] The network side device reassembles the third data packet and delivers the reassembled data packet to the PDCP layer;

[0257] The network side device reorders the first data packet and the third data packet through the PDCP layer.

[0258] Optionally, the target indication information is 1-bit indication information, or the target indication information is a logical channel identifier LCID.

[0259] Optionally, after the network side device sends the first configuration to the terminal, the method further includes:

[0260] The network side device sends a second configuration to the terminal, where the second configuration is a reconfiguration of the terminal by the network side device;

[0261] The network side device performs a second operation, including:

[0262] In a case where the first configuration is used to configure turning on or off a target switch, and the second configuration is used to configure turning on the target switch, if the network side device is a sending end, the network side device performs an initialization operation on a sending variable, and the network side device performs a sending process corresponding to the second operation on the first unsent data packet after the reconfiguration; or

[0263] In a case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the network side device is a receiving end, the network side device performs an initialization operation on a receiving variable, and the network side device delivers the data packet before reconfiguration to the PDCP layer, and performs receiving processing corresponding to the second operation on the data packet after reconfiguration.

[0264] Optionally, the method further comprises at least one of the following:

[0265] In the case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the network side device is a sending end, the network side device performs an initialization operation on a sending variable, and the network side device performs a sending process corresponding to the second configuration on the first unsent data packet after the reconfiguration;

[0266] In the case where the first configuration is used to configure the target switch to be turned on, and the second configuration is used to configure the target switch not to be turned on, if the network side device is a receiving end, the network side device performs an initialization operation on the receiving variable, and the network side device delivers the data packet before the reconfiguration to the PDCP layer, and performs receiving processing corresponding to the second configuration on the data packet after the reconfiguration;

[0267] The target switch is a switch used to control whether to enable the data transmission mode corresponding to the second operation.

[0268] It should be noted that this embodiment is Figure 5 The implementation of the corresponding network side device in the embodiment shown in the figure can be found in the specific implementation of Figure 5 To avoid repeated description of the embodiment shown, the present embodiment will not be described in detail.

[0269] The data packet transmission method provided in the embodiment of the present application is described below through several specific embodiments:

[0270] In the following embodiments, L2 new operation refers to Figure 5 The first operation in the embodiment, or Figure 6 The second operation in the embodiment.

[0271] Embodiment 1:

[0272] In this embodiment, the new configuration of L2 processing on the network side and the reporting of relevant capabilities of the user equipment (UE, ie terminal) required before the new configuration are mainly introduced.

[0273] Generally speaking, the introduction of new functions requires the support of terminal capabilities and network-side functions. In one case, if the function is a mandatory function for 6G terminals and the network side, it can be assumed that all 6G terminals support the function, and all 6G network nodes support the function. In this case, whether the terminal and network node support the new function will be bound to the version information or 6G capabilities. In another case, if the function is an optional function for 6G terminals and the network side, the 6G terminal needs to carry the corresponding capability bit to report whether it supports the function, and the network node also needs the optional configuration to support the function.

[0274] For a network node supporting new L2 operations, it is necessary to first obtain the UE's capabilities and confirm that the UE supports the function before further configuring the function for the UE.

[0275] The UE capability information includes at least one of the following:

[0276] UE version information or capability information bound to the function, for example, if the UE is a 6G version, the L2 new operation function is supported by default, or the UE supports the 6G enhanced L2 processing capability, including support for the L2 new operation function;

[0277] Explicit capability indication information of whether the UE supports the new L2 operation, for example, by explicitly indicating support for the function through 1-bit indication information; if it is not carried, it means that the UE does not support the function;

[0278] Specific capability information of the UE supporting the new L2 operation, for example, the UE supports configuring a maximum of N RBs to adopt the new L2 operation at the same time, or the maximum data rate that the UE supports configuring to adopt the new L2 operation at the same time, etc.

[0279] It should be noted that the UE can package the above-mentioned capability information together with the existing capability information and report it to the network side according to the traditional capability reporting process, or it can adopt an independent capability acquisition process, such as the UE reporting again when the network side indicates that it supports the function, or the network side explicitly queries the UE for the capability information and then reports it, etc., to provide the network with corresponding capability information.

[0280] For a network-side entity that does not support the new L2 operation, even if the corresponding capability of the UE is obtained, it may be ignored because the capability domain cannot be identified. Therefore, different support versions of the UE and the network entity can be well compatible and collaborative.

[0281] When a network entity supporting the new L2 operation obtains a report of the UE's related capabilities and decides to configure the new L2 operation for the UE based on its own algorithm or service requirements or UE's inclination, the network side may configure at least one of the following for the terminal:

[0282] Whether to enable the L2 new operation switch for all RBs that meet the configuration conditions of the UE. The RBs that meet the configuration conditions are determined by some default rules or network configuration rules. For example, the simplest rule is that the RBs corresponding to the RLC AM cannot be configured or enabled with the L2 new operation function, and only the RBs corresponding to the RLC UM can be configured or enabled with the L2 new operation function;

[0283] For UEs, whether to enable the new L2 operation switch is configured individually based on the RB granularity;

[0284] For UE RB-based UL or DL, configure whether to enable the L2 new operation switch;

[0285] Some detailed parameters related to the new L2 operation functions, such as additional LCID configuration, two LCIDs corresponding to the TM module and UM module, or RLC TM entity and RLC UM entity, etc.

[0286] The UE can send and receive according to the new operation only when the network is configured to turn on the L2 new operation switch, otherwise it will be processed in the traditional way.

[0287] The reconfiguration on the network side includes both reconfiguration within a cell and reconfiguration in a handover scenario. The processing methods of the sender and the receiver include the following situations:

[0288] The first type: when the original configuration does not enable new L2 operations and the reconfiguration enables new L2 operations,

[0289] The transmitting end performs an initialization operation on the transmission variables, including initializing the PDCP layer and the RLC layer. For example, the RLC layer creates a TM module and a UM module according to the new configuration, or creates a RLC TM entity and an RLC UM entity.

[0290] The sender starts sending data using the new L2 operation and its configuration from the first data packet that has not been sent.

[0291] The receiving end performs initialization operations on the receiving variables, including initialization of the PDCP layer and the RLC layer. For example, the RLC layer creates a TM module and a UM module according to the new configuration, or creates a RLC TM entity and an RLC UM entity.

[0292] The receiving end delivers the PDCP packets before reconfiguration to the higher layer in ascending order of sequence number or COUNT value, and enables L2 new operation for the RLC layer and PDCP layer of subsequent packets;

[0293] The second type: When the original configuration enables new L2 operations and the reconfiguration does not enable new L2 operations,

[0294] The transmitting end performs initialization operations on the transmitting variables, including initialization of the PDCP layer and the RLC layer, for example, the RLC layer is established according to the traditional entity;

[0295] The sender starts sending data using traditional operations from the first data packet that has not been sent;

[0296] The receiving end performs initialization operations on the receiving variables, including initialization of the PDCP layer and the RLC layer. For example, the RLC layer is established according to the traditional entity, and the segments that have not been successfully reassembled in the original RLC UM module or RLC UM entity will be deleted;

[0297] The receiving end delivers the PDCP data packets before reconfiguration to the higher layer in ascending order of sequence number or COUNT value, and takes conventional operations on the subsequent data packets at the RLC layer and PDCP layer;

[0298] The third type: When the original configuration enables new L2 operations and the reconfiguration also enables new L2 operations,

[0299] The transmitting end performs an initialization operation on the transmission variables, including initializing the PDCP layer and the RLC layer, for example, the RLC layer creates a new TM module and a UM module according to the new configuration, or creates a new RLC TM entity and an RLC UM entity, and deletes the old TM module and UM module, or the old RLC TM entity and RLC UM entity;

[0300] The sender starts sending data using the new L2 operation and its configuration from the first data packet that has not been sent.

[0301] The receiving end performs an initialization operation on the receiving variables, including initializing the PDCP layer and the RLC layer, for example, the RLC layer creates a new TM module and a UM module according to the new configuration, or creates a new RLC TM entity and an RLC UM entity, and deletes the old TM module and the UM module, or the old RLC TM entity and the RLC UM entity;

[0302] The receiving end delivers the PDCP data packets before reconfiguration to the higher layer in ascending order of sequence number or COUNT value, and enables L2 new operation for the RLC layer and PDCP layer of subsequent data packets.

[0303] Embodiment 2:

[0304] This embodiment introduces a new L2 operation mode of a unified RLC entity.

[0305] The specific schematic diagram of the unified RLC entity is as follows Figure 7 As shown, an RLC entity includes at least two independent submodules. The TM module is used to process transparent mode data packets, which have the highest transmission efficiency and the smallest header overhead; the UM module is used to process UM mode data packets. These data packets increase certain processing overhead and header overhead due to the need to add an RLC header, but can better adapt to the size of the transmission resource block and avoid wasting resources.

[0306] For the transmitting end, the behavior from the PDCP entity to the MAC entity may include the following steps:

[0307] Step 11: The PDCP entity still corresponds to one RB. After being processed at the PDCP layer, the high-level data packet forms a PDCP PDU and is sent to the corresponding RLC unified entity.

[0308] Step 12: After receiving the PDCP PDU, the RLC unified entity stores it in the transmission buffer as an RLC SDU according to the first-in-first-out principle, waits for the MAC to indicate the transmission resource size, and then organizes the data packet for transmission;

[0309] When the MAC layer obtains transmission resources and allocates resource size for the RB according to the logical channel priority LCP operation, the RLC unified entity organizes the data packet to be sent to the MAC layer according to the resource size it has obtained. When the data packet sent in the order of arrival is a complete RLC SDU, it is directly sent to the MAC layer, which is equivalent to the complete RLC SDU passing through the TM module, and does not require any processing or adding headers. When the remaining resource size is not enough to accommodate a new RLC SDU, the RLC SDU needs to be segmented. At this time, the RLC SDU is sent to the UM module to perform segmentation and add RLC header operations. After that, the RLC PDU composed of the RLC SDU segments is sent to the MAC layer.

[0310] It should be noted that the complete RLC SDU and the segmented RLC SDU need to be sent to the MAC layer through different inter-node paths or carry different indications so that the MAC layer can distinguish between the two types of data.

[0311] When there are remaining RLC SDU segments in the RLC UM module, the next time a new transmission block indicated by the MAC layer arrives, these remaining segments must be processed first, and after all the segments are sent, other new complete RLC SDUs or new RLC SDU segments can be considered. That is, it is necessary to ensure that the remaining RLC SDU segments stored in the UM module have a higher sending priority than the complete RLC SDU in the RLC unified sending buffer.

[0312] When a MAC transmission resource block size is indicated, the data packet sent by the RLC unified entity to the MAC entity contains at most two RLC SDU segments (located at the first block position and the last block position respectively) and N complete RLC SDUs in between (N is an integer such as 0, 1, 2, 3, etc.).

[0313] For example, Figure 8As shown in the figure, when the SDU sizes in the RLC unified buffer are SDU1 100 bytes, SDU2 200 bytes, SDU3 400 bytes, SDU4 100 bytes, and SDU5 300 bytes in the order of arrival, the MAC layer indicates the transmission resource block size of 400 bytes for the first time, which can be used to transmit SDU1, SDU2, and SDU3 segments, of which SDU1 occupies 100 bytes, SDU2 occupies 200 bytes, RLC Header occupies 1 byte, and SDU3 segment occupies 99 bytes. The MAC layer indicates the transmission resource block size of 200 bytes for the second time, which can be used to transmit SDU3 segment, of which RLC Header occupies 3 bytes, and SDU3 segment occupies 197 bytes. The MAC layer indicates the transmission resource block size of 400 bytes for the third time, of which RLC Header occupies 3 bytes + SDU3 segment occupies 104 bytes + SDU4 occupies 100 bytes + RLC Header occupies 1 byte + SDU5 segment occupies 192 bytes. The MAC layer indicates for the fourth time that the transmission resource block size is 111 bytes, of which the RLC Header occupies 3 bytes and the SDU5 segment occupies 108 bytes. The packetization process is as follows:

[0314] Among them, the RLC Header takes the SN length of 6 bits as an example. Three of the four values ​​of the 2-bit segmentation information (Segmentation Info, SI) respectively distinguish the first segment, the middle segment and the last segment of the original SDU. The segment offset (segment offset, SO) length is 16 bits, indicating the starting byte position of the segment in the original SDU. Among them, the first segment does not set SO, and the middle segment and the last segment need to set SO. Therefore, the first segment of the SDU carries a 1-byte header, and the middle segment and the last segment carry a 3-byte header. Fig. 9 The figure shows the RLC Header without setting SO. Fig.10 The figure shows the RLC Header for setting SO.

[0315] It should be noted that the above only takes the SN+SI+SO format as an example of the UM PDU header. In the future, there may be a new UM PDU header format, such as a fixed header length format. The header contains SN+LSF+Seg_num, where the last segment flag (LSF) distinguishes whether it is the last segment, and the Seg_num field is the subsequence number of the segment packet.

[0316] Step 13: After receiving the RLC PDU from the RLC unified entity, the MAC layer concatenates the PDUs in sequence and distinguishes the data packets from the RLC SDU and the RLC SDU segments in the following manner:

[0317] Mode 1: Different logical channel identifications (LCIDs) are used to distinguish RLC SDU data (i.e., data from the TM module) and RLC SDU segment data (i.e., data from the UM module); RLC SDU data refers to a complete RLC SDU, i.e., an RLC SDU that does not require segmented transmission; RLC SDU segment data refers to an RLC SDU that is transmitted in segments.

[0318] Mode 2: For RLC SDU data (i.e., data from the TM module) and RLC SDU segmented data (i.e., data from the UM module), although the same LCID is used, 1-bit indication information in the MAC subheader is used to indicate whether the data packet is RLC SDU data or RLC SDU segmented data. For example, 1-bit indication information of 0 represents complete RLC SDU data, and 1-bit indication information of 1 represents RLC SDU segmented data, or vice versa; or, the 1-bit indication information is used to indicate whether it is RLC SDU data; or, the 1-bit indication information is used to indicate whether it is RLC SDU segmented data; etc. Different data types can be distinguished by the 1-bit indication information. RLC SDU data refers to RLC SDU that does not need to be segmented.

[0319] For the receiving end, the behavior from the MAC entity to the PDCP entity includes the following steps:

[0320] Step 21: The MAC layer distinguishes the received data packets according to the packet format and the logical channel identifier, and distinguishes different data from the TM module and the UM module of different logical channels, as follows:

[0321] Mode 1: When the data of the TM module and the UM module in an RLC entity are distinguished by different LCIDs, the MAC layer can distinguish the TM module or UM submodule of which logical channel the data packet comes from by reading different LCIDs in the subheader, and send the data to the corresponding module of the corresponding entity;

[0322] Mode 2: When the data of the TM module and the UM module in an RLC entity use the same LCID, but use different values ​​of the 1-bit indication information in the subheader field to distinguish the RLC SDU data or RLC SDU segment data, the corresponding RLC entity is found by the LCID, and then the corresponding module is found by the value of the 1-bit indication information, and the data is sent to the corresponding module of the corresponding entity;

[0323] Step 22: For the RLC entity, if the TM module receives the data, the data must be a complete RLC SDU, so it is directly delivered to the corresponding PDCP layer. If the UM module receives the data, the UM receiving end reassembles the data packet segments according to the SN and segment SI, SO and other tags in the RLC header format, and immediately delivers the successfully reassembled RLC SDU to the corresponding PDCP layer. If certain conditions are met, such as the reordering timer expires, the segments that are still not successfully reassembled are deleted.

[0324] Step 23. For the PDCP PDU received by the RLC entity, if it is configured that it does not need to be delivered in sequence, the PDCP layer directly delivers it to the upper layer after processing it at the PDCP layer. The processing at the PDCP layer may include: removing the header, decompressing the security operation, and decompressing the header. If it is configured that it needs to be delivered in sequence, the data packets are reordered according to the COUNT value according to the SN carried in the PDCP header and the locally maintained Hyper Frame Number (HFN), as well as the window mechanism and other rules, and the PDCP SDU is delivered to the upper layer in ascending order.

[0325] From the above receiving side processing flow, it can be seen that in the RLC entity, the TM module and the UM module respectively deliver the RLC SDU to the PDCP layer, and the functions of reordering and in-order delivery of the data are handed over to the PDCP layer to complete, which is not only efficient but also has a small header overhead and can meet the service QoS requirements.

[0326] Embodiment three:

[0327] This embodiment introduces a new L2 operation mode of an independent RLC entity.

[0328] The specific schematic diagram of an independent RLC entity is as follows Fig.11As shown, one PDCP entity, i.e. one RB, corresponds to at least two RLC entities, one RLC TM entity and one RLC UM entity. The RLC TM entity is used to process transparent mode data packets, which have the highest transmission efficiency and the smallest header overhead. The RLC UM entity is used to process UM mode data packets, which have a certain amount of processing overhead and header overhead due to the need to add the RLC Header, but can better adapt to the size of the transmission resource block, so as not to cause resource waste.

[0329] In order to ensure that the RLC SDU data packets can meet the first-come-first-out and relatively fair cache strategy, the PDCP layer at the sending end sends the processed PDCP PDU, namely the RLC SDU, to the RLC TM entity for unified cache. The RLC TM entity decides whether to directly deliver the complete RLC SDU to the MAC layer through the RLC TM entity according to the transmission resource block size indicated by the MAC layer each time, and whether to deliver the RLC SDU that needs to be segmented to the MAC layer after being processed by the RLC UM entity. Therefore, there is a one-way data flow transmission between the RLC TM entity and the RLCUM entity.

[0330] For the receiving end, the MAC layer distinguishes different data types and sends them to the RLC TM entity and the RLC UM entity respectively. The two entities can each submit the complete RLC SDU to the PDCP layer for processing. Therefore, the RLC UM entity can have a direct upward submission channel connected to the PDCP, but does not need to directly connect to the downward delivery channel of the MAC layer.

[0331] For the transmitting end, the behavior from the PDCP entity to the MAC entity may include the following steps:

[0332] Step 31: The PDCP entity still corresponds to one RB. After being processed by the PDCP layer, the high-level data packet forms a PDCP PDU and is sent to the corresponding RLC TM entity.

[0333] Step 32: After receiving the PDCP PDU, the RLC TM entity stores it in the transmission buffer as an RLC SDU according to the first-in-first-out principle, waits for the MAC layer to indicate the transmission resource size, and then organizes the data packet for transmission;

[0334] When the MAC layer obtains transmission resources and allocates resource size for the RB according to the logical channel priority LCP operation, the RLC TM entity organizes the data packet to be sent to the MAC layer according to the resource size indicated by the MAC layer. When the data packet sent in the arrival order is a complete RLC SDU, it is directly sent to the MAC layer, which is equivalent to the complete RLC SDU passing through the RLC TM entity, and does not require any processing or adding headers. When the remaining resource size is not enough to accommodate a new RLC SDU, the RLC SDU needs to be segmented. At this time, the RLC SDU is sent to the RLC UM entity to perform segmentation and add RLC header operations. Then the RLC PDU composed of the RLC SDU segments is sent to the MAC layer.

[0335] It should be noted that the complete RLC SDU and the segmented RLC SDU need to be sent to the MAC layer through different inter-node paths or carry different indications so that the MAC layer can distinguish between the two types of data.

[0336] When there are remaining RLC SDU segments in the RLC UM entity, the next time a new transport block indicated by the MAC layer arrives, these remaining segments should be processed first, and after all the segments are sent, other new complete RLC SDUs or new RLC SDU segments should be considered. That is, it is necessary to ensure that the remaining RLC SDU segments stored in the RLC UM entity have a higher sending priority than the complete RLC SDU in the RLC TM entity sending buffer.

[0337] When a MAC transmission resource block size is indicated, the data packet sent by the RLC TM entity and the RLC UM entity to the MAC entity at one time contains at most two RLC SDU segments (located at the first block position and the last block position respectively) and N complete RLC SDUs in between the two (N is an integer such as 0, 1, 2, 3, etc.).

[0338] The example in the second embodiment is also applicable to this embodiment. The collaboration between the TM module and the UM module in the second embodiment can be replaced by the RLC TM entity and the RLC UM in this embodiment to ultimately achieve a similar data processing effect, which will not be repeated here.

[0339] In particular, different from the processing of different modules in the second embodiment, since the present embodiment processes TM data and UM data respectively by two entities, the processing order needs to be noted. The two entities can only be processed serially, and it is necessary to ensure that RLC SDU data and RLC SDU segmented data can reach the MAC entity in order, that is, RLC SDU segmented data can only be located at the first block position or the last block position of a data transmission, and cannot be located in the middle position, that is, in the resource data block requested by the MAC layer once, the data located at the first position of the data block can be RLC SDU segmented data or RLC SDU data, the middle N data are RLC SDU data, and the data at the last position can be RLC SDU segmented data or RLC SDU data, and the order cannot be disordered. The order is ensured by the serial execution and interaction of the RLC TM entity and the RLC UM entity.

[0340] Step 33: After receiving the RLC PDU from the RLC TM entity or the RLC UM entity, the MAC layer concatenates the RLC PDUs in sequence and distinguishes the data packets from the RLC TM entity and the RLC UM entity in the following manner:

[0341] Mode 1: Different logical channel identifications (LCIDs) are used to distinguish RLC SDU data (i.e., data from the RLC TM entity) and RLC SDU segment data (i.e., data from the RLC UM entity);

[0342] Mode 2: For RLC SDU data (i.e., data from the RLC TM entity) and RLC SDU segment data (i.e., data from the RLC UM entity), although the same LCID is used, a 1-bit indication information in the MAC subheader is used to indicate whether the data packet is RLC SDU data or RLC SDU segment data. For example, a 1-bit indication information of 0 represents complete RLC SDU data, and a 1-bit indication information of 1 represents RLC SDU segment data, or vice versa; or, the 1-bit indication information is used to indicate whether it is RLC SDU data; or, the 1-bit indication information is used to indicate whether it is RLC SDU segment data; and so on. Different data types can be distinguished by the 1-bit indication information.

[0343] For the receiving end, the behavior from the MAC entity to the PDCP entity includes the following steps:

[0344] Step 41: The MAC layer distinguishes the received data packets according to the packet format and the logical channel identifier, and distinguishes different data from the TM entity and the UM entity of different logical channels, as follows:

[0345] Mode 1: When the data of the RLC TM entity and UM entity belonging to the same bearer are distinguished by different LCIDs, the MAC layer can distinguish which bearer TM entity or UM entity the data packet comes from by reading the different LCIDs in the subheader, and send the data to the corresponding entity;

[0346] Mode 2: When the data of the RLC TM entity and UM entity of the same bearer use the same LCID, but use different values ​​of the 1-bit indication information in the subheader field to distinguish the RLC SDU data or RLC SDU segment data, the corresponding bearer is found by the LCID, and then the corresponding RLC entity is found by the value of the 1-bit indication information, and the data is sent to the corresponding entity;

[0347] Step 42: For the RLC entity, if the TM entity receives the data, the data must be a complete RLC SDU, so it is directly delivered to the corresponding PDCP layer. If the UM entity receives the data, the UM entity receiving end reassembles the data packet segments according to the SN and segment SI, SO and other tags in the RLC header format, and immediately delivers the successfully reassembled RLC SDU to the corresponding PDCP layer. For the segments that meet certain conditions, such as the reordering timer timeout, the segments that are still not successfully reassembled are deleted.

[0348] Step 43: For the PDCP PDU received by the RLC entity, if it is configured that it does not need to be delivered in sequence, the PDCP layer directly delivers it to the upper layer after processing by the PDCP layer. The processing by the PDCP layer may include: removing the header, decompressing the security operation, decompressing the header, etc. If it is configured that it needs to be delivered in sequence, the data packets are reordered according to the COUNT value according to the SN carried in the PDCP header and the locally maintained HFN, as well as the window mechanism and other rules, and the PDCP SDU is delivered to the upper layer in ascending order.

[0349] From the above receiving side processing flow, it can be seen that the RLC TM entity and the UM entity respectively deliver the RLC SDU to the PDCP layer, and the functions of reordering and in-order delivery of the data are handed over to the PDCP layer to complete, which is not only efficient but also has a small header overhead and can meet the service QoS requirements.

[0350] The embodiment of the present application proposes a method for efficiently processing data packets, so that the sending end can adopt a more efficient processing method for data packets that do not need to be segmented, thereby ensuring the high efficiency of UE data transmission, reducing the UE processing overhead and header overhead while ensuring the data transmission effect, and improving the system efficiency.

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

[0352] See also Fig.12 , Fig.12 is a structural diagram of a data packet transmission device provided in an embodiment of the present application, wherein a terminal includes the data packet transmission device, such as Fig.12 As shown, the data packet transmission device 300 includes:

[0353] The first execution module 301 is configured to execute a first operation, wherein the first operation includes at least one of the following:

[0354] Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments;

[0355] A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

[0356] Optionally, the first operation further includes at least one of the following:

[0357] Sending a third data packet based on the unacknowledged mode UM, wherein the third data packet is a data packet that needs to be transmitted in segments;

[0358] A fourth data packet is received based on the UM, where the fourth data packet is a data packet that needs to be transmitted in segments.

[0359] Optionally, the sending the first data packet based on the TM includes: sending the first data packet through a TM module in the RLC entity; or

[0360] The receiving the second data packet based on the TM comprises: receiving the second data packet through a TM module in the RLC entity; or

[0361] The sending of the third data packet based on UM includes: sending the third data packet through a UM module in an RLC entity; or

[0362] The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through a UM module in the RLC entity.

[0363] Optionally, the sending the first data packet based on the TM includes: sending the first data packet through an RLC TM entity; or

[0364] The receiving the second data packet based on the TM comprises: receiving the second data packet through an RLC TM entity; or

[0365] The sending of the third data packet based on UM includes: sending the third data packet through an RLC UM entity; or

[0366] The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through an RLC UM entity.

[0367] Optionally, when the terminal is a transmitting end, the device further includes:

[0368] A first determining module, used to determine resources to be transmitted;

[0369] A second determining module, configured to determine N data packets to be sent in the sending buffer of the terminal based on a preset sending order and a resource block size of the resource to be transmitted, where N is a positive integer;

[0370] The third determination module is used to determine the first data packet or the third data packet among the N data packets to be sent based on the data packet size of the N data packets to be sent and the resource block size of the resources to be transmitted.

[0371] Optionally, the first data packet to be sent among the N data packets to be sent belongs to the first data packet or the third data packet, wherein:

[0372] In a case where the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resource to be transmitted, the data packets to be sent except the first data packet to be sent among the N data packets to be sent belong to the first data packet;

[0373] or

[0374] When the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted, the Nth data packet to be sent among the N data packets to be sent belongs to the third data packet, and the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent belong to the first data packet.

[0375] Optionally, the device further comprises:

[0376] The first sending module is used to send target capability information to a network side device, wherein the target capability information is used to indicate whether the terminal supports a data transmission mode corresponding to the first operation.

[0377] Optionally, the target capability information includes at least one of the following:

[0378] Indication information indicating whether the terminal supports TM data transmission;

[0379] Capability information of TM data transmission supported by the terminal.

[0380] Optionally, the device further comprises:

[0381] The first receiving module is used to receive a first configuration sent by a network side device, where the first configuration is a configuration for performing the first operation.

[0382] Optionally, the first configuration is used to configure at least one of the following:

[0383] Whether the terminal supports TM data transmission;

[0384] Whether all data radio bearers (DRBs) of the terminal support TM transmission;

[0385] Whether each DRB of the terminal supports TM transmission;

[0386] TM data transmission method.

[0387] Optionally, when the terminal is a transmitting end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the first execution module is further used for at least one of the following:

[0388] Implement a first-in-first-out routing mechanism for data packets, or process data packets according to their priority;

[0389] Using different target indication information to indicate the first data packet and the third data packet;

[0390] Performing cascade processing on the first data packet and the third data packet through a media access control MAC layer;

[0391] The first data packet and the third data packet are multiplexed through the MAC layer.

[0392] Optionally, when the terminal is a receiving end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the first execution module is further used for at least one of the following:

[0393] Determining, based on the target indication information, that the received data packet is the second data packet or the fourth data packet;

[0394] Delivering the second data packet directly to the Packet Data Convergence Protocol PDCP layer;

[0395] reassembling the fourth data packet and delivering the reassembled data packet to the PDCP layer;

[0396] The second data packet and the fourth data packet are reordered through the PDCP layer.

[0397] Optionally, the target indication information is 1-bit indication information, or the target indication information is a logical channel identifier LCID.

[0398] Optionally, the device further comprises:

[0399] A second receiving module, configured to receive a second configuration sent by the network side device, where the second configuration is a reconfiguration of the terminal by the network side device;

[0400] The first execution module is specifically used for:

[0401] In the case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a sending end, an initialization operation is performed on a sending variable, and a sending process corresponding to the first operation is performed on a first unsent data packet after the reconfiguration; or

[0402] In a case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a receiving end, an initialization operation is performed on a receiving variable, and the data packet before reconfiguration is delivered to the PDCP layer, and the data packet after reconfiguration is received and processed corresponding to the first operation.

[0403] Optionally, the device further comprises a first processing module, configured to perform at least one of the following:

[0404] In the case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the terminal is a sending end, an initialization operation is performed on a sending variable, and a sending process corresponding to the second configuration is performed on a first unsent data packet after reconfiguration;

[0405] In a case where the first configuration is used to configure the target switch to be turned on, and the second configuration is used to configure the target switch not to be turned on, if the terminal is a receiving end, initializing a receiving variable, delivering a data packet before reconfiguration to the PDCP layer, and performing receiving processing corresponding to the second configuration on a data packet after reconfiguration;

[0406] The target switch is a switch used to control whether to enable the data transmission mode corresponding to the first operation.

[0407] The data packet transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0408] The data packet transmission device provided in the embodiment of the present application can achieve Figure 5 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0409] See also Fig.13 , Fig.13 is a structural diagram of a data packet transmission device provided in an embodiment of the present application, and a network side device includes the data packet transmission device, such as Fig.13 As shown, the data packet transmission device 400 includes:

[0410] The second execution module 401 is configured to execute a second operation, where the second operation includes at least one of the following:

[0411] Sending a second data packet based on the transparent mode TM, where the second data packet is a data packet that does not need to be transmitted in segments;

[0412] A first data packet is received based on the TM, where the first data packet is a data packet that does not need to be transmitted in segments.

[0413] Optionally, the second operation further includes at least one of the following:

[0414] Sending a fourth data packet based on the unacknowledged mode UM, wherein the fourth data packet is a data packet that needs to be transmitted in segments;

[0415] A third data packet is received based on the UM, where the third data packet is a data packet that needs to be transmitted in segments.

[0416] Optionally, the sending the second data packet based on the TM comprises: sending the second data packet through a TM module in the RLC entity; or,

[0417] The receiving the first data packet based on the TM comprises: receiving the first data packet through a TM module in the RLC entity; or

[0418] The sending of the fourth data packet based on UM includes: sending the fourth data packet through a UM module in an RLC entity; or

[0419] The receiving the third data packet based on the UM includes: receiving the third data packet through a UM module in the RLC entity.

[0420] Optionally, the sending the second data packet based on the TM includes: sending the second data packet through an RLC TM entity; or

[0421] The receiving the first data packet based on the TM comprises: receiving the first data packet through an RLC TM entity; or

[0422] The sending of the fourth data packet based on UM includes: sending the fourth data packet through an RLC UM entity; or

[0423] The receiving the third data packet based on UM includes: receiving the third data packet through an RLC UM entity.

[0424] Optionally, when the network side device is a sending end, the apparatus further includes:

[0425] A fourth determination module, used to determine resources to be transmitted;

[0426] A fifth determination module, configured to determine N data packets to be sent in the sending buffer of the network side device based on a preset sending order and a resource block size of the resource to be transmitted, where N is a positive integer;

[0427] The sixth determination module is used to determine the second data packet or the fourth data packet among the N data packets to be sent based on the data packet size of the N data packets to be sent and the resource block size of the resources to be transmitted.

[0428] Optionally, the first data packet to be sent among the N data packets to be sent belongs to the second data packet or the fourth data packet, wherein:

[0429] In a case where the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resource to be transmitted, the data packets to be sent among the N data packets to be sent except the first data packet to be sent belong to the second data packet;

[0430] or

[0431] When the sum of the data packet sizes and corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted, the Nth data packet to be sent among the N data packets to be sent belongs to the fourth data packet, and the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent belong to the second data packet.

[0432] Optionally, the device further comprises:

[0433] The third receiving module is used to receive target capability information sent by the terminal, wherein the target capability information is used to indicate whether the terminal supports the data transmission mode corresponding to the second operation.

[0434] Optionally, the target capability information includes at least one of the following:

[0435] Indication information indicating whether the terminal supports TM data transmission;

[0436] Capability information of TM data transmission supported by the terminal.

[0437] Optionally, the device further comprises:

[0438] The second sending module is used to send a first configuration to the terminal, where the first configuration is a configuration for performing the second operation.

[0439] Optionally, the first configuration is used to configure at least one of the following:

[0440] Whether the terminal supports TM data transmission;

[0441] Whether all data radio bearers (DRBs) of the terminal support TM transmission;

[0442] Whether each DRB of the terminal supports TM transmission;

[0443] TM data transmission method.

[0444] Optionally, when the network side device is a transmitting end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the second execution module is further used for at least one of the following:

[0445] Implement a first-in-first-out routing mechanism for data packets, or process data packets according to their priority;

[0446] Using different target indication information to indicate the second data packet and the fourth data packet;

[0447] Performing cascade processing on the second data packet and the fourth data packet through a media access control MAC layer;

[0448] The second data packet and the fourth data packet are multiplexed through the MAC layer.

[0449] Optionally, when the network side device is a receiving end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the second execution module is further used for at least one of the following:

[0450] Determining, based on the target indication information, whether the received data packet is the first data packet or the third data packet;

[0451] Delivering the first data packet directly to the Packet Data Convergence Protocol (PDCP) layer;

[0452] Reassembling the third data packet and delivering the reassembled data packet to the PDCP layer;

[0453] The first data packet and the third data packet are reordered through the PDCP layer.

[0454] Optionally, the target indication information is 1-bit indication information, or the target indication information is a logical channel identifier LCID.

[0455] Optionally, the device further comprises:

[0456] a fourth receiving module, configured to send a second configuration to the terminal, where the second configuration is a reconfiguration of the terminal by the network side device;

[0457] The second execution module is specifically used for at least one of the following:

[0458] In a case where the first configuration is used to configure turning on or off a target switch, and the second configuration is used to configure turning on the target switch, if the network side device is a sending end, the network side device performs an initialization operation on a sending variable, and the network side device performs a sending process corresponding to the second operation on the first unsent data packet after the reconfiguration; or

[0459] In a case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the network side device is a receiving end, the network side device performs an initialization operation on a receiving variable, and the network side device delivers the data packet before reconfiguration to the PDCP layer, and performs receiving processing corresponding to the second operation on the data packet after reconfiguration.

[0460] Optionally, the device further comprises a second processing module, configured to perform at least one of the following:

[0461] In the case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the network side device is a sending end, the network side device performs an initialization operation on a sending variable, and the network side device performs a sending process corresponding to the second configuration on the first unsent data packet after the reconfiguration;

[0462] In the case where the first configuration is used to configure the target switch to be turned on, and the second configuration is used to configure the target switch not to be turned on, if the network side device is a receiving end, the network side device performs an initialization operation on the receiving variable, and the network side device delivers the data packet before the reconfiguration to the PDCP layer, and performs receiving processing corresponding to the second configuration on the data packet after the reconfiguration;

[0463] The target switch is a switch used to control whether to enable the data transmission mode corresponding to the second operation.

[0464] The data packet transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0465] The data packet transmission device provided in the embodiment of the present application can achieve Figure 6 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0466] Alternatively, if Fig.14 As shown, the embodiment of the present application also provides a communication device 500, including a processor 501 and a memory 502, and the memory 502 stores a program or instruction that can be run on the processor 501. For example, when the communication device 500 is a terminal, the program or instruction is executed by the processor 501 to implement the various steps of the above-mentioned data packet transmission method embodiment applied to the terminal, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 500 is a network side device, the program or instruction is executed by the processor 501 to implement the various steps of the above-mentioned data packet transmission method embodiment applied to the network side device, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0467] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 5 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect.

[0468] Specifically, Fig.15A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0469] The terminal 600 includes but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609 and at least some of the components of a processor 610.

[0470] Those skilled in the art will appreciate that the terminal 600 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 610 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.15 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0471] It should be understood that in the embodiment of the present application, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042, and the GPU 6041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes a touch panel 6071 and at least one of other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0472] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 601 can transmit the data to the processor 610 for processing; in addition, the RF unit 601 can send uplink data to the network side device. Generally, the RF unit 601 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0473] The memory 609 can be used to store software programs or instructions and various data. The memory 609 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 609 may include a volatile memory or a non-volatile memory, or the memory 609 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 609 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0474] The processor 610 may include one or more processing units; optionally, the processor 610 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 610.

[0475] The processor 610 is used for:

[0476] Perform a first operation, where the first operation includes at least one of the following:

[0477] Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments;

[0478] A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

[0479] Optionally, the first operation further includes at least one of the following:

[0480] Sending a third data packet based on the unacknowledged mode UM, wherein the third data packet is a data packet that needs to be transmitted in segments;

[0481] A fourth data packet is received based on the UM, where the fourth data packet is a data packet that needs to be transmitted in segments.

[0482] Optionally, the sending the first data packet based on the TM includes: sending the first data packet through a TM module in the RLC entity; or

[0483] The receiving the second data packet based on the TM comprises: receiving the second data packet through a TM module in the RLC entity; or

[0484] The sending of the third data packet based on UM includes: sending the third data packet through a UM module in an RLC entity; or

[0485] The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through a UM module in the RLC entity.

[0486] Optionally, the sending the first data packet based on the TM includes: sending the first data packet through an RLC TM entity; or

[0487] The receiving the second data packet based on the TM comprises: receiving the second data packet through an RLC TM entity; or

[0488] The sending of the third data packet based on UM includes: sending the third data packet through an RLC UM entity; or

[0489] The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through an RLC UM entity.

[0490] Optionally, when the terminal is a transmitting end, the processor 610 is further configured to:

[0491] Determine the resources to be transmitted;

[0492] Determine N data packets to be sent in the sending buffer of the terminal based on a preset sending order and a resource block size of the resource to be transmitted, where N is a positive integer;

[0493] Based on the data packet sizes of the N data packets to be sent and the resource block size of the resources to be transmitted, the first data packet or the third data packet among the N data packets to be sent is determined.

[0494] Optionally, the first data packet to be sent among the N data packets to be sent belongs to the first data packet or the third data packet, wherein:

[0495] In a case where the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resource to be transmitted, the data packets to be sent except the first data packet to be sent among the N data packets to be sent belong to the first data packet;

[0496] or

[0497] When the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted, the Nth data packet to be sent among the N data packets to be sent belongs to the third data packet, and the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent belong to the first data packet.

[0498] Optionally, the radio frequency unit 601 is used for:

[0499] Sending target capability information to a network side device, wherein the target capability information is used to indicate whether the terminal supports a data transmission mode corresponding to the first operation.

[0500] Optionally, the target capability information includes at least one of the following:

[0501] Indication information indicating whether the terminal supports TM data transmission;

[0502] Capability information of TM data transmission supported by the terminal.

[0503] Optionally, the radio frequency unit 601 is used for:

[0504] A first configuration sent by a network-side device is received, where the first configuration is a configuration for performing the first operation.

[0505] Optionally, the first configuration is used to configure at least one of the following:

[0506] Whether the terminal supports TM data transmission;

[0507] Whether all data radio bearers (DRBs) of the terminal support TM transmission;

[0508] Whether each DRB of the terminal supports TM transmission;

[0509] TM data transmission method.

[0510] Optionally, when the terminal is a transmitting end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the processor 610 is further configured to perform at least one of the following:

[0511] Implement a first-in-first-out routing mechanism for data packets, or process data packets according to their priority;

[0512] Using different target indication information to indicate the first data packet and the third data packet;

[0513] Performing cascade processing on the first data packet and the third data packet through a media access control MAC layer;

[0514] The first data packet and the third data packet are multiplexed through the MAC layer.

[0515] Optionally, when the terminal is a receiving end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the processor 610 is further configured to perform at least one of the following:

[0516] Determining, based on the target indication information, that the received data packet is the second data packet or the fourth data packet;

[0517] Delivering the second data packet directly to the Packet Data Convergence Protocol PDCP layer;

[0518] reassembling the fourth data packet and delivering the reassembled data packet to the PDCP layer;

[0519] The second data packet and the fourth data packet are reordered through the PDCP layer.

[0520] Optionally, the target indication information is 1-bit indication information, or the target indication information is a logical channel identifier LCID.

[0521] Optionally, the radio frequency unit 601 is used for:

[0522] receiving a second configuration sent by the network side device, where the second configuration is a reconfiguration of the terminal by the network side device;

[0523] The processor 610 is specifically configured to:

[0524] In the case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a sending end, an initialization operation is performed on a sending variable, and a sending process corresponding to the first operation is performed on a first unsent data packet after the reconfiguration; or

[0525] In a case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a receiving end, an initialization operation is performed on a receiving variable, and the data packet before reconfiguration is delivered to the PDCP layer, and the data packet after reconfiguration is received and processed corresponding to the first operation.

[0526] Optionally, the method further comprises at least one of the following:

[0527] In the case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the terminal is a sending end, an initialization operation is performed on a sending variable, and a sending process corresponding to the second configuration is performed on a first unsent data packet after reconfiguration;

[0528] In a case where the first configuration is used to configure the target switch to be turned on, and the second configuration is used to configure the target switch not to be turned on, if the terminal is a receiving end, initializing a receiving variable, delivering a data packet before reconfiguration to the PDCP layer, and performing receiving processing corresponding to the second configuration on a data packet after reconfiguration;

[0529] The target switch is a switch used to control whether to enable the data transmission mode corresponding to the first operation.

[0530] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the method embodiment Figure 5 The related descriptions are the same or corresponding technical effects, and to avoid repetition, they will not be repeated here.

[0531] Specifically, the terminal of the embodiment of the present application also includes: instructions or programs stored in the memory 609 and executable on the processor 610, and the processor 610 calls the instructions or programs in the memory 609 to execute Fig.12 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0532] The embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 6 The steps of the method embodiment shown. This network side device embodiment corresponds to the above-mentioned data packet transmission method embodiment applied to the network side device, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the network side device embodiment and can achieve the same technical effect.

[0533] Specifically, the embodiment of the present application also provides a network side device. Fig.16As shown, the network side device 700 includes: an antenna 701, a radio frequency device 702, a baseband device 703, a processor 704 and a memory 705. The antenna 701 is connected to the radio frequency device 702. In the uplink direction, the radio frequency device 702 receives information through the antenna 701 and sends the received information to the baseband device 703 for processing. In the downlink direction, the baseband device 703 processes the information to be sent and sends it to the radio frequency device 702. The radio frequency device 702 processes the received information and sends it out through the antenna 701.

[0534] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 703, which includes a baseband processor.

[0535] The baseband device 703 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.16 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 705 through a bus interface to call the program in the memory 705 to execute the network device operations shown in the above method embodiment.

[0536] The network side device may further include a network interface 706, which is, for example, a Common Public Radio Interface (CPRI).

[0537] Specifically, the network side device 700 of the embodiment of the present application further includes: instructions or programs stored in the memory 705 and executable on the processor 704, and the processor 704 calls the instructions or programs in the memory 705 to execute Fig.13 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0538] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned data packet transmission method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0539] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk, etc. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0540] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data packet transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0541] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0542] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned data packet transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0543] An embodiment of the present application also provides a data packet transmission system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the data packet transmission method applied to the terminal as described above, and the network side device can be used to execute the steps of the data packet transmission method applied to the network side device as described above.

[0544] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0545] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, it can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable the terminal or network side device to execute the method described in each embodiment of the present application.

[0546] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A data packet transmission method, characterized in that: include: The terminal performs a first operation, where the first operation includes at least one of the following: Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments; A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

2. The method according to claim 1, characterized in that: The first operation further includes at least one of the following: Sending a third data packet based on the unacknowledged mode UM, wherein the third data packet is a data packet that needs to be transmitted in segments; A fourth data packet is received based on the UM, where the fourth data packet is a data packet that needs to be transmitted in segments.

3. The method according to claim 1 or 2, characterized in that: The sending of the first data packet based on the TM includes: sending the first data packet through a TM module in the RLC entity; or The receiving the second data packet based on the TM comprises: receiving the second data packet through a TM module in the RLC entity; or The sending of the third data packet based on UM includes: sending the third data packet through a UM module in an RLC entity; or The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through a UM module in the RLC entity.

4. The method according to claim 1 or 2, characterized in that: The sending of the first data packet based on the TM includes: sending the first data packet through an RLC TM entity; or The receiving the second data packet based on the TM comprises: receiving the second data packet through an RLC TM entity; or The sending of the third data packet based on UM includes: sending the third data packet through an RLC UM entity; or The receiving the fourth data packet based on the UM includes: receiving the fourth data packet through an RLC UM entity.

5. The method according to any one of claims 2 to 4, characterized in that: In the case where the terminal is a transmitting end, before the terminal performs the first operation, the method further includes: Determine the resources to be transmitted; Determine N data packets to be sent in the sending buffer of the terminal based on a preset sending order and a resource block size of the resource to be transmitted, where N is a positive integer; Based on the data packet sizes of the N data packets to be sent and the resource block size of the resources to be transmitted, the first data packet or the third data packet among the N data packets to be sent is determined.

6. The method according to claim 5, characterized in that The first data packet to be sent among the N data packets to be sent belongs to the first data packet or the third data packet, wherein: In a case where the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resource to be transmitted, the data packets to be sent except the first data packet to be sent among the N data packets to be sent belong to the first data packet; or When the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted, the Nth data packet to be sent among the N data packets to be sent belongs to the third data packet, and the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent belong to the first data packet.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The terminal sends target capability information to a network side device, wherein the target capability information is used to indicate whether the terminal supports a data transmission mode corresponding to the first operation.

8. The method according to claim 7, characterized in that The target capability information includes at least one of the following: Indication information indicating whether the terminal supports TM data transmission; Capability information of TM data transmission supported by the terminal.

9. The method according to any one of claims 1 to 8, characterized in that Before the terminal performs the first operation, the method further includes: The terminal receives a first configuration sent by a network-side device, where the first configuration is a configuration for performing the first operation.

10. The method according to claim 9, characterized in that The first configuration is used to configure at least one of the following: Whether the terminal supports TM data transmission; Whether all data radio bearers (DRBs) of the terminal support TM transmission; Whether each DRB of the terminal supports TM transmission; TM data transmission method.

11. The method according to claim 9 or 10, characterized in that: In a case where the terminal is a transmitting end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the terminal performs a first operation, further comprising at least one of the following: The terminal executes a first-in-first-out routing mechanism for data packets, or processes data packets according to their priority; The terminal uses different target indication information to indicate the first data packet and the third data packet; The terminal performs cascade processing on the first data packet and the third data packet through a media access control MAC layer; The terminal multiplexes the first data packet and the third data packet through the MAC layer.

12. The method according to claim 9 or 10, characterized in that: In a case where the terminal is a receiving end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the terminal performs a first operation, further comprising at least one of the following: The terminal determines, based on the target indication information, that the received data packet is the second data packet or the fourth data packet; The terminal directly delivers the second data packet to the Packet Data Convergence Protocol PDCP layer; The terminal reassembles the fourth data packet and delivers the reassembled data packet to the PDCP layer; The terminal reorders the second data packet and the fourth data packet through the PDCP layer.

13. The method according to claim 11 or 12, characterized in that: The target indication information is 1-bit indication information, or the target indication information is a logical channel identifier LCID.

14. The method according to any one of claims 9 to 13, characterized in that: After the terminal receives the first configuration sent by the network side device, the method further includes: The terminal receives a second configuration sent by the network side device, where the second configuration is a reconfiguration of the terminal by the network side device; The terminal performs a first operation, including: In the case where the first configuration is used to configure turning on or off a target switch, and the second configuration is used to configure turning on the target switch, if the terminal is a transmitting end, the terminal performs an initialization operation on a transmission variable, and the terminal performs a transmission process corresponding to the first operation on a first unsent data packet after reconfiguration; or In a case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the terminal is a receiving end, the terminal performs an initialization operation on a receiving variable, and the terminal delivers the data packet before reconfiguration to the PDCP layer, and performs reception processing corresponding to the first operation on the data packet after reconfiguration.

15. The method according to claim 14, characterized in that The method further comprises at least one of the following: In the case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the terminal is a sending end, the terminal performs an initialization operation on a sending variable, and the terminal performs a sending process corresponding to the second configuration on the first unsent data packet after the reconfiguration; In a case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the terminal is a receiving end, the terminal performs an initialization operation on a receiving variable, and the terminal delivers a data packet before reconfiguration to the PDCP layer, and performs reception processing corresponding to the second configuration on a data packet after reconfiguration; The target switch is a switch used to control whether to enable the data transmission mode corresponding to the first operation.

16. A data packet transmission method, characterized in that: include: The network-side device performs a second operation, where the second operation includes at least one of the following: Sending a second data packet based on the transparent mode TM, where the second data packet is a data packet that does not need to be transmitted in segments; A first data packet is received based on the TM, where the first data packet is a data packet that does not need to be transmitted in segments.

17. The method according to claim 16, characterized in that The second operation further includes at least one of the following: Sending a fourth data packet based on the unacknowledged mode UM, wherein the fourth data packet is a data packet that needs to be transmitted in segments; A third data packet is received based on the UM, where the third data packet is a data packet that needs to be transmitted in segments.

18. The method according to claim 16 or 17, characterized in that The sending of the second data packet based on the TM comprises: sending the second data packet through a TM module in the RLC entity; or, The receiving the first data packet based on the TM comprises: receiving the first data packet through a TM module in the RLC entity; or The sending of the fourth data packet based on UM includes: sending the fourth data packet through a UM module in an RLC entity; or The receiving the third data packet based on the UM includes: receiving the third data packet through a UM module in the RLC entity.

19. The method according to claim 16 or 17, characterized in that The sending of the second data packet based on the TM comprises: sending the second data packet through an RLC TM entity; or The receiving the first data packet based on the TM comprises: receiving the first data packet through an RLC TM entity; or The sending of the fourth data packet based on UM includes: sending the fourth data packet through an RLC UM entity; or The receiving the third data packet based on UM includes: receiving the third data packet through an RLC UM entity.

20. The method according to any one of claims 17 to 19, characterized in that In the case where the network side device is a transmitting end, before the network side device performs the second operation, the method further includes: Determine the resources to be transmitted; Determine N data packets to be sent in the sending buffer of the network side device based on a preset sending order and a resource block size of the resource to be transmitted, where N is a positive integer; The second data packet or the fourth data packet among the N data packets to be sent is determined based on the data packet sizes of the N data packets to be sent and the resource block size of the resources to be transmitted.

21. The method according to claim 20, characterized in that The first data packet to be sent among the N data packets to be sent belongs to the second data packet or the fourth data packet, wherein, In a case where the sum of the data packet sizes and the corresponding data header sizes of the N data packets to be sent is less than or equal to the resource block size of the resource to be transmitted, the data packets to be sent among the N data packets to be sent except the first data packet to be sent belong to the second data packet; or When the sum of the data packet sizes and corresponding data header sizes of the N data packets to be sent is greater than the resource block size of the resources to be transmitted, the Nth data packet to be sent among the N data packets to be sent belongs to the fourth data packet, and the data packets to be sent among the N data packets to be sent except the first data packet to be sent and the Nth data packet to be sent belong to the second data packet.

22. The method according to any one of claims 16 to 21, characterized in that The method further comprises: The network side device receives target capability information sent by the terminal, wherein the target capability information is used to indicate whether the terminal supports a data transmission mode corresponding to the second operation.

23. The method according to claim 22, characterized in that The target capability information includes at least one of the following: Indication information indicating whether the terminal supports TM data transmission; Capability information of TM data transmission supported by the terminal.

24. The method according to any one of claims 16 to 23, characterized in that Before the network side device performs the second operation, the method further includes: The network side device sends a first configuration to the terminal, where the first configuration is a configuration for performing the second operation.

25. The method according to claim 24, characterized in that The first configuration is used to configure at least one of the following: Whether the terminal supports TM data transmission; Whether all data radio bearers (DRBs) of the terminal support TM transmission; Whether each DRB of the terminal supports TM transmission; TM data transmission method.

26. The method according to claim 24 or 25, characterized in that In a case where the network side device is a transmitting end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the network side device performs a second operation, further comprising at least one of the following: The network side device executes a first-in-first-out routing mechanism for data packets, or processes data packets according to their priority; The network side device uses different target indication information to indicate the second data packet and the fourth data packet; The network side device performs cascade processing on the second data packet and the fourth data packet through the media access control MAC layer; The network side device multiplexes the second data packet and the fourth data packet through the MAC layer.

27. The method according to claim 24 or 25, characterized in that In a case where the network side device is a receiving end and the first configuration is used to configure at least one DRB of the terminal to support TM transmission, the network side device performs a second operation, further comprising at least one of the following: The network side device determines, based on the target indication information, that the received data packet is the first data packet or the third data packet; The network side device directly delivers the first data packet to the Packet Data Convergence Protocol PDCP layer; The network side device reassembles the third data packet and delivers the reassembled data packet to the PDCP layer; The network side device reorders the first data packet and the third data packet through the PDCP layer.

28. The method according to claim 26 or 27, characterized in that The target indication information is 1-bit indication information, or the target indication information is a logical channel identifier LCID.

29. The method according to any one of claims 24 to 28, characterized in that After the network side device sends the first configuration to the terminal, the method further includes: The network side device sends a second configuration to the terminal, where the second configuration is a reconfiguration of the terminal by the network side device; The network side device performs a second operation, including: In a case where the first configuration is used to configure turning on or off a target switch, and the second configuration is used to configure turning on the target switch, if the network side device is a sending end, the network side device performs an initialization operation on a sending variable, and the network side device performs a sending process corresponding to the second operation on the first unsent data packet after the reconfiguration; or In a case where the first configuration is used to configure whether to turn on or off a target switch, and the second configuration is used to configure to turn on the target switch, if the network side device is a receiving end, the network side device performs an initialization operation on a receiving variable, and the network side device delivers the data packet before reconfiguration to the PDCP layer, and performs receiving processing corresponding to the second operation on the data packet after reconfiguration.

30. The method according to claim 29, characterized in that The method further comprises at least one of the following: In the case where the first configuration is used to configure to turn on a target switch, and the second configuration is used to configure not to turn on the target switch, if the network side device is a sending end, the network side device performs an initialization operation on a sending variable, and the network side device performs a sending process corresponding to the second configuration on the first unsent data packet after the reconfiguration; In the case where the first configuration is used to configure the target switch to be turned on, and the second configuration is used to configure the target switch not to be turned on, if the network side device is a receiving end, the network side device performs an initialization operation on the receiving variable, and the network side device delivers the data packet before the reconfiguration to the PDCP layer, and performs receiving processing corresponding to the second configuration on the data packet after the reconfiguration; The target switch is a switch used to control whether to enable the data transmission mode corresponding to the second operation.

31. A data packet transmission device, characterized in that: The terminal includes the data packet transmission device, and the device includes: The first execution module is configured to execute a first operation, wherein the first operation includes at least one of the following: Sending a first data packet based on a transparent mode TM, where the first data packet is a data packet that does not need to be transmitted in segments; A second data packet is received based on the TM, where the second data packet is a data packet that does not need to be transmitted in segments.

32. A data packet transmission device, characterized in that: The network side device includes the data packet transmission device, and the device includes: The second execution module is configured to execute a second operation, where the second operation includes at least one of the following: Sending a second data packet based on the transparent mode TM, where the second data packet is a data packet that does not need to be transmitted in segments; A first data packet is received based on the TM, where the first data packet is a data packet that does not need to be transmitted in segments.

33. A terminal, characterized in that: It comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data packet transmission method according to any one of claims 1 to 15 are implemented.

34. A network side device, characterized in that: It includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data packet transmission method as described in any one of claims 16-30 are implemented.

35. A chip, characterized in that: The chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the data packet transmission method as described in any one of claims 1-15, or to implement the steps of the data packet transmission method as described in any one of claims 16-30.

36. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the data packet transmission method as described in any one of claims 1-15, or implements the steps of the data packet transmission method as described in any one of claims 16-30.

Images