Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus, applied to the field of communications. In the technical solution provided by the present application, upon acquiring first media content transmitted by means of an MoQ protocol, a UPF entity can convert the transmission format of the first media content into a transmission format of a protocol supported by a terminal and send the transmission format to the terminal, so that a terminal that does not support an MoQ protocol can acquire media content transmitted by means of the MoQ protocol.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on February 27, 2024, with application number 202410217471.1 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] To improve the transmission performance of media content in a communication network, media content producers and / or relay nodes can transmit media content to media content consumers using the media over quick UDP internet connection (MoQ) protocol. However, this technical solution has the following problems: consumers must support the MoQ protocol, or consumers that do not support the MoQ protocol cannot obtain media content transmitted using the MoQ protocol. Summary of the Invention

[0004] The present application provides a communication method and a communication device, which can enable a terminal that does not support the media over quick user datagram protocol internet connection (MoQ) protocol to obtain media content transmitted through the MoQ protocol.

[0005] In a first aspect, the present application provides a communication method, which is applied to a user plane function UPF entity, and the method includes: obtaining first media content, where the first media content is media content transmitted to the UPF entity by an application server through a media MoQ protocol based on a fast user datagram protocol Internet connection; and sending the first media content to the terminal through a protocol supported by the terminal.

[0006] As an example, the method may be performed by a user plane function (UPF) entity, or may be performed by a chip system, hardware circuit, and / or software module applied to the UPF entity, or may be implemented by other devices capable of implementing the functions of the UPF entity, without limitation herein. It should be understood that the UPF entity is only an example and may also be referred to as a UPF network element or other names, without limitation herein.

[0007] As an example, media content can be understood as business data of real-time media services such as cloud gaming, audio and video conferencing, and live broadcasting.

[0008] As an example, the first media content may be understood as the media content of a subscribed service of the terminal, and the first media content is transmitted via a media over quick user datagram protocol internet connection (MoQ) protocol.

[0009] As an example, after the terminal completes registration and session establishment, the UPF entity can obtain the first media content based on the contract data of the terminal. For example, the UPF entity can obtain the first media content from the media content stored in the UPF entity. The media content stored in the UPF entity can be the media content transmitted to the UPF entity by the application server (AS) through the MoQ protocol. For another example, the AS can transmit the first media content to the UPF entity based on the contract data of the terminal, and accordingly, the UPF entity can receive the first media content. Among them, the AS can be understood as the server that provides the first media content.

[0010] As an example, after obtaining the first media content, the UPF entity may convert the transmission format of the first media content into a transmission format corresponding to a protocol supported by the terminal and then send the content to the terminal. For example, the UPF entity may encapsulate the protocol supported by the terminal for the first media content, or the UPF entity may add information about the protocol supported by the terminal to the front end of the first media content.

[0011] As an example, the protocols supported by the terminal may include at least one of the following: real-time transport protocol (RTP), real-time streaming protocol (RTSP), transmission control protocol (TCP), real-time transport control protocol (RTCP), or hypertext transfer protocol (HTTP).

[0012] In this technical solution, the UPF entity can obtain first media content for a terminal and send the first media content to the terminal via a protocol supported by the terminal, thereby enabling a terminal that does not support the MoQ protocol to obtain media content transmitted via the MoQ protocol. It should be noted that this technical solution does not impose any specific restrictions on the method by which the UPF entity determines the protocols supported by the terminal. For example, the protocols supported by the terminal can be stored in the terminal's contract data or pre-configured in the UPF entity in advance.

[0013] In combination with the first aspect, in certain implementations of the first aspect, before sending the first media content to the terminal through a protocol supported by the terminal, the method further includes: receiving first information from the terminal, the first information being used to request the first media content, the first information including a uniform resource locator (URL) of the first media content.

[0014] As an example, the first information may be an application layer message requesting to obtain or access the first media content, or the first information may be carried in an application layer message requesting to obtain or access the first media content, without limitation herein. In this example, after receiving the first information sent by the terminal, the UPF entity may send the obtained first media content to the terminal via a protocol supported by the terminal, thereby avoiding the UPF entity sending the first media content to the terminal immediately after obtaining it, thereby reducing communication overhead.

[0015] As an example, the first information may include a uniform resource locator (URL) of the first media content, so that the UPF entity can determine, based on the first information, that the media content that the terminal needs to obtain is the first media content. The URL may also be called a web page address.

[0016] In some embodiments, the terminal can send the first information according to its own needs, and the UPF entity can obtain the media content requested by the terminal based on the first information sent by the terminal, so that the terminal can obtain media content other than the contracted data, thereby improving the flexibility of the terminal in obtaining media content and enhancing the user experience.

[0017] In combination with the first aspect, in certain implementations of the first aspect, the URL includes indication information of the protocol supported by the terminal; wherein, sending the first media content to the terminal through the protocol supported by the terminal includes: determining the protocol supported by the terminal based on the URL; and when the protocol supported by the terminal does not include the MoQ protocol, sending the first media content to the terminal through the protocol supported by the terminal.

[0018] In this implementation, the UPF entity can determine the protocol supported by the terminal based on the indication information of the protocol supported by the terminal in the URL, and only when it is determined that the terminal does not support the MoQ protocol will the transmission format of the first media content be converted into a transmission format supported by the terminal.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the destination address of the first information includes the address of the UPF entity.

[0020] In this implementation, the destination address of the first information may include the address of the UPF entity, so that the UPF entity can receive the first information based on the destination address of the first information.

[0021] As an example, the first information may include a destination address, or in other words, the destination address of the first information may be included in the first information.

[0022] In combination with the first aspect, in certain implementations of the first aspect, before receiving the first information from the terminal, the method also includes: receiving second information from the terminal, the second information being used to request the address of the application server that provides the first media content; and sending third information to the terminal based on the second information, the third information indicating the address of the UPF entity.

[0023] As an example, the second information may be Domain Name System (DNS) request information, or the second information may be carried in the DNS request information. DNS is a system that converts domain names into Internet Protocol (IP) addresses. For example, when a terminal requests access to first media content on a website or webpage, it may send a DNS request.

[0024] In this implementation, the terminal device can obtain the destination address of the first information by sending the second information.

[0025] In combination with the first aspect, in certain implementations of the first aspect, the second information includes the formal domain name FQDN of the application server providing the first media content; wherein, sending the third information to the terminal based on the second information includes: when the FQDN is the FQDN pre-configured in the UPF entity, sending the third information to the terminal.

[0026] For example, when a terminal requests to access or obtain first media content on a website, the fully qualified domain name (FQDN) of the AS providing the first media content can be the FQDN of the website. It should be noted that the IP address corresponding to the website's FQDN is the IP address of the website's server, i.e., the IP address of the AS providing the first media content.

[0027] In this implementation, if the FQDN carried in the second information is the FQDN pre-configured in the UPF entity, the UPF entity can send third information indicating the address of the UPF entity to the terminal, so that the terminal can request the first media content from the UPF entity, and then the UPF entity can obtain the first media content for the terminal, and then the terminal that does not support the MoQ protocol can obtain the media content transmitted through the MoQ protocol.

[0028] In combination with the first aspect, in some implementations of the first aspect, obtaining the first media content includes: sending fourth information to the application server, where the fourth information is used to request the first media content; and receiving the first media content.

[0029] As an example, when the UPF entity obtains the first media content based on the terminal's contract, if the media content stored by the UPF entity does not include the first media content, it can send fourth information to the AS that provides the first media content to request to obtain the first media content.

[0030] As an example, after receiving the first information sent by the terminal, if the media content stored by the UPF entity does not include the first media content, the UPF entity can send fourth information to the AS that provides the first media content to request to obtain the first media content.

[0031] In combination with the first aspect, in some implementations of the first aspect, the fourth information includes a resource address of the first media content in the application server, and there is a mapping relationship between the resource address and the URL.

[0032] In this implementation, when the UPF entity requests the first media content from the AS, it may carry indication information of the first media content, so that the AS may know that the media content requested by the UPF entity is the first media content.

[0033] As an example, the fourth information may include the resource address of the first media content in the AS. It should be understood that the resource address may be replaced by a query parameter, a search parameter, or other parameters, as long as it can indicate the first media content, and is not limited here.

[0034] As an example, the fourth information may include at least one of the following first parameters: a first path name (track name), a first path identifier (track ID), or a first path alias (track alias). The first parameter is used to indicate the first media content, or the first parameter is a parameter corresponding to the first media content. It should be noted that track name, track ID and track alias can be collectively referred to as media content parameters, which are used to indicate specific media content. This application does not limit the specific names of track name, track ID and track alias. For example, track name can also be called program name, track ID can also be called program identifier, and track alias can also be called program alias.

[0035] It should be noted that, since the terminal does not support the MoQ protocol, when the terminal requests to obtain the first media content, it can only send the request information through the protocol supported by the terminal. For example, when the protocol supported by the terminal is the HTTP protocol, the terminal can send the request information through the HTTP protocol, or the request information sent by the terminal is an HTTP request. If the AS only supports the MoQ protocol, the AS cannot determine that the media content requested by the terminal is the first media content through the request information sent by the terminal, or the AS cannot parse the request information sent by the terminal. Therefore, the UPF entity requests the AS to obtain the first media content. When the UPF entity requests the first media content from the AS, it should transmit the request information through the protocol supported by the AS (such as the MoQ protocol) and carry the parameters indicating the first media content in the MoQ protocol, such as the track name, track ID or track alias. Therefore, the UPF entity needs to map the URL sent by the terminal to a track name, track ID or track alias, so that the AS can determine that the media content requested by the UPF entity is the first media content based on the track name, track ID or track alias. It should be understood that URL and track name, track ID or track alias are different forms of indicating the same media content in different protocols.

[0036] As an example, the mapping relationship between the URL and media content parameters such as track name, track ID or track alias can be pre-configured in the UPF entity in advance, or the UPF entity can obtain it through signaling, which is not limited here.

[0037] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: receiving fifth information, the fifth information instructing the UPF entity to activate the function of the relay node defined by the MoQ protocol; wherein, sending the first media content to the terminal through the protocol supported by the terminal includes: sending the first media content to the terminal through the protocol supported by the terminal based on the function of the relay node defined by the MoQ protocol.

[0038] It should be understood that the UPF entity should support the MoQ protocol so that the UPF entity can obtain the first media content transmitted via the MoQ protocol and convert the transmission format of the first media content into a transmission format supported by the terminal. Among them, the UPF entity supports the MoQ protocol, which can also be said to be the UPF entity having the function of a relay node defined by the MoQ protocol.

[0039] In this implementation, in order to enable the UPF entity to support the MoQ protocol, the session management function (SMF) entity can send fifth information to the UPF entity, and the fifth information instructs the UPF entity to activate the function of the relay node defined by the MoQ protocol. It should be noted that activating the function of the relay node defined by the MoQ protocol can be understood as configuring, enabling, turning on or enabling the function of the relay node defined by the MoQ protocol, which is not limited here. It should be understood that the UPF entity should have the ability to activate the function of the relay node defined by the MoQ protocol.

[0040] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending sixth information in response to the fifth information, the sixth information indicating that the UPF entity has activated the relay node function defined by the MoQ protocol.

[0041] In this implementation, after activating the function of the relay node defined by the MoQ protocol, the UPF entity may send response information to the SMF entity indicating that the function of the relay node defined by the MoQ protocol has been activated.

[0042] In combination with the first aspect, in certain implementations of the first aspect, the sending the first media content to the terminal through a protocol supported by the terminal includes: when the stream format of the first media content is a stream format supported by the terminal, sending the first media content to the terminal through the protocol supported by the terminal; when the stream format of the first media content is not a stream format supported by the terminal, converting the stream format of the first media content into a stream format supported by the terminal, and then sending the first media content to the terminal through the protocol supported by the terminal.

[0043] In this implementation, before the UPF entity sends the first media content to the terminal through a protocol supported by the terminal, it is also necessary to determine the stream format of the first media content. If the stream format of the first media content is a stream format supported by the terminal, the UPF entity can directly send the first media content to the terminal through the protocol supported by the terminal; if the stream format of the first media content is not a stream format supported by the terminal, the UPF entity needs to convert the stream format of the first media content to a stream format supported by the terminal before sending the first media content to the terminal through a protocol supported by the terminal, so that the terminal can receive the first media content. Among them, the stream format refers to a standardized data format used to store and transmit media content.

[0044] In a second aspect, the present application provides a communication method, which is applied to a terminal, and the method includes: determining seventh information, wherein the seventh information indicates that the user plane function UPF entity serving the terminal should support the media MoQ protocol based on the fast user datagram protocol Internet connection; and sending the seventh information to the session management function SMF entity.

[0045] As an example, the method can be executed by a terminal, or by a chip system, hardware circuit and / or software module applied to the terminal, or by other devices capable of implementing terminal functions, without limitation herein.

[0046] In this technical solution, in order to ensure that the UPF entity can obtain media content transmitted via the MoQ protocol for a terminal that does not support the MoQ protocol, the UPF entity should support the MoQ protocol. Therefore, the terminal can send the seventh information to the SMF entity to indicate that the UPF entity serving the terminal should support the MoQ protocol, so that the SMF entity can select the UPF entity for the terminal, and the UPF entity supports the MoQ protocol.

[0047] In combination with the second aspect, in some implementations of the second aspect, the seventh information includes an identifier of the terminal and / or a service type of the terminal, and the service type includes a service that uses the MoQ protocol to transmit service data.

[0048] As an example, the seventh information may include an identifier of the terminal and / or a service type of the terminal. As an example, the identifier of the terminal may be a user permanent identifier (SUPI) or other identifier, which is not limited here. As an example, the service type of the terminal may include MoQ service, which can be understood as a service that uses the MoQ protocol to transmit service data.

[0049] In combination with the second aspect, in some implementations of the second aspect, the seventh information is carried in a session establishment request message or a session establishment modification message.

[0050] As an example, the terminal may send the seventh information to the SMF entity when initiating a session establishment request or a session modification request. The seventh information may be carried in the session establishment request message or the session establishment modification message.

[0051] In a third aspect, the present application provides a communication method, which is applied to a session management function SMF entity, and the method includes: receiving seventh information, wherein the seventh information indicates that the user plane function UPF entity serving the terminal should support the media MoQ protocol based on the fast user datagram protocol Internet connection; based on the seventh information, selecting a first UPF entity for the terminal, and the first UPF entity supports the MoQ protocol.

[0052] As an example, the method can be executed by an SMF entity, or by a chip system, hardware circuit and / or software module applied to the SMF entity, or by other devices capable of implementing the functions of the SMF entity, without limitation here.

[0053] In this technical solution, the SMF entity can receive the seventh information sent by the terminal and select the first UPF entity for the terminal based on the seventh information. The first UPF entity supports the MoQ protocol, so that the first UPF entity can obtain media content transmitted through the MoQ protocol for the terminal, so that the terminal that does not support the MoQ protocol can obtain media content transmitted through the MoQ protocol.

[0054] In combination with the third aspect, in some implementations of the third aspect, the seventh information includes an identifier of the terminal and / or a service type of the terminal, and the service type includes a service that uses the MoQ protocol to transmit service data.

[0055] As an example, the seventh information may include the terminal identifier and / or the terminal's service type. As an example, the terminal identifier may be SUPI or other, which is not limited here. As an example, the terminal's service type may include MoQ service, which can be understood as a service that uses the MoQ protocol to transmit service data.

[0056] In combination with the third aspect, in some implementations of the third aspect, the seventh information is carried in a session establishment request message or a session establishment modification message.

[0057] As an example, the terminal may send the seventh information to the SMF entity when initiating a session establishment request or a session modification request. The seventh information may be carried in the session establishment request message or the session establishment modification message.

[0058] In combination with the third aspect, in certain implementations of the third aspect, selecting a first UPF entity for the terminal based on the seventh information, and the first UPF entity supports the MoQ protocol, includes: selecting the first UPF entity that supports the MoQ protocol for the terminal based on the seventh information.

[0059] As an example, when the SMF entity selects a UPF entity for the terminal, it can directly select the first UPF entity that supports the MoQ protocol.

[0060] In combination with the third aspect, in certain implementations of the third aspect, the selecting a first UPF entity for the terminal based on the seventh information, the first UPF entity supporting the MoQ protocol, includes: selecting the first UPF entity based on the seventh information; sending fifth information to the first UPF entity, the fifth information instructing the first UPF entity to activate the function of the relay node defined by the MoQ protocol.

[0061] As an example, when the SMF entity selects a UPF entity for the terminal, it can send fifth information to the first UPF entity after selecting the first UPF entity so that the first UPF entity can activate the relay node function defined by the MoQ protocol, or so that the first UPF entity supports the MoQ protocol.

[0062] In combination with the third aspect, in some implementations of the third aspect, the method further includes: receiving sixth information, where the sixth information indicates that the first UPF entity has activated the relay node function defined by the MoQ protocol.

[0063] As an example, after activating the function of the relay node defined by the MoQ protocol, the first UPF entity can send response information to the SMF entity to indicate that the function of the relay node defined by the MoQ protocol has been activated.

[0064] In a fourth aspect, the present application provides a communication device, which includes modules for implementing the method in the first aspect or any one of the implementation methods, and each module can be implemented in the form of hardware and / or software.

[0065] For example, the apparatus may include: a processing module and a sending module. The processing module is configured to obtain first media content, where the first media content is media content transmitted from an application server to the UPF entity via the MoQ protocol; and the sending module is configured to send the first media content to the terminal via a protocol supported by the terminal.

[0066] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the apparatus may further include a receiving module configured to receive first information from the terminal, the first information being used to request the first media content, the first information including a uniform resource locator (URL) of the first media content.

[0067] In combination with the fourth aspect, in certain implementations of the fourth aspect, the URL includes indication information of the protocol supported by the terminal; the processing module is further used to determine the protocol supported by the terminal based on the URL; and the sending module is specifically used to send the first media content to the terminal through the protocol supported by the terminal when the protocol supported by the terminal does not include the MoQ protocol.

[0068] In combination with the fourth aspect, in certain implementations of the fourth aspect, the destination address of the first information includes the address of the UPF entity.

[0069] In combination with the fourth aspect, in certain implementations of the fourth aspect, the receiving module is further used to receive second information from the terminal, and the second information is used to request the address of the application server that provides the first media content; the sending module is further used to send third information to the terminal based on the second information, and the third information indicates the address of the UPF entity.

[0070] In combination with the fourth aspect, in certain implementations of the fourth aspect, the second information includes the formal domain name FQDN of the application server providing the first media content; the sending module is specifically used to send the third information to the terminal when the FQDN is the FQDN pre-configured in the UPF entity.

[0071] In combination with the fourth aspect, in some implementations of the fourth aspect, the sending module is further used to send fourth information to the application server, where the fourth information is used to request the first media content; and the receiving module is further used to receive the first media content.

[0072] As an example, the processing module can be connected to the sending module and the receiving module. For example, the processing module can control the sending module to send information, and the processing module can control the receiving module to receive information.

[0073] In combination with the fourth aspect, in some implementations of the fourth aspect, the fourth information includes a resource address of the first media content in the application server, and there is a mapping relationship between the resource address and the URL.

[0074] In combination with the fourth aspect, in certain implementations of the fourth aspect, the receiving module is further used to receive fifth information, wherein the fifth information instructs the UPF entity to activate the function of the relay node defined by the MoQ protocol; the sending module is specifically used to send the first media content to the terminal through the protocol supported by the terminal based on the function of the relay node defined by the MoQ protocol.

[0075] In combination with the fourth aspect, in certain implementations of the fourth aspect, the sending module is further used to send sixth information in response to the fifth information, and the sixth information indicates that the UPF entity has activated the relay node function defined by the MoQ protocol.

[0076] In combination with the fourth aspect, in certain implementations of the fourth aspect, the processing module is further used to send the first media content to the terminal through a protocol supported by the terminal when the stream format of the first media content is a stream format supported by the terminal; the processing module is further used to convert the stream format of the first media content into a stream format supported by the terminal when the stream format of the first media content is not a stream format supported by the terminal, and then send the first media content to the terminal through a protocol supported by the terminal.

[0077] In a fifth aspect, the present application provides a communication device, which includes modules for implementing the method in the second aspect or any one of the implementation methods, and each module can be implemented in the form of hardware and / or software.

[0078] For example, the apparatus may include: a processing module and a sending module. The processing module is configured to determine seventh information, wherein the seventh information indicates that a user plane function (UPF) entity serving the terminal should support a media MoQ protocol based on a fast user datagram protocol internet connection; and the sending module is configured to send the seventh information to a session management function (SMF) entity.

[0079] In combination with the fifth aspect, in some implementations of the fifth aspect, the seventh information includes an identifier of the terminal and / or a service type of the terminal, and the service type includes a service that uses the MoQ protocol to transmit service data.

[0080] In combination with the fifth aspect, in certain implementations of the fifth aspect, the seventh information is carried in a session establishment request message or a session establishment modification message.

[0081] In a sixth aspect, the present application provides a communication device, which includes various modules for implementing the method in the third aspect or any one of the implementation methods therein, and each module can be implemented in the form of hardware and / or software.

[0082] For example, the apparatus may include: a receiving module and a processing module. The receiving module is configured to receive seventh information indicating that a user plane function (UPF) entity serving a terminal should support a media over fast user datagram protocol (UDP) internet connection (MoQ) protocol; and the processing module is configured to select a first UPF entity for the terminal based on the seventh information, the first UPF entity supporting the MoQ protocol.

[0083] In combination with the sixth aspect, in some implementations of the sixth aspect, the seventh information includes an identifier of the terminal and / or a service type of the terminal, and the service type includes a service that uses the MoQ protocol to transmit service data.

[0084] In combination with the sixth aspect, in certain implementations of the sixth aspect, the seventh information is carried in a session establishment request message or a session establishment modification message.

[0085] In combination with the sixth aspect, in some implementations of the sixth aspect, the processing module is specifically configured to select the first UPF entity that supports the MoQ protocol for the terminal based on the seventh information.

[0086] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the apparatus may further include a sending module. A processing module is specifically configured to select a first UPF entity based on the seventh information; and a sending module is configured to send fifth information to the first UPF entity, where the fifth information instructs the first UPF entity to activate a relay node function defined by the MoQ protocol.

[0087] As an example, the processing module can be connected to the sending module. For example, the processing module can control the sending module to send information.

[0088] In combination with the sixth aspect, in some implementations of the sixth aspect, the receiving module is further used to receive sixth information, where the sixth information indicates that the first UPF entity has activated the relay node function defined by the MoQ protocol.

[0089] In a seventh aspect, the present application provides a communication device, comprising a processor, the processor being coupled to a memory and configured to call program code in the memory to execute the method described in the first aspect or any possible implementation thereof. Optionally, the device further comprises a memory. Optionally, the device further comprises a communication interface, the processor being coupled to the communication interface.

[0090] As an example, the device can be a UPF entity, or a chip system, hardware circuit and / or software module applied in UPF, or other devices that can realize the functions of UPF entity, without limitation here.

[0091] In an eighth aspect, the present application provides a communication device, comprising a processor, the processor being coupled to a memory and configured to call program code in the memory to execute the method described in the second aspect or any possible implementation thereof. Optionally, the device further comprises a memory. Optionally, the device further comprises a communication interface, the processor being coupled to the communication interface.

[0092] As an example, the device may be a terminal, or a chip system, hardware circuit and / or software module applied in a terminal, or other devices that can implement terminal functions, which is not limited here.

[0093] In a ninth aspect, the present application provides a communication device, comprising a processor, the processor being coupled to a memory and configured to call program code in the memory to execute the method described in the second aspect or any possible implementation thereof. Optionally, the device further comprises a memory. Optionally, the device further comprises a communication interface, the processor being coupled to the communication interface.

[0094] As an example, the device may be an SMF entity, or a chip system, hardware circuit and / or software module applied to the SMF entity, or other devices that can implement the functions of the SMF entity, without limitation here.

[0095] In a tenth aspect, the present application provides a communication system, which includes the device in the fourth aspect or the seventh aspect, the device in the fifth aspect or the eighth aspect, and the device in the sixth aspect or the ninth aspect.

[0096] In an eleventh aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first aspect, the second aspect, the third aspect, or any possible implementation thereof.

[0097] In a twelfth aspect, the present application provides a computer-readable medium storing a program code for execution by a device, wherein the program code includes a method for executing the method described in the first aspect, the second aspect, the third aspect, or any possible implementation thereof.

[0098] For the technical effects that can be achieved by any of the above-mentioned aspects 4 to 12 and any possible design of any of them, please refer to the description of the technical effects that can be brought about by the above-mentioned aspects 1 to 3, and no further details will be given here. BRIEF DESCRIPTION OF THE DRAWINGS

[0099] FIG1 is a schematic diagram of a network architecture of a communication system provided by an embodiment of the present application;

[0100] FIG2 is an exemplary diagram illustrating a MoQ protocol architecture;

[0101] FIG3 is an exemplary flow chart of a communication method provided by one embodiment of the present application;

[0102] FIG3a is an exemplary diagram illustrating a method of transmitting first media content according to an embodiment of the present application;

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

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

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

[0106] FIG7 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

[0107] FIG8 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0108] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0109] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0110] To facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.

[0111] It should be noted that in the embodiments of 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.

[0112] In the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0113] It should be noted that the communication method and communication device provided in this application are based on the same technical concept. Since the principles of solving problems by the method and the device are similar, the implementation of the method and the device can refer to each other, and the repeated parts will not be repeated.

[0114] The technical solution provided in the present application can be applied to various communication systems, including but not limited to: narrowband Internet of Things (NB-IoT) system, global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), wireless fidelity (WiFi) system, third generation (3G) mobile communication system, long term evolution (LTE), advanced long term evolution (LTE-A), LTE frequency division duplex (FDD), LTE time division duplex (TDD), fourth generation (4G) mobile communication system, fifth generation (5G) mobile communication system. The three major application scenarios of the new wireless (NR) communication system are enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communication (mMTC), as well as the future sixth generation (6G) mobile communication system, such as high frequency, terahertz, and optical communication. This application does not impose specific restrictions on this.

[0115] Taking a 5G communication system as an example, Figure 1 is a schematic diagram of the network architecture of a communication system provided by an embodiment of the present application. As shown in Figure 1, the communication system includes a terminal, an access network, a core network, and a data network.

[0116] The terminal may also be referred to as user equipment (UE), which refers to a device that provides voice / data connectivity to a user. Currently, some examples of terminals include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, etc., which are not specifically limited in the embodiments of the present application. In the embodiments of the present application, the device for implementing the functions of the terminal can be the terminal itself, or a device that can support the terminal to implement the functions, such as a chip system. This device can be installed in the terminal, or it can be other equipment that can implement the functions of the terminal. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0117] The access network may be a (radio) access network (R)AN), which is used to provide wireless connectivity and is located between the UE and the core network (CN). As an example, the (R)AN may be a base station, a relay station, or an access point. The base station may be a base transceiver station (BTS) in a global system for mobile communication (GSM) or a code division multiple access (CDMA) network, a node base station (NB) in wideband code division multiple access (WCDMA), an evolutionary NB (eNB or eNodeB) in long term evolution (LTE), a wireless controller in a cloud radio access network (CRAN) scenario, a base station device in a future 5G network, an access network device in a future evolved PLMN network, or a wearable device or an in-vehicle device. In an embodiment of the present application, the device for implementing the function of the access network may be the access network itself, or it may be a device that can support the access network to implement the function, such as a chip system. The device can be installed in the access network, or it may be other equipment that can implement the function of the access network. There is no limitation here.

[0118] The core network includes but is not limited to the following functional entities: network slice-specific authentication and authorization function (NSSAAF) entity, authentication server function (AUSF) entity, access and mobility management function (AMF) entity, session management function (SMF) entity, service control point (SCP), network slice admission control function (NSACF) entity, edge application server discovery function (EASDF) entity, application function (AF) entity, unified data management function (UDM) entity, policy control function (PCF) entity, network repository function (NRF) entity, network exposure function (NEF) entity, network slice selection function (NSSF) entity, and user plane function (UPF) entity. In an embodiment of the present application, the device for implementing the functions of each functional entity in the core network may be the functional entity itself, or it may be a device that can support each functional entity to implement the function, such as a chip system. The device can be installed in each functional entity, or it may be other equipment that can implement the functions of each functional entity. There is no limitation here.

[0119] As an example, the main functions of the AMF entity include managing user registration, reachability detection, SMF entity selection, mobile state transition management, etc.

[0120] The SMF entity's main function is to control the establishment, modification, and deletion of sessions, the selection of user plane nodes, etc.

[0121] The UPF entity mainly functions as packet routing and forwarding, mobility anchor, uplink classifier to support routing service flows to the data network, branch point to support multi-homing protocol data unit (PDU) sessions, etc.

[0122] The main function of the PCF entity is a policy decision point, providing rules based on business data flow and application detection, gating, quality of service (QoS) and flow-based charging control.

[0123] The UDM entity's main function is to store user subscription data.

[0124] The AUSF entity's main function is to provide authentication services.

[0125] The AF entity's main function is to interact with the 3rd Generation Partnership Project (3GPP) core network to provide services, influence traffic routing, access network capability exposure, and policy control.

[0126] The NSSF entity's main function is to determine the network slice instance that the terminal is allowed to access based on the terminal's slice selection auxiliary information, contract data, etc.

[0127] The AUSF entity's main function is to provide authentication services.

[0128] The main function of the NEF entity is to securely open the services and capabilities provided by 3GPP network functions, such as third parties, edge computing, and AF.

[0129] A data network (DN) refers to a network that provides data transmission services to users, such as operator services, Internet access, or third-party services.

[0130] In this embodiment, the UE can access the DN by establishing a PDU session between the UE and the (R)AN and the UPF entity and the DN.

[0131] Referring to Figure 1 , it can be seen that the terminal, access network, UPF entity and DN are in the user plane, and other functional entities of the core network are in the control plane.

[0132] Referring to Figure 1, the UE and the AMF entity can communicate through the N1 interface, the (R)AN and the AMF entity can communicate through the N2 interface, the (R)AN and the UPF entity can communicate through the N3 interface, the UPF entity and the SMF entity can communicate through the N4 interface, the UPF entity and the DN can communicate through the N6 interface, and the UPF entities can communicate through the N9 interface.

[0133] As shown in Figure 1, the service-oriented interface provided by the NSSAF entity is Nmssaaf; the service-oriented interface provided by the AUSF entity is Nausf; the service-oriented interface provided by the AMF entity is Namf; the service-oriented interface provided by the SMF entity is Nsmf; the service-oriented interface provided by the NSACF entity is Nnsacf; the service-oriented interface provided by the EASDF entity is Neasdf; the service-oriented interface provided by the AF entity is Naf; the service-oriented interface provided by the UDM entity is Nudm; the service-oriented interface provided by the PCF entity is Npcf; the service-oriented interface provided by the NRF entity is Nnrf; the service-oriented interface provided by the NEF entity is Nnef; and the service-oriented interface provided by the NSSF entity is Nnssf.

[0134] The technical problem to be solved by this application is described below with reference to FIG2 .

[0135] With the evolution of computer technology and the expansion of its application scenarios, new network transmission protocols have emerged, such as the Media over Quick User Datagram Protocol (QUIC) (MoQ) protocol. MoQ defines a unified, low-latency, and highly scalable media distribution protocol and architecture based on the QUIC protocol. It can be applied to real-time media services such as cloud gaming, audio and video conferencing, and live streaming.

[0136] For example, Figure 2 illustrates an exemplary MoQ protocol architecture. As shown in Figure 2, the MoQ protocol architecture includes content consumers, relay nodes, and content producers. It should be understood that there can be multiple relay nodes, and this is not a limitation.

[0137] Among them, the subscription / publishing of media content can be carried out between content consumers and relay nodes, as well as between relay nodes and content producers, in the form of subscription / publishing. For example, content consumers can send subscription requests to relay nodes to obtain media content; relay nodes can receive subscription requests sent by content consumers, and determine whether the media content is stored in the relay nodes based on the received subscription requests. If the media content is stored in the relay nodes, the relay nodes can publish the media content to content consumers; if the media content is not stored in the relay nodes, the relay nodes can subscribe to the media content from the upper-level node (such as content producers) to obtain the media content, and publish the obtained media content to content consumers. It should be noted that media content can be understood as the business data of the above-mentioned real-time media services.

[0138] As an example, the content consumer may be a terminal, and the content producer may be an application server (AS) or an AF entity.

[0139] However, in this protocol architecture, media content subscription and publishing are both transmitted using the MoQ protocol, requiring content consumers to support the MoQ protocol. In other words, content consumers that do not support the MoQ protocol cannot obtain media content transmitted using the MoQ protocol. Therefore, how to enable content consumers that do not support the MoQ protocol to obtain media content transmitted using the MoQ protocol has become a pressing technical problem.

[0140] In view of this, the present application provides a communication method and a communication device. The present application provides a method for obtaining media content transmitted through the MoQ protocol for a terminal that does not support the MoQ protocol, or the present application proposes a method for providing media content transmitted through the MoQ protocol for a terminal that does not support the MoQ protocol. In the method provided by the present application, the UPF entity can convert media content transmitted using the MoQ protocol into media content transmitted by a protocol supported by the terminal, so that a terminal that does not support the MoQ protocol can obtain media content transmitted through the MoQ protocol. The present application can be applied to real-time media services such as cloud games, audio and video conferencing, and live broadcasts. As an example, the protocols supported by the terminal may include at least one of the following: real-time transport protocol (RTP), real-time streaming protocol (RTSP), transmission control protocol (TCP), real-time transport control protocol (RTCP), or hypertext transfer protocol (HTTP).

[0141] The communication method provided by the present application is described in detail below with reference to Figures 3 to 6. It should be understood that the terminal in the embodiment of the present application does not support the MoQ protocol.

[0142] Figure 3 is an exemplary flow chart of a communication method provided by an embodiment of the present application. As shown in Figure 3, the method may include S301 and S302.

[0143] As an example, the method can be performed by a UPF entity, or can be performed by a chip system, hardware circuit and / or software module applied to the UPF entity, or can be implemented by other devices that can implement the functions of the UPF entity, without limitation here.

[0144] S301: Acquire first media content, where the first media content is media content transmitted from an application server to a UPF entity through a MoQ protocol.

[0145] As an example, media content can be understood as business data for real-time media services such as cloud gaming, audio and video conferencing, and live broadcasts. It should be understood that media content can include one or more data packets. Media content can also be referred to as business data, data, etc., which is not limited in this application.

[0146] As an example, the first media content can be understood as the media content of a service contracted by the terminal. For example, when a user needs to watch a live broadcast through the terminal, they can sign a contract with the service provider of the service so that the terminal can obtain the media content of the service. The service provider of the service can be understood as the AS or AF entity that provides the service. In this embodiment, the first media content is media content transmitted via the MoQ protocol.

[0147] In some embodiments, the service provider of a service can only transmit the media content of the service through the MoQ protocol, or in other words, the server provider of the service can only provide media content transmitted through the MoQ protocol.

[0148] As an example, after the terminal completes registration and session establishment, the UPF entity can obtain the first media content based on the terminal's subscription data. For example, the UPF entity can obtain the first media content from the media content stored by the UPF entity. The media content stored by the UPF entity can be the media content transmitted to the UPF entity by the AS via the MoQ protocol. For another example, the AS can transmit the first media content to the UPF entity based on the terminal's subscription data, and the UPF entity can receive the first media content accordingly.

[0149] S302: Send first media content to the terminal through a protocol supported by the terminal.

[0150] In this embodiment, after acquiring the first media content, the UPF entity may send the first media content to the terminal through a protocol supported by the terminal.

[0151] As an example, after obtaining the first media content, the UPF entity may convert the transmission format of the first media content into the transmission format corresponding to the protocol supported by the terminal, and then send it to the terminal. For example, the UPF entity may encapsulate the protocol supported by the terminal for the first media content, or the UPF entity may add the protocol information supported by the terminal to the front end of the first media content. In some embodiments, before the UPF entity sends the first media content to the terminal through the protocol supported by the terminal, it is also necessary to judge the stream format of the first media content. If the stream format of the first media content is a stream format supported by the terminal, the UPF entity can directly send the first media content to the terminal through the protocol supported by the terminal; if the stream format of the first media content is not a stream format supported by the terminal, the UPF entity needs to convert the stream format of the first media content into a stream format supported by the terminal before sending the first media content to the terminal through the protocol supported by the terminal, so that the terminal can receive the first media content. Among them, the stream format refers to a standardized data format for storing and transmitting media content.

[0152] For example, Figure 3a illustrates an exemplary method for transmitting first media content, according to one embodiment of the present application. As shown in Figure 3a, the UPF entity obtains first media content transmitted via the MoQ protocol. When sending the first media content to a terminal, it must pass through the application layer and the transport layer. The application layer may include at least one stream format, such as stream format 1 through stream format N.

[0153] As an example, after the UPF entity obtains the first media content transmitted through the MoQ protocol, it needs to determine whether the stream format of the obtained first media content is a stream format supported by the terminal. If the stream format of the first media content is not a stream format supported by the terminal, the UPF entity can convert the stream format of the first media content into a stream format supported by the terminal in the application layer, and encapsulate the first media content after the stream format conversion with a protocol supported by the terminal (such as RTP, RTSP, RTCP, HTTP, etc.), and then send it to the terminal through the transport layer corresponding to the protocol supported by the terminal. It should be understood that if the stream format of the first media content is a stream format supported by the terminal, the UPF entity does not need to convert the stream format of the first media content. Among them, the stream format of the first media content obtained by the UPF entity can be the stream format used when the UPF entity saves the first media content, or the stream format used when the AS sends the first media content to the UPF entity.

[0154] It should be noted that this embodiment does not impose any specific restrictions on the method by which the UPF entity determines the protocols supported by the terminal. For example, the protocols supported by the terminal may be stored in the terminal's subscription data or may be pre-configured in the UPF entity in advance.

[0155] In this embodiment, the UPF entity can send the first media content transmitted through the MoQ protocol to the terminal through the protocol supported by the terminal, so that the terminal that does not support the MoQ protocol can also obtain the media content transmitted through the MoQ protocol, thereby improving communication efficiency.

[0156] In some implementations, after completing registration and session establishment, the terminal may actively request to obtain the first media content, and the UPF entity may send the first media content to the terminal through a protocol supported by the terminal based on the terminal's request information.

[0157] Figure 4 is an exemplary flow chart of a communication method provided in another embodiment of the present application. As shown in Figure 4, the method may include S401 to S406.

[0158] As an example, the method can be performed by a UPF entity, or can be performed by a chip system, hardware circuit and / or software module applied to the UPF entity, or can be implemented by other devices that can implement the functions of the UPF entity, without limitation here.

[0159] S401: Receive second information from a terminal, where the second information is used to request an address of an application server that provides first media content.

[0160] For example, after completing registration and establishing a session, if a terminal needs to access or obtain first media content, it can send second information to the UPF entity to request the address of the AS that provides the first media content. In response, the UPF entity can receive the second information. The first media content is media content transmitted using the MoQ protocol.

[0161] As an example, the second information may be Domain Name System (DNS) request information, or the second information may be carried in the DNS request information. DNS is a system that converts domain names into Internet Protocol (IP) addresses. For example, when a terminal requests to access or obtain first media content on a website, webpage, or application, it may send a DNS request.

[0162] As an example, the second information may include the fully qualified domain name (FQDN) of the AS that provides the first media content. The FQDN may also be called a fully qualified domain name.

[0163] As an example, when a terminal requests to access or obtain first media content on a website, the FQDN of the AS providing the first media content can be the FQDN of the website. It should be noted that the IP address corresponding to the FQDN of the website is the IP address of the website server, that is, the IP address of the AS providing the first media content.

[0164] S402: Send third information to the terminal, where the third information indicates the address of the UPF entity.

[0165] As an example, after receiving the second information, the UPF entity may send third information to the terminal based on the second information. For example, the UPF entity may determine the FQDN carried in the second information. If the FQDN carried in the second information is the FQDN pre-configured in the UPF entity, the UPF entity may send the third information to the terminal in response to the second information.

[0166] As an example, the third information may include the address of the UPF entity, or may include indication information of the address of the UPF entity.

[0167] It should be noted that if the FQDN carried in the second information is not the FQDN pre-configured in the UPF entity, the UPF entity may not send the third information to the terminal, or the UPF entity may only perform transparent forwarding. In this case, the address received by the terminal should be the address of the application server. It should be understood that when the FQDN carried in the second information is the FQDN pre-configured in the UPF entity, the UPF intercepts the second information and replaces the address of the application server with the address of the UPF entity, so that the UPF entity can obtain the first media content for the terminal.

[0168] As an example, the FQDN preconfigured in the UPF entity can be understood as one or more FQDNs preconfigured in the UPF entity.

[0169] As an example, the FQDN carried in the second information is the FQDN pre-configured in the UPF entity. It can be understood that the FQDN carried in the second information can be the same as or match one of the FQDNs pre-configured in the UPF entity.

[0170] As an example, the FQDN pre-configured in the UPF entity may be associated with the address of the UPF entity. The address of the UPF entity may be the IP address of the UPF entity.

[0171] In this embodiment, the FQDN preconfigured in the UPF entity can be set according to actual needs or obtained through signaling, and is not specifically limited here. In some embodiments, the IP address corresponding to the preconfigured FQDN can be the IP address of an AS that can only transmit media content via the MoQ protocol, or the IP address corresponding to the preconfigured FQDN can be the IP address of an AS that can only provide media content transmitted via the MoQ protocol.

[0172] As an example, when the second information is DNS request information, the third information may be DNS response information, or the third information may be carried in the DNS response information, which is not limited here.

[0173] S403: Receive first information from the terminal, where the first information is used to request first media content and includes a uniform resource locator of the first media content.

[0174] In this embodiment, after receiving the third information, the terminal may send the first information to the UPF entity based on the third information to request access to the first media content. Accordingly, the UPF entity may receive the first information. It should be understood that the destination address of the first information is the address of the UPF entity indicated by the third information.

[0175] As an example, the first information may be an application layer message requesting to obtain or access the first media content, or the first information may be carried in an application layer message requesting to obtain or access the first media content, which is not limited here.

[0176] As an example, the first information may include a uniform resource locator (URL) of the first media content to indicate the first media content. The URL may also be called a web page address.

[0177] As an example, the general format of a URL is protocol type: / / server address[:port number] / file name[parameter=value]. For example, the URL may be as follows: http: / / www.aspxfans.com:8080 / news / index_asp?boardID=5&ID=24618&page=1#name.

[0178] The protocol portion of the URL is "http:", indicating that the webpage uses the HTTP protocol. It should be understood that after receiving the URL, the UPF entity can determine the protocol supported by the terminal based on the protocol portion of the URL, such as the HTTP protocol in this example. Since the terminal does not support the MoQ protocol, the protocol portion of the URL sent by the terminal will not be the MoQ protocol, and the URL sent by the terminal can be considered a non-MoQ URL.

[0179] The domain name portion or server address of the URL is "www.aspxfans.com". In some embodiments, an IP address may also be used as the domain name.

[0180] The port part of the URL is "8080" after the domain name, and ":" is used as a separator between the domain name and the port.

[0181] The dummy directory portion of the URL is "new," which is the portion from the first " / " after the domain name to the last " / ." The dummy directory portion is not a required part of the URL.

[0182] The file name portion of the URL is "index_asp?", which is the portion from the last " / " after the domain name to the "?".

[0183] The parameter portion of the URL is "boardID=5&ID=24618&page=1," which is the portion between the "?" and the "#." The parameter portion can also be called the search portion or the query portion.

[0184] The anchor portion of the URL is "name". The anchor portion is not a required part of the URL.

[0185] S404: Send fourth information to the application server, where the fourth information is used to request the first media content.

[0186] As an example, after receiving the first message, the UPF entity may determine that the media content requested by the terminal is the first media content based on the URL carried in the first message, and obtain the first media content for the terminal. For example, the UPF entity may determine that the media content requested by the terminal is the first media content based on the parameter portion, file name portion, or other portion of the URL; and after determining the first media content, send fourth information to the AS that provides the first media content, requesting to obtain the first media content. In response, the AS may receive the fourth information.

[0187] As an example, the fourth information may include the resource address of the first media content in the AS, so that the AS can know that the media content requested by the UPF entity is the first media content. It should be understood that the resource address can be replaced by a query parameter, a search parameter, or other parameters, as long as it can indicate the first media content.

[0188] As an example, the fourth information may include at least one of the following first parameters: a first path name (track name), a first path identifier (track ID), or a first path alias (track alias). The first parameter is used to indicate the first media content, or the first parameter is a parameter corresponding to the first media content. It should be noted that track name, track ID and track alias can be collectively referred to as media content parameters, which are used to indicate specific media content. This application does not limit the specific names of track name, track ID and track alias. For example, track name can also be called program name, track ID can also be called program identifier, and track alias can also be called program alias.

[0189] It should be noted that, since the terminal does not support the MoQ protocol, when the terminal requests to obtain the first media content, it can only send the request information through the protocol supported by the terminal. For example, when the protocol supported by the terminal is the HTTP protocol, the terminal can send the request information through the HTTP protocol, or the request information sent by the terminal is an HTTP request. If the AS only supports the MoQ protocol, the AS cannot determine that the media content requested by the terminal is the first media content through the request information sent by the terminal, or the AS cannot parse the request information sent by the terminal. Therefore, in this application, the UPF entity requests the AS to obtain the first media content. When the UPF entity requests the first media content from the AS, it should transmit the request information through the protocol supported by the AS (such as the MoQ protocol) and carry the parameters indicating the first media content in the MoQ protocol, such as track name, track ID or track alias. Therefore, the UPF entity needs to map the URL sent by the terminal to a track name, track ID or track alias, so that the AS can determine that the media content requested by the UPF entity is the first media content based on the track name, track ID or track alias. It should be understood that URL and track name, track ID or track alias are different forms of indicating the same media content in different protocols. Therefore, the resource address included in the fourth information should be the address used to indicate the first media content in the MoQ protocol.

[0190] As an example, the mapping relationship between the URL and media content parameters such as track name, track ID or track alias can be pre-configured in the UPF entity in advance, or the UPF entity can obtain it through signaling, which is not limited here.

[0191] As an example, the mapping relationship between a URL and media content parameters such as a track name, track ID, or track alias can be a mapping relationship between key information in the URL and media content parameters such as the track name, track ID, or track alias. The key information in the URL can be, for example, a parameter portion, a file name portion, or other portion of the URL, which is not limited in this application.

[0192] In one possible implementation, the process of the UPF entity sending the fourth information to the AS can be understood as the process of the UPF entity subscribing to the first media content from the AS; and the process of the AS sending the first media content to the UPF entity can be understood as the process of the AS publishing the first media content to the UPF entity. In this implementation, the fourth information can include subscription parameters for the first media content. This application does not specifically limit the subscription parameters for the first media content. For example, the subscription parameters for the first media content can be the first parameter.

[0193] In this embodiment, the URL includes indication information of the protocols supported by the terminal, so that the UPF entity can determine the protocols supported by the terminal based on the URL sent by the terminal.

[0194] In some embodiments, when the protocol supported by the terminal does not include the MoQ protocol, the UPF entity may, after acquiring the first media content, convert the transmission format of the first media content into a transmission format corresponding to the protocol supported by the terminal and send it to the terminal.

[0195] S405: Receive first media content.

[0196] As an example, after receiving the fourth information, the AS may determine the first media content based on the fourth information and send the first media content to the UPF entity. Correspondingly, the UPF entity may receive the first media content sent by the AS.

[0197] S406: Send the first media content to the terminal through a protocol supported by the terminal.

[0198] As an example, after receiving the first media content sent by the AS, the UPF entity can send the first media content to the terminal through a protocol supported by the terminal. For details, please refer to S302, which will not be described in detail again. For example, when the terminal requests the first media content from the UPF entity through the HTTP protocol, the UPF entity can send the first media content to the terminal through the HTTP protocol.

[0199] In this embodiment, if the FQDN carried in the second information sent by the terminal is the FQDN pre-configured in the UPF entity, the UPF entity can intercept the second information and return the address of the UPF entity to the terminal, so that the terminal can request the UPF entity to obtain the first media content, and then the UPF entity can obtain the first media content for the terminal. After obtaining the first media content, the first media content is sent to the terminal through the protocol supported by the terminal, so that the terminal that does not support the MoQ protocol can obtain the media content transmitted through the MoQ protocol.

[0200] In some implementations, S404 and S405 may not be executed, that is, S406 may be executed directly after S403 is executed. For example, after receiving the first information and determining based on the first information that the media content requested by the terminal is the first media content, the UPF entity may determine whether the first media content exists in the media content stored in the UPF entity. If the first media content exists in the media content stored in the UPF entity, the UPF entity may directly extract the first media content from the media content stored in the UPF entity and transmit the first media content to the terminal through a protocol supported by the terminal, without having to obtain the first media content from the AS.

[0201] It should be understood that in an embodiment of the present application, the UPF entity should support the MoQ protocol so that the UPF entity can obtain the first media content transmitted via the MoQ protocol for the terminal and convert the transmission format of the first media content into the transmission format supported by the terminal. The UPF entity supports the MoQ protocol, which can also be referred to as the UPF entity having the function of a relay node defined by the MoQ protocol. It should be noted that the UPF entity has the function of a relay node defined by the MoQ protocol, which can be that the UPF entity itself has the function of a relay node defined by the MoQ protocol, or the UPF entity contains a device having the function of a relay node defined by the MoQ protocol, or the UPF entity can call a device having the function of a relay node defined by the MoQ protocol, without limitation. The function of the relay node defined by the MoQ protocol can refer to the relevant description in Figure 2 and will not be repeated here. In some embodiments, the function of the relay node defined by the MoQ protocol can be referred to as a MoQ relay function, and the device having the function of a relay node defined by the MoQ protocol can be referred to as a MoQ relay instance, without limitation. In some embodiments, the address of the UPF entity can be the address of the MoQ relay instance.

[0202] In one achievable manner, it is assumed that all UPF entities in the network support the MoQ protocol.

[0203] In one possible implementation, not all UPF entities in the network support the MoQ protocol. In this implementation, the SMF entity can select a UPF entity that supports the MoQ protocol for the terminal, or after selecting the UPF entity, instruct the UPF entity to activate the relay node function defined by the MoQ protocol.

[0204] Figure 5 is an exemplary flow chart of a communication method provided by another embodiment of the present application. As shown in Figure 5, the method may include S501 and S502.

[0205] S501, the terminal sends the seventh information to the SMF entity, and the seventh information indicates that the UPF entity serving the terminal should support the MoQ protocol.

[0206] As an example, the terminal may send the seventh information to the SMF entity to indicate that the UPF entity serving the terminal should support the MoQ protocol. Accordingly, the SMF entity may receive the seventh information.

[0207] As an example, the seventh information may be carried in a session establishment request message or a session establishment modification message. For example, the terminal may send the seventh information to the SMF entity when initiating a session establishment request or a session modification request.

[0208] As an example, the terminal can send the seventh information to the SMF entity through the AMF entity.

[0209] In some embodiments, the seventh information may include an identifier of the terminal and / or a service type of the terminal. As an example, the identifier of the terminal may be a user permanent identifier (SUPI) or other identifier, which is not limited here. As an example, the service type of the terminal may include a service that uses the MoQ protocol to transmit service data.

[0210] S502, the SMF entity selects a first UPF entity for the terminal based on the seventh information, and the first UPF entity supports the MoQ protocol.

[0211] As an example, the first UPF entity is a UPF entity serving the terminal.

[0212] In one achievable manner, after receiving the seventh information, the SMF entity may select the first UPF entity that supports the MoQ protocol based on the seventh information. For example, the SMF entity may select the first UPF entity during session establishment or session modification. It should be noted that this application does not limit the method by which the SMF entity obtains information on whether the UPF entity supports the MoQ protocol. For example, the SMF entity may send a request message to each UPF entity within the service scope of the SMF entity to request each UPF entity to report its own function, such as indicating information on whether the MoQ protocol is supported or indicating information on the supported protocol types. For another example, when registering for network access, the UPF entity may report its own functions to the SMF entity, such as indicating information on whether the MoQ protocol is supported or indicating information on the supported protocol types.

[0213] In one achievable manner, after receiving the seventh information, the SMF entity can select the first UPF entity based on the seventh information and send the fifth information to the first UPF entity, wherein the fifth information instructs the first UPF entity to activate the function of the relay node defined by the MoQ protocol. Accordingly, the first UPF entity can receive the fifth information and activate the function of the relay node defined by the MoQ protocol. It should be noted that the function of activating the relay node defined by the MoQ protocol can be understood as configuring, enabling, turning on or enabling the function of the relay node defined by the MoQ protocol, which is not limited here. It should be understood that in this implementation manner, the first UPF entity selected by the SMF entity has the ability to activate the function of the relay node defined by the MoQ protocol.

[0214] As an example, the fifth information may be carried in an N4 session, which is not limited here.

[0215] In some embodiments, after activating the function of the relay node defined by the MoQ protocol, the first UPF entity may send sixth information to the SMF entity in response to the fifth information, and the sixth information indicates that the first UPF entity has activated the function of the relay node defined by the MoQ protocol.

[0216] It should be noted that after the SMF entity selects the first UPF entity for the terminal, or after the session establishment or session modification is completed, the method in Figure 3 or Figure 4 can be used to enable the terminal that does not support the MoQ protocol to obtain media content transmitted via the MoQ protocol. It should be understood that the session establishment or session modification process may also include other steps, such as SMF entity selection and secondary authentication, which are not shown in this embodiment.

[0217] In this embodiment, the SMF entity can select a first UPF entity for the terminal based on the seventh information sent by the terminal, and the first UPF entity supports the MoQ protocol, so that the first UPF entity can obtain the first media content for the terminal that does not support the MoQ protocol.

[0218] In one possible implementation, the SMF entity can select a UPF entity to serve the terminal based on the protocol supported by the terminal. In this implementation, it is assumed that when the terminal supports the MoQ protocol, it will use a subscription method to obtain media content transmitted via the MoQ protocol, as shown in Figure 2; when the terminal does not support the MoQ protocol, it will obtain media content transmitted via the MoQ protocol through the UPF entity, as shown in Figure 3 or Figure 4. Therefore, the UPF entity selected by the SMF entity for a terminal that does not support the MoQ protocol should support the MoQ protocol, so that the UPF entity can obtain media content transmitted via the MoQ protocol for the terminal.

[0219] Figure 6 is an exemplary flow chart of a communication method provided in yet another embodiment of the present application. As shown in Figure 6 , the method may include S601 and S602.

[0220] As an example, the method can be performed by an SMF entity, or can be performed by a chip system, hardware circuit and / or software module applied to the SMF entity, or can be implemented by other devices that can implement the functions of the SMF entity, without limitation here.

[0221] S601: Acquire protocols supported by the terminal.

[0222] In one achievable manner, the SMF entity may obtain the contract data of the terminal from the UDM entity during the session establishment / modification process. The contract data of the terminal may include indication information of the protocols supported by the terminal, so that the SMF entity may obtain the protocols supported by the terminal. For example, the SMF entity may send a request message to the UDM entity to request the contract data of the terminal, or request the indication information of the protocols supported by the terminal in the contract data of the terminal.

[0223] As an example, the terminal's supported protocols indication information may include information indicating whether the terminal supports the MoQ protocol. For example, the terminal's supported protocols indication information is 1 bit. When the terminal's supported protocols indication information is "0," it indicates that the terminal does not support the MoQ protocol; when the terminal's supported protocols indication information is "1," it indicates that the terminal supports the MoQ protocol; or, when the terminal's supported protocols indication information is "0," it indicates that the terminal supports the MoQ protocol; when the terminal's supported protocols indication information is "1," it indicates that the terminal does not support the MoQ protocol. The specific setting can be based on actual needs and is not limited here.

[0224] As an example, the terminal's supported protocols indication information may include information indicating the protocol types supported by the terminal. For example, when the terminal's supported protocols indication information is "0," it indicates that the terminal supports HTTP, or when the terminal's supported protocols indication information is "0," it indicates that the terminal supports TCP. Specific settings can be made based on actual needs and are not specifically limited here.

[0225] As an example, the terminal's supported protocol indication information may include information indicating protocol types that the terminal does not support. For example, when the terminal's supported protocol indication information is "0," it indicates that the terminal does not support the protocol type "MoQ." For another example, when the terminal's supported protocol indication information is "0," it indicates that the terminal does not support the protocol type "TCP." This is not a limitation.

[0226] In one possible implementation, when initiating a session establishment request or a session modification request, the terminal sends an indication of the protocols supported by the terminal to the SMF entity, so that the SMF entity can obtain the protocols supported by the terminal. In this implementation, the indication of the protocols supported by the terminal can be carried in the session establishment request message or the session modification request message.

[0227] As an example, the terminal may carry information indicating the service type of the terminal in the session establishment request message, and the service type may include MoQ service. MoQ service can be understood as a service that uses the MoQ protocol to transmit service data. For example, the session establishment request message may carry an identifier of a network slice that supports the MoQ protocol and / or a DN identifier that supports the MoQ protocol. In this example, a class of service types, such as MoQ service, may be specifically defined for the terminal.

[0228] S602: Select a first UPF entity, which supports the MoQ protocol.

[0229] As an example, after the SMF entity obtains the protocol supported by the terminal, if the terminal does not support the MoQ protocol, the SMF entity can select a UPF entity that supports the MoQ protocol for the terminal, or the SMF entity can instruct the UPF entity to activate the relay node function defined by the MoQ protocol after selecting the UPF entity. For details, please refer to the relevant description in S502 and will not be repeated here.

[0230] In this embodiment, the SMF entity can select a UPF entity that supports the MoQ protocol for a terminal that does not support the MoQ protocol, or after selecting the UPF entity, instruct the selected UPF entity to activate the function of the relay node defined by the MoQ protocol, so that the terminal that does not support the MoQ protocol can request the UPF entity to obtain the media content transmitted through the MoQ protocol. For details, please refer to the relevant content in the aforementioned embodiments, which will not be repeated here.

[0231] It should be understood that the method in Figure 6 is only an example and not a limitation. For example, when the terminal supports the MoQ protocol, the first media content can also be obtained through the UPF entity, and in this case the UPF entity should also support the MoQ protocol.

[0232] In some implementations, when the terminal supports the MoQ protocol, the terminal can subscribe to media content from the relay node. Before the relay node publishes the media content to the terminal, the AF entity can dynamically calculate the publishing path of the media content and, when the UPF entity in the optimal publishing path does not support the MoQ protocol, send an instruction to the UPF entity to instruct the UPF entity to activate the relay node function defined by the MoQ protocol, so that the UPF entity can transmit the media content to the terminal, and then the relay node can publish the media content to the terminal through the optimal publishing path calculated by the AF entity, saving transmission power consumption. It should be noted that in this implementation, the AF entity can know the application server topology information in the communication network, so that it can dynamically calculate the publishing path of the media content; the AF entity can know the information of each node in the network (such as whether the UPF entity supports the MoQ protocol), so that it can ensure that the UPF entity in the determined optimal publishing path of the media content can transmit the media content through the MoQ protocol. The optimal publishing path can be understood as a publishing path whose path length is less than or equal to a preset threshold. The preset threshold can be set according to actual needs and is not limited here.

[0233] Figure 7 is a schematic diagram of the structure of a communication device provided in one embodiment of the present application. As shown in Figure 7, the device 700 of this embodiment can be used to implement the method shown in any of the aforementioned embodiments. As shown in Figure 7, the device 700 of this embodiment may include: a processing module 710, a sending module 720, and a receiving module 730.

[0234] As an example, the apparatus 700 may be used to implement the various steps / operations performed by the UPF entity in the method shown in FIG. 3 or FIG. 4 .

[0235] For example, when the apparatus 700 is used to implement the method implemented by the UPF entity in FIG. 3 , the processing module 710 can be used to implement S301 ; the sending module 720 can be used to implement the operation performed by the UPF entity in S302 .

[0236] When the device 700 is used to implement the method implemented by the UPF entity in Figure 4, the sending module 720 can be used to implement the operations performed by the UPF entity in S402, S404 and S406; the receiving module 730 can be used to implement the operations performed by the UPF entity in S401, S403 and S405.

[0237] As an example, the apparatus 700 may be used to implement the various steps / operations performed by the terminal in the method shown in FIG. 3 , FIG. 4 , or FIG. 5 .

[0238] For example, when the apparatus 700 is used to implement the method implemented by the terminal in FIG. 3 , the receiving module 730 may be used to implement the operation performed by the terminal in S302 .

[0239] When the apparatus 700 is used to implement the method implemented by the terminal in FIG. 4 , the sending module 720 may be used to implement the operations performed by the terminal in S401 and S403 ; the receiving module 730 may be used to implement the operations performed by the terminal in S402 and S406 .

[0240] When the apparatus 700 is used to implement the method implemented by the terminal in FIG. 5 , the sending module 720 may be used to implement the operation performed by the terminal in S501 .

[0241] As an example, the apparatus 700 may be used to implement the various steps / operations performed by the SMF entity in the method shown in FIG. 5 or FIG. 6 .

[0242] For example, when the apparatus 700 is used to implement the method implemented by the SMF entity in FIG. 5 , the processing module 710 may be used to implement S502 ; and the receiving module 730 may be used to implement the operation performed by the SMF entity in S501 .

[0243] When the apparatus 700 is used to implement the method implemented by the SMF entity in FIG6 , the processing module 710 may be used to implement S601 and S602 .

[0244] Figure 8 is a schematic diagram of the structure of a communication device provided in yet another embodiment of the present application. As shown in Figure 8, the device 800 is used to implement the method shown in any of the above embodiments.

[0245] As shown in Figure 8 , the apparatus 800 of this embodiment includes a memory 810, a processor 820, a communication interface 830, and a bus 840. The memory 810, the processor 820, and the communication interface 830 are connected to each other via the bus 840.

[0246] The memory 810 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 810 may store programs. When the program stored in the memory 810 is executed by the processor 820, the processor 820 is configured to perform the steps in any of the aforementioned embodiments.

[0247] The processor 820 may be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits to execute related programs.

[0248] The processor 820 may also be an integrated circuit chip with signal processing capabilities. In the implementation process, the various related steps in the embodiment of the present application may be completed by hardware integrated logic circuits in the processor 820 or software instructions.

[0249] The processor 820 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor 820 may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor.

[0250] The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-established in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 810, and processor 820 reads the information in memory 810 and, in conjunction with its hardware, completes the functions required to be performed by the units included in the apparatus of the present application.

[0251] Optionally, the memory 810 and the processor 820 may be integrated together.

[0252] The communication interface 830 may use, but is not limited to, a transceiver or other transceiver device to implement communication between the apparatus 800 and other devices or apparatuses.

[0253] The bus 840 may include a path for transmitting information between the various components of the device 800 (eg, the memory 810 , the processor 820 , and the communication interface 830 ).

[0254] Some embodiments of the present application also provide a computer program product that, when executed on a processor, can implement the method described in any of the above embodiments. Some embodiments of the present application also provide a computer-readable storage medium that contains computer instructions that, when executed on a processor, can implement the method described in any of the above embodiments.

[0255] It should be noted that the modules or components shown in the above embodiments may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), one or more microprocessors (digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented by a processing element calling a program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program code, such as a controller. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

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

[0257] It will be understood that the various numerical numbers involved in the embodiments of the present application are merely distinctions for the convenience of description and are not intended to limit the scope of the embodiments of the present application.

[0258] It can be understood that in the embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Claims

1. A communication method, characterized in that: The method is applied to a user plane function (UPF) entity, and the method includes: Acquire first media content, where the first media content is media content transmitted from an application server to the UPF entity through a media MoQ protocol based on a fast user datagram protocol internet connection; The first media content is sent to the terminal through a protocol supported by the terminal.

2. The method according to claim 1, characterized in that Before sending the first media content to the terminal using a protocol supported by the terminal, the method further includes: First information is received from the terminal, where the first information is used to request the first media content, and the first information includes a uniform resource locator (URL) of the first media content.

3. The method according to claim 2, characterized in that The URL includes information indicating the protocols supported by the terminal; The sending the first media content to the terminal by using a protocol supported by the terminal includes: determining a protocol supported by the terminal based on the URL; When the protocols supported by the terminal do not include the MoQ protocol, the first media content is sent to the terminal by using a protocol supported by the terminal.

4. The method according to claim 2 or 3, characterized in that The destination address of the first information includes the address of the UPF entity.

5. The method according to claim 4, characterized in that Before receiving the first information from the terminal, the method further includes: receiving second information from the terminal, where the second information is used to request an address of an application server that provides the first media content; Send third information to the terminal according to the second information, where the third information indicates the address of the UPF entity.

6. The method according to claim 5, characterized in that The second information includes the fully qualified domain name (FQDN) of the application server providing the first media content; The sending third information to the terminal according to the second information includes: When the FQDN is the FQDN pre-configured in the UPF entity, the third information is sent to the terminal.

7. The method according to any one of claims 2 to 6, characterized in that The acquiring of the first media content includes: Sending fourth information to the application server, where the fourth information is used to request the first media content; The first media content is received.

8. The method according to claim 7, characterized in that The fourth information includes the resource address of the first media content in the application server, and there is a mapping relationship between the resource address and the URL.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: receiving fifth information, where the fifth information instructs the UPF entity to activate a relay node function defined by the MoQ protocol; The sending the first media content to the terminal by using a protocol supported by the terminal includes: Based on the function of the relay node defined by the MoQ protocol, the first media content is sent to the terminal through a protocol supported by the terminal.

10. The method according to claim 9, characterized in that The method further comprises: In response to the fifth information, sixth information is sent, where the sixth information indicates that the UPF entity has activated the relay node function defined by the MoQ protocol.

11. The method according to any one of claims 1 to 10, characterized in that The sending the first media content to the terminal by using a protocol supported by the terminal includes: When the stream format of the first media content is a stream format supported by the terminal, sending the first media content to the terminal through a protocol supported by the terminal; When the stream format of the first media content is not a stream format supported by the terminal, the stream format of the first media content is converted into a stream format supported by the terminal, and then the first media content is sent to the terminal through a protocol supported by the terminal.

12. A communication method, characterized in that: The method is applied to a terminal, and includes: determining seventh information, the seventh information indicating that a user plane function (UPF) entity serving the terminal should support a media MoQ protocol based on a fast user datagram protocol internet connection; The seventh information is sent to the session management function SMF entity.

13. The method according to claim 12, characterized in that The seventh information includes the identifier of the terminal and / or the service type of the terminal, and the service type includes a service that uses the MoQ protocol to transmit service data.

14. The method according to claim 12 or 13, characterized in that The seventh information is carried in a session establishment request message or a session establishment modification message.

15. A communication method, characterized in that: The method is applied to a session management function (SMF) entity, and includes: receiving seventh information, wherein the seventh information indicates that the user plane function (UPF) entity serving the terminal should support the media MoQ protocol based on the fast user datagram protocol internet connection; A first UPF entity is selected for the terminal based on the seventh information, where the first UPF entity supports the MoQ protocol.

16. The method according to claim 15, characterized in that The seventh information includes the identifier of the terminal and / or the service type of the terminal, and the service type includes a service that uses the MoQ protocol to transmit service data.

17. The method according to claim 15 or 16, characterized in that The seventh information is carried in a session establishment request message or a session establishment modification message.

18. The method according to any one of claims 15 to 17, characterized in that The selecting a first UPF entity for the terminal based on the seventh information, where the first UPF entity supports the MoQ protocol, includes: The first UPF entity that supports the MoQ protocol is selected for the terminal based on the seventh information.

19. The method according to any one of claims 15 to 17, characterized in that The selecting a first UPF entity for the terminal based on the seventh information, where the first UPF entity supports the MoQ protocol, includes: Selecting a first UPF entity based on the seventh information; Send fifth information to the first UPF entity, where the fifth information instructs the first UPF entity to activate a relay node function defined by the MoQ protocol.

20. The method according to claim 19, characterized in that The method further comprises: Receive sixth information, where the sixth information indicates that the first UPF entity has activated a relay node function defined by the MoQ protocol.

21. A communication device, characterized in that: The method comprises various functional modules for implementing the method according to any one of claims 1 to 11, any one of claims 12 to 14, or any one of claims 15 to 20.

22. A communication device, characterized in that: include: A processor, the processor being coupled to a memory, the memory being used to store a computer program, wherein when the processor calls the computer program, the device is caused to perform the method according to any one of claims 1 to 11, any one of claims 12 to 14, or any one of claims 15 to 20.

23. A communication system, characterized in that: comprising communication means for performing the method of any one of claims 1 to 11 or any one of claims 12 to 14 or any one of claims 15 to 20.

24. A computer program product, characterized in that The method comprises a computer program code which, when executed on a computer, causes the computer to implement the method according to any one of claims 1 to 11, any one of claims 12 to 14, or any one of claims 15 to 20.

25. A computer-readable medium, characterized in that The computer-readable medium stores a program code for computer execution, the program code including instructions for executing the method according to any one of claims 1 to 11, any one of claims 12 to 14, or any one of claims 15 to 20.

Images