Communication method and apparatus

Abstract

The present application relates to the technical field of communications, and provides a communication method and apparatus, used for solving the problems that a large amount of data forwarding occupies large network transmission resources, the service processing delay is long, and the communication efficiency is low in a scenario where a user plane network element transmits, to an application server, a large amount of media data requested by terminals. The method comprises: receiving a first message, the first message comprising a media data transmission requirement based on a quick user datagram protocol (UDP) Internet connection (QUIC) of a terminal; and determining a second apparatus on the basis of the first message, wherein the second apparatus supports a first function, the first function is a QUIC-based media data transmission function, and the second apparatus is used for establishing a first QUIC link with the terminal, and transmitting media data by means of the first QUIC link.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 27, 2024, with application number 202410376220.8 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] Transport layer protocols in wireless communication transmission include the User Datagram Protocol (UDP), which can provide simple communication transmission services. Quick UDP Internet Connections (QUIC) is a reliable UDP transmission protocol that can provide secure, reliable, and low-latency communication transmission services. For example, in QUIC-based media over QUIC (MoQ) transmission scenarios, QUIC can be used to transmit media data, such as audio or video, reducing latency and improving communication efficiency.

[0004] Currently, terminals and application servers can establish a QUIC connection to support QUIC-based media data transmission. Based on the terminal's session requirements and the terminal's subscription data, the network control plane function can assign a user plane function (UPF) to the terminal to create a session and establish a user plane connection from the terminal to the UPF. The UPF, acting as a transit node between the server and the terminal, does not need to decode the media data.

[0005] In the scenario where multiple terminals request the same or different media data from the same application server, for example, the UPF requests media data from the server of the first application and forwards the media data to terminal 1; subsequently, terminal 2 requests media data of the first application, and the UPF needs to request media data from the first application server again and forward the media data of the first application to terminal 2, resulting in a large amount of data forwarding occupying a large amount of network transmission resources, and a long service processing delay, and low communication efficiency. Summary of the Invention

[0006] The present application provides a communication method and device for solving the problem that in a scenario where a user-side network element transmits a large amount of media data requested by a terminal to an application server, the forwarding of a large amount of data occupies a large amount of network transmission resources, the service processing delay is long, and the communication efficiency is low.

[0007] To achieve the above objectives, this application adopts the following technical solutions:

[0008] In a first aspect, a communication method is provided, which can be performed by a first device or by a module (such as a chip or circuit) of the first device. For example, the first device can be a control plane function of a core network, such as a session management function. The method includes: receiving a first message, wherein the first message includes that a terminal has a media data transmission requirement based on a Quick Datagram Protocol Internet Connection (QUIC); determining a second device based on the first message, wherein the second device supports a first function, the first function being a media data transmission function based on QUIC, and the second device is used to establish a first QUIC link with the terminal and transmit media data through the first QUIC link.

[0009] In the above implementation manner, for a terminal with MoQ transmission requirements, the control plane function of the network, such as the first device, can select a user plane function, such as the second device, with MoQ transmission capability for the terminal according to the media access requirements of the terminal, thereby establishing a QUIC connection between the terminal and the user plane function, such as the second device. Multimedia data is transmitted to the terminal through the user plane function without the need for transmission through the application server of the media application, which can improve the MoQ transmission efficiency, avoid the occupation of network resources by large-scale data forwarding, and improve the utilization of network resources.

[0010] In one embodiment, the first message includes the media data parameters requested by the terminal, and the second device stores the media data corresponding to the media data parameters, or the second device serves the media application corresponding to the media data parameters.

[0011] In the above embodiment, the first message may carry the media data parameters of the MoQ requested by the terminal, such as the media content identifier, so that the first device can match and query the second device according to the media data parameters in the first message, query the second device that stores the media data corresponding to the media data parameters, or query the second device that can serve the media application corresponding to the media data parameters, establish a QUIC connection between the terminal and the second device, and improve communication efficiency.

[0012] In one embodiment, receiving a first message includes: receiving a first message from the terminal, the first message being used to request session establishment; determining a second device includes: sending a second message to a data management function, requesting to obtain the contract data of the terminal; receiving a response message from the data management function, the response message indicating that the terminal supports the first function, the response message also including media data parameters supported by the terminal; and determining, based on the response message, a second device that meets the media data parameters supported by the terminal from nodes supporting the first function.

[0013] In the above implementation, the first device can determine whether the terminal supports the MoQ function and the supported media data parameters by requesting the terminal's contract data from the data management function, so that the first device can determine the second device that meets the media data parameters supported by the terminal from the node that supports the first function, thereby improving communication efficiency.

[0014] In one embodiment, the first message includes first indication information, and the first indication information is used to indicate that the terminal requests to establish a QUIC-based media data transmission link.

[0015] In one embodiment, receiving a first message includes: receiving a first message from an edge application server discovery function, the first message including domain name information corresponding to a domain name system DNS server, the first message indicating that the terminal supports the first function, and including media data parameters requested by the terminal; determining a second device includes: determining, based on the domain name information, a second device that satisfies the media data parameters requested by the terminal from a node supporting the first function.

[0016] In the above implementation, an implementation method of configuring user plane functions to the terminal based on the Domain Name System (DNS) addressing process is supported. The edge application server discovery function can obtain information about the relay UPF that supports the MoQ function, such as the second device, based on the domain name query request, and feed it back to the terminal, so that a QUIC link can be established between the terminal and the second device of the user plane function. Multimedia data is transmitted to the terminal through the user plane function without the need for transmission through the application server of the media application, which can improve the MoQ transmission efficiency, avoid the occupation of network resources by large-scale data forwarding, and improve the utilization of network resources.

[0017] In one embodiment, the method includes: receiving second indication information from the second device or network storage function, the second indication information indicating that the second device supports the first function, and the second indication information also includes media data parameters corresponding to the media data stored by the second device.

[0018] In the above implementation, the user plane function in the network, such as the second device, can report that it supports the first function by sending a second indication information to the first device, and can also carry the media data parameters stored by the second device, so that the first device stores the capability information of the second device. When the terminal requests the MoQ function, the UPF that supports the MoQ transmission requirements can be matched for the terminal according to the capability of the second device, and a QUIC link can be established to improve communication efficiency.

[0019] In one embodiment, the method further includes: receiving third indication information from the second device, where the third indication information indicates that the second device does not support the media data parameters requested by the terminal.

[0020] In the above embodiment, if the second device of the user plane function allocated by the network to the terminal can only meet part of the media request of the terminal, a third indication message can be sent to the first device to indicate that the second device does not support the media data parameters requested by the terminal, so that a connection between the application server and the terminal can be established subsequently, thereby improving the flexibility of communication transmission.

[0021] In one embodiment, the method includes: sending a third message to the application function entity through a capability exposure interface, wherein the third message includes media data parameters requested by the terminal and information of the second device; the third message is used to request the application server to establish a second QUIC link with the second device, and transmit media data through the second QUIC link.

[0022] In the above embodiment, when the second device cannot fully meet the media data request of the terminal, the first device can send the media data parameters requested by the terminal and the information of the current second device UPF to the application function, thereby requesting the application server that can support the media data parameters requested by the terminal to establish a connection with the terminal to realize media data transmission, which can improve communication efficiency and flexibility.

[0023] In one embodiment, the method includes: sending a fourth message to a data management function, the fourth message including the media data parameters requested by the terminal, the fourth message being used to request information of an application server corresponding to the media data parameters requested by the terminal; receiving a response message from the data management function, the response message including information of a first application server, wherein the first application server is used to establish a third QUIC link with the second device and transmit media data through the third QUIC link; and sending information of the first application server to the second device.

[0024] In the above embodiment, when the second device cannot fully meet the media data request of the terminal, the first device can send the media data parameters requested by the terminal to the data management function to request information about an application server that can support the media data parameters requested by the terminal. Through the first application server, a connection can be established with the terminal to realize media data transmission, which can improve communication efficiency and flexibility.

[0025] In a second aspect, a communication method is provided, which can be executed by a terminal or a module (such as a chip or circuit) of the terminal. The method includes: sending a first message to a first device, the first message including first indication information, the first indication information being used to instruct the terminal to request to establish a QUIC-based media data transmission link; establishing a first QUIC link with a second device, and transmitting media data corresponding to the media data parameters via the first QUIC link.

[0026] In one embodiment, the first message further includes media data parameters requested by the terminal, and the second device stores media data corresponding to the media data parameters, or the second device serves a media application corresponding to the media data parameters.

[0027] In a third aspect, a communication method is provided. For example, the method can be executed by a data management function or by a module (such as a chip or circuit) of the data management function. The method includes: receiving a second message from a first device, the second message being used to request the acquisition of the contract data of the terminal; determining the contract data corresponding to the terminal based on the second message and the stored contract data corresponding to at least one terminal, the contract data including that the terminal supports a first function, the first function being a QUIC-based media data transmission function; and sending a response message to the first device, the response message indicating that the terminal supports the first function, the response message also including media data parameters supported by the terminal.

[0028] In one embodiment, the data management function stores media data parameters supported by the terminal.

[0029] In one embodiment, the method further includes: acquiring, through a capability exposure interface, information of an application server and parameters of media data supported for transmission by the application server based on the first function.

[0030] In a fourth aspect, a communication method is provided. The method can be performed by a second device or a module (such as a chip or circuit) of the second device. For example, the second device can be a user plane function of a core network, such as a user plane function (UPF). The method includes: sending second indication information to a network storage function, where the second indication information indicates support for a first function, where the first function is a QUIC-based media data transmission function; or, establishing a node-level connection with the first device and sending the second indication information to the first device.

[0031] In one embodiment, the second indication information further includes media data parameters corresponding to the media data stored in the second device.

[0032] In a fifth aspect, a communication device is provided, comprising: a processor; the processor is configured to be coupled to a memory, and after reading instructions from the memory, execute the method described in any of the above aspects according to the instructions. The communication device can be the first device described in the first aspect, or the terminal described in the second aspect, or the data management function described in the third aspect, or the second device described in the fourth aspect, or a node or device comprising the first device, second device, terminal, or data management function, or a module in the first device, second device, terminal, or data management function, such as a chip, chip system, or circuit, or a logical node, logical module, or software that can implement some or all of the functions.

[0033] In combination with the fifth aspect above, in a possible implementation, the communication device further includes a memory, which is used to store necessary program instructions and data.

[0034] In conjunction with the fifth aspect above, in one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0035] In a sixth aspect, a communication device is provided, comprising: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instruction and transmit it to the processor; and the processor is configured to execute the computer program or instruction so that the communication device performs the method described in any of the above aspects. The communication device may be the first device described in the first aspect, or the terminal described in the second aspect, or the data management function described in the third aspect, or the second device described in the fourth aspect, or a node or device comprising the first device, second device, terminal, or data management function, or a module in the first device, second device, terminal, or data management function, such as a chip, chip system, or circuit, or a logical node, logical module, or software capable of implementing some or all of the functions.

[0036] In conjunction with the sixth aspect above, in one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0037] In a seventh aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on the computer, the computer can execute the method described in any one of the above aspects.

[0038] In an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method described in any one of the above aspects.

[0039] In a ninth aspect, a communication system is provided, which includes a first device for executing any possible implementation of the first aspect, and a terminal for executing any possible implementation of the second aspect.

[0040] In combination with the ninth aspect above, in a possible implementation, the communication system further includes a data management function for executing any possible implementation of the third aspect above.

[0041] In combination with the ninth aspect above, in a possible implementation, the communication system further includes a second device for executing any possible implementation of the fourth aspect above.

[0042] Among them, the technical effects brought about by any possible implementation method in the second to ninth aspects can refer to the technical effects brought about by different possible implementation methods in the above-mentioned first aspect, and will not be repeated here.

[0043] It is understandable that, provided that the solutions are not contradictory, the solutions in each aspect can be combined. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0045] FIG2 is a schematic diagram of another communication system provided in an embodiment of the present application;

[0046] FIG3 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

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

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

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

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

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

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

[0053] FIG10 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0055] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0056] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0057] First, a brief introduction to the implementation environment and application scenarios of the embodiments of the present application is given.

[0058] The communication method provided in the embodiments of the present application can be applied to the communication system architecture shown in Figure 1. Figure 1 takes the network service architecture of the fifth generation (5G) mobile communication system as an example to illustrate the interaction between network functions (NFs) and entities and the corresponding interfaces. The 3rd Generation Partnership Project (3GPP) service-based architecture (SBA) of the 5G system mainly includes the following network functions and entities: User Equipment (UE), at least one access network (AN) or radio access network (RAN) node, user plane function (UPF), data network (DN), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), unified data management (UDM), network exposure function (NEF), unified data repository (UDR) and network storage function (NRF).

[0059] Among them, UE, (R)AN node, UPF and DN are generally referred to as user plane network functions and entities (or user plane network elements), and the other parts are generally referred to as control plane network functions and entities (or control plane network elements). The control plane network element is defined by 3GPP as the processing function in a network. The control plane network element has 3GPP-defined functional behaviors and 3GPP-defined interfaces. NF can be a network element running on dedicated hardware, or a software instance running on dedicated hardware, or a virtual function instantiated on a suitable platform, such as being implemented on a cloud infrastructure.

[0060] The following is a detailed introduction to the main functions of each network element.

[0061] Among them, the user plane network functions in the communication system include:

[0062] (R)AN Node: The (R)AN can be either an AN or a RAN, and can also be referred to as access network equipment, a RAN entity, or an access node. It forms part of a communication system and helps terminals access the communication network. For example, the (R)AN can be various base stations, such as macro base stations, micro base stations, wireless controllers, relay stations, access points, or network equipment in vehicle-mounted devices, wearable devices, or future public land mobile networks (PLMNs). The (R)AN is primarily responsible for radio resource management, quality of service management, data compression, and encryption on the air interface side.

[0063] In addition, the (R)AN node can also be an access node in an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or an access node in a communication system that integrates two or more of the above systems.

[0064] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, a RAN node may also be a server, a wearable device, a vehicle or an onboard device. For example, an access network device in vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in this application may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application may also be a logical node, a logical module, or software that can implement all or part of the functions of a RAN node.

[0065] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0066] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0067] UE: It can also be called terminal, terminal equipment, mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the device form of the terminal.

[0068] UPF: Responsible for forwarding and receiving user data. The UPF receives downlink data from the DN and transmits it to the UE via the (R)AN. The UPF also receives uplink data from the UE via the (R)AN and forwards it to the DN.

[0069] DN: For example, a DN can be a carrier service network, an internet access network, or a third-party service network. A DN can exchange information with a UE via Protocol Data Unit (PDU) sessions. PDU sessions can be of various types, such as Internet Protocol version 4 (IPv4) and IPv6.

[0070] In addition, the control plane network functions in the communication system include:

[0071] AMF: Mainly responsible for processing control plane messages and user mobility management, including mobility status management, allocating temporary user identities, and authenticating and authorizing users. For example, these functions include access control, mobility management, registration and deregistration, and network element selection.

[0072] SMF: Mainly used for session management, session establishment, UE IP address allocation and management, responsible for session establishment, modification and release, and quality of service (QoS) control.

[0073] UDM: Mainly used for authentication and credit processing, responsible for managing subscription data, user identification processing, access authorization, registration / mobility management, subscription management, and short message management. For example, when a user's subscription data is modified, the UDM is responsible for notifying the corresponding network element.

[0074] PCF: Mainly used for policy management, responsible for managing policy-related data in the network, and can provide policy rules to the control plane functions in the network (such as AMF, SMF, etc.).

[0075] NEF: Mainly used to provide corresponding security guarantees to ensure the security of external applications to the communication network, and provide functions such as external application QoS customization capability exposure, mobility status event subscription, and AF request distribution.

[0076] NRF: Mainly used to provide internal / external addressing functions, etc.

[0077] AF: Mainly used to send application-affected data routing information to the network side, and to perform policy control through interaction between network open function elements and the policy framework.

[0078] Among them, the functions of other network elements included in Figure 1 can be referred to the relevant descriptions in conventional technologies and will not be repeated here.

[0079] It should be noted that the network architecture shown in Figure 1 is for example purposes only and is not intended to limit the technical solutions of this application. Those skilled in the art will appreciate that, in a specific implementation, other network elements or devices may also be included, and the number of access network devices, terminals, and / or core network devices may also be determined based on specific needs.

[0080] Optionally, each network element shown in FIG1 may be a device, a functional module within a device, or a logical functional unit. It is understood that the above functions may be network elements in a hardware device, such as a communication chip in a mobile phone, or software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0081] In addition, the communication method provided in the embodiment of the present application can be applied to the communication system shown in Figure 2. As shown in Figure 2, the communication system may include a terminal, a control plane function such as a first device, a user plane function such as a second device, and an application server (AS). The terminal can establish a connection with the application server and transmit data through the user plane function. For example, a simple communication transmission service can be provided through UDP, or a secure, reliable and low-latency communication transmission service can be provided through QUIC. In the QUIC-based media (Media over QUIC, MoQ) transmission scenario, media data can be transmitted through QUIC, such as transmitting media data such as audio or video, reducing latency and improving communication efficiency.

[0082] In the embodiments provided herein, the user plane function acts as a relay node, identifying media data and caching some of the identified media data parameters. This allows the user plane function to forward cached media data to the terminal based on the terminal's media access requirements, eliminating the need to request the terminal's requested media data from the application server each time.

[0083] For example, terminal 1 requests media data 1 from a first application. A user plane function, such as UPF 1, can obtain the media data 1 from the first application and forward it to terminal 1. Meanwhile, the UPF can cache the media data 1 locally in the UPF. When terminal 2 requests media data 1, UPF 1 can forward the media data 1 to terminal 2 based on its own cached media data, eliminating the need to obtain the media data from the first application (e.g., application server) again.

[0084] In a specific implementation scenario, the network may include multiple user plane functions, some of which support MoQ transmission function, while some do not support MoQ transmission capability. Therefore, through the implementation method provided by the present application, the control plane function (such as the first device) can select a user plane function that has MoQ transmission capability and stores the media data parameters requested by the terminal for the terminal based on the MoQ transmission access requirements of the terminal, thereby establishing a QUIC connection between the terminal and the user plane function (such as the second device), and transmitting multimedia data to the terminal through the QUIC connection.

[0085] For example, the user plane function in the communication system can be the UPF in 5G, or the network element with the user plane function in 6G or future communication systems, and the control plane function can be the AMF, SMF, UDM, PCF and other network elements in 5G, or the network element with control plane function in 6G or future communication systems, etc. This application does not limit this.

[0086] It can be understood that in the communication system of Figure 1 or Figure 2 above, devices or network elements can communicate directly with each other, or communicate through forwarding by other nodes or devices. The embodiments of the present application do not make specific limitations on this.

[0087] It is understood that FIG2 is merely a schematic diagram and does not limit the applicable scenarios of the technical solutions provided in this application. Those skilled in the art should understand that, in a specific implementation, the communication system may include fewer devices or network elements than those shown in FIG2 , or the communication system may also include other devices or other network elements. The number of devices or network elements in the communication system may also be determined based on specific needs.

[0088] It should be noted that the communication system shown in Figure 1 or Figure 2 is for example only and is not intended to limit the technical solution of this application. Those skilled in the art should understand that in a specific implementation, the communication system may also include other devices or network elements, and the number of each network element may also be determined according to specific needs.

[0089] Optionally, each network element in Figure 1 or Figure 2 of the embodiment of the present application can be a functional module within a device. It can be understood that the above-mentioned functions can be network elements in hardware devices, such as communication chips in mobile phones, or software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform).

[0090] For example, each network element in Figure 1 or Figure 2 can be implemented by the communication device 300 in Figure 3. Figure 3 shows a schematic diagram of the hardware structure of a communication device applicable to embodiments of the present application. The communication device 300 includes at least one processor 301, a communication line 302, a memory 303, and at least one communication interface 304.

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

[0092] The communication link 302 may include a path for transmitting information between the above components, such as a bus.

[0093] The communication interface 304 uses any transceiver or other device for communicating with other devices or communication networks, such as an Ethernet interface, a RAN interface, a wireless local area network (WLAN) interface, etc.

[0094] The memory 303 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited to this. The memory can be independent and connected to the processor via a communication line 302. The memory can also be integrated with the processor. The memory provided in the embodiment of the present application can generally have non-volatility. Among them, the memory 303 is used to store the computer execution instructions involved in executing the solution of the present application, and is controlled by the processor 301. The processor 301 is used to execute the computer-executable instructions stored in the memory 303, thereby implementing the method provided in the embodiment of the present application.

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

[0096] In a specific implementation, as an embodiment, the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3 .

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

[0098] In a specific implementation, as an embodiment, the communication device 300 may further include an output device 305 and an input device 306. The output device 305 communicates with the processor 301 and can display information in a variety of ways. For example, the output device 305 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 306 communicates with the processor 301 and can receive user input in a variety of ways. For example, the input device 306 can be a mouse, a keyboard, a touch screen device, or a sensor device.

[0099] The communication device 300 described above can be a general-purpose device or a dedicated device. In a specific implementation, the communication device 300 can be a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal, an embedded device, or a device with a similar structure to that shown in FIG3 . The embodiments of the present application do not limit the type of the communication device 300.

[0100] The communication method provided in the embodiments of the present application is described in detail below.

[0101] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of the present application are only examples, and other names may be used in specific implementations. The embodiments of the present application do not specifically limit this.

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

[0103] The present application provides a communication method. For a terminal with MoQ transmission requirements, a control plane function of a network, such as a first device, can select a user plane function with MoQ transmission capability for the terminal based on the terminal's media access requirements, thereby establishing a QUIC connection between the terminal and the user plane function (such as a second device). Multimedia data is transmitted to the terminal through the user plane function, which can improve MoQ transmission efficiency, avoid the occupation of network resources by large-scale data forwarding, and improve the utilization of network resources.

[0104] As shown in FIG4 , the communication method may be applied to a first device and includes the following steps.

[0105] 401: The first device receives a first message, where the first message includes a terminal having a QUIC-based media data transmission requirement.

[0106] The first device can receive the access requirements of the terminal through the first message, such as the first message indicates the access requirements of the terminal, including that the terminal has a QUIC-based media data transmission requirement, that is, the terminal requests MoQ transmission.

[0107] In one embodiment, the first message may include first indication information, where the first indication information is used to indicate that the terminal requests to establish a QUIC-based media data transmission link. In other words, the first message may carry the first indication information to explicitly indicate that the terminal requests to establish a QUIC link to transmit media data, i.e., the terminal requests MoQ transmission.

[0108] 402: The first device determines the second device according to the first message.

[0109] At this time, the first device, such as the control plane function of the network, can obtain the access requirements of the terminal based on the first message, match the user plane function with MoQ transmission capability for the terminal, select and determine the second device, and establish a QUIC link with the terminal through the second device for transmitting media data. Exemplarily, the second device can be a UPF.

[0110] The second device supports the first function, which refers to a QUIC-based media data transmission function, that is, MoQ transmission capability. Exemplarily, the second device can be used to establish a first QUIC link with the terminal and transmit media data through the first QUIC link.

[0111] Exemplarily, the first device may locally store node information for multiple user plane functions. For example, the node information may specifically include a node identity and MoQ capability information supported by the node (such as information such as media data parameters stored by the node). The capability information may include whether the user plane function supports MoQ transmission capability, that is, whether it supports the first function. The first device may retrieve the node information for the user plane function and select, from nodes having the first function, a user plane function that meets the MoQ transmission requirements of the terminal indicated in the first message in step 401, and determine it as the target user plane function, i.e., the second device.

[0112] Alternatively, the first device can obtain node information of the user plane function in the network from other nodes. For example, the NRF can maintain node information of multiple user plane functions (such as multiple UPFs) in the network. The first device can obtain node information of the user plane function from the NRF and select a user plane function for the terminal that meets the MoQ transmission capability requested by the terminal.

[0113] In the above two implementations, the user plane function can report its own node information to the core network periodically or in real time, such as by registering, updating, or establishing an N4 connection, and configuring its own node information in the core network. The specific process can refer to the implementation process described in Figure 5 below and will not be repeated here.

[0114] For example, the first message may include the identifier of the media application for which the terminal requests MoQ transmission. For example, if the terminal requests media data from a first media application, the first message may carry the identifier corresponding to the first media application. Accordingly, the first device may query for a UPF that supports MoQ transmission based on the media application identifier carried in the first message, select a UPF that serves the first media application, and determine it as the target UPF, i.e., the second device.

[0115] In one embodiment, the second device stores media data corresponding to the media data parameters, or the second device serves a media application corresponding to the media data parameters. Furthermore, the second device may periodically report the media data parameters stored by itself to the SMF or NRF.

[0116] In one embodiment, the first message may include media data parameters requested by the terminal, such as a portion or segment of a specified media category (such as a TV series or movie), a specified short video content, or a specified music / video segment. For example, the media data parameter may specifically be a media content identifier.

[0117] Exemplarily, the first device may determine, based on the first message, a second device that satisfies the media data parameters supported by the terminal from nodes that support the first function.

[0118] Exemplarily, UPF1 serves a first media application and establishes a user plane connection with other user terminals. When acting as a relay node to forward media data of the first media application requested by the terminal, UPF1 can identify and save some or all of the transmitted media data and establish a mapping relationship between the media data and media data parameters. Therefore, when a terminal requests media data from the first media application, the SMF can select UPF1 to establish a QUIC link with the terminal based on the media data parameters requested by the terminal. UPF1 then transmits the media data corresponding to the media data parameters to the terminal without having to transmit through the application server of the first media application. This improves network resource utilization, reduces transmission latency, and enhances user experience.

[0119] It should be noted that the user plane function in the network, such as UPF, can start or disable the relay forwarding function, or start or disable the first function, such as the MoQ function. When the UPF starts the relay forwarding function and the UPF enables the first function, it can be used as the second device determined by the first device in the above embodiment to establish a QUIC link between the terminal and the UPF for media data transmission.

[0120] In one embodiment, at least one user plane function, such as a second device, may report / configure its own node information to the core network. For example, the second device may send second indication information to a network storage function of the core network to indicate that the device supports the first function. Optionally, the second indication information may also include media data parameters corresponding to media data stored by the second device.

[0121] Exemplarily, as shown in FIG5 , the UPF may configure its own node information to the core network through method one or method two.

[0122] Method 1:

[0123] 501: UPF sends a registration request message or an update request message to NRF.

[0124] In one embodiment, the UPF may request registration from the NRF and register its own node information with the NRF, so that network elements in the core network can obtain the UPF's node information through the NRF and select the UPF. For example, the UPF may register by sending a registration request message to the NRF, such as the Nnrf_NFManagement_NFRegister operation. Alternatively, the UPF may update the node information by sending an update request message to the NRF.

[0125] The registration request message or update request message may include second indication information, where the second indication information indicates that the second device, i.e., the UPF, supports the first function. Optionally, the second indication information may also include media data parameters corresponding to media data stored by the second device, i.e., the UPF.

[0126] Optionally, the registration request message or update request message may include the data network name (DNN), a single network slice selection assistance information (S-NSSAI) list, the IPv4 address range available to the terminal, and media data parameters corresponding to the media data supported by the UPF, such as the namespace of the media data and other information.

[0127] Correspondingly, the NRF receives the second indication information from the UPF, and records / stores the mapping relationship between the UPF identifier and the second indication information (carried node information).

[0128] 502: SMF requests NRF to query the node information of interest.

[0129] 503: NRF sends a query response to SMF.

[0130] Optionally, the SMF may periodically or periodically request the NRF to query the node information of interest.

[0131] Alternatively, the SMF can request the NRF to query the node information of interest when there is a business need. For example, when the SMF receives a session establishment request from a terminal and needs to select an appropriate user plane function for the terminal, it can query the NRF for node information that meets the terminal's business needs and select the UPF from it.

[0132] Alternatively, in one embodiment, the SMF may subscribe to the node information of interest to the NRF, and when the NRF obtains the node information that meets the SMF subscription conditions, it may send a subscription response to the SMF. This application does not limit the above-mentioned embodiments.

[0133] Exemplarily, the SMF may send a subscription request to the NRF, such as querying the NRF for the node information and target UPF of interest through the Nnrf_NFManagement_NFStatusSubscribe service. Correspondingly, the NRF may send the node information of one or a pair of UPFs that meet the SMF subscription conditions to the SMF through the Nnrf_NFManagement_NFStatusNotify service. Exemplarily, the subscription request may indicate a request to subscribe to the node information of the UPF, or, further, the subscription request may indicate a request to subscribe to the node information of the UPF with the first function, or, the subscription request may also indicate a request to subscribe to the UPF node information serving the first media application or a request to subscribe to the UPF node information that stores a specific media data, etc. Thus, the NRF matches the UPF that meets the conditions according to the subscription request and feeds back the subscription response to the SMF.

[0134] Exemplarily, the SMF receives a service access request from a first terminal, which carries the identifier of a first media application and, further, the identifier of the requested media data. The SMF can then send a query request message to the NRF to query the UPF information storing the media data of the first media application. The query request message can carry the identifier of the first media application and, further, the identifier of the media data requested by the terminal. If the NRF determines that UPF1 meets the conditions through the query, it can return a query response message to the SMF, carrying the identifier of UPF1.

[0135] Method 2:

[0136] 504: SMF establishes N4 connection with UPF.

[0137] Specifically, SMF can establish an N4 node-level connection with UPF through the N4 node connection establishment process (such as N4Association Setup). SMF and UPF can connect through the N4 node and interact with each other's supported functions. Subsequently, when the terminal requests to establish a PDU session, SMF can establish a PDU session-granularity connection with UPF.

[0138] Exemplarily, the N4 node connection establishment process may specifically include: SMF sending an N4 connection establishment request (such as N4Association Setup Request) message to UPF, UPF determining to establish an N4 connection with SMF, and sending an N4 connection establishment response (such as N4Association Setup Response) message to SMF to complete the establishment of the N4 node connection between SMF and UPF.

[0139] 505: SMF and UPF exchange node information via N4 connection.

[0140] In one implementation, the UPF may send to the SMF information such as the first function it supports, namely the MoQ function, and media data parameters corresponding to the media data cached by the UPF.

[0141] Similarly, SMF can send an N4 connection update request (such as N4Association Update Request) message to UPF to request the node information of UPF, and UPF sends an N4 connection update response (such as N4Association Update Response) message to SMF, carrying the node information of UPF, where the node information may include UPF support for the first function, as well as media data parameters.

[0142] It should be noted that the above-mentioned configuration methods 1 and 2 are not mutually exclusive. The two configuration methods can exist at the same time, or one method can be selected to implement the configuration of user plane function node information in the network. This application does not limit this.

[0143] In one embodiment, the first device may be SMF, and the terminal may send a session establishment request message to the AMF network element of the core network. Then, the AMF selects the SMF and forwards the terminal's access requirements to the SMF, and the SMF selects a suitable user plane function for the terminal to create a user plane MoQ connection.

[0144] In this implementation scenario, the first message received by the first device may specifically be a first message received by the first device from a terminal, and the first message may be used to request session establishment.

[0145] In this implementation scenario, the first device determines the second device based on the first message, which may specifically include: the first device sends a second message to the data management function to request to obtain the contract data of the terminal. If the terminal supports the first function, optionally, the contract data of the terminal also includes media data parameters supported by the terminal; then the first device can determine the second device that meets the media data parameters supported by the terminal from the node that supports the first function.

[0146] Specifically, the data management function pre-configures or stores media data parameters supported by the terminal. Exemplarily, the data management function may be UDM.

[0147] For the specific interaction process, please refer to the following embodiment 1.

[0148] Example 1

[0149] As shown in FIG6 , the method may include the following steps.

[0150] 600: UDM stores information about the terminal's support for the MoQ function and media data parameters.

[0151] Exemplarily, UDM can pre-store information on whether multiple terminals support the MoQ function, and if the terminal supports the MoQ function, UDM can store one or more media data parameters supported by the terminal, such as the namespace information corresponding to the media data, etc. UDM can store the above information as the terminal's contract data locally in UDM.

[0152] 601: The terminal sends a session establishment request to the AMF.

[0153] Optionally, the session establishment request may carry first indication information of the terminal, which is used to indicate that the terminal requests to establish a QUIC-based media data transmission link, that is, the terminal has MoQ access requirements.

[0154] Exemplarily, the terminal sends a PDU session establishment request (such as a PDU Session Establishment Request) message to the AMF. Optionally, the request message may carry first indication information, such as an MoQ connection indication (Indicator of MoQ connection), which is used to indicate that the terminal has MoQ access requirements and needs to create a user plane QUIC connection.

[0155] 602: AMF selects SMF and forwards the terminal's session establishment request to SMF.

[0156] Specifically, AMF selects a suitable SMF for the terminal and forwards the terminal's access requirements to the SMF.

[0157] Exemplarily, AMF may send a PDU session establishment context (such as PDU Session_CreateSMContext) request message to SMF.

[0158] Optionally, the session establishment request sent by AMF to SMF may carry first indication information, such as an MoQ connection indication (Indicator of MoQ connection), used to indicate that the terminal has MoQ access requirements and needs to create a user plane QUIC connection.

[0159] 603: SMF sends a data request message to UDM.

[0160] Among them, the data request message sent by SMF to UDM is used to request to obtain the contract data of the terminal.

[0161] Exemplarily, the SMF may subscribe to the contract data of the terminal from the UDM, wherein the contract data of the terminal may include whether the terminal supports the MoQ function, and if the terminal supports the MoQ function, may also include media data parameters corresponding to the media data supported by the terminal.

[0162] 604: UDM sends the terminal's contract data to SMF.

[0163] The UDM can obtain the contract data corresponding to the terminal requested by the SMF according to the information of multiple terminals pre-stored in the aforementioned step 600 and the terminal identification query, and send the contract data corresponding to the terminal to the SMF.

[0164] 605: The SMF selects a user plane function and determines the second device.

[0165] Specifically, SMF can obtain the UPF with MoQ function and the media data parameters corresponding to the UPF based on the UPF configuration enhancement method in method one or method two in the aforementioned process, and select the UPF that meets the terminal access requirements, that is, the second device.

[0166] 606: SMF establishes a PDU session connection with UPF.

[0167] Specifically, the SMF establishes a PDU session connection with the UPF that supports the MoQ function and has the media data parameters requested by the terminal.

[0168] 607: The terminal completes the session establishment.

[0169] For example, the terminal completes the PDU session establishment.

[0170] Specifically, the SMF sends a response message to the AMF, such as a Namf_Communication_N1N2MessageTransfer message, carrying the IP address, port number, and MoQ context information of the UPF that supports the MoQ function. The AMF then forwards the response message to the terminal via the RAN. The terminal can then initiate a PDU session connection with the corresponding UPF based on the information carried in the response message to support MoQ service transmission.

[0171] 608: The terminal establishes a QUIC connection with the UPF to transmit media data.

[0172] After the PDU session is established, the terminal establishes a QUIC connection with the UPF that supports the MoQ function. MoQ transmission can be created on the QUIC connection based on the terminal's business needs. For example, the terminal can send a data subscription request to the UPF to request to subscribe to specific media data; the UPF can send a subscription response to the terminal and send the requested media data to the terminal.

[0173] In the above implementation, data management functions such as the UDM pre-store whether a terminal has MoQ transmission requirements and pre-store parameters of media data supporting MoQ as the terminal's subscription data. Therefore, during the terminal session establishment process, the core network can query the UDM based on the terminal's access requirements to determine whether the terminal supports MoQ transmission. Based on the network's user plane function registration information, the core network can then match the terminal with a UPF that supports MoQ. Furthermore, the terminal can be matched with a UPF that supports the media data requested by the terminal, thereby improving communication efficiency and reducing data transmission latency.

[0174] In addition, in one embodiment, the present application also supports an implementation method for configuring user plane functions to the terminal based on the Domain Name System (DNS) addressing process to create a QUIC link from the terminal to the user plane function to transmit media data. Among them, the Edge Application Server Discovery Function (EASDF) can obtain information about the relay UPF that supports the MoQ function based on the DNS query request and feedback it to the terminal.

[0175] In this implementation scenario, the first device in step 401 of the aforementioned embodiment receives the first message, which may specifically include: the first device receives the first message from EASDF, the first message includes domain name information corresponding to the DNS server, the first message indicates that the terminal supports the first function, and includes media data parameters requested by the terminal.

[0176] In this implementation scenario, the first device in step 402 of the aforementioned embodiment determines the second device based on the first message, which may specifically include: the first device determines the second device that meets the media data parameters requested by the terminal from the node supporting the first function based on the domain name information carried by the first message of EASDF.

[0177] Specifically, in this implementation scenario, the terminal can carry the MoQ transmission requirements (such as media data parameters) to request DNS query from EASDF. EASDF can trigger SMF to select UPF and forward the terminal MoQ transmission requirements to SMF. At this time, SMF can select a relay UPF that supports the terminal MoQ request for the terminal based on the UPF configuration process of the aforementioned method one or method two. SMF can insert the selected UPF as a local-PDU Session Anchor (L-PSA) or as an uplink classifier (ULCL) into the user session corresponding to the terminal. Specifically, in one implementation method, SMF can return the information of the selected UPF (such as node identifier) ​​to EASDF, and EASDF will provide the UPF information to the terminal through DNS response. Alternatively, in another implementation method, EASDF can also send the UPF information to the terminal via DNS, so that the terminal can subsequently establish a QUIC link with the UPF and transmit media data.

[0178] For the specific interaction process, please refer to the description of the following embodiment 2.

[0179] Example 2

[0180] As shown in FIG. 7 , the method may include the following steps.

[0181] 700: The terminal completes session creation.

[0182] The terminal has completed the session creation process. For example, the terminal completes the PDU session creation and establishes a PDU session with the PDU Session Anchor (PSA) UPF. The PSA UPF can also be called a target UPF, which can be understood as the initial UPF that the network uses to establish a session for the terminal.

[0183] During the session creation process of the terminal, the SMF may check whether the terminal is authorized to discover the edge application server (EAS) through the EASDF. If it is determined that the terminal is authorized, the corresponding EASDF is selected for the terminal.

[0184] 701: The terminal sends a DNS query request to the EASDF.

[0185] Specifically, the application on the terminal may trigger a DNS query request (eg, DNS Query Request) to be sent to the EASDF. The DNS query request may carry relevant information of the MoQ transmission request, such as the first indication information, and may optionally further include media data parameters.

[0186] 702: EASDF sends a DNS query request to the DNS server.

[0187] EASDF can send a query request to the DNS server according to the request of the terminal, requesting domain name resolution and querying the information of the EAS that can serve the service requested by the terminal.

[0188] 703: The DNS server sends a DNS query response to the EASDF.

[0189] Correspondingly, the DNS server performs a query based on the received DNS query request to obtain DNS information, such as the target fully qualified domain name (FQDN), EAS address, etc. The DNS server can send a DNS query response to the EASDF, carrying the queried DNS information.

[0190] 704: EASDF sends the first message to SMF.

[0191] Specifically, the first message may be a DNS context notification (such as Neasdf_DNSContext_Notify Request) message, which EASDF sends to SMF, carrying the DNS information obtained from the aforementioned step 703; optionally, the notification message may also carry relevant information of the terminal's MoQ transmission request obtained in the aforementioned step 701, such as media data parameters.

[0192] 705: SMF selects a UPF that supports the MoQ function.

[0193] Correspondingly, the SMF can select a matching UPF for the terminal according to the received first message and the MoQ transmission requirements of the terminal.

[0194] Specifically, SMF can obtain the UPF with MoQ function and the media data parameters corresponding to the UPF based on the UPF configuration enhancement method in method one or method two in the aforementioned process, and select the UPF that meets the terminal access requirements, that is, the second device.

[0195] 706: SMF establishes an N4 / PDU session connection with UPF.

[0196] 707: The SMF and UPF establish a path and distribute traffic based on ULCL.

[0197] It should be understood that the 5G communication system can support the insertion of multiple session anchor points UPF on the user plane path of a PDU session to support the connection of the terminal to the local data network DN, so that the terminal device can access the application in the local DN nearby. Diversion refers to the diversion of business data and ultimately reaches different networks or servers. During the routing and local diversion of 5G data packets, ULCL UPF or branching point (BP) UPF can be used to selectively transfer edge computing application traffic to L-PSAUPF.

[0198] In this application, the relay UPF selected by the SMF can be inserted into the user session corresponding to the terminal as an L-PSA or as an ULCL for diversion. Specifically, the SMF can determine the N6 traffic routing information associated with the data network access identifier (DNAI) according to the N6 traffic routing information of the DNAI included in the EAS deployment information, and configure the L-PSA UPF using the forwarding action derived from the N6 traffic routing information. The SMF can perform the selection and insertion of ULCL / BP and L-PSA.

[0199] 708: SMF sends UPF information to EASDF.

[0200] Specifically, the SMF may send a DNS context update request (such as Neasdf_DNSContext_Update Request) message to the EASDF, which may carry the UPF information, thereby sending the information of the UPF supporting MoQ transmission to the EASDF.

[0201] 709: EASDF sends UPF information to the terminal.

[0202] Specifically, the EASDF may send information about the UPF supporting MoQ transmission to the terminal by sending a DNS query response (such as a DNS Query response) message to the terminal.

[0203] 710: The terminal establishes a QUIC connection with the UPF to transmit media data.

[0204] The terminal establishes a QUIC connection with the UPF that supports the MoQ function, and can create MoQ transmission on the QUIC connection according to the business needs of the terminal.

[0205] In the above implementation, by enhancing the DNS addressing process and participating in scheduling through EASDF, the network can select the UPF that supports the MoQ function to establish a user plane connection with the terminal according to the MoQ requirements of the terminal, thereby improving communication efficiency and reducing data transmission delay.

[0206] Furthermore, the aforementioned embodiment provides an implementation process for selecting a MoQ UPF for a terminal based on the terminal's MoQ transmission requirements. Considering that the selected MoQ UPF may not meet all of the terminal's MoQ transmission requirements, for example, the MoQ UPF stores media data 1 requested by the terminal but does not store media data 2 requested by the terminal. In other words, the MoQ UPF can only partially meet the terminal's MoQ transmission requirements. In this case, the MoQ UPF can request the corresponding application server to fulfill the remaining MoQ transmission requirements, such as obtaining media data 2.

[0207] That is, in the aforementioned first or second embodiment, after step 608 or 701, in one embodiment, the second device (i.e., the MoQ UPF) may send third indication information to the SMF to indicate that the second device does not support some or all of the media data parameters requested by the terminal. In other words, to meet the service requirements of the terminal, the network needs to establish a connection between the terminal and the application server AS to obtain media data.

[0208] In one embodiment, when the AS supports QUIC connection and MoQ functions, or when the AS enables QUIC connection and MoQ functions, the AS may send its own node information to a data management function, such as a UDM or a unified data repository (UDR), through a capability exposure interface. The node information sent by the AS may specifically include the AS's identity, the AS's support for the first function, i.e., the MoQ transmission function, and media data parameters corresponding to the media data supported by the AS for transmission based on the first function. For example, the media data parameters may specifically include a namespace, indication information, or a protocol type.

[0209] That is to say, by enhancing the openness of AS capabilities, the MoQ service functions supported by AS are stored in UDM / UDR in the form of contract data. Subsequently, when UPF requests AS to establish a QUIC connection and MoQ service, SMF can establish a QUIC connection between the terminal and AS by obtaining the AS information supporting the corresponding MoQ service stored in UDR or UDM.

[0210] In one embodiment, the first device (such as SMF) may send a fourth message to the data management function (such as UDM or UDR), where the fourth message includes the media data parameters requested by the terminal, and the fourth message is used to request information about the application server that supports the media data parameters requested by the terminal. Correspondingly, the data management function may query based on the received fourth message to obtain information about the application server that meets the terminal's MoQ requirements, such as the first application server, and send a response message to the first device, where the response message may include information about the first application server. The first application server may be used to establish a third QUIC link with the second device and transmit media data through the third QUIC link.

[0211] For the specific interaction process, please refer to the description of the following embodiment three.

[0212] Example 3:

[0213] As shown in FIG8 , the method may include the following steps.

[0214] 801: AS sends node information to AF, including support for MoQ function and corresponding media data parameters.

[0215] Specifically, the AS may send its own identity and the media data parameters supported for transmission by the AS based on the MoQ function to the AF.

[0216] 802: AF sends AS node information to NEF.

[0217] Specifically, the AF can send the node information of the AS to the NEF through the capability exposure interface. For example, it can send a parameter provision (Nnef_ParameterProvision) message to the NEF, carrying the identity information of the AS, the indication information that the AS supports MoQ, and the media data parameters that the AS supports the MoQ function.

[0218] In one embodiment, the operator may pre-configure the MoQ-supporting AS node information on the UDM. Alternatively, the process of the data management function (e.g., UDM or UDR) obtaining the AS node information may adopt the following method 1 (steps 803a-806a) or method 2 (803b-804b), which is not limited in this application.

[0219] In one implementation, for a terminal roaming scenario, or a scenario requiring AF security authentication, the steps of the following method 1 may be performed.

[0220] 803a: NEF sends AS node information to UDM.

[0221] Specifically, after the NEF authenticates the AF, it can send a Nudm_ParameterProvision message to the UDM, which carries the AS's identification information, the AS's support for MoQ, and the media data parameters that the AS supports for MoQ. The UDM can then receive and store the above information.

[0222] Optionally, the following steps 804a-805a may also be performed.

[0223] 804a: UDM sends the AS node information to UDR.

[0224] Specifically, the UDM can send a Nudr_DM_Query or Nudr_DM_Update request message to the UDR, carrying information such as the AS's identification, information indicating that the AS supports MoQ, and media data parameters supporting the MoQ function. The UDR can then receive and store this information.

[0225] 805a: The UDR sends a response message to the UDM.

[0226] Optionally, after receiving the above message from the UDM and obtaining the node information of the AS, the UDR may send a response message to the UDM, indicating that the node information of the AS has been successfully received. For example, the response message may be an acknowledgement (ACK) response.

[0227] 806a: UDM sends a response message to NEF.

[0228] Optionally, after receiving the above message from the NEF and obtaining the node information of the AS, the UDM may send a response message to the NEF, indicating that the node information of the AS has been successfully received. For example, the response message may be an ACK response.

[0229] In one implementation, for a non-roaming terminal scenario, or a scenario where UDM security authentication is not required, the following method 2 steps may be performed.

[0230] 803b: NEF sends AS node information to UDR.

[0231] Specifically, the NEF can directly send a Nudr_DM_Update request message to the UDR, carrying the AS identification information, the indication information that the AS supports MoQ, and the media data parameters of the AS supporting the MoQ function. Correspondingly, the UDR can receive and store the above information.

[0232] 804b: The UDR sends a response message to the NEF.

[0233] Optionally, after receiving the above message from the NEF and obtaining the node information of the AS, the UDR may send a response message to the NEF, indicating that the node information of the AS has been successfully received. For example, the response message may be an ACK response.

[0234] 807: NEF sends a response message to AF.

[0235] The NEF may send a response message to the AF to indicate that the sending of the AS node information to the data management function has been completed.

[0236] 808: SMF sends a query request to UDM.

[0237] Specifically, when SMF confirms that the current UPF does not meet all the MoQ data transmission requirements requested by the terminal and needs to establish a QUIC connection between the terminal and the AS that supports MoQ transmission, SMF can request UDM to query the stored identity information and media data parameters of the AS that supports the MoQ function.

[0238] Alternatively, in another embodiment, the SMF may send a subscription request to the UDM in advance, requesting to subscribe to the node information of the AS that meets the conditions, so that when the UDM confirms that an AS meets the subscription request of the SMF, it may send a subscription response to the SMF, carrying the node information of the AS.

[0239] 809: UDM sends a query response to SMF.

[0240] Correspondingly, the UDM can locally search for information about the AS that supports the MoQ function and information about the AS that supports the media data parameters requested by the terminal based on the query request of the SMF.

[0241] 810: SMF establishes an N4 / PDU connection with UPF and sends AS information to UPF.

[0242] Specifically, SMF can establish an N4 / PDU connection with UPF, and SMF can provide UPF with the identification information of the AS obtained from UDM, as well as the media data parameters supported by the AS.

[0243] 811: Establish a QUIC connection between the terminal and the AS to transmit media data.

[0244] Specifically, UPF can establish a QUIC connection with AS according to the business needs of the terminal, create a MoQ connection and realize media data transmission.

[0245] The above implementation method, by enhancing the openness of AS capabilities, stores the MoQ service functions supported by AS in UDM / UDR. When UPF requests AS to establish a QUIC connection and MoQ service, SMF can establish a QUIC connection between the terminal and AS by obtaining the AS information supporting the corresponding MoQ service stored in UDR or UDM, thereby solving the problem that the relay UPF cannot provide the terminal with all the MoQ transmission requirements requested by the terminal. In this way, media data can be transmitted through the QUIC connection between the terminal and AS. The implementation process is flexible and can improve communication efficiency.

[0246] In addition, for the aforementioned, MoQ UPF may not be able to meet all the MoQ transmission requirements of the terminal. The present application also provides another implementation method. According to the business needs of the terminal, the application server that meets the MoQ transmission requirements of the terminal can be queried and obtained. Through UPF, a QUIC connection can be established between the terminal and the AS to transmit the media data requested by the terminal.

[0247] In one embodiment, the first device (such as SMF) can send a third message to the application function entity through the capability exposure interface. The third message includes the media data parameters requested by the terminal and information of the second device (such as MoQ UPF). The third message is used to request the application server to establish a second QUIC link with the UPF and transmit media data through the second QUIC link.

[0248] In this embodiment, the UPF establishing the first QUIC connection with the terminal can send the media data parameters supported by the UPF to the relevant AS. At this time, the UPF acts as a MoQ relay node and the AS acts as a MoQ client. The AS can trigger media data transmission to the UPF.

[0249] In the scenario of this embodiment, the AS supports QUIC connection and MoQ functions as a MoQ client. The AS can request the UPF to establish a QUIC connection and MoQ service. The UPF can report DNAI information to the AF through the SMF and carry the UPF ID and supported media data parameters. The AS can establish a QUIC connection with the current MoQ UPF by obtaining the current DNAI information and UPF node information.

[0250] For the specific interaction process, please refer to the description of the following fourth embodiment.

[0251] Example 4:

[0252] As shown in FIG9 , the method may include the following steps.

[0253] 901: AF subscribes to user plane management event notification from SMF.

[0254] Specifically, AF can initiate a subscription request to SMF, in which a new first trigger (trigger) carrying a trigger event report is added. The new first trigger is used when SMF detects that the demand for user plane function has changed, such as when SMF receives a third indication information from a specified user plane function, indicating that the second device such as UPF cannot meet all the media data parameters requested by the terminal, it can trigger SMF to send a notification message to AF. Exemplarily, the first trigger can be MoQ relay function change. After the first trigger is triggered, SMF can send an event notification message to AF, carrying information such as MoQ UPF information (such as identifier or IP address), UDP port information, and media data parameters.

[0255] 902: UPF establishes an N4 / PDU connection with SMF.

[0256] When the SMF selects the UPF as the MoQ relay for the terminal, the UPF establishes a QUIC link with the terminal to provide the terminal's MoQ access requirements. In addition, the UPF establishes an N4 / PDU connection with the SMF.

[0257] Optionally, in one embodiment, the UPF sends third indication information to the SMF, indicating that the UPF cannot meet part or all of the MoQ transmission requirements requested by the terminal.

[0258] 903: The SMF sends an event notification message to the AF.

[0259] According to the trigger received in step 901, the SMF determines that the user plane management event subscribed by the AF occurs. Based on the trigger, the SMF sends an event notification message to the AF. The event notification message can be the aforementioned third message. The SMF sends the third message to the AF through the capability exposure interface, carrying the media data parameters requested by the terminal and the information of the MoQ relay UPF. The third message is used to request the application server to establish a QUIC link with the current MoQ UPF and transmit media data through the QUIC link.

[0260] Specifically, the SMF may send an event notification message to the AF through a capability exposure interface, or the SMF may send an event notification message to the AF through forwarding by a network exposure function NEF.

[0261] For example, in one embodiment, the implementation of step 903 may include the following process: the SMF sends an event notification message (such as Nsmf_EventExposure_Notify) to the NEF, carrying the current DNAI information and MoQ UPF information, such as the UPF identifier or IP address, UDP port, media data parameters, etc. Then, the NEF sends a notification message (such as Nnef_TrafficInfluence_Notify) to the AF through the capability exposure service, carrying the DNAI information and MoQ UPF information.

[0262] 904: AF sends a notification message to AS.

[0263] Correspondingly, when AF receives the event notification message and determines that AS can meet the MoQ transmission requirements requested by the terminal, it sends a notification message to the AS, carrying DNAI information and MoQ UPF information, requesting the AS to establish a QUIC connection with MoQ UPF.

[0264] 905: AS establishes a QUIC connection with UPF.

[0265] Specifically, the AS can choose to establish a QUIC connection with the MoQ UPF based on the DNAI information and the MoQ UPF information, create a MoQ connection and implement media data transmission.

[0266] In the above implementation, through the capability exposure function, SMF can notify AF of the information and DNAI information of the UPF currently serving as the MoQ relay, so that AF can notify AS and create a user plane connection from AS to UPF, thereby solving the problem that the relay UPF cannot provide the terminal with all the MoQ transmission requirements requested by the terminal, meeting the MoQ transmission requirements of the terminal, and the implementation process is flexible and can improve communication efficiency.

[0267] It should be understood that the various embodiments mentioned above in this application can be combined without limitation if there is no contradiction between the solutions.

[0268] The above mainly introduces the solution provided by the present application from the perspective of interaction between various network elements. Accordingly, the present application also provides a communication device, which can be the first device in the above method embodiment, or a node or device containing the above first device, or a component that can be used for the first device; or, the communication device can be the second device in the above method embodiment, or a node or device containing the above second device, or a component that can be used for the second device. Further, the communication device can be the terminal in the above method embodiment, or a node or device containing the above terminal, or a component that can be used for a third device. In addition, the communication device can be the data management function in the above method embodiment, or a node or device containing the above data management function, or a component that can be used for the data management function.

[0269] It is understandable that, in order to implement the above functions, the above communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithmic operations of the various examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0270] It should be understood that the above description only uses the first device, terminal, data management function, or second device as examples to describe the interactions between various network elements. In practice, the processing performed by the terminal is not limited to being performed by a single network element, and the processing performed by the network device is not limited to being performed by a single network element.

[0271] The present application can divide the functional modules of the communication device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software functional modules. It is understood that the division of modules in this application is schematic and is only a logical functional division. In actual implementation, other division methods may be used.

[0272] For example, in the case of dividing the functional modules in an integrated manner, FIG10 shows a schematic structural diagram of a communication device 1000. The communication device 1000 includes an interface module 1001 and a processing module 1002.

[0273] In some embodiments, the communication device 1000 may further include a storage module (not shown in FIG. 10 ) for storing program instructions and data.

[0274] For example, the communication device 1000 can be used to implement the function of the first device. The communication device 1000 is, for example, the first device or SMF described in the above embodiments.

[0275] Among them, the interface module 1001 is used to receive a first message, and the first message includes that the terminal has a media data transmission requirement based on the Quick Datagram Protocol Internet Connection QUIC.

[0276] The processing module 1002 is used to determine a second device based on the first message, wherein the second device supports a first function, the first function is a QUIC-based media data transmission function, and the second device is used to establish a first QUIC link with the terminal and transmit media data through the first QUIC link.

[0277] In one embodiment, the first message includes the media data parameters requested by the terminal, the second device stores the media data corresponding to the media data parameters, or the second device serves the media application corresponding to the media data parameters.

[0278] In one embodiment, the interface module 1001 is configured to receive a first message from the terminal, the first message being used to request session establishment. The interface module 1001 is further configured to send a second message to the data management function, requesting to obtain the subscription data of the terminal; and receive a response message from the data management function, the response message indicating that the terminal supports the first function and further including media data parameters supported by the terminal.

[0279] The processing module 1002 is configured to determine, from nodes supporting the first function, a second device that satisfies the media data parameters supported by the terminal.

[0280] In one embodiment, the first message includes first indication information, and the first indication information is used to indicate that the terminal requests to establish a QUIC-based media data transmission link.

[0281] In one embodiment, the interface module 1001 is also used to receive a first message from the edge application server discovery function, the first message including domain name information corresponding to the domain name system DNS server, the first message indicating that the terminal supports the first function, and including media data parameters requested by the terminal.

[0282] The processing module 1002 is configured to determine, based on the domain name information, a second device that satisfies the media data parameters requested by the terminal from among nodes that support the first function.

[0283] In one embodiment, the interface module 1001 is also used to receive second indication information from the second device or network storage function, where the second indication information indicates that the second device supports the first function, and the second indication information also includes media data parameters corresponding to the media data stored by the second device.

[0284] In one implementation, the interface module 1001 is further configured to receive third indication information from the second apparatus, where the third indication information indicates that the second apparatus does not support the media data parameters requested by the terminal.

[0285] In one embodiment, the interface module 1001 is also used to send a third message to the application function entity through the capability exposure interface, where the third message includes the media data parameters requested by the terminal and information about the second device; the third message is used to request the application server to establish a second QUIC link with the second device and transmit media data through the second QUIC link.

[0286] In one embodiment, the interface module 1001 is also used to send a fourth message to the data management function, wherein the fourth message includes the media data parameters requested by the terminal, and the fourth message is used to request information of the application server corresponding to the media data parameters requested by the terminal; receive a response message from the data management function, wherein the response message includes information of the first application server, wherein the first application server is used to establish a third QUIC link with the second device and transmit media data through the third QUIC link; and send information of the first application server to the second device.

[0287] In addition, the communication device 1000 can also be used to implement the terminal in the embodiments shown above.

[0288] The interface module 1001 is configured to send a first message to a first device, the first message including first indication information, the first indication information being used to instruct the terminal to request establishment of a QUIC-based media data transmission link. The interface module 1001 is further configured to establish a first QUIC link with a second device, and transmit media data corresponding to the media data parameters via the first QUIC link.

[0289] In one embodiment, the first message further includes media data parameters requested by the terminal, and the second device stores media data corresponding to the media data parameters, or the second device serves a media application corresponding to the media data parameters.

[0290] In addition, the communication device 1000 can also be used to implement the data management device in the above-mentioned embodiment, for example.

[0291] The interface module 1001 is configured to receive a second message from the first device, where the second message is used to request the acquisition of the subscription data of the terminal.

[0292] Processing module 1002 is used to determine the contract data corresponding to the terminal based on the second message and the contract data corresponding to at least one stored terminal, where the contract data includes that the terminal supports a first function, and the first function is a QUIC-based media data transmission function.

[0293] The interface module 1001 is further configured to send a response message to the first device, where the response message indicates that the terminal supports the first function, and the response message further includes media data parameters supported by the terminal.

[0294] In one implementation, the apparatus 1000 stores media data parameters supported by the terminal.

[0295] In one implementation, the interface module 1001 is further configured to obtain, through a capability exposure interface, information about the application server and parameters of media data supported for transmission by the application server based on the first function.

[0296] In addition, the communication device 1000 can also be used to implement, for example, the second device in the aforementioned embodiment, such as UPF.

[0297] The interface module 1001 is configured to send second indication information to the network storage function, where the second indication information indicates support for a first function, where the first function is a QUIC-based media data transmission function; or

[0298] The interface module 1001 is further configured to establish a node-level connection with the first device and send the second indication information to the first device.

[0299] In one embodiment, the second indication information further includes media data parameters corresponding to the media data stored in the device.

[0300] When the communication device 1000 is used to implement the functions of the first device, terminal, data management function or second device in the above embodiments, for other functions that the communication device 1000 can implement, please refer to the relevant introduction of the embodiments shown in Figures 4 to 9, and no further details will be given.

[0301] In a simple embodiment, those skilled in the art may conceive that the communication device 1000 may adopt the form shown in Figure 3. For example, the processor 301 in Figure 3 may call the computer-executable instructions stored in the memory 303 to enable the communication device 1000 to execute the method described in the above method embodiment.

[0302] Exemplarily, the functions / implementation processes of the processing module 1002 in FIG. 10 may be implemented by the processor 301 in FIG. 3 .

[0303] Exemplarily, the functions / implementation processes of the interface module 1001 in FIG. 10 may be implemented through the communication interface 304 in FIG. 3 .

[0304] It is understandable that one or more of the above modules or units can be implemented by software, hardware or a combination of the two. When any of the above modules or units is implemented by software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow. The processor can be built into an SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions to perform calculations or processing within the processor, it can further include necessary hardware accelerators, such as field programmable gate arrays (FPGAs), PLDs (programmable logic devices), or logic circuits that implement dedicated logic operations.

[0305] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0306] Optionally, the present application also provides a chip system, comprising: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instruction in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the chip system also includes a memory. Optionally, the chip system can be composed of a chip, or can include a chip and other discrete devices, which is not specifically limited in this application.

[0307] Optionally, the present application also provides a computer-readable storage medium. All or part of the processes in the above-mentioned method embodiments can be completed by a computer program to instruct the relevant hardware. The program can be stored in the above-mentioned computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The computer-readable storage medium can be an internal storage unit of the communication device of any of the above-mentioned embodiments, such as a hard disk or memory of the communication device. The above-mentioned computer-readable storage medium can also be an external storage device of the above-mentioned communication device, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. equipped on the above-mentioned communication device. Furthermore, the above-mentioned computer-readable storage medium can also include both the internal storage unit of the above-mentioned communication device and an external storage device. The above-mentioned computer-readable storage medium is used to store the above-mentioned computer program and other programs and data required by the above-mentioned communication device. The above-mentioned computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.

[0308] Optionally, the present application also provides a computer program product. All or part of the processes in the above method embodiments may be completed by a computer program instructing related hardware. The program may be stored in the above computer program product, and when executed, the program may include the processes in the above method embodiments.

[0309] Optionally, the present application also provides a computer instruction. All or part of the process in the above method embodiment can be completed by the computer instruction to instruct the relevant hardware (such as a computer, processor, network device or terminal, etc.). The program can be stored in the above computer-readable storage medium or in the above computer program product.

[0310] Optionally, the present application also provides a communication system, including: the first device and the second device in the above embodiment.

[0311] Optionally, the present application also provides a communication system, including: the first device and terminal in the above embodiment.

[0312] Optionally, the present application also provides a communication system, including: the first device, terminal and data management function in the above embodiment.

[0313] Optionally, the present application also provides a communication system, including: the first device, the terminal, the data management function and the second device in the above embodiment.

[0314] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0315] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0316] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0317] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0318] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: Applied to a first device, the method includes: Receiving a first message, the first message including a request for media data transmission by the terminal based on Quick Datagram Protocol Internet Connection (QUIC); A second device is determined based on the first message, wherein the second device supports a first function, the first function is a QUIC-based media data transmission function, and the second device is used to establish a first QUIC link with the terminal and transmit media data through the first QUIC link.

2. The method according to claim 1, characterized in that The first message includes media data parameters requested by the terminal, The second device stores the media data corresponding to the media data parameters, or the second device serves the media application corresponding to the media data parameters.

3. The method according to claim 1 or 2, characterized in that The receiving of the first message includes: receiving a first message from the terminal, where the first message is used to request session establishment; The determining the second device includes: Sending a second message to the data management function to request the terminal's subscription data; receiving a response message from the data management function, the response message indicating that the terminal supports the first function, the response message further including media data parameters supported by the terminal; According to the response message, a second device that meets the media data parameters supported by the terminal is determined from nodes that support the first function.

4. The method according to any one of claims 1 to 3, characterized in that The first message includes first indication information, and the first indication information is used to instruct the terminal to request to establish a QUIC-based media data transmission link.

5. The method according to claim 1 or 2, characterized in that The receiving of the first message includes: Receiving a first message from an edge application server discovery function, the first message including domain name information corresponding to a domain name system DNS server, indicating that the terminal supports the first function, and including media data parameters requested by the terminal; The determining the second device includes: Determine, based on the domain name information, a second device that satisfies the media data parameters requested by the terminal from among nodes that support the first function.

6. The method according to any one of claims 1 to 5, characterized in that The method comprises: Receive second indication information from the second device or the network storage function, where the second indication information indicates that the second device supports the first function, and the second indication information also includes media data parameters corresponding to the media data stored by the second device.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Third indication information is received from the second device, where the third indication information indicates that the second device does not support the media data parameters requested by the terminal.

8. The method according to claim 7, characterized in that The method comprises: A third message is sent to the application function entity through the capability exposure interface, where the third message includes the media data parameters requested by the terminal and information of the second device; the third message is used to request the application server to establish a second QUIC link with the second device and transmit media data through the second QUIC link.

9. The method according to claim 7, characterized in that The method comprises: Sending a fourth message to the data management function, where the fourth message includes the media data parameters requested by the terminal, and the fourth message is used to request information of an application server that supports the media data parameters requested by the terminal; receiving a response message from the data management function, the response message including information of a first application server, wherein the first application server is configured to establish a third QUIC link with the second device and transmit media data over the third QUIC link; Send information of the first application server to the second device.

10. A communication method, characterized in that: Applied to a terminal, the method includes: Sending a first message to a first device, where the first message includes first indication information, where the first indication information is used to instruct the terminal to request establishment of a QUIC-based media data transmission link; Establish a first QUIC link with the second device, and transmit media data corresponding to the media data parameters through the first QUIC link.

11. The method according to claim 10, characterized in that The first message also includes the media data parameters requested by the terminal, The second device stores the media data corresponding to the media data parameters, or the second device serves the media application corresponding to the media data parameters.

12. A communication method, characterized in that: Applied to data management functions, the method includes: receiving a second message from the first device, where the second message is used to request acquisition of subscription data of the terminal; Determining, according to the second message and the stored subscription data corresponding to the at least one terminal, the subscription data corresponding to the terminal, the subscription data including that the terminal supports a first function, where the first function is a QUIC-based media data transmission function; A response message is sent to the first device, where the response message indicates that the terminal supports the first function, and the response message also includes media data parameters supported by the terminal.

13. The method according to claim 12, characterized in that The data management function stores media data parameters supported by the terminal.

14. The method according to claim 12 or 13, characterized in that The method further comprises: The information of the application server and the media data parameters supported by the application server for transmission based on the first function are obtained through the capability exposure interface.

15. A communication method, characterized in that: Applied to the second device, the method includes: Sending second indication information to the network storage function, where the second indication information indicates support for the first function, where the first function is a QUIC-based media data transmission function; or Establish a node-level connection with the first device, and send the second indication information to the first device.

16. The method according to claim 15, characterized in that The second indication information also includes media data parameters corresponding to the media data stored in the second device.

17. A communication device, characterized in that: The device comprises: The interface module is configured to receive a first message, wherein the first message includes a request for media data transmission by the terminal based on a Quick Datagram Protocol Internet Connection (QUIC); The processing module is used to determine a second device based on the first message, wherein the second device supports a first function, the first function is a QUIC-based media data transmission function, and the second device is used to establish a first QUIC link with the terminal and transmit media data through the first QUIC link.

18. The device according to claim 17, characterized in that The first message includes media data parameters requested by the terminal, The second device stores the media data corresponding to the media data parameters, or the second device serves the media application corresponding to the media data parameters.

19. The device according to claim 17 or 18, characterized in that The interface module is used to receive a first message from the terminal, where the first message is used to request session establishment; The interface module is further configured to send a second message to the data management function, requesting to obtain the subscription data of the terminal; and receive a response message from the data management function, the response message indicating that the terminal supports the first function, the response message also including media data parameters supported by the terminal; The processing module is configured to determine, from nodes supporting the first function, a second device that satisfies media data parameters supported by the terminal.

20. The device according to any one of claims 17 to 19, characterized in that The first message includes first indication information, and the first indication information is used to instruct the terminal to request to establish a QUIC-based media data transmission link.

21. The device according to claim 17 or 18, characterized in that The interface module is further configured to receive a first message from the edge application server discovery function, the first message including domain name information corresponding to a domain name system DNS server, indicating that the terminal supports the first function, and including media data parameters requested by the terminal; The processing module is configured to determine, based on the domain name information, a second device that satisfies the media data parameters requested by the terminal from among nodes that support the first function.

22. The device according to any one of claims 17 to 21, characterized in that The interface module is further configured to receive second indication information from the second device or a network storage function, wherein the second indication information indicates that the second device supports the first function, and the second indication information further includes media data parameters corresponding to the media data stored in the second device.

23. The device according to any one of claims 17 to 22, characterized in that The interface module is further configured to receive third indication information from the second device, where the third indication information indicates that the second device does not support the media data parameters requested by the terminal.

24. The device according to claim 23, characterized in that The interface module is also used to send a third message to the application function entity through the capability exposure interface, where the third message includes the media data parameters requested by the terminal and information about the second device; the third message is used to request the application server to establish a second QUIC link with the second device and transmit media data through the second QUIC link.

25. The device according to claim 24, characterized in that The interface module is further configured to send a fourth message to the data management function, where the fourth message includes the media data parameters requested by the terminal, and the fourth message is used to request information of an application server that supports the media data parameters requested by the terminal; receiving a response message from the data management function, the response message including information of a first application server, wherein the first application server is configured to establish a third QUIC link with the second device and transmit media data over the third QUIC link; Send information of the first application server to the second device.

26. A communication device, characterized in that: The device comprises: An interface module, configured to send a first message to a first device, where the first message includes first indication information, where the first indication information is used to instruct the terminal to request establishment of a QUIC-based media data transmission link; The interface module is also used to establish a first QUIC link with the second device, and transmit the media data corresponding to the media data parameters through the first QUIC link.

27. The device according to claim 26, characterized in that The first message also includes the media data parameters requested by the terminal, The second device stores the media data corresponding to the media data parameters, or the second device serves the media application corresponding to the media data parameters.

28. A communication device, characterized in that: The device comprises: An interface module, configured to receive a second message from the first device, wherein the second message is used to request acquisition of subscription data of the terminal; a processing module, configured to determine, based on the second message and stored subscription data corresponding to at least one terminal, subscription data corresponding to the terminal, the subscription data including support for a first function by the terminal, where the first function is a QUIC-based media data transmission function; The interface module is further configured to send a response message to the first device, where the response message indicates that the terminal supports the first function, and the response message further includes media data parameters supported by the terminal.

29. The device according to claim 28, characterized in that The device stores media data parameters supported by the terminal.

30. The device according to claim 28 or 29, characterized in that The interface module is further configured to obtain information about the application server and media data parameters supported for transmission by the application server based on the first function through a capability exposure interface.

31. A communication device, characterized in that: The device comprises: an interface module, configured to send second indication information to the network storage function, where the second indication information indicates support for a first function, where the first function is a QUIC-based media data transmission function; or The interface module is further configured to establish a node-level connection with the first device and send the second indication information to the first device.

32. The device according to claim 31, characterized in that The second indication information also includes media data parameters corresponding to the media data stored in the device.

33. A communication device, characterized in that: include: A processor is coupled to a memory, wherein the memory is used to store a program or an instruction, and when the program or the instruction is executed by the processor, the method according to any one of claims 1 to 16 is performed.

34. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instructions are executed, the method according to any one of claims 1 to 16 is performed.

35. A computer program product, comprising computer program code, characterized in that: When the computer program code is run on a computer, the method according to any one of claims 1 to 16 is executed.

36. A communication system, characterized in that: The communication system comprises the apparatus according to any one of claims 17 to 25 and the apparatus according to any one of claims 26 to 27.

37. The communication system according to claim 36, wherein: The communication system further comprises an apparatus according to any one of claims 28-30 and / or an apparatus according to any one of claims 31-32.

Images