Data transmission method and device, terminal and network side equipment

Abstract

The invention discloses a data transmission method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the data transmission method comprises the steps that the terminal sends a first data packet to the network side equipment in a first mode; wherein the first mode comprises at least one of the following modes: configuring an information sending mode based on the first header field size; based on the maximum transmission size limited by the second header field size configuration information, the data packet is sent in a segmented mode; wherein the header field size configured in the first header field size configuration information is greater than the header field size configured in the second header field size configuration information.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a data transmission method, apparatus, terminal, and network-side equipment. Background Technology

[0002] With the continuous advancement of technology, artificial intelligence (AI) and sensing technologies are being widely applied across various industries. Typically, the data generated during AI and sensing processes is transmitted directly between terminal and network devices through the business layer.

[0003] Traditional user data is typically transmitted in mobile networks via the traditional control plane (CP). Specifically, traditional user data is processed by the transmission network layer, such as Transmission Control Protocol (TCP) or Internet Protocol Address (IP), to ensure that the size of the transmitted data meets the maximum transmission limit of the Packet Data Convergence Protocol (PDCP) layer. Finally, the processed data is transmitted through the logical channel mapped by the PDCP layer.

[0004] However, in the future, the use of AI and sensing services will generate a large amount of data. If this data needs to be transmitted through mobile networks, the data packet size will be much larger than the size limited by the protocol, making it impossible to transmit giant data packets in mobile networks.

[0005] Therefore, how to transmit giant data packets in the traditional user transmission channel in mobile networks is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a data transmission method, apparatus, terminal, and network-side device that can transmit large data packets in traditional user transmission channels in mobile networks.

[0007] In a first aspect, a data transmission method is provided, executed by a terminal, the method comprising: the terminal sending a first data packet to a network-side device using a first method; wherein the first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending the data packet in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is greater than the header field size configured in the second header field size configuration information.

[0008] Secondly, a data transmission method is provided, executed by a terminal, the method comprising: the terminal receiving a second data packet from a network-side device according to a first header field size configuration information; or, the terminal receiving at least two third data packets from a network-side device according to the second header field size configuration information, and combining the at least two third data packets to obtain a fourth data packet; wherein the header field size configured in the first header field size configuration information is greater than the header field size configured in the second header field size configuration information.

[0009] Thirdly, a data transmission method is provided, executed by a network-side device, the method comprising: the network-side device sending a first data packet to a terminal using a first method; wherein the first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending the data packet in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0010] Fourthly, a data transmission method is provided, executed by a network-side device. The method includes: the network-side device receiving a second data packet from a terminal according to a first header field size configuration information; or, the network-side device receiving at least two third data packets from the terminal according to the second header field size configuration information, and combining the at least two third data packets to obtain a fourth data packet; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0011] Fifthly, a data transmission apparatus is provided, comprising: a sending module; the sending module being configured to send a first data packet to a network-side device using a first method; wherein the first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending the data packet in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0012] In a sixth aspect, a data transmission apparatus is provided, comprising: a receiving module and a processing module; the receiving module is configured to receive a second data packet from a network-side device according to a first header field size configuration information; or, the receiving module is configured to receive at least two third data packets from a network-side device according to the second header field size configuration information; the processing module is configured to combine the at least two third data packets to obtain a fourth data packet; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0013] A seventh aspect provides a data transmission apparatus, comprising: a sending module; the sending module being configured to send a first data packet to a terminal using a first method; wherein the first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending the data packet in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0014] Eighthly, a data transmission apparatus is provided, comprising: a receiving module and a processing module; the receiving module is configured to receive a second data packet from a terminal according to first header field size configuration information; or, the receiving module is configured to receive at least two third data packets from the terminal according to the second header field size configuration information; the processing module is configured to combine the at least two third data packets to obtain a fourth data packet; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0015] A ninth aspect provides a terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first or second aspect.

[0016] In a tenth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send a first data packet to a network-side device using a first method; wherein the first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending the data packet in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0017] Eleventhly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a second data packet from a network-side device according to a first header size configuration information; or, to receive at least two third data packets from a network-side device according to the second header size configuration information; the processor is configured to combine the at least two third data packets to obtain a fourth data packet; wherein the header size configured in the first header size configuration information is greater than the header size configured in the second header size configuration information.

[0018] In a twelfth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third or fourth aspect.

[0019] In a thirteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first data packet to a terminal using a first method; wherein the first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending the data packet in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

[0020] In a fourteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a second data packet from a terminal according to a first header field size configuration information; or, to receive at least two third data packets from a terminal according to the second header field size configuration information; the processor is configured to combine the at least two third data packets to obtain a fourth data packet; wherein the header field size configured in the first header field size configuration information is greater than the header field size configured in the second header field size configuration information.

[0021] In a fifteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect.

[0022] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first or second aspect, and the network-side device can be used to perform the steps of the method as described in the third aspect.

[0023] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0024] In a thirteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fourth aspect.

[0025] In this embodiment, the terminal uses a first method to send a first data packet to the network-side device. The first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending data packets in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information. In this solution, the terminal can transmit data packets in different ways. On the one hand, it can send data packets based on a larger header field size configured in the first header field size configuration information; on the other hand, it can segment data packets based on the maximum transmission size limited by the second header field size configuration information. This allows for more flexible and efficient support for the transmission of large data packets, improving data transmission efficiency and service experience, and ensuring system efficiency while enhancing data transmission performance. Attached Figure Description

[0026] Figure 1 This is a possible structural diagram of the communication system involved in the embodiments of this application;

[0027] Figure 2 This is a schematic diagram of a user plane protocol stack provided in an embodiment of this application;

[0028] Figure 3 This is a flowchart illustrating a data transmission method provided in an embodiment of this application;

[0029] Figure 4 This is a flowchart illustrating another data transmission method provided in an embodiment of this application;

[0030] Figure 5 This is a flowchart illustrating another data transmission method provided in an embodiment of this application;

[0031] Figure 6 This is a flowchart illustrating another data transmission method provided in an embodiment of this application;

[0032] Figure 7 This is one of the structural schematic diagrams of a data transmission device provided in the embodiments of this application;

[0033] Figure 8 This is a second schematic diagram of the structure of a data transmission device provided in an embodiment of this application;

[0034] Figure 9 This is the third schematic diagram of a data transmission device provided in the embodiments of this application;

[0035] Figure 10 This is one of the structural schematic diagrams of another data transmission device provided in the embodiments of this application;

[0036] Figure 11 This is a second schematic diagram of another data transmission device provided in the embodiments of this application;

[0037] Figure 12 This is one of the structural schematic diagrams of another data transmission device provided in the embodiments of this application;

[0038] Figure 13 This is a second schematic diagram of another data transmission device provided in the embodiments of this application;

[0039] Figure 14 This is a third schematic diagram of another data transmission device provided in the embodiments of this application;

[0040] Figure 15 This is one of the structural schematic diagrams of another data transmission device provided in the embodiments of this application;

[0041] Figure 16 This is a second schematic diagram of another data transmission device provided in the embodiments of this application;

[0042] Figure 17 This is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application;

[0043] Figure 18 This is a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application;

[0044] Figure 19 This is a schematic diagram of the hardware structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0045] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0046] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0047] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0048] The following explains the technical terms used in the embodiments of this application:

[0049] 1) Data processing in the user plane

[0050] In existing New Radio (NR) networks, such as Figure 2 As shown, the user plane protocol stack mainly includes: Medium Access Control (MAC) protocol, Radio Link Control (RLC) protocol, Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and Physical Layer (PHY).

[0051] The protocol stack consists of four layers: PHY (Layer 1, L1) and L2. The MAC layer is primarily responsible for mapping between logical and transport channels, prioritizing logical channels, multiplexing and demultiplexing MAC Service Data Units (SDUs), scheduling, and Hybrid Automatic Repeat Request (HARQ) operations. The RLC layer provides data transmission in three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM), and also provides segmentation and reassembly, Automatic Repeat Request (ARQ), and independent sequence numbers. The PDCP layer provides header compression and decompression, secure operation, separate bearer routing, and replication. The SDAP layer maps Quality of Service (QoS) flows to radio bearers and marks uplink and downlink packets with QoS flow identifiers.

[0052] In existing 5G NR systems, there are clear limitations on the size of a data packet. The PDCP layer specifies that the maximum supported size of a PDCP SDU is 9000 bytes, and the maximum supported size of a PDCP Control PDU is also 9000 bytes. This 9000-byte limit primarily stems from wired transmission networks. For example, Ethernet routers have Maximum Transport Unit (MTU) limitations of 1500 bytes, 9000 bytes, and 65535 bytes. Considering header overhead and transmission efficiency, 9000 bytes was the most commonly chosen size at the time.

[0053] For packet reassembly processing at the RLC layer, the Segment Offset (SO) field of the segmented data packet indicates the start position (number of bytes) of the current segment in the original SDU. Additionally, the RLC AM status report indicates the start (SOstart) and end (SOend) positions of lost data segments in the original SDU. These three SO-related fields are all 16 bits in size, meaning they can indicate a maximum length of 65535 bytes.

[0054] For MAC layer packet assembly, the MAC layer concatenates data packets from different logical channels or different data packets from the same logical channel. To distinguish each data packet and meet the needs of the receiving end for unpacking, it carries a length (L) field to indicate the length of each data packet. The L field has two lengths: 8 bits or 16 bits, with the F field taking values ​​of 0 or 1 corresponding to the two lengths of L. That is to say, the maximum data packet size currently supported by the MAC layer is 65535 bytes.

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

[0056] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0057] The data transmission method, apparatus, terminal, and network-side device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0058] Figure 3 The illustration shows a flowchart of a data transmission method provided in an embodiment of this application, as shown below. Figure 3 As shown, this data transmission method, applied to a terminal, may include the following step 201:

[0059] Step 201: The terminal uses the first method to send the first data packet to the network-side device.

[0060] In some embodiments of this application, the first approach described above includes at least one of the following:

[0061] The method of sending configuration information based on the first header field size;

[0062] The method of sending data packets in segments is based on the maximum transmission size limited by the second header field size configuration information.

[0063] In some embodiments of this application, the head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0064] In some embodiments of this application, the header field of the above-mentioned domain size configuration information includes at least one of the following: SO field, F field, L field.

[0065] The configuration information for the F field is used to indicate the size of the L field.

[0066] In one possible embodiment, the terminal sends a first data packet to the network-side device based on the method of sending the first header size configuration information.

[0067] In some embodiments of this application, since transmitting a large packet is more efficient and less costly than transmitting multiple small packets, and the size of the data packets that can be accommodated by the header field size of each protocol layer can be further improved, when bandwidth and speed are sufficient, in order to avoid segmentation and reassembly operations as much as possible, the header field structure size of L2 packets can be configured to a larger size by reconfiguring the network-side device, so that transmission can be performed when the data packet is smaller than or equal to the header field structure size.

[0068] It should be noted that for traditional user plane bearers, which are still limited by the MTU of the wired network, the existing size can be maintained; when processing packets, it is necessary to consider the coexistence of different services, as well as the handling of reconfiguration and switching processes.

[0069] Optionally, in some embodiments of this application, where the first method includes sending information based on the first header field size configuration information, the data transmission method provided in this application embodiment further includes step 301 before step 201:

[0070] Step 301: The terminal receives the first header domain size configuration information from the network-side device.

[0071] In some embodiments of this application, the above configuration information includes at least one of the following:

[0072] Instruction information, which indicates whether to use extended header field size;

[0073] The ordinal value of the header field size;

[0074] Head domain size.

[0075] In some embodiments of this application, the above-mentioned indication information can be a value, such as 0 or 1, or a truth value, such as true or false.

[0076] For example, when the above indication information is 0, the terminal is instructed not to use the extended header field size; when the above indication information is 1, the terminal is instructed to use the extended header field size.

[0077] For example, if the above indication is false, the terminal is instructed not to use the extended header field size; if the above indication is true, the terminal is instructed to use the extended header field size.

[0078] In some embodiments of this application, the sequence value of the above-mentioned head domain size can be the sequence value of the same head domain.

[0079] For example, if the index of the header field size is 1, it indicates the length of the first SO field; if the index of the header field size is 2, it indicates the length of the second SO field.

[0080] In some embodiments of this application, the above-mentioned header field size includes at least one of the following: the size of the SO field, and the length of the F field.

[0081] For example, the terminal selects the value of the L field according to the different lengths indicated by the F field.

[0082] For example, when the length of the F field is 1 bit, the value of the F field is 0, which means that the length of the L field being indicated is 8 bits; when the value of the F field is 1, it means that the length of the L field being indicated is 16 bits.

[0083] or,

[0084] When the length of the F field is 2 bits, the value of the F field is 00, which means that the length of the L field being indicated is 8 bits; the value of the F field is 01, which means that the length of the L field being indicated is 16 bits; the value of the F field is 10, which means that the length of the L field being indicated is 24 bits; the value of the F field is 11, which means that the length of the L field being indicated is 32 bits, and so on.

[0085] It should be noted that the correspondence between the values ​​of the F field and the length of the L field can be agreed upon by the protocol or defined by the user.

[0086] In another possible embodiment, the terminal segments the data packets based on the maximum transmission size limited by the second header field size configuration information.

[0087] For example, this embodiment introduces a new protocol layer function. This protocol layer function can be a newly added protocol layer function or a function added on the original protocol layer. It performs appropriate segmentation and reassembly processing for ultra-large data packets to adapt to the maximum transmission size limit of L2 packet and header field size configuration. The upper limit of segmentation can also be adaptively adjusted to adapt to link conditions, resource conditions, etc. to achieve higher processing efficiency. The segmentation needs to carry a certain segmentation identifier so that the receiving end can better perform reassembly and recovery processing, and handle possible packet loss and out-of-order situations such as handover and reconfiguration.

[0088] In one possible embodiment, the first method described above can be used alone or in combination with the other two methods. That is, after receiving the first header field size configuration from the network-side device, the terminal can reconfigure the header field sizes of each protocol layer. If the size of the data packet to be transmitted is still larger than the current header field size, the data packet needs to be segmented before transmission.

[0089] For example, the terminal sends information based on the size configuration of the first header field, which increases the size of the data packets that the lower layer can carry. However, this method is limited in some cases. For example, it is unclear what the actual upper limit of the data packets is, and the situation of the data packets may change. There may be new requirements in different scenarios, which may lead to the risk that the configured or estimated data packet size may not cover the full actual size.

[0090] Secondly, when the actual data packets are too large, a single transmission at the lower layer cannot fully accommodate them. This necessitates segmentation at the lower layer, introducing fields such as SO, which reduces transmission efficiency. For example, a 24-bit SO or L field is approximately 16MB in size. Assuming the lower layer schedules data every 1ms, transmitting 16MB of data within 1ms would require a data rate of 16GB / s, which is already very high and exceeds typical speeds. Therefore, a 24-bit data packet length may be the upper limit that the lower layer can handle. Thus, the lower layer's transmission settings can use 24 bits as the upper limit for data packets for configuration and indication.

[0091] Therefore, for high-level data packets, if there is data longer than 24 bits, approximately 16M bytes in size, such as AI models or perception data, the adaptation layer function is still required to perform segmentation and reassembly shaping processes.

[0092] That is, we can use the two methods shown in the first approach simultaneously, using the first header field size configuration to extend the lower layer packet size limit to 24 bits in length, and at the same time support the adaptation layer function of segmenting packets using the second header field size, and perform shaping processing such as segmentation and reassembly on packets that exceed the limit.

[0093] Furthermore, adaptive segmentation packet length determination rules can be introduced. When the system load is light and the transmission link is good, the allocated resources are sufficient, so the upper limit of the segmentation packet length can be increased, for example, by using 24 bits or 16 bits, so that very large data packets can be transmitted in one go, avoiding low-level segmentation and thus achieving higher transmission efficiency. When the system load is heavy or the transmission link is poor, the allocated resource size is smaller, that is, the size of the transmission block that can be transmitted at one time is smaller. In this case, the upper limit of the segmentation packet length can be reduced, for example, by using 16 bits or 8 bits, to further reduce the probability of low-level segmentation operations.

[0094] In the data transmission method provided in this application embodiment, the terminal uses a first method to send a first data packet to the network-side device. The first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending data packets in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information. In this solution, the terminal can transmit data packets in different ways. On the one hand, it can send data packets based on a larger header field size configured in the first header field size configuration information; on the other hand, it can segment data packets based on the maximum transmission size limited by the second header field size configuration information. This supports the transmission of large data packets in a more flexible and efficient manner, improving data transmission efficiency and service experience, thus ensuring system efficiency while enhancing data transmission effectiveness.

[0095] Optionally, in some embodiments of this application, when the first method includes a method of segmenting data packets based on the maximum transmission size limited by the second header field size configuration information, step 201 specifically includes steps 201a and 201b:

[0096] Step 201a: Based on the maximum transmission size limited by the second header field size configuration information, the terminal segments the first data packet at the first protocol layer to obtain at least two segmented data packets.

[0097] In some embodiments of this application, the first protocol layer described above is used to segment or reassemble data packets.

[0098] In some embodiments of this application, the first protocol layer is located between the functional layer of the service data and the PDCP layer; or, the first protocol layer is located within the functional layer of the service data; or, the first protocol layer is located within the PDCP layer.

[0099] In one example, the first protocol layer is located below the functional layer of business data and above the PDCP layer, performing shaping and restoration operations on the giant data packets between the two.

[0100] In another example, the first protocol layer is located within the functional layer of the business data. The new adaptation function is executed in the functional layer of the business data, and the data generation and shaping operations of the AI ​​or perception functional layer are implemented in the same layer.

[0101] In another example, the first protocol layer is located within an existing L2 sublayer, such as the PDCP layer. The new adaptation functions are executed at the PDCP layer. When the PDCP layer receives a large data packet from a higher layer, it first performs shape-shifting, followed by the traditional PDCP layer processing. The PDCP layer can even perform partial operations first, such as security encryption and / or integrity protection, before performing shape-shifting, and then continue with the remaining PDCP layer operations, such as adding serial numbers and headers, and routing. These are all feasible examples and do not limit other reasonable implementations.

[0102] In some embodiments of this application, the functional layer of the aforementioned business data is an AI functional layer, a perception functional layer, or a data collection functional layer.

[0103] For example, between two network nodes, such as a terminal and a network-side device, wired interface transmission uses traditional transport layer protocols such as GTP, UDP, SCTP, and / or IP. These protocols can already perform certain shaping operations, such as with an MTU of 9000 bytes. Therefore, in this case, if the Adaptation layer, i.e., the first protocol layer mentioned above, only has the function of data shaping, then this layer or this function can be omitted and configured to be disabled. If this layer or function has other functions besides data shaping, such as security operations, then the data shaping function can be disabled or omitted, and the other functions can be retained.

[0104] It should be noted that the functions of the first protocol layer can be configured and enabled only for the required data. For example, when a terminal simultaneously transmits traditional data and AI or sensing data, the network-side device can map the two to different bearers, such as Data Radio Bearer (DRB) 1 and DRB2, or DRB1 and CRB1. In this way, the new functions of the first protocol layer only need to be effective for DRB2 or Common Resource Block (CRB) 1, while DRB1, where traditional data resides, remains unaffected.

[0105] Step 201b: The terminal sends at least two segmented data packets to the network-side device.

[0106] In some embodiments of this application, the terminal sends at least two segmented data packets to the network-side device via a logical channel.

[0107] In this way, the terminal can segment excessively large data packets through the protocol layer with segmentation capabilities, allowing the data packets to be transmitted through L2.

[0108] Optionally, in some embodiments of this application, step 201 specifically includes steps 201c and 201d:

[0109] Step 201c: The terminal segments the first data packet based on the maximum segmentation limit to obtain at least two segmented data packets.

[0110] Step 201d: The terminal sends at least two segmented data packets to the network-side device.

[0111] In some embodiments of this application, the maximum segmentation limit is less than or equal to the maximum transmission size based on the second header field size configuration limit.

[0112] In some embodiments of this application, the above-mentioned maximum segmentation limit is a segmentation limit of static configuration or semi-static configuration; or, the maximum segmentation limit is a segmentation limit determined based on the current transmission status of the terminal.

[0113] For example, regarding the maximum segment size, static or semi-static segment size limits can be implemented. For instance, simply setting the maximum segment size to 9000 bytes is applicable to 5G NR air interface and wired path transmission. Alternatively, a semi-static maximum segment size limit, such as N bytes, can be configured or reconfigured by control signaling for use by the adaptation layer / function for shaping operations. Furthermore, a dynamic adaptive segment size adjustment method can also be adopted, such as dynamically performing adaptive segmentation based on the current link conditions and resource size to maximize transmission efficiency.

[0114] In this way, the terminal can adaptively segment massive data packets according to the maximum segmentation limit, allowing the segmented data packets to be transmitted via L2. Furthermore, by adaptively adjusting the maximum segmentation limit, data packets can be divided into as few segments as possible while maintaining transmission efficiency.

[0115] Optionally, in some embodiments of this application, the data transmission method provided in the embodiments of this application further includes step 301:

[0116] Step 301: The terminal adds the first information to the first data packet.

[0117] In some embodiments of this application, the first information includes at least one of the following:

[0118] The first identifier is used to indicate whether the first data packet is a complete data packet or a segmented data packet;

[0119] Segmentation information is used to indicate the order of segmented data packets;

[0120] The second identifier is used to indicate segmented data packets that belong to the same complete data packet.

[0121] For example, the first identifier is used to indicate whether the first data packet is a segmented data packet or a complete data packet.

[0122] For example, the first protocol layer can determine whether the first data packet is a complete data packet or a segmented data packet by distinguishing the first identifier.

[0123] For example, the first identifier mentioned above can be an explicit identifier, directly indicating whether the data packet is segmented or complete. The first identifier can also be an implicit identifier, that is, a data packet carrying segmentation information is a segmented data packet, and a data packet not carrying segmentation information is a complete data packet without segmentation.

[0124] For example, the above segmentation information includes at least one of the following: segmentation sequence number and tail segment identifier.

[0125] For example, the segment sequence number mentioned above is used to indicate the order of the various segments of the first data packet.

[0126] For example, the above-mentioned tail segment identifier is used to indicate the last segment data packet of the first data packet.

[0127] For example, the above segment sequence number is used to assemble the segments in order at the receiving end, and to detect the loss of segments, thereby avoiding reassembly errors.

[0128] For example, the above-mentioned tail segment identifier is used to mark the end of a data packet segment.

[0129] Generally, in simple transmission scenarios, such as when out-of-order delivery or packet loss is not considered, and assuming that each segmented data packet arrives at the receiving end in order, the tail segment identifier can be used independently. However, in general, transmission scenarios are more complex, and various special events such as reconfiguration and switching occur. Using both segment sequence numbers and tail segment identifiers together will better cope with out-of-order delivery and packet loss.

[0130] In one example, a second identifier can also be added to the original data packets that are segmented.

[0131] For example, the second identifier mentioned above can be a serial number.

[0132] For example, the sequence number can be used for accurate identification of large packets and large packet segments. For instance, the first segment of data with SN=1 cannot be assembled with the second segment of data with SN=2, as they belong to different original data packets.

[0133] Optionally, in some embodiments of this application, such as Figure 4 As shown, the data transmission method provided in this application embodiment further includes step 401 or step 402:

[0134] Step 401: The terminal receives the second data packet from the network-side device according to the first header field size configuration information.

[0135] In some embodiments of this application, the first header size configuration information is the extended header size sent by the network-side device.

[0136] In some embodiments of this application, the terminal receives a second data packet sent by the network-side device based on each protocol layer of the extended header field size.

[0137] It is understandable that the first and second data packets mentioned above can be complete data packets or segmented data packets.

[0138] Step 402: The terminal receives at least two third data packets from the network-side device through the second header field size configuration information, and combines the at least two third data packets to obtain a fourth data packet.

[0139] In some embodiments of this application, the above-mentioned at least two third data packets are data packets that input the same original data packet.

[0140] In some embodiments of this application, the above-mentioned at least two data packets may be consecutive data packets or non-consecutive data packets.

[0141] Optionally, in some embodiments of this application, step 402 specifically includes step 402a:

[0142] Step 402a: If at least two third data packets received by the terminal belong to the same data packet, the terminal reassembles at least two third data packets in ascending order according to the segment sequence number of each third data packet.

[0143] In some embodiments of this application, when a data packet is received at the receiving end, i.e., the terminal, it first determines whether it is an unsegmented complete data packet or a segmented data packet. If it is an unsegmented complete data packet, it proceeds directly to the next operation. If it is a segmented data packet, it is first reassembled.

[0144] In some embodiments of this application, if each of the above third data packets has a segment sequence number, the segment data packets are connected in ascending order of the sequence number until the end segment identifier is reached, at which point the data reassembly is considered complete.

[0145] Furthermore, in some embodiments of this application, in conjunction with step 402 above, the data transmission method provided by the embodiments of this application further includes step 403 or step 404:

[0146] Step 403: If the terminal does not receive the data packet corresponding to the missing segment sequence number within the first time period when the segment sequence numbers of at least two received third data packets are not consecutive, then the terminal will send at least two third data packets to the fourth protocol layer for processing.

[0147] In some embodiments of this application, the fourth protocol layer is a higher layer than the third protocol layer.

[0148] Step 404: If the terminal does not receive the data packet corresponding to the missing segment sequence number within the first time period when the segment sequence numbers of at least two received third data packets are not consecutive, then the terminal will discard at least two third data packets.

[0149] In some embodiments of this application, the first duration is user-defined or may be a default setting of the terminal.

[0150] For example, the first duration mentioned above can be the duration set by the timer.

[0151] For example, if the first and third segment data packets are received, but the second segment data packet is not received, a timer is started. If the second segment data packet is received before the timer expires, the timer is stopped, and the sorting and reassembly process continues. If the timer expires and the second segment data packet is still not received, it is considered that the data packet cannot be correctly reassembled, and other related segment data packets can be deleted by default.

[0152] Even if the first and third segmented data packets, or even subsequent segmented data packets, have already been received, a configuration method can be adopted. The configuration can be set to delete packets if reassembly fails, or to deliver out-of-order segmented data packets in ascending order as much as possible if reassembly fails. If the latter is configured, the first segmented data packet, the third segmented data packet, and other segmented data packets that belong to the same original data packet received later will be delivered to the higher layer for processing in ascending order of segmented data packet sequence number.

[0153] For example, if the first and third segment data packets are received, but the second segment data packet is not received, a timer is started. If the fifth segment data packet is received during the timer's operation, meaning the fourth segment data packet is also detected as lost, the timer can be restarted. This way, the new timer will apply to both the second and fourth segment data packets simultaneously. The timer will only stop if all the preceding data packets are received, or it will wait for the timer to expire. If any segment data packet fails to be delivered successfully, the default operation of deleting other segment data packets or the configured operation of successfully delivered segment data packets must be executed.

[0154] It should be noted that in some cases, the lower layer can be considered to provide in-order delivery. Once a data packet is lost, it cannot be recovered. Instead, other related segmented data packets should be deleted, or operations that can successfully deliver segmented data packets according to the configuration can be performed.

[0155] In one example, when a large packet has a serial number (SN), a simple reordering operation can be performed based on the SN. For instance, if the data packet corresponding to the next SN is received but the data packet corresponding to the previous SN has not yet been received, a timer can be started to wait for the previous data packet. If the timer expires and the previous data packet is still not received, the waiting is abandoned and the subsequent data packets are directly submitted to the higher layer in ascending order of SN.

[0156] In this way, the terminal can reassemble the segmented data packets according to the reassembly rules, so that the terminal can receive complete data packets and ensure the effectiveness of data transmission.

[0157] It should be noted that steps 401 to 404 above, and their subordinate methods, can be implemented in conjunction with step 201, or as a separate embodiment. The implementation process is the same, and can be referred to [reference needed]. Figure 4 This will not be elaborated upon here.

[0158] Optionally, in some embodiments of this application, before step 201 "the terminal sends a first data packet to the network-side device using a first method" described above, the data transmission method provided in this application embodiment further includes step A1:

[0159] Step A1: The terminal reports capability information to the network-side device.

[0160] In some embodiments of this application, the aforementioned capability information includes at least one of the following:

[0161] Supports the ability to transmit large data packets;

[0162] Supports extended header field sizes;

[0163] Supports pre-segmentation functionality;

[0164] Supported terminal version information.

[0165] First, due to the new SO and L field length values ​​introduced by the ultra-large data packet length, and the support for the adaptation layer, these are all new UE capabilities. That is, 5G UEs do not support them; only 6G UEs, or some 6G UEs, support them. Therefore, before configuration and use, it is necessary to report the relevant UE capabilities. This can be done by reporting simple, similar UE versions. For example, 5G UEs do not support any extended SO and L fields or new adaptation layer functions, while 6G UEs support extended SO and L fields and new adaptation layer functions. The relevant UE capabilities can be deduced from the UE version number or similar version number capability information. Alternatively, for 6G UEs, separate capability indicators can be set, such as indicators of whether extended SO and L fields are supported, and / or whether new adaptation layers are supported, to obtain the UE capabilities.

[0166] Secondly, after obtaining the UE's capabilities, the network side can configure extended SO and L domains and / or new adaptation layers for the supported UEs when needed. As described in Embodiments 1 and 2, ordinary service data and data supporting jumbo packets, such as new AI and perception data, can be distinguished as different bearers. The new configuration is only enabled for the bearer of the jumbo packets, without affecting traditional data transmission.

[0167] In particular, extending the SO and L domains, and / or adding a new adaptation layer, can all support reconfiguration, such as switching from off to on, or on to off, and even reconfiguring detailed parameters while on. The simplest way to perform reconfiguration is synchronous reconfiguration, where both the transmitting and receiving ends reset the L2's RLC and MAC, starting from the initial state, and then apply the new configuration.

[0168] In this way, network-side devices can determine the configuration information of the protocol layer header field size or the configuration information of the protocol layer with segmentation function based on the capability information sent by the terminal, so that the terminal or network-side devices can configure the protocol layer according to the configuration information.

[0169] In one possible embodiment, the terminal will also undergo a handover, performing configuration transfer and state transition between the source cell and the target cell, including at least one of the following related operations:

[0170] When the source cell requests a handover to the target cell, it can send the extended SO and L domains and / or the configuration of the first protocol layer, such as enabling / disabling, parameter configuration, etc., to the target cell so that the target cell can determine the new configuration for the UE.

[0171] The new configuration may include extended SO and L domains and / or the configuration of the first protocol layer in the target cell, such as enabling / disabling, parameter configuration, etc., which are sent to the UE by the source cell via a handover command and executed by the UE in the target cell.

[0172] When the source cell enables extended SO and L domains and / or first protocol layer configuration, regardless of whether the target cell enables the new configuration, since the RLC and MAC layers, including the first protocol layer, are basically reset, there is no data related to the new function that needs special handling during the handover process.

[0173] Figure 5 A flowchart illustrating another data transmission method provided in an embodiment of this application is shown, as follows: Figure 5 As shown, this data transmission method is applied to a network-side device, and the method may include the following step 501:

[0174] Step 501: The network-side device sends the first data packet to the terminal using the first method.

[0175] In some embodiments of this application, the first approach described above includes at least one of the following:

[0176] The method of sending configuration information based on the first header field size;

[0177] The method of sending data packets in segments based on the maximum transmission size limit imposed by the second header field size configuration information;

[0178] In some embodiments of this application, the head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0179] It is understood that the explanation of the first method above can refer to step 201 on the terminal side, and will not be repeated here.

[0180] Optionally, in some embodiments of this application, when the first method includes sending based on the first header domain size configuration information, the data transmission method provided in this application embodiment further includes step 601 before step 501.

[0181] Step 601: The network-side device sends the first header domain size configuration information to the terminal;

[0182] In some embodiments of this application, the above configuration information includes at least one of the following:

[0183] Instruction information, which indicates whether to use extended header field size;

[0184] The ordinal value of the header field size;

[0185] Head domain size.

[0186] In some embodiments of this application, in existing L2 packet assembly operations, network-side devices generally consider two main factors when designing the size of fields such as SO and L: first, the maximum size of data that the higher layers need to transmit; and second, the requirement that each layer's header must meet the requirement of integer byte arrangement for better processing and segmentation. Therefore, the maximum size of the SO and L fields is chosen to be 16 bits, which can support 9000 bytes (at least 10 bits) and is arranged with integer byte arrangement.

[0187] On the other hand, network-side devices, based on the current basic principles of header field design, require the entire header field to be arranged in whole bytes. Therefore, the SO and L field sizes can be extended to 24 bits or 36 bits, etc. When the maximum size of these header fields is extended, it also means that the dynamic range of the original higher-layer data packet size is larger. In this case, an optimization design is to introduce or extend the Field indicator field, such as a 2-bit Field indicator field, where 00 represents an 8-bit SO or L field length, 01 represents a 16-bit SO or L field length, 10 represents a 24-bit SO or L field length, 11 represents a 36-bit SO or L field length, and so on.

[0188]

[0189] Furthermore, since only some data requires support for giant data packets, such as AI or sensing data transmission, or AI or sensing data transmission that does not undergo TCP or IP transmission protocol shaping, the base station needs to perform certain identification for this data and map it to independent bearers, such as a separate DRB or a dedicated CRB, to distinguish it from traditional SRBs and user data DRBs. Traditional data can use traditional data packet formats, while new bearers, because they need to support giant data packets, need to support extended header structures and field lengths. The network side can provide different header field lengths for each bearer, or different types of bearers can correspond to different default header field lengths. For example, if DRB1 is traditional data, the SO / SOstart / SOend field length is 16 bits. If DRB2 or CRB1 carries AI models, the SO / SOstart / SOend field length can be configured to 24 bits or other larger values. Furthermore, it can support, for example, a 2-bit F field, where different values ​​of F indicate the length of the corresponding SO / SOstart / SOend field. This allows for variable-length SO / SOstart / SOend fields. When the data packet is small, a smaller SO / SOstart / SOend length is used to save overhead, while when the data packet is large, a larger SO / SOstart / SOend length is used to adapt to the transmission requirements of large data packets.

[0190] It should be noted that because the MAC layer corresponds to the entire transmission channel, data carried in different DRBs or CRBs is processed uniformly at the MAC layer and may be cascaded into the same MAC PDU for transmission. Therefore, the MAC layer header format, if configured with at least one special RB supporting jumbo packets, needs to support extended MAC subheadings and field lengths. For example, terminal 1, which only has traditional data DRB1 and DRB2, maintains the traditional configuration size for its MAC subheading and L field length. The L field can be selected from 8-bit and 16-bit lengths, and the F field is 1-bit long, with 0 and 1 values ​​in the F field explicitly corresponding to the two lengths of the L field. Another UE2, supporting both traditional data DRB1 and jumbo packet format CRB1 or DRB2, needs to support extended configuration sizes for its MAC subheading and L field length. The L field can be selected from 8-bit, 16-bit, 24-bit, and 36-bit lengths, and the F field is 2-bit long, with 00, 01, 10, and 11 values ​​in the F field explicitly corresponding to the four lengths of the L field.

[0191] In the data transmission method provided in this application embodiment, the network-side device uses a first method to send a first data packet to the terminal. The first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending data packets in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information. In this solution, the network-side device can use different methods to transmit data packets. On the one hand, it can send data packets based on a larger header field size configured in the first header field size configuration information; on the other hand, it can segment data packets based on a maximum transmission size limited by the second header field size configuration information. This allows for more flexible and efficient support for the transmission of large data packets, improving data transmission efficiency and service experience, and ensuring system efficiency while enhancing data transmission effectiveness.

[0192] Optionally, in some embodiments of this application, when the first method includes a method of segmenting data packets based on the maximum transmission size limited by the second header field size configuration information, step 501 specifically includes steps 501a and 501b:

[0193] Step 501a: The network-side device segments the first data packet at the first protocol layer based on the maximum transmission size limited by the second header field size configuration information, resulting in at least two segmented data packets.

[0194] Step 501b: The network-side device sends at least two segmented data packets to the terminal.

[0195] In some embodiments of this application, the first protocol layer described above is used to segment or reassemble data packets.

[0196] In some embodiments of this application, the first protocol layer is located between the functional layer of the service data and the PDCP layer; or, the first protocol layer is located within the functional layer of the service data; or, the first protocol layer is located within the PDCP layer.

[0197] In some embodiments of this application, the functional layer of the aforementioned business data is an AI functional layer, a perception functional layer, or a data collection functional layer.

[0198] Optionally, in some embodiments of this application, step 501 specifically includes steps 501c and 501d:

[0199] Step 501c: The network-side device segments the first data packet based on the maximum segmentation limit to obtain at least two segmented data packets.

[0200] Step 501d: The network-side device sends at least two segmented data packets to the terminal.

[0201] In some embodiments of this application, the above-mentioned maximum segmentation limit is the segmentation limit of static configuration or semi-static configuration.

[0202] In some embodiments of this application, the network-side device can configure or reconfigure the segment limit by controlling signaling.

[0203] In this way, network-side devices can adaptively segment giant data packets according to the maximum segmentation limit, so that the segmented data packets can be transmitted through L2.

[0204] Optionally, in some embodiments of this application, the data transmission method provided in the embodiments of this application further includes step 701:

[0205] Step 701: The network-side device adds first information to the first data packet.

[0206] In some embodiments of this application, the first information includes at least one of the following:

[0207] The first identifier is used to indicate whether the first data packet is a complete data packet or a segmented data packet;

[0208] Segmentation information is used to indicate the order of segmented data packets;

[0209] The second identifier is used to indicate segmented data packets that belong to the same complete data packet.

[0210] It should be noted that the description of the first information and the process of adding the first information to the first data packet can refer to the specific process of step 301 above, and will not be repeated in this application.

[0211] In one possible embodiment, the network-side device receives the second data packet from the terminal according to the first header field size configuration information, or the network-side device receives at least two third data packets from the terminal according to the second header field size configuration, and combines the at least two third data packets to obtain the fourth data packet. The specific process can be referred to the description process of step 401 or step 402 on the terminal side, which will not be repeated here.

[0212] It should be noted that the specific process by which the network-side device receives the second data packet from the terminal according to the first header field size configuration information, or by the network-side device receiving at least two third data packets from the terminal according to the second header field size configuration, and combining the at least two third data packets to obtain the fourth data packet, can be implemented in conjunction with step 501, or as a separate embodiment. The implementation process is the same, as follows: Figure 6 Steps 1 and 2 shown in the diagram will not be elaborated here.

[0213] Optionally, in some embodiments of this application, before step 501 "the network-side device sends a first data packet to the terminal using a first method", the data transmission method provided in the embodiments of this application further includes step B1:

[0214] Step B1: The network-side device receives capability information from the terminal.

[0215] In some embodiments of this application, the aforementioned capability information includes at least one of the following:

[0216] Supports the ability to transmit large data packets;

[0217] Supports extended header field sizes;

[0218] Supports pre-segmentation functionality;

[0219] Supported terminal version information.

[0220] In this way, network-side devices can determine the configuration information of the protocol layer header field size or the configuration information of the protocol layer with segmentation function based on the capability information sent by the terminal, so that the terminal or network-side devices can configure the protocol layer according to the configuration information.

[0221] This application provides a data transmission device. As an example, the data transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0222] The data transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0223] For details, see Figure 7 When the data transmission device is a terminal or a component in a terminal, the data transmission device 6000A includes: a transmission module 6001A.

[0224] The aforementioned sending module 6001A is used to send a first data packet to the network-side device using a first method;

[0225] The first method includes at least one of the following:

[0226] The method of sending configuration information based on the first header field size;

[0227] The method of sending data packets in segments based on the maximum transmission size limit imposed by the second header field size configuration information;

[0228] The head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0229] Optionally, in some embodiments of this application, combined with Figure 7 ,like Figure 8 As shown, the aforementioned device 6000A further includes: a receiving module 6002A; the aforementioned first method includes a method of sending based on the first header domain size configuration information;

[0230] The receiving module 6002A is further configured to receive first header field size configuration information from the network side device before the sending module 6001A sends the first data packet to the network side device in the first manner.

[0231] The first head domain size configuration information includes at least one of the following:

[0232] Indication information, used to indicate whether to use extended header field size;

[0233] The ordinal value of the header field size;

[0234] Head domain size.

[0235] Optionally, in some embodiments of this application, the first method described above includes a method of sending data packets in segments based on the maximum transmission size limited by the second header field size configuration information;

[0236] The aforementioned transmitting module 6001A is specifically used for:

[0237] Based on the maximum transmission size limited by the second header field size configuration information, the first data packet is segmented at the first protocol layer to obtain at least two segmented data packets. The first protocol layer is used to segment or reassemble data packets.

[0238] Send at least two segmented data packets to the network-side device.

[0239] Optionally, in some embodiments of this application, the first protocol layer is located between the functional layer of the service data and the Packet Data Convergence Protocol (PDCP) layer; or, the first protocol layer is located within the functional layer of the service data; or, the first protocol layer is located within the PDCP layer.

[0240] Optionally, in some embodiments of this application, the above-mentioned functional layer is an artificial intelligence (AI) functional layer, a perception functional layer, or a data collection functional layer.

[0241] Optionally, in some embodiments of this application, the above-mentioned sending module 6001A is specifically used for:

[0242] Based on the maximum segmentation limit, the first data packet is segmented to obtain at least two segmented data packets. The maximum segmentation limit is less than or equal to the maximum transmission size limited by the second header field size configuration information.

[0243] Send at least two segmented data packets to the network-side device.

[0244] Optionally, in some embodiments of this application, the above-mentioned maximum segmentation limit is a segmentation limit of static configuration or semi-static configuration; or, the maximum segmentation limit is a segmentation limit determined based on the current transmission status of the terminal.

[0245] Optionally, in some embodiments of this application, combined with Figure 7 ,like Figure 9 As shown, the aforementioned device 6000A further includes: a processing module 6003A: the processing module 6003A is used to add first information to the first data packet, the first information including at least one of the following:

[0246] The first identifier is used to indicate whether the first data packet is a complete data packet or a segmented data packet;

[0247] Segmentation information is used to indicate the order of segmented data packets;

[0248] The second identifier is used to indicate segmented data packets that belong to the same complete data packet.

[0249] Optionally, in some embodiments of this application, the segmentation information includes at least one of the following: segmentation sequence number and tail segment identifier; wherein, the segmentation sequence number is used to indicate the order of each segment data packet of the first data packet, and the tail segment identifier is used to indicate the last segment data packet of the first data packet.

[0250] Optionally, in some embodiments of this application, the receiving module 6002A is further configured to receive a second data packet from a network-side device according to the first header field size configuration information;

[0251] or,

[0252] The aforementioned receiving module 6002A is also used to receive at least two third data packets from the network-side device through the second header field size configuration information;

[0253] The aforementioned processing module 6003A is also used to combine at least two third data packets to obtain a fourth data packet.

[0254] Optionally, in some embodiments of this application, the above-mentioned processing module 6003A is specifically used for:

[0255] If at least two third data packets received by the receiving module 6002A belong to the same data packet, the at least two third data packets are sequentially connected and reassembled in ascending order according to the segment sequence number of each third data packet.

[0256] Optionally, in some embodiments of this application, the above-described processing module 6003A is further used for:

[0257] If the segment sequence numbers of at least two received third data packets are not consecutive, and if no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be sent to the fourth protocol layer for processing. The fourth protocol layer is a higher layer than the third protocol layer.

[0258] Alternatively, if the segment sequence numbers of at least two received third data packets are not consecutive, and no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be discarded.

[0259] Optionally, in some embodiments of this application, before the terminal sends the first data packet to the network-side device using the first method, the aforementioned sending module 6001A is further used to report capability information to the network-side device;

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

[0261] Supports the ability to transmit large data packets;

[0262] Supports extended header field sizes;

[0263] Supports pre-segmentation functionality;

[0264] Supported terminal version information.

[0265] For details, see Figure 10 When the data transmission device is a terminal or a component in a terminal, the data transmission device 6000B includes: a receiving module 6001B and a processing module 6002B.

[0266] The receiving module 6001B is used to receive a second data packet from the network-side device according to the first header field size configuration information.

[0267] or,

[0268] The aforementioned receiving module 6001B is used to receive at least two third data packets from the network-side device through the second header field size configuration information;

[0269] The aforementioned processing module 6002B is used to combine at least two third data packets to obtain a fourth data packet;

[0270] The head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0271] Optionally, in some embodiments of this application, the receiving module 6001B is further configured to receive the first header field size configuration information from the network side device before receiving the second data packet from the network side device according to the first header field size configuration information;

[0272] The first head domain size configuration information includes at least one of the following:

[0273] Indication information, used to indicate whether to use extended header field size;

[0274] The ordinal value of the header field size;

[0275] Head domain size.

[0276] Optionally, in some embodiments of this application, the above-mentioned processing module 6002B is specifically used for:

[0277] If at least two third data packets received by the receiving module 6001B belong to the same data packet, the at least two third data packets are sequentially connected and reassembled in ascending order according to the segment sequence number of each third data packet.

[0278] Optionally, in some embodiments of this application, the above-mentioned processing module 6002B is further used for:

[0279] If the segment sequence numbers of at least two received third data packets are not consecutive, and if no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be sent to the fourth protocol layer for processing. The fourth protocol layer is a higher layer than the third protocol layer.

[0280] Alternatively, if the segment sequence numbers of at least two received third data packets are not consecutive, and no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be discarded.

[0281] Optionally, in some embodiments of this application, combined with Figure 10 ,like Figure 11 As shown, the above-mentioned device 6000B further includes: a sending module 6003B; the sending module 6003B is used to report capability information to the network side device before the receiving module 6001B receives the second data packet from the network side device according to the first header field size configuration information, or before the receiving module 6001B receives at least two third data packets from the network side device through the second header field size configuration information and combines the at least two third data packets to obtain a fourth data packet;

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

[0283] Supports the ability to transmit large data packets;

[0284] Supports extended header field sizes;

[0285] Supports pre-segmentation functionality;

[0286] Supported terminal version information.

[0287] In the data transmission apparatus provided in this application embodiment, the data transmission apparatus employs a first method to send a first data packet to a network-side device. The first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending data packets in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information. In this solution, the data transmission apparatus can transmit data packets in different ways. On the one hand, it can send data packets based on a larger header field size configured in the first header field size configuration information; on the other hand, it can segment data packets based on a maximum transmission size limited by the second header field size configuration information. This provides a more flexible and efficient way to support the transmission of large data packets, improving data transmission efficiency and service experience, thus ensuring system efficiency while enhancing data transmission effectiveness.

[0288] See Figure 12 When the data transmission device is a network-side device or a component in a network-side device, the data transmission device 7000A includes: a transmission module 7001A;

[0289] The aforementioned sending module 7001A is used to send a first data packet to the terminal using a first method;

[0290] The first method includes at least one of the following:

[0291] The method of sending based on the first header field size configuration information;

[0292] The method of sending data packets in segments based on the maximum transmission size limit imposed by the second header field size configuration information;

[0293] The head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0294] Optionally, in some embodiments of this application, the first method described above includes a method of sending based on the first header field size configuration information;

[0295] The aforementioned sending module 7001A is further configured to send first header field size configuration information to the terminal before sending the first data packet to the terminal using the first method;

[0296] The first head domain size configuration information includes at least one of the following:

[0297] Indication information, used to indicate whether to use extended header field size;

[0298] The ordinal value of the header field size;

[0299] Head domain size.

[0300] Optionally, in some embodiments of this application, the first method described above includes a method of sending data packets in segments based on the maximum transmission size limited by the second header field size configuration information;

[0301] The aforementioned transmitting module 7001A is specifically used for:

[0302] Based on the maximum transmission size limited by the second header field size configuration information, the first data packet is segmented at the first protocol layer to obtain at least two segmented data packets. The first protocol layer is used to segment or reassemble data packets.

[0303] Send at least two segmented data packets to the terminal.

[0304] Optionally, in some embodiments of this application, the first protocol layer is located between the functional layer of the service data and the PDCP layer; or, the first protocol layer is located within the functional layer of the service data; or, the first protocol layer is located within the PDCP layer.

[0305] Optionally, in some embodiments of this application, the above-mentioned functional layer is an AI functional layer, a perception functional layer, or a data collection functional layer.

[0306] Optionally, in some embodiments of this application, the above-mentioned sending module 7001A is specifically used for:

[0307] Based on the maximum segmentation limit, the first data packet is segmented to obtain at least two segmented data packets. The maximum segmentation limit is less than or equal to the maximum transmission size limited by the second header field size configuration information.

[0308] Send at least two segmented data packets to the terminal.

[0309] Optionally, in some embodiments of this application, the above-mentioned maximum segmentation limit is a segmentation limit of static configuration or semi-static configuration; or, the maximum segmentation limit is a segmentation limit determined based on the current transmission status of the terminal.

[0310] Optionally, in some embodiments of this application, combined with Figure 12 ,likeFigure 13 As shown, the aforementioned device 7000A further includes: a processing module 7002A; the processing module 7002A is used to add first information to the first data packet, the first information including at least one of the following:

[0311] The first identifier is used to indicate whether the first data packet is a complete data packet or a segmented data packet;

[0312] Segmentation information is used to indicate the order of segmented data packets;

[0313] The second identifier is used to indicate segmented data packets that belong to the same complete data packet.

[0314] Optionally, in some embodiments of this application, the segmentation information includes at least one of the following: segmentation sequence number and tail segment identifier; wherein, the segmentation sequence number is used to indicate the order of each segment data packet of the first data packet, and the tail segment identifier is used to indicate the last segment data packet of the first data packet.

[0315] Optionally, in some embodiments of this application, combined with Figure 13 ,like Figure 14 As shown, the above-mentioned device 7000A further includes: a receiving module 7003A; the receiving module 7003A is used to receive a second data packet from the terminal according to the first header field size configuration information; or, the receiving module 7003A is used to receive at least two third data packets from the terminal through the second header field size configuration information; the processing module 7002A is further used to combine at least two third data packets to obtain a fourth data packet.

[0316] Optionally, in some embodiments of this application, the above-mentioned processing module 7002A is specifically used for:

[0317] If at least two third data packets received by the receiving module 7003A belong to the same data packet, the at least two third data packets are sequentially connected and reassembled in ascending order according to the segment sequence number of each third data packet.

[0318] Optionally, in some embodiments of this application, the above-mentioned processing module 7002A is further used for:

[0319] If the segment sequence numbers of at least two received third data packets are not consecutive, and if no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be sent to the fourth protocol layer for processing. The fourth protocol layer is a higher layer than the third protocol layer.

[0320] Alternatively, if the segment sequence numbers of at least two received third data packets are not consecutive, and no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be discarded.

[0321] Optionally, in some embodiments of this application, the receiving module 7003A is further configured to receive capability information from the terminal before the sending module 7001A sends the first data packet to the terminal in the first manner;

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

[0323] Supports the ability to transmit large data packets;

[0324] Supports extended header field sizes;

[0325] Supports pre-segmentation functionality;

[0326] Supported terminal version information.

[0327] See Figure 15 When the data transmission device is a network-side device or a component of a network-side device, the data transmission device 7000B includes: a receiving module 7001B and a processing module 7002B.

[0328] The receiving module 7001B is used to receive the second data packet from the terminal according to the first header field size configuration information.

[0329] or,

[0330] The aforementioned receiving module 7001B is used to receive at least two third data packets from the terminal through the second header field size configuration information;

[0331] The aforementioned processing module 7002B is used to combine at least two third data packets to obtain a fourth data packet;

[0332] The head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0333] Optionally, in some embodiments of this application, combined with Figure 15 ,like Figure 16 As shown, the above-mentioned device further includes: a sending module 7003B; the sending module 7003B is used to send the first header field size configuration information to the terminal before the receiving module 7001B receives the second data packet from the terminal according to the first header field size configuration information.

[0334] The first head domain size configuration information includes at least one of the following:

[0335] Indication information, used to indicate whether to use extended header field size;

[0336] The ordinal value of the header field size;

[0337] Head domain size.

[0338] Optionally, in some embodiments of this application, the above-mentioned processing module 7002B is specifically used for:

[0339] If at least two third data packets received by the receiving module 7001B belong to the same data packet, the at least two third data packets are sequentially connected and reassembled in ascending order according to the segment sequence number of each third data packet.

[0340] Optionally, in some embodiments of this application, the above-mentioned processing module 7002B is further used for:

[0341] If the segment sequence numbers of at least two received third data packets are not consecutive, and if no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be sent to the fourth protocol layer for processing. The fourth protocol layer is a higher layer than the third protocol layer.

[0342] Alternatively, if the segment sequence numbers of at least two received third data packets are not consecutive, and no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be discarded.

[0343] Optionally, in some embodiments of this application, the receiving module 7001B is further configured to receive capability information from the terminal before receiving the second data packet from the terminal according to the first header field size configuration information, or before receiving at least two third data packets from the terminal through the second header field size configuration information and combining the at least two third data packets to obtain the fourth data packet.

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

[0345] Supports the ability to transmit large data packets;

[0346] Supports extended header field sizes;

[0347] Supports pre-segmentation functionality;

[0348] Supported terminal version information.

[0349] In the data transmission apparatus provided in this application embodiment, the data transmission apparatus employs a first method to send a first data packet to a network-side device. The first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending data packets in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information. In this solution, the data transmission apparatus can transmit data packets in different ways. On the one hand, it can send data packets based on a larger header field size configured in the first header field size configuration information; on the other hand, it can segment data packets based on a maximum transmission size limited by the second header field size configuration information. This provides a more flexible and efficient way to support the transmission of large data packets, improving data transmission efficiency and service experience, thus ensuring system efficiency while enhancing data transmission effectiveness.

[0350] The data transmission device provided in this application embodiment can implement all the processes implemented in the data transmission method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0351] like Figure 17 As shown in the illustration, this application also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above-described data transmission method embodiment and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the various steps of the above-described data transmission method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0352] This application embodiment 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 programs or instructions to implement the steps in the data transmission method embodiment. This terminal embodiment corresponds to the above-described terminal-side method embodiment; all implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 7 The data transmission device shown. Specifically, Figure 18 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0353] The terminal 100 includes, but is not limited to, at least some of the following components: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0354] Those skilled in the art will understand that the terminal 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 18 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0355] It should be understood that, in this embodiment, the input unit 104 may include a graphics processor 1041 and a microphone 1042. The graphics processor 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0356] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 101 can transmit it to the processor 110 for processing; in addition, the radio frequency unit 101 can send uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0357] The memory 109 can be used to store software programs or instructions, as well as various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0358] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0359] The radio frequency unit 101 is used to send a first data packet to the network-side device using a first method;

[0360] The first method includes at least one of the following:

[0361] The method of sending configuration information based on the first header field size;

[0362] The method of sending data packets in segments based on the maximum transmission size limit imposed by the second header field size configuration information;

[0363] The head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0364] Optionally, in some embodiments of this application, the first method mentioned above includes a method of sending based on the first header domain size configuration information; the radio frequency unit 101 is further configured to receive the first header domain size configuration information from the network side device before the radio frequency unit 101 sends the first data packet to the network side device using the first method.

[0365] The first head domain size configuration information includes at least one of the following:

[0366] Indication information, used to indicate whether to use extended header field size;

[0367] The ordinal value of the header field size;

[0368] Head domain size.

[0369] Optionally, in some embodiments of this application, the first method described above includes a method of sending data packets in segments based on the maximum transmission size limited by the second header field size configuration information;

[0370] The aforementioned radio frequency unit 101 is specifically used for:

[0371] Based on the maximum transmission size limited by the second header field size configuration information, the first data packet is segmented at the first protocol layer to obtain at least two segmented data packets. The first protocol layer is used to segment or reassemble data packets.

[0372] Send at least two segmented data packets to the network-side device.

[0373] Optionally, in some embodiments of this application, the first protocol layer is located between the functional layer of the service data and the Packet Data Convergence Protocol (PDCP) layer; or, the first protocol layer is located within the functional layer of the service data; or, the first protocol layer is located within the PDCP layer.

[0374] Optionally, in some embodiments of this application, the above-mentioned functional layer is an artificial intelligence (AI) functional layer, a perception functional layer, or a data collection functional layer.

[0375] Optionally, in some embodiments of this application, the radio frequency unit 101 described above is specifically used for:

[0376] Based on the maximum segmentation limit, the first data packet is segmented to obtain at least two segmented data packets. The maximum segmentation limit is less than or equal to the maximum transmission size limited by the second header field size configuration information.

[0377] Send at least two segmented data packets to the network-side device.

[0378] Optionally, in some embodiments of this application, the above-mentioned maximum segmentation limit is a segmentation limit of static configuration or semi-static configuration; or, the maximum segmentation limit is a segmentation limit determined based on the current transmission status of the terminal.

[0379] Optionally, in some embodiments of this application, the processor 110 is configured to add first information to the first data packet, the first information including at least one of the following:

[0380] The first identifier is used to indicate whether the first data packet is a complete data packet or a segmented data packet;

[0381] Segmentation information is used to indicate the order of segmented data packets;

[0382] The second identifier is used to indicate segmented data packets that belong to the same complete data packet.

[0383] Optionally, in some embodiments of this application, the segmentation information includes at least one of the following: segmentation sequence number and tail segment identifier; wherein, the segmentation sequence number is used to indicate the order of each segment data packet of the first data packet, and the tail segment identifier is used to indicate the last segment data packet of the first data packet.

[0384] Optionally, in some embodiments of this application, the radio frequency unit 101 is further configured to receive a second data packet from a network-side device according to the first header size configuration information;

[0385] or,

[0386] The aforementioned radio frequency unit 101 is also used to receive at least two third data packets from the network-side device through the second header field size configuration information;

[0387] The processor 110 described above is also used to combine at least two third data packets to obtain a fourth data packet.

[0388] Optionally, in some embodiments of this application, the processor 110 is specifically used for:

[0389] If at least two third data packets received by the radio frequency unit 101 belong to the same data packet, the at least two third data packets are sequentially connected and reassembled in ascending order according to the segment sequence number of each third data packet.

[0390] Optionally, in some embodiments of this application, the processor 110 is further configured to:

[0391] If the segment sequence numbers of at least two received third data packets are not consecutive, and if no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be sent to the fourth protocol layer for processing. The fourth protocol layer is a higher layer than the third protocol layer.

[0392] Alternatively, if the segment sequence numbers of at least two received third data packets are not consecutive, and no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be discarded.

[0393] Optionally, in some embodiments of this application, before the terminal sends the first data packet to the network-side device using the first method, the radio frequency unit 101 is further used to report capability information to the network-side device;

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

[0395] Supports the ability to transmit large data packets;

[0396] Supports extended header field sizes;

[0397] Supports pre-segmentation functionality;

[0398] Supported terminal version information.

[0399] The radio frequency unit 101 is also used to receive a second data packet from the network-side device according to the first header size configuration information.

[0400] or,

[0401] The aforementioned radio frequency unit 101 is also used to receive at least two third data packets from the network-side device through the second header field size configuration information;

[0402] The processor 110 described above is also used to combine at least two third data packets to obtain a fourth data packet;

[0403] The head domain size configured in the first head domain size configuration information is larger than the head domain size configured in the second head domain size configuration information.

[0404] Optionally, in some embodiments of this application, the radio frequency unit 101 is further configured to receive the first header domain size configuration information from the network side device before receiving the second data packet from the network side device according to the first header domain size configuration information;

[0405] The first head domain size configuration information includes at least one of the following:

[0406] Indication information, used to indicate whether to use extended header field size;

[0407] The ordinal value of the header field size;

[0408] Head domain size.

[0409] Optionally, in some embodiments of this application, the processor 110 is specifically used for:

[0410] If at least two third data packets received by the radio frequency unit 101 belong to the same data packet, the at least two third data packets are sequentially connected and reassembled in ascending order according to the segment sequence number of each third data packet.

[0411] Optionally, in some embodiments of this application, the processor 110 is further configured to:

[0412] If the segment sequence numbers of at least two received third data packets are not consecutive, and if no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be sent to the fourth protocol layer for processing. The fourth protocol layer is a higher layer than the third protocol layer.

[0413] Alternatively, if the segment sequence numbers of at least two received third data packets are not consecutive, and no data packet corresponding to the missing segment sequence number is received within the first time period, then at least two third data packets will be discarded.

[0414] Optionally, in some embodiments of this application, the radio frequency unit 101 is further configured to report capability information to the network side device before receiving the second data packet from the network side device according to the first header field size configuration information, or before receiving at least two third data packets from the network side device through the second header field size configuration information and combining the at least two third data packets to obtain the fourth data packet.

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

[0416] Supports the ability to transmit large data packets;

[0417] Supports extended header field sizes;

[0418] Supports pre-segmentation functionality;

[0419] Supported terminal version information.

[0420] In the terminal provided in this application embodiment, the terminal uses a first method to send a first data packet to the network-side device. The first method includes at least one of the following: a method of sending based on first header field size configuration information; a method of sending data packets in segments based on a maximum transmission size limited by second header field size configuration information; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information. In this solution, the terminal can transmit data packets in different ways. On the one hand, it can send data packets based on a larger header field size configured in the first header field size configuration information; on the other hand, it can segment data packets based on the maximum transmission size limited by the second header field size configuration information. This supports the transmission of large data packets in a more flexible and efficient manner, improving data transmission efficiency and service experience, thus ensuring system efficiency while enhancing data transmission effectiveness.

[0421] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the data transmission method embodiment. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0422] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 12 The data transmission device shown. (For example...) Figure 19 As shown, the network-side device 900 includes: an antenna 91, a radio frequency (RF) device 92, a baseband device 93, a processor 94, and a memory 95. The antenna 91 is connected to the RF device 92. In the uplink direction, the RF device 92 receives information through the antenna 91 and transmits the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be transmitted and sends it to the RF device 92. The RF device 92 processes the received information and transmits it through the antenna 91.

[0423] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 93, which includes a baseband processor.

[0424] Baseband device 93 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 19 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 95 via a bus interface to call the program in the memory 95 and execute the network device operations shown in the above method embodiment.

[0425] The network-side device may also include a network interface 96, such as a Common Public Radio Interface (CPRI).

[0426] Specifically, the network-side device 900 in this application embodiment further includes: instructions or programs stored in memory 95 and executable on processor 94, wherein processor 94 calls the instructions or programs in memory 95 to execute. Figure 8 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0427] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data transmission method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0428] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0429] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0430] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0431] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described data transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0432] This application also provides a data transmission system, including a terminal and a network-side device. The terminal can be used to execute the steps of the data transmission method described above, and the network-side device can be used to execute the steps of the data transmission method described above.

[0433] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0434] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0435] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A data transmission method, characterized by, The method comprises: The terminal sends a first data packet to a network side device in a first mode; The first mode comprises at least one of the following: a mode based on first header field size configuration information; a mode of segmenting and sending a data packet based on a maximum transmission size limited by second header field size configuration information; The header field size configured in the first header field size configuration information is greater than the header field size configured in the second header field size configuration information.

2. The method of claim 1, wherein, The first mode comprises the mode based on the first header field size configuration information; Before the terminal sends the first data packet to the network side device in the first mode, the method further comprises: The terminal receives the first header field size configuration information from the network side device; The first header field size configuration information comprises at least one of the following: indication information for indicating whether to use an extended header field size; a serial number value of a header field size; a header field size.

3. The method according to claim 1 or 2, characterized in that, The first mode comprises the mode of segmenting and sending a data packet based on the maximum transmission size limited by the second header field size configuration information; The terminal sends the first data packet to the network side device in the first mode, comprising: The terminal segments the first data packet at a first protocol layer based on the maximum transmission size limited by the second header field size configuration information, to obtain at least two segmented data packets, the first protocol layer being used for segmenting or packetizing a data packet; The terminal sends the at least two segmented data packets to the network side device.

4. The method of claim 3, wherein, The first protocol layer is located between a functional layer of service data and a packet data convergence protocol (PDCP) layer; or The first protocol layer is located within the functional layer of service data; or The first protocol layer is located within the PDCP layer.

5. The method of claim 4, wherein, The functional layer is an artificial intelligence (AI) functional layer or a perception functional layer or a data collection functional layer.

6. The method according to claim 1 or 3, characterized in that, The terminal sends the first data packet to the network side device in the first mode, comprising: The terminal segments the first data packet based on a maximum segmentation upper limit to obtain at least two segmented data packets, the maximum segmentation upper limit being less than or equal to the maximum transmission size limited by the second header field size configuration information; The terminal sends the at least two segmented data packets to the network side device.

7. The method of claim 6, wherein, The maximum segmentation upper limit is a statically configured or semi-statically configured segmentation upper limit; or The maximum segmentation upper limit is a segmentation upper limit determined based on a current transmission condition of the terminal. The method further comprises:

8. The method according to claims 1 to 7, characterized in that, adding first information in the first data packet, the first information comprising at least one of the following: a first identifier for indicating whether the first data packet is a complete data packet or a segmented data packet; segmentation information for indicating an order of segmented data packets; a second identifier for indicating segmented data packets belonging to a same complete data packet.

9. The method of claim 8, wherein The segmentation information comprises at least one of the following: a segmentation serial number and a tail segment identifier. ​ The segment sequence number is used to indicate the order of the segment data packets of the first data packet, and the tail segment identifier is used to indicate the last segment data packet of the first data packet.

10. The method according to claims 1 to 9, characterized in that, The method further comprises: The terminal receives a second data packet from the network side device according to the first header field size configuration information; Or, The terminal receives at least two third data packets from the network side device through the second header field size configuration information, and combines the at least two third data packets to obtain a fourth data packet.

11. The method of claim 10, wherein, The combining of the at least two third data packets to obtain the fourth data packet comprises: In the case that the at least two third data packets received by the terminal belong to the same data packet, the terminal sequentially connects and reorganizes the at least two third data packets in ascending order according to the segment sequence number of each third data packet.

12. The method according to claim 9 or 11, characterized in that, The method further comprises: In the case that the segment sequence numbers of the at least two third data packets received are not continuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, the at least two third data packets are sent to a fourth protocol layer for processing, the fourth protocol layer being a higher layer of the third protocol layer; Or, in the case that the segment sequence numbers of the at least two third data packets received are not continuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, the at least two third data packets are discarded.

13. The method of claims 1-12, wherein, Before the terminal sends the first data packet to the network side device in the first mode, the method further comprises: The terminal reports capability information to the network side device; The capability information comprises at least one of the following: The capability of supporting large-size data packet transmission; The capability of supporting extended header field size; The capability of supporting pre-segmentation function; Terminal version information supported.

14. A data transmission method, characterized by, The method further comprises: The terminal receives a second data packet from the network side device according to the first header field size configuration information; Or, The terminal receives at least two third data packets from the network side device through the second header field size configuration information, and combines the at least two third data packets to obtain a fourth data packet; The header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

15. The method of claim 14, wherein, Before the terminal receives the second data packet from the network side device according to the first header field size configuration information, the method further comprises: The terminal receives the first header field size configuration information from the network side device; The first header field size configuration information comprises at least one of the following: Indication information, which is used to indicate whether to use an extended header field size; A sequence number value of a header field size; A header field size.

16. The method of claim 14, wherein, The combining of the at least two third data packets to obtain the fourth data packet comprises: In the case that the at least two third data packets received by the terminal belong to the same data packet, the terminal sequentially connects and reorganizes the at least two third data packets in ascending order according to the segment sequence number of each third data packet.

17. The method of claim 14 or 16, wherein, The method further comprises: In the case that the received segment sequence numbers of the at least two third data packets are discontinuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are sent to a fourth protocol layer for processing, the fourth protocol layer being a higher layer of the third protocol layer. Or, in the case that the received segment sequence numbers of the at least two third data packets are discontinuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are discarded.

18. The method according to claims 14 to 17, characterized in that, Before the terminal receives the second data packet from the network side device according to the first header field size configuration information, or before the terminal receives the at least two third data packets from the network side device according to the second header field size configuration information and combines the at least two third data packets to obtain the fourth data packet, the method further comprises: The terminal reports capability information to the network side device; The capability information comprises at least one of the following: The capability of supporting large-size data packet transmission; The capability of supporting extended header field size; The capability of supporting pre-segmentation function; Terminal version information supported.

19. A data transmission method, characterized by, Comprises: The network side device sends a first data packet to the terminal in a first manner; The first manner comprises at least one of the following: A sending manner based on first header field size configuration information; A manner of sending a data packet in segments based on a maximum transmission size limited by second header field size configuration information; The header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

20. The method of claim 19, wherein, The first manner comprises a sending manner based on first header field size configuration information; Before the network side device sends a first data packet to the terminal in a first manner, the method further comprises: The network side device sends the first header field size configuration information to the terminal; The first header field size configuration information comprises at least one of the following: Indication information for indicating whether to use an extended header field size; Sequence number value of the header field size; Header field size.

21. The method of claim 14 or 15, wherein, The first manner comprises a manner of sending a data packet in segments based on a maximum transmission size limited by second header field size configuration information; The network side device sends a first data packet to the terminal in a first manner, comprising: The network side device segments the first data packet at a first protocol layer based on a maximum transmission size limited by the second header field size configuration information, to obtain at least two segment data packets, the first protocol layer being used for segmenting or packetizing a data packet; The network side device sends the at least two segment data packets to the terminal.

22. The method of claim 21, wherein, The first protocol layer is located between a functional layer of service data and a PDCP layer; or The first protocol layer is located within the functional layer of service data; or The first protocol layer is located within the PDCP layer.

23. The method of claim 22, wherein, The functional layer is an AI functional layer, a perception functional layer, or a data collection functional layer.

24. The method of claim 19 or 21, wherein, The network side device sends a first data packet to the terminal in a first manner, comprising: The network-side device segments the first data packet based on a maximum segment upper limit to obtain at least two segment data packets, the maximum segment upper limit being less than or equal to a maximum transmission size limited based on the second header field size configuration information; The network-side device sends the at least two segment data packets to the terminal.

25. The method of claim 24, wherein, The maximum segment upper limit is a statically configured or semi-statically configured segment upper limit. Alternatively, The maximum segment upper limit is a segment upper limit determined based on a current transmission condition of the terminal.

26. The method of claims 19-25, wherein, The method further comprises: adding first information in the first data packet, the first information including at least one of the following: a first identifier, the first identifier being used to indicate that the first data packet is a complete data packet or a segment data packet; segment information, the segment information being used to indicate an order of segment data packets; a second identifier, the second identifier being used to indicate segment data packets belonging to a same complete data packet.

27. The method of claim 26, wherein The segment information includes at least one of the following: a segment sequence number, a last segment identifier; The segment sequence number is used to indicate an order of each segment data packet of the first data packet, and the last segment identifier is used to indicate a last segment data packet of the first data packet.

28. The method of claims 19-27, wherein, The method further comprises: The network-side device receives a second data packet from the terminal according to the first header field size configuration information; Alternatively, The network-side device receives at least two third data packets from the terminal through the second header field size configuration information, and combines the at least two third data packets to obtain a fourth data packet.

29. The method of claim 28, wherein, The combining of the at least two third data packets to obtain the fourth data packet includes: In a case where the at least two third data packets received by the network-side device belong to a same data packet, the network-side device sequentially connects and recombines the at least two third data packets in ascending order according to segment sequence numbers of each third data packet.

30. The method of claim 28 or 29, wherein, The method further comprises: In a case where segment sequence numbers of the at least two third data packets received are not continuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, the at least two third data packets are sent to a fourth protocol layer for processing, the fourth protocol layer being a higher layer of the third protocol layer; Alternatively, in a case where segment sequence numbers of the at least two third data packets received are not continuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, the at least two third data packets are discarded.

31. The method of claims 19-30, wherein, Before the network-side device sends the first data packet to the terminal in the first mode, the method further comprises: The network-side device receives capability information from the terminal; The capability information includes at least one of the following: a capability of supporting large-size data packet transmission; a capability of supporting an extended header field size; a capability of supporting a pre-segment function; terminal version information supported.

32. A method of data transmission, characterized by, The method further comprises: The network-side device receives a second data packet from the terminal according to the first header field size configuration information; Alternatively, The network side device receives at least two third data packets from the terminal through second header field size configuration information, and combines the at least two third data packets to obtain a fourth data packet; The header field size configured in the first header field size configuration information is greater than the header field size configured in the second header field size configuration information.

33. The method of claim 32, wherein, Before the network side device receives the second data packet from the terminal according to the first header field size configuration information, the method further comprises: The network side device sends the first header field size configuration information to the terminal; The first header field size configuration information comprises at least one of the following: indication information for indicating whether to use an extended header field size; a sequence number value of the header field size; a header field size.

34. The method of claim 32, wherein, The combining of the at least two third data packets to obtain a fourth data packet comprises: In the case that the at least two third data packets received by the network side device belong to the same data packet, the network side device sequentially connects and reorganizes the at least two third data packets in ascending order according to the segment sequence numbers of each third data packet.

35. The method of claim 32 or 34, wherein, The method further comprises: In the case that the segment sequence numbers of the received at least two third data packets are not continuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are sent to a fourth protocol layer processing, the fourth protocol layer being a higher layer of the third protocol layer; Or, in the case that the segment sequence numbers of the received at least two third data packets are not continuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are discarded.

36. The method of claims 32-35, wherein, Before the network side device receives the second data packet from the terminal according to the first header field size configuration information, or before the network side device receives at least two third data packets from the terminal through second header field size configuration information and combines the at least two third data packets to obtain a fourth data packet, the method further comprises: The network side device receives capability information from the terminal; The capability information comprises at least one of the following: capability of supporting large-size data packet transmission; support for extended header field size; support for pre-segmentation function; supported terminal version information.

37. A data transmission device, comprising: Comprise: a sending module; The sending module is configured to send a first data packet to a network side device in a first mode; The first mode comprises at least one of the following: a mode of sending based on first header field size configuration information; a mode of segmenting and sending a data packet based on a maximum transmission size limited by second header field size configuration information; The header field size configured in the first header field size configuration information is greater than the header field size configured in the second header field size configuration information.

38. The device of claim 37, wherein, The first mode comprises a mode of sending based on first header field size configuration information; the apparatus further comprises a receiving module; The receiving module is further configured to receive the first header field size configuration information from the network side device before the sending module sends a first data packet to a network side device in a first mode; The first header field size configuration information includes at least one of the following: indication information, the indication information being used to indicate whether to use an extended header field size; a sequence number value of the header field size; a header field size.

39. The device of claim 37 or 38, wherein, The first mode includes a mode of sending a data packet in segments based on a maximum transmission size limited by second header field size configuration information; The sending module is specifically configured to: segment the first data packet at a first protocol layer based on a maximum transmission size limited by the second header field size configuration information, to obtain at least two segmented data packets, the first protocol layer being used to segment or pack data packets; send the at least two segmented data packets to the network side device.

40. The device of claim 39, wherein, The first protocol layer is located between a functional layer of service data and a packet data convergence protocol (PDCP) layer; or The first protocol layer is located within the functional layer of service data; or The first protocol layer is located within the PDCP layer.

41. The device of claim 40, wherein, The functional layer is an artificial intelligence (AI) functional layer or a perception functional layer or a data collection functional layer.

42. The apparatus of claim 37 or 39, wherein, The sending module is specifically configured to: segment the first data packet based on a maximum segmentation upper limit to obtain at least two segmented data packets, the maximum segmentation upper limit being less than or equal to the maximum transmission size limited by the second header field size configuration information; send the at least two segmented data packets to the network side device.

43. The device of claim 42, wherein, The maximum segmentation upper limit is a statically configured or semi-statically configured segmentation upper limit; or The maximum segmentation upper limit is a segmentation upper limit determined based on a current transmission condition of the terminal. The apparatus further includes a processing module.

44. The apparatus of claims 37-43, wherein, The processing module is configured to add first information to the first data packet, the first information including at least one of the following: a first identifier, the first identifier being used to indicate that the first data packet is a complete data packet or a segmented data packet; segmentation information, the segmentation information being used to indicate an order of segmented data packets; a second identifier, the second identifier being used to indicate segmented data packets belonging to a same complete data packet.

45. The apparatus of claim 44, wherein the segmentation information includes at least one of the following: a segmentation sequence number and a last segment identifier; The segmentation sequence number is used to indicate an order of each segmented data packet of the first data packet, and the last segment identifier is used to indicate a last segmented data packet of the first data packet. The receiving module is further configured to receive, from the network side device, a second data packet according to the first header field size configuration information; 46. The apparatus of claims 37-45, wherein, or The receiving module is further configured to receive, from the network side device, at least two third data packets through the second header field size configuration information; The processing module is further configured to combine the at least two third data packets to obtain a fourth data packet. The processing module is specifically configured to:

47. The device of claim 46, wherein, in a case where the at least two third data packets received by the receiving module belong to a same data packet, sequentially and in ascending order connect and recombine the at least two third data packets according to a segmentation sequence number of each third data packet. The processing module is further configured to:

48. The device of claim 45 or 47, wherein, ​ In a case where the segment sequence numbers of the received at least two third data packets are discontinuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are sent to a fourth protocol layer for processing, the fourth protocol layer being a higher layer of the third protocol layer. Or, in a case where the segment sequence numbers of the received at least two third data packets are discontinuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are discarded.

49. The apparatus of claims 37-48, wherein, In a case where the terminal adopts the first mode, before the sending module sends the first data packet to the network side device, the sending module further reports capability information to the network side device. The capability information includes at least one of the following: a capability of supporting large-size data packet transmission; supporting an extended header field size; supporting a pre-segmentation function; supported terminal version information.

50. A data transmission device, comprising: The apparatus includes: a receiving module and a processing module; the receiving module is configured to receive a second data packet from the network side device according to first header field size configuration information; or, the receiving module is configured to receive at least two third data packets from the network side device through second header field size configuration information; the processing module is configured to combine the at least two third data packets to obtain a fourth data packet; wherein the header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

51. The device of claim 50, wherein, The receiving module is further configured to receive the first header field size configuration information from the network side device before receiving the second data packet from the network side device according to the first header field size configuration information. The first header field size configuration information includes at least one of the following: indication information, the indication information being used to indicate whether to use an extended header field size; a sequence number value of a header field size; a header field size.

52. The device of claim 50, wherein, The processing module is specifically configured to: in a case where the at least two third data packets received by the receiving module belong to the same data packet, sequentially connect and reorganize the at least two third data packets in ascending order according to the segment sequence numbers of each third data packet.

53. The device of claim 50 or 52, wherein, The processing module is further configured to: in a case where the segment sequence numbers of the received at least two third data packets are discontinuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are sent to a fourth protocol layer for processing, the fourth protocol layer being a higher layer of the third protocol layer; or, in a case where the segment sequence numbers of the received at least two third data packets are discontinuous, if the data packet corresponding to the missing segment sequence number is not received within a first time length, the at least two third data packets are discarded.

54. The apparatus of claims 50-53, wherein, The apparatus further includes a sending module; The sending module is configured to report capability information to the network side device before the receiving module receives the second data packet from the network side device according to the first header field size configuration information, or before the receiving module receives at least two third data packets from the network side device according to the second header field size configuration information, combines the at least two third data packets, and obtains a fourth data packet. The capability information includes at least one of the following: a capability of supporting large-size data packet transmission; supporting an extended header field size; supporting a pre-segmentation function; terminal version information supported by the terminal.

55. A data transmission device, comprising: The apparatus includes: a sending module; The sending module is configured to send a first data packet to a terminal in a first mode. The first mode includes at least one of the following: a sending mode based on first header field size configuration information; a mode of sending a data packet in segments based on a maximum transmission size limited by second header field size configuration information. The first header field size configuration information configures a header field size that is larger than a header field size configured by the second header field size configuration information.

56. The method of claim 55, wherein, The first mode includes a sending mode based on first header field size configuration information. The sending module is further configured to send the first header field size configuration information to the terminal before sending the first data packet to the terminal in the first mode. The first header field size configuration information includes at least one of the following: indication information for indicating whether to use an extended header field size; a sequence number value of a header field size; and a header field size.

57. The device of claim 55 or 56, wherein, The first mode includes a mode of sending a data packet in segments based on a maximum transmission size limited by second header field size configuration information. The sending module is specifically configured to: segment the first data packet at a first protocol layer based on the maximum transmission size limited by the second header field size configuration information, to obtain at least two segmented data packets, the first protocol layer being configured to segment or pack data packets; send the at least two segmented data packets to the terminal.

58. The device of claim 57, wherein, The first protocol layer is located between a functional layer of service data and a PDCP layer; or The first protocol layer is located within the functional layer of service data; or The first protocol layer is located within the PDCP layer.

59. The device of claim 58, wherein, The functional layer is an AI functional layer, a perception functional layer, or a data collection functional layer.

60. The device of claim 55 or 57, wherein, The sending module is specifically configured to: segment the first data packet based on a maximum segmentation upper limit to obtain at least two segmented data packets, the maximum segmentation upper limit being less than or equal to the maximum transmission size limited by the second header field size configuration information; send the at least two segmented data packets to the terminal.

61. The device of claim 60, wherein, The maximum segmentation upper limit is a statically configured or semi-statically configured segmentation upper limit; or The maximum segmentation upper limit is a segmentation upper limit determined based on a current transmission condition of the terminal. The apparatus further includes a processing module.

62. The apparatus of claims 55-61, wherein, The processing module is configured to add first information to the first data packet, the first information including at least one of the following: a first identifier for indicating whether the first data packet is a complete data packet or a segmented data packet; ​ Segment information, the segment information being used for indicating the order of the segment data packets; Second identification, the second identification being used for indicating the segment data packets belonging to the same complete data packet.

63. The apparatus of claim 62, wherein, The segment information comprises at least one of the following: segment sequence number, tail segment identification; The segment sequence number is used for indicating the order of the segment data packets of the first data packet, and the tail segment identification is used for indicating the last segment data packet of the first data packet.

64. The device of claims 55-63, wherein, The apparatus further comprises an accepting module; The receiving module is configured to receive a second data packet from the terminal according to the first header field size configuration information; Or, The receiving module is configured to receive at least two third data packets from the terminal according to the second header field size configuration information; The processing module is further configured to combine the at least two third data packets to obtain a fourth data packet.

65. The method of claim 64, wherein, The processing module is specifically configured to: In a case where the at least two third data packets received by the receiving module belong to the same data packet, sequentially connect and recombine the at least two third data packets in ascending order according to the segment sequence numbers of the third data packets.

66. The method of claim 64 or 65, wherein, The processing module is further configured to: In a case where the segment sequence numbers of the at least two third data packets received are not continuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, send the at least two third data packets to a fourth protocol layer processing, the fourth protocol layer being a higher layer of the third protocol layer; Or, in a case where the segment sequence numbers of the at least two third data packets received are not continuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, discard the at least two third data packets.

67. The method of claims 55-66, wherein, The receiving module is further configured to receive capability information from the terminal before the sending module sends the first data packet to the terminal in the first mode; The capability information comprises at least one of the following: Capability of supporting large-size data packet transmission; Capability of supporting extended header field size; Capability of supporting pre-segmentation function; Terminal version information supported.

68. A data transmission device, comprising: Comprise: A receiving module and a processing module; The receiving module is configured to receive a second data packet from the terminal according to first header field size configuration information; Or, The receiving module is configured to receive at least two third data packets from the terminal according to second header field size configuration information; The processing module is configured to combine the at least two third data packets to obtain a fourth data packet; The header field size configured in the first header field size configuration information is larger than the header field size configured in the second header field size configuration information.

69. The device of claim 68, wherein, The apparatus further comprises a sending module; The sending module is configured to send the first header field size configuration information to the terminal before the receiving module receives a second data packet from the terminal according to the first header field size configuration information; The first header field size configuration information comprises at least one of the following: Indication information, the indication information being used for indicating whether to use an extended header field size; Sequence number value of the header field size; Header field size.

70. The device of claim 68, wherein, The processing module is specifically configured to: In a case where the at least two third data packets received by the receiving module belong to the same data packet, sequentially connecting and recombining the at least two third data packets in ascending order according to the segment sequence numbers of each third data packet.

71. The device of claim 68 or 70, wherein, The processing module is further configured to: In a case where the segment sequence numbers of the at least two received third data packets are discontinuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, sending the at least two third data packets to a fourth protocol layer processing, the fourth protocol layer being a higher layer of the third protocol layer. Or, in a case where the segment sequence numbers of the at least two received third data packets are discontinuous, if a data packet corresponding to a missing segment sequence number is not received within a first time length, discarding the at least two third data packets.

72. The device of claims 68-71, wherein, The receiving module is further configured to receive capability information from the terminal before receiving a second data packet from the terminal according to first header field size configuration information, or before receiving at least two third data packets from the terminal through second header field size configuration information, combining the at least two third data packets to obtain a fourth data packet. The capability information includes at least one of the following: A capability of supporting large-size data packet transmission; Supporting an extended header field size; Supporting a pre-segmentation function; Terminal version information supported.

73. A terminal, characterized by A processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the data transmission method of any one of claims 1 to 13, or to implement the steps of the data transmission method of any one of claims 14 to 18.

74. A network-side device, comprising: A processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the data transmission method of any one of claims 19 to 31, or to implement the steps of the data transmission method of any one of claims 32 to 36.

75. A readable storage medium characterized by, The readable storage medium stores programs or instructions, the programs or instructions being executed by the processor to implement the data transmission method of any one of claims 1 to 13, or to implement the data transmission method of any one of claims 14 to 18, or to implement the data transmission method of any one of claims 19 to 31, or to implement the steps of the data transmission method of any one of claims 32 to 36.

Images