Communication method and apparatus

By removing the Baotou verification field of IP packets in Internet protocol voice services such as VoLTE/VoNR, the problem of large overhead transmission overhead is solved and network transmission performance is improved.

WO2025152681A1PCT designated stage expired Publication Date: 2025-07-24HUAWEI TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/139599
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-01-17
Filing Date
2024-12-16
Publication Date
2025-07-24

AI Technical Summary

Technical Problem

In Internet protocol voice services such as VoLTE/VoNR, despite the implementation of robust Baotou compression (ROHC), the transmission overhead of Baotou is still large, especially in communication systems with smaller bandwidth, which affects network transmission performance.

Method used

By removing the verification field in the header of the IP packet, the amount of information in the header is reduced, thereby reducing transmission overhead and improving network performance.

Benefits of technology

It effectively reduces the transmission overhead of the packet header and improves the transmission performance of the network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024139599_24072025_PF_FP_ABST
    Figure CN2024139599_24072025_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to a communication method and an apparatus. A first apparatus performs packet header compression on a first data packet to obtain a second data packet; the first apparatus removes a check field in a packet header of the second data packet to obtain a third data packet; and the first apparatus transmits the third data packet. The embodiments of the present application enable the information amount of the packet header of the second data packet to be reduced, so as to reduce the packet header transmission overheads, thus helping to improve the network transmission performance.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on January 17, 2024, with application number 202410075364.X and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] In Internet Protocol (IP) voice services such as voice over long-term evolution (VoLTE) and voice over new radio (VoNR), the payload in an IP packet is almost the same size as, or even smaller than, the packet header. In this case, the header occupies more resources than the payload, resulting in significant air interface transmission overhead.

[0005] To reduce air interface transmission overhead, user equipment (UE) and base stations can use robust header compression (ROHC) technology to compress the IP packet headers of voice services on the user plane during uplink and downlink data transmission. ROHC compression can, in optimal conditions, compress a 40-byte IP / User Datagram Protocol (UDP) / Real-time Transport Protocol (RTP) header to just 3 bytes. This helps reduce air interface header transmission overhead and improve network transmission performance.

[0006] However, even if ROHC compression is performed, the optimal compression situation still requires the transmission of a 3-byte packet header. For communication systems with a small transmission bandwidth, the transmission overhead of the packet header is still very large. Summary of the Invention

[0007] Embodiments of the present application provide a communication method and apparatus for reducing the transmission overhead of a packet header.

[0008] In a first aspect, a first communication method is provided, which can be executed by a first device, which is, for example, a terminal device or an access network device. The terminal device is, for example, a terminal device, or other device including the functions of a terminal device, or a chip system (or, chip) or other functional module, which can realize the functions of the terminal device, and the chip system or functional module is, for example, set in the terminal device. The access network device is, for example, an access network device, or other device including the functions of an access network device, or a chip system (or, chip) or other functional module, which can realize the functions of the access network device, and the chip system or functional module is, for example, set in the access network device. Optionally, the access network device is, for example, a base station, or other device in the access network. The method includes: compressing the header of the first data packet to obtain a second data packet; removing the check field included in the header of the second data packet to obtain a third data packet; and sending the third data packet.

[0009] In an embodiment of the present application, the first device can remove the check field in the header of the second data packet, so that the second data packet (i.e., the third data packet) is sent after the check field is removed. The amount of information in the header of the second data packet is reduced, thereby reducing the transmission overhead of the header, which is beneficial to improving the transmission performance of the network.

[0010] In an optional implementation, the checksum field is a UDP checksum field. The checksum field may also be other fields used for checking in the header of the second data packet, which is not limited thereto.

[0011] In an optional embodiment, before performing header compression on the first data packet, the method includes: modifying the value of the checksum field in the UDP header of the first data packet to a first value. The first device performs compression, and the second device that receives the third data packet performs decompression. When the second device decompresses the received third data packet, it may first fill the checksum field in the header of the third data packet. However, the second device may not know the actual value of the checksum field at this time. Therefore, the first device and the second device may both set the value of the checksum field to the first value, so that the compression process corresponds to the decompression process.

[0012] In an optional embodiment, the method further includes: sending or receiving capability information, wherein the capability information is used to indicate support for removing the check field during transmission. For example, if the first device is a terminal device, the first device can send the capability information of the terminal device; or, if the first device is an access network device, the first device can receive the capability information (for example, the capability information comes from the second device, and the capability information is the capability information of the second device). The capability information can indicate whether the sender of the capability information supports removing the check field during transmission. If the sender supports removing the check field during transmission, the solution provided in the embodiment of the present application can be executed.

[0013] In an optional embodiment, the method further includes: sending or receiving a first message, wherein the first message is used to indicate activation of a function of removing the check field during transmission. Removing the check field during transmission can be used as a function that can be activated or deactivated to flexibly apply the function. For example, if the first device is a terminal device, the first device can receive a first message, for example, the first message comes from an access network device. If the first device receives the first message, the function can be used, otherwise the function is deemed to be inactivated; or, if the first device is an access network device, the first device can send a first message, for example, the first message can be sent to a terminal device, and the access network device and the terminal device can use this function to transmit data packets.

[0014] In an optional embodiment, the method further includes: receiving a bearer establishment message from a core network device, the bearer establishment message being used to establish a media-dedicated bearer; and sending a first message, including: sending the first message based on the bearer establishment message. Establishing the media-dedicated bearer indicates that a service corresponding to the media-dedicated bearer may be about to begin transmission, so the first device (e.g., an access network device) may send the first message to utilize a function of removing a check field during transmission of the service to improve network performance.

[0015] In an optional embodiment, the method further includes: determining that the access network device adopts NB-IoT communication; or determining that the media dedicated bearer is a bearer through NB-IoT communication. For example, after the first device (such as an access network device) receives the bearer establishment message, if the access network device adopts NB-IoT communication, and / or the G2 media dedicated bearer is a bearer through NB-IoT communication, the first message can be sent. Because the supported bandwidth is small for NB-IoT, it is particularly important to reduce the transmission overhead. Therefore, for NB-IoT, the function of removing the check field during transmission provided in the embodiment of the present application can be adopted to reduce the transmission overhead, improve network performance, and reduce the probability of network congestion.

[0016] In an optional embodiment, the method further includes: receiving a second message from a UE or a core network device, the second message being used to indicate the start of transmission of a media service; and sending a first message, including: sending the first message based on the second message. If the network does not establish a media-dedicated bearer for a media service (e.g., a service corresponding to a first data packet), but instead transmits the media service through a default bearer, the first device (e.g., an access network device) may not receive the bearer establishment message. In this case, if the first device receives the second message, indicating that the service corresponding to the media-dedicated bearer may be about to start transmission, the first device may send the first message.

[0017] In an optional embodiment, the method further includes: determining that the access network device adopts NB-IoT communication; and / or determining that the media service is a service transmitted via NB-IoT.

[0018] In an optional implementation, the packet header compression is ROHC compression, or the packet header compression may be other compression methods, which are not limited.

[0019] In a second aspect, a second communication method is provided. The method can be performed by a second device, such as a terminal device or an access network device. For example, the first device is a terminal device and the second device is an access network device; or, alternatively, the first device is an access network device and the second device is a terminal device. For information regarding terminal devices or access network devices, refer to the first aspect. The method includes: receiving a third data packet; decompressing a header of the third data packet; determining a second value for a checksum field in the decompressed third data packet; and setting the value of the checksum field in the decompressed third data packet to the second value to obtain a fourth data packet.

[0020] In an optional implementation, before decompressing the header of the third data packet, the method further includes: adding the check field in the third data packet, where the value of the check field is a first value.

[0021] In an optional implementation, the check field is a UDP checksum field.

[0022] In an optional embodiment, determining the value of the check field as the second value based on the third data packet after decompression of the packet header includes: determining the value of the check field as the second value based on the IP header, UDP header and UDP data of the decompressed third data packet.

[0023] In an optional implementation, the method further includes: sending or receiving capability information, where the capability information is used to indicate that the check field is allowed to be removed during transmission.

[0024] In an optional implementation, the method further includes: sending or receiving a first message, where the first message is used to indicate activation of a function of removing the UDP checksum field during transmission.

[0025] In an optional implementation, the method further includes: receiving a bearer establishment message from a core network device, the bearer establishment message being used to establish a media-dedicated bearer; and sending a first message, including: sending the first message based on the bearer establishment message.

[0026] In an optional embodiment, the method further includes: determining that the access network device communicates in an NB-IoT manner; and / or determining that the media dedicated bearer is a bearer for communication in an NB-IoT manner.

[0027] In an optional implementation, the method further includes: receiving a second message from the UE or the core network device, the second message being used to indicate the start of transmitting the media service; and sending the first message, including: sending the first message based on the second message.

[0028] In an optional embodiment, the method further includes: determining that the access network device communicates using an NB-IoT manner; and / or determining that the media service is a service transmitted via an NB-IoT manner.

[0029] Regarding the technical effects brought about by the second aspect or various optional implementations, reference may be made to the introduction of the technical effects of the first aspect or corresponding implementations.

[0030] In a third aspect, a third communication method is provided. The method can be performed by a first device, such as a terminal device or an access network device. For an introduction to the terminal device or access network device, refer to the first aspect. The method includes sending N data packets, wherein some of the N data packets include headers, and the remaining data packets do not include headers, where N is an integer greater than or equal to 2.

[0031] The embodiment of the present application can remove the headers of some data packets among N data packets, so that what are sent are N data packets after the headers are removed, which can greatly reduce the transmission overhead and is conducive to improving the transmission performance of the network.

[0032] In an optional embodiment, the partial data packet is the first data packet, the last data packet, or any data packet among the N data packets, or is the portion of data packets transmitted first among the N data packets. For example, if both the first device and the second device can clearly identify which data packet(s) among the N data packets the partial data packet(s) are, the second device can recover the removed headers of the N data packets based on the retained headers in the N data packets, and thus there is no restriction on which data packet(s) among the N data packets the partial data packet(s) are.

[0033] In an optional embodiment, the N data packets are all the data packets corresponding to the first service, or are part of the data packets corresponding to the first service. For example, if the N data packets are all the data packets corresponding to the first service, then for all the data packets corresponding to the first service, it is only necessary to retain the packet header in part of the data packets, which can reduce the transmission overhead to a large extent. Or the N data packets are part of the data packets corresponding to the first service. For example, the processing of the embodiment of the present application can be performed on part of the data packets of the first service, while the other data packets of the first service can be transmitted in a manner without removing the packet header, thereby reducing the transmission overhead to a certain extent and ensuring the transmission reliability of the first service. Or it can be considered that the data packets of the first service are divided (actively or passively) into multiple parts, and each part can be executed separately according to the scheme of the embodiment of the present application, then the transmission reliability is high for each part, and the probability of mutual influence between the parts is reduced.

[0034] In an optional embodiment, the N data packets are partial data packets corresponding to the first service, wherein the N data packets are data packets sent through resources scheduled once. For example, during the transmission process of the first service, the transmission may be completed by scheduling resources multiple times, and the N data packets may be data packets sent through resources scheduled once. The technical solution of the embodiment of the present application can be implemented for the data packets sent by resources scheduled once, which can not only reduce the transmission overhead, but also reduce the impact of these N data packets on other data packets of the first service. Optionally, before sending uplink data, the UE needs to apply to the access network device for resources for sending uplink data. Therefore, the resources scheduled once can be understood as the air interface wireless resources allocated to the UE by the access network device when the UE requests resources for one transmission from the access network device. The air interface wireless resources can be used for the UE to transmit uplink data. Among them, the basic unit or minimum unit of wireless resource scheduling can be a physical resource block (PRB).

[0035] In an optional embodiment, the method further includes: sending or receiving capability information, wherein the capability information is used to indicate support for removing the header of the data packet during transmission. Removing the header during transmission can be used as a function, and the function can be activated or deactivated to flexibly apply the function. For example, if the first device is a terminal device, the first device can receive a first message, for example, the first message comes from an access network device. If the first device receives the first message, the function can be used, otherwise the function is deemed to be inactivated; or, if the first device is an access network device, the first device can send a first message, for example, the first message can be sent to a terminal device, and the access network device and the terminal device can use this function to transmit data packets.

[0036] In an optional implementation, the method further includes: sending or receiving a first message, where the first message is used to indicate activation of a function of removing a header of a data packet during transmission.

[0037] In an optional implementation, the method further includes: receiving a bearer establishment message from a core network device, the bearer establishment message being used to establish a media-dedicated bearer; and sending a first message, including: sending the first message based on the bearer establishment message.

[0038] In an optional embodiment, the method further includes: determining that the access network device communicates in an NB-IoT manner; and / or determining that the media dedicated bearer is a bearer for communication in an NB-IoT manner.

[0039] In an optional implementation, the method further includes: receiving a second message from the UE or the core network device, the second message being used to indicate the start of transmitting the media service; and sending the first message, including: sending the first message based on the second message.

[0040] In an optional embodiment, the method further includes: determining that the access network device communicates using an NB-IoT manner; and / or determining that the media service is a service transmitted via an NB-IoT manner.

[0041] Regarding the technical effects brought about by some optional implementations of the third aspect, reference may be made to the introduction of the technical effects of the first aspect or corresponding implementations.

[0042] In a fourth aspect, a fourth communication method is provided, which can be performed by a second device, such as a terminal device or an access network device. For example, the first device is a terminal device and the second device is an access network device; or, the first device is an access network device and the second device is a terminal device. For an introduction to terminal devices and access network devices, reference can be made to the first aspect. The method includes: receiving N data packets, wherein some of the N data packets include headers, and the remaining data packets of the N data packets do not include the headers, where N is an integer greater than or equal to 2; and determining the headers of the remaining data packets based on the headers of the some data packets.

[0043] In an optional implementation, the partial data packet is the first data packet among the N data packets, or is the partial data packet transmitted first among the N data packets.

[0044] In an optional implementation, the N data packets are all data packets corresponding to the first service, or are part of the data packets corresponding to the first service.

[0045] In an optional implementation, the method further includes: sending or receiving capability information, where the capability information is used to indicate support for removing a header of a data packet during transmission.

[0046] In an optional implementation, the method further includes: sending or receiving a first message, where the first message is used to indicate activation of a function of removing a header of a data packet during transmission.

[0047] In an optional implementation, the method further includes: receiving a bearer establishment message from a core network device, the bearer establishment message being used to establish a media-dedicated bearer; and sending a first message, including: sending the first message based on the bearer establishment message.

[0048] In an optional embodiment, the method further includes: determining that the access network device communicates in an NB-IoT manner; and / or determining that the media dedicated bearer is a bearer for communication in an NB-IoT manner.

[0049] In an optional embodiment, before sending the first message, the method further includes: receiving a second message from the UE or the core network device, the second message being used to indicate the start of transmitting the media service; and sending the first message, including: sending the first message based on the second message.

[0050] In an optional embodiment, the method further includes: determining that the access network device communicates using an NB-IoT manner; and / or determining that the media service is a service transmitted via an NB-IoT manner.

[0051] In an optional implementation, the packet header is a ROHC header.

[0052] Regarding the technical effects brought about by the fourth aspect or various optional implementations, reference may be made to the introduction to the technical effects of the third aspect or corresponding implementations.

[0053] In a fifth aspect, a fifth communication method is provided. The method can be performed by a first device, such as a terminal device or an access network device. For an introduction to the terminal device or access network device, refer to the first aspect. The method includes: obtaining N data packets; obtaining a first data packet based on the N data packets, wherein the first data packet includes the payload of the N data packets and a first packet header, the first packet header being determined based on the packet headers of some or all of the N data packets, where N is an integer greater than or equal to 2; and sending the first data packet.

[0054] The embodiment of the present application can merge the payloads of N data packets, so that the first data packet obtained can only include the first packet header and no longer include other packet headers, which can greatly reduce the transmission overhead and help improve the transmission performance of the network.

[0055] In an optional embodiment, the first packet header is determined based on the packet header of a second packet among the N packets, where the second packet is the first or last packet transmitted among the N packets. Alternatively, the second packet may be any one or more of the N packets. For example, both the first device and the second device can clearly identify which packet or packets the second packet is, so that the second device can recover the packet headers of the N packets based on the first packet header. Therefore, the embodiment of the present application does not limit which packet or packets among the N packets the second packet is.

[0056] In an optional implementation, the N data packets are all data packets corresponding to the first service, or are part of the data packets corresponding to the first service.

[0057] In an optional implementation, the N data packets are partial data packets corresponding to the first service, wherein the N data packets are data packets sent through resources scheduled once.

[0058] In an optional embodiment, the sum of the lengths of the payloads of the N data packets is less than or equal to an upper limit on the length of a data packet. The upper limit may be, for example, an upper limit on the length of a data packet specified by a protocol or required by a system. Therefore, the sum of the lengths of the payloads of the N data packets may be within the upper limit to ensure that the first data packet can be sent.

[0059] In an optional implementation, the method further includes: sending or receiving capability information, where the capability information is used to indicate support for merging payloads of data packets during transmission.

[0060] In an optional implementation, the method further includes: sending or receiving a first message, where the first message is used to indicate activation of a function of merging payloads of data packets during transmission.

[0061] In an optional implementation, the method further includes: receiving a bearer establishment message from a core network device, the bearer establishment message being used to establish a media-dedicated bearer; and sending a first message, including: sending the first message based on the bearer establishment message.

[0062] In an optional embodiment, the method further includes: determining that the access network device communicates in an NB-IoT manner; and / or determining that the media dedicated bearer is a bearer for communication in an NB-IoT manner.

[0063] In an optional implementation, the method further includes: receiving a second message from the UE or the core network device, the second message being used to indicate the start of transmitting the media service; and sending the first message, including: sending the first message based on the second message.

[0064] In an optional embodiment, the method further includes: determining that the access network device communicates using an NB-IoT manner; and / or determining that the media service is a service transmitted via an NB-IoT manner.

[0065] In an optional implementation, the first packet header is a ROHC header.

[0066] Regarding the technical effects brought about by some optional implementations of the fifth aspect, reference may be made to the introduction of the technical effects of the first aspect or the corresponding implementations, and / or reference may be made to the introduction of the technical effects of the third aspect or the corresponding implementations.

[0067] In a sixth aspect, a sixth communication method is provided, which can be executed by a second device, which is, for example, a terminal device or an access network device. For example, the first device is a terminal device, and the second device is an access network device; or, the first device is an access network device, and the second device is a terminal device. For an introduction to terminal devices and access network devices, reference can be made to the first aspect. The method includes: receiving a first data packet, wherein the first data packet includes a payload of N data packets, and includes a first packet header in the N data packets, the first packet header being determined based on the packet headers of some or all of the N data packets, and N being an integer greater than or equal to 2; determining the packet headers of the N data packets based on the first packet header; and restoring the first data packet to the N data packets.

[0068] In an optional implementation, the first packet header is determined based on a packet header of a second data packet among the N data packets, and the second data packet is the first or last data packet transmitted among the N data packets.

[0069] In an optional implementation, the N data packets are all data packets corresponding to the first service, or are part of the data packets corresponding to the first service.

[0070] In an optional implementation, the sum of the lengths of the payloads of the N data packets is less than or equal to an upper limit on the length of the data packets.

[0071] In an optional implementation, the method further includes: sending or receiving capability information, where the capability information is used to indicate support for merging payloads of data packets during transmission.

[0072] In an optional implementation, the method further includes: sending or receiving a first message, where the first message is used to indicate activation of a function of merging payloads of data packets during transmission.

[0073] In an optional implementation, the method further includes: receiving a bearer establishment message from a core network device, the bearer establishment message being used to establish a media-dedicated bearer; and sending a first message, including: sending the first message based on the bearer establishment message.

[0074] In an optional embodiment, the method further includes: determining that the access network device communicates in an NB-IoT manner; and / or determining that the media dedicated bearer is a bearer for communication in an NB-IoT manner.

[0075] In an optional implementation, the method further includes: receiving a second message from the UE or the core network device, the second message being used to indicate the start of transmitting the media service; and sending the first message, including: sending the first message based on the second message.

[0076] In an optional embodiment, the method further includes: determining that the access network device communicates using an NB-IoT manner; and / or determining that the media service is a service transmitted via an NB-IoT manner.

[0077] In an optional implementation, the first packet header is a ROHC header.

[0078] Regarding the technical effects brought about by some optional implementations of the sixth aspect, please refer to the introduction of the technical effects of the fifth aspect or corresponding implementations.

[0079] In the seventh aspect, a communication device is provided. The communication device may be the first device described in any one of the first to sixth aspects above. The communication device has the functions of the above-mentioned first device. If the first device is, for example, a terminal device, then the communication device is, for example, a terminal device, or other device including the functions of a terminal device, or a chip system (or, chip) or other functional module, and the chip system or functional module can realize the functions of the terminal device, and the chip system or functional module is, for example, set in the terminal device. Alternatively, if the first device is, for example, an access network device, then the communication device is, for example, an access network device, or other device including the functions of an access network device, or a chip system (or, chip) or other functional module, and the chip system or functional module can realize the functions of the access network device, and the chip system or functional module is, for example, set in the access network device. In an optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). A transceiver unit can perform both sending and receiving functions. When performing the sending function, it can be called a sending unit (sometimes also called a sending module). When performing the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit can be the same functional module, which is called a transceiver unit and can perform both sending and receiving functions. Alternatively, the sending unit and the receiving unit can be different functional modules, with the transceiver unit being the general term for these functional modules.

[0080] In an optional embodiment, the processing unit is used to compress the header of the first data packet to obtain a second data packet; the processing unit is also used to remove the check field included in the header of the second data packet to obtain a third data packet; the transceiver unit (or, the sending unit) is used to send the third data packet.

[0081] In an optional embodiment, the transceiver unit (or, the sending unit) is used to send N data packets, wherein some of the N data packets include packet headers, and the remaining data packets of the N data packets do not include packet headers, and N is an integer greater than or equal to 2.

[0082] In an optional embodiment, the processing unit is used to obtain N data packets; the processing unit is further used to obtain a first data packet based on the N data packets, wherein the first data packet includes the payload of the N data packets and a first packet header, and the first packet header is determined based on the packet headers of some or all of the N data packets, and N is an integer greater than or equal to 2; the transceiver unit (or, the sending unit) is used to send the first data packet.

[0083] In an optional embodiment, the communication device also includes a storage unit (sometimes also referred to as a storage module), and the processing unit is used to couple with the storage unit and execute the program or instructions in the storage unit, enabling the communication device to perform the function of the first device described in any one of the first to sixth aspects above.

[0084] In an eighth aspect, a communication device is provided. The communication device may be the second device described in any one of the first to sixth aspects. The communication device has the functions of the second device. If the second device is, for example, a terminal device, then the communication device is, for example, a terminal device, or other device including the functions of a terminal device, or a chip system (or, chip) or other functional module. The chip system or functional module can implement the functions of the terminal device, and the chip system or functional module is, for example, provided in the terminal device. Alternatively, if the second device is, for example, an access network device, then the communication device is, for example, an access network device, or other device including the functions of an access network device, or a chip system (or, chip) or other functional module. The chip system or functional module can implement the functions of the access network device, and the chip system or functional module is, for example, provided in the access network device. In an optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). For the implementation of the transceiver unit, reference may be made to the introduction of the seventh aspect.

[0085] In an optional embodiment, the transceiver unit (or, the receiving unit) is used to receive a third data packet; the processing unit is used to decompress the header of the third data packet; the processing unit is also used to determine the value of the check field based on the third data packet after the header is decompressed to a second value; the processing unit is also used to set the value of the check field in the third data packet after the header is decompressed to the second value to obtain a fourth data packet.

[0086] In an optional embodiment, the transceiver unit (or, the receiving unit) is used to receive N data packets, wherein some of the N data packets include packet headers, and the remaining data packets of the N data packets do not include the packet headers, and N is an integer greater than or equal to 2; the processing unit is used to determine the packet headers of the remaining data packets based on the packet headers of the some data packets.

[0087] In an optional embodiment, the transceiver unit (or, the receiving unit) is used to receive a first data packet, wherein the first data packet includes the payload of N data packets and the first packet header of the N data packets, and the first packet header is determined based on the packet headers of some or all of the N data packets, and N is an integer greater than or equal to 2; the processing unit is used to determine the packet headers of the N data packets based on the first packet header; the processing unit is also used to restore the first data packet to the N data packets.

[0088] In an optional embodiment, the communication device also includes a storage unit (sometimes also referred to as a storage module), and the processing unit is used to couple with the storage unit and execute the program or instructions in the storage unit, enabling the communication device to perform the function of the second device described in any one of the first to sixth aspects above.

[0089] In a ninth aspect, a communication device is provided. The communication device may be a terminal device, or a chip or chip system used in a terminal device. The communication device includes a communication interface and a processor, and optionally, a memory. The memory is used to store a computer program. The processor is coupled to the memory and the communication interface. When the processor reads the computer program or instructions, the communication device executes the method performed by the first device in each of the above aspects.

[0090] In a tenth aspect, a communication device is provided. The communication device may be an access network device, or a chip or chip system used in an access network device. The communication device includes a communication interface and a processor, and optionally, a memory. The memory is configured to store a computer program. The processor is coupled to the memory and the communication interface. When the processor reads the computer program or instructions, the communication device executes the method performed by the second device in each of the above aspects.

[0091] In an eleventh aspect, a communication system is provided, comprising a first apparatus and a second apparatus, wherein the first apparatus is configured to execute the method described in any one of the first to sixth aspects, and the second apparatus is configured to execute the method described in any one of the first to sixth aspects. For example, the first apparatus may be implemented by the communication apparatus described in the seventh or ninth aspect, and the second apparatus may be implemented by the communication apparatus described in the eighth or tenth aspect.

[0092] In the twelfth aspect, a computer-readable storage medium is provided, which is used to store computer programs or instructions. When the computer program or instructions are executed, the methods performed by the first device and / or the second device and / or the application server in the above aspects are implemented.

[0093] In a thirteenth aspect, a computer program product comprising instructions is provided, which enables the methods described in the above aspects to be implemented when the computer program or instructions are executed on a computer.

[0094] In a fourteenth aspect, a chip system is provided, comprising a processor and an interface, wherein the processor is used to call and execute instructions from the interface so that the chip system implements the methods in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0095] FIG1A is a schematic diagram of a packet header before ROHC compression is performed;

[0096] FIG1B is a schematic diagram of a packet header after ROHC compression is performed;

[0097] 2A to 2C are schematic diagrams of several application scenarios of the embodiments of the present application;

[0098] FIG3 is a flow chart of a communication method provided in an embodiment of the present application;

[0099] FIG4A is a schematic diagram of a header of a first data packet in an embodiment of the present application;

[0100] FIG4B is a schematic diagram of a header of a second data packet in an embodiment of the present application;

[0101] FIG5 is a schematic diagram of a configuration of the first module in an embodiment of the present application;

[0102] FIG6 is an example of a processing process of the first device and the second device in an embodiment of the present application;

[0103] FIG7 is a flow chart of another communication method provided in an embodiment of the present application;

[0104] FIG8 is an example of another processing process of the first device and the second device;

[0105] FIG9 is a flow chart of another communication method provided in an embodiment of the present application;

[0106] 10A and 10B are schematic diagrams of two configurations of the third module in an embodiment of the present application;

[0107] FIG11 is an example of another processing process of the first device and the second device;

[0108] FIG12 is a schematic diagram of a device provided in an embodiment of the present application;

[0109] FIG13 is a schematic diagram of another device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0110] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0111] In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. For example, A / B means: A or B. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

[0112] In the embodiments of this application, ordinal numbers such as "first" and "second" are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects. In addition, the numbering of steps in the various embodiments introduced in this application is only to distinguish different steps and is not used to define the order between steps. For example, S301 can occur before S302, or after S302, or at the same time as S302.

[0113] Below, some terms or concepts in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0114] In the embodiment of the present application, the terminal device is a device with wireless transceiver function, which can be a fixed device, a mobile device, a handheld device (such as a mobile phone), a wearable device, a vehicle-mounted device, or a wireless device built into the above device (such as a communication module, a modem, or a chip system, etc.). The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: perception scenarios, cellular communications, device-to-device communication (D2D), vehicle to everything (V2X), machine-to-machine / machine-type communications (M2M / MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, indoor commercial scenarios (such as mobile phone screen projection, file sharing, mobile phone to VR glasses video transmission) and other scenarios. When the terminal device is applied to V2X, it can also be called a V2X device, for example, a smart car (or intelligent car), a digital car, an unmanned car (or driverless car or pilotless car or automobile), a self-driving car (or autonomous car), a pure electric vehicle (or battery EV), a hybrid electric vehicle (HEV), a range-extended EV (REEV), a plug-in hybrid electric vehicle (PHEV), a new energy vehicle (new energy vehicle), or a roadside unit (RSU). The terminal device can also be a device used in D2D communication, such as an electricity meter or water meter.

[0115] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0116] The various terminal devices described above, if located on a vehicle (e.g., placed in or installed in a vehicle), can be considered as vehicle-mounted terminal devices, which are also referred to as on-board units (OBUs). The terminal device of the present application can also be an on-board module, on-board module, on-board component, on-board chip, or on-board unit built into a vehicle as one or more components or units, and the vehicle can implement the method of the present application through the built-in on-board module, on-board module, on-board component, on-board chip, or on-board unit.

[0117] The terminal device may sometimes be referred to as user equipment (UE), terminal, access station, UE station, remote station, wireless communication device, or user equipment, etc.

[0118] In the embodiments of the present application, the communication device for implementing the terminal device function may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system, which may be installed in the terminal device. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the terminal device as an example in which the device for implementing the terminal device function is a terminal device. In addition, for ease of description, the terminal device in the embodiments of the present application is described by taking a UE as an example.

[0119] The network devices in the embodiments of the present application include, for example, access network devices, and / or core network devices. The access network device is a device with wireless transceiver functions, which is used to communicate with the terminal device. The access network devices include but are not limited to base stations (base transceiver station (BTS), node B (Node B), evolved node B (eNodeB) / eNB, or the next generation node B (gNodeB) / gNB), transmission reception points (TRP), base stations subsequently evolved by the third generation partnership project (3GPP), access nodes in wireless fidelity (Wi-Fi) systems, wireless relay nodes, wireless backhaul nodes, etc. The base station can be: a macro base station, a micro base station, a pico base station, a small station, a relay station, etc. Multiple base stations can support networks with the same access technology, or they can support networks with different access technologies. The base station can include one or more co-station or non-co-station transmission and receiving points. The access network device may also be a wireless controller, a centralized unit (CU), and / or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. The access network device may also be a server, etc. For example, the network device in the V2X technology may be a road side unit (RSU). The following describes the access network device using a base station as an example. The base station can communicate with the terminal device, or it can communicate with the terminal device through a relay station. The terminal device can communicate with multiple base stations in different access technologies. The core network device is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of the devices that implement core network functions in systems with different access technologies may be different, and the embodiments of the present application are not limited to this. Taking the fifth generation mobile communication technology (5G) system as an example, the core network equipment includes, for example, access and mobility management function (AMF), session management function (SMF), policy control function (PCF) or user plane function (UPF), etc.

[0120] In the CU-DU architecture, the access network equipment may include one or more logical network elements such as a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be configured separately or included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0121] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an open RAN (ORAN) system, CU may also be called an open CU (open CU, O-CU), DU may also be called an open DU (open DU, O-DU), CU-CP may also be called an open CU-CP (open CU-CP, O-CU-CP), CU-UP may also be called an open CU-UP (open CU-CP, O-CU-UP), and RU may also be called an open RU (open RU, O-RU). For convenience of description, the embodiments of the present application are described by taking CU, CU-CP, CU-UP, DU and RU as examples. Any of the CU (or CU-CP, CU-UP), DU and RU in the embodiments of the present application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0122] Optionally, in various embodiments of the present application, if the network device is a distributed architecture, for example, the network device includes a CU and a DU, or includes a CU-CP, a CU-UP and a DU, then the network device sends information to the UE, specifically, the DU included in the network device sends information to the UE; the network device receives information from the UE, specifically, the DU included in the network device receives information from the UE.

[0123] In the embodiments of the present application, the communication device for implementing the function of the network device may be a network device, or may be a device capable of supporting the network device to implement the function, such as a chip system, which may be installed in the network device. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the device for implementing the function of the network device as an example (for example, the device for implementing the function of the access network device is an access network device, and the device for implementing the function of the core network device is a core network device).

[0124] The technical features involved in the embodiments of this application are introduced below.

[0125] In IP voice services such as VoLTE / VoNR, the payload in an IP packet is almost the same size as, or even smaller than, the packet header. In this case, the header occupies more resources than the payload, resulting in significant air interface transmission overhead.

[0126] To save air interface transmission overhead, the UE and base station can use ROHC technology to perform packet header compression on the user plane for voice service IP packets during uplink and downlink data transmission. ROHC compression can, in optimal conditions, compress a 40-byte IP / UDP / RTP packet header to just 3 bytes. Refer to Figures 1A and 1B. Figure 1A shows a packet header before ROHC compression, and Figure 1B shows a packet header after ROHC compression. As shown in Figure 1A, before ROHC compression, the packet header includes the IP header, UDP header, and RTP header, which together occupy 40 bytes. The IP header includes a version field, denoted by VERS in FIG1A , as well as a header length (HLEN) field, a type of service (TOS) byte, a total length field, an IP identification field, a flags field, a fragment offset field, a time to live field, a protocol field, a header checksum field, a source IP address field, and a destination IP address field. The UDP header includes a source port number field, a destination port number field, a UDP length field, and a UDP checksum field. The RTP header includes a version number field (indicated by V=2 in Figure 1A), a padding identifier field (indicated by P in Figure 1A), an extension identifier field (indicated by X in Figure 1A), a contributing source (CSRC) counter field (indicated by CC in Figure 1A), a flag field (indicated by M in Figure 1A), a payload type field (indicated by PT in Figure 1A), an RTP sequence number field, a timestamp field, a synchronization source (SSRC) identifier field, and a contributing source (CSRC) identifier field.

[0127] As shown in Figure 1B, after ROHC compression is performed, the IP header, UDP header, and RTP header are compressed to form the ROHC header. The ROHC header includes the ROHC packet and the UDP checksum, occupying a total of three bytes. UO-0 in Figure 1B represents a type of ROHC packet. This shows that ROHC compression helps reduce air interface header transmission overhead and improve network transmission performance.

[0128] However, even if ROHC compression is performed, the optimal compression situation still requires the transmission of a 3-byte packet header. For communication systems with a small transmission bandwidth, the transmission overhead of the packet header is still very large.

[0129] In view of this, the embodiment of the present application can remove the check field in the header of the second data packet, so that the second data packet (i.e., the third data packet) after the check field is removed is sent. The amount of information in the header of the second data packet is reduced, thereby reducing the transmission overhead of the header, which is beneficial to improving the transmission performance of the network.

[0130] The technical solutions provided in the embodiments of the present application can be applied to 4G systems, such as long term evolution (LTE) systems, or can be applied to 5G systems, such as new radio (NR) systems, or can also be applied to next generation mobile communication systems or other similar communication systems, such as future communication systems, etc., without specific limitations. In addition, the technical solutions provided in the embodiments of the present application can also be applied to D2D scenarios, such as NR-D2D scenarios, etc., or to V2X scenarios, such as NR-V2X scenarios, etc. For example, the embodiments of the present application can be used in fields such as factory manufacturing, whole-house intelligence, intelligent driving, assisted driving, intelligent connected vehicles, or indoor commercial scenarios.

[0131] Please refer to Figures 2A to 2C for schematic diagrams of several application scenarios according to embodiments of the present application. Figures 2A, 2B, and 2C each include a UE, network equipment, and a data network (DN), where the network equipment may include access network equipment and core network equipment. For example, an application server within the DN can provide corresponding services to the UE, and services are transmitted between the UE and the application server via the access network equipment and the core network equipment.

[0132] Figure 2A illustrates a terrestrial communication scenario, or a terrestrial network, while Figures 2B and 2C illustrate satellite communication scenarios, or non-terrestrial networks (NTNs). These are all communication scenarios applicable to embodiments of the present application. The NTN may include a transparent mode and a regenerative mode. Figure 2B illustrates the transparent mode, while Figure 2C illustrates the regenerative mode. In the transparent mode, the satellite does not function as an access network device, and the access network device is deployed on the ground. In the regenerative mode, the satellite functions as an access network device, or the access network device is deployed on the satellite.

[0133] The following describes the method provided by the embodiments of the present application in conjunction with the accompanying drawings. The services in the various embodiments of the present application (such as the first service described below) may include media services, such as one or more of voice services, video services, or image services; or the services in the various embodiments of the present application may also include other types of services, without limitation.

[0134] The various embodiments of this document can be applied to the network architecture shown in any of Figures 2A to 2C. For example, the first device described in the various embodiments of this document can be the UE in any of Figures 2A to 2C, and the second device described in the various embodiments of this document can be the access network device in any of Figures 2A to 2C; or, the first device described in the various embodiments of this document can be the access network device in any of Figures 2A to 2C, and the second device described in the various embodiments of this document can be the UE in any of Figures 2A to 2C. Among them, the first device is the sender of the data packet, and the second device is the receiver of the data packet. The core network device described in the various embodiments of this document can be the core network device in any of Figures 2A to 2C.

[0135] An embodiment of the present application provides a communication method. Please refer to FIG3 , which is a flowchart of the method.

[0136] S301: A first device compresses a header of a first data packet to obtain a second data packet. The first data packet is, for example, a data packet of a first service, and the first data packet after header compression is referred to as a second data packet.

[0137] Performing header compression on the first data packet can be understood as compressing the header of the first data packet. Optionally, the compression method is, for example, ROHC compression, or it can be other compression methods, and the embodiments of the present application are not limited to this. Optionally, S301 is executed by, for example, the packet data convergence protocol (PDCP) layer of the first device. For example, if the compression method is ROHC compression, S301 can be executed by the ROHC module in the PDCP layer. Taking the header compression as ROHC compression as an example, for example, the header of the first data packet can refer to Figure 4A, and the header of the second data packet can refer to Figure 4B.

[0138] The header of the first data packet, for example, includes one or more of an IP header, a UDP header, or an RTP header. The UDP header may include a checksum field that can be used to verify the transmission correctness of the first data packet or the transmission correctness of the payload within the first data packet. This checksum field is, for example, a UDP checksum field, or may be another field used for verification. For other fields within the header of the first data packet, please refer to the description of FIG. 1A above. Optionally, before performing header compression on the first data packet, the first device may modify the value of the checksum field within the UDP header of the first data packet to a first value. The first value may be predefined by a protocol, configured by a core network device and / or an access network device, preconfigured between the first device and the second device, or determined by negotiation between the first device and the second device. The first value may be, for example, a dummy value. In S301, the checksum field within the UDP header of the first data packet compressed by the first device is set to the first value.

[0139] S302: The first device removes the check field included in the header of the second data packet to obtain a third data packet. For example, the second data packet after the check field is removed is referred to as the third data packet.

[0140] Optionally, S301 can be executed by a first module in the first device, and the first module can be a hardware module or a software module. The first module can be located in an application processor (AP) or a modem of the first device. For example, the first module can be an independent functional module in the AP, and the first module can be located below the RTP / UDP / IP layer; or, the first module can also be located in an existing protocol layer in the AP, for example, the first module can be located in the RTP / UDP / IP layer. For another example, the first module can be an independent functional module in the modem, and the first module can be located above the PDCP layer; or, the first module can also be located in an existing protocol layer in the modem, for example, the first module can be located in the PDCP layer, refer to Figure 5. Figure 5 takes the example that the first device is a UE and the second device is an access network device. In addition to the RTP / UDP / IP layer and the PDCP layer, the UE can also include an application (APP) layer, and can also include other access layers (other AN layer). In addition to the PDCP layer, UDP / IP layer, and other access layers, access network equipment may also include Layers (L1, L2), and the General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U), without limitation. Furthermore, because access network equipment transmits data packets between the UE and the application server, it can be considered a relay.

[0141] The header of the second data packet is a compressed header, for example, the header includes a check field. Taking the compression method as the ROHC method as an example, the header of the second data packet can refer to Figure 4B. In Figure 4B, the header of the second data packet is called, for example, a ROHC header, and the ROHC header includes a ROHC packet and a check field. Optionally, the ROHC packet occupies 1 byte, and the check field occupies 2 bytes. It can be seen that after the header is compressed, the header also includes a check field. Then, in an embodiment of the present application, the first device can remove the check field, so that the header of the third data packet does not include the check field. For example, the check field occupies 2 bytes. By removing the check field, the amount of information in the third data packet can be reduced to a large extent, thereby reducing the transmission overhead of the third data packet.

[0142] S303: The first device sends a third data packet, and correspondingly, the second device receives the third data packet.

[0143] S304: The second device decompresses the header of the third data packet. Optionally, S301 is performed by the PDCP layer of the second device, for example.

[0144] Decompressing the header of the third data packet can be understood as decompressing the header of the third data packet. Optionally, the compression method may be, for example, ROHC compression, or other compression methods, which are not limited in this embodiment of the present application. Optionally, S304 is performed by, for example, the PDCP layer of the second device. For example, if the compression method is ROHC compression, S304 may be performed by the ROHC module in the PDCP layer.

[0145] Optionally, before decompressing the header of the third data packet, the second device may first add a checksum field to the header of the third data packet, for example, with the checksum field having a first value. Because the first device removed the checksum field from the header, decompression may first add the checksum field to decompress the data according to the complete header. However, the second device cannot yet determine the true value of the checksum field, so the second device may set the checksum field to the first value. If the first device set the checksum field in the header of the first data packet to the first value before compressing the first data packet, then the second device may add the checksum field to the header of the third data packet with the first value. This ensures consistent processing between the transmitting and receiving ends, improving decompression accuracy. Alternatively, the first device may not have set the checksum field in the header of the first data packet to the first value when compressing the first data packet, but instead compressed the data according to the true value of the checksum field. In this case, the second device may also add the checksum field to the header of the third data packet with the first value to restore the complete header.

[0146] After adding the check field, the second device can decompress the header of the third data packet to which the check field is added.

[0147] S305. The second device determines, based on the third data packet after decompressing the header, that the value of the check field is a second value. The second value can be understood as the true value of the check field determined by the second device. Optionally, the second value can be the same as the true value of the check field determined by the first device.

[0148] For example, if the first device is a UE and the second device is an access network device, although the second device receives the third data packet, it may not be the intended recipient of the data in the third data packet. For example, the data is ultimately intended for transmission to an application server providing the first service, meaning the second device still needs to send the data. The checksum field can be used by the application server to verify the received data to determine whether it has been received correctly. Therefore, the second device can determine the true value of the checksum field, enabling it to set the true value of the checksum field in the packet header when it continues to transmit the data for verification by the application server.

[0149] Optionally, the second device can determine the value of the check field as a second value based on information such as the IP header, UDP header, and UDP data of the decompressed third data packet. For example, the second device can determine the second value based on the pseudo header + UDP header + first part (for example, understood as a bit stream of these three parts connected in series). The first part can be the result of performing one-in-two summation of the UDP data according to 16 bits. The process includes, for example, splitting the UDP data into multiple parts according to 16 bits, for example, each part includes 16 bits, inverting the values ​​of the bits included in each part (for example, if the value of a bit is originally 1, it is changed to 0; or if the value of a bit is originally 0, it is changed to 1), inverting the values ​​of the bits included in the multiple parts, and then adding the corresponding values ​​of the bits in each part (for example, any two parts of the multiple parts can have a one-to-one correspondence in sequence, and the values ​​of the corresponding two bits are added), to obtain a 16-bit bit stream, which can be used as the above-mentioned first part.

[0150] In addition, the pseudo header may include one or more of the following: the IP source address in the IP header within the header of the decompressed third data packet, the IP destination address in the IP header, the protocol number in the IP header, or the UDP length in the UDP header within the header of the decompressed third data packet.

[0151] UDP data may include information other than the UDP header in the third data packet's header. For example, the IP layer, RTP layer, and UDP layer are protocol layers in a top-down relationship. A data packet is transmitted from the IP layer to the UDP layer, and each layer adds a header corresponding to that layer as the data packet is processed. The UDP layer receives a data packet from the RTP layer, and the UDP layer can add a UDP header to the data packet. After the UDP header is added, all other information in the data packet, except for the UDP header, can be considered UDP data.

[0152] S306. Set the value of the check field in the third data packet after decompressing the header to the second value to obtain a fourth data packet. Optionally, S305 and / or S306 can be executed by the first module in the second device, and reference can be made to Figure 5. That is, the embodiment of the present application can also set the first module in the second device, and the first module in the second device can implement the function corresponding to the first module in the first device. The implementation method of the first module in the second device can refer to the introduction to the first module in the first device. The first module in the first device and the first module in the second device can be in the same position, for example, both are located in the PDCP layer (as shown in Figure 5); or, the first module in the first device and the first module in the second device can also be in different positions, for example, the first module in the first device is located in the AP, and the first module in the second device is located in the PDCP layer.

[0153] Before decompressing the header of the third data packet, the second device may first add a checksum field to the header of the third data packet, for example, with the value of the checksum field set to the first value. In S306, the second device may then set the value of the checksum field to the second value, thereby restoring the checksum field. If the restoration is successful, the fourth data packet recovered by the second device may be identical to the first data packet processed by the first device.

[0154] For example, referring to Figure 6, an example of a processing process between a first device and a second device is shown. For example, the first device obtains a first data packet. The header of the first data packet may include an IP header, a UDP header, and an RTP header, and the first data packet also includes a payload. The first device sets the value of the checksum field in the UDP header to a first value. Then, the ROHC module in the first device performs header compression on the first data packet to obtain a second data packet. The second data packet may include an ROHC header (for example, including a checksum field and an ROHC packet) and a payload. The first module in the first device removes the checksum field from the second data packet to obtain a third data packet. The third data packet may include an ROHC header and a payload, but the ROHC header no longer includes the checksum field. The first device sends the third data packet, and the second device receives the third data packet. The second device may add a checksum field to the header of the third data packet, with the value of the checksum field set to the first value. The third data packet with the added checksum field may include an ROHC header (for example, including a checksum field and an ROHC packet) and a payload. The ROHC module of the second device decompresses the header of the third data packet to which the check field is added. The decompressed third data packet may include an IP header, a UDP header, an RTP header, and a payload, wherein the value of the check field in the UDP header is a first value. The first module in the second device may determine the true value of the check field and modify the value of the check field to the second value, thereby obtaining a fourth data packet.

[0155] Optionally, if the second device is not the target receiving device of the fourth data packet, for example, the first device is a UE, the second device is an access network device, and the target receiving device of the fourth data packet is an application server providing the first service, then after S306, the second device may send the fourth data packet. For example, the second device may send the fourth data packet to a core network device, so that the fourth data packet is sent to the application server through the core network device.

[0156] Alternatively, if the second device is the target receiving device of the fourth data packet, for example, the first device is an access network device and the second device is a UE, the second device does not need to send the fourth data packet and the transmission process ends.

[0157] The function of removing the check field provided in the embodiments of the present application is, for example, a capability of the first device and / or the second device, which may be supported by some devices and not supported by others. To this end, optionally, the first device or the second device may report capability information, which may indicate whether the first device or the second device supports removing the check field during transmission. Taking the check field as an example, the capability information is called UDP checksum reduction, such as UChsRed for short, or the capability information may have other names. For example, if the first device is a UE and the second device is an access network device, the first device may send the capability information of the first device to the second device, which may indicate whether the first device supports removing the check field during transmission; or, if the second device is a UE and the first device is an access network device, the second device may send the capability information of the second device to the first device, which may indicate whether the second device supports removing the check field during transmission. Optionally, the receiving end of the capability information (the first device or the second device) may first send capability query information to the sending end of the capability information (the second device or the first device) to query the capabilities of the sending end. After receiving the capability query information, the transmitting end may send the capability information to the receiving end. Optionally, the receiving end may also send the capability information to a core network device so that the core network device can also clearly identify the capabilities of the corresponding device. The core network device may be, for example, an AMF, or other device within the core network.

[0158] Alternatively, the first device or the second device may not need to report capability information. For example, the first device or the second device supports removing the check field during transmission by default.

[0159] Optionally, the function of removing the check field during transmission provided in the embodiment of the present application can be activated or deactivated for flexible application. For example, the access network equipment in the first device and the second device can instruct the UE in the two devices to activate or deactivate the function. Taking the first service as a call service as an example, the network can establish a dedicated bearer for the call service, such as a media-dedicated bearer, which is usually a guaranteed bit rate (GBR) bearer, or the network can also not establish a dedicated bearer for the call service, but transmit the call service through a default bearer (default bearer) established when establishing an IP multimedia system (IMS) protocol data unit (PDU) session or a QoS flow (QoS Flow associated with default QoS rule) associated with a default QoS rule. Optionally, the default bearer is usually a non-GBR bearer. If the network wants to establish a media-dedicated bearer for the call service, the access network device can activate the function if it determines one or more of the following; otherwise, it is not necessary to activate or deactivate the function: the access network device uses narrowband (NB)-IoT communication, and the first service is a service transmitted through NB-IoT, or the media-dedicated bearer is a bearer communicated through NB-IoT (for example, the quality of service (QoS) level requirement of the media-dedicated bearer is voice or video, for example, the QoS corresponding to the QoS is 1 or 2.). Because the supported bandwidth is small for NB-IoT, it is particularly important to reduce transmission overhead. Therefore, for NB-IoT, the function of removing the check field during transmission provided in the embodiment of the present application can be used to reduce transmission overhead, improve network performance, and reduce the probability of network congestion. For example, the core network device sends a bearer establishment message to the access network device, and the bearer establishment message can be used to establish the media-dedicated bearer, and the media-dedicated bearer is used to transmit the first service. The access network device may then send a first message to the UE, where the first message may indicate activation of a function for removing the check field during transmission. Optionally, the access network device may send the first message to the UE upon determining one or more of the above conditions. The bearer establishment message may be, for example, an S1 interface message in an LTE system or an N2 message in a 5G system.Optionally, the first message is, for example, a radio resource control (RRC) message, such as an RRC reconfiguration (RRC reconfiguration) message, or may be other RRC messages or messages of other protocol layers.

[0160] If the network does not establish a media-dedicated bearer for the call service, but transmits the call service through the default bearer, the access network device can activate this function if it determines that the access network device adopts NB-IoT communication and / or determines that the first service is a service transmitted through NB-IoT. Otherwise, it is not necessary to activate or deactivate this function. For example, if the access network device receives a second message from the UE or the core network device, the access network device can send a first message to the UE. Optionally, the access network device can send a first message to the UE if it determines that the access network device adopts NB-IoT communication and / or determines that the first service is a service transmitted through NB-IoT. The second message may indicate the start of transmission of the media service. For the introduction of the first message, please refer to the previous text.

[0161] For example, if the UE receives a session initialization protocol (SIP) message from the IMS, such as the calling UE receives a SIP 180, SIP 183, or SIP 200OK message from the called UE, it can be determined that the call is connected, and the UE can send a second message to the access network device. The second message can trigger the access network device to perceive the start of transmission of the first service (taking the first service as a call service as an example, the start of transmission of the first service can also be understood as the start of transmission of call data). After receiving the second message, the access network device can send the first message to the UE. The second message, for example, includes indication information, which can instruct the UE to start transmission of the first service, or start transmission of data packets of the first service. Optionally, the second message can also include description information of the data packets of the first service, such as the IP3 tuple or IP5 tuple corresponding to the data packets of the first service. Optionally, the second message is, for example, an RRC message, or it can also be information of other protocol layers. The UE may be a calling UE, and the access network device may be an access network device serving the calling UE; or the UE may be a called UE, and the access network device may be an access network device serving the called UE.

[0162] For another example, after the call between the calling UE and the called UE is connected, the IMS serving the called UE can send a SIP message to the called UE. After the called UE receives the SIP message (such as a SIP provisional response ACKnowledgement (PRACK) or a SIP update (UPDATE) message), it can send a second message to the access network device serving the called UE. Alternatively, after the call between the calling UE and the called UE is connected, when the called UE sends a SIP message (such as a SIP 180, SIP 183, or SIP 200OK message), it can send a second message to the access network device serving the called UE. The second message can trigger the access network device to perceive and start transmitting the first service. After receiving the second message, the access network device can send the first message to the called UE.

[0163] In addition, after receiving the SIP message, the called UE can also send a SIP message to the IMS, and after receiving the SIP message, the IMS can send a SIP message to the IMS serving the calling UE. After receiving the SIP message, the IMS serving the calling UE can send a SIP message to the calling UE. After receiving the SIP message, the calling UE can send a second message to the access network device serving the calling UE. The second message can trigger the access network device to perceive and start transmitting the first service. After receiving the second message, the access network device can send the first message to the calling UE. Regarding the above first message or second message, etc., please refer to the introduction above. It can be seen that the solution of the embodiment of the present application can be applicable to the calling party and / or the called party. For example, the calling party and the called party can both execute the solution of the embodiment of the present application.

[0164] In summary, the embodiment of the present application can remove the check field in the header of the second data packet, so that the second data packet (i.e., the third data packet) after the check field is removed is sent. The amount of information in the header of the second data packet is reduced, thereby reducing the transmission overhead of the header, which is beneficial to improving the transmission performance of the network. If the second device is not the target receiving device of the first data packet, the second device can also restore the check field so that the target receiving device of the first data packet (such as the application server) can verify the correctness of the received data packet based on the check field. It can be seen that the embodiment of the present application can not only ensure the correctness of transmission to a certain extent, but also reduce the transmission overhead.

[0165] An embodiment of the present application provides another communication method. Please refer to FIG7 , which is a flowchart of the method.

[0166] S701: A first device sends N data packets. Correspondingly, a second device receives N data packets, where N is an integer greater than or equal to 2.

[0167] The N data packets may be data packets for the first service. Among the N data packets, some may include packet headers, while the remaining data packets in the N data packets, excluding the portion, may not include packet headers. For example, a packet header may include an IP header, a UDP header, and an RTP header. In other words, the embodiment of the present application may remove the packet headers of some data packets corresponding to the first service, thereby reducing transmission overhead.

[0168] Optionally, the partial data packet may be the first data packet among N data packets (for example, the N data packets have their own corresponding numbers, and the partial data packet may be the data packet that is numbered first when numbered sequentially, such as the data packet with the smallest or earliest number) or the last data packet (for example, the partial data packet may be the data packet that is numbered last when numbered sequentially, such as the data packet with the largest or latest number), in which case the number of the partial data packets is 1; or, the partial data packet may be any data packet among the N data packets; or, the partial data packet may be the partial data packet that is transmitted first or last among the N data packets, or any partial data packet among the N data packets, in which case the number of the partial data packets may be greater than or equal to 1.

[0169] Optionally, the N data packets may be all data packets corresponding to the first service, or may be a portion of the data packets corresponding to the first service. For example, if the N data packets are all data packets corresponding to the first service, and the portion of the data packets is the first of the N data packets, then for the first service, only the first data packet has a header, and the other data packets do not. This solution can significantly reduce transmission overhead.

[0170] For another example, if the N data packets are partial data packets corresponding to the first service, the number N can be predefined by the protocol, preconfigured in the first and second devices, or determined by negotiation between the first and second devices. Alternatively, the number N can be dynamically determined. For example, the N data packets can be data packets sent via a single scheduled resource. In this case, the corresponding value of N can be the same or different in different resource scheduling cycles. It can be understood that during the transmission of the first service, the first device may need to schedule resources multiple times to send data packets of the first service. A single scheduled resource can send one or more data packets of the first service. In this case, the N data packets can be all or part of the data packets sent via the single scheduled resource. This is equivalent to allowing some data packets to carry headers while the remaining data packets do not, thereby reducing transmission overhead. Furthermore, since a single scheduled resource has relatively few data packets, even if some data packets do not carry headers, the missing headers can be recovered based on the existing headers, which helps reduce error rates.

[0171] Optionally, an embodiment of the present application may add a second module to the first device, and the second module may be used to determine the headers of N data packets, for example, to determine which of the N data packets retain the headers and which data packets remove the headers. The second module may be a hardware module or a software module. The second module may be located in the AP or modem of the first device. For example, the second module may be an independent functional module within the AP, and the second module may be located below the RTP / UDP / IP layer; or, the second module may also be located in an existing protocol layer within the AP, and the second module may be located in the RTP / UDP / IP layer. For another example, the second module may be an independent functional module within the modem, and the second module may be located above the PDCP layer; or, the second module may also be located in an existing protocol layer within the modem, and the second module may be located in the PDCP layer.

[0172] For example, if the second module is located within the AP of the first device, the AP may add a header to each of some of the N data packets, while not adding a header to the remaining data packets. The AP then passes the processed N data packets to the modem of the first device. Alternatively, this approach may be applicable where N is statically configured, for example, predefined by a protocol, preconfigured in the first and second devices, or determined through negotiation between the first and second devices. Alternatively, the AP may add a header to each of the received data packets, but may temporarily not pass these packets to the modem. If the AP receives an indication from the modem indicating data packet transmission or indicating the availability of resources for data packet transmission, the AP may retain the headers of some of the unsent data packets within the AP, remove the headers of the remaining data packets, and then pass the processed data packets to the modem. These data packets constitute the N data packets. Alternatively, this approach may be applicable where N is dynamically determined. Regardless of which approach the AP adopts, the modem can simply transmit the data packets from the AP without having to perform any additional processing such as adding or removing headers.

[0173] Alternatively, if the second module is located within a modem of the first device, the AP of the first device may add a header to each received data packet in a conventional manner and send the processed data packets to the modem. After receiving the data packets from the AP, the modem may retain the headers of some of the data packets, remove the headers of the remaining data packets, and then send the processed data packets. If N is determined dynamically, and the number of data packets from the AP may be less than, greater than, or equal to N, if the number of data packets from the AP is less than N, the modem may wait until the number of data packets from the AP reaches N, retain the headers of some of the data packets, remove the headers of the remaining data packets, and then send the processed data packets. Alternatively, if the number of data packets from the AP is equal to N, the modem may retain the headers of some of the data packets, remove the headers of the remaining data packets, and then send the processed data packets. Alternatively, if the number of data packets from the AP is greater than N, the modem may select N data packets (e.g., select N data packets received earlier), retain the packet headers of some of the data packets, remove the packet headers of the remaining data packets, and then send the processed data packets. As for the data packets that are not selected, the modem may process them next time.

[0174] Optionally, regardless of whether the second module is located in the AP or the modem, the modem can compress each retained header in the N data packets separately, and then send the N data packets after the header compression to reduce transmission overhead. The compression method is, for example, ROHC, or it can be other methods. In order to further save transmission overhead, the embodiment of the present application can also be optionally combined with the embodiment shown in Figure 3. For example, for each data packet in a portion of the N data packets, the first device can compress the header of the data packet, and can remove the check field included in the compressed header, and the first device can send the N data packets after the check field is removed. For an introduction to the specific content of this part, please refer to the embodiment shown in Figure 3.

[0175] S702, the second device determines the headers of the remaining data packets based on the headers of some data packets in the N data packets. Optionally, S702 can be executed by the second module of the second device, that is, the embodiment of the present application can also set a second module in the second device, and the second module in the second device can implement the function corresponding to the second module in the first device. The implementation method of the second module in the second device can refer to the introduction of the second module in the first device. The second module in the first device and the second module in the second device can be in the same position, for example, both are located in the PDCP layer; or the second module in the first device and the second module in the second device can also be in different positions, for example, the second module in the first device is located in the AP, and the second module in the second device is located in the PDCP layer.

[0176] The second device receives N data packets, but only some of them have headers, while the remaining data packets do not. The second device can then restore the headers of the remaining data packets based on the headers of the partial data packets, so that the N data packets all have their own headers. For example, if the target receiving device of the N data packets is not the second device, but the second device continues to send the N data packets (for example, the first device is a UE, the second device is an access network device, and the target receiving device is an application server providing the first service), the second device can restore the headers of the remaining data packets so that the target receiving device can obtain the complete N data packets.

[0177] For example, if the partial data packet is the first of N data packets, the second device may number the remaining data packets starting with the number of the first data packet plus 1, and number the remaining data packets in the order in which the remaining data packets were received. For example, if the first data packet is numbered n, the N data packets may be numbered n+1, n+2, ..., in the order in which they were received, so that the second device can recover the packet headers of the remaining data packets.

[0178] For another example, if the partial data packet is the last of N data packets, the second device can reverse number the remaining data packets, starting from the number of the last data packet minus 1, according to the order in which the remaining data packets were received. For example, if the last data packet is numbered n, the N data packets can be reverse numbered n-1, n-2, ..., according to the order in which they were received, where the data packet numbered n-1 is received after the data packet numbered n-2. In this way, the second device can recover the packet headers of the remaining data packets.

[0179] For another example, if the partial data packet is any one of N data packets, the second device can predict the position of the arbitrary data packet in the N data packets. For example, the position can be negotiated by the first device and the second device, or predefined through a protocol, or preconfigured in the first device and the second device. The second device can then number the remaining data packets according to the position of the arbitrary data packet and the order in which the remaining data packets were received. For example, if the arbitrary data packet is the third data packet in the N data packets, the second device can start with the number of the arbitrary data packet minus 1, and reverse number the first two data packets in the N data packets, and forward number the data packets after the third data packet in the N data packets. In this way, the second device can recover the packet header of the remaining data packet.

[0180] If the embodiment of the present application is combined with the embodiment shown in FIG3 , for example, for each of the partial data packets of N data packets, the first device compresses the header of the data packet and removes the check field included in the compressed header. The first device sends the N data packets after the check field is removed, and the second device receives the N data packets after the check field is removed. Optionally, the second device can restore the check field in each retained header of the N data packets. The restoration method can refer to the embodiment shown in FIG3 . For example, the second device can restore the check field and then determine the headers of the remaining data packets based on the retained headers, or the second device can first determine the headers of the remaining data packets based on the retained headers and then restore the check field in the retained headers.

[0181] For example, refer to Figure 8, which illustrates an example of the processing process between the first and second devices. In Figure 8, of the N data packets sent by the first device, some carry headers (including IP headers, UDP headers, and RTP headers), while the remaining data packets do not carry headers. For example, the remaining data packets include payloads but not headers. After the N data packets arrive at the second device, the second device can recover the headers of the remaining data packets based on the headers of the partial data packets, thereby obtaining the complete N data packets.

[0182] Optionally, if the second device is not the intended recipient of the N data packets, for example, the first device is a UE, the second device is an access network device, and the intended recipient of the fourth data packet is an application server providing the first service, then after S702, the second device may send the N data packets. For example, the second device may send the N data packets to the core network device, which then sends the N data packets to the application server via the core network device. Each of the N data packets sent by the second device may have a header.

[0183] Alternatively, if the second device is the target receiving device of the N data packets, for example, the first device is an access network device and the second device is a UE, the second device does not need to send N data packets again, and the transmission process ends.

[0184] The function of removing the header of a data packet during transmission provided in an embodiment of the present application is, for example, a capability of the first device and / or the second device, which may be supported by some devices and not supported by others. To this end, optionally, the first device or the second device may report capability information, which may indicate whether the first device or the second device supports removing the header of the data packet during transmission. The capability information is called, for example, IP / UDP / RTP header reduction, such as IUPHRed for short, or the capability information may have other names. For the method of reporting the capability information, please refer to the embodiment shown in Figure 3. Alternatively, the first device or the second device may not need to report capability information, for example, the first device or the second device may support removing the header of the data packet during transmission by default.

[0185] Optionally, the function of removing the packet header during transmission provided in the embodiments of the present application can be activated or deactivated for flexible application. For example, the access network equipment in the first and second devices can instruct the UEs in the two devices to activate or deactivate the function. For details on activation methods, please refer to the relevant description of the function of removing the check field during transmission in the embodiment shown in Figure 3.

[0186] In summary, the embodiment of the present application can remove the headers of some of the N data packets, so that the N data packets after the headers are removed are sent, which can greatly reduce the transmission overhead and help improve the transmission performance of the network. If the second device is not the target receiving device of the N data packets, the second device can also restore the headers of the N data packets, so that the target receiving device of the N data packets (such as an application server) can receive the complete N data packets. It can be seen that the embodiment of the present application can not only ensure the correctness of transmission to a certain extent, but also reduce the transmission overhead.

[0187] An embodiment of the present application provides another communication method. Please refer to FIG9 , which is a flowchart of the method.

[0188] S901. The first device obtains N data packets, where N is an integer greater than or equal to 2.

[0189] The N data packets may be data packets of the first service. Optionally, the N data packets may be all data packets corresponding to the first service, or may be part of the data packets corresponding to the first service. For an introduction to this, reference may be made to the embodiment shown in FIG7 .

[0190] S902. The first device obtains a first data packet based on N data packets.

[0191] The first data packet may include the payloads of N data packets and a first header, and the number of first headers is, for example, 1, that is, the first data packet may include one header but may include the payloads of N data packets. For example, it can be understood that the first device may place the payloads of N data packets into one data packet, or it can be understood that the first device merges the payloads of N data packets (or merges N data packets), thereby reducing the number of headers corresponding to the N data packets (for example, from N headers to one header), which can save transmission overhead.

[0192] Optionally, the sum of the lengths of the payloads of the N data packets may be less than or equal to an upper limit on the length of the data packets. This upper limit may be, for example, an upper limit on the length of the data packets specified by the protocol, i.e., the payload length of a data packet should be less than or equal to this upper limit. Optionally, the first device may determine the N data packets based on this upper limit. For example, if the sum of the payload lengths of a+1 data packets of the first service exceeds this upper limit, and the sum of the payload lengths of a data packets therein is less than or equal to this upper limit, the first device may determine that the a data packets are the N data packets.

[0193] The first packet header can be determined based on the packet headers of some or all of the N data packets. For example, the first device can comprehensively determine the first packet header based on the packet headers of multiple data packets (some or all of the data packets) in the N data packets; or, the first device can also determine the first packet header based on the packet header of a data packet in the N data packets. For example, the first packet header can be determined based on the packet header of the second data packet in the N data packets, and the second data packet can be, for example, the first or last data packet transmitted among the N data packets, or the first data packet, the last data packet, or any data packet in the N data packets. For an introduction to the first data packet, the last data packet, or any data packet, etc., please refer to the embodiment shown in Figure 7.

[0194] The first packet header is determined according to the packet header of the second data packet. For example, one method is that the first device uses the packet header of the second data packet as the first packet header. This method is relatively simple and can simplify the process of determining the first packet header.

[0195] Optionally, the embodiment of the present application may add a third module to the first device, and S901 and S902 may be executed by the third module. The third module may be a hardware module or a software module. The third module may be located in the AP or modem of the first device. For example, the third module may be an independent functional module within the AP, and the third module may be located below the RTP / UDP / IP layer, as shown in FIG10A ; or, the third module may be located in an existing protocol layer within the AP, for example, the third module may be located in the RTP / UDP / IP layer. For another example, the third module may be an independent functional module within the modem, and the third module may be located above the PDCP layer; or, the third module may be located in an existing protocol layer within the modem, for example, the third module may be located in the PDCP layer, as shown in FIG10B . Regarding other protocol layers in FIG10A and FIG10B , please refer to the previous description of FIG5 .

[0196] For example, if the third module is located within the AP of the first device, then after receiving N data packets from an application (APP), the third module can obtain a first data packet based on the N data packets. The method for obtaining the first data packet can be referred to above. The third module then sends the first data packet to the modem of the first device. The modem of the first device can send the first data packet. Optionally, the modem of the first device can compress the first packet header, for example, the ROHC module within the modem can compress the first packet header, and then send the first data packet with the compressed packet header. N can be statically configured, for example, N is predefined by the protocol, or preconfigured in the first device and the second device, or determined by negotiation between the first device and the second device. In the case of static configuration, the third module can process every N data packets received. Alternatively, N can also be dynamically determined, for example, the value of N is not fixed, and the third module can continue to receive data packets from the APP and temporarily not process the data packets after receiving them. When the third module receives an instruction from the modem in the first device, such as an instruction to transmit a data packet or an indication that resources are available for transmitting a data packet, the third module may derive a first data packet from the received data packets. In this case, the received data packets are considered to be N data packets, and the third module sends the first data packet to the modem of the first device. Alternatively, if the sum of the payload lengths of the data packets received by the third module exceeds an upper limit on the data packet length, the third module may derive the first data packet from N data packets received (e.g., the N data packets received previously), and then send the first data packet to the modem of the first device. The third module may process the remaining received data packets at a later time.

[0197] Alternatively, if the third module is located within a modem of the first device, after receiving N data packets from the AP of the first device, the third module may derive a first data packet based on the N data packets. The method for deriving the first data packet is described above. The modem may then transmit the first data packet. Optionally, the third module may pass the first data packet to a ROHC module within the PDCP layer. The ROHC module may compress the first packet header (this is assuming the header compression method is ROHC, or the first packet header may be compressed using other methods). If N is statically configured, the third module may derive the first data packet based on each N data packets received from the AP of the first device. Alternatively, if N is dynamically determined, the third module may continuously receive data packets from the AP of the first device. When resources are available to transmit data packets, the third module derives the first data packet based on the data packets already received from the AP. Alternatively, if the sum of the payload lengths of the data packets received from the AP by the third module exceeds the upper limit of the data packet length, the third module may derive the first data packet based on N data packets already received from the AP (e.g., the N data packets previously received). The third module may process the remaining data packets already received from the AP at a later time.

[0198] As can be seen from the above, regardless of whether the third module is located in the AP or the modem, the modem can compress the first packet header and then send the first data packet with the compressed header to reduce transmission overhead. The compression method is, for example, ROHC, or other methods. To further reduce transmission overhead, the embodiment of the present application can optionally be combined with the embodiment shown in Figure 3. For example, for the first data packet, the first device can compress the first packet header and remove the check field included in the compressed first packet header. The first device can then send the compressed data packet with the check field removed. For an introduction to the specific content of this part, please refer to the embodiment shown in Figure 3.

[0199] S903: The first device sends a first data packet, and the second device receives the first data packet accordingly.

[0200] S904: The second device determines the headers of the N data packets based on the first header. This can be understood as the second device recovering the headers of the N data packets based on the first header.

[0201] Optionally, S904 may be executed by a third module of the second device, that is, the embodiment of the present application may also set a third module in the second device, and reference may be made to FIG10A or FIG10B. The third module in the second device may implement the function corresponding to the third module in the first device, and the implementation method of the third module in the second device may refer to the introduction to the third module in the first device. The third module in the first device and the third module in the second device may be in the same position, for example, both are located in the PDCP layer (as shown in FIG10B); or, the third module in the first device and the third module in the second device may also be in different positions, for example, the third module in the first device is located in the AP, and the third module in the second device is located in the PDCP layer (as shown in FIG10A).

[0202] The second device receives the first data packet, but it contains only the first packet header and no other packet headers. The second device can then restore the packet headers of the N data packets based on the first packet header, so that the N data packets all have their own packet headers. For example, if the target receiving device of the N data packets is not the second device, but the second device continues to send the N data packets (for example, the first device is a UE, the second device is an access network device, and the target receiving device is an application server providing the first service), the second device can restore the packet headers of the N data packets so that the target receiving device can obtain the complete N data packets.

[0203] For example, if the first packet header is determined based on the second packet header, for example, if the second packet is the first of N packets, the second device can number the remaining packets in the N packets, starting with the number indicated by the first packet header plus 1, according to the order in which the remaining packets were received. For example, if the first packet is numbered n, the remaining N-1 packets are numbered n+1, n+2, and so on, in the order in which they were received. This allows the second device to recover the packet headers of the N packets.

[0204] For another example, if the second data packet is the last of N data packets, the second device can reverse number the remaining data packets, starting from the number of the last data packet minus 1, according to the order in which the remaining data packets in the N data packets were received. For example, if the last data packet is numbered n, the remaining N-1 data packets are reverse numbered n-1, n-2, ..., according to the order in which they were received, where the data packet numbered n-1 is received after the data packet numbered n-2. In this way, the second device can recover the packet headers of the N data packets.

[0205] For another example, if the second data packet is any one of the N data packets, the second device can predict the position of the any one data packet in the N data packets. For example, the position can be negotiated by the first device and the second device, or predefined by a protocol, or preconfigured in the first device and the second device. The second device can number the remaining data packets according to the position of the any one data packet and the order in which the remaining data packets in the N data packets are received. For example, if the any one data packet is the third data packet in the N data packets, the second device can start from the number of the any one data packet minus 1, and reversely number the first two data packets in the N data packets, and forward number the data packets after the third data packet in the N data packets. In this way, the second device can recover the packet headers of the N data packets.

[0206] If the embodiment of the present application is combined with the embodiment shown in FIG3 , for example, the first device compresses the first packet header and removes the check field included in the compressed first packet header. The first device sends the first data packet after the check field is removed, and the second device receives the first data packet after the check field is removed. Optionally, the second device can restore the check field in the first packet header. The restoration method can refer to the embodiment shown in FIG3 . For example, the second device can restore the check field and then determine the packet headers of N data packets based on the first packet header. Alternatively, the second device can first determine the packet headers of N data packets based on the first packet header and then restore the check field in the first packet header.

[0207] For example, referring to Figure 11, an example of the processing process of the first device and the second device is shown. In Figure 11, the first device obtains N data packets. After processing the N data packets, the first device obtains a first data packet. The first data packet may include a first packet header and the payloads of the N data packets (for example, payload 1 to payload N shown in Figure 11). The first packet header may include an IP header, a UDP header, and an RTP header. The first device performs ROHC compression on the first packet header and then sends the first data packet. For example, the first data packet sent by the first device includes an ROHC header (the ROHC header, for example, includes a checksum field and a ROHC packet) and the payloads of the N data packets. Figure 11 is an example of the embodiment of the present application not being combined with the embodiment shown in Figure 3, that is, the first device does not remove the checksum field in the compressed first packet header. After the first data packet arrives at the second device, the second device can decompress the first packet header and then restore the packet headers of the N data packets based on the decompressed first packet header, so that the second device can obtain the complete N data packets.

[0208] Optionally, if the second device is not the intended recipient of the N data packets, for example, the first device is a UE, the second device is an access network device, and the intended recipient of the fourth data packet is an application server providing the first service, then after S904, the second device may send the N data packets. For example, the second device may send the N data packets to the core network device, which then sends the N data packets to the application server via the core network device. Each of the N data packets sent by the second device may have a header.

[0209] Alternatively, if the second device is the target receiving device of the N data packets, for example, the first device is an access network device and the second device is a UE, the second device does not need to send N data packets again, and the transmission process ends.

[0210] The function of merging data packets (or merging the payloads of data packets) during transmission provided in the embodiments of the present application is, for example, a capability of the first device and / or the second device, which may be supported by some devices and not supported by some devices. To this end, optionally, the first device or the second device may report capability information, which may indicate whether the first device or the second device supports merging data packets (or merging the payloads of data packets) during transmission. The capability information is, for example, called application payload combination (APC), for example, or the capability information may have other names. For the method of reporting the capability information, reference may be made to the embodiment shown in FIG3 . Alternatively, the first device or the second device may not need to report capability information, for example, the first device or the second device may support merging data packets (or merging the payloads of data packets) during transmission by default.

[0211] Optionally, the function of merging data packets (or merging the payloads of data packets) during transmission provided in the embodiments of the present application can be activated or deactivated for flexible application. For example, the access network devices in the first device and the second device can instruct the UEs in the two devices to activate or deactivate the function. For details on activation methods, etc., please refer to the relevant description of the function of removing the check field during transmission in the embodiment shown in Figure 3.

[0212] In summary, the embodiment of the present application can merge the payloads of N data packets, so that the first data packet obtained can only include the first packet header and no longer include other packet headers, which can greatly reduce the transmission overhead and help improve the transmission performance of the network. If the second device is not the target receiving device of the N data packets, the second device can also restore the packet headers of the N data packets based on the first packet header, so that the target receiving device of the N data packets (such as an application server) can receive the complete N data packets. It can be seen that the embodiment of the present application can not only ensure the correctness of transmission to a certain extent, but also reduce the transmission overhead.

[0213] Figure 12 shows a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1200 may be the first device described in the embodiment shown in any one of Figures 3, 7 or 9, for implementing the method corresponding to the first device in the above method embodiment. Alternatively, the communication device 1200 may be the second device described in the embodiment shown in any one of Figures 3, 7 or 9, for implementing the method corresponding to the second device in the above method embodiment. The first device is, for example, a device or a circuit system; the second device is, for example, a device or a circuit system. For example, a circuit system is a chip system.

[0214] The communication device 1200 includes at least one processor 1201. Processor 1201 can be used for internal processing of the device, implementing certain control processing functions. Optionally, processor 1201 includes instructions. Optionally, processor 1201 can store data. Optionally, different processors can be independent devices, located in different physical locations, or on different integrated circuits. Optionally, different processors can be integrated into one or more processors, for example, on one or more integrated circuits.

[0215] Optionally, the communication device 1200 includes one or more memories 1203 for storing instructions. Optionally, data may also be stored in the memories 1203. The processor and memory may be provided separately or integrated together.

[0216] Optionally, the communication device 1200 includes a communication line 1202 and at least one communication interface 1204. Since the memory 1203, the communication line 1202 and the communication interface 1204 are all optional, they are indicated by dotted lines in FIG12 .

[0217] Optionally, the communication device 1200 may further include a transceiver and / or an antenna. The transceiver may be used to send information to or receive information from other devices. The transceiver may be referred to as a transceiver, a transceiver circuit, an input / output interface, etc., and is used to implement the transceiver function of the communication device 1200 through an antenna. Optionally, the transceiver includes a transmitter and a receiver. For example, the transmitter may be used to generate a radio frequency signal from a baseband signal, and the receiver may be used to convert the radio frequency signal into a baseband signal.

[0218] The processor 1201 may include a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0219] The communication link 1202 may include a pathway for transmitting information between the aforementioned components.

[0220] The communication interface 1204 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.

[0221] The memory 1203 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1203 may exist independently and be connected to the processor 1201 via the communication line 1202. Alternatively, the memory 1203 may be integrated with the processor 1201.

[0222] The memory 1203 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 1201. The processor 1201 is used to execute the computer-executable instructions stored in the memory 1203, thereby implementing the steps performed by the first device or the second device in the embodiment shown in any of Figures 3, 7, or 9.

[0223] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0224] In a specific implementation, as an embodiment, the processor 1201 may include one or more CPUs, such as CPU0 and CPU1 in FIG12 .

[0225] In a specific implementation, as an embodiment, the communication device 1200 may include multiple processors, such as the processor 1201 and the processor 1205 in FIG12 . Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0226] When the apparatus 1200 shown in FIG12 is a chip, such as a chip of a UE or an access network device, the chip includes a processor 1201 (and may also include a processor 1205), a communication circuit 1202, and a communication interface 1204. Optionally, the chip may include a memory 1203. Specifically, the communication interface 1204 may be an input interface, a pin, or a circuit. The memory 1203 may be a register, a cache, or the like. The processor 1201 and the processor 1205 may be a general-purpose CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of a program of the communication method of any of the above-described embodiments.

[0227] The embodiment of the present application can divide the functional modules of the device according to the above-mentioned method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. For example, in the case of dividing each functional module according to each function, Figure 13 is a schematic diagram of a device, and the device 1300 can be the first device or the second device involved in each of the above-mentioned method embodiments. The device 1300 is, for example, a device, or a chip or a chip system. The device 1300 includes a processing unit 1302 and a transceiver unit 1301.

[0228] It should be understood that the device 1300 can be used to implement the steps performed by the first device or the second device in the communication method of the embodiment of the present application. The relevant features can refer to the embodiments shown in any of the figures in Figures 3, 7 or 9 above, and will not be repeated here.

[0229] Optionally, the functions / implementation processes of the transceiver unit 1301 and the processing unit 1302 in FIG13 may be implemented by the processor 1201 in FIG12 calling computer-executable instructions stored in the memory 1203. Alternatively, the functions / implementation processes of the processing unit 1302 in FIG13 may be implemented by the processor 1201 in FIG12 calling computer-executable instructions stored in the memory 1203, and the functions / implementation processes of the transceiver unit 1301 in FIG13 may be implemented by the communication interface 1204 in FIG12.

[0230] Optionally, when the device 1300 is a chip or circuit, the functions / implementation processes of the transceiver unit 1301 may also be implemented via pins or circuits. Optionally, the transceiver unit 1301 may include a transmitting unit and / or a receiving unit, where the transmitting unit is configured to implement the transmitting function and the receiving unit is configured to implement the receiving function. Alternatively, the transceiver unit 1301 may be an integral module capable of implementing the transmitting function and / or the receiving function. Optionally, the transceiver unit 1301 may be implemented via a transceiver.

[0231] The present application also provides a computer-readable storage medium, which stores a computer program or instruction, and when the computer program or instruction is run, implements the method performed by the first device or the second device in the aforementioned method embodiment. In this way, the functions described in the above embodiments can be implemented in the form of software functional units and sold or used as independent products. Based on this understanding, the technical solution of the present application is essentially or the part that contributes or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. Storage media include: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

[0232] The present application also provides a computer program product, which includes: computer program code, which, when running on a computer, enables the computer to execute the method executed by the first device or the second device in any of the aforementioned method embodiments.

[0233] An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is used to execute the method executed by the first device or the second device involved in any of the above method embodiments.

[0234] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0235] The various illustrative logic units and circuits described in the embodiments of the present application can be implemented or operated by a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any conventional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

[0236] The steps of the methods or algorithms described in the embodiments of the present application can be directly embedded in hardware, software units executed by a processor, or a combination of the two. The software unit can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), EEPROM, registers, hard disks, removable disks, CD-ROMs, or other storage media in any form known in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and storage medium can be provided in an ASIC, which can be provided in a terminal device. Alternatively, the processor and storage medium can also be provided in different components in the terminal device.

[0237] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0238] The contents of the various embodiments of this application can refer to each other. If there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0239] It is understood that in the embodiments of the present application, the first device and / or the second device can perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples. In the embodiments of the present application, other operations or variations of various operations can also be performed. In addition, the various steps can be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.

Claims

1. A communication method, characterized in that, The method includes: Perform header compression on a first data packet to obtain a second data packet; Remove a check field included in the header of the second data packet to obtain a third data packet; Transmit the third data packet.

2. The method according to claim 1, characterized in that, The check field is a User Datagram Protocol (UDP) checksum field.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Transmit or receive capability information, where the capability information is used to indicate support for removing the check field during transmission.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Transmit or receive a first message, where the first message is used to indicate activation of the function of removing the check field during transmission.

5. The method according to claim 4, characterized in that The method further includes: receiving a bearer establishment message from a core network device, where the bearer establishment message is used to establish a media dedicated bearer; transmitting the first message, including: based on the bearer establishment message, transmitting the first message; or, The method further includes: receiving a second message from a User Equipment (UE) or a core network device, where the second message is used to indicate the start of media service transmission; transmitting the first message, including: based on the second message, transmitting the first message.

6. The method according to claim 5, wherein The method further includes one or more of the following: Determine that the access network device uses NarrowBand Internet of Things (NB-IoT) communication; Determine that the media dedicated bearer is a bearer through NB-IoT communication; or, Determine that the media service is a service transmitted through NB-IoT.

7. A communication method, characterized in that, The method includes: Receive a third data packet; Perform header decompression on the third data packet; Determine that the value of the check field is a second value according to the third data packet after header decompression; Set the value of the check field in the third data packet after header decompression to the second value to obtain a fourth data packet.

8. The method according to claim 7, wherein Before performing header decompression on the third data packet, the method further includes: Add the check field within the third data packet, where the value of the check field is a first value.

9. The method according to claim 7 or 8, characterized in that, Determine that the value of the check field is a second value according to the third data packet after header decompression, including: Determine that the value of the check field is the second value according to the Internet Protocol (IP) header, UDP header, and UDP data of the third data packet after decompression.

10. The method according to any one of claims 7 to 9, characterized in that The method further includes: Transmit or receive capability information, where the capability information is used to indicate permission to remove the check field during transmission.

11. The method according to any one of claims 7 to 10, characterized in that, The method further includes: Transmit or receive a first message, where the first message is used to indicate activation of the function of removing the UDP checksum field during transmission.

12. The method according to claim 11, characterized in that The method further includes: receiving a bearer establishment message from a core network device, where the bearer establishment message is used to establish a media dedicated bearer; transmitting the first message, including: based on the bearer establishment message, transmitting the first message; or, The method further includes: receiving a second message from a UE or a core network device, where the second message is used to indicate the start of media service transmission; transmitting the first message, including: based on the second message, transmitting the first message.

13. The method according to claim 12, wherein The method further includes one or more of the following: Determine that the access network device communicates in NB-IoT mode; Determine that the media-specific bearer is a bearer communicating via the NB-IoT mode; or, Determine that the media service is a service transmitted via the NB-IoT mode.

14. A communication method, characterized in that, The method includes: Send N data packets, where some of the N data packets include packet headers, and the remaining data packets of the N data packets do not include packet headers. The partial data packets are the first data packet among the N data packets or the partial data packets that are transmitted first among the N data packets. N is an integer greater than or equal to 2.

15. The method according to claim 14, wherein The N data packets are all the data packets corresponding to the first service or partial data packets corresponding to the first service, where The N data packets are partial data packets corresponding to the first service, and the N data packets are data packets sent through resources scheduled at one time.

16. The method according to claim 14 or 15, characterized in that, The method further includes: Send or receive capability information, where the capability information is used to indicate support for removing the packet header during transmission.

17. The method according to any one of claims 14 to 16, characterized in that The method further includes: Send or receive a first message, where the first message is used to indicate activation of the function of removing the packet header during transmission.

18. The method according to claim 17, wherein The method further includes: receiving a bearer establishment message from a core network device, where the bearer establishment message is used to establish a media-specific bearer; sending a first message, including: based on the bearer establishment message, sending the first message; or, The method further includes: receiving a second message from a UE or a core network device, where the second message is used to indicate the start of transmitting a media service; sending a first message, including: based on the second message, sending the first message.

19. The method according to claim 18, wherein The method further includes one or more of the following: Determine that the access network device communicates via the NB-IoT mode; Determine that the media-specific bearer is a bearer communicating via the NB-IoT mode; or, Determine that the media service is a service transmitted via the NB-IoT mode.

20. A communication method, characterized in that, The method includes: Obtain N data packets; Obtain a first data packet according to the N data packets, where the first data packet includes the payloads of the N data packets and includes a first packet header, and the first packet header is determined according to the packet headers of some or all of the N data packets. N is an integer greater than or equal to 2; Send the first data packet.

21. The method according to claim 20, characterized in that, The N data packets are all the data packets corresponding to the first service or partial data packets corresponding to the first service, where The N data packets are partial data packets corresponding to the first service, and the N data packets are data packets sent through resources scheduled at one time.

22. The method according to claim 20 or 21, characterized in that The method further includes: Send or receive capability information, where the capability information is used to indicate support for merging the payloads of data packets during transmission.

23. The method according to any one of claims 20 to 22, characterized in that, The method further includes: Send or receive a first message, where the first message is used to indicate activation of the function of merging the payloads of data packets during transmission.

24. The method according to claim 23, wherein The method further includes: receiving a bearer establishment message from a core network device, where the bearer establishment message is used to establish a media dedicated bearer; sending a first message, including: based on the bearer establishment message, sending the first message; or, The method further includes: receiving a second message from a UE or a core network device, where the second message is used to indicate the start of media service transmission; sending a first message, including: based on the second message, sending the first message.

25. The method according to claim 24, wherein The method further includes one or more of the following: Determining that the access network device communicates in the NB-IoT mode; Determining that the media dedicated bearer is a bearer communicating in the NB-IoT mode; or, Determining that the media service is a service transmitted in the NB-IoT mode.

26. A communication method, characterized in that, The method includes: Receiving N data packets, where some of the N data packets include packet headers, and the remaining data packets among the N data packets do not include the packet headers, and N is an integer greater than or equal to 2; Determining the packet headers of the remaining data packets according to the packet headers of the partial data packets.

27. The method according to claim 26, wherein The partial data packets are the first data packet among the N data packets, or are the partial data packets transmitted first among the N data packets.

28. The method according to claim 26, wherein The N data packets are all the data packets corresponding to a first service, or are partial data packets corresponding to the first service.

29. The method according to any one of claims 26 to 28, characterized in that, The method further includes: Sending or receiving capability information, where the capability information is used to indicate support for removing the packet headers of data packets during transmission.

30. The method according to any one of claims 26 to 29, characterized in that, The method further includes: Sending or receiving a first message, where the first message is used to indicate activating the function of removing the packet headers of data packets during transmission.

31. The method according to claim 30, wherein, The method further includes: receiving a bearer establishment message from a core network device, where the bearer establishment message is used to establish a media dedicated bearer; Sending a first message, including: based on the bearer establishment message, sending the first message.

32. The method according to claim 31, wherein The method further includes: Determining that the access network device communicates in the NB-IoT mode; and / or, Determining that the media dedicated bearer is a bearer communicating in the NB-IoT mode.

33. The method according to claim 30, wherein, Before sending the first message, the method further includes: receiving a second message from a UE or a core network device, where the second message is used to indicate the start of media service transmission; Sending a first message, including: based on the second message, sending the first message.

34. The method according to claim 33, wherein The method further includes: Determining that the access network device communicates in the NB-IoT mode; and / or, Determining that the media service is a service transmitted in the NB-IoT mode.

35. The method according to any one of claims 26 to 34, characterized in that The packet header is a ROHC header.

36. A communication method, characterized in that, The method includes: Receiving a first data packet, where the first data packet includes the payloads of N data packets and includes the first packet header among the N data packets, and the first packet header is determined according to the packet headers of some or all of the N data packets, and N is an integer greater than or equal to 2; Determining the packet headers of the N data packets according to the first packet header; restoring the first data packet to the N data packets.

37. The method according to claim 36, wherein The first packet header is determined according to the packet header of the second data packet among the N data packets, and the second data packet is the first or the last data packet to be transmitted among the N data packets.

38. The method according to claim 36 or 37, characterized in that, The N data packets are all the data packets corresponding to the first service, or are partial data packets corresponding to the first service.

39. The method according to any one of claims 36 to 38, characterized in that The sum of the lengths of the payloads of the N data packets is less than or equal to the upper limit of the data packet length.

40. The method according to any one of claims 36 to 39, characterized in that The method further includes: Sending or receiving capability information, where the capability information is used to indicate support for combining the payloads of data packets during transmission.

41. The method according to any one of claims 36 to 40, characterized in that, The method further includes: Sending or receiving a first message, where the first message is used to indicate activation of the function of combining the payloads of data packets during transmission.

42. The method according to claim 41, wherein The method further includes: Receiving a bearer establishment message from a core network device, where the bearer establishment message is used to establish a media dedicated bearer; Sending a first message, including: sending the first message based on the bearer establishment message.

43. The method according to claim 42, wherein The method further includes: Determining that the access network device communicates in the NB-IoT mode; and / or, Determining that the media dedicated bearer is a bearer that communicates in the NB-IoT mode.

44. The method according to claim 41, wherein, The method further includes: Receiving a second message from a UE or a core network device, where the second message is used to indicate the start of transmitting a media service; Sending a first message, including: sending the first message based on the second message.

45. The method according to claim 44, wherein The method further includes: Determining that the access network device communicates in the NB-IoT mode; and / or, Determining that the media service is a service transmitted in the NB-IoT mode.

46. The method according to any one of claims 36 to 45, characterized in that, The first packet header is a ROHC header.

47. A communication device, characterized in that, The communication device includes a processing unit and a transceiver unit, and the processing unit is coupled to the transceiver unit to execute the method according to any one of claims 1 to 6, or execute the method according to any one of claims 7 to 13, or execute the method according to any one of claims 14 to 19, or execute the method according to any one of claims 20 to 25, or execute the method according to any one of claims 26 to 35, or execute the method according to any one of claims 36 to 46.

48. A communication device, characterized in that, The communication device includes a processor coupled to a memory, the memory is used to store a computer program, and the processor is used to execute the computer program stored on the memory, so that the communication device executes the method according to any one of claims 1 to 6, or so that the communication device executes the method according to any one of claims 7 to 13, or so that the communication device executes the method according to any one of claims 14 to 19, or so that the communication device executes the method according to any one of claims 20 to 25, or so that the communication device executes the method according to any one of claims 26 to 35, or so that the communication device executes the method according to any one of claims 36 to 46.

49. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when run on a computer, causes the computer to execute the method according to any one of claims 1 to 6, or causes the computer to execute the method according to any one of claims 7 to 13, or causes the computer to execute the method according to any one of claims 14 to 19, or causes the computer to execute the method according to any one of claims 20 to 25, or causes the computer to execute the method according to any one of claims 26 to 35, or causes the computer to execute the method according to any one of claims 36 to 46.

50. A computer program product, characterized in that, The computer program product includes a computer program, which, when run on a computer, causes the computer to execute the method according to any one of claims 1 to 6, or causes the computer to execute the method according to any one of claims 7 to 13, or causes the computer to execute the method according to any one of claims 14 to 19, or causes the computer to execute the method according to any one of claims 20 to 25, or causes the computer to execute the method according to any one of claims 26 to 35, or causes the computer to execute the method according to any one of claims 36 to 46.

51. A chip, characterized in that, The chip includes: a processor and an interface, the processor is used to call and run instructions from the interface, and when the processor executes the instructions, it implements the method according to any one of claims 1 to 6, or implements the method according to any one of claims 7 to 13, or implements the method according to any one of claims 14 to 19, or implements the method according to any one of claims 20 to 25, or implements the method according to any one of claims 26 to 35, or implements the method according to any one of claims 36 to 46.

Citation Information

Patent Citations

  • Data transmission processing method, device and system

    CN102377650A

  • Method and device for transmitting / receiving broadcast signal

    CN105659612A

  • Method and apparatus for reducing overhead of ethernet frame in next generation mobile communication system

    CN112970235A

  • Method and device for processing general packet radio service (GPRS) tunnel protocol (GTP) packets

    CN113518386A

  • Protocol overhead reduction for packet data convergence protocol

    US20230291816A1