A communication method and apparatus

Abstract

A communication method and apparatus are disclosed. The method includes: enabling header compression functionality of a terminal device and / or a User Plane Function (UPF) network element using an SMF network element; and sending instruction information for the header compression functionality to the terminal device and / or the UPF network element. Using the method and apparatus of this application, packet header compression can be achieved, thereby improving transmission efficiency.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] To address the challenges of wireless broadband technology, and to maintain the 3rd Generation Partnership Project (3GPP) rd Leveraging the leading advantages of the Generation Partnership Project (3GPP) network, the 3GPP standards group formulated the next-generation mobile communication network architecture, known as the 5G network architecture, at the end of 2016. This architecture not only supports radio technologies defined by the 3GPP standards group for accessing the core network (3GPP access), but also supports non-3GPP access technologies for accessing the core network through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG), known as non-3GPP access. For example, 3GPP access can include Long Term Evolution (LTE) and New Radio (NR). Non-3GPP access can include Wireless Fidelity (Wi-Fi) access or fixed-line access. Under the existing network architecture, how to compress the packet header to improve transmission efficiency is the technical problem to be solved in the embodiments of this application. Summary of the Invention

[0003] This application provides a communication method and apparatus for compressing the header of data packets to improve transmission efficiency.

[0004] In a first aspect, a communication method is provided, comprising: a Session Management Function (SMF) network element enabling header compression functionality of a terminal device and / or a User Plane Function (UPF) network element; the SMF network element sending instruction information for the header compression functionality to the terminal device and / or the UPF network element.

[0005] Through the above design, the SMF network element can enable the header compression function of the terminal device and / or UPF network element, and send the header compression function indication information to the terminal device and / or UPF network element, thereby enabling the UE and / or UPF network element to enable their respective header compression functions and improve the data packet compression rate.

[0006] In one possible design, the SMF network element further includes: the SMF network element receiving a first message from the terminal device, the first message including indication information of a first header compression capability, the first header compression capability being used to indicate that the terminal device supports header compression functionality; the SMF network element enabling the header compression functionality of the terminal device and / or the User Plane Function (UPF) network element, including: the SMF network element enabling the header compression functionality of the terminal device and / or the UPF network element based on the first header compression capability and / or the Multi-Link Fast User Datagram Protocol (MPQUIC) offloading function.

[0007] In one possible design, the first message may also include the first header compression configuration parameters of the terminal device.

[0008] In one possible design, the SMF network element further includes sending a second message to the policy control function PCF network element. The second message includes indication information of a second header compression capability, which indicates that both the terminal device and the UPF network element support header compression capability.

[0009] In one possible design, the SMF network element further includes: receiving a third message from the PCF network element, the third message including service flow information and header compression function indication information; the SMF network element determining, based on the header compression function indication information, to enable header compression function for the data packet corresponding to the service flow information; or, the third message including service flow information and MPQUIC splitting function indication information; the SMF network element determining, based on the MPQUIC splitting function indication information, to enable header compression function for the data packet corresponding to the service flow information.

[0010] In one possible design, the SMF network element sends the header compression function indication information to the UPF network element, including: the SMF network element sends a fourth message to the UPF network element, the fourth message including service flow information and header compression function indication information.

[0011] In one possible design, the fourth message further includes: a second header compression configuration parameter, wherein the second header compression configuration parameter is allocated by the SMF network element to the UPF network element, or the second header compression configuration parameter is determined by the SMF network element based on the first header compression configuration parameter of the terminal device, or the second header compression configuration parameter is the first header compression configuration parameter of the terminal device forwarded by the SMF network element.

[0012] In one possible design, the SMF network element also includes: the SMF network element receiving a fifth message from the UPF network element, the fifth message including a third header compression configuration parameter, the third header compression configuration parameter being the header compression configuration parameter of the UPF network element.

[0013] In one possible design, the SMF network element sends header compression function indication information to the terminal device, including: the SMF network element sends a sixth message to the terminal device, the sixth message including service flow information and header compression function indication information.

[0014] In one possible design, the header compression capability includes packet inner protocol header compression capability, the header compression function includes packet inner protocol header compression function, the packet inner protocol header compression includes at least one of Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header compression; and / or, the header compression capability includes packet outer protocol header compression capability, the header compression function includes packet outer protocol header compression function, the packet outer protocol header compression includes at least one of IP header or UDP header header compression.

[0015] The above design allows for compression of either the inner or outer protocol header of a data packet, or both simultaneously. Compression of both headers can further improve data transmission efficiency.

[0016] In one possible design, the method further includes: the SMF network element sending a seventh message to the access network device, the seventh message including indication information to disable the compression function of the IP header and / or UDP header, for instructing the access network device to no longer perform header compression processing of the IP header and / or UDP header on data packets.

[0017] In one possible design, the method further includes: the SMF network element sending indication information of a first access mode to the terminal device and / or the UPF network element, for instructing the terminal device and / or the UPF network element to enable header compression function for data packets transmitted in the link corresponding to the first access mode.

[0018] In this embodiment of the application, the outer protocols encapsulated for different access methods are not the same. For example... Figure 3As shown, for example, for a UE, 3GPP access methods are encapsulated using the IP@1 protocol, while non-3GPP access methods are encapsulated using the IP@2 protocol. For a UPF network element, 3GPP access methods are encapsulated using the IP@4 protocol, while non-3GPP access methods are encapsulated using the IP@3 protocol. Therefore, in this embodiment, the SMF network element needs to notify the UE and the UPF network element of the corresponding access method so that the terminal device and the UPF network element know which access method's corresponding protocol should be compressed in the header.

[0019] In a second aspect, a communication method is provided, comprising: a terminal device receiving instruction information for header compression function from a Session Management Function (SMF) network element; the terminal device enabling header compression function according to the instruction information for header compression function.

[0020] Through the above design, the terminal device can enable the header compression function according to the instructions of the SMF network element, thereby improving the data packet transmission efficiency.

[0021] In one possible design, the terminal device further includes sending a first message to the SMF network element, the first message including indication information of a first header compression capability, the first header compression capability being used to indicate that the terminal device supports header compression functionality.

[0022] In one possible design, the first message may also include the first header compression configuration parameters of the terminal device.

[0023] In one possible design, the terminal device receives header compression function indication information from the SMF network element, including: the terminal device receives a sixth message from the SMF network element, the sixth message including service flow information and header compression function indication information; the terminal device enables the header compression function according to the header compression function indication information, including: the terminal device enables the header compression function of the data packet corresponding to the service flow information according to the service flow information and the header compression function indication information.

[0024] In one possible design, the first header compression capability includes packet inner protocol header compression capability, the header compression function includes packet inner protocol header compression function, the packet inner protocol header compression includes at least one of Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header compression; and / or, the first header compression capability includes packet outer protocol header compression capability, the header compression function includes packet outer protocol header compression function, the packet outer protocol header compression includes at least one of IP header or UDP header header compression.

[0025] In one possible design, the method further includes: the terminal device receiving indication information of a first access method from the SMF network element; and the terminal device enabling header compression for data packets transmitted in the link corresponding to the first access method.

[0026] In one possible design, the method further includes: the terminal device receiving a data packet containing a complete header corresponding to the service flow information from the UPF network element; the terminal device generating a first decompressed file based on the data packet with the complete header; and the terminal device storing the correspondence between the first decompressed file and the service flow information.

[0027] Thirdly, a communication method is provided, comprising: a User Plane Function (UPF) network element receiving instruction information for header compression function from a Session Management Function (SMF) network element; the UPF network element enabling header compression function according to the instruction information for header compression function.

[0028] Through the above design, the UPF network element can enable header compression capability according to the instructions of the SMF network element, thereby improving data transmission efficiency.

[0029] In one possible design, the UPF network element receives header compression function indication information from the SMF network element, including: the UPF network element receiving a fourth message from the SMF network element, the fourth message including the service flow information and header compression function indication information; the UPF network element enabling the header compression function according to the header compression function indication information, including: the UPF network element enabling the header compression function of the data packet corresponding to the service flow information according to the service flow information and the header compression function indication information.

[0030] In one possible design, the fourth message further includes: a second header compression configuration parameter, wherein the second header compression configuration parameter is allocated by the SMF network element to the UPF network element, or the second header compression configuration parameter is determined by the SMF network element based on the first header compression configuration parameter of the terminal device, or the second header compression configuration parameter is the first header compression configuration parameter of the terminal device forwarded by the SMF network element.

[0031] In one possible design, the UPF network element further includes sending a fifth message to the SMF network element, the fifth message including the second header compression configuration parameter, which is the header compression configuration parameter of the UPF network element.

[0032] In one possible design, the header compression function includes inner packet protocol header compression, which includes compression of at least one of the Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header; and / or, the header compression function includes outer packet protocol header compression, which includes compression of at least one of the IP header or UDP header.

[0033] In one possible design, the method further includes: the UPF network element receiving indication information of a first access mode from the SMF network element; and the UPF network element enabling header compression for data packets transmitted in the link corresponding to the first access mode.

[0034] In one possible design, the UPF network element further includes: receiving a data packet containing a complete header corresponding to the service flow information from the terminal device; generating a second decompressed file based on the data packet with the complete header; and storing the correspondence between the second decompressed file and the service flow information.

[0035] Fourthly, a communication method is provided, comprising: a first device sending a first message to a second device, the first message including indication information for stopping or activating a header compression function; the first device receiving a second message from the second device, the second message being a response message to the first message.

[0036] With the above design, when the network condition is poor or other reasons lead to a high packet loss rate, the first device and the second device can perform tasks such as decompressing, pausing, or restarting the data packet header.

[0037] In one possible design, the first message also includes service flow information, and the first device stops or activates the header compression function of the data packet corresponding to the service flow information.

[0038] In one possible design, the second message includes an indication that the second device has successfully stopped or activated the header compression function, or an indication that the second device has failed to stop or activate the header compression function.

[0039] In one possible design, the first device determines whether to stop or activate the header compression function based on at least one of link state, internal state, or local policy.

[0040] Fifthly, a communication method is provided, comprising: a second device receiving a first message from a first device, the first message including indication information for stopping or activating a header compression function; the second device sending a second message to the first device, the second message being a response message to the first message.

[0041] With the above design, when the network condition is poor or other reasons lead to a high packet loss rate, the first device and the second device can perform tasks such as decompressing, pausing, or restarting the data packet header.

[0042] In one possible design, the first message also includes service flow information, and the second device stops or activates the header compression function of the data packet corresponding to the service flow information.

[0043] In one possible design, the second message includes an indication that the second device has successfully stopped or activated the header compression function, or an indication that the second device has failed to stop or activate the header compression function.

[0044] A sixth aspect provides a communication method, comprising: a first device sending a first message to a second device, the first message including indication information of a complete header request; the first device receiving a second message from the second device, the second message being a response message to the first message.

[0045] With the above design, if the decompressed packet is lost or expired, in order to reduce the impact of data packet decompression failure, the first or second device can notify the other end to immediately send the complete data packet header so that the decompressed file can be regenerated or updated.

[0046] In one possible design, the first message may further include at least one of service flow information or decompression file identifier. The first device receives a data packet carrying a complete header corresponding to the service flow from the second device. The first device generates or updates the decompression file corresponding to the service flow based on the data packet carrying the complete header.

[0047] In one possible design, the second message includes an indication that the second device agrees to or rejects the first device's full header request.

[0048] In one possible design, when the first device determines that the decompressed file is unavailable, it performs the step of sending a first message from the first device to the second device.

[0049] A seventh aspect provides a communication method, comprising: a second device receiving a first message from a first device, the first message including indication information of a complete header request; the second device sending a second message to the first device, the second message being a response message to the first message.

[0050] With the above design, if the decompressed packet is lost or expired, in order to reduce the impact of data packet decompression failure, the first or second device can notify the other end to immediately send the complete data packet header so that the decompressed file can be regenerated or updated.

[0051] In one possible design, the first message may also include at least one of service flow information or decompressed file identifier, and the second device may send a data packet with a complete header corresponding to the service flow to the first device.

[0052] In one possible design, the second message includes an indication that the second device agrees to or rejects the first device's full header request.

[0053] Eighthly, a communication apparatus is provided, the apparatus comprising units for implementing the method of any one of the first to seventh aspects described above.

[0054] A ninth aspect provides a communication device including a processor and a memory, the processor and the memory being coupled, the processor being configured to implement the method of any one of the first to seventh aspects.

[0055] In a tenth aspect, a communication apparatus is provided, comprising a processor and a communication interface, wherein the processor utilizes the communication interface to implement the method of any one of the first to seventh aspects.

[0056] Eleventhly, a computer-readable storage medium is provided, the computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method of any one of the first to seventh aspects.

[0057] In a twelfth aspect, a chip system is provided, comprising a processor and potentially a memory, for implementing the methods of any one of the first to seventh aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0058] In a thirteenth aspect, a computer program product is provided, including instructions that, when executed on a computer, cause the computer to perform the methods of any one of the first to seventh aspects. Attached Figure Description

[0059] Figure 1 This is a schematic diagram of the network architecture provided in the embodiments of this application;

[0060] Figure 2 A schematic diagram of a multi-access PDU session provided in an embodiment of this application;

[0061] Figure 3 A schematic diagram of the MPQUIC protocol stack provided in an embodiment of this application;

[0062] Figure 4 , Figure 5 and Figure 6 A flowchart provided for Embodiment 1 of this application;

[0063] Figure 7 and Figure 8 A flowchart provided for Embodiment 2 of this application;

[0064] Figure 9 and Figure 10 A flowchart provided for Embodiment 3 of this application;

[0065] Figure 11 A schematic diagram of the apparatus provided in an embodiment of this application;

[0066] Figure 12 Another schematic diagram of the apparatus provided in an embodiment of this application. Detailed Implementation

[0067] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0068] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0069] like Figure 1 As shown, a network architecture is provided, which includes at least one of the following:

[0070] 1. Terminal equipment

[0071] A terminal device, often simply referred to as a terminal, is a device with wireless transceiver capabilities. Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water (such as on ships); and in the air (such as on airplanes, balloons, and satellites). These terminal devices can include mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, self-driving, remote medical, smart grid, transportation safety, smart city, and smart home applications, and may also include user equipment (UE). Terminal equipment can also be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal equipment in future 5G networks, or terminal equipment in future evolved public land mobile networks (PLMNs), etc. Terminal equipment may also be referred to as terminal equipment, user equipment (UE), access terminal equipment, in-vehicle terminal equipment, industrial control terminal equipment, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent, or UE device, etc. Terminal equipment can be fixed or mobile. This application embodiment does not limit this. By way of example and not limitation, in this application embodiment, the terminal equipment can be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday clothing, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories.Wearable devices are not merely hardware devices, but also devices that achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large sizes, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those focused on a specific application function that require interaction with other devices like smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring. In this application, the terminal device can be a terminal in an Internet of Things (IoT) system. IoT is an important component of future information technology development, its main technical characteristic being the connection of objects to networks via communication technology, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection. The terminal device in this application can be a terminal device in machine-type communication (MTC). The terminal device in this application can be an onboard module, onboard component, onboard chip, or onboard unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in onboard module, onboard component, onboard chip, or onboard unit. Therefore, the embodiments of this application can be applied to the Internet of Vehicles, such as vehicle-to-everything (V2X), long-term evolution vehicle (LTE-V) communication technology, vehicle-to-vehicle (V2V) communication, etc.

[0072] 2. Access Network

[0073] The access network is used to implement functions related to radio access, and access network equipment is equipment that provides access for terminal equipment. Access network equipment includes radio access network (RAN) equipment and / or access network (AN) equipment. RAN equipment can be access network equipment defined in the 3rd Generation Partnership Project (3GPP). AN equipment can be access network equipment not defined by 3GPP.

[0074] RAN equipment is primarily responsible for radio resource management, quality of service (QoS) management, data compression, and security processing on the air interface side. RAN equipment can include various types of base stations, such as macro base stations, micro base stations (small cells), relay stations, or access points. RAN equipment includes, but is not limited to, the following in 5G: next-generation node B (gNB), evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved node B, or home node B, HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), and mobile switching center. RAN equipment can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario, or RAN equipment can be a relay station, access point, vehicle-mounted equipment, terminal equipment, wearable devices, and access network equipment in future 6G networks or access network equipment in future evolved public land mobile network (PLMN) networks, etc.

[0075] An AN device is used to enable interconnection between terminal devices and the 3GPP core network using non-3GPP technologies. These non-3GPP technologies include, but are not limited to: Wireless Fidelity (WIFI), Worldwide Interoperability for Microwave Access (WiMAX), and Code Division Multiple Access (CDMA) network technologies.

[0076] 3. Core Network

[0077] Core network equipment may include one or more of the following network elements: access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, application function (AF) network element, unified data management (UDM) network element, authentication server function (AUSF) network element, and network slice selection function (NSSF) network element.

[0078] AMF (Automatic Mobility Management) elements: Primarily responsible for mobility management in mobile networks, such as user location updates, user registration with the network, and user handover. SMF (Signal Management) elements: Primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting UPF (User-Defined Provider) elements to provide packet forwarding. UPF (User-Defined Provider) elements: Primarily responsible for forwarding and receiving user data. In downlink transmission, UPF elements can receive user data from the data network (DN) and transmit it to the terminal device through the access network equipment; in uplink transmission, UPF elements can receive user data from the terminal device through the access network equipment and forward the user data to the DN. Optionally, the transmission resources and scheduling functions provided by the UPF elements to the terminal device can be managed and controlled by the SMF elements. PCF (Programmable Component Function) elements: Primarily support providing a unified policy framework to control network behavior, providing policy rules to control layer network functions, and acquiring user subscription information related to policy decisions. AF (Automatic Component Function) elements: Primarily support interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. UDM network elements are primarily used for generating authentication credentials, user identification processing (such as storing and managing permanent user identities), access authorization control, and subscription data management. AUSF network elements are primarily used to perform authentication when terminal devices access the network, including receiving authentication requests from the security anchor function (SEAF), selecting authentication methods, and requesting authentication vectors from the authentication repository and processing function (ARPF). NSSF network elements are primarily used to select network slice instances for terminal devices, determine allowed network slice selection assistance information (NSSAI), configure NSSAI, and determine the AMF set for the serving UE.

[0079] 4. DN

[0080] A Data Network (DN) can be a service network that provides data services to users. For example, a DN can be an IP multimedia service network or the Internet. Terminal devices can establish a Protocol Data Unit (PDU) session with the DN to access it.

[0081] It should be noted that the network elements in the core network described above may have different names in different communication systems. Figure 1The schematic diagram shown is illustrated using a fifth-generation mobile communication system as an example and is not intended to limit this application. Furthermore, the above... Figure 1 The core network elements shown are for illustrative purposes only and are not intended to limit the embodiments of this application. For example, in Figure 1 In the network architecture shown, the core network elements may also include one or more of the following: network exposure function (NEF), network repository function (NRF), or service control point (SCP).

[0082] Through the above Figure 1 As described, a UE can access the core network using either 3GPP or non-3GPP access technologies. In one design, multiple access technologies can be supported for a single PDU session. For example... Figure 2 As shown, PDU session A can access the network via either a first access method or a second access method. This PDU session is referred to as a multi-access PDU session. In this embodiment, the first and second access methods are not limited. For example, the first and second access methods can be any of the following, and the first and second access methods are different: Any of the following access technologies include: 3GPP access, non-3GPP access, LTE access, 5G NR access, trusted non-3GPP access, untrusted non-3GPP access, WLAN access, or fixed network access, etc. A multi-access PDU session can enable the movement or concurrency of service flows between different access technologies. For example, service flow 1 is transmitted through access technology 1, and subsequently, service flow 1 moves to be transmitted through access technology 2. Alternatively, the data packets of the service flow can be transmitted simultaneously using access technology 1 and access technology 2 to expand bandwidth.

[0083] To achieve the traffic splitting function in the aforementioned multi-access PDU session, a new multi-path Fast User Datagram Protocol (UDP) connection can be established between the UE and the UPF. In one design, the protocol stack for the MPQUIC connection can be found [link to relevant documentation]. Figure 3 As shown. In accordance with Figure 3 When the MPQUIC protocol stack shown encapsulates data packets, the payload or net payload can be configured according to... Figure 3The MPQUIC protocol stack shown is encapsulated, and the payload or payload can refer to the data portion transmitted by the user. Figure 3 As can be seen, the encapsulation process first involves UE IP@0 and UDP / TCP protocols, which can be referred to as inner encapsulation in this embodiment. The inner UE IP@0 is the UE IP address assigned to the UE by the SMF or UPF, used as the source IP address for uplink data packets, and the destination IP is the server IP address of the server corresponding to the service flow. Afterwards, it undergoes encapsulation at the UDP, UEIP@1, or UE IP@2 layer, which can be referred to as outer encapsulation in this embodiment. The outer UE IP@1 or UE IP@2 is the UE IP address assigned to the UE by the UPF and bound to the access technology. For example, taking uplink service flows as an example, UE IP@1 is bound to the 3GPP access side, meaning that when uplink data packets are transmitted through 3GPP, UE IP@1 is used as the source IP address. UE@2 is bound to non3GPP, meaning that when uplink data packets are transmitted through non3GPP, UE IP@2 is used as the source IP address. The destination IP of the outer layer is the IP address of the UPF, specifically the UPF IP address corresponding to the MPQUIC function on the UPF. In addition to the above, another option for outer IP encapsulation is that the UE-side UE IP address is independent of the access technology, meaning there is only one UE IP address. This UE IP address is still assigned by the UPF and is applicable to both 3GPP and non-3GPP access. However, the UPF's MPQUIC function has two IP addresses, corresponding to 3GPP and non-3GPP access respectively. For example, taking uplink traffic as an example, UPF IP@1 corresponds to 3GPP access. Therefore, when uplink data packets are transmitted via 3GPP, the source address is the UE IP, and the destination IP is UPF IP@1. UPF IP@2 corresponds to non-3GPP access. When uplink data packets are transmitted via non-3GPP, the source address is still the UE IP, and the destination IP is UPF IP@2. Based on the above encapsulation methods, it can be seen that after the user's actual data packets are encapsulated in the inner layer, they still need to undergo outer encapsulation, which may lead to excessively large packet headers and affect transmission efficiency.

[0084] First, let's clarify a concept: a data packet can consist of a header and a payload. The payload can be the actual data transmitted by the user, while the header can be considered as some control information that assists in the transmission of the data packet, such as the source address and destination address. In this embodiment, when a data packet uses... Figure 3As shown in the MPQUIC protocol stack encapsulation diagram, each encapsulation layer generates a corresponding header. For example, encapsulation at the IP layer generates an IP header, and encapsulation at the UDP layer generates a UDP header. To address the issue of protocol stack duplication in MPQUIC inner and outer encapsulation (e.g., the IP layer might undergo two encapsulations, generating two IP headers, leading to excessively large packet headers and low transmission efficiency), this application provides a solution that compresses packet headers. This compression can refer to eliminating full header encapsulation for each packet. When a packet contains complete header information, it can be called fully header-encapsulated data, or simply full header data. When a packet contains only part of the full header information, i.e., when compressed header encapsulation is used, it can be called a compressed packet. For example, with 10 packets as a group, only the first packet in each group can be transmitted with a full header. Subsequently, the packet headers are compressed, meaning the compressed packets can reduce the length of the inner and / or outer IP header, UDP header, or TCP header. Subsequently, the receiving end obtains a decompressed file based on the header of the first data packet. This decompressed file stores relevant information contained in the full header, such as source / destination IP addresses and source / destination port numbers. The decompressed file can also be called a data packet header information file or a restored header file; this patent does not restrict the file name. Based on the decompressed file, the receiving end restores the full header information of subsequently received compressed data packets, that is, recovers the missing header information from the compressed packet; this is called the decompression process. This application's embodiments focus on how the SMF network element enables header compression functionality for both the UE and UPF network elements.

[0085] This application provides a communication method, which includes: an SMF network element enabling header compression functionality of a UE and / or a UPF network element, where enabling includes meanings such as activation or startup. The SMF network element sends indication information for the header compression functionality to the UE and the UPF network element.

[0086] Example 1

[0087] like Figure 4 As shown, a communication method flow includes at least the following:

[0088] Step 400: The UE sends a first message to the SMF, which includes an indication of a first header compression capability, indicating that the UE supports header compression functionality. Alternatively, the UE sends a non-access stratum (NAS) transmission message to the AMF, which includes the first message and the first header compression capability indication. The AMF forwards the first message and the first header compression capability indication to the SMF.

[0089] In one design, the UE can initiate a PDU session establishment or update procedure, where the first message is a PDU session establishment or update request message. This PDU session establishment or update request message may include indication information of the first header compression capability, which the SMF network element can obtain from the PDU session establishment or update request message. Alternatively, the NAS transmission message may include the indication information of the first header compression capability, which the AMF obtains from the NAS transmission message, and the AMF forwards the first header compression capability indication information to the SMF. The indication information of the first header compression capability can be explained as follows:

[0090] First, the aforementioned indication information for the first header compression capability can be an indication of whether the UE supports header compression functionality. For example, an indication including the first header compression capability indicates that header compression capability is supported, while an indication not including the first header compression capability indicates that header compression capability is not supported. Alternatively, for example, setting the indication information for the first header compression capability to 0 indicates that the UE does not support header compression functionality, and setting it to 1 indicates that the UE supports header compression functionality, etc.

[0091] Second, the indication information for the first header compression capability mentioned above can be an indication of the specific header compression function supported by the UE. For example, according to the description of the MPQUIC protocol above, the inner header includes IP header, UDP header, or TCP header, etc. The indication information for the first header compression capability mentioned above can specifically be an indication of at least one of the header compression functions in the IP header, UDP header, or TCP header, etc. The outer header includes IP header and UDP header, etc., and the indication information for the first header compression capability mentioned above can specifically be an indication of at least one of the header compression functions in the IP header or UDP header, etc.

[0092] Third, the aforementioned indication information regarding the first header compression capability can be an indication information for the MPQUIC splitting function. For example, header compression is required for data packets using the MPQUIC splitting function. The indication information for the MPQUIC splitting function can not only indicate that the data is split using MPQUIC, but also indicate that header compression is performed on data packets split using MPQUIC.

[0093] Alternatively, in another implementation, the UE's first header compression capability can be implicitly indicated through the UE's first header compression configuration parameters. That is, the first message mentioned above may include the UE's first header compression configuration parameters, which implicitly indicate the UE's first header compression capability. Alternatively, the first message mentioned above may simultaneously include indication information of the first header compression capability and the first header compression configuration parameters. In other words, the first message mentioned above may include the UE's first header compression configuration parameters in addition to the indication information of the first header compression capability. For example, the first header compression configuration parameters are used to represent the relevant configuration parameters when the UE implements header compression, and may include at least one of the following: maximum compressed header length (MAX-header), maximum number of header compression connections (i.e., the maximum number of traffic flows that can be compressed simultaneously), maximum time interval (used to represent the maximum interval between transmitting two data packets carrying complete headers), or maximum number of data packet intervals (used to represent the number of compressed packets between transmitting two data packets carrying complete headers), etc. Of course, the first header compression configuration parameters may include other parameters besides those described above; please refer to the description in RFC2507 for details.

[0094] Step 401: Enable header compression function of UE and / or UPF network element in SMF network element.

[0095] In one design, the SMF network element can enable header compression functionality for the UE and / or UPF network element based on a first header compression capability. For example, if the first header compression capability is that the UE supports compression of both IP and UDP headers, the SMF network element can activate or enable IP and UDP header compression for both the UE and / or UPF network element. Alternatively, the SMF network element can consider both the UE's and UPF network element's header compression capabilities, combining both to enable header compression functionality for both the UE and / or UPF network element. For example, if the UE supports IP header compression, and the UPF network element supports compression of IP, UDP, and TCP headers, the SMF network element can enable IP header compression for both the UE and UPF network element. The UPF network element's header compression capability can be reported to the SMF network element during deployment, or indicated to the SMF network element via NRF, etc. That is, the UPF or NRF sends a message to the SMF containing UPF header compression capability indication information. The definition of the head compression capability indication information of the above UPF is the same as that of the first head compression capability indication information.

[0096] Regarding enabling header compression functionality for the UE and / or UPF network element by the SMF network element, the following explanation is provided: Since the UPF network element actually supports a comprehensive range of header compression functions, under normal circumstances, the SMF network element can only consider the first header compression capability supported by the UE and enable the header compression function for the UE and / or UPF network element. Alternatively, even if the UPF network element cannot support all header compression functions, the SMF network element can select the UPF network element that supports the corresponding function based on the first header compression capability supported by the UE.

[0097] In another design, the SMF network element can enable header compression for the UE and / or UPF network element based on the MPQUIC traffic offloading function. The process by which the SMF network element determines the MPQUIC traffic offloading function can be as follows: The SMF network element sends a policy request message to the PCF network element. The SMF network element receives a policy response message from the PCF network element, which includes service flow information and indication information for the MPQUIC traffic offloading function. Based on the service flow information and the MPQUIC traffic offloading function indication information, the SMF network element can determine whether to encapsulate the data packets corresponding to the aforementioned service flow information using the MPQUIC protocol. As described above regarding the MPQUIC protocol encapsulation method, this method suffers from inner and outer header encapsulation issues. When the SMF network element receives the service flow information and the MPQUIC traffic offloading function indication information, it can directly determine to perform header compression on the data packets corresponding to the aforementioned service flow information.

[0098] In another design, the SMF network element can enable the header compression function of the UE and / or UPF network element based on the MPQUIC traffic splitting function and the first header compression capability. That is, when the SMF receives the first header compression capability and obtains the service flow information and the MPQUIC traffic splitting function indication, it enables the header compression function of the UE and / or UPF network element for the aforementioned service flow data packets.

[0099] Step 402: The SMF network element sends a second message to the PCF network element. This second message can be a policy request message, which includes indication information of a second header compression capability. This second header compression capability can be a header compression capability supported by both the UE and the UPF network element. Alternatively, the second header compression capability indication information can be used to indicate that both the UE and the UPF network element support header compression functionality.

[0100] Step 403: The SMF network element receives a third message from the PCF network element. This third message can be a policy reply message, which includes service flow information and header compression function indication information. The SMF network element can determine whether to enable header compression function for the data packet corresponding to the service flow information based on the header compression function indication information. Alternatively, the third message may include service flow information and MPQUIC traffic splitting function indication information. The SMF network element can determine whether to enable header compression function for the data packet corresponding to the service flow information based on the MPQUIC traffic splitting function indication information. The service flow information may include at least one of the following:

[0101] • One or more service flow descriptions, such as at least one of the service flow 5-tuple information (including source / destination IP address, source / destination port number, or protocol number), used to indicate that a header compression mechanism is used for certain service flows.

[0102] • One or more connection information, such as the MPQUIC connection identifier, are used to indicate that all service flows in the MPQUIC connection use header compression.

[0103] • Packet forwarding control protocol (PFCP) session identifier, used to indicate that all traffic flows in the PFCP session that are split based on the MPQUIC splitting function use the header compression mechanism.

[0104] • One or more Quality of Service Flow Indicators (QFIs) indicate that all service flows using the MPQUIC splitting function in the QFI-corresponding Quality of Service (QoS) flow employ header compression.

[0105] • One or more MPQUIC stream identifiers (stream IDs, etc.)

[0106] In one design, the PCF network element can send service flow information and header compression function indication information to the SMF network element. Specifically, the PCF network element determines whether to enable the header compression function based on at least one of the following: an indication of second header compression capability, a local policy, or the MPQUIC traffic splitting function corresponding to the service flow, and then sends the header compression function indication information to the SMF network element. In this embodiment, the local policy is not limited. For example, the local policy may include initiating the header compression mechanism for services that are insensitive to packet loss rate, latency, or high bandwidth.

[0107] Steps 402 and 403 above can be optional.

[0108] Step 404: The SMF network element sends an instruction message for header compression function to the UE and / or UPF network element.

[0109] In one design, the header compression indication information can instruct the UE and / or UPF network element whether to enable or activate the header compression function. For example, if the UE and / or UPF network element receives an indication for header compression, it indicates that the header compression function is activated or enabled. If the UE and / or UPF network element does not receive an indication for header compression, it indicates that the header compression function is not activated or enabled. Alternatively, for example, setting the header compression indication information to 1 indicates that the UE and / or UPF network element enables or activates the header compression function, and setting the header compression indication information to 0 indicates that the UE and / or UPF network element does not enable or activate the header compression function. The specific protocol types (e.g., IP header compression, UDP header compression, or TCP header compression) that are enabled or activated can be specified by the protocol or pre-configured to the UE and / or UPF, etc., and is not limited. In another design, the header compression indication information can instruct the UE and / or UPF to specifically enable or activate header compression for which protocol headers. Continuing with the above example, the inner packet header includes IP header, UDP header, and TCP header, etc. The SMF network element can specifically instruct the UE and / or UPF network element to enable or activate header compression for at least one of the IP header, UDP header, or TCP header. Alternatively, in another design, the instruction information for the above header compression function can be an instruction for the MPQUIC offloading function. When the UE and / or UPF network element receives the above instruction information for the MPQUIC offloading function, it indicates that the MPQUIC offloading protocol is used to encapsulate the data packet and compress the data packet header.

[0110] In one possible implementation, the process of the SMF network element sending header compression indication information to the UPF network element may include: the SMF network element sending a fourth message to the UPF network element, which may be a PFCP session establishment or update request message, including service flow information and header compression indication information. Optionally, the fourth message may also include a second header compression configuration parameter, which may be allocated by the SMF network element to the UPF network element, or determined by the SMF network element based on the UE's first header compression configuration parameter, or forwarded by the SMF network element from the UE's first header compression configuration parameter. The SMF network element may receive a fifth message from the UPF network element, which may be a PFCP session establishment or update reply message, including a third header compression configuration parameter, which may be the UPF network element's header compression configuration parameter. Correspondingly, the UPF network element may enable header compression for the data packets corresponding to the service flow information based on the service flow information and the header compression indication information. Optionally, the UPF network element can receive a data packet containing a complete header corresponding to the service flow information from the UE; the UE generates a second decompressed file based on the data packet with the complete header; and the UPF network element stores the correspondence between the second decompressed file and the service flow.

[0111] In one possible implementation, the process of the SMF network element sending header compression instruction information to the UE may include: the SMF network element sending a sixth message to the UE, the sixth message including service flow information and header compression instruction information, the sixth message being a PDU session reply message, etc. Correspondingly, the UE can enable header compression of the data packet corresponding to the service flow information according to the service flow information and header compression instruction information. Optionally, the UE can receive a data packet including a complete header corresponding to the service flow information from the UPF network element; the UE generates a first decompressed file based on the data packet with the complete header; and the UE stores the correspondence between the first decompressed file and the service flow.

[0112] For example, the process of enabling header compression for service flows by the UE and the UPF network element may include: if the service flow information sent by the SMF network element and the header compression function indication information indicate that the service flow includes a first service flow and the header compression function includes IP header compression, then, taking this as an example, the UE can perform IP header compression on the data packets corresponding to the first service flow. The UPF network element can then decompress the IP header of the data packets corresponding to the first service flow using the aforementioned second decompression file.

[0113] It should be pointed out that the above Figure 4The methods in the process can be applied to compress the inner header of a data packet, or to compress the outer header of a data packet, or to compress both the inner and outer headers simultaneously; there are no limitations. If used to compress the inner header of a data packet, then the above... Figure 4 The header compression capability in the process includes the ability to compress the inner protocol header of the data packet. The header compression function includes the compression of the inner protocol header of the data packet, which includes at least one of the following header types: IP header, UDP header, or TCP header. Alternatively, if used to compress the outer header of the data packet, then the above... Figure 4 The header compression capability in the process includes the ability to compress the outer protocol header of data packets. The header compression function includes the compression of the outer protocol header of data packets, and this compression includes at least one of the IP header or UPF header. Optionally, through the above... Figure 3 As can be seen from the MPQUIC protocol description, the outer header compression can differ for different access methods. For example, for 3GPP access, it can be encapsulated according to the IP@1 protocol, with the packet header including the IP@1 header. For non-3GPP access, it can be encapsulated according to the IP@2 protocol, with the packet header including the IP@2 header. Therefore, the above... Figure 4 The illustrated process may further include: the SMF network element sending indication information for the first access method to the UE and / or UPF network element, instructing the UE and / or UPF network element to enable header compression for data packets transmitted in the link corresponding to the first access method. For example, if the first access method is 3GPP access, the UE and / or UPF network element can enable header compression for data packets (IP@1 encapsulated data packets) transmitted in the link corresponding to the 3GPP access technology. Alternatively, if the first access method is non-3GPP access, the UE and / or UPF network element can enable header compression for data packets (IP@2 encapsulated data packets) transmitted in the link corresponding to the non-3GPP access technology. In one design, the outer header compression function can be performed by the access network device. In this embodiment, the outer header compression function is transferred to the UE or UPF for execution. Therefore, the SMF network element can send a seventh message to the access network device. This seventh message includes an indication to disable header compression, such as an indication of IP header and / or UDP header compression, to instruct the access network device to no longer perform IP header and / or UDP header compression on data packets. In this embodiment, the order in which the seventh message is sent with other messages is not limited.

[0114] As can be seen from the above, in the embodiments of this application, the SMF network element can enable the header compression function of the UE and / or UPF network element, and send the header compression function indication information to the UE and / or UPF network element, thereby enabling the UE and / or UPF network element to enable their respective header compression functions and improving the data packet compression efficiency.

[0115] like Figure 5 The diagram illustrates a communication method that can compress the header of the inner protocol layer of data packets, including at least the following:

[0116] Step 501: The UE sends a PDU session request to the SMF network element. This PDU session request includes an indication of the first header compression capability supported by the UE and / or the UE's first header compression configuration parameters. This PDU session request is used to request the establishment or update of a PDU session; it is also referred to as a PDU session establishment or PDU session update message. In one design, the SMF network element can obtain the indication of the first header compression capability and the first header compression configuration parameters through the PDU session establishment or PDU session update message. Alternatively, in another design, the UE can send a NAS transmission message to the AMF network element. This NAS transmission message includes the indication of the first header compression capability and / or the first header compression configuration parameters. After obtaining the indication of the first header compression capability and / or the first header compression configuration parameters from the NAS transmission message, the AMF network element forwards the indication of the first header compression capability and / or the first header compression configuration parameters to the SMF network element.

[0117] Step 502: The SMF network element determines the header compression capability based on the UE's header compression capability and the UPF network element's header compression capability. This header compression capability represents the header compression capabilities supported by both the UE and the network side, specifically including at least one of the following header compression capabilities: IP header, UDP header, and TCP header. For example, if the header compression capabilities supported by the UE include IP header and UDP header, and the header compression capabilities supported by the UPF include IP header and TCP header, then the determined header compression capability may include the IP header.

[0118] Step 503: The SMF network element sends a policy request message to the PCF network element, which includes the above-mentioned header compression capability indication information.

[0119] Step 504: The PCF network element determines the traffic splitting function based on its header compression capability.

[0120] For example, if the overall header compression capability includes support for IP or UDP header compression, and / or support for IP or TCP header compression, the PCF network element can choose the QUIC-based traffic offloading function. If IP or UDP header compression is not supported, the PCF network element can choose the ATSSS-LL traffic offloading function. Alternatively, if IP or TCP header compression is not supported, the PCF network element can choose the MPTCP traffic offloading function, or the ATSSS-LL traffic offloading function, etc.

[0121] Step 505: The PCF network element sends a policy response message to the SMF network element. The policy response message includes service flow information, traffic splitting mode indication, or traffic splitting function indication, etc.

[0122] Step 506: The SMF network element sends a PFCP session establishment request or update message to the UPF network element. This message includes service flow information and an indication of header compression functionality, indicating that header compression functionality for the relevant service flow is activated or enabled. The header compression functionality indication includes at least one header compression enable indication from the IP header, UDP header, or TCP header.

[0123] For example, the PFCP session establishment request message or update message mentioned above may include the UE's header compression configuration parameters and / or the UPF's header compression configuration parameters. The UE's header compression configuration parameters are as shown in step 501. The UPF's header compression configuration parameters may be the UPF-side header compression configuration parameters allocated by the SMF network element, specifically including the same parameters as the UE-side parameters, but the parameter values ​​may differ from those on the UE-side. Alternatively, the UPF-side header compression parameters may be the UPF-side header compression parameters determined by the SMF network element based on the UE's header compression configuration parameters, etc.

[0124] Step 507: The UPF network element activates its header compression function based on the instruction from the SMF network element. Specifically, if the header compression enable instruction includes at least one of IP header, UDP header, and TCP header compression, the UPF network element activates the corresponding header compression function. Optionally, the UPF network element generates header compression configuration parameters on the UPF side and sends them to the SMF network element. For example, if the UPF network element receives header compression configuration parameters from the UE, it can generate UPF-side header compression configuration parameters based on the UE's header compression configuration parameters. Figure 5 The process shown is illustrated by an example where a UPF network element sends a PFCP session establishment request or update reply message to an SMF network element, and this message includes header compression configuration parameters.

[0125] Step 507 is optional for the following reason: In one design, the PFCP session establishment request or update message in step 506 may or may not carry the UPF header compression configuration parameters. If the PFCP session establishment request or update message in step 506 does not carry the UPF header compression configuration parameters, the UPF network element can execute step 507 to send the UPF header compression configuration parameters to the SMF network element.

[0126] Step 508: The SMF network element sends a PDU session establishment or update success message to the UE. This message includes service flow information and an indication of header compression functionality, used to indicate the activation of at least one of the IP, UDP, and TCP header compression functions for the relevant service flow. Optionally, the PDU session establishment or update success message may also include service flow information, traffic splitting mode indication information, or traffic splitting function indication information, etc.

[0127] Step 509: After the UE receives the header compression enable instruction, the UE sends a PMF message, HTTP message or MPQUIC data packet to the UPF network element. The header compression configuration parameters on the UE side can be carried in the PMF message, HTTP message or MPQUIC data packet.

[0128] For example, the above MPQUIC data packet has two specific implementations: 1) The MPQUIC data packet header encapsulates a stream-type data frame. A special type of stream ID value is used to indicate that this data frame contains one or more 3GPP-defined control parameters, and the compressed configuration parameter is one of these control parameters. 2) The MPQUIC data packet header encapsulates a 3GPP control type frame, that is, the data frame type indicates that it is a 3GPP data frame. This frame contains one or more 3GPP-defined control parameters, and the header compressed configuration parameter is one of these control parameters.

[0129] Similarly, the UPF can also send the header compression configuration parameters of the UPF side to the UE through PMF messages, HTTP messages, or MPQUIC data packets.

[0130] Step 509 is optional for the following reasons: Steps 501 to 508 can be considered as transmitting messages or signaling in the control plane. After steps 501 to 508, a data plane connection can be established between the UE and the UPF network element, allowing data transmission between them. In one design, the UE and the UPF network element can exchange their respective header compression parameters in the control plane. Alternatively, the UE and the UPF network element can also exchange their respective header compression configuration parameters in the data plane, i.e., in step 509, without limitation. That is, if the UE and the UPF network element have already exchanged their respective header compression configuration parameters in the control plane, step 509 need not be executed.

[0131] Step 5010: The UE and / or UPF network element can generate a decompressed file based on the complete packet header of the data packet, and store the correspondence between the decompressed file and the service flow information. The service flow information is as defined above. Afterwards, the UE and / or UPF network element can recover the complete packet header information of the data packet based on the decompressed file, thereby obtaining the data packet including the complete packet header.

[0132] For example, a UE can receive data packets, including complete headers, from a UPF network element, generate a decompressed file, and store the correspondence between the decompressed file and service flow information. The decompressed file can also be called a decompression context, and can be identified by a context ID. Service flow information includes the MPQUIC connection identifier and / or the stream identifier within the MPQUIC connection. The UE can establish a correspondence between the stream ID and the decompressed file (context ID). When the UE receives a downlink data packet from the UPF network element, it obtains the stream ID from the QUIC or MPQUIC protocol header of the data packet. Based on the correspondence between the stream ID and the decompressed file (context ID), it determines the decompressed file and uses it to obtain the complete header information of the data packet, i.e., the parameter information of the IP header, UDP header, or TCP header.

[0133] Similarly, for uplink service flows, the UPF can receive data packets from the UE, including the complete header, generate a decompressed file, and store the mapping between the decompressed file and the service flow, i.e., the mapping between the stream ID and the decompressed file (contextID). When the UPF receives an uplink data packet sent by the UE, it obtains the stream ID from the data packet. Based on the mapping between the stream ID and the decompressed file (contextID), it determines the decompressed file and uses the decompressed file to obtain the complete header information of the data packet.

[0134] Through the above Figure 5The process can implement a header compression mechanism for at least one of the IP header, TCP header, and UDP header between the UE and the UPF side, thereby reducing the packet header length and improving transmission efficiency.

[0135] like Figure 6 The diagram illustrates a communication method flow that enables compression of the outer protocol header of data packets, including at least the following:

[0136] Step 601: The UE sends a PDU session request to the SMF network element. This PDU session request includes indication information of the first compression capability and / or first header compression configuration parameters, etc. Alternatively, the UE sends a NAS transmission message to the AMF network element. This NAS transmission message contains indication information of the first compression capability and / or first header compression configuration parameters, and a PDU session request message, etc. The AMF network element forwards the indication information of the first compression capability and / or first header compression configuration parameters, and the PDU session request message to the SMF network element.

[0137] Step 602: The SMF network element determines the header compression capability based on the header compression capabilities of the UE and UPF network elements.

[0138] Step 603: The SMF network element sends a policy request to the PCF network element, which includes header compression capability.

[0139] Step 604: The PCF network element determines the traffic splitting function based on its header compression capability.

[0140] Step 605: The SMF network element receives a policy response from the PCF network element. The policy response includes service flow information, traffic splitting mode indication, or traffic splitting function indication, etc.

[0141] For detailed explanations of steps 601 to 605, please refer to the above. Figure 5 Steps 501 to 505 in the process shown.

[0142] Step 606: The SMF network element enables outer header compression for both the UE and the UPF network element based on the outer header compression capabilities supported by the UE and the UPF network element. The enabled outer header compression includes compression of the IP header and / or UDP header.

[0143] Step 607: The SMF network element sends a PFCP session establishment request or update request message to the UPF network element. This message includes an indication of enabling header compression and an indication of the access technology. Optionally, it may also include header compression configuration parameters. The access technology indication includes 3GPP access or non-3GPP access, indicating that outer packet header compression will be performed on data packets transmitted through tunnels corresponding to 3GPP or non-3GPP access technologies.

[0144] Step 608: The UPF network element enables the outer IP and / or UDP header compression function based on the indication information for the outer header compression function. It generates header compression configuration parameters, or uses header compression configuration parameters sent by the SMF network element. If the header compression configuration parameters are generated by the UPF network element, the UPF network element can send a PFCP session establishment request or update reply message to the SMF network element, which includes the header compression configuration parameters.

[0145] Step 608 is an optional step, and the reason for this can be found in the explanation above for why step 507 is an optional step.

[0146] Step 609: If the SMF network element enables the outer header compression function on the 3GPP side, the SMF network element notifies the base station through the AMF network element to disable the header compression function on the base station side. That is, the SMF network element sends an N2 message to the base station. This N2 message contains the PDU session ID and a disable header compression indication, indicating that header compression is disabled for all service flows in the relevant PDU session. Alternatively, the N2 message sent by the SMF network element contains the QFI and a disable header compression indication, indicating that header compression is disabled for the service flows in the relevant QFI.

[0147] Step 6010: The RAN sends a PDU session response to the UE. This PDU session response is obtained by the RAN from the N2 message. The PDU session response may be a PDU session establishment or update success message, etc. It may include an indication of enabling outer header compression and access technology, indicating that the UE performs outer IP and / or UDP layer header compression on data packets transmitted via the aforementioned access technologies. Optionally, the PDU session response may also include: service flow information, traffic splitting mode indication, traffic splitting function indication, and header compression configuration parameters, etc.

[0148] With the above Figure 5 The process is similar. When the outer header compression function is enabled, the header compression configuration parameters can also be exchanged between the UE and the UPF network element through PMF messages, HTTP messages, or MPQUIC data packets.

[0149] Step 6011: The UE and / or UPF network element can obtain the complete packet header, generate a decompressed file, and store the correspondence between the decompressed file and the service flow information. The aforementioned service flow information is the MPQUIC connection identifier. Afterwards, the UE and / or UPF network element can decompress the compressed data packets based on the decompressed file to obtain data packets including the complete packet header.

[0150] The above method enables the UE and UPF network elements to compress the outer data packet header, further reducing the header length of the data packet and improving transmission efficiency.

[0151] Example 2

[0152] This application also provides a communication method that can pause or restart header compression. The method includes: a first device sending a first message to a second device, the first message including indication information for stopping or activating header compression. The first device receives a second message from the second device, the second message being a response message to the first message. In one design, the above-mentioned pause or restart header compression function can be initiated by a UE, with the first device being the UE and the second device being the UPF. Alternatively, the above-mentioned pause or restart header compression function can be initiated by the UPF, with the first device being the UPF and the second device being the UE.

[0153] like Figure 7 As shown, taking the UE initiating the pause or restart of the packet header compression function as an example, a communication method flow is provided, which includes at least:

[0154] Step 701: The UE sends a first message to the UPF network element. This first message can be a link state detection function (PMF) message, a hypertext transfer protocol (HTTP) message, or an MPQUIC data packet, etc. The first message is used to stop or activate the header compression function. For example, the first message may include indication information for stopping or activating the header compression function, which indicates whether the header compression function is stopped or activated. Optionally, the first message may also include service flow information, used to instruct the UE and / or UPF to stop or activate the header compression function of the data packets corresponding to the service flow information.

[0155] In one design, the UE can determine whether to stop or activate the header compression function based on at least one of link state, internal state, or local policy. The link state can include link packet loss rate status. For example, when the packet loss rate is high, the header compression function is stopped, and when the packet loss rate is low, the header compression function is activated. The internal state can include internal resource consumption. For example, when resources are scarce, the header compression function is stopped; otherwise, the header compression function is activated. In one possible implementation, the UE can decide to stop or activate the header compression function based on network quality or UE policy. For example, if the UE determines that the current network-side state is poor, such as a high packet loss rate, the UE can suspend header compression for all service flows, or suspend header compression for certain service flows (e.g., high-value service flows, or packet loss-sensitive service flows). Optionally, when the network-side state recovers, the UE and UPF can resume the header compression function.

[0156] Step 702: Based on the UE's request, the UPF stops or activates the header compression function and sends a second message to the UE, which is a response to the first message. Optionally, the second message may include indications that the UPF has successfully stopped or activated the header compression function, or indications that the UPF has failed to stop or activate the header compression function.

[0157] Using the above method, when the network condition is poor or other reasons lead to a high packet loss rate, the UE and UPF network element can perform tasks such as decompressing, pausing, or restarting the data packet header.

[0158] like Figure 8 As shown, a specific process in Embodiment 2 is provided, which includes at least:

[0159] Step 801: Based on the scheme of Embodiment 1, enable the header compression function of UE and / or UPF.

[0160] Step 801 is optional because, in one design, the header compression function of the UE and / or UPF network element can be enabled based on the method provided in Embodiment 1 above. Alternatively, the header compression function of the UE and / or UPF network element can also be enabled based on other methods, without limitation. Therefore, step 801 is optional.

[0161] Step 802: The UE pauses or restarts the packet header compression function based on network quality.

[0162] Step 802 is optional because the UE can decide to pause or restart the header compression function based on network quality. Alternatively, the UE can pause or restart the header compression function based on other factors, etc., without limitation. Therefore, step 802 is optional.

[0163] Step 803: The UE sends a PMF message to the UPF. The PMF message includes indication information for pausing or restarting the header compression function and QFI, indicating that the UE requests to pause or restart the header compression function of the data packet corresponding to the QFI.

[0164] Step 804: UPF pauses or restarts the header compression function based on the request.

[0165] Step 804 is optional because: the UPF can agree to the request, suspend or restart the header compression function. Alternatively, the UPF can refuse the request, not suspend or restart the header compression function, etc., without limitation. Step 804 above is described using the example of the UPF agreeing to the request; therefore, step 804 is optional.

[0166] Step 805: The UPF sends a PMF message to the UE. This PMF message includes a restart or pause header compression response and QFI, etc. The restart or pause header compression response may indicate successful restart or pause header compression, or failure to restart or pause header compression.

[0167] Example 3

[0168] This application also provides a communication method, including: a first device sending a first message to a second device, the first message including indication information of a complete header request; the first device receiving a second message from the second device, the second message being a response message to the first message. In one design, the first device can be a UE, and the second device can be a UPF network element. Alternatively, the first device can be a UPF network element, and the second device can be a UE.

[0169] like Figure 9 As shown, taking the first device as the UE and the second device as the UPF network element as an example, a communication method flow is provided, which includes at least:

[0170] Step 901: The UE sends a first message to the UPF network element. This first message includes a PMF message, an HTTP message, or an MPQUIC message, etc. The first message requests the peer to send a data packet carrying a complete data packet header. For example, the first message may include an indication of a complete header request, indicating a request for the peer to send a data packet containing a complete data packet header. Optionally, the first message may also include at least one of service flow information or a decompression file identifier. Upon receiving the first message, the UPF network element can send a data packet carrying a complete header corresponding to the service flow to the UE. The UE can receive the data packet carrying a complete header corresponding to the service flow from the UPF network element, and the UE can generate or update a decompression file, etc., corresponding to the service flow based on the data packet carrying the complete header.

[0171] In one design, when the UE determines that the decompressed file is lost or expired, i.e., it is not the latest version of the decompressed file, the UE can send an indication message requesting a complete packet header to the UPF network element.

[0172] Step 902: The UE receives a second message from the UPF network element, which may be a response to the first message. Optionally, the second message may include indication information indicating whether the UPF network element agrees to or rejects the UE's full header request.

[0173] In one design, if the UPF agrees to the request sent by the UE, the UPF can clear or reset relevant compression configuration parameters, such as the maximum time interval and / or the maximum packet interval. Of course, the second message mentioned above also includes indication information that the UPF network element agrees to the UE's full-packet header request.

[0174] Using the above method, if the decompressed packet is lost or expired, in order to reduce the impact of data packet decompression failure, the UE and UPF network element can notify the other end to immediately send the complete data packet header so that the decompressed file can be regenerated or updated.

[0175] like Figure 10 As shown, a specific example of implementation three is provided, which includes at least:

[0176] Step 1001: Enable the header compression function of UE and / or UPF based on the method in Embodiment 1.

[0177] Step 1001 is an optional step, for reasons similar to those for step 801 above, and both can be referred to.

[0178] Step 1002: The UE determines that the decompressed file is missing or expired, that is, the decompressed file is not the latest version of the decompressed file.

[0179] Step 1002 is an optional step, for reasons similar to those for step 802 above, and both can be referred to.

[0180] Step 1003: The UE sends a PMF to the UPF. The PMF includes a full header request indication, a decompression file identifier, and service flow information. The service flow information may include flow description information, a flow identifier in the MPQUIC connection, or at least one of the QFIs, used to indicate to the UPF that the UPF needs to transmit the complete data packet header for the relevant service flow.

[0181] Step 1004: The UPF sends a data packet with a complete header based on the UE's instruction and clears the relevant compression configuration parameters.

[0182] Step 1004 is an optional step, for reasons similar to those for step 804 above, and both can be referred to.

[0183] Step 1005: The UPF retransmits the data packet, including the complete header, to the UE.

[0184] Step 1006: The UPF sends a PMF to the UE, which includes a success indication.

[0185] Regarding Examples 1 to 3, it should be noted that:

[0186] 1. The above text focuses on describing the differences between the different processes. Other content can be found by referring to the different processes.

[0187] 2. Not all steps shown in the flowcharts described in Examples 1 to 3 are mandatory. Some steps can be added or deleted based on the actual needs of each flowchart. For example, step 400 above can be selectively executed.

[0188] It is understood that in the embodiments of this application, the UE and / or core network elements may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0189] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0190] The above combination Figures 1 to 10 The methods provided in the embodiments of this application are described in detail below. Figure 11 and Figure 12 The apparatus provided in the embodiments of this application is described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for any content not described in detail, please refer to the description in the method embodiments above.

[0191] Figure 11 The schematic block diagram of the apparatus 1100 provided in the embodiments of this application includes a communication unit 1101 and a processing unit 1102. The communication unit 1101 is used to communicate with the processor and may also be referred to as a communication interface, transceiver unit, or input or output interface, etc. The processing unit 1102 is used to perform processing.

[0192] In the first embodiment, device 1100 can be an SMF network element or a chip within an SMF network element. Processing unit 1102 is used to enable header compression functionality of the terminal device and / or the User Plane Function (UPF) network element. Communication unit 1101 is used to send indication information of the header compression functionality to the terminal device and / or the UPF network element. Communication unit 1101 can also be used to receive a first message from the terminal device, the first message including indication information of a first header compression capability, which indicates that the terminal device supports header compression functionality. Processing unit 1102 enables the header compression capability of the terminal device and / or the UPF network element, including: enabling the header compression function of the terminal device and / or the UPF network element based on the first header compression capability and / or the Multi-Link Fast User Datagram Protocol (MPQUIC) offloading function.

[0193] Optionally, the first message may also include the first header compression configuration parameters of the terminal device.

[0194] The communication unit 1101 can also send a second message to the policy control function PCF network element. The second message includes indication information of the second header compression capability. The indication information of the second header compression capability is used to indicate that both the terminal device and the UPF network element support header compression capability.

[0195] The communication unit 1101 can also receive a third message from the PCF network element. The third message includes service flow information and header compression function indication information. The SMF network element determines that the header compression function is enabled for the data packet corresponding to the service flow information based on the header compression function indication information. Alternatively, the third message includes service flow information and MPQUIC splitting function indication information. The SMF network element determines that the header compression function is enabled for the data packet corresponding to the service flow information based on the MPQUIC splitting function indication information.

[0196] Sending the header compression function instruction information to the UPF network element includes: sending a fourth message to the UPF network element, the fourth message including service flow information and header compression function instruction information.

[0197] In one optional manner, the fourth message further includes a second header compression configuration parameter, which is allocated by the SMF network element to the UPF network element, or the second header compression configuration parameter is determined by the SMF network element based on the first header compression configuration parameter of the terminal device, or the second header compression configuration parameter is the first header compression configuration parameter of the terminal device forwarded by the SMF network element.

[0198] The communication unit 1101 can also receive a fifth message from the UPF network element, the fifth message including a third header compression configuration parameter, the third header compression configuration parameter being the header compression configuration parameter of the UPF network element.

[0199] In one optional manner, the communication unit 1101 sends header compression function indication information to the terminal device, including sending a sixth message to the terminal device, the sixth message including service flow information and header compression function indication information.

[0200] The header compression capability may include packet inner protocol header compression capability, the header compression function includes packet inner protocol header compression function, the packet inner protocol header compression includes at least one of Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header compression; and / or, the header compression capability includes packet outer protocol header compression capability, the header compression function includes packet outer protocol header compression function, the packet outer protocol header compression includes at least one of IP header or UDP header.

[0201] The communication unit 1101 can also send a seventh message to the access network device. The seventh message includes an indication message to disable the compression function of the IP header and / or UDP header, which is used to instruct the access network device to no longer perform header compression processing on the IP header and / or UDP header of the data packets.

[0202] The communication unit 1101 can also send indication information of the first access mode to the terminal device and / or the UPF network element, for instructing the terminal device and / or the UPF network element to enable header compression function for the data packets transmitted in the link corresponding to the first access mode.

[0203] In the second embodiment, the aforementioned device 1100 can be a terminal device or a chip in a terminal device, then:

[0204] The communication unit 1101 is used to receive instruction information for header compression function from the session management function (SMF) network element; the processing unit 1102 is used to enable header compression function according to the instruction information for header compression function.

[0205] In one possible design, the communication unit 1101 is further configured to: send a first message to the SMF network element, the first message including indication information of a first header compression capability, the first header compression capability being used to indicate that the terminal device supports header compression functionality.

[0206] In one possible design, the first message may also include the first header compression configuration parameters of the terminal device.

[0207] In one possible design, receiving header compression instruction information from the SMF network element includes: receiving a sixth message from the SMF network element, the sixth message including service flow information and header compression instruction information. Enabling the header compression function based on the header compression instruction information includes: enabling header compression of the data packets corresponding to the service flow information based on the service flow information and the header compression instruction information.

[0208] In one possible design, the first header compression capability includes packet inner protocol header compression capability, the header compression function includes packet inner protocol header compression function, the packet inner protocol header compression includes at least one of Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header compression; and / or, the first header compression capability includes packet outer protocol header compression capability, the header compression function includes packet outer protocol header compression function, the packet outer protocol header compression includes at least one of IP header or UDP header header compression.

[0209] In one possible design, the communication unit 1101 is further configured to: receive indication information of a first access mode from the SMF network element; the processing unit 1102 is further configured to: enable header compression function for data packets transmitted in the link corresponding to the first access mode.

[0210] In one possible design, the communication unit 1101 is further configured to: receive a data packet including a complete header corresponding to the service flow information from the UPF network element; the processing unit 1102 is further configured to: generate a first decompressed file based on the data packet with the complete header, and store the correspondence between the first decompressed file and the service flow information.

[0211] In the third embodiment, the device 1100 can be a UPF network element or a chip within a UPF network element, then:

[0212] The communication unit 1101 is used to receive instruction information for header compression function from the session management function (SMF) network element; the processing unit 1102 is used to enable header compression function according to the instruction information for header compression function.

[0213] In one possible design, receiving the header compression function indication information from the SMF network element includes: receiving a fourth message from the SMF network element, the fourth message including the service flow information and the header compression function indication information. Enabling the header compression function according to the header compression function indication information includes: enabling the header compression function of the data packets corresponding to the service flow information according to the service flow information and the header compression function indication information.

[0214] In one possible design, the fourth message further includes: a second header compression configuration parameter, wherein the second header compression configuration parameter is allocated by the SMF network element to the UPF network element, or the second header compression configuration parameter is determined by the SMF network element based on the first header compression configuration parameter of the terminal device, or the second header compression configuration parameter is the first header compression configuration parameter of the terminal device forwarded by the SMF network element.

[0215] In one possible design, the communication unit 1101 is further configured to send a fifth message to the SMF network element, the fifth message including the second header compression configuration parameter, which is the header compression configuration parameter of the UPF network element.

[0216] In one possible design, the header compression function includes inner packet protocol header compression, which includes compression of at least one of the Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header; and / or, the header compression function includes outer packet protocol header compression, which includes compression of at least one of the IP header or UDP header.

[0217] In one possible design, the communication unit 1101 is further configured to: receive indication information of a first access mode from the SMF network element; the processing unit 1102 is further configured to: enable header compression function for data packets transmitted in the link corresponding to the first access mode.

[0218] In one possible design, the communication unit 1101 is further configured to: receive a data packet including a complete header corresponding to the service flow information from the terminal device; the processing unit 1102 is further configured to: generate a second decompressed file based on the data packet with the complete header, and store the correspondence between the second decompressed file and the service flow information.

[0219] In the fourth embodiment, device 1100 can be a first device or a chip in the first device, then:

[0220] The communication unit 1101 is configured to send a first message to the second device, the first message including indication information for stopping or activating the header compression function; the communication unit 1101 is also configured to receive a second message from the second device, the second message being a response message to the first message.

[0221] In one possible design, the first message also includes service flow information, and the first device stops or activates the header compression function of the data packet corresponding to the service flow information.

[0222] In one possible design, the second message includes an indication that the second device has successfully stopped or activated the header compression function, or an indication that the second device has failed to stop or activate the header compression function.

[0223] In one possible design, the first device determines whether to stop or activate the header compression function based on at least one of link state, internal state, or local policy.

[0224] In the fifth embodiment, if device 1100 can be a second device or a chip in the second device, then:

[0225] The communication unit 1101 is configured to receive a first message from the first device, the first message including indication information for stopping or activating the header compression function; the communication unit 1101 is also configured to send a second message to the first device, the second message being a response message to the first message.

[0226] In one possible design, the first message also includes service flow information, and the second device stops or activates the header compression function of the data packet corresponding to the service flow information.

[0227] In one possible design, the second message includes an indication that the second device has successfully stopped or activated the header compression function, or an indication that the second device has failed to stop or activate the header compression function.

[0228] In the sixth embodiment, device 1100 can be a first device or a chip in the first device, then:

[0229] Communication unit 1101 is configured to send a first message to the second device, the first message including indication information of a complete packet header request; communication unit 1101 is configured to receive a second message from the second device, the second message being a response message to the first message.

[0230] In one possible design, the first message may further include at least one of service flow information or decompression file identifier. The first device receives a data packet carrying a complete header corresponding to the service flow from the second device. The first device generates or updates the decompression file corresponding to the service flow based on the data packet carrying the complete header.

[0231] In one possible design, the second message includes an indication that the second device agrees to or rejects the first device's full header request.

[0232] In one possible design, when the first device determines that the decompressed file is unavailable, it performs the step of sending a first message from the first device to the second device.

[0233] In the seventh embodiment, if device 1100 can be a second device or a chip in the second device, then:

[0234] The communication unit 1101 is configured to receive a first message from the first device, the first message including indication information of a complete header request; the communication unit 1101 is also configured to send a second message to the first device, the second message being a response message to the first message.

[0235] In one possible design, the first message may also include at least one of service flow information or decompressed file identifier, and the second device may send a data packet with a complete header corresponding to the service flow to the first device.

[0236] In one possible design, the second message includes an indication that the second device agrees to or rejects the first device's full header request.

[0237] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, and some units can be implemented in hardware. For example, each unit can be a separately established processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element mentioned here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0238] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).

[0239] The communication unit 1101 described above is an interface circuit of the device, used to receive signals from other devices or send signals to other devices. For example, when the device is implemented as a chip, the communication unit 1101 is an interface circuit for the chip to receive signals from other chips or devices, or to send signals to other chips or devices.

[0240] refer to Figure 12 This is a schematic diagram of a device 1200 provided in an embodiment of this application. The device includes a processor 1210 and an interface 1230. Optionally, the device may also include a memory 1220. The interface 1230 is used to enable communication with other devices.

[0241] The methods executed by the SMF network element, terminal device, UPF network element, first device, or second device in the above embodiments can be implemented by the processor 1210 calling a program stored in the memory. That is, the SMF network element, terminal device, UPF network element, first device, or second device may include the processor 1210, which executes the methods executed by the SMF network element, terminal device, UPF network element, first device, or second device in the above method embodiments by calling a program in the memory. The processor 1210 here can be an integrated circuit with signal processing capabilities, such as a CPU. The SMF network element, terminal device, UPF network element, first device, or second device can be implemented by one or more integrated circuits configured to implement the above methods. For example, one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms.

[0242] Specifically, Figure 11 The functions / implementation processes of the communication unit 1101 and the processing unit 1102 can be obtained through Figure 12 The processor 1210 in the illustrated device 1200 calls computer-executable instructions stored in memory 1220 to implement the function. Alternatively, Figure 11 The function / implementation process of the processing unit 1102 can be achieved through... Figure 12 The processor 1210 in the illustrated device 1200 calls computer execution instructions stored in memory 1220 to implement this. Figure 11 The function / implementation process of the communication unit 1101 can be achieved through... Figure 12 This is achieved through interface 1230 in the device 1200 shown.

[0243] It should be understood that, in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this invention.

[0244] This application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer, implements the functions of any of the above method embodiments.

[0245] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0246] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0247] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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, all or part of the processes or functions described in the embodiments of this application are generated. 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. 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 wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. 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 integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0248] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor, application-specific integrated circuit (ASIC), 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; alternatively, it can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0249] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be housed in an ASIC.

[0250] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0251] In one or more exemplary designs, the functions described herein can be implemented in hardware, software, firmware, or any combination of these three. If implemented in software, these functions can be stored on a computer-readable medium or transmitted on a computer-readable medium in the form of one or more instructions or code. Computer-readable media includes computer storage media and communication media that facilitate the transfer of computer programs from one location to another. Storage media can be any available media accessible to a general-purpose or special-purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other formats readable by a general-purpose or special-purpose computer or processor. Furthermore, any connection can be suitably defined as a computer-readable medium, for example, if the software is transmitted from a website, server, or other remote resource via a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the definition of a computer-readable medium. The disks and discs mentioned include compressed disks, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while discs typically copy data optically using lasers. Combinations of the above can also be contained in computer-readable media.

[0252] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0253] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above descriptions are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, or improvements made based on the technical solution of this application should be included within the scope of protection of this application. The above description in this application specification allows for the utilization or implementation of the content of this application by anyone skilled in the art. Any modifications based on the disclosed content should be considered obvious in the art. The basic principles described in this application can be applied to other variations without departing from the inventive nature and scope of this application. Therefore, the content disclosed in this application is not limited to the described embodiments and designs but can be extended to the maximum extent consistent with the principles and novel features disclosed in this application.

[0254] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method characterized by comprising: include: The Session Management Function (SMF) network element enables the header compression function of terminal equipment and / or User Plane Function (UPF) network elements; The SMF network element sends the header compression function instruction information to the terminal device and / or the UPF network element. There is a Multi-Link Fast User Datagram Protocol Internet Connection (MPQUIC) between the terminal device and the UPF network element. The header compression function includes no longer encapsulating the data packets corresponding to the MPQUIC with a full header. The header compression function includes inner packet protocol header compression and / or outer packet protocol header compression. The inner packet protocol stack includes the Internet Protocol (IP) layer, the User Datagram Protocol (UDP) layer, or the Transmission Control Protocol (TCP) layer. The inner packet protocol header compression includes no longer encapsulating the packet with at least one of the following: IP layer, UDP layer, or TCP layer, and the encapsulated packet no longer contains the corresponding IP header, UDP header, or TCP header. The outer packet stack includes the IP layer or the UDP layer, and the outer packet protocol header compression includes no longer encapsulating the packet with the IP layer or the UDP layer, and the encapsulated packet no longer contains the corresponding IP header or the UDP header.

2. The method of claim 1, wherein, Also includes: The SMF network element receives a first message from the terminal device, the first message including indication information of a first header compression capability, the first header compression capability being used to indicate that the terminal device supports header compression function; The SMF network element enables the header compression function of the terminal equipment and / or the user plane function UPF network element, including: The SMF network element enables the header compression function of the terminal device and / or the UPF network element based on the first header compression capability and / or the MPQUIC (Multi-Link Fast User Datagram Protocol) offloading function of the Internet connection.

3. The method of claim 2, wherein, The first message also includes the first header compression configuration parameters of the terminal device.

4. The method according to any one of claims 1 to 3, characterized in that, Also includes: The SMF network element sends a second message to the Policy Control Function (PCF) network element. The second message includes indication information of the second header compression capability, which indicates that both the terminal device and the UPF network element support header compression capability.

5. The method as described in claim 4, characterized in that, Also includes: The SMF network element receives a third message from the PCF network element. The third message includes service flow information and header compression function indication information. The SMF network element determines that the header compression function is enabled for the data packet corresponding to the service flow information based on the header compression function indication information. Alternatively, the third message may include service flow information and indication information for MPQUIC traffic splitting function. The SMF network element determines the data packet enable header compression function corresponding to the service flow information based on the indication information for MPQUIC traffic splitting function.

6. The method according to any one of claims 1, 2, 3, or 5, characterized in that, The SMF network element sends the header compression function instruction information to the UPF network element, including: The SMF network element sends a fourth message to the UPF network element, the fourth message including service flow information and header compression function indication information.

7. The method as described in claim 6, characterized in that, The fourth message also includes: a second header compression configuration parameter, wherein the second header compression configuration parameter is allocated by the SMF network element to the UPF network element, or the second header compression configuration parameter is determined by the SMF network element based on the first header compression configuration parameter of the terminal device, or the second header compression configuration parameter is the first header compression configuration parameter of the terminal device forwarded by the SMF network element.

8. The method as described in claim 7, characterized in that, Also includes: The SMF network element receives a fifth message from the UPF network element. The fifth message includes a third header compression configuration parameter, which is the header compression configuration parameter of the UPF network element.

9. The method according to any one of claims 1, 2, 3, 5, 7, or 8, characterized in that, The SMF network element sends header compression function instruction information to the terminal device, including: The SMF network element sends a sixth message to the terminal device, the sixth message including service flow information and header compression function indication information.

10. The method as described in claim 2 or 3, characterized in that, The header compression capability includes packet inner protocol header compression capability, and the header compression function includes packet inner protocol header compression function. The packet inner protocol header compression includes at least one of the following header compression methods: Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header; and / or, The header compression capability includes the packet outer protocol header compression capability, the header compression function includes the packet outer protocol header compression function, and the packet outer protocol header compression includes header compression of at least one of the IP header or UDP header.

11. The method according to any one of claims 1, 2, 3, 5, 7, or 8, characterized in that, The method further includes: The SMF network element sends a seventh message to the access network device. The seventh message includes an indication to disable the compression function of the IP header and / or UDP header, which is used to instruct the access network device to no longer perform header compression processing on the IP header and / or UDP header of the data packets.

12. The method according to any one of claims 1, 2, 3, 5, 7, or 8, characterized in that, The method further includes: The SMF network element sends indication information of the first access mode to the terminal device and / or the UPF network element, which is used to instruct the terminal device and / or the UPF network element to enable header compression function for the data packets transmitted in the link corresponding to the first access mode.

13. A communication method, characterized in that, include: The terminal device receives instruction information from the Session Management Function (SMF) network element regarding header compression function; The terminal device enables the header compression function according to the instruction information of the header compression function. There is a multi-link fast user datagram protocol Internet connection (MPQUIC) between the terminal device and the user plane function UPF network element. The header compression function includes no longer encapsulating the data packets corresponding to the MPQUIC with a full header. The header compression function includes inner packet protocol header compression and / or outer packet protocol header compression. The inner packet protocol stack includes the Internet Protocol (IP) layer, the User Datagram Protocol (UDP) layer, or the Transmission Control Protocol (TCP) layer. The inner packet protocol header compression includes no longer encapsulating the packet with at least one of the following: IP layer, UDP layer, or TCP layer, and the encapsulated packet no longer contains the corresponding IP header, UDP header, or TCP header. The outer packet stack includes the IP layer or the UDP layer, and the outer packet protocol header compression includes no longer encapsulating the packet with the IP layer or the UDP layer, and the encapsulated packet no longer contains the corresponding IP header or the UDP header.

14. The method as described in claim 13, characterized in that, Also includes: The terminal device sends a first message to the SMF network element. The first message includes indication information of a first header compression capability, which is used to indicate that the terminal device supports header compression functionality.

15. The method as described in claim 14, characterized in that, The first message also includes the first header compression configuration parameters of the terminal device.

16. The method according to any one of claims 13 to 15, characterized in that, The terminal device receives instruction information from the SMF network element regarding the header compression function, including: The terminal device receives a sixth message from the SMF network element, the sixth message including service flow information and header compression function indication information; The terminal device enables the header compression function according to the instruction information of the header compression function, including: The terminal device enables the header compression function of the data packet corresponding to the service flow information according to the service flow information and the header compression function instruction information.

17. The method as described in claim 14 or 15, characterized in that, The first header compression capability includes packet inner protocol header compression capability, the header compression function includes packet inner protocol header compression function, and the packet inner protocol header compression includes compression of at least one of the following headers: Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header; and / or, The first header compression capability includes the packet outer protocol header compression capability, and the header compression function includes the packet outer protocol header compression function, wherein the packet outer protocol header compression includes header compression of at least one of the IP header or UDP header.

18. The method as described in any one of claims 13, 14, or 15, characterized in that, The method further includes: The terminal device receives indication information of the first access method from the SMF network element; The terminal device enables header compression for data packets transmitted in the link corresponding to the first access method.

19. The method as described in claim 16, characterized in that, Also includes: The terminal device receives a data packet, including a complete header, corresponding to the service flow information from the User Plane Function (UPF) network element. The terminal device generates a first decompressed file based on the data packet with the complete header; The terminal device stores the correspondence between the first decompressed file and the service flow information.

20. A communication method, characterized in that, include: User plane function (UPF) network elements receive instruction information from the session management function (SMF) network elements regarding header compression. The UPF network element enables the header compression function according to the instruction information of the header compression function. There is a Multi-Link Fast User Datagram Protocol Internet Connection (MPQUIC) between the terminal device and the UPF network element. The header compression function includes no longer encapsulating the data packets corresponding to the MPQUIC with a full header. The header compression function includes inner packet protocol header compression and / or outer packet protocol header compression. The inner packet protocol stack includes the Internet Protocol (IP) layer, the User Datagram Protocol (UDP) layer, or the Transmission Control Protocol (TCP) layer. The inner packet protocol header compression includes no longer encapsulating the packet with at least one of the following: IP layer, UDP layer, or TCP layer, and the encapsulated packet no longer contains the corresponding IP header, UDP header, or TCP header. The outer packet stack includes the IP layer or the UDP layer, and the outer packet protocol header compression includes no longer encapsulating the packet with the IP layer or the UDP layer, and the encapsulated packet no longer contains the corresponding IP header or the UDP header.

21. The method as described in claim 20, characterized in that, The UPF network element receives instruction information from the SMF network element regarding the header compression function, including: The UPF network element receives a fourth message from the SMF network element, the fourth message including service flow information and header compression function indication information; The UPF network element enables the header compression function according to the instruction information of the header compression function, including: The UPF network element enables the header compression function of the data packet corresponding to the service flow information according to the service flow information and the header compression function instruction information.

22. The method as described in claim 21, characterized in that, The fourth message also includes: a second header compression configuration parameter, wherein the second header compression configuration parameter is allocated by the SMF network element to the UPF network element, or the second header compression configuration parameter is determined by the SMF network element based on the first header compression configuration parameter of the terminal device, or the second header compression configuration parameter is the first header compression configuration parameter of the terminal device forwarded by the SMF network element.

23. The method according to any one of claims 20 to 22, characterized in that, Also includes: The UPF network element sends a fifth message to the SMF network element. The fifth message includes a second header compression configuration parameter, which is the header compression configuration parameter of the UPF network element.

24. The method according to any one of claims 20 to 22, characterized in that, The header compression function includes packet inner protocol header compression, which includes compression of at least one of the following: Internet Protocol (IP) header, User Datagram Protocol (UDP) header, or Transmission Control Protocol (TCP) header; and / or, The header compression function includes a packet outer protocol header compression function, which includes header compression of at least one of the IP header or UDP header.

25. The method according to any one of claims 20 to 22, characterized in that, The method further includes: The UPF network element receives indication information of the first access method from the SMF network element; The UPF network element enables header compression for data packets transmitted in the link corresponding to the first access method.

26. The method as described in claim 21, characterized in that, Also includes: The UPF network element receives data packets, including complete headers, corresponding to the service flow information from the terminal device; The UPF network element generates a second decompressed file based on the data packet with the complete packet header; The UPF network element stores the correspondence between the second decompressed file and the service flow information.

27. A communication device, characterized in that, The device includes a processor and a memory, the processor and the memory being coupled; the memory stores computer program instructions, and the processor invokes the computer program instructions to implement the method of any one of claims 1 to 12, or to implement the method of any one of claims 13 to 19, or to implement the method of any one of claims 20 to 26.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 12, or the method of any one of claims 13 to 19, or the method of any one of claims 20 to 26.

Images