Data transmission method, terminal and network side device

Abstract

The present application pertains to the technical field of communications, and discloses a data transmission method, a terminal, and a network side device. The data transmission method of an embodiment of the present application comprises: a terminal executing at least one of a first operation and a second operation. The first operation comprises at least one of: receiving a first data packet of a first bearer or data stream, and generating a second data packet, the second data packet comprising the first data packet and any one of an IP header, an IP and UDP header, and an IP, UDP and RTP header; and sending a third data packet of the first bearer or data stream, the third data packet not having any one of an IP header, an IP and UDP header, and an IP, UDP and RTP header. The second operation comprises: the terminal sending first capability information to a network side node, the first capability information being used for indicating that the terminal is capable of executing the first operation, and the first bearer or data stream being used for transmitting an IP protocol data packet.

Description

Data transmission methods, terminals and network-side equipment

[0001] Cross-reference to related applications

[0002] This application is based on Chinese Patent Application No. 202411593977.9, filed on November 8, 2024, and the priority of that Chinese Patent Application is incorporated herein by reference in its entirety. Technical Field

[0003] This application relates to the field of communication technology, and more specifically, to a data transmission method, a terminal, and a network-side device. Background Technology

[0004] In related technologies, the transmission of Internet Protocol (IP) data packets sometimes results in the air interface delivery time being longer than the packet interval time. This can affect the quality of audio playback, causing stuttering. The greater the difference between the air interface delivery time and the packet interval time, the more severe the stuttering. It can also lead to packet backlog, cache occupation, and negatively impact the user experience. Summary of the Invention

[0005] This application provides a data transmission method, terminal, and network-side device that can solve the problems of poor communication quality and message backlog caused by the air interface delivery time being longer than the message interval in related technologies.

[0006] Firstly, a data transmission method is provided, executed by a terminal, the method comprising:

[0007] The terminal performs at least one of the first operation and the second operation;

[0008] The first operation includes at least one of the following:

[0009] Receive a first data packet from a first bearer or data stream, and generate a second data packet, wherein the second data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0010] Send a third data packet of the first bearer or data stream, wherein the third data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0011] The second operation includes: the terminal sending first capability information to a network-side node, wherein the first capability information is used to indicate that the terminal has the capability to perform the first operation;

[0012] The first bearer or data stream is used to transmit IP protocol data packets.

[0013] Secondly, a data transmission method is provided, executed by a first network node, the method comprising:

[0014] The first network node performs at least one of the third and fourth operations;

[0015] The third operation includes at least one of the following:

[0016] Receive the third data packet from the first bearer or data stream, and forward the fifth data packet;

[0017] Receive the sixth data packet and forward the first data packet through the first bearer or data stream;

[0018] The fourth operation includes at least one of the following:

[0019] Receive second instruction information from the second network node, and perform the third operation based on the second instruction information;

[0020] Receive first capability information from the terminal, and perform the third operation based on the first capability information;

[0021] The first bearer or data stream is used to transmit IP protocol data packets;

[0022] The third data packet does not include any of the following: IP header; IP and UDP header; IP, UDP and RTP header;

[0023] The fifth data packet includes the third data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

[0024] The first data packet does not include any of the following: IP header; IP and UDP header; IP, UDP, and RTP header;

[0025] The sixth data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

[0026] Thirdly, a data transmission method is provided, executed by a second network node, the method comprising:

[0027] The second network node performs the fifth and sixth operations;

[0028] The fifth operation includes at least one of the following:

[0029] Send a first indication message to the terminal, the first indication message being used to indicate at least one of the following: not to transmit the IP header; not to transmit the UDP header; not to transmit the RTP header;

[0030] Send a second indication message to the first network node, the second indication message being used to indicate at least one of the following: not to transmit IP headers; request not to transmit IP headers; not to transmit UDP headers; request not to transmit UDP headers; not to transmit RTP headers; request not to transmit RTP headers.

[0031] Send a third indication message to the access network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0032] Send an interval duration to the access network node, the interval duration being used to indicate the interval between transmitted data packets;

[0033] The sixth operation includes: receiving first capability information from the terminal and performing the fifth operation based on the first capability information.

[0034] Fourthly, a data transmission method is provided, executed by a third network node, the method comprising:

[0035] The third network node selects the first network node of the service terminal as the media gateway in the IMS system.

[0036] Fifthly, a data transmission method is provided, executed by an access network node, the method comprising:

[0037] The access network node performs a seventh operation, which includes at least one of the following:

[0038] The interval time at which the access network node receives the data sent by the first network node;

[0039] The interval duration at which the access network node receives data sent by the second network node;

[0040] The access network node receives a third indication message sent by the first network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0041] The access network node receives a third indication message sent by the second network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0042] The access network node does not enable IP layer protocol-related functions based on at least one of the following: terminal access status, information related to the first bearer or data stream, and session information related to the first bearer or data stream;

[0043] The access network node receives a third data packet from the first bearer or data stream of the terminal, and transmits the third data packet to the first network node via the GTP-U protocol. The third data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0044] Receive a first data packet from a first network node, and transmit the first data packet to the terminal via the PDCP protocol. The first data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0045] In a sixth aspect, a data transmission apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect, or to implement the steps of the method described in the fourth aspect, or to implement the steps of the method described in the fifth aspect.

[0046] In a seventh aspect, a terminal is provided, the 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 aspect.

[0047] Eighthly, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to perform at least one of a first operation and a second operation;

[0048] The first operation includes at least one of the following:

[0049] Receive a first data packet from a first bearer or data stream, and generate a second data packet, wherein the second data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0050] Send a third data packet of the first bearer or data stream, wherein the third data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0051] The second operation includes: the terminal sending first capability information to a network-side node, wherein the first capability information is used to indicate that the terminal has the capability to perform the first operation;

[0052] The first bearer or data stream is used to transmit IP protocol data packets.

[0053] A ninth aspect provides a 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 second aspect, or implementing the steps of the method as described in the third aspect, or implementing the steps of the method as described in the fourth aspect, or implementing the steps of the method as described in the fifth aspect.

[0054] A tenth aspect provides a network-side device, including a processor and a communication interface, wherein the processor is configured to perform at least one of a third operation and a fourth operation; wherein the third operation includes at least one of: receiving a third data packet from a first bearer or data stream, and forwarding a fifth data packet; receiving a sixth data packet, and forwarding a first data packet through a first bearer or data stream; wherein the fourth operation includes at least one of: receiving second indication information from a second network node, and performing the third operation based on the second indication information; receiving first capability information from a terminal, and performing the third operation based on the first capability information; wherein the first bearer... The data stream is used to transmit IP protocol data packets; wherein, the third data packet does not include any of the following: IP header; IP and UDP header; IP, UDP and RTP header; the fifth data packet includes the third data packet and any of the following: IP header; IP and UDP header; IP, UDP and RTP header; wherein, the first data packet does not include any of the following: IP header; IP and UDP header; IP, UDP and RTP header; the sixth data packet includes the first data packet and any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0055] Alternatively, the processor is configured to perform a fifth operation and a sixth operation; wherein the fifth operation includes at least one of the following: sending a first indication message to the terminal, the first indication message indicating at least one of the following: not transmitting an IP header; not transmitting a UDP header; not transmitting an RTP header; sending a second indication message to a first network node, the second indication message indicating at least one of the following: not transmitting an IP header; requesting not to transmit an IP header; not transmitting a UDP header; requesting not to transmit a UDP header; not transmitting an RTP header; requesting not to transmit an RTP header; sending a third indication message to an access network node, the third indication message indicating that IP layer protocol-related functions are not enabled; sending an interval duration to the access network node, the interval duration indicating the interval between transmitted data packets; wherein the sixth operation includes: receiving first capability information from the terminal, and performing the fifth operation based on the first capability information.

[0056] Alternatively, the processor may be used to select the first network node of the serving terminal as the media gateway in the IMS system.

[0057] Alternatively, the processor is configured to perform a seventh operation, the seventh operation including at least one of the following: the access network node receiving an interval duration sent by a first network node; the access network node receiving an interval duration sent by a second network node; the access network node receiving third indication information sent by the first network node, the third indication information indicating that IP layer protocol-related functions are not enabled; the access network node receiving third indication information sent by the second network node, the third indication information indicating that IP layer protocol-related functions are not enabled; the access network node disabling IP layer protocol-related functions based on at least one of the following: terminal access status, the seventh operation ... The access network node receives a third data packet from the terminal's first bearer or data stream, and transmits the third data packet to the first network node via the GTP-U protocol. The third data packet does not contain any of the following: IP header; IP and UDP headers; IP, UDP, and RTP headers. The access network node also receives a first data packet from the first network node and transmits the first data packet to the terminal via the PDCP protocol. The first data packet does not contain any of the following: IP header; IP and UDP headers; IP, UDP, and RTP headers.

[0058] Eleventhly, 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, or the steps of the method described in the fifth aspect.

[0059] In a twelfth aspect, a wireless communication system is provided, comprising: a terminal, a first network node, a second network node, a third network node, and an access network node, wherein the terminal is configured to perform the steps of the method described in the first aspect, the first network node is configured to perform the steps of the method described in the second aspect, the second network node is configured to perform the steps of the method described in the third aspect, the third network node is configured to perform the steps of the method described in the fourth aspect, and the access network node is configured to perform the steps of the method described in the fifth aspect.

[0060] In a thirteenth 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 the method as described in the second aspect, or the method as described in the third aspect, or the method as described in the fourth aspect, or the method as described in the fifth aspect.

[0061] In a fourteenth 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 perform the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect, or to implement the steps of the method as described in the third aspect, or to implement the steps of the method as described in the fourth aspect, or to implement the steps of the method as described in the fifth aspect.

[0062] In this embodiment, when the terminal receives a data packet of the first bearer or data stream, the data packet may lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers. The terminal restores the IP header of the data packet, or restores both IP and UDP headers, or restores both IP, UDP, and RTP headers. Alternatively, when the terminal sends a data packet of the first bearer or data stream, the data packet may lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers. This achieves that during the transmission of IP protocol data packets between the terminal and the network-side node, the IP protocol data packets sent by the sender lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers, reducing the size of the IP protocol data packets, shortening data transmission time, improving communication quality, and thus enhancing user experience. Attached Figure Description

[0063] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0064] Figure 2 is a flowchart illustrating one of the data transmission methods provided in this application embodiment;

[0065] Figure 3 is a schematic diagram of the data transmission method in the protocol stack according to an embodiment of this application;

[0066] Figure 4 is a second schematic flowchart of the data transmission method provided in the embodiments of this application;

[0067] Figure 5 is a schematic diagram of the interaction between the first network node, the terminal, and other network nodes provided in an embodiment of this application.

[0068] Figure 6 is a third flowchart illustrating the data transmission method provided in this application embodiment;

[0069] Figure 7 is a fourth flowchart illustrating the data transmission method provided in an embodiment of this application;

[0070] Figure 8 is a fifth flowchart illustrating the data transmission method provided in an embodiment of this application;

[0071] Figure 9 is one of the interactive flow diagrams of the data transmission method provided in the embodiments of this application;

[0072] Figure 10 is a second schematic diagram of the interaction flow of the data transmission method provided in the embodiments of this application;

[0073] Figure 11 is a schematic diagram of one of the data transmission devices provided in the embodiments of this application;

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

[0075] Figure 13 is a third schematic diagram of the data transmission device provided in the embodiment of this application;

[0076] Figure 14 is a fourth structural schematic diagram of the data transmission device provided in the embodiments of this application;

[0077] Figure 15 is a fifth schematic diagram of the data transmission device provided in the embodiments of this application;

[0078] Figure 16 is a schematic diagram of the structure of the communication device provided in an embodiment of this application;

[0079] Figure 17 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application;

[0080] Figure 18 is a schematic diagram of the structure of a network-side device that implements an embodiment of this application;

[0081] Figure 19 is a second schematic diagram of the structure of a network-side device implementing an embodiment of this application. Detailed Implementation

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

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

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

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

[0086] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment 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 (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, 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 the embodiments of this application. Network-side device 12 may include access network nodes or core network functions, wherein access network nodes may also be referred to as Radio Access Network (RAN) devices, radio access network functions, or radio access network units. Access network nodes 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.

[0087] Core network functions, also known as core network nodes, core network units, or core network equipment, include, but are not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Body Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses the core network functions of the NR system as an example and does not limit the specific types of core network functions. If the names of the core network functions mentioned in this application embodiment change in subsequent protocol versions (e.g., 6G), they will also be within the scope of protection of this application.

[0088] Optionally, core network functions can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0089] In related technologies, IP multimedia data transmission sometimes experiences situations where the air interface delivery time exceeds the message interval, affecting voice playback quality and causing stuttering. The larger the difference between the air interface delivery time and the message interval, the more severe the stuttering. This also leads to message backlog, buffer congestion, and negatively impacts user experience. While robust header compression (ROHC) is used to reduce header size, ROHC suffers from message size rollback due to state changes, resulting in intermittent and severe stuttering and failing to effectively solve the problems associated with IP multimedia data transmission.

[0090] The data transmission method, 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.

[0091] Figure 2 is a flowchart illustrating one of the data transmission methods provided in this application. As shown in Figure 2, the data transmission method is applied to a terminal and includes:

[0092] Step 100: The terminal performs at least one of the first operation and the second operation.

[0093] The first operation includes at least one of the following:

[0094] 1) Receive a first data packet from a first bearer or data stream and generate a second data packet, wherein the second data packet includes the first data packet and any one of the following: an IP header; an IP and User Datagram Protocol (UDP) header; or an IP, UDP and Real-time Transport Protocol (RTP) header.

[0095] Understandably, the first datagram of the first bearer or data stream does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

[0096] The terminal receives the first data packet of the first bearer or data stream and restores any one of the following from the first data packet: IP header; IP and UDP header; IP, UDP and RTP header, thereby generating the second data packet.

[0097] For example, if the first data packet does not have IP and UDP headers, the terminal restores the IP and UDP headers of the first data packet, that is, restores the information of each field in the IP header and UDP header, thereby generating the second data packet.

[0098] In the embodiments of this application, "restore" can also be replaced by "reconstruction", "generation", "regeneration", etc.

[0099] The first bearer or data stream is used to transmit IP protocol data packets, and the first data packet and the second data packet can be understood as IP protocol data packets.

[0100] Optionally, IP protocol datagrams can transmit IP multimedia data, RTP-based media data, IP Multimedia Subsystem (IMS) multimedia data, or other types of data. IP multimedia data refers to multimedia data transmitted using the IP protocol, such as video streams and audio streams, which can be encapsulated in IP datagrams for transmission. RTP-based media data refers to multimedia data transmitted using RTP.

[0101] 2) Send a third data packet of the first bearer or data stream, wherein the third data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

[0102] It is understandable that the terminal sends a third data packet to the network side. The third data packet does not contain an IP header, or it does not contain IP and UDP headers, or it does not contain IP, UDP and RTP headers. The payload is transmitted on top of the air interface data transmission protocol (i.e., the packet data convergence protocol (PDCP)).

[0103] Optionally, the terminal performs a second operation, which includes: the terminal sending first capability information to a network-side node, the first capability information indicating that the terminal has the capability to perform the first operation.

[0104] It is understandable that the terminal sends the first capability information to the network-side node, thereby instructing the network-side node that the terminal has the capability to perform the first operation.

[0105] Optionally, during the process of accessing the mobile network, the terminal sends first capability information to the network-side node via a Non-Access Stratum (NAS) message. Optionally, the network-side node here is an AMF, SMF, or MME, etc.

[0106] In this embodiment, when the terminal receives a data packet of the first bearer or data stream, the data packet may lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers. The terminal restores the IP header of the data packet, or restores both IP and UDP headers, or restores both IP, UDP, and RTP headers. Alternatively, when the terminal sends a data packet of the first bearer or data stream, the data packet may lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers. This achieves that during the transmission of IP protocol data packets between the terminal and the network-side node, the IP protocol data packets sent by the sender lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers, reducing the size of the IP protocol data packets, shortening data transmission time, improving communication quality, and thus enhancing user experience.

[0107] In some embodiments, generating the second data packet includes any one of the following: generating the IP header of the second data packet, i.e., restoring the IP header of the first data packet; generating the IP and UDP headers of the second data packet, i.e., restoring the IP and UDP headers of the first data packet; generating the IP, UDP, and RTP headers of the second data packet, i.e., restoring the IP, UDP, and RTP headers of the first data packet.

[0108] Optionally, the IP header of the second data packet is generated, including at least one of the following:

[0109] a) Based on the IP address information in the configuration information related to the first bearer or data stream, generate at least one of the source IP address and the destination IP address in the IP header;

[0110] b) Generate the SN in the IP header based on the sequence number SN in the PDCP header carrying the first data packet;

[0111] It should be noted that the first data packet here can be the current first data packet, the first data packet preceding the current first data packet, or a combination of both. That is, the SN in the IP header is generated based on the SN of the current first data packet and / or the first data packet preceding the current first data packet.

[0112] The sequence number (SN) information in the IP header does not need to be reconstructed from the original value. It is only necessary to ensure that the reconstructed message is in the same order as the original message in the message sequence. Therefore, the SN in the IP header is generated based on the SN in the PDCP header. For example, it can be the same as the SN in the PDCP header, or it can be started with 0 and incremented by 1 in the order of the SN in the PDCP header.

[0113] c) Calculate the checksum in the IP header based on the second data packet;

[0114] The second data packet here is the current second data packet.

[0115] In some embodiments, calculating the checksum in the IP header based on the second data packet includes:

[0116] If the Cyclic Redundancy Check (CRC) of the first data packet is successful, the checksum in the IP header is calculated based on the second data packet.

[0117] It is understandable that the presence or absence of errors is determined by the CRC checksum at the physical layer. If there are no errors, that is, if the CRC checksum of the first data packet is successful, the checksum in the IP header is calculated using the second data packet.

[0118] d) Configure the QoS-related fields in the IP header based on the Quality of Service (QoS) information of the first bearer or data stream;

[0119] Optionally, QoS-related fields include the Type of Service (TOS) field, the TOC field, etc. For example, if the QoS information of the first bearer or data stream indicates voice, then the corresponding fixed value is set according to the voice.

[0120] e) Generate segmentation-related information in the IP header using preset values;

[0121] Optionally, segmentation-related information includes: Flow label (IPv6), identification (IPv4), etc., and the segmentation-related information in the IP header can be generated using preset values.

[0122] f) Generate other information in the IP header besides the above items using preset values. That is, other information in the IP header besides the source IP address, destination IP address, SN, checksum, QoS related fields, and segmentation related information can be generated using preset values.

[0123] In some embodiments, the method further includes:

[0124] When the third data packet is sent, the terminal stops performing IP layer segmentation operations.

[0125] It is understandable that when the terminal sends a third data packet, the terminal stops performing IP layer segmentation operations to ensure that the third data packet is not segmented by IP.

[0126] In some embodiments, the UDP header of the second data packet is generated, including at least one of the following:

[0127] g) Based on the port information in the configuration information related to the first bearer or data stream, generate at least one of the source port information and the destination port information in the UDP header;

[0128] h) Calculate the checksum in the UDP header based on the second data packet;

[0129] i) Generate other information in the UDP header besides the above items using preset values. That is, other information in the UDP header besides the source port information, destination port information and checksum in the UDP header can be generated using preset values.

[0130] The terminal executes at least one of the above steps to generate the UDP header of the second data packet.

[0131] In some embodiments, the RTP header of the second data packet is generated, including at least one of the following:

[0132] j) Generate the timestamp in the RTP header based on the interval duration;

[0133] Optionally, the interval duration refers to the interval duration PTime between transmitted IP protocol data packets, that is, the difference in timestamps between adjacent IP protocol data packets.

[0134] Based on the interval duration, a timestamp can be generated in the RTP header. For example, the initial timestamp TimeStamp is the current time, and the TimeStamp of subsequent adjacent packets is the TimeStamp of the previous packet plus Ptime.

[0135] In some embodiments, the method further includes at least one of the following:

[0136] The terminal receives signaling from a network-side node, including the interval duration information, and the signaling is related to the first bearer or data stream.

[0137] The terminal learns the interval duration from the IMS signaling, which is related to the establishment or update of the first bearer or data stream.

[0138] In various embodiments of this application, network-side nodes may also be referred to as network-side devices or network-side functions.

[0139] Understandably, the terminal receives signaling from a network-side node that includes the interval duration information, the signaling being related to the first bearer or data stream, and / or obtains the interval duration from IMS signaling, the IMS signaling being related to establishing or updating the first bearer or data stream. Based on the interval duration, the terminal generates a timestamp in the RTP header.

[0140] k) Set the timestamp in the RTP header of the first second data packet to the preset time;

[0141] The timestamp in the RTP header of the first second data packet indicates the start time of the data stream. When generating the timestamp in the RTP header of the first second data packet, it is not necessary to generate a value that is exactly the same as the actual value. It is only necessary to ensure that the generated value allows the receiver to use the payload of the second data packet immediately. For example, if the payload of the second data packet is IMS multimedia data, it is sufficient to allow the receiver to play the IMS multimedia data immediately. Therefore, the timestamp in the RTP header of the first second data packet is set to a preset time, which can be the current time or any time in the past.

[0142] l) Generate the SN in the RTP header based on the SN in the PDCP header carrying the first data packet;

[0143] m) Based on the generated Synchronization Source (SSRC) identifier, set the SSRC in the RTP header;

[0144] Optionally, data packets from the same bearer or data stream may have the same SSRC in their RTP headers.

[0145] n) Set the value of the Contributing Source (CSRC) identifier in the RTP header using a preset value;

[0146] For example, the value of CSRC in the RTP header can be set to 0.

[0147] o) Generate other information in the RTP header besides the above items using preset values. That is, all information in the RTP header except for timestamp, SN, SSRC, and CSRC can be generated using preset values.

[0148] In some embodiments, the method further includes at least one of the following:

[0149] The terminal receives first indication information from a network-side node, the first indication information being used to indicate at least one of the following: not transmitting IP headers; not transmitting UDP headers; not transmitting RTP headers;

[0150] Enable the ability to perform the first operation.

[0151] Optionally, the second network node indicates the first indication information via a NAS message, or the first network node indicates the first indication information via the second network node.

[0152] The first instruction information can be understood as instructing the terminal to perform a first operation or to enable the capability to perform the first operation. After receiving the first instruction information, the terminal performs the first operation or enables the capability to perform the first operation.

[0153] In some embodiments, the terminal also performs:

[0154] Send the second data packet to the application layer or operating system layer; or

[0155] The third data packet that sends the first bearer or data stream includes:

[0156] Receive a fourth data packet sent by the application layer or operating system layer, and send the third data packet, wherein the fourth data packet includes the third data packet and any one of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0157] Understandably, the terminal receives a first data packet from a first bearer or data stream, and the first data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header; the terminal restores the IP header, or the IP and UDP header, or the IP, UDP, and RTP header from the first data packet, generates a second data packet, and sends the second data packet to the application layer or operating system layer.

[0158] The terminal receives a fourth data packet sent by the application layer or the operating system layer, deletes the IP header, or the IP and UDP header, or the IP, UDP and RTP header in the fourth data packet, generates the third data packet, and sends the third data packet.

[0159] In this embodiment, when the terminal receives a data packet from the first bearer or data stream, it restores its IP header, or restores its IP and UDP headers, or restores its IP, UDP, and RTP headers, and then sends it to the upper application layer or operating system layer for processing. The terminal receives the data packet sent by the application layer or operating system layer and deletes the IP header, or the IP and UDP header, or the IP, UDP, and RTP header from the data packet. This achieves that during the transmission of IP protocol data packets between the terminal and the network-side node, the IP protocol data packets sent by the sender do not have IP headers, or do not have IP and UDP headers, or do not have IP, UDP, and RTP headers. This reduces the size of the IP protocol data packets, shortens the data transmission time, improves communication quality, and thus enhances the user experience.

[0160] Figure 3 is a schematic diagram of the data transmission method provided in an embodiment of this application in the protocol stack. As shown in Figure 3, when the terminal UE sends an IP protocol data packet to the network-side node, it deletes the IP, UDP, and RTP headers and directly places the payload on top of the air interface data transmission protocol (i.e., on top of PDCP) for transmission (the packet length in the PDCP protocol needs to be adjusted). When the core network functions (Serving Gateway (SGW), PDN Gateway (PGW), and User Plane Function (UPF)) send an IP protocol data packet to the terminal, they delete the IP, UDP, and RTP headers and directly place the payload on top of the bearer protocol (i.e., the GPRS Tunneling Protocol for the User Plane (GTP-U)) for transmission (the packet length in the GTP-U protocol needs to be adjusted).

[0161] The base station does not enable IP-related functions (such as ROHC) based on the QoS information of the relevant bearer or data stream.

[0162] When the core network functions (SGW, PGW, UPF, or Access Gateway (AGW) etc.) receive data from the relevant bearer or data stream, they restore the IP, UDP, and RTP layers; when the terminal receives data from the relevant bearer or data stream, it restores the IP, DP, and RTP layers, and does not enable IP-related functions (such as ROHC).

[0163] It should be noted that the AGW in this application embodiment is the media gateway in the IMS system, namely the IP Multimedia Subsystem-Access Gateway (IMS-AGW).

[0164] The data transmission method provided in the embodiments of this application is described below from the perspective of the network side.

[0165] Figure 4 is a second schematic flowchart of the data transmission method provided in this application embodiment. This data transmission method is applied to a first network node, which may be a UPF, PGW, AGW (media gateway in the IMS system), a network node where PGW / UPF and AGW are co-located, or other network nodes capable of executing the method shown in Figure 4.

[0166] As shown in Figure 4, the method includes:

[0167] Step 200: The first network node performs at least one of the third and fourth operations.

[0168] The third operation includes at least one of the following:

[0169] Receive the third data packet from the first bearer or data stream, and forward the fifth data packet;

[0170] Receive the sixth data packet and forward the first data packet through the first bearer or data stream.

[0171] Understandably, the first network node receives a third data packet from the first bearer or data stream, which does not include any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header. It then recovers any of the following from the third data packet: an IP header; an IP and UDP header; or an IP, UDP, and RTP header. Finally, it generates a fifth data packet and forwards it. The fifth data packet includes the third data packet and any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

[0172] Alternatively, the first network node receives a sixth data packet, the sixth data packet including the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header, deletes any one of the following from the sixth data packet: an IP header; an IP and UDP header; or an IP, UDP, and RTP header, generates the first data packet, and forwards the first data packet through the first bearer or data stream.

[0173] The first bearer or data stream is used to transmit IP protocol data packets.

[0174] The fourth operation includes at least one of the following:

[0175] Receive second instruction information from the second network node, and perform the third operation based on the second instruction information;

[0176] Receive first capability information from the terminal, and perform the third operation based on the first capability information;

[0177] Optionally, the first network node receives the second instruction information from the second network node, and in response to the second instruction information, the first network node performs the third operation.

[0178] Optionally, the second indication information is used to indicate at least one of the following: not transmitting the IP header; requesting not to transmit the IP header; not transmitting the UDP header; requesting not to transmit the UDP header; not transmitting the RTP header; requesting not to transmit the RTP header.

[0179] Optionally, the first network node receives first capability information from the terminal, the first capability information being used to indicate that the terminal has the capability to perform the first operation.

[0180] Optionally, the first network node receives the NAS message sent by the terminal and obtains the first capability information through the NAS message.

[0181] In this embodiment, when the first network node receives a data packet of the first bearer or data stream, the data packet may lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers. The terminal restores the IP header of the data packet, or restores both IP and UDP headers, or restores both IP, UDP, and RTP headers. Alternatively, when the first network node sends a data packet of the first bearer or data stream to the terminal, the data packet may lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers. This achieves that during the transmission of IP protocol data packets between the sender and the terminal, the IP protocol data packets sent by the sender lack an IP header, or lack both IP and UDP headers, or lack both IP, UDP, and RTP headers, reducing the size of the IP protocol data packets, shortening data transmission time, improving communication quality, and thus enhancing user experience.

[0182] In some embodiments, the method further includes: the first network node generating the fifth data packet.

[0183] The first network node generates the fifth data packet in any of the following ways: the first network node generates the IP header of the fifth data packet; the first network node generates the IP and UDP headers of the fifth data packet; the first network node generates the IP, UDP and RTP headers of the fifth data packet.

[0184] Optionally, the first network node generates the IP header of the fifth data packet, including at least one of the following:

[0185] a) Based on the IP address information in the configuration information related to the first bearer or data stream, generate at least one of the source IP address and the destination IP address in the IP header;

[0186] b) Generate the SN in the IP header based on the sequence number SN in the GTP-U header carrying the third data packet;

[0187] It should be noted that the third data packet here can be the current third data packet, the third data packet preceding the current third data packet, or a combination of both. That is, the SN in the IP header is generated based on the SN of the current third data packet and / or the previous third data packet.

[0188] The sequence number (SN) information in the IP header does not need to be reconstructed from the original value. It is only necessary to ensure that the reconstructed message is in the same order as the original message in the message sequence. Therefore, the SN in the IP header is generated based on the SN in the PDCP header. For example, it can be the same as the SN in the PDCP header, or it can be started with 0 and incremented by 1 in the order of the SN in the PDCP header.

[0189] c) Calculate the checksum in the IP header based on the fifth data packet;

[0190] The fifth data packet here refers to the current fifth data packet.

[0191] Optionally, calculating the checksum in the IP header based on the fifth data packet includes:

[0192] If the CRC check of the third data packet is successful, the checksum in the IP header is calculated based on the fifth data packet.

[0193] It is understandable that the presence or absence of errors is determined by the CRC checksum at the physical layer. If there are no errors, that is, if the CRC checksum of the third data packet is successful, the checksum in the IP header is calculated using the fifth data packet.

[0194] d) Configure the QoS-related fields in the IP header based on the QoS information of the first bearer or data stream;

[0195] Optionally, QoS-related fields include TOS, TOC, etc. For example, if the QoS information of the first bearer or data stream indicates voice, then the corresponding fixed value is set according to the voice.

[0196] e) Generate segmentation-related information in the IP header using preset values;

[0197] Optionally, segmentation-related information includes: Flow label (IPv6), identification (IPv4), etc., and the segmentation-related information in the IP header can be generated using preset values.

[0198] f) Generate other information in the IP header besides the above items using preset values. That is, other information in the IP header besides the source IP address, destination IP address, SN, checksum, QoS related fields and segmentation related information can be generated using preset values.

[0199] In some embodiments, the method further includes:

[0200] When forwarding the first data packet, the first network node stops performing IP layer segmentation operations.

[0201] Understandably, when the first network node forwards the first data packet, the first network node stops performing IP layer segmentation operations to ensure that the first data packet is not segmented by IP.

[0202] In this embodiment, when the first network node forwards IP protocol data packets, it generates an IP header before forwarding. This enables the IP protocol data packets sent by the sender to be without an IP header, or without IP and UDP headers, or without IP, UDP and RTP headers during the transmission of IP protocol data packets between the sender and the terminal. This reduces the size of the IP protocol data packets, shortens the data transmission time, improves communication quality, and enhances the user experience.

[0203] Optionally, the first network node generates the UDP header of the fifth data packet, including at least one of the following:

[0204] g) Based on the port information in the configuration information related to the first bearer or data stream, generate the source port information and destination port information in the UDP header;

[0205] h) Calculate the checksum in the UDP header based on the fifth data packet;

[0206] i) Generate other information in the UDP header besides the above items using preset values. That is, other information in the UDP header besides the source port information, destination port information and checksum in the UDP header can be generated using preset values.

[0207] In this embodiment, when the first network node forwards IP protocol data packets, it generates IP headers and UDP headers before forwarding. The IP protocol data packets sent by the sender do not have IP headers, or do not have both IP and UDP headers, which reduces the size of the IP protocol data packets, shortens the data transmission time, improves communication quality, and thus enhances the user experience.

[0208] Optionally, the first network node generates the RTP header of the fifth data packet, including at least one of the following:

[0209] j) Generate the timestamp in the RTP header based on the interval duration;

[0210] Optionally, the interval duration refers to the interval duration PTime between transmitted IP protocol data packets, that is, the difference in timestamps between adjacent IP protocol data packets.

[0211] Based on the interval duration, a timestamp can be generated in the RTP header. For example, the initial timestamp TimeStamp is the current time, and the TimeStamp of subsequent adjacent packets is the TimeStamp of the previous packet plus Ptime.

[0212] In some embodiments, the method further includes at least one of the following:

[0213] The first network node receives signaling including the interval duration information from the third or fourth network node, and the signaling is related to the first bearer or data stream;

[0214] The first network node learns the interval duration from IMS signaling, which is related to the establishment or update of the first bearer or data stream.

[0215] Optionally, the third network node is a Proxy-Call Session Control Function (P-CSCF), and the fourth network node is a PCRF or PCF.

[0216] Understandably, the first network node receives signaling including the interval duration information from a third or fourth network node, the signaling being related to the first bearer or data stream, and / or obtains the interval duration from IMS signaling, the IMS signaling being related to establishing or updating the first bearer or data stream. The first network node generates a timestamp in the RTP header based on the interval duration.

[0217] k) Set the timestamp in the RTP header of the first fifth data packet to the preset time;

[0218] The timestamp in the RTP header of the first fifth data packet indicates the start time of the data stream. When generating the timestamp in the RTP header of the first fifth data packet, it is not necessary to generate a value that is exactly the same as the actual value. It is only necessary to ensure that the generated value allows the receiver to use the payload of the fifth data packet immediately. For example, if the payload of the fifth data packet is IMS multimedia data, then it is necessary to allow the receiver to play the IMS multimedia data immediately. Therefore, the timestamp in the RTP header of the first fifth data packet is set to a preset time, which can be the current time or any time in the past.

[0219] l) Generate the SN in the RTP header based on the SN in the GTP-U header carrying the third data packet;

[0220] m) Based on the generated synchronization source identifier SSRC, set the SSRC in the RTP header;

[0221] Optionally, data packets from the same bearer or data stream may have the same SSRC in their RTP headers.

[0222] n) Set the value of the Contribution Source Identifier (CSRC) in the RTP header using a preset value;

[0223] For example, the value of CSRC in the RTP header can be set to 0.

[0224] o) Generate all information in the RTP header except for the items mentioned above using preset values. That is, all information in the RTP header except for the timestamp, SN, SSRC, and CSRC can be generated using preset values.

[0225] In this embodiment, when the first network node forwards IP protocol data packets, it generates IP, UDP, and RTP headers before forwarding. This enables the IP protocol data packets sent by the sender to be without IP, UDP, and RTP headers during the transmission of IP protocol data packets between the sender and the terminal, thereby reducing the size of the IP protocol data packets, shortening the data transmission time, improving communication quality, and ultimately enhancing the user experience.

[0226] In some embodiments, the method further includes at least one of the following:

[0227] The first network node sends the interval duration to the access network node through the second network node;

[0228] The first network node sends a first indication message to the terminal, or sends the first indication message to the terminal through the second network node, wherein the first indication message is used to indicate at least one of the following: not to transmit the IP header; not to transmit the UDP header; not to transmit the RTP header;

[0229] The first network node sends a third indication message to the access network node, or sends a third indication message to the access network node through the second network node. The third indication message is used to indicate that functions related to the IP layer protocol are not enabled.

[0230] Figure 5 is a schematic diagram of the interaction between the first network node, the terminal, and other network nodes provided in the embodiments of this application.

[0231] Optionally, the first network node sends the interval duration to the access network node through the second network node, so that the access network node can schedule the air interface resources of the first bearer or data stream according to the interval duration.

[0232] Optionally, the first network node sends a first instruction message to the terminal, or sends the first instruction message to the terminal through the second network node, thereby instructing the terminal to perform a first operation, or enabling the terminal to perform the first operation.

[0233] Optionally, the first network node sends a third indication message to the access network node, or the second network node sends the third indication message to the access network node, thereby instructing the access network node not to enable IP layer protocol-related functions, such as instructing the access network node not to enable the ROHC function.

[0234] In some embodiments, the method further includes:

[0235] The first network node selects a third network node and sends the information of the third network node to the terminal.

[0236] For example, the terminal can be informed of the information of the third network node through the Protocol Configuration Options (PCO) field.

[0237] Figure 6 is a flowchart of the data transmission method provided in the embodiment of this application. The data transmission method is applied to a second network node. Optionally, the second network node is an AMF, SMF, MME or other network node capable of executing the data transmission method shown in Figure 6.

[0238] As shown in Figure 6, the data transmission method includes:

[0239] Step 300: The second network node performs the fifth and sixth operations;

[0240] The fifth operation includes at least one of the following:

[0241] Send a first indication message to the terminal, the first indication message being used to indicate at least one of the following: not to transmit the IP header; not to transmit the UDP header; not to transmit the RTP header;

[0242] Send a second indication message to the first network node, the second indication message being used to indicate at least one of the following: not to transmit IP headers; request not to transmit IP headers; not to transmit UDP headers; request not to transmit UDP headers; not to transmit RTP headers; request not to transmit RTP headers.

[0243] Send a third indication message to the access network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0244] Send an interval duration to the access network node, the interval duration being used to indicate the interval between transmitted data packets;

[0245] The sixth operation includes: receiving first capability information from the terminal and performing the fifth operation based on the first capability information.

[0246] Optionally, the second network node sends a first instruction message to the terminal, thereby instructing the terminal to perform a first operation or enabling the ability to perform the first operation.

[0247] Optionally, the second network node sends a second instruction message to the first network node, thereby instructing the first network node to perform a third operation. The first network node responds to the second instruction message and performs the third operation.

[0248] Optionally, the second network node sends a third indication message to the access network node, thereby instructing the access network node not to enable IP layer protocol-related functions, for example, instructing the access network node not to enable the ROHC function.

[0249] Optionally, the second network node sends the interval duration to the access network node, so that the access network node can schedule the air interface resources of the first bearer or data stream according to the interval duration.

[0250] In this embodiment, the second network node interacts with the first network node, the access network node, and the terminal to transmit IP protocol data packets without IP layer, UDP layer, or RTP layer protocol headers, thereby reducing the size of the IP protocol data packets, shortening data transmission time, improving communication quality, and ultimately enhancing user experience.

[0251] In some embodiments, the method further includes:

[0252] Upon receiving the first capability information from the terminal, the second network node selects the first network node based on at least one of the first capability information and the terminal's wireless access technology.

[0253] Optionally, the second network node receives the NAS message from the terminal and learns the first capability information, which is used to indicate that the terminal has the ability to perform the first operation.

[0254] The second network node selects the first network node based on at least one of the first capability information and the wireless access technology of the terminal. The selected first network node can be a PGW or UPF co-located with the AGW, or it can be either a PGW or a UPF.

[0255] That is, the first network node is selected based on at least one of the terminal's first capability information and the terminal's Radio Access Technology (RAT) type.

[0256] In this embodiment, the second network node interacts with the terminal to obtain capability information. Based on the capability information and the terminal's access status, the second network node determines the first network node serving the terminal. The second network node can instruct the first network node to perform a third operation, which disables IP layer protocol-related functions, thereby reducing the size of IP protocol data packets, shortening data transmission time, and improving user experience.

[0257] In some embodiments, the method further includes:

[0258] The second network node receives at least one of the following from the first network node: the first indication information; the third indication information; and the interval duration.

[0259] It is understandable that the first network node receives the first instruction information sent by the second network node, and the second network node forwards the first instruction information to the terminal.

[0260] Optionally, the first network node receives the third indication information sent by the second network node and forwards the third indication information to the access network node to instruct the access network node not to enable IP layer protocol-related functions.

[0261] Optionally, the first network node receives the interval duration sent by the first network node and forwards the interval duration to the access network node, so that the access network node can schedule the air interface resources of the first bearer or data stream according to the interval duration.

[0262] In some embodiments, the method further includes:

[0263] The second network node receives the interval duration from the third network node.

[0264] Optionally, the second network node receives the interval duration from the third network node and forwards the interval duration to the access network node, so that the access network node can schedule the air interface resources of the first bearer or data stream according to the interval duration.

[0265] In this embodiment, the second network node obtains the interval duration for transmitting IP protocol data packets by interacting with the first or third network node, and sends the interval duration to the access network node, so that the access network node can schedule air interface resources according to the interval duration, thereby improving resource utilization.

[0266] Figure 7 is a flowchart of the data transmission method provided in the embodiment of this application. The data transmission method is applied to a third network node, which may be a P-CSCF or other network node capable of implementing the data transmission method shown in Figure 7.

[0267] As shown in Figure 7, the data transmission method includes:

[0268] Step 400: The third network node selects the first network node of the service terminal as the media gateway in the IMS system.

[0269] In this embodiment, the media gateway in the IMS system and the first network node of the service terminal are co-located, that is, the media gateway in the IMS system and the first network node of the service terminal are deployed on the same device.

[0270] In this embodiment, the third network node selects the first network node of the service terminal as the media gateway in the IMS system, which can shorten the data transmission time and improve the user experience.

[0271] In some embodiments, the third network node selects the first network node of the serving terminal as the media gateway in the IMS system, including:

[0272] The third network node selects the media gateway based on the terminal's IP address.

[0273] The third network node selects the first network node of the service terminal based on the terminal's IP address, and acts as the media gateway in the IMS system.

[0274] Figure 8 is a fifth flowchart of the data transmission method provided in the embodiments of this application. This data transmission method is applied to an access network node, which can be called an access network function or access network device, such as a base station.

[0275] As shown in Figure 8, the data transmission method includes:

[0276] Step 500: The access network node performs the seventh operation.

[0277] The seventh operation includes at least one of the following:

[0278] The interval time at which the access network node receives the data sent by the first network node;

[0279] The interval duration at which the access network node receives data sent by the second network node;

[0280] The access network node receives a third indication message sent by the first network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0281] The access network node receives a third indication message sent by the second network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0282] The access network node does not enable IP layer protocol-related functions based on at least one of the following: terminal access status, information related to the first bearer or data stream, and session information related to the first bearer or data stream;

[0283] The access network node receives a third data packet from the first bearer or data stream of the terminal, and transmits the third data packet to the first network node via the GTP-U protocol. The third data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0284] Receive a first data packet from a first network node, and transmit the first data packet to the terminal via the PDCP protocol. The first data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0285] In this embodiment, the access network node interacts with the first network node, the second network node, or the terminal to realize the transmission of the payload on the air interface data transmission protocol or bearer protocol, which can reduce the size of IP protocol data packets, shorten the data transmission time, and improve the user experience.

[0286] In some embodiments, the method further includes:

[0287] The access network node schedules the air interface resources of the first bearer or data stream based on the specified interval duration.

[0288] It is understandable that the access network node receives the interval time sent by the first network node or the second network node, and schedules the air interface resources of the first bearer or data stream based on the interval time.

[0289] In this embodiment, the access network node can schedule air interface resources according to the time interval, which can improve resource utilization.

[0290] Optionally, the method further includes:

[0291] The access network node does not enable IP layer protocol-related functions based on the third indication information.

[0292] It is understandable that the access network node receives the third indication information sent by the first network node or the second network node, and based on the third indication information, does not enable the functions related to the IP layer protocol.

[0293] In this embodiment, after receiving the third indication information sent by the first network node or the second network node, the access network node does not enable the functions related to the IP layer protocol. This enables data transmission between the terminal and the network-side node to be performed without IP and headers, or without IP and UDP headers, or without IP, UDP and RTP headers. This can reduce the size of IP protocol data packets, shorten data transmission time, and improve user experience.

[0294] Figure 9 is a schematic diagram of the interaction flow of the data transmission method provided in this application embodiment. As shown in Figure 9, the first network node is co-located with the media gateway in the IMS system, and the data transmission method includes the following steps:

[0295] 900. The UE establishes a Packet Data Network (PDN) connection or Protocol Data Unit (PDU) session via satellite access (NTN, GEO, LEO, MEO). Upon receiving the establishment request, the MME / SMF / AMF optionally sends its capabilities to the network, such as to the MME / SMF / AMF, via a NAS message during the mobile network access process. This capability indicates that the UE can perform a first operation. Optionally, the MME / SMF / AMF selects a PGW / UPF based on at least one of the UE's Radio Access Technology (RAT type) and capability information. In this embodiment, a PGW / UPF co-located with the AGW is selected. The PGW / UPF selects a P-CSCF and informs the UE of the P-CSCF information (e.g., via the PCO field). In this embodiment, the selected P-CSCF supports selecting an AGW co-located with the PGW / UPF.

[0296] 901. The UE initiates a call and sends a SIP INVITE message, which includes the UE's Session Description Protocol (SDP) information.

[0297] 902. The IMS system responds with a SIP 183 Progress message, including SDP information from the called side, which includes PTime information.

[0298] 903. The P-CSCF selects the PGW / UPF serving the UE as the AGW.

[0299] 904. P-CSCF and AGW reserve media resources for interaction. During this interaction process, SDP information will be sent to AGW, and naturally PTime will also be sent to AGW.

[0300] 905. P-CSCF interacts with PCRF / PCF to reserve bearer or QoS flow resources. This process informs PCRF / PCF of information such as source IP address, destination IP address, source port, destination port, and protocol number.

[0301] 906. PCF / PCRF notifies the UE's MME / SMF / AMF, and MME / SMF / AMF notifies the UE's PGW / UPF (co-located with AGW) reserved bearer resources. This process will inform the PGW / UPF of information such as source IP address, destination IP address, source port, destination port, and protocol number through MME / SMF / AMF.

[0302] 907. PCF / PCRF response to P-CSCF.

[0303] 908. The P-CSCF forwards the SIP 183 Progress message to the UE.

[0304] 909. When the MME / SMF / AMF performs a session update operation and reserves bearer resources, optionally, the PGW / UPF (co-located with the AGW) sends a PTime to the base station through the MME / SMF / AMF, which is used by the base station to schedule air interface resources based on the PTime. Optionally, the PGW / UPF instructs the base station to stop ROHC through the MME / SMF, or the MME / SMF / AMF may instruct the base station to stop ROHC, or the base station may stop ROHC based on the UE's access status (e.g., satellite access) and the QoS information of the bearer / data stream. Optionally, the MME / SMF / AMF instructs the UE to perform a first operation through a NAS message, or the PGW / UPF instructs the UE to perform a first operation through the MME / SMF / AMF (e.g., through the PCO field).

[0305] 910. The IMS session establishment process continues.

[0306] 911. After the IMS session is established, the AGW (co-located with the PGW / UPF) receives the IP multimedia data sent to the UE, deletes the IP, UDP, and RTP headers, and transmits the IP multimedia data payload to the base station via the GTP-U protocol. The base station forwards the IP multimedia data payload, that is, it transmits the payload to the UE via the PDCP protocol.

[0307] 912. The UE receives the data packet of the corresponding bearer or data stream, restores the IP, UDP and RTP headers, and then delivers the restored data packet to the application.

[0308] 913. When a UE needs to send data packets to the network through the corresponding bearer or data stream, the IP, UDP, and RTP protocol layers are removed, and the IP multimedia data payload is transmitted to the base station via the PDCP protocol. The base station forwards the IP multimedia data payload, that is, it transmits the payload to the PGW / UPF via the GTP-U protocol.

[0309] 914. The AGW (co-located with the PGW / UPF) receives IP multimedia data sent by the UE, restores the IP, UDP, and RTP protocol layers, and then sends out the restored data packets.

[0310] It should be noted that the AGW (co-located with PGW / UPF) or PGW / UPF (co-located with AGW) in the above steps refers to the first network node in the aforementioned embodiments, the MME / SMF / AMF in the above steps refers to the second network node in the aforementioned embodiments, the P-CSCF in the above steps refers to the third network node in the aforementioned embodiments, and the PCF / PCRF in the above steps refers to the fourth network node in the aforementioned embodiments.

[0311] Figure 10 is a second schematic diagram of the interaction flow of the data transmission method provided in this application embodiment. As shown in Figure 10, the first network node and the media gateway in the IMS system are separate. The data transmission method includes the following steps:

[0312] Steps 1000-1002 are the same as steps 900-902 in Figure 9.

[0313] Step 1003: P-CSCF selects AGW. P-CSCF interacts with AGW to reserve media resources, and this interaction process will send SDP information to AGW.

[0314] Step 1004: The P-CSCF interacts with the PCRF / PCF to request reserved bearer or QoS flow resources. During this process, the P-CSCF will inform the PCF / PCRF of information such as the source IP address, destination IP address, source port, destination port, and protocol number. Optionally, the P-CSCF will inform the PCF / PCRF of the PTime.

[0315] Step 1005: The PCF / PCRF notifies the UE's MME / SMF / AMF, and the MME / SMF / AMF notifies the UE's PGW / UPF of reserved bearer resources or data stream resources. This process involves informing the PGW / UPF of information such as the source IP address, destination IP address, source port, destination port, and protocol number through the MME / SMF / AMF. Optionally, the PCF / PCRF informs the MME / SMF / AMF of the PTime, and the MME / SMF / AMF in turn informs the PGW / UPF.

[0316] Steps 1006-1007: PGW / UPF responds to PCF / PCRF, and PCF / PCRF responds to P-CSCF.

[0317] Steps 1008-10014 are the same as steps 908-914 in Figure 9.

[0318] It should be noted that PGW / UPF in the above steps refers to the first network node in the aforementioned embodiments, MME / SMF / AMF in the above steps refers to the second network node in the aforementioned embodiments, P-CSCF in the above steps refers to the third network node in the aforementioned embodiments, and PCF / PCRF in the above steps refers to the fourth network node in the aforementioned embodiments.

[0319] The data transmission method provided in this application embodiment can reduce the size of IP multimedia data, shorten transmission time, and improve user experience when satellite access is available.

[0320] The data transmission method provided in this application can be executed by a data transmission device. This application uses a data transmission device executing the data transmission method as an example to illustrate the data transmission device provided in this application.

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

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

[0323] Figure 11 is a schematic diagram of the structure of a data transmission device provided in an embodiment of this application. Referring to Figure 11, when the data transmission device is a terminal or a component in a terminal, the data transmission device 1100 includes a first processing module 1101, which is used to perform at least one of a first operation and a second operation.

[0324] The first operation includes at least one of the following:

[0325] Receive a first data packet from a first bearer or data stream, and generate a second data packet, wherein the second data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0326] Send a third data packet of the first bearer or data stream, wherein the third data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0327] The second operation includes: sending first capability information to a network-side node, wherein the first capability information is used to indicate that the terminal has the capability to perform the first operation;

[0328] The first bearer or data stream is used to transmit IP protocol data packets.

[0329] Optionally, the IP header of the second data packet is generated, including at least one of the following:

[0330] Based on the IP address information in the configuration information related to the first bearer or data stream, at least one of the source IP address and the destination IP address in the IP header is generated;

[0331] The SN in the IP header is generated based on the sequence number SN in the PDCP header carrying the first data packet;

[0332] Calculate the checksum in the IP header based on the second data packet;

[0333] Configure the QoS-related fields in the IP header based on the QoS information of the first bearer or data stream;

[0334] The segmentation-related information in the IP header is generated using preset values;

[0335] The IP header is generated using preset values ​​to include all information other than those mentioned above.

[0336] Optionally, calculating the checksum in the IP header based on the second data packet includes:

[0337] If the CRC check of the first data packet is successful, the checksum in the IP header is calculated based on the second data packet.

[0338] Optionally, the first processing module is further configured to:

[0339] When the third data packet is sent, the terminal stops performing IP layer segmentation operations.

[0340] Optionally, the UDP header of the second data packet is generated, including at least one of the following:

[0341] Based on the port information in the configuration information related to the first bearer or data stream, at least one of the source port information and the destination port information in the UDP header is generated;

[0342] Based on the second data packet, calculate the checksum in the UDP header;

[0343] The UDP header is generated using preset values ​​to include all information other than those mentioned above.

[0344] Optionally, the RTP header of the second data packet is generated, including at least one of the following:

[0345] The timestamp in the RTP header is generated based on the interval duration;

[0346] Set the timestamp in the RTP header of the first second data packet to the preset time;

[0347] The SN in the RTP header is generated based on the SN in the PDCP header carrying the first data packet;

[0348] Based on the generated synchronization source identifier SSRC, set the SSRC in the RTP header;

[0349] The value of the Contribution Source Identifier (CSRC) in the RTP header is set using a preset value;

[0350] The RTP header is generated using preset values, and includes all other information besides the items mentioned above.

[0351] Optionally, it also includes a first receiving module for performing at least one of the following:

[0352] The terminal receives signaling from a network-side node, including the interval duration information, and the signaling is related to the first bearer or data stream.

[0353] The terminal learns the interval duration from the IMS signaling, which is related to the establishment or update of the first bearer or data stream.

[0354] Optionally, a second receiving module is also included, for:

[0355] Receive first indication information from the network-side node, the first indication information being used to indicate at least one of the following: not to transmit IP headers; not to transmit UDP headers; not to transmit RTP headers;

[0356] The first processing module is further configured to: enable the ability to perform the first operation.

[0357] Optionally, the first processing module is further configured to:

[0358] Send the second data packet to the application layer or operating system layer; or...

[0359] The third data packet that sends the first bearer or data stream includes:

[0360] Receive a fourth data packet sent by the application layer or operating system layer, and send the third data packet, wherein the fourth data packet includes the third data packet and any one of the following: IP header; IP and UDP header; IP, UDP and RTP header.

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

[0362] Figure 12 is a second structural schematic diagram of the data transmission device provided in the embodiment of this application. Referring to Figure 12, when the data transmission device is a first network node or a component in the first network node, the data transmission device 1200 includes a second processing module 1201, which is used to perform at least one of the third and fourth operations.

[0363] The third operation includes at least one of the following:

[0364] Receive the third data packet from the first bearer or data stream, and forward the fifth data packet;

[0365] Receive the sixth data packet and forward the first data packet through the first bearer or data stream;

[0366] The fourth operation includes at least one of the following:

[0367] Receive second instruction information from the second network node, and perform the third operation based on the second instruction information;

[0368] Receive first capability information from the terminal, and perform the third operation based on the first capability information;

[0369] The first bearer or data stream is used to transmit IP protocol data packets;

[0370] The third data packet does not include any of the following: IP header; IP and UDP header; IP, UDP and RTP header;

[0371] The fifth data packet includes the third data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

[0372] The first data packet does not include any of the following: IP header; IP and UDP header; IP, UDP, and RTP header;

[0373] The sixth data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

[0374] Optionally, the second processing module 1201 is further configured to: generate the IP header of the fifth data packet, wherein generating the IP header of the fifth data packet includes at least one of the following:

[0375] Based on the IP address information in the configuration information related to the first bearer or data stream, at least one of the source IP address and the destination IP address in the IP header is generated;

[0376] The SN in the IP header is generated based on the sequence number SN in the GTP-U header carrying the third data packet;

[0377] Based on the fifth data packet, calculate the checksum in the IP header;

[0378] Configure the QoS-related fields in the IP header based on the QoS information of the first bearer or data stream;

[0379] The segmentation-related information in the IP header is generated using preset values;

[0380] The IP header is generated using preset values ​​to include all information other than those mentioned above.

[0381] Optionally, calculating the checksum in the IP header based on the fifth data packet includes:

[0382] If the CRC check of the third data packet is successful, the checksum in the IP header is calculated based on the fifth data packet.

[0383] Optionally, the second processing module 1201 is further configured to:

[0384] If the first data packet is forwarded, the IP layer segmentation operation is stopped.

[0385] Optionally, the second processing module 1201 is further configured to: generate a UDP header for the fifth data packet, wherein generating the UDP header for the fifth data packet includes at least one of the following:

[0386] Based on the port information in the configuration information related to the first bearer or data stream, the source port information and destination port information in the UDP header are generated.

[0387] Based on the fifth data packet, calculate the checksum in the UDP header;

[0388] The UDP header is generated using preset values ​​to include all information other than those mentioned above.

[0389] Optionally, the second processing module 1201 is further configured to: generate the RTP header of the fifth data packet, wherein generating the RTP header of the fifth data packet includes at least one of the following:

[0390] The timestamp in the RTP header is generated based on the interval duration;

[0391] Set the timestamp in the RTP header of the first fifth data packet to the preset time;

[0392] The SN in the RTP header is generated based on the SN in the GTP-U header carrying the third data packet;

[0393] Based on the generated synchronization source identifier SSRC, set the SSRC in the RTP header;

[0394] The value of the Contribution Source Identifier (CSRC) in the RTP header is set using a preset value;

[0395] The RTP header is generated using preset values, and includes all other information besides the items mentioned above.

[0396] Optionally, a second receiving module is also included, for:

[0397] Receive signaling including the interval duration information from a third or fourth network node, wherein the signaling is related to the first bearer or data stream;

[0398] The interval duration is obtained from IMS signaling, which is related to the establishment or update of the first bearer or data stream.

[0399] Optionally, it also includes a first sending module for performing at least one of the following:

[0400] The interval duration is sent to the access network node through the second network node;

[0401] Sending a first indication message to the terminal, or sending the first indication message to the terminal through a second network node, wherein the first indication message is used to indicate at least one of the following: not transmitting an IP header; not transmitting a UDP header; not transmitting an RTP header;

[0402] Send a third indication message to the access network node, or send a third indication message to the access network node through a second network node, wherein the third indication message is used to indicate that IP layer protocol-related functions are not enabled.

[0403] Optionally, the second processing module 1201 is further configured to:

[0404] The first network node selects a third network node and sends the information of the third network node to the terminal.

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

[0406] Figure 13 is a third structural schematic diagram of the data transmission device provided in the embodiment of this application. Referring to Figure 13, when the data transmission device is a second network node or a component in the second network node, the data transmission device 1300 includes a third processing module 1301, which is used to perform the fifth operation and the sixth operation.

[0407] The fifth operation includes at least one of the following:

[0408] Send a first indication message to the terminal, the first indication message being used to indicate at least one of the following: not to transmit the IP header; not to transmit the UDP header; not to transmit the RTP header;

[0409] Send a second indication message to the first network node, the second indication message being used to indicate at least one of the following: not to transmit IP headers; request not to transmit IP headers; not to transmit UDP headers; request not to transmit UDP headers; not to transmit RTP headers; request not to transmit RTP headers.

[0410] Send a third indication message to the access network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0411] Send an interval duration to the access network node, the interval duration being used to indicate the interval between transmitted data packets;

[0412] The sixth operation includes: receiving first capability information from the terminal and performing the fifth operation based on the first capability information.

[0413] Optionally, the third processing module is further configured to:

[0414] Upon receiving the first capability information from the terminal, the first network node is selected based on at least one of the first capability information and the wireless access technology of the terminal.

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

[0416] Figure 14 is a fourth structural schematic diagram of the data transmission device provided in the embodiments of this application. Referring to Figure 14, when the data transmission device is a third network node or a component in the third network node, the data transmission device 1400 includes a fourth processing module 1401, which selects the first network node of the service terminal as the media gateway in the IMS system.

[0417] Optionally, selecting the first network node of the service terminal as the media gateway in the IMS system includes:

[0418] The media gateway is selected based on the IP address of the terminal.

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

[0420] Figure 15 is a fifth structural schematic diagram of the data transmission device provided in an embodiment of this application. Referring to Figure 15, when the data transmission device is an access network node or a component in an access network node, the data transmission device 1500 includes a fifth processing module 1501 for performing a seventh operation, the seventh operation including at least one of the following:

[0421] The interval for receiving data from the first network node;

[0422] The interval for receiving data from the second network node;

[0423] Receive a third indication message sent by the first network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0424] Receive a third indication message sent by the second network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled;

[0425] IP layer protocol-related functions are not enabled based on at least one of the following: terminal access status, information related to the first bearer or data stream, and session information related to the first bearer or data stream;

[0426] Receive a third data packet from the first bearer or data stream of the terminal, and transmit the third data packet to the first network node via the GTP-U protocol. The third data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0427] Receive a first data packet from a first network node, and transmit the first data packet to the terminal via the PDCP protocol. The first data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

[0428] Optionally, the fifth processing module is further configured to:

[0429] The air interface resources of the first bearer or data stream are scheduled based on the interval duration.

[0430] Optionally, the fifth processing module is further configured to:

[0431] Based on the third indication information, IP layer protocol-related functions are not enabled.

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

[0433] Figure 16 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 16, this application also provides a communication device 1600, including a processor 1601 and a memory 1602. The memory 1602 stores a program or instructions that can run on the processor 1601. For example, when the communication device 1600 is a terminal, the program or instructions executed by the processor 1601 implement the various steps of the above-described data transmission method embodiment and achieve the same technical effect. When the communication device 1600 is a network-side device, the program or instructions executed by the processor 1601 implement the various steps of the above-described data transmission method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0434] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the data transmission device shown in FIG11. Specifically, FIG17 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0435] The terminal 1700 includes, but is not limited to, at least some of the following components: radio frequency unit 1701, network module 1702, audio output unit 1703, input unit 1704, sensor 1705, display unit 1706, user input unit 1707, interface unit 1708, memory 1709, and processor 1710.

[0436] Those skilled in the art will understand that terminal 1700 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 1710 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 14 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.

[0437] It should be understood that, in this embodiment, the input unit 1704 may include a graphics processor 17041 and a microphone 17042. The graphics processor 17041 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 1706 may include a display panel 17061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 1707 includes at least one of a touch panel 17071 and other input devices 17072. The touch panel 17071 is also called a touch screen. The touch panel 17071 may include a touch detection device and a touch controller. Other input devices 17072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

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

[0439] The memory 1709 can be used to store software programs or instructions, as well as various data. The memory 1709 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 1709 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 1709 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0440] Processor 1710 may include one or more processing modules; optionally, processor 1710 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 1710.

[0441] The processor 1710 is configured to perform at least one of the first operation and the second operation;

[0442] The first operation includes at least one of the following:

[0443] Receive a first data packet from a first bearer or data stream, and generate a second data packet, wherein the second data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0444] Send a third data packet of the first bearer or data stream, wherein the third data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header;

[0445] The second operation includes: the terminal sending first capability information to a network-side node, wherein the first capability information is used to indicate that the terminal has the capability to perform the first operation;

[0446] The first bearer or data stream is used to transmit IP protocol data packets.

[0447] In this embodiment, when the terminal receives a data packet from the first bearer or data stream, it restores its IP header, or restores its IP and UDP headers, or restores its IP, UDP, and RTP headers. When sending a data packet from the first bearer or data stream, the data packet does not contain an IP header, or does not contain an IP and UDP header, or does not contain an IP, UDP, and RTP header. This achieves the transmission of IP protocol data packets with network-side nodes without IP layer, UDP layer, or RTP layer protocol headers, reducing the size of IP protocol data packets, shortening data transmission time, improving communication quality, and thus enhancing user experience.

[0448] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0449] 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 method embodiment shown in FIG8. 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 can achieve the same technical effect.

[0450] Specifically, this application embodiment also provides a network-side device, which can be the data transmission device shown in FIG15. FIG18 is a schematic diagram of the structure of one of the network-side devices implementing the embodiments of this application. As shown in FIG18, the network-side device 1800 includes: an antenna 1801, a radio frequency device 1802, a baseband device 1803, a processor 1804, and a memory 1805. The antenna 1801 is connected to the radio frequency device 1802. In the uplink direction, the radio frequency device 1802 receives information through the antenna 1801 and sends the received information to the baseband device 1803 for processing. In the downlink direction, the baseband device 1803 processes the information to be transmitted and sends it to the radio frequency device 1802. The radio frequency device 1802 processes the received information and transmits it through the antenna 1801.

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

[0452] The baseband device 1803 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG18. One of the chips is, for example, a baseband processor, which is connected to the memory 1805 via a bus interface to call the program in the memory 1805 and execute the network device operation shown in the above method embodiment.

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

[0454] Specifically, the network-side device 1800 in this application embodiment further includes: instructions or programs stored in memory 1805 and executable on processor 1804. Processor 1804 calls the instructions or programs in memory 1805 to execute the methods executed by each module shown in FIG15 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0455] Specifically, this application also provides a network-side device. Figure 19 is a second schematic diagram of the structure of a network-side device implementing an embodiment of this application. As shown in Figure 19, the network-side device 1900 includes: a processor 1901, a network interface 1902, and a memory 1903. The network-side device can be the data transmission device shown in Figures 12, 13, or 14. The network interface 1902 is, for example, a Common Public Radio Interface (CPRI).

[0456] Specifically, the network-side device 1900 in this application embodiment further includes: instructions or programs stored in memory 1903 and executable on processor 1901. Processor 1901 calls the instructions or programs in memory 1903 to execute the methods executed by the modules shown in FIG12, 13 or 14 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

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

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

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

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

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

[0462] This application also provides a communication system, including: a terminal, a first network node, a second network node, a third network node, and an access network node. The terminal can be used to perform the steps of the method described above, the first network node can be used to perform the steps of the method described above, the second network node can be used to perform the steps of the method described above, the third network node can be used to perform the steps of the method described above, and the access network node is used to perform the steps of the method described above.

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

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

[0465] 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, applied to a terminal, comprising: The terminal performs at least one of the first operation and the second operation; The first operation includes at least one of the following: Receive a first data packet from a first bearer or data stream, and generate a second data packet, wherein the second data packet includes the first data packet and any one of the following: Internet Protocol (IP) header; IP and User Datagram Protocol (UDP) header; IP, UDP, and Real-Time Transport Protocol (RTP) header; Send a third data packet of the first bearer or data stream, wherein the third data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header; The second operation includes: the terminal sending first capability information to a network-side node, wherein the first capability information is used to indicate that the terminal has the capability to perform the first operation; The first bearer or data stream is used to transmit IP protocol data packets.

2. The method according to claim 1, wherein, The IP header of the second data packet is generated, including at least one of the following: Based on the IP address information in the configuration information related to the first bearer or data stream, at least one of the source IP address and the destination IP address in the IP header is generated; The SN in the IP header is generated based on the sequence number SN in the Packet Data Convergence Protocol (PDCP) header carrying the first data packet; Calculate the checksum in the IP header based on the second data packet; Configure the QoS-related fields in the IP header based on the QoS information of the first bearer or data stream; The segmentation-related information in the IP header is generated using preset values; The IP header is generated using preset values ​​to include all information other than those mentioned above.

3. The method according to claim 2, wherein, The step of calculating the checksum in the IP header based on the second data packet includes: If the CRC check of the first data packet is successful, the checksum in the IP header is calculated based on the second data packet.

4. The method according to any one of claims 1-3, wherein, The method further includes: When the third data packet is sent, the terminal stops performing IP layer segmentation operations.

5. The method according to any one of claims 1-4, wherein, The UDP header of the second data packet is generated, including at least one of the following: Based on the port information in the configuration information related to the first bearer or data stream, at least one of the source port information and the destination port information in the UDP header is generated; Based on the second data packet, calculate the checksum in the UDP header; The UDP header is generated using preset values ​​to include all information other than those mentioned above.

6. The method according to any one of claims 1-5, wherein, The RTP header of the second data packet is generated, including at least one of the following: The timestamp in the RTP header is generated based on the interval duration; Set the timestamp in the RTP header of the first second data packet to the preset time; The SN in the RTP header is generated based on the SN in the PDCP header carrying the first data packet; Based on the generated synchronization source identifier SSRC, set the SSRC in the RTP header; The value of the Contribution Source Identifier (CSRC) in the RTP header is set using a preset value; The RTP header is generated using preset values, and includes all other information besides the items mentioned above.

7. The method according to claim 6, wherein, The method further includes at least one of the following: The terminal receives signaling from a network-side node, including the interval duration information, and the signaling is related to the first bearer or data stream. The terminal learns the interval duration from the IP Multimedia Subsystem (IMS) signaling, which is related to the establishment or update of the first bearer or data stream.

8. The method according to any one of claims 1-7, wherein, The method further includes at least one of the following: The terminal receives first indication information from a network-side node, the first indication information being used to indicate at least one of the following: not transmitting IP headers; not transmitting UDP headers; not transmitting RTP headers; Enable the ability to perform the first operation.

9. The method according to any one of claims 1-8, wherein, The terminal also performs: Send the second data packet to the application layer or operating system layer; or... The third data packet that sends the first bearer or data stream includes: Receive a fourth data packet sent by the application layer or operating system layer, and send the third data packet, wherein the fourth data packet includes the third data packet and any one of the following: IP header; IP and UDP header; IP, UDP and RTP header.

10. A data transmission method, applied to a first network node, comprising: The first network node performs at least one of the third and fourth operations; The third operation includes at least one of the following: Receive the third data packet from the first bearer or data stream, and forward the fifth data packet; Receive the sixth data packet and forward the first data packet through the first bearer or data stream; The fourth operation includes at least one of the following: Receive second instruction information from the second network node, and perform the third operation based on the second instruction information; Receive first capability information from the terminal, and perform the third operation based on the first capability information; The first bearer or data stream is used to transmit IP protocol data packets; The third data packet does not include any of the following: IP header; IP and UDP header; IP, UDP and RTP header; The fifth data packet includes the third data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header. The first data packet does not include any of the following: IP header; IP and UDP header; IP, UDP, and RTP header; The sixth data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

11. The method according to claim 10, wherein, The method further includes: the first network node generating an IP header for the fifth data packet, wherein generating the IP header for the fifth data packet includes at least one of the following: Based on the IP address information in the configuration information related to the first bearer or data stream, at least one of the source IP address and the destination IP address in the IP header is generated; The SN in the IP header is generated based on the sequence number SN in the GPRS Tunneling Protocol GTP-U header for the user plane that carries the third data packet; Based on the fifth data packet, calculate the checksum in the IP header; Configure the QoS-related fields in the IP header based on the QoS information of the first bearer or data stream; The segmentation-related information in the IP header is generated using preset values; The IP header is generated using preset values ​​to include all information other than those mentioned above.

12. The method according to claim 11, wherein, The step of calculating the checksum in the IP header based on the fifth data packet includes: If the CRC check of the third data packet is successful, the checksum in the IP header is calculated based on the fifth data packet.

13. The method according to any one of claims 10-12, wherein, The method further includes: When forwarding the first data packet, the first network node stops performing IP layer segmentation operations.

14. The method according to any one of claims 10-13, wherein, The method further includes: the first network node generating a UDP header for the fifth data packet, wherein generating the UDP header for the fifth data packet includes at least one of the following: Based on the port information in the configuration information related to the first bearer or data stream, the source port information and destination port information in the UDP header are generated. Based on the fifth data packet, calculate the checksum in the UDP header; The UDP header is generated using preset values ​​to include all information other than those mentioned above.

15. The method according to any one of claims 10-14, wherein, The method further includes: the first network node generating an RTP header for the fifth data packet, wherein generating the RTP header for the fifth data packet includes at least one of the following: The timestamp in the RTP header is generated based on the interval duration; Set the timestamp in the RTP header of the first fifth data packet to the preset time; The SN in the RTP header is generated based on the SN in the GTP-U header carrying the third data packet; Based on the generated synchronization source identifier SSRC, set the SSRC in the RTP header; The value of the Contribution Source Identifier (CSRC) in the RTP header is set using a preset value; The RTP header is generated using preset values, and includes all other information besides the items mentioned above.

16. The method according to claim 15, wherein, The method further includes at least one of the following: The first network node receives signaling including the interval duration information from the third or fourth network node, and the signaling is related to the first bearer or data stream; The first network node learns the interval duration from IMS signaling, which is related to the establishment or update of the first bearer or data stream.

17. The method according to any one of claims 10-16, wherein, The method further includes at least one of the following: The first network node sends the interval duration to the access network node through the second network node; The first network node sends a first indication message to the terminal, or sends the first indication message to the terminal through the second network node, wherein the first indication message is used to indicate at least one of the following: not to transmit the IP header; not to transmit the UDP header; not to transmit the RTP header; The first network node sends a third indication message to the access network node, or sends a third indication message to the access network node through the second network node. The third indication message is used to indicate that functions related to the IP layer protocol are not enabled.

18. The method according to any one of claims 10-17, wherein, The method further includes: The first network node selects a third network node and sends the information of the third network node to the terminal.

19. A data transmission method, applied to a second network node, comprising: The second network node performs the fifth and sixth operations; The fifth operation includes at least one of the following: Send a first indication message to the terminal, the first indication message being used to indicate at least one of the following: not to transmit the IP header; not to transmit the UDP header; not to transmit the RTP header; Send a second indication message to the first network node, the second indication message being used to indicate at least one of the following: not to transmit IP headers; request not to transmit IP headers; not to transmit UDP headers; request not to transmit UDP headers; not to transmit RTP headers; request not to transmit RTP headers. Send a third indication message to the access network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled; Send an interval duration to the access network node, the interval duration being used to indicate the interval between transmitted data packets; The sixth operation includes: receiving first capability information from the terminal and performing the fifth operation based on the first capability information.

20. The method according to claim 19, wherein, The method further includes: Upon receiving the first capability information from the terminal, the second network node selects the first network node based on at least one of the first capability information and the terminal's wireless access technology.

21. The method according to claim 19 or 20, wherein, The method further includes: The second network node receives at least one of the following from the first network node: the first indication information; the third indication information; and the interval duration.

22. The method according to any one of claims 19-21, wherein, The method further includes: The second network node receives the interval duration from the third network node.

23. A data transmission method, applied to a third network node, comprising: The third network node selects the first network node of the service terminal as the media gateway in the IMS system.

24. The method according to claim 23, wherein, The third network node selects the first network node of the serving terminal as the media gateway in the IMS system, including: The third network node selects the media gateway based on the terminal's IP address.

25. A data transmission method, applied to an access network node, comprising: The access network node performs a seventh operation, which includes at least one of the following: The interval time at which the access network node receives the data sent by the first network node; The interval duration at which the access network node receives data sent by the second network node; The access network node receives a third indication message sent by the first network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled; The access network node receives a third indication message sent by the second network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled; The access network node does not enable IP layer protocol-related functions based on at least one of the following: terminal access status, information related to the first bearer or data stream, and session information related to the first bearer or data stream; The access network node receives a third data packet from the first bearer or data stream of the terminal, and transmits the third data packet to the first network node via the GTP-U protocol. The third data packet does not contain any of the following: an IP header; or IP and UDP headers. IP, UDP, and RTP headers; Receive a first data packet from a first network node, and transmit the first data packet to the terminal via the PDCP protocol. The first data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

26. The method of claim 25, wherein, The method further includes: The access network node schedules the air interface resources of the first bearer or data stream based on the specified interval duration.

27. The method according to claim 25 or 26, wherein, The method further includes: The access network node does not enable IP layer protocol-related functions based on the third indication information.

28. A data transmission apparatus, comprising: A first processing module is configured to perform at least one of a first operation and a second operation; The first operation includes at least one of the following: Receive a first data packet from a first bearer or data stream, and generate a second data packet, wherein the second data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header; Send a third data packet of the first bearer or data stream, wherein the third data packet does not contain any of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header; The second operation includes: sending first capability information to a network-side node, wherein the first capability information is used to indicate that the terminal has the capability to perform the first operation; The first bearer or data stream is used to transmit IP protocol data packets.

29. The data transmission apparatus according to claim 28, wherein, It also includes a first receiving module for performing at least one of the following: Receive signaling including interval duration information from a network-side node, wherein the signaling is related to the first bearer or data stream; The interval duration is obtained from IMS signaling, which is related to the establishment or update of the first bearer or data stream.

30. The data transmission apparatus according to claim 28, wherein, It also includes a second receiving module, used for: Receive first indication information from the network-side node, the first indication information being used to indicate at least one of the following: not to transmit IP headers; not to transmit UDP headers; not to transmit RTP headers; The first processing module is further configured to: enable the ability to perform the first operation.

31. A data transmission apparatus, comprising: The second processing module is used for at least one of the third and fourth operations performed; The third operation includes at least one of the following: Receive the third data packet from the first bearer or data stream, and forward the fifth data packet; Receive the sixth data packet and forward the first data packet through the first bearer or data stream; The fourth operation includes at least one of the following: Receive second instruction information from the second network node, and perform the third operation based on the second instruction information; Receive first capability information from the terminal, and perform the third operation based on the first capability information; The first bearer or data stream is used to transmit IP protocol data packets; The third data packet does not include any of the following: IP header; IP and UDP header; IP, UDP and RTP header; The fifth data packet includes the third data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header. The first data packet does not include any of the following: IP header; IP and UDP header; IP, UDP, and RTP header; The sixth data packet includes the first data packet and any one of the following: an IP header; an IP and UDP header; or an IP, UDP, and RTP header.

32. The data transmission apparatus according to claim 31, wherein, It also includes a first sending module for performing at least one of the following: The interval duration is sent to the access network node through the second network node; Sending a first indication message to the terminal, or sending the first indication message to the terminal through a second network node, wherein the first indication message is used to indicate at least one of the following: not transmitting an IP header; not transmitting a UDP header; not transmitting an RTP header; Send a third indication message to the access network node, or send a third indication message to the access network node through a second network node, wherein the third indication message is used to indicate that IP layer protocol-related functions are not enabled.

33. A data transmission apparatus, comprising: The third processing module is used to perform the fifth and sixth operations; The fifth operation includes at least one of the following: Send a first indication message to the terminal, the first indication message being used to indicate at least one of the following: not to transmit the IP header; not to transmit the UDP header; not to transmit the RTP header; Send a second indication message to the first network node, the second indication message being used to indicate at least one of the following: not to transmit IP headers; request not to transmit IP headers; not to transmit UDP headers; request not to transmit UDP headers; not to transmit RTP headers; request not to transmit RTP headers. Send a third indication message to the access network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled; Send an interval duration to the access network node, the interval duration being used to indicate the interval between transmitted data packets; The sixth operation includes: receiving first capability information from the terminal and performing the fifth operation based on the first capability information.

34. The data transmission apparatus according to claim 33, wherein, The third processing module is also used for: Upon receiving the first capability information from the terminal, the first network node is selected based on at least one of the first capability information and the wireless access technology of the terminal.

35. A data transmission apparatus, comprising: The fourth processing module is used to select the first network node of the service terminal as the media gateway in the IMS system.

36. A data transmission apparatus, comprising: The fifth processing module is used to perform the seventh operation, which includes at least one of the following: The interval for receiving data from the first network node; The interval for receiving data from the second network node; Receive a third indication message sent by the first network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled; Receive a third indication message sent by the second network node, the third indication message being used to indicate that IP layer protocol-related functions are not enabled; IP layer protocol-related functions are not enabled based on at least one of the following: terminal access status, information related to the first bearer or data stream, and session information related to the first bearer or data stream; Receive a third data packet from the first bearer or data stream of the terminal, and transmit the third data packet to the first network node via the GTP-U protocol. The third data packet does not contain any of the following: an IP header; or an IP and UDP header. IP, UDP, and RTP headers; Receive a first data packet from a first network node, and transmit the first data packet to the terminal via the PDCP protocol. The first data packet does not contain any of the following: IP header; IP and UDP header; IP, UDP and RTP header.

37. A terminal comprising 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 data transmission method as claimed in any one of claims 1 to 9.

38. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the data transmission method as claimed in any one of claims 10 to 18, or implement the steps of the data transmission method as claimed in any one of claims 19 to 22, or implement the steps of the data transmission method as claimed in claim 23 or 24, or implement the steps of the data transmission method as claimed in any one of claims 25 to 27.

39. A readable storage medium storing a program or instructions that, when executed by a processor, implement the data transmission method as described in any one of claims 1 to 9, or the data transmission method as described in any one of claims 10 to 18, or the data transmission method as described in any one of claims 19 to 22, or the data transmission method as described in claim 23 or 24, or the data transmission method as described in any one of claims 25 to 27.

Images