CN120567838A - Communication method and communication device - Google Patents
Communication method and communication deviceInfo
- Publication number
- CN120567838A CN120567838A CN202410217471.1A CN202410217471A CN120567838A CN 120567838 A CN120567838 A CN 120567838A CN 202410217471 A CN202410217471 A CN 202410217471A CN 120567838 A CN120567838 A CN 120567838A
- Authority
- CN
- China
- Prior art keywords
- terminal
- information
- media content
- protocol
- moq
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/756—Media network packet handling adapting media to device capabilities
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application provides a communication method and a communication device applied to the communication field. In the technical scheme provided by the application, after the UPF entity obtains the first media content transmitted through MoQ protocols, the UPF entity converts the transmission format of the first media content into the transmission format of the protocol supported by the terminal and sends the transmission format to the terminal, so that the terminal which does not support MoQ protocols can obtain the media content transmitted through MoQ protocols.
Description
Technical Field
The present application relates to the field of wireless communications, and in particular, to a communication method and a communication device.
Background
In a communication network, in order to improve the transmission performance of media content, a producer (producer) and/or a relay node (relay) of media content may transmit media content to consumers (consumers) of media content via a media over quick quench (MoQ) protocol based on a fast user datagram protocol (user datagram protocol, UDP) internet-connected media (media over quick UDP internet connection). The technical solution has the problem that the consumer must support MoQ protocol, or that the consumer not supporting MoQ protocol cannot obtain the media content transmitted through MoQ protocol.
Disclosure of Invention
The application provides a communication method and a communication device, which can enable a terminal which does not support a media (media over quick user datagram protocol internet connection, moQ) protocol based on a rapid user datagram protocol internet connection to acquire media content transmitted through a MoQ protocol.
In a first aspect, the present application provides a communication method, where the method 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 that an application server transmits to the UPF entity through a media MoQ protocol based on a rapid user datagram protocol internet connection, and sending the first media content to the terminal through a protocol supported by the terminal.
By way of example, the method may be performed by a user plane function (user plane function, UPF) entity, or may be performed by a system on a chip, hardware circuitry, and/or software modules applied in the UPF entity, or may be implemented by other devices capable of implementing the UPF entity function, without limitation. It should be understood that the UPF entity is only one example and may also be referred to as a UPF network element or other name, without limitation.
As an example, media content may be understood as service data of real-time media services such as cloud gaming, audio-video conferencing, live streaming, etc.
As an example, the first media content may be understood as media content of a subscription service of the terminal, the first media content being transmitted via a media (media over quick user datagram protocol internet connection, moQ) protocol based on a fast user datagram protocol internet connection.
As an example, after the terminal completes registration and session establishment, the UPF entity may obtain the first media content according to subscription data of the terminal. For example, the UPF entity can obtain a first media content from among the media content stored by the UPF entity. The media content held by the UPF entity may be media content that an application server (application server, AS) transmits to the UPF entity via the MoQ protocol. For another example, the AS may transmit the first media content to the UPF entity according to the subscription data of the terminal, and correspondingly, the UPF entity may receive the first media content. Wherein the AS may be understood AS a server providing the first media content.
As an example, after obtaining the first media content, the UPF entity may convert a transport format of the first media content into a transport format corresponding to a protocol supported by the terminal, and then send the transport format to the terminal. For example, the UPF entity may encapsulate a protocol supported by the terminal for the first media content, or the UPF entity may add protocol information supported by the terminal at the front end of the first media content.
By way of example, the protocols supported by the terminal may include at least one of real-time transport protocol (real-time transport protocol, RTP), real-time streaming protocol (REAL TIME STREAMING protocol, RTSP), transmission control protocol (transmission control protocol, TCP), real-time transmission control protocol (realtime transport control protocol, RTCP), or hypertext transfer protocol (hypertext transfer protocol, HTTP).
In the technical scheme, the UPF entity can acquire the first media content for the terminal and send the first media content to the terminal through a protocol supported by the terminal, so that the terminal which does not support MoQ protocol can acquire the media content transmitted through MoQ protocol. It should be noted that, in this technical solution, a method for determining a protocol supported by a terminal by a UPF entity is not specifically limited. For example, the protocols supported by the terminal may be stored in the subscription data of the terminal, or may be pre-configured in advance in the UPF entity.
With reference to the first aspect, in certain implementation manners of the first aspect, before the sending, by the protocol supported by the terminal, the first media content to the terminal, the method further includes receiving first information 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.
As an example, the first information may be an application layer message requesting to acquire or access the first media content, or the first information may be carried in an application layer message requesting to acquire or access the first media content, without limitation. In this example, the UPF entity may send the acquired first media content to the terminal through the protocol supported by the terminal after receiving the first information sent by the terminal, which avoids sending the first media content to the terminal after the UPF entity acquires the first media content, and reduces communication overhead.
As an example, the first information may include a uniform resource locator (uniform resource locator, URL) of the first media content, such that the UPF entity may 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 referred to as a web page address.
In some embodiments, the terminal may send the first information according to its own requirement, and the UPF entity may obtain the media content requested by the terminal based on the first information sent by the terminal, so that the terminal may obtain media content other than subscription data, which improves flexibility of the terminal in obtaining media content, and improves user experience.
With reference to the first aspect, in some implementation manners of the first aspect, the URL includes indication information of a protocol supported by the terminal, where the sending, by the protocol supported by the terminal, the first media content to the terminal includes determining, based on the URL, the protocol supported by the terminal, and sending, by the protocol supported by the terminal, the first media content to the terminal when the protocol supported by the terminal does not include the MoQ protocol.
In this implementation, the UPF entity may determine a protocol supported by the terminal based on the indication information of the protocol supported by the terminal in the URL, and may convert the transport format of the first media content into the transport format supported by the terminal when determining that the terminal does not support the MoQ protocol.
With reference to the first aspect, in certain implementations of the first aspect, the destination address of the first information includes an address of the UPF entity.
In this implementation, the destination address of the first information may comprise an address of the UPF entity, such that the UPF entity may receive the first information based on the destination address of the first information.
As an example, the first information may contain a destination address, or the destination address of the first information may be contained in the first information.
With reference to the first aspect, in certain implementation manners of the first aspect, before the receiving the first information from the terminal, the method further includes receiving second information from the terminal, where the second information is used for requesting an address of an application server that provides the first media content, and sending third information to the terminal according to the second information, where the third information indicates an address of the UPF entity.
As an example, the second information may be Domain Name System (DNS) request information, or the second information may be carried in DNS request information. DNS is a system that converts domain names into internet protocol addresses (internet protocol, IP) addresses. For example, the DNS request may be sent when the terminal requests access to the first media content on a website or web page.
In this implementation, the terminal device may obtain the destination address of the first information by sending the second information.
With reference to the first aspect, in some implementation manners of the first aspect, the second information includes a formal domain name FQDN of an application server that provides the first media content, and the sending third information to the terminal according to the second information includes sending the third information to the terminal when the FQDN is a FQDN preconfigured in the UPF entity.
AS an example, when a terminal requests access to or acquisition of a first media content on a website, the formal domain name (fully qualified domain name, FQDN) of the AS providing the first media content may 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.
In this implementation manner, if the FQDN carried in the second information is a preconfigured FQDN in the UPF entity, the UPF entity may send third information indicating an address of the UPF entity to the terminal, so that the terminal may request the first media content to the UPF entity, further, the UPF entity may acquire the first media content for the terminal, and further, the terminal that does not support MoQ protocols may acquire media content transmitted through MoQ protocols.
With reference to the first aspect, in certain implementation manners of the first aspect, the acquiring 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.
AS an example, when the UPF entity acquires the first media content based on the subscription of the terminal, if the media content stored in the UPF entity does not include the first media content, the UPF entity may send fourth information to the AS providing the first media content, so AS to request to acquire the first media content.
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 may send fourth information to the AS that provides the first media content, so AS to request to obtain the first media content.
With reference to the first aspect, in certain implementation manners of the first aspect, the fourth information includes a resource address of the first media content in the application server, where the resource address has a mapping relationship with the URL.
In this implementation, when the UPF entity requests the first media content from the AS, the UPF entity may carry indication information of the first media content, so that the AS may know that the media content requested to be acquired by the UPF entity is the first media content.
AS an example, the fourth information may contain a resource address of the first media content in the AS. It should be appreciated that the resource address may be replaced with a query parameter, a search parameter, or otherwise, so long as the first media content may be indicated, without limitation.
As an example, the fourth information may include at least one of a first path name (TRACK NAME), a first path identification (track ID), or a first path alias (TRACK ALIAS). The first parameter is used for indicating the first media content, or the first parameter is a parameter corresponding to the first media content. Note that TRACK NAME, track ID, and TRACK ALIAS may be collectively referred to as media content parameters for indicating specific media content. The specific names of TRACK NAME, track ID, and TRACK ALIAS are not limited in this disclosure. For example TRACK NAME may also be referred to as a program name, track ID may also be referred to as a program identification, TRACK ALIAS may also be referred to as a program alias.
It should be noted that, since the terminal does not support MoQ protocols, the terminal can only send the request information through the protocol supported by the terminal when requesting to acquire the first media content, for example, when the protocol supported by the terminal is HTTP, the terminal can send the request information through HTTP protocol, or the request information sent by the terminal is an HTTP request. If the AS only supports MoQ protocols, the AS cannot determine that the media content requested by the terminal is the first media content according to the request information sent by the terminal, or the AS cannot parse the request information sent by the terminal, so that the UPF entity requests the AS to acquire the first media content. When the UPF entity requests the first media content from the AS, the request information should be transmitted through a protocol supported by the AS (such AS MoQ protocol), and carries MoQ parameters indicating the first media content in the protocol, such AS TRACK NAME, track ID or TRACK ALIAS. Thus, the UPF entity needs to map the URL sent by the terminal to TRACK NAME, track ID or TRACK ALIAS so that the AS can determine the media content requested by the UPF entity AS the first media content based on TRACK NAME, track ID or TRACK ALIAS. It should be appreciated that URL and TRACK NAME, track ID or TRACK ALIAS are different versions of the same media content indicated in different protocols.
As an example, the mapping between the URL and TRACK NAME, track ID or TRACK ALIAS, etc. media content parameters may be pre-configured in the UPF entity in advance, or the UPF entity may be acquired through signaling, without limitation.
With reference to the first aspect, in certain implementation manners of the first aspect, the method further includes receiving fifth information, where the fifth information indicates that the UPF entity activates a function of the relay node defined by the MoQ protocol, and where the sending, by the protocol supported by the terminal, the first media content to the terminal includes sending, by the protocol supported by the terminal, the first media content to the terminal based on the function of the relay node defined by the MoQ protocol.
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 through the MoQ protocol and convert the transmission format of the first media content into a transmission format supported by the terminal. The UPF entity supports MoQ protocol, and may also be called as a UPF entity having the function of a relay node defined by MoQ protocol.
In this implementation, in order for the UPF entity to support the MoQ protocol, the session management function (session management function, SMF) entity may send fifth information to the UPF entity, the fifth information instructing the UPF entity to activate the functionality 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 may be understood as configuring, enabling, starting or enabling the function of the relay node defined by the MoQ protocol, which is not limited herein. It should be appreciated that the UPF entity should be capable of activating the functions of the relay node defined by the MoQ protocol.
With reference to the first aspect, in certain implementation manners of the first aspect, the method further includes transmitting sixth information in response to the fifth information, the sixth information indicating that the UPF entity has activated a function of the relay node defined by the MoQ protocol.
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.
With reference to the first aspect, in some implementation manners of the first aspect, the sending the first media content through the protocol supported by the terminal includes sending the first media content through the protocol supported by the terminal to the terminal when the stream format of the first media content is the stream format supported by the terminal, and after converting the stream format of the first media content into the stream format supported by the terminal when the stream format of the first media content is not the stream format supported by the terminal, sending the first media content through the protocol supported by the terminal to the terminal.
In the implementation manner, before the UPF entity sends the first media content to the terminal through the protocol supported by the terminal, the UPF entity needs to judge the stream format of the first media content, if the stream format of the first media content is the 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, and if the stream format of the first media content is not the stream format supported by the terminal, the UPF entity needs to convert the stream format of the first media content into the 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. Where streaming format refers to a standardized data format for storing and transmitting media content.
In a second aspect, the application provides a communication method applied to a terminal, the method comprising 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 rapid user datagram protocol internet connection, and sending the seventh information to a session management function SMF entity.
By way of example, the method may be performed by a terminal, by a chip system, a hardware circuit and/or a software module applied in a terminal, or by other devices capable of implementing the functions of a terminal, without limitation.
In the technical scheme, in order to ensure that the UPF entity can acquire the media content transmitted through the MoQ protocol for the terminal which does not support the MoQ protocol, the UPF entity should support the MoQ protocol. Thus, the terminal may send seventh information to the SMF entity to indicate that the UPF entity serving the terminal should support MoQ protocols, so that the SMF entity may select the UPF entity for the terminal, the UPF entity supporting MoQ protocols.
With reference to the second aspect, in certain implementations of the second aspect, the seventh information includes an identification of the terminal and/or a service type of the terminal, where the service type includes a service for transmitting service data using the MoQ protocol.
As an example, the seventh information may contain an identification of the terminal and/or a traffic type of the terminal. As an example, the identity of the terminal may be a user permanent identifier (subscription PERMANENT IDENTIFIER, SUPI) or others, without limitation. As an example, the service type of the terminal may include MoQ services, and MoQ services may be understood as services for transmitting service data using the MoQ protocol.
With reference to the second aspect, in certain implementations of the second aspect, the seventh information is carried in a session establishment request message or a session establishment modification message.
As an example, the terminal may send seventh information to the SMF entity when initiating the session establishment request or the session modification request, and the seventh information may be carried in the session establishment request message or the session establishment modification message.
In a third aspect, the present application provides a communication method applied to a session management function, SMF, entity, the method comprising receiving seventh information indicating that a user plane function, UPF, entity serving a terminal shall support a media MoQ protocol based on a fast user datagram protocol, internet connection, selecting a first UPF entity for the terminal based on the seventh information, the first UPF entity supporting the MoQ protocol.
By way of example, the method may be performed by an SMF entity, by a system-on-chip, hardware circuitry, and/or software modules applied in the SMF entity, or by other means capable of implementing the functions of the SMF entity, without limitation.
In the technical scheme, the SMF entity may receive the seventh information sent by the terminal, and select the first UPF entity for the terminal based on the seventh information, where the first UPF entity supports MoQ protocols, so that the first UPF entity may acquire, for the terminal, media content transmitted through MoQ protocols, and thus, a terminal that does not support MoQ protocols may acquire media content transmitted through MoQ protocols.
With reference to the third aspect, in certain implementations of the third aspect, the seventh information includes an identification of the terminal and/or a service type of the terminal, where the service type includes a service for transmitting service data using the MoQ protocol.
As an example, the seventh information may contain an identification of the terminal and/or a traffic type of the terminal. As an example, the identity of the terminal may be SUPI or otherwise, without limitation. As an example, the service type of the terminal may include MoQ services, and MoQ services may be understood as services for transmitting service data using the MoQ protocol.
With reference to 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.
As an example, the terminal may send seventh information to the SMF entity when initiating the session establishment request or the session modification request, and the seventh information may be carried in the session establishment request message or the session establishment modification message.
With reference to the third aspect, in some 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 supporting the MoQ protocol for the terminal based on the seventh information.
As an example, when the SMF entity selects a UPF entity for a terminal, the SMF entity may directly select the first UPF entity supporting MoQ protocols.
With reference to the third aspect, in some implementations of the third aspect, 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, and sending fifth information to the first UPF entity, where the fifth information indicates that the first UPF entity activates a function of a relay node defined by the MoQ protocol.
As an example, when the SMF entity selects a UPF entity for the terminal, after selecting the first UPF entity, fifth information may be sent to the first UPF entity, so that the first UPF entity may activate the function of the relay node defined by the MoQ protocol, or so that the first UPF entity supports the MoQ protocol.
With reference to the third aspect, in certain implementations of the third aspect, the method further includes receiving sixth information indicating that the first UPF entity has activated a function of the relay node defined by the MoQ protocol.
As an example, the first UPF entity may send response information to the SMF entity after activating the function of the relay node defined by the MoQ protocol to indicate that the function of the relay node defined by the MoQ protocol has been activated.
In a fourth aspect, the present application provides a communications apparatus comprising means for implementing the method of the first aspect or any one of the implementations, each of the means being implemented in hardware and/or software.
For example, the apparatus may include a processing module and a transmitting module. The system comprises a processing module for acquiring first media content, a sending module for sending the first media content to a terminal through a protocol supported by the terminal, wherein the first media content is media content which is transmitted to the UPF entity by an application server through MoQ protocol.
With reference to the fourth aspect, in some implementations of the fourth aspect, the apparatus may further include a receiving module. And the receiving module is used for receiving first information from the terminal, wherein the first information is used for requesting the first media content and comprises a Uniform Resource Locator (URL) of the first media content.
With reference to the fourth aspect, in some implementations of the fourth aspect, the URL includes indication information of a protocol supported by the terminal, the processing module is further configured to determine the protocol supported by the terminal based on the URL, and the sending module is specifically configured 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.
With reference to the fourth aspect, in certain implementations of the fourth aspect, the destination address of the first information includes an address of the UPF entity.
With reference to the fourth aspect, in some implementations of the fourth aspect, the receiving module is further configured to receive 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, and the sending module is further configured to send third information to the terminal according to the second information, where the third information indicates an address of the UPF entity.
With reference to the fourth aspect, in some implementations of the fourth aspect, the second information includes a formal domain name FQDN of an application server that provides the first media content, and the sending module is specifically configured to send the third information to the terminal when the FQDN is a FQDN preconfigured in the UPF entity.
With reference to the fourth aspect, in some implementations of the fourth aspect, the sending module is further configured 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 configured to receive the first media content.
As an example, the processing module may be connected with the transmitting module and the receiving module. For example, the processing module may control the sending module to implement sending of the information, and the processing module may control the receiving module to implement receiving of the information.
With reference to 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, where the resource address has a mapping relationship with the URL.
With reference to the fourth aspect, in some implementations of the fourth aspect, the receiving module is further configured to receive fifth information, where the fifth information indicates that the UPF entity activates a function of a relay node defined by the MoQ protocol, and the sending module is specifically configured to send the first media content to the terminal through a protocol supported by the terminal based on the function of the relay node defined by the MoQ protocol.
With reference to the fourth aspect, in some implementations of the fourth aspect, the sending module is further configured to send sixth information in response to the fifth information, where the sixth information indicates that the UPF entity has activated a function of the relay node defined by the MoQ protocol.
With reference to the fourth aspect, in some implementations of the fourth aspect, the processing module is further configured 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 the stream format supported by the terminal, and the processing module is further configured to, when the stream format of the first media content is not the stream format supported by the terminal, convert the stream format of the first media content to the stream format supported by the terminal, and then send the first media content to the terminal through the protocol supported by the terminal.
In a fifth aspect, the present application provides a communications apparatus comprising means for implementing the method of the second aspect or any one of the implementations, each of the means being implemented in hardware and/or software.
For example, the apparatus may include a processing module and a transmitting module. The system comprises a processing module for determining seventh information, a transmitting module for transmitting the seventh information to a session management function SMF entity, wherein the seventh information indicates that a user plane function UPF entity serving the terminal should support a media MoQ protocol based on a rapid user datagram protocol (UPP) internet connection.
With reference to the fifth aspect, in certain implementations of the fifth aspect, the seventh information includes an identification of the terminal and/or a service type of the terminal, where the service type includes a service for transmitting service data using the MoQ protocol.
With reference to 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.
In a sixth aspect, the present application provides a communications apparatus comprising means for implementing the method of the third aspect or any one of the implementations, each of the means being implemented in hardware and/or software.
For example, the apparatus may include a receiving module and a processing module. The terminal comprises a receiving module for receiving 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 rapid user datagram protocol (UPP) internet connection, and a processing module for selecting a first UPF entity for the terminal based on the seventh information, and the first UPF entity supports the MoQ protocol.
With reference to the sixth aspect, in certain implementations of the sixth aspect, the seventh information includes an identification of the terminal and/or a service type of the terminal, where the service type includes a service for transmitting service data using the MoQ protocol.
With reference to the sixth aspect, in some implementations of the sixth aspect, the seventh information is carried in a session establishment request message or a session establishment modification message.
With reference to the sixth aspect, in some implementations of the sixth aspect, a processing module is specifically configured to select, for the terminal, the first UPF entity supporting the MoQ protocol based on the seventh information.
With reference to the sixth aspect, in some implementations of the sixth aspect, the apparatus may further include a transmitting module. The system comprises a processing module, a transmitting module and a receiving module, wherein the processing module is specifically used for selecting a first UPF entity based on the seventh information, and the transmitting module is used for transmitting fifth information to the first UPF entity, wherein the fifth information indicates the first UPF entity to activate the function of the relay node defined by the MoQ protocol.
As an example, the processing module may be connected with the transmitting module. For example, the processing module may control the sending module to effect the sending of the information.
With reference to the sixth aspect, in certain implementation manners of the sixth aspect, the receiving module is further configured to receive sixth information, where the sixth information indicates that the first UPF entity has activated a function of the relay node defined by the MoQ protocol.
In a seventh aspect, the present application provides a communications apparatus comprising a processor, the processor being couplable to a memory for invoking program code in the memory to perform a method as described in the first aspect or any one of the possible implementations. Optionally, the apparatus further comprises a memory. Optionally, the apparatus further comprises a communication interface, and the processor may be coupled with the communication interface.
By way of example, the device may be a UPF entity, a system on chip, a hardware circuit and/or a software module applied in a UPF, or other devices that may implement the functionality of a UPF entity, without limitation.
In an eighth aspect, the present application provides a communications apparatus comprising a processor, the processor being couplable to a memory for invoking program code in the memory to perform a method as described in the second aspect or any one of the possible implementations. Optionally, the apparatus further comprises a memory. Optionally, the apparatus further comprises a communication interface, and the processor may be coupled with the communication interface.
The apparatus may be, for example, a terminal, a chip system, a hardware circuit and/or a software module applied in the terminal, or other apparatus capable of implementing a terminal function, which is not limited herein.
In a ninth aspect, the present application provides a communications apparatus comprising a processor, the processor being couplable to a memory for invoking program code in the memory to perform a method as described in the second aspect or any one of the possible implementations. Optionally, the apparatus further comprises a memory. Optionally, the apparatus further comprises a communication interface, and the processor may be coupled with the communication interface.
As an example, the device may be an SMF entity, a system on a chip, a hardware circuit and/or a software module applied in the SMF entity, or other devices that may implement the functions of the SMF entity, which is not limited herein.
In a tenth aspect, the present application provides a communication system comprising the apparatus of the fourth or seventh aspect, including the apparatus of the fifth or eighth aspect, and including the apparatus of the sixth or ninth aspect.
In an eleventh aspect, the application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method according to the first aspect, the second aspect, the third aspect or any one of the possible implementations thereof.
In a twelfth aspect, the application provides a computer readable medium storing program code for execution by a device, the program code comprising instructions for performing the method of the first aspect, the second aspect, the third aspect or any one of the possible implementations thereof.
The technical effects that any one of the fourth to twelfth aspects and any one of the possible designs of the fourth to twelfth aspects may achieve are described with reference to the technical effects that any one of the first to third aspects may achieve, and the description is not repeated here.
Drawings
Fig. 1 is a schematic diagram of a network architecture of a communication system according to an embodiment of the present application;
FIG. 2 is an exemplary illustration of a MoQ protocol architecture;
FIG. 3 is an exemplary flow chart of a communication method provided by one embodiment of the application;
FIG. 3a is an exemplary illustration of a transmission of first media content provided in accordance with one embodiment of the present application;
FIG. 4 is an exemplary flow chart of a communication method provided in accordance with another embodiment of the present application;
FIG. 5 is an exemplary flow chart of a communication method provided by yet another embodiment of the application;
FIG. 6 is an exemplary flow chart of a communication method provided in accordance with yet another embodiment of the present application;
fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;
Fig. 8 is a schematic structural diagram of a communication device according to another embodiment of the present application.
Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
In order to clearly describe the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.
It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
In embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or" describes an association of associated objects, meaning that there may be three relationships, e.g., A and/or B, and that there may be A alone, while A and B are present, and B alone, where A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a, b, or c) of a, b, c, a-b, a-c, b-c, or a-b-c may be represented, wherein a, b, c may be single or plural.
It should be noted that, the communication method and the communication device provided by the present application are based on the same technical concept, and because the principles of solving the problems by the method and the device are similar, the implementation of the method and the device can be referred to each other, and the repetition is omitted.
The technical scheme provided by the application can be applied to various communication systems, including but not limited to a narrow-band-internet of things, NB-IoT (Internet of things) system, a global system for mobile communication (global system for mobile communications, GSM), an enhanced data rate GSM evolution system (ENHANCED DATA RATE for GSM evolution, EDGE), a wideband code division multiple access system (wideband code division multiple access, WCDMA), a code division multiple access 2000 system (code division multiple access, CDMA 2000), a time division synchronous code division multiple access system (time division-synchronization code division multiple access, TD-SCDMA), a wireless fidelity (WIRELESS FIDELITY, wiFi) system, a third generation (3rd generation,3G) mobile communication system, a long-term evolution (long term evolution, LTE) system, an advanced long-term evolution (LTE ADVANCED, LTE-A) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, io), a fourth generation (fourth generation, 4G) mobile communication system, a fifth generation (5th generation,5G) mobile communication system, three application scenarios of a new wireless (new, NR) communication system, such as enhanced mobile wideband (enhanced mobile broadband, eMBB), ultra-high reliability and low-frequency communication (ultra-wideband) 69, 9795, and a high-frequency communication (TDD) system, such as a future communication system, a high-frequency communication system, a future communication system, a communication system, and the application is not limited by the application.
Taking a 5G communication system as an example, fig. 1 is a schematic diagram of a network architecture of a communication system according to an embodiment of the present application. As shown in fig. 1, the communication system includes a terminal, an access network, a core network, and a data network.
A terminal may also be referred to as a User Equipment (UE), which is a device that provides voice/data connectivity to a user. Examples of some terminals are currently mobile phones, tablet computers, notebook computers, palm computers, mobile internet devices (mobile INTERNET DEVICE, MID), wearable devices, virtual Reality (VR) devices, augmented reality (augmented reality, AR) devices, wireless terminals in industrial control (industrial control), wireless terminals in unmanned (SELF DRIVING), wireless terminals in tele-surgery (remote medical surgery), wireless terminals in smart grid (SMART GRID), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (SMART CITY), wireless terminals in smart home (smart home), cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personnel DIGITAL ASSISTANT, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle devices, wearable devices, etc., the embodiments of the application are not limited in this respect. In the embodiment of the present application, the device for implementing the function of the terminal may be the terminal itself, or may be a device capable of supporting the terminal to implement the function, for example, a chip system, and the device may be installed in the terminal, or may be other devices capable of implementing the function of the terminal, which is not limited herein. In the embodiment of the application, the chip system can be composed of chips, and can also comprise chips and other discrete devices.
The access network may be a (radio) access network (R) AN for providing a radio connection between the UE and a 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 (base transceiver station, BTS) in a global system for mobile communications (global system for mobile communication, GSM) or code division multiple access (code division multiple access, CDMA) network, may be a node base station (node base station, NB) in wideband code division multiple access (wideband code division multiple access, WCDMA), may be an evolved (evolutional) NB (eNB or eNodeB) in long term evolution (long term evolution, LTE), may be a radio controller in the context of a cloud radio access network (cloud radio access network, CRAN), may be a base station device in a future 5G network or an access network device in a future evolved PLMN network, may be a wearable device or a vehicle-mounted device. In the embodiment of the present application, the device for implementing the function of the access network may be the access network itself, or may be a device capable of supporting the access network to implement the function, for example, a chip system, where the device may be installed in the access network, or may be other devices capable of implementing the function of the access network, and is not limited herein.
The core network includes, but is not limited to, network slice selected authentication and authorization function (network slice-specific authentication and authorization function, NSSAAF) entities, authentication server function (authentication server function, AUSF) entities, access and mobility management function (ACCESS AND mobility management function, AMF) entities, session management function (session management function, SMF) entities, service control point (service control point, SCP), network slice admission control function (network slice admission control function, NSACF) entities, edge application server discovery function (edge application server discovery function, EASDF) entities, application function (application function, AF) entities, unified data management function (unified DATA MANAGEMENT, UDM) entities, policy control function (policy control function, PCF) entities, network storage function (network repository function, NRF) entities, network opening function (network exposure function, NEF) entities, network slice selection function (network slice selection function, NSSF) entities, and user plane function (user plane function, UPF) entities. In the embodiment of the present application, the device for implementing the function of each functional entity in the core network may be each functional entity, or may be a device capable of supporting each functional entity to implement the function, for example, a chip system, where the device may be installed in each functional entity, or may be other devices capable of implementing the function of each functional entity, which is not limited herein.
As an example, the AMF entity, the main functions include managing user registration, reachability detection, selection of SMF entity, mobility state transition management, and the like.
The SMF entity has the main functions of controlling the establishment, modification and deletion of the session, the selection of the user plane node and the like.
The UPF entity, the main functions are packet routing and forwarding, mobility anchor, upstream classifier to support routing traffic to data network, branch point to support multi-homing protocol data unit (protocol data unit, PDU) session, etc.
The PCF entity is mainly used for policy decision point and providing rules based on service data flow and application detection, gating, service quality (quality of service, qoS) and flow-based charging control.
The UDM entity, the main function is to store user subscription data.
AUSF entity, main function enables to provide authentication service.
The AF entity, the main function is to interact with the third generation partnership project (3rd generation partnership project,3GPP) core network to provide services to affect traffic routing, access network capability opening, policy control, etc.
And NSSF, determining network slice examples which are allowed to be accessed by the terminal according to the slice selection auxiliary information, subscription data and the like of the terminal.
AUSF entity, the main function is to provide authentication service.
The NEF entity, the main function is to securely open services and capabilities provided by 3GPP network functions, such as third parties, edge computing, AF, etc.
A Data Network (DN) refers to a network that provides a data transmission service for a user, such as an operator service, internet access, or a third party service.
In this embodiment, the UE may access the DN by establishing a PDU session between the UE to the (R) AN, the UPF entity to the DN.
Referring to fig. 1, it can be seen that the terminal, the access network, the UPF entity and the DN are in the user plane and the other functional entities of the core network are in the control plane.
Referring to fig. 1, the ue and the AMF entity may communicate through AN N1 interface, the (R) AN and the AMF entity may communicate through AN N2 interface, the (R) AN and the UPF entity may communicate through AN N3 interface, the UPF entity and the SMF entity may communicate through AN N4 interface, the UPF entity and the DN may communicate through AN N6 interface, and the UPF entity may communicate through AN N9 interface.
Referring to fig. 1, the nssaf entity provides a service interface Nmssaaf, the AUSF provides a service interface Nausf, the AMF entity provides a service interface Namf, the SMF provides a service interface Nsmf, the NSACF provides a service interface Nnsacf, the EASDF provides a service interface Neasdf, the AF provides a service interface Naf, the UDM provides a service interface Nudm, the PCF provides a service interface Npcf, the NRF provides a service interface Nnrf, the NEF provides a service interface Nnef, and the NSSF provides a service interface Nnssf.
The technical problem to be solved by the present application will be described with reference to fig. 2.
With the evolution of computer technology and the abundance of application scenarios, new network transmission protocols, such as the media (media over quick user datagram protocol internet connection,media over quick UDP internet connection,media over QUIC,MoQ) protocol based on the rapid user datagram protocol internet connection, are emerging. The MoQ protocol is used for defining a unified low-delay and high-expandability media distribution protocol and architecture based on the QUIC protocol, and can be applied to real-time media services such as cloud games, audio-video conferences, live broadcasting and the like.
Illustratively, FIG. 2 is an exemplary illustration of a MoQ protocol architecture. As shown in fig. 2, the MoQ protocol architecture includes a content consumer (consumer), a relay node (relay), and a content producer (producer). It should be understood that the number of relay nodes may be plural, and is not limited herein.
The subscription/release of the media content can be performed between the content consumer and the relay node and between the relay node and the content producer in a subscription/release mode. For example, a content consumer may send a subscription request to a relay node to obtain media content, the relay node may receive the subscription request sent by the content consumer and determine whether the media content is stored in the relay node based on the received subscription request, if the media content is stored in the relay node, the relay node may publish the media content to the content consumer, and if the media content is not stored in the relay node, the relay node may subscribe to a previous node (e.g., a content producer) to obtain the media content, and publish the obtained media content to the content consumer. It should be noted that, the media content may be understood as service data of the real-time media service.
AS an example, the content consumer may be a terminal and the content producer may be an application server (application server, AS) or an AF entity.
However, in this protocol architecture, both subscription and publishing of media content are transmitted using MoQ protocol, thus requiring content consumers to support MoQ protocol, or content consumers not supporting MoQ protocol, to be unable to obtain media content transmitted via MoQ protocol. Therefore, how to enable content consumers that do not support MoQ to obtain media content transmitted using MoQ protocol is a technical problem that needs to be solved.
In view of this, the present application provides a communication method and a communication apparatus. The present application provides a method for obtaining media content transmitted through MoQ protocol for a terminal that does not support MoQ protocol, or provides a method for providing media content transmitted through MoQ protocol for a terminal that does not support MoQ protocol. In the method provided by the application, the UPF entity can convert the media content transmitted by using MoQ protocol into the media content transmitted by the protocol supported by the terminal, so that the terminal which does not support MoQ protocol can acquire the media content transmitted by MoQ protocol. The method and the device can be applied to real-time media services such as cloud games, audio-video conferences, live broadcasting and the like. By way of example, the protocols supported by the terminal may include at least one of real-time transport protocol (real-time transport protocol, RTP), real-time streaming protocol (REAL TIME STREAMING protocol, RTSP), transmission control protocol (transmission control protocol, TCP), real-time transmission control protocol (realtime transport control protocol, RTCP), or hypertext transfer protocol (hypertext transfer protocol, HTTP).
The following describes the communication method provided by the present application in detail with reference to fig. 3 to 6. It should be understood that the terminal in the embodiment of the present application does not support MoQ protocols.
Fig. 3 is an exemplary flow chart of a communication method according to an embodiment of the present application. As shown in fig. 3, the method may include S301 and S302.
By way of example, the method may be performed by the UPF entity, or may be performed by a system-on-chip, hardware circuitry, and/or software modules applied in the UPF entity, or may be implemented by other devices capable of implementing the UPF entity functionality, without limitation.
S301, acquiring first media content, wherein the first media content is media content which is transmitted to a UPF entity by an application server through MoQ protocol.
As an example, media content may be understood as service data of real-time media services such as cloud gaming, audio-video conferencing, live streaming, etc. It should be appreciated that the media content may include one or more data packets (DATA PACKET). Media content may also be referred to as business data, etc., as the application is not limited in this regard.
As an example, the first media content may be understood as media content of a subscription service of the terminal. For example, when a user needs to watch live broadcast through a terminal, the user can sign up with a service provider of the service, so that the terminal can acquire media content of the service. Wherein a service provider of a service may be understood AS an AS or AF entity providing the service of the service. In this embodiment, the first media content is media content transmitted through MoQ protocol.
In some embodiments, the service provider of the service can only transmit media content of the service via the MoQ protocol, or the server provider of the service can only provide media content transmitted via the MoQ protocol.
As an example, after the terminal completes registration and session establishment, the UPF entity may obtain the first media content according to subscription data of the terminal. For example, the UPF entity can obtain a first media content from among the media content stored by the UPF entity. The media content stored by the UPF entity may be media content that the AS transmits to the UPF entity via the MoQ protocol. For another example, the AS may transmit the first media content to the UPF entity according to the subscription data of the terminal, and correspondingly, the UPF entity may receive the first media content.
S302, the first media content is sent to the terminal through a protocol supported by the terminal.
In this embodiment, after obtaining the first media content, the UPF entity may send the first media content to the terminal through a protocol supported by the terminal.
As an example, the UPF entity may, after obtaining the first media content, convert a transport format of the first media content into a transport format corresponding to a protocol supported by the terminal, and send the transport format to the terminal. For example, the UPF entity may encapsulate a protocol supported by the terminal for the first media content, or the UPF entity may add protocol information supported by the terminal at 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, the UPF entity needs to determine a stream format of the first media content, if the stream format of the first media content is the stream format supported by the terminal, the UPF entity may send the first media content to the terminal directly through the protocol supported by the terminal, and if the stream format of the first media content is not the stream format supported by the terminal, the UPF entity needs to convert the stream format of the first media content into the 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 may receive the first media content. Where streaming format refers to a standardized data format for storing and transmitting media content.
Fig. 3a is an exemplary illustration of a transmission of a first media content according to one embodiment of the present application. As shown in fig. 3a, the UPF entity obtains the first media content transmitted through the MoQ protocol, and when sending the first media content to the terminal, the first media content needs to pass through an application layer and a transmission layer. Wherein the application layer may comprise at least one stream format, such as stream format 1 through stream format N.
As an example, after the UPF entity obtains the first media content transmitted through the MoQ protocol, it needs to determine whether the obtained stream format of the first media content is a stream format supported by the terminal, if the stream format of the first media content is not the stream format supported by the terminal, the UPF entity may convert the stream format of the first media content into the stream format supported by the terminal in the application layer, encapsulate the protocol supported by the terminal (such as RTP, RTSP, RTCP, HTTP) on the first media content after the stream format conversion, and then send the first media content to the terminal through a transmission layer corresponding to the protocol supported by the terminal. It should be appreciated that if the streaming format of the first media content is a streaming format supported by the terminal, the UPF entity does not need to translate the streaming format of the first media content. The streaming format of the first media content obtained by the UPF entity may be a streaming format used when the UPF entity stores the first media content, or a streaming format used when the AS sends the first media content to the UPF entity.
It should be noted that, the method for determining the protocol supported by the terminal by the UPF entity is not particularly limited in this embodiment. For example, the protocols supported by the terminal may be stored in the subscription data of the terminal, or may be pre-configured in advance in the UPF entity.
In this embodiment, the UPF entity may 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 the communication efficiency.
In some implementations, after the terminal completes registration and session establishment, the terminal may actively request to acquire 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 request information of the terminal.
Fig. 4 is an exemplary flowchart of a communication method according to another embodiment of the present application. As shown in fig. 4, the method may include S401 to S406.
By way of example, the method may be performed by the UPF entity, or may be performed by a system-on-chip, hardware circuitry, and/or software modules applied in the UPF entity, or may be implemented by other devices capable of implementing the UPF entity functionality, without limitation.
S401, receiving second information from the terminal, wherein the second information is used for requesting an address of an application server providing the first media content.
AS an example, after registration and session establishment are completed, the terminal may send second information to the UPF entity requesting an address of an AS providing the first media content when it needs to access or acquire the first media content. Accordingly, the UPF entity may receive the second information. Wherein the first media content is media content transmitted via MoQ protocol.
As an example, the second information may be Domain Name System (DNS) request information, or the second information may be carried in DNS request information. DNS is a system that converts domain names into internet protocol addresses (internet protocol, IP) addresses. For example, the DNS request may be sent when the terminal requests access to or acquisition of the first media content on a website, web page, or application.
AS an example, the second information may include a formal domain name (fully qualified domain name, FQDN) of the AS providing the first media content. FQDNs may also be referred to as full domain names.
AS an example, when a terminal requests access to or acquires first media content on a website, the FQDN of the AS providing the first media content may 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.
And S402, sending third information to the terminal, wherein the third information indicates the address of the UPF entity.
As an example, the UPF entity may send third information to the terminal according to the second information after receiving the second information. For example, the UPF entity may determine the FQDN carried in the second information, and if the FQDN carried in the second information is a FQDN preconfigured in the UPF entity, the UPF entity may send third information to the terminal in response to the second information.
As an example, the third information may contain an address of the UPF entity, or may contain indication information of the address of the UPF entity.
It should be noted that, if the FQDN carried in the second information is not the FQDN preconfigured in the UPF entity, the UPF entity may not send the third information to the terminal, or the UPF entity is only a function of transparent forwarding, where the address received by the terminal should be an address of the application server. It should be understood that when the FQDN carried in the second information is a preconfigured FQDN 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 acquire the first media content for the terminal.
As an example, a preconfigured FQDN in a UPF entity may be understood as one or more FQDNs preconfigured in the UPF entity.
As an example, the FQDN carried in the second information is a preconfigured FQDN in the UPF entity, which may be understood that the FQDN carried in the second information may be the same as or match one of the preconfigured FQDNs in the UPF entity.
As an example, a preconfigured FQDN in a UPF entity may be associated with an address of the UPF entity. The address of the UPF entity may be an IP address of the UPF entity.
In this embodiment, the FQDN preconfigured in the UPF entity may be set according to actual requirements, or may be obtained through signaling, which is not limited herein. In some embodiments, the IP address corresponding to the preconfigured FQDN may be an IP address of an AS capable of transmitting media content only through MoQ protocols, or the IP address corresponding to the preconfigured FQDN may be an IP address of an AS capable of providing media content only through MoQ protocols.
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 DNS response information, which is not limited herein.
S403, receiving first information from the terminal, wherein the first information is used for requesting first media content, and the first information comprises a uniform resource locator of the first media content.
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 to obtain 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.
As an example, the first information may be an application layer message requesting to acquire or access the first media content, or the first information may be carried in an application layer message requesting to acquire or access the first media content, without limitation.
As an example, the first information may include a uniform resource locator (uniform resource locator, URL) of the first media content to indicate the first media content. The URL may also be referred to as a web page address.
As an example, the general format of a URL is protocol type:// server address [: port number ]/filename [ parameter = value ]. For example, the URL may be an example of http:// www.aspxfans.com:8080/news/index_ aspboardID =5 & ID=24618 & page=1#name.
The protocol part of the URL is 'http:', which means that the web page uses the HTTP protocol. It should be appreciated that after receiving the URL, the UPF entity may determine the protocols supported by the terminal, such as the HTTP protocol in this example, based on the protocol portion in the URL. Since the terminal does not support MoQ protocol, the protocol part in the URL transmitted by the terminal will not be MoQ protocol, because the URL transmitted by the terminal can be considered as a URL other than MoQ.
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 a domain name.
The port portion of the URL is the content "8080" following the domain name, and the use of ":" between domain name and port is a separator.
The datagram directory portion of the URL is "new", i.e., the portion from the first one after the domain name from the first "/" after the domain name to the last "/". The datagram directory portion is not an essential portion of the URL.
The file name part of the URL is "index _ asp? i.e., the portion from the last"/"beginning to".
The parameter portion of the URL is "boardID =5 & id=24618 & page=1", i.e., the portion from ". The parameter portion may also be referred to as a search portion, a query portion.
The anchor portion of the URL is "name". The anchor portion is not an essential part of the URL.
And S404, sending fourth information to the application server, wherein the fourth information is used for requesting the first media content.
As an example, after receiving the first information, the UPF entity may determine, based on the URL carried in the first information, that the media content requested to be acquired by the terminal is the first media content, and acquire the first media content for the terminal. For example, the UPF entity may determine that the media content requested to be acquired by the terminal is the first media content based on a parameter portion, a file name portion, or other portion in the URL, and after determining the first media content, send fourth information to the AS providing the first media content to request acquisition of the requested first media content. Accordingly, the AS may receive the fourth information.
AS an example, the fourth information may contain a resource address of the first media content in the AS, so that the AS may be aware that the media content requested to be acquired by the UPF entity is the first media content. It should be appreciated that the resource address may be replaced with a query parameter, a search parameter, or otherwise, as long as the first media content may be indicated.
As an example, the fourth information may include at least one of a first path name (TRACK NAME), a first path identification (track ID), or a first path alias (TRACK ALIAS). The first parameter is used for indicating the first media content, or the first parameter is a parameter corresponding to the first media content. Note that TRACK NAME, track ID, and TRACK ALIAS may be collectively referred to as media content parameters for indicating specific media content. The specific names of TRACK NAME, track ID, and TRACK ALIAS are not limited in this disclosure. For example TRACK NAME may also be referred to as a program name, track ID may also be referred to as a program identification, TRACK ALIAS may also be referred to as a program alias.
It should be noted that, since the terminal does not support MoQ protocols, the terminal can only send the request information through the protocol supported by the terminal when requesting to acquire the first media content, for example, when the protocol supported by the terminal is HTTP, the terminal can send the request information through HTTP protocol, or the request information sent by the terminal is an HTTP request. If the AS only supports MoQ protocols, the AS cannot determine that the media content requested by the terminal is the first media content according to the request information sent by the terminal, or the AS cannot analyze the request information sent by the terminal, so that the UPF entity requests the AS to acquire the first media content in the application. When the UPF entity requests the first media content from the AS, the request information should be transmitted through a protocol supported by the AS (such AS MoQ protocol), and carries MoQ parameters indicating the first media content in the protocol, such AS TRACK NAME, track ID or TRACK ALIAS. Thus, the UPF entity needs to map the URL sent by the terminal to TRACK NAME, track ID or TRACK ALIAS so that the AS can determine the media content requested by the UPF entity AS the first media content based on TRACK NAME, track ID or TRACK ALIAS. It should be appreciated that URL and TRACK NAME, track ID or TRACK ALIAS are different versions of the same media content indicated in different protocols. Thus, the resource address included in the fourth information should be an address in MoQ protocol for indicating the first media content.
As an example, the mapping between the URL and TRACK NAME, track ID or TRACK ALIAS, etc. media content parameters may be pre-configured in the UPF entity in advance, or the UPF entity may be acquired through signaling, without limitation.
As an example, the mapping relationship between the URL and the media content parameters such as TRACK NAME, track ID or TRACK ALIAS may be the mapping relationship between the key information in the URL and the media content parameters such as TRACK NAME, track ID or TRACK ALIAS. The key information in the URL is, for example, a parameter portion, a file name portion, or other portion in the URL, which the present application is not limited to.
In one implementation, the process of sending the fourth information to the AS by the UPF entity may be understood AS a process of subscribing the first media content to the AS by the UPF entity, and the process of sending the first media content to the UPF entity by the AS may be understood AS a process of publishing the first media content to the UPF entity by the AS. In this implementation manner, the fourth information may include a subscription parameter of the first media content, and the subscription parameter of the first media content is not specifically limited in the present application. For example, the subscription parameter of the first media content may be the first parameter.
In this embodiment, the URL includes indication information of a protocol supported by the terminal, so that the UPF entity may determine the protocol supported by the terminal based on the URL sent by the terminal.
In some embodiments, when the protocol supported by the terminal does not include MoQ protocols, the UPF entity may convert, after obtaining the first media content, a transport format of the first media content into a transport format corresponding to the protocol supported by the terminal, and send the transport format to the terminal.
S405, receiving the first media content.
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. Accordingly, the UPF entity may receive the first media content sent by the AS.
And S406, sending the first media content to the terminal through a protocol supported by the terminal.
AS an example, after receiving the first media content sent by the AS, the UPF entity may send the first media content to the terminal through a protocol supported by the terminal, and specifically, S302 may be referred to, which is not described herein again. For example, when the terminal requests the first media content from the UPF entity through the HTTP protocol, the UPF entity may send the first media content to the terminal through the HTTP protocol.
In this embodiment, if the FQDN carried in the second information sent by the terminal is a FQDN preconfigured in the UPF entity, the UPF entity may intercept the second information and return an address of the UPF entity to the terminal, so that the terminal may request to obtain the first media content from the UPF entity, further, the UPF entity may obtain the first media content for the terminal, and after obtaining the first media content, the terminal may send the first media content to the terminal through a protocol supported by the terminal, so that the terminal that does not support MoQ may obtain the media content transmitted through MoQ.
In some implementations, S404 and S405 may not be performed, i.e., S406 may be performed directly after S403 is performed. For example, after the UPF entity receives the first information and determines that the media content requested to be acquired by the terminal is the first media content based on the first information, it may be determined whether the first media content exists in the media content stored in the UPF entity, and 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 acquiring the first media content from the AS.
It should be understood that, in the embodiment of the present application, the UPF entity should support MoQ protocols, so that the UPF entity can acquire the first media content transmitted by the MoQ protocols 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 MoQ protocols, which may also be referred to as a UPF entity having the functionality of the relay node defined by the MoQ protocol. Note that the UPF entity may have a function of a relay node defined by MoQ protocol, may have a function of a relay node defined by MoQ protocol, may include a device having a function of a relay node defined by MoQ protocol, or may call a device having a function of a relay node defined by MoQ protocol, which is not limited herein. The function of the relay node defined by MoQ protocol may refer to the relevant description in fig. 2, and will not be described here again. In some embodiments, the function of the relay node defined by MoQ protocol may be referred to as MoQ relay function, and the device with the function of the relay node defined by MoQ protocol may be referred to as MoQ relay instance, without limitation. In some embodiments, the address of the UPF entity may be the address of the MoQ relay instance.
In one implementation, the UPF entities in the default network all support the MoQ protocol.
In one implementation, the UPF entities in the network do not all support the MoQ protocol. In this implementation, the SMF entity may select a UPF entity supporting the MoQ protocol for the terminal, or may instruct the UPF entity to activate MoQ protocol-defined functions of the relay node after selecting the UPF entity.
Fig. 5 is an exemplary flowchart of a communication method according to still another embodiment of the present application. As shown in fig. 5, the method may include S501 and S502.
S501, the terminal sends seventh information to the SMF entity, where the seventh information indicates that the UPF entity serving the terminal should support MoQ protocols.
As an example, the terminal may send seventh information to the SMF entity to indicate that the UPF entity serving the terminal should support MoQ protocols. Accordingly, the SMF entity may receive the seventh information.
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 transmit seventh information to the SMF entity when initiating a session establishment request or a session modification request.
As an example, the terminal may transmit seventh information to the SMF entity through the AMF entity.
In some embodiments, the seventh information may comprise an identification of the terminal and/or a traffic type of the terminal. As an example, the identity of the terminal may be a user permanent identifier (subscription PERMANENT IDENTIFIER, SUPI) or others, without limitation. As an example, the service type of the terminal may include a service for transmitting service data using MoQ protocol.
S502, the SMF entity selects a first UPF entity for the terminal based on the seventh information, where the first UPF entity supports MoQ protocols.
As an example, the first UPF entity is a UPF entity serving the terminal.
In one implementation, after receiving the seventh information, the SMF entity may select a first UPF entity supporting MoQ protocols 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 the present application does not limit how the SMF entity knows whether the UPF entity supports MoQ protocols. For example, the SMF entity may send request information to each UPF entity within the service range of the SMF entity, so as to request each UPF entity to report its own function, such as reporting information about whether MoQ protocols are supported or information about supported protocol types. For another example, the UPF entity may report its own functions to the SMF entity when registering on the network, such as whether or not the indication of the MoQ protocol is supported or the indication of the type of protocol supported.
In one implementation, after receiving the seventh information, the SMF entity may select the first UPF entity based on the seventh information, and send fifth information to the first UPF entity, where the fifth information indicates that the first UPF entity activates a function of the relay node defined by the MoQ protocol. Accordingly, the first UPF entity may receive the fifth information and activate MoQ protocol-defined functions of the relay node. It should be noted that, the function of activating the relay node defined by the MoQ protocol may be understood as configuring, enabling, starting or enabling the function of the relay node defined by the MoQ protocol, which is not limited herein. It should be appreciated that in this implementation, the first UPF entity selected by the SMF entity is capable of activating the functions of the relay node defined by the MoQ protocol.
As an example, the fifth information may be carried in an N4 session (session), which is not limited herein.
In some embodiments, after activating the function of the relay node defined by the MoQ protocol, the first UPF entity may send a sixth message to the SMF entity in response to the fifth message, the sixth message indicating that the first UPF entity has activated the function of the relay node defined by the MoQ protocol.
It should be noted that, after the SMF entity selects the first UPF entity for the terminal, or after the session establishment or the session modification is completed, the terminal that does not support MoQ protocols may be enabled to acquire the media content transmitted through MoQ protocols by using the method in fig. 3 or fig. 4. It should be understood that the session establishment or session modification procedure may further include other steps, such as steps of SMF entity selection, secondary authentication, etc., which are not shown in this embodiment.
In this embodiment, the SMF entity may select the first UPF entity for the terminal based on the seventh information sent by the terminal, where the first UPF entity supports MoQ protocols, so that the first UPF entity may obtain the first media content for the terminal that does not support MoQ protocols.
In one possible implementation, the SMF entity may select a UPF entity to serve the terminal based on protocols supported by the terminal. In this implementation, it is considered that the terminal may acquire the media content transmitted through the MoQ protocol in a subscription manner when supporting the MoQ protocol, such as the method in fig. 2, and may acquire the media content transmitted through the MoQ protocol by using the UPF entity when not supporting the MoQ protocol, such as the method in fig. 3 or fig. 4. Thus, 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 for the terminal that is transmitted over the MoQ protocol.
Fig. 6 is an exemplary flow chart of a communication method according to yet another embodiment of the present application. As shown in fig. 6, the method may include S601 and S602.
By way of example, the method may be performed by an SMF entity, or may be performed by a system-on-chip, hardware circuitry, and/or software modules applied in the SMF entity, or may be implemented by other means capable of implementing the functions of the SMF entity, without limitation.
S601, acquiring a protocol supported by a terminal.
In one implementation manner, the SMF entity may acquire subscription data of the terminal from the UDM entity in a session establishment/modification process, where the subscription data of the terminal may include indication information of a protocol supported by the terminal, so that the SMF entity may acquire the protocol supported by the terminal. For example, the SMF entity may send request information to the UDM entity to request acquisition of subscription data of the terminal, or to request acquisition of indication information of agreements supported by the terminal in the subscription data of the terminal.
As an example, the indication information of the protocol supported by the terminal may include indication information of whether the terminal supports MoQ protocols. For example, the indication information of the protocol supported by the terminal is 1 bit, when the indication information of the protocol supported by the terminal is "0", it indicates that the terminal does not support MoQ protocols, when the indication information of the protocol supported by the terminal is "1", it indicates that the terminal supports MoQ protocols, or when the indication information of the protocol supported by the terminal is "0", it indicates that the terminal supports MoQ protocols, when the indication information of the protocol supported by the terminal is "1", it indicates that the terminal does not support MoQ protocols, and the method can be specifically set according to actual requirements, and is not limited herein.
As an example, the indication information of the protocol supported by the terminal may include indication information of the protocol type supported by the terminal. For example, when the indication information of the protocol supported by the terminal is "0", it indicates that the protocol type supported by the terminal is "HTTP", or when the indication information of the protocol supported by the terminal is "0", it indicates that the protocol type supported by the terminal is "TCP", which may be specifically set according to actual requirements, and is not particularly limited herein.
As an example, the indication information of the protocol supported by the terminal may include indication information of a protocol type not supported by the terminal. For example, when the indication information of the protocol not supported by the terminal is "0", it indicates that the protocol type not supported by the terminal is "MoQ", and for example, when the indication information of the protocol not supported by the terminal is "0", it indicates that the protocol type not supported by the terminal is "TCP", which is not limited herein.
In an implementation manner, when a terminal initiates a session establishment request or a session modification request, indication information of a protocol supported by the terminal is sent to an SMF entity, so that the SMF entity can acquire the protocol supported by the terminal. In this implementation, the indication information of the protocol supported by the terminal may be carried in a session establishment request message or a session modification request message.
As an example, the terminal may carry, in the session establishment request message, indication information of a service type of the terminal, which may include MoQ services. MoQ traffic can be understood as traffic that uses the MoQ protocol to transport traffic data. For example, the session establishment request message may carry an identification of a network slice supporting the MoQ protocol and/or a DN identification supporting the MoQ protocol. In this example, a class of service type, such as MoQ services, may be specifically defined for the terminal.
S602, selecting a first UPF entity, wherein the first UPF entity supports MoQ protocols.
As an example, after the SMF entity obtains the protocol supported by the terminal, if the terminal does not support MoQ protocols, the SMF entity may select a UPF entity supporting MoQ protocols for the terminal, or after the UPF entity is selected, the SMF entity may instruct the UPF entity to activate the function of the relay node defined by MoQ protocols, which may be specifically described with reference to S502 and will not be described herein.
In this embodiment, the SMF entity may select a UPF entity supporting MoQ protocol for a terminal that does not support MoQ protocols, or instruct the selected UPF entity to activate a function of a relay node defined by MoQ protocols after selecting the UPF entity, so that the terminal that does not support MoQ protocols may request to the UPF entity to acquire media content transmitted through MoQ protocols, which may be referred to in the related content in the foregoing embodiments, and will not be described herein.
It should be understood that the method in fig. 6 is by way of example only and not by way of limitation. For example, when the terminal supports MoQ protocol, the first media content may also be acquired by the UPF entity, and at this time the UPF entity should also support MoQ protocol.
In some implementations, when the terminal supports MoQ protocols, the terminal may subscribe to the media content to the relay node, before the relay node publishes the media content to the terminal, the AF entity may dynamically calculate a publishing path of the media content, and when a UPF entity in an optimal publishing path does not support MoQ protocols, send indication information to the UPF entity to instruct the UPF entity to activate a function of the relay node defined by MoQ protocols, so that the UPF entity may transmit the media content to the terminal, and further, the relay node may publish the media content to the terminal through the optimal publishing path calculated by the AF entity, thereby saving transmission power consumption. It should be noted that in this implementation, the AF entity may be aware of topology information of an application server in the communication network, so that a distribution path of the media content may be dynamically calculated, and the AF entity may be aware of information of each node in the network (for example, whether the UPF entity supports MoQ protocol or not), so that it may be ensured that the UPF entity in the determined optimal distribution path of the media content may transmit the media content through MoQ protocol. The optimal release path may be understood as a release path with a path length less than or equal to a preset threshold, which may be set according to actual requirements, and is not limited herein.
Fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in fig. 7, the apparatus 700 of the present embodiment may be used to implement the method shown in any of the foregoing embodiments. As shown in fig. 7, the apparatus 700 of the present embodiment may include a processing module 710, a transmitting module 720, and a receiving module 730.
As an example, the apparatus 700 may be used to implement various steps/operations performed by a UPF entity in the methods illustrated in fig. 3 or 4.
For example, when the apparatus 700 is used to implement the method implemented by the UPF entity in fig. 3, the processing module 710 may be used to implement S301, and the sending module 720 may be used to implement the operations performed by the UPF entity in S302.
When the apparatus 700 is used to implement the method implemented by the UPF entity in fig. 4, the sending module 720 may be used to implement the operations performed by the UPF entity in S402, S404, and S406, and the receiving module 730 may be used to implement the operations performed by the UPF entity in S401, S403, and S405.
As an example, the apparatus 700 may be used to implement various steps/operations performed by a terminal in the methods shown in fig. 3, 4, or 5.
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 operations performed by the terminal in S302.
When the apparatus 700 is used to implement the method implemented by the terminal in fig. 4, the transmitting module 720 may be used to implement the operations performed by the terminal in S401 and S403, and the receiving module 730 may be used to implement the operations performed by the terminal in S402 and S406.
When the apparatus 700 is used to implement the method implemented by the terminal in fig. 5, the transmitting module 720 may be used to implement the operations performed by the terminal in S501.
As an example, the apparatus 700 may be used to implement various steps/operations performed by an SMF entity in the methods shown in fig. 5 or 6.
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 operations performed by the SMF entity in S501.
When the apparatus 700 is used to implement the method implemented by the SMF entity in fig. 6, the processing module 710 may be used to implement S601 and S602.
Fig. 8 is a schematic structural diagram of a communication device according to another embodiment of the present application. As shown in FIG. 8, apparatus 800 is used to implement the method shown in any of the foregoing embodiments.
As shown in fig. 8, the apparatus 800 of the present 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 communicatively coupled to each other via a bus 840.
The memory 810 may be a Read Only Memory (ROM), a static storage device, a dynamic storage device, or a random access memory (random access memory, RAM). The memory 810 may store a program that, when executed by the processor 820, the processor 820 is configured to perform the steps of any of the foregoing embodiments.
Processor 820 may employ a general-purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits for executing the associated program.
Processor 820 may also be an integrated circuit chip with signal processing capabilities. In implementation, various relevant steps of embodiments of the application may be accomplished through integrated logic circuitry in hardware or instructions in software in processor 820.
The processor 820 may also be a general purpose processor, a digital signal processor (DIGITAL SIGNAL processing unit, DSP), an Application Specific Integrated Circuit (ASIC), a field programmable gate array (field programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in memory 810 and processor 820 reads information from memory 810 and, in combination with hardware, performs the functions necessary for the unit comprised by the apparatus of the application.
Alternatively, memory 810 and processor 820 may be integrated.
Communication interface 830 may enable communication between apparatus 800 and other devices or apparatuses using, but is not limited to, a transceiver or the like.
Bus 840 may include a path to transfer information between various components of device 800 (e.g., memory 810, processor 820, communication interface 830).
Some embodiments of the application also provide a computer program product which, when run on a processor, can implement the method shown in any of the embodiments described above. Some embodiments of the application also provide a computer readable storage medium containing computer instructions which, when executed on a processor, implement the method shown in any of the embodiments above.
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, for example, one or more Application SPECIFIC INTEGRATED Circuits (ASICs), or one or more microprocessors (DIGITAL SIGNAL processors, DSPs), or one or more field programmable gate arrays (field programmable GATE ARRAY, FPGAs), or the like. For another example, when a module above is implemented in the form of a processing element calling program code, the processing element may be a general-purpose processor, such as a central processing unit (central processing unit, CPU) or other processor that may call program code, such as a controller. For another example, the modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, software modules or any combination thereof. When implemented in software, may 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 processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.) means from one website, computer, server, or data center. Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc., that contain an integration of one or more available media. Usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tape), optical media (e.g., DVD), or semiconductor media (e.g., solid State Disk (SSD)) or the like.
It will be appreciated that the various numerical numbers referred to in the embodiments of the present application are merely for ease of description and are not intended to limit the scope of the embodiments of the present application.
It should be understood that, in the embodiment of the present application, the sequence number of each process does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.
Claims (25)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410217471.1A CN120567838A (en) | 2024-02-27 | 2024-02-27 | Communication method and communication device |
PCT/CN2025/076883 WO2025180215A1 (en) | 2024-02-27 | 2025-02-11 | Communication method and communication apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410217471.1A CN120567838A (en) | 2024-02-27 | 2024-02-27 | Communication method and communication device |
Publications (1)
Publication Number | Publication Date |
---|---|
CN120567838A true CN120567838A (en) | 2025-08-29 |
Family
ID=96815910
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202410217471.1A Pending CN120567838A (en) | 2024-02-27 | 2024-02-27 | Communication method and communication device |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN120567838A (en) |
WO (1) | WO2025180215A1 (en) |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113365369B (en) * | 2020-03-06 | 2025-02-25 | 华为技术有限公司 | Communication method and device |
WO2023147695A1 (en) * | 2022-02-07 | 2023-08-10 | Zte Corporation | Traffic handling method for quic application |
US20250202801A1 (en) * | 2022-03-23 | 2025-06-19 | Lenovo (Singapore) Pte. Ltd. | Sending data using steering in a selected quic connection |
CN117014951A (en) * | 2022-04-27 | 2023-11-07 | 华为技术有限公司 | Communication method and communication device |
EP4505693A1 (en) * | 2022-05-05 | 2025-02-12 | InterDigital Patent Holdings, Inc. | Enabling xr service proxies |
-
2024
- 2024-02-27 CN CN202410217471.1A patent/CN120567838A/en active Pending
-
2025
- 2025-02-11 WO PCT/CN2025/076883 patent/WO2025180215A1/en active Pending
Also Published As
Publication number | Publication date |
---|---|
WO2025180215A1 (en) | 2025-09-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US12184606B2 (en) | Method and device for edge application server discovery | |
EP4167625A1 (en) | Communication method and apparatus | |
WO2023280121A1 (en) | Method and apparatus for obtaining edge service | |
CN110662308B (en) | Communication method and device | |
CN114270789B (en) | Method and device for acquiring information | |
US20240056496A1 (en) | Method and Apparatus for Selecting Edge Application Server | |
US12232023B2 (en) | Providing slice attribute information to user equipment in a mobile network environment | |
TWI757595B (en) | Interception aware access node selection | |
CN104247505A (en) | System and method for andsf enhancement with anqp server capability | |
WO2008006314A1 (en) | A gateway system and the method for implementing various media accesses | |
JP7717700B2 (en) | Network function registration method, discovery method, apparatus, device and medium | |
WO2021051420A1 (en) | Dns cache record determination method and apparatus | |
WO2021218595A1 (en) | Address acquiring method and apparatus | |
US20230061152A1 (en) | Communication method, apparatus, and system | |
WO2022170518A1 (en) | Method and apparatus for determining address of terminal device, and network device | |
CN103312749B (en) | A kind of application layer traffic optimizes discovery method, equipment and the system of server | |
CN113439459B (en) | Method and apparatus for proxy deployment | |
US20230239720A1 (en) | Wireless communication method and device | |
EP4262244A1 (en) | Method and device for determining mec access point | |
WO2023143212A1 (en) | Communication method and apparatus | |
CN114557045B (en) | Communication method and related device | |
CN120567838A (en) | Communication method and communication device | |
US9843553B2 (en) | Method and device for sending message | |
JP7651722B2 (en) | COMMUNICATION METHOD AND COMMUNICATION DEVICE | |
CN119729888A (en) | Communication method and communication device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication |