Real-time communication using MOQ

Abstract

The present disclosure relates to real-time communication using MOQ. A method used by a first user device is provided, the method comprising: receiving, from a QUIC-based media (MOQ) media server, a combined MOQ directory comprising: media descriptions of media publishable by the first user device, media descriptions of media publishable by one or more second user devices, or media descriptions of media publishable by an application server; and a namespace of the first user device, one or more namespaces of the one or more second user devices, or a namespace of the application server. Sending, to the MOQ media server, a request to subscribe to receive media publishable by the one or more second user devices or the application server; and receiving, from the MOQ media server, media publishable by the one or more second user devices or the application server.

Description

Technical Field

[0001] The various examples disclosed relate to methods, apparatuses, systems, and computer programs, and specifically, but not exclusively, to real-time communication using QUIC-based media (MOQ). Background Technology

[0002] A communication system can be viewed as a facility that enables communication between two or more user devices (e.g., real-time communication) or provides user devices with access to a data network. A mobile or wireless communication system is an example of a communication system.

[0003] Communication systems can operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards provided by 3GPP are the so-called 3GPP standards for cellular (e.g., radio access) technologies, such as the 3GPP standards for 4G, 5G, and 6G technologies.

[0004] 3GPP standards describe different architectures for delivering media, including the 5G Media Streaming (5GMS) architecture and the Internet Protocol (IP) Multimedia Subsystem (IMS)-based architecture. QUIC is an end-to-end encrypted transport layer protocol that supports reliable multiple traffic streams and provides ordered delivery to the receiver. QUIC offers several advantages over its predecessor, Transmission Control Protocol (TCP), including shorter connection establishment times, better loss handling, and support for unreliable delivery of latency-sensitive and loss-tolerant traffic. Recently, MOQ has been developed for delivering media. While MOQ has been adopted for certain purposes, it has not yet been adopted for use in 3GPP architectures (5GMS and IMS architectures) for delivering media. Further development in this area remains possible. Summary of the Invention

[0005] Examples of aspects described herein are intended to indicate certain aspects. These aspects are not intended to indicate key or essential features of the various examples of this disclosure, nor are they intended to limit its scope. Other features, aspects, and elements will be apparent to those skilled in the art in light of this disclosure. For example, it should be understood that additional aspects may be provided by any combination of any two or more of the aspects described below.

[0006] According to one aspect, a method performed by a first user equipment is provided, the method comprising: sending a request to a QUIC-based media MOQ signaling server to establish a communication session with one or more second user equipments, the request indicating that the MOQ transport protocol will be used for media transmission; receiving a response to the request from the MOQ signaling server, the response indicating acceptance of the request, the response including an identifier of the MOQ media server; and, upon receiving the response to the request, sending information to the MOQ media server for establishing a first QUIC connection between the first user equipment and the MOQ media server and a first MOQ session via the first QUIC connection, wherein... The information includes the namespace of a first user equipment; sending a first MOQ directory to the MOQ server, the MOQ directory including media descriptions of media that can be published by the first user equipment through a first MOQ session; receiving the namespace of the MOQ media server from the MOQ media server; receiving a combined MOQ directory from the MOQ media server, the combined MOQ directory including: media descriptions of media that can be published by the first user equipment, media descriptions of media published by one or more second user equipments, or media descriptions of media that can be published by an application server; and the namespace of the first user equipment, one or more namespaces of one or more second user equipments, or the namespace of the application server.

[0007] A communication session can be used for a call. A call can be an audio / or video conference, a webinar, a game stream, or an event stream.

[0008] The media description may include at least one of the following: track name, track type, track creation date, track modification date, track size, track frame rate, track codec, or track namespace.

[0009] The terms "namespace", "address", or "resource identifier" can be used interchangeably.

[0010] The method may include sending a request to the MOQ media server to subscribe to receive media that can be published by one or more second user devices or application servers, and receiving media that can be published by one or more second user devices or application servers from the MOQ media server.

[0011] The information may include instructions for the first user equipment to operate as a publisher of media and a subscriber of media through the first MOQ session.

[0012] The method may include receiving information from an MOQ media server for establishing a first QUIC connection between a first user equipment and an MOQ server, and a first MOQ session via the first QUIC connection, wherein the information includes the namespace of the MOQ media server.

[0013] The information may include instructions for the MOQ media server to operate as a publisher and subscriber of media through the first MOQ session.

[0014] The combined MOQ directory can include the namespace of the MOQ media server.

[0015] The media description of media that can be published by the first user equipment includes at least one of the following: a media description of media that can be published by the first user equipment through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the first user equipment through the first MOQ session but not processed by the MOQ media server.

[0016] The media description of media that can be published by a second user equipment may include at least one of the following: a media description of media that can be published by one or more second user equipments through a first MOQ session and processed by an MOQ media server; or a media description of media that can be published by one or more second user equipments through a first MOQ session but is not processed by an MOQ media server.

[0017] The media description of media that can be published by the application server includes at least one of the following: a media description of media that can be published by the application server through a third MOQ session and processed by the MOQ media server; or a media description of media that can be published by the application server through a third MOQ session but not processed by the MOQ media server.

[0018] The combined catalog may include media descriptions of media that are publishable by a first user device through a first MOQ session and by one or more second user devices through one or more MOQ sessions and processed by the MOQ media server.

[0019] Processing may include transcoding, compositing, encapsulation, combining, and / or rejection.

[0020] Media that can be published by the first user equipment through the first MOQ session may include different versions of the same media content.

[0021] Media that can be published by each of one or more second user devices through a first MOQ session may include different versions of the same media content.

[0022] Media that can be published by the application server through a third MOQ session may include different versions of the same media content.

[0023] Different versions of the same media content can have different qualities (e.g., resolution) or can be encoded using different codecs.

[0024] The method may include sending at least one of the following to the MOQ signaling server: an indication that the first user equipment is capable of encoding and decoding media, an indication of the quality of media that can be published by the first user equipment, an indication of the quality of the radio link of the first user equipment, or an indication of user preferences of the first user equipment.

[0025] The method may include: sending a first MOQ directory to an MOQ signaling server, the first MOQ directory including a media description of media that can be published by a first user equipment through a first MOQ session and at least one of the following: an indication that the first user equipment is capable of encoding and decoding media, an indication of the quality of the media that can be published by the first user equipment, the quality of the radio link of the first user equipment, or the user preferences of the first user equipment.

[0026] The first MOQ catalog can be sent to the MOQ signaling server out of band (i.e., without the first MOQ session).

[0027] The first directory can be sent to the MOQ media server in-band (i.e., via the first MOQ session).

[0028] Sending a request to establish a communication session with one or more second user equipment may include sending a session description protocol proposal indicating that the MOQ transport protocol will be used for media transmission, and receiving a response to the request includes receiving a session description protocol response indicating acceptance of the session description protocol proposal.

[0029] The Session Description Protocol (STP) proposal and response can be carried using at least one of the Session Initiation Protocol, Simple WebRTC Application Protocol, or Hypertext Transfer Protocol.

[0030] According to one aspect, a first user equipment is provided, including components for performing steps of any of the methods described above.

[0031] According to one aspect, a first user equipment is provided, comprising at least one processor and at least one memory storing instructions, said instructions, when executed by the at least one processor, causing the device to perform at least the steps of any of the methods described above.

[0032] According to one aspect, a first user equipment is provided, which includes circuitry configured to perform steps of any of the methods described above.

[0033] According to one aspect, a method performed by a QUIC-based media server is provided, the method comprising: receiving from an MOQ signaling server: an indication of resources to be allocated by the MOQ media server for serving a communication session with one or more second user equipments using the MOQ transport protocol for media transmission; and an indication of session information for at least one of: a first MOQ session between the MOQ media server and a first user equipment, one or more second MOQ sessions between the MOQ media server and one or more second user equipments, or a third MOQ session between the MOQ media server and an application server; allocating resources of the MOQ media server to serve the first MOQ session, one or more second MOQ sessions, or the third MOQ session; receiving from a first user equipment information for establishing a first QUIC connection between the first user equipment and the MOQ media server and a first MOQ session via the first QUIC connection, wherein the information includes the namespace of the first user equipment; and receiving from one or more... Each of the second user equipments receives information for establishing a second QUIC connection between the second user equipment and the MOQ media server and a second MOQ session via the second QUIC connection, wherein the information includes the namespace of the second user equipment; receives a first MOQ directory from a first user equipment, the first MOQ directory including media descriptions of media that can be published by the first user equipment through the first MOQ session; receives a second MOQ directory from each of one or more second user equipments, the second MOQ directory including media descriptions of media that can be published by the second user equipment through the second MOQ session; and sends a combined MOQ directory to the first user equipment, the combined MOQ directory including: media descriptions of media that can be published by the first user equipment, media descriptions of media that can be published by one or more second user equipments or media that can be published by an application server; and namespaces of media that can be published by the first user equipment, one or more namespaces of one or more second user equipments or namespaces of the application server.

[0034] Session information for a first MOQ session, one or more second MOQ sessions with one or more user devices, or a third MOQ session with an application server may include at least one of the following: an identifier of the first MOQ session, one or more second MOQ sessions, or the third MOQ session with the application server; an identifier of the first user device; an identifier of each of the one or more second user devices or an identifier of the application server.

[0035] The resources of an MOQ media server used for a first MOQ session, one or more second MOQ sessions, or a third MOQ session of a service and application server may include at least one of the following: storage resources; or processing resources.

[0036] The method may include: receiving a request from a first user device to subscribe to media that can be published by one or more second user devices or an application server; and sending the media that can be published by one or more second user devices or an application server to the first user device.

[0037] Information used to establish a first QUIC connection between a first user equipment and an MOQ media server, and a first MOQ session via the first QUIC connection, may include: instructions for the first user equipment to operate as a publisher and subscriber of media via the first MOQ session; and information used to establish a second QUIC connection between a second user equipment and an MOQ media server, and a second MOQ session via the second QUIC connection, may include: instructions for the second user equipment to operate as a publisher and subscriber of media via the second MOQ session.

[0038] The method may include: sending information to a first user equipment for establishing a first QUIC connection between the first user equipment and an MOQ media server and a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the MOQ media server; and sending information to each of one or more second user equipments for establishing a second QUIC connection between the second user equipment and the MOQ media server and a second MOQ session through the second QUIC connection, wherein the information includes the namespace of the MOQ media server.

[0039] Information used to establish a first QUIC connection between a first user equipment and an MOQ media server, and a first MOQ session via the first QUIC connection, may include: instructions for the MOQ media server to operate as a publisher and subscriber of media via the first MOQ session; and information used to establish a second QUIC connection between a second user equipment and an MOQ media server, and a MOQ session via the second QUIC connection, may include: instructions for the MOQ media server to operate as a publisher and subscriber of media via the second MOQ session.

[0040] The combined MOQ directory can include the namespace of the MOQ media server.

[0041] The media description of media that can be published by the first user equipment may include at least one of the following: a media description of media that can be published by the first user equipment through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the first user equipment through the first MOQ session but not processed by the MOQ media server.

[0042] The media description of media that can be published by a second user equipment may include at least one of the following: a media description of media that can be published by one or more second user equipments through a first MOQ session and processed by an MOQ media server; or a media description of media that can be published by one or more second user equipments through a first MOQ session but is not processed by an MOQ media server.

[0043] The media description of media that can be published by the application server may include at least one of the following: a media description of media that can be published by the application server through a third MOQ session and processed by the MOQ media server; or a media description of media that can be published by the application server through a third MOQ session but not processed by the MOQ media server.

[0044] The combined catalog may include media descriptions of media that are publishable by a first user device through a first MOQ session and by one or more second user devices through one or more MOQ sessions and processed by the MOQ media server.

[0045] Processing may include transcoding, compositing, encapsulation, combining, or rejection.

[0046] Media that can be published by the first user equipment through the first MOQ session may include different versions of the same media content.

[0047] Media that can be published by each of one or more second user devices through a second MOQ session may include different versions of the same media content.

[0048] Media that can be published by the application server through a third MOQ session with the application server can include different versions of the same media content.

[0049] Different versions of the same media content can have different qualities (e.g., resolution) or can be encoded using different codecs.

[0050] The method may include: receiving from one or more second user devices a request to subscribe to receive media that can be published by a first user device or an application server, and sending the media that can be published by the first user device or an application server to one or more second user devices.

[0051] The MOQ media server may include at least one of the following: application functions of a cellular system; application server of a real-time communication system; media functions of an Internet Protocol Multimedia Subsystem; or multimedia resource functions of an Internet Protocol Multimedia Subsystem.

[0052] According to one aspect, a QUIC-based media server is provided, which includes components for performing steps of any of the methods described above.

[0053] According to one aspect, a QUIC-based media server is provided, comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform at least the steps of any of the methods described above.

[0054] According to one aspect, a QUIC-based media server is provided, which includes circuitry configured to perform steps of any of the methods described above.

[0055] According to one aspect, a method performed by a first user equipment is provided, the method comprising: receiving a combined MOQ catalog from a QUIC-based media MOQ server, the combined MOQ catalog including: media descriptions of media that can be published by the first user equipment, media descriptions of media that can be published by one or more second user equipments, or media descriptions of media that can be published by an application server; and a namespace of the first user equipment, one or more namespaces of one or more second user equipments, or a namespace of the application server; sending a request to the MOQ media server for subscribing to receiving media that can be published by one or more second user equipments or the application server; and receiving media that can be published by one or more second user equipments or the application server from the MOQ media server.

[0056] The method may include at least one of the following: sending a request to an MOQ signaling server to establish a communication session with one or more second user equipments, the request indicating that the MOQ transport protocol will be used for media transmission; receiving a response to the request from the MOQ signaling server, the response indicating acceptance of the request, the response including an identifier of the MOQ media server; after receiving the response to the request, sending information to the MOQ media server to establish a first QUIC connection between the first user equipment and the MOQ media server and a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the first user equipment; sending a first MOQ directory to the MOQ media server, the first MOQ directory including media descriptions of media that can be published by the first user equipment through the first MOQ session; or receiving the namespace of the MOQ media server from the MOQ media server.

[0057] A communication session can be used for a call. A call can be an audio / or video conference, a webinar, a game stream, or an event stream.

[0058] The media description may include at least one of the following: track name, track type, track creation date, track modification date, track size, track frame rate, track codec, or track namespace.

[0059] The terms "namespace", "address", or "resource identifier" can be used interchangeably.

[0060] The information may include instructions for the first user equipment to operate as a publisher and subscriber of media through the first MOQ session.

[0061] The method may include: receiving information from an MOQ media server for establishing a first QUIC connection between a first user equipment and an MOQ server, and a first MOQ session via the first QUIC connection, wherein the information includes the namespace of the MOQ media server.

[0062] The information may include instructions for the MOQ media server to operate as a publisher and subscriber of media through the first MOQ session.

[0063] The combined MOQ directory can include the namespace of the MOQ media server.

[0064] The media description of media that can be published by the first user equipment includes at least one of the following: a media description of media that can be published by the first user equipment through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the first user equipment through the first MOQ session but not processed by the MOQ media server.

[0065] The media description of media that can be published by a second user equipment may include at least one of the following: a media description of media that can be published by one or more second user equipments through a first MOQ session and processed by an MOQ media server; or a media description of media that can be published by one or more second user equipments through a first MOQ session but is not processed by an MOQ media server.

[0066] The media description of media that can be published by the application server may include at least one of the following: a media description of media that can be published by the application server through a third MOQ session and processed by the MOQ media server; or a media description of media that can be published by the application server through a third MOQ session but not processed by the MOQ media server.

[0067] The combined catalog may include media descriptions of media that are publishable by a first user device through a first MOQ session and by one or more second user devices through one or more MOQ sessions and processed by the MOQ media server.

[0068] Processing may include transcoding, compositing, encapsulation, combining, and / or rejection.

[0069] Media that can be published by the first user equipment through the first MOQ session may include different versions of the same media content.

[0070] Media that can be published by each of one or more second user devices through a first MOQ session may include different versions of the same media content.

[0071] Media published by the application server via a third MOQ session can include different versions of the same media content.

[0072] Different versions of the same media content can have different qualities (e.g., resolution) or can be encoded using different codecs.

[0073] The method may include sending at least one of the following to the MOQ signaling server: an indication that the first user equipment is capable of encoding and decoding media, an indication of the quality of media that can be published by the first user equipment, an indication of the quality of the radio link of the first user equipment, or an indication of user preferences of the first user equipment.

[0074] The method may include: sending a first MOQ directory to an MOQ signaling server, the first MOQ directory including a media description of media that can be published by a first user equipment through a first MOQ session and at least one of the following: an indication that the first user equipment is capable of encoding and decoding media, an indication of the quality of the media that can be published by the first user equipment, the quality of the radio link of the first user equipment, or the user preferences of the first user equipment.

[0075] The first MOQ catalog can be sent to the MOQ signaling server out of band (i.e., without the first MOQ session).

[0076] The first directory can be sent to the MOQ media server in-band (i.e., via the first MOQ session).

[0077] Sending a request to establish a communication session with one or more second user equipment may include: sending a session description protocol proposal indicating that the MOQ transport protocol will be used for the transmission of media, and wherein receiving a response to the request includes: receiving a session description protocol response indicating acceptance of the session description protocol proposal.

[0078] The Session Description Protocol (SDP) proposal and response are carried (e.g., included therein) using at least one of Session Initiation Protocol (SIP) signaling, Simple WebRTC Application Protocol (SIP) messages, or Hypertext Transfer Protocol (HTTP) messages. In other words, SIP signaling may include an SDP proposal or response, a SIP message may include an SDP proposal or response, or an HTTP message may include an SDP proposal or response.

[0079] According to one aspect, a first user equipment is provided, which includes components for performing steps of any of the methods described above.

[0080] According to one aspect, a first user equipment is provided, comprising at least one processor and at least one memory storing instructions, said instructions, when executed by the at least one processor, causing the device to perform at least the steps of any of the methods described above.

[0081] According to one aspect, a first user equipment is provided, which includes circuitry configured to perform steps of any of the methods described above.

[0082] According to one aspect, a method performed by a QUIC-based media server is provided, the method comprising: sending a combined MOQ catalog to a first user equipment, the combined MOQ catalog including: media descriptions of media publishable by the first user equipment, media descriptions of media publishable by one or more second user equipments, or media publishable by an application server; and namespaces of the media publishable by the first user equipment, one or more namespaces of the one or more second user equipments, or the namespace of the application server; receiving from the first user equipment a request to subscribe to the media publishable by the one or more second user equipments or the application server; and sending the media publishable by the one or more second user equipments or the application server to the first user equipment.

[0083] The method may include at least one of the following: receiving from an MOQ signaling server: an indication of resources to be allocated by an MOQ media server for serving a communication session with one or more second user equipments using the MOQ transport protocol for media transmission; and an indication of session information for at least one of the following: a first MOQ session between the MOQ media server and a first user equipment, one or more second MOQ sessions between the MOQ media server and one or more second user equipments, or a third MOQ session between the MOQ media server and an application server; allocating resources of the MOQ media server to serve the first MOQ session, one or more second MOQ sessions, or the third MOQ session; and receiving from the first user equipment a first QUIC for establishing a first user equipment-MOQ media server connection. The method includes: receiving information about a first MOQ session connected via a first QUIC connection, wherein the information includes the namespace of a first user equipment; receiving information from each of one or more second user equipments for establishing a second QUIC connection between the second user equipment and the MOQ media server and a second MOQ session connected via the second QUIC connection, wherein the information includes the namespace of the second user equipment; receiving a first MOQ directory from the first user equipment, the first MOQ directory including media descriptions of media that can be published by the first user equipment through the first MOQ session; or receiving a second MOQ directory from each of one or more second user equipments, the second MOQ directory including media descriptions of media that can be published by the second user equipment through the second MOQ session.

[0084] Session information for a first MOQ session, one or more second MOQ sessions with one or more user devices, or a third MOQ session with an application server may include at least one of the following: an identifier for the first MOQ session, one or more second MOQ sessions, or a third MOQ session with an application server; an identifier for the first user device; an identifier for each of the one or more second user devices or an identifier for the application server.

[0085] The resources of an MOQ media server used to serve a first MOQ session, one or more second MOQ sessions, or a third MOQ session with an application server may include at least one of the following: storage resources; or processing resources.

[0086] Information used to establish a first QUIC connection between a first user equipment and an MOQ media server, and a first MOQ session via the first QUIC connection, may include: instructions for the first user equipment to operate as a publisher and subscriber of media via the first MOQ session; and information used to establish a second QUIC connection between a second user equipment and an MOQ media server, and a second QUIC session via the second QUIC connection, includes: instructions for the second user equipment to operate as a publisher and subscriber of media via the second MOQ session.

[0087] The method may include: sending information to a first user equipment for establishing a first QUIC connection between the first user equipment and an MOQ media server and a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the MOQ media server; and sending information to each of one or more second user equipments for establishing a second QUIC connection between the second user equipment and the MOQ media server and a second MOQ session through the second QUIC connection, wherein the information includes the namespace of the MOQ media server.

[0088] Information used to establish a first QUIC connection between a first user equipment and an MOQ media server, and a first MOQ session via the first QUIC connection, may include: instructions for the MOQ media server to operate as a publisher and subscriber of media via the first MOQ session; and information used to establish a second QUIC connection between a second user equipment and an MOQ media server, and a second MOQ session via the second QUIC connection, may include: instructions for the MOQ media server to operate as a publisher and subscriber of media via the second MOQ session.

[0089] The combined MOQ directory can include the namespace of the MOQ media server.

[0090] The media description of media that can be published by the first user equipment may include at least one of the following: a media description of media that can be published by the first user equipment through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the first user equipment through the first MOQ session but not processed by the MOQ media server.

[0091] The media description of media that can be published by a second user equipment may include at least one of the following: a media description of media that can be published by one or more second user equipments through a first MOQ session and processed by an MOQ media server; or a media description of media that can be published by one or more second user equipments through a first MOQ session but is not processed by an MOQ media server.

[0092] The media description of media that can be published by the application server includes at least one of the following: a media description of media that can be published by the application server through a third MOQ session and processed by the MOQ media server; or a media description of media that can be published by the application server through a third MOQ session but not processed by the MOQ media server.

[0093] The combined catalog may include media descriptions of media that are publishable by a first user device through a first MOQ session and by one or more second user devices through one or more MOQ sessions and processed by the MOQ media server.

[0094] Processing may include transcoding, compositing, encapsulation, combining, or rejection.

[0095] Media that can be published by the first user equipment through the first MOQ session may include different versions of the same media content.

[0096] Media that can be published by each of one or more second user devices through a second MOQ session may include different versions of the same media content.

[0097] Media that can be published by the application server through a third MOQ session with the application server can include different versions of the same media content.

[0098] Different versions of the same media content can have different qualities (e.g., resolution) or can be encoded using different codecs.

[0099] The method may include: receiving from one or more second user devices a request to subscribe to receive media that can be published by a first user device or an application server; and sending media that can be published by the first user device or an application server to one or more second user devices.

[0100] The MOQ media server may include at least one of the following: application functions of a cellular system; application server of a real-time communication system; media functions of an Internet Protocol Multimedia Subsystem; or multimedia resource functions of an Internet Protocol Multimedia Subsystem.

[0101] According to one aspect, a QUIC-based media server is provided, which includes components for performing steps of any of the methods described above.

[0102] According to one aspect, a QUIC-based media server is provided, comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least the steps of any of the methods described above.

[0103] According to one aspect, a QUIC-based media server is provided, which includes circuitry configured to perform steps of any of the methods described above.

[0104] According to one aspect, a computer program is provided that includes computer-executable code, which, when run on at least one processor, is configured to perform any of the methods described above.

[0105] According to one aspect, a computer-readable medium is provided, comprising instructions that, when executed by a device, cause the device to perform any of the methods described above.

[0106] According to one aspect, a non-transitory computer-readable medium is provided, comprising program instructions that, when executed by a device, cause the device to perform any of the methods described above.

[0107] Many different aspects have been described above. As previously stated, it should be understood that additional aspects can be provided through any combination of two or more of the aforementioned aspects. Other features, aspects, and elements will become apparent in light of the following. Attached Figure Description

[0108] Some examples will now be described by way of non-limiting and illustrative means with reference to the accompanying drawings, in which: Figure 1 Examples of communication systems to which the examples disclosed herein can be applied are shown; Figure 2 A schematic representation of an example network node is shown; Figure 3 A schematic representation of an example of a user equipment (UE) is shown; Figure 4 A schematic diagram of a communication system is shown, including UE1, one or more UE2, a QUIC-based media (MOQ) signaling server (SS), and an MOQ media server (MS). Figure 5 The diagram shows an Internet Protocol Multimedia Subsystem Multimedia Telephony (MTSI) protocol stack extended to include QUIC for MTSI clients; Figure 6 The signaling and operation diagrams for performing real-time communication using MOQ are shown. Figure 7a and Figure 7b The signaling and operation diagrams for performing real-time communication using MOQ are shown. Figure 8 A schematic diagram of a system including MOQ SS and MOQ MS based on the Internet Multimedia Subsystem (IMS) is shown. Figure 9 A schematic diagram of a real-time communication (RTC) system including MOQ SS and MOQ MS is shown; Figure 10 A method for performing real-time communication using MOQ is shown, wherein the method is performed by a first UE; Figure 11 A method for performing real-time communication using MOQ is shown, wherein the method is performed by the MOQ MS; Figure 12 A method for performing real-time communication using MOQ is shown, wherein the method is performed by a first UE; and Figure 13 A method for performing real-time communication using MOQ is shown, wherein the method is performed by MOQ MS. Detailed Implementation

[0109] Some examples of this disclosure can be implemented in communication systems such as any of the following: Global Microwave Access Interoperability (WiMAX) systems, Global System for Mobile Communications (GSM, 2G), General Packet Radio Service (GRPS) systems, Universal Mobile Telecommunications System (UMTS, 3G) based on Basic Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA) systems, Long Term Evolution (LTE) systems, Advanced LTE systems and Enhanced LTE (eLTE) systems, 5G systems (also known as NR systems), or any future communication system such as 6G systems (e.g., communication systems operating according to 6th generation radio access technology). Furthermore, communication within the communication system can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), and / or Discrete Fourier Transform Extended OFDM (DFT-s-OFDM).

[0110] As used herein, the term "network node" can refer to a node in a communication system through which a UE can access the core network of the communication system. A network node can be a radio access network node (e.g., a base station) (BS), an access point (AP), or an access node. In various implementations, a "network node" is a radio access network node (e.g., a base station) that controls radio communications and manages the radio resources of the cell provided by the base station. A radio access network node (e.g., a base station) can be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node, a non-terrestrial network (NTN) or non-land network node (such as a satellite network node, a low Earth orbit (LEO) satellite, and a geostationary Earth orbit (GEO) satellite), or an aircraft network node.

[0111] Furthermore, in some implementations, the radio access network can have a split architecture. In these implementations, network nodes can refer to the central unit (CU) of a radio access network node (e.g., a base station), the distributed unit (DU), and / or the radio unit (RU) of a radio access network node (e.g., a base station). The central unit can also be referred to as a centralized unit. The interface between the CU and the DU may be referred to as the F1 interface in NR. In a split RAN architecture, node operations can be performed at least partially in a CU (e.g., a server, host, or node) that is operationally coupled to a DU (e.g., a radio head / node). A CU can control one or more DUs, at least acting as a transmit / receive (Tx / Rx) node. In some examples, a DU may include, for example, a Radio Link Control (RLC), a Media Access Control (MAC) layer, and a Physical (PHY) layer, while the CU may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, the Radio Resource Control (RRC) layer, and the Internet Protocol (IP) layer. Further functional splitting of the functions of a radio access network node (e.g., a base station) is possible. Any processing task of a radio access network node can be performed in the CU or DU. Which processing tasks are performed by the CU and which are performed by the DU depends on the functional division of processing tasks between the CU and DU.

[0112] The term "UE" can refer to any terminal device capable of wireless communication. As examples, a UE can be referred to as a communication device, subscriber station (SS), or mobile station (MS). UEs can include mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable UEs, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition UEs (such as digital cameras), gaming UEs, music storage and playback devices, in-vehicle wireless UEs, USB dongles, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and so on.

[0113] Figure 1 An example of a communication system to which the examples disclosed herein can be applied is shown. The communication system may include a network node 90 providing one or more cells (such as cell 100) and a network node 92 providing one or more other cells (such as cell 102). For example, each cell may be a macrocell, microcell, femtocell, or picocell. Cells 100 and 102 may define the coverage area or service area of ​​the network nodes 90 and 92 providing that cell.

[0114] Network node 90 can provide radio access to the communication system to UE 120 (one or more UEs). Radio access can include downlink (DL) communication from network node 90 to UE 120 and uplink (UL) communication from UE 120 to network node 90. UL communication can be performed over uplink channels, which include, for example, a Physical Uplink Control Channel (PUCCH) for sending control information to network node 90 and a Physical Uplink Shared Channel (PUSCH) for sending data to network node 90. DL communication can be performed over downlink channels, which include, for example, a Physical Downlink Control Channel (PDCCH) for sending control information to UE 120 and a Physical Downlink Shared Channel (PDSCH) for sending data to UE 120.

[0115] Multiple UEs 120 and 122 can exist and communicate with the communication system. Each UE can be served by the same or different network nodes 90 and 92. UEs can be configured with dual connectivity (DC), where a UE (e.g., UE 120) can connect to multiple network nodes 90 and 92. UEs 120 and 122 can communicate with each other when a device-to-device (D2D) communication interface is established between UEs 120 and 122 via a so-called side link (SL). For example, such D2D communication can be referred to as machine-to-machine, peer-to-peer (P2P) communication, or vehicle-to-vehicle (V2V) communication.

[0116] In the case of multiple network nodes in a communication system, the network nodes can connect to each other via interfaces. For example, LTE network nodes can connect to each other via an interface called the X2 interface. The interface between an LTE node and a 5G node, or between two 5G nodes, can be referred to as the Xn interface. Network nodes 90 and 92 can also connect to the core network 96 of the communication system via another interface.

[0117] Figure 2 A schematic representation of an example of means for a network node 200 (which may be an example of network node 90 or network node 92 previously described) is shown. The means for network node 200 may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and a network interface 214. At least one processor 212, 213 may be coupled to RAM 211a and ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215 (e.g., instructions). The software code 215 (e.g., instructions) may, for example, be configured to, when executed by one or more of the at least one processor, cause the means for the network node to perform one or more operations described herein. The software code 215 (e.g., instructions) may be stored in ROM 211b. Network node 200 may receive wireless signals (e.g., radio signals) via air or radio interface 307 via appropriate means for receiving wireless (e.g., radio) signals, and may transmit wireless (e.g., radio) signals via a transceiver. A transceiver may include, for example, radio components and an associated antenna arrangement. The antenna arrangement may include one or more antenna elements.

[0118] Figure 3 A schematic representation of an example of UE 300 (which may be an example of UE 120 or UE 122 previously described) is shown. UE 300 can receive signals via air or radio interface 307 via appropriate means for receiving radio signals, and can transmit signals via appropriate means for transmitting radio signals. Figure 3In this context, a suitable device may be a transceiver schematically specified by block 306. Transceiver 306 may include, for example, radio components and an associated antenna arrangement. The antenna arrangement may be located inside or outside the UE 300. The antenna arrangement may include one or more antenna elements.

[0119] UE 300 may include at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for software and hardware-assisted execution of tasks configured for the UE to perform, including control of access and communication with network nodes and other UEs. At least one processor 301 is coupled to RAM 302b and ROM 302a. At least one processor 301 may be configured to execute appropriate software code 308 (e.g., instructions). The software code 308 (e.g., instructions) may, for example, be configured to cause the UE to perform the operations described herein when executed by at least one processor. The software code 308 (e.g., instructions) may be stored in ROM 302a.

[0120] At least one processor, RAM 302b, and ROM 302a may be disposed on a suitable circuit board and / or in a chipset. This feature is indicated by reference numeral 304. UE 300 may optionally include a user interface, such as a keypad 305, a touch-sensitive screen or touch pad, or combinations thereof. Optionally, UE 300 may include one or more of a display device (e.g., a touchscreen display), a speaker, a microphone, and / or an input device.

[0121] UE and communication systems (such as Figure 1 The communication system (in the context) may have an RTC architecture for transmitting media, as described in, for example, 3GPP TS 26.501, 26.510, and 26.512. Alternatively, the communication system (e.g. Figure 1 The communication system (in this context) may include an IMS-based architecture for delivering media, as described, for example, in 3GPP TS 23.229 and 26.114. A communication system including an IMS configured for media delivery is referred to herein as an IMS-based system.

[0122] As previously mentioned, recent QUIC-based media (MOQ) has been developed for media delivery (e.g., media delivery). QUIC is an end-to-end encrypted transport layer protocol running on User Datagram Protocol (UDP). MOQ has the potential to coordinate media delivery protocols (e.g., protocols used for media delivery), including HTTP-based live and video-on-demand video delivery (e.g., DASH, HLS) as well as RTP-based video conferencing delivery and other real-time applications (e.g., WebRTC, MTSI).

[0123] MOQ, or MOQ Transport (MOQT), enables media producers to publish data and consume it via subscriptions across multiple endpoints. As used herein, MOQ and MOQT are used interchangeably. MOQ supports Content Delivery Networks (CDNs) and is particularly well-suited for large-scale, low-latency distribution of content to servers. MOQ features a hierarchical object model for data, including objects, subgroups, groups, and tracks.

[0124] Objects are the basic data elements of MOQ. An object is an addressable unit with a payload as a sequence of bytes. All objects belong to groups, indicating ordering and potential dependencies. Objects are uniquely identified by their track namespace, track name, group identity (ID), and object identity (ID), and must be the same sequence of bytes regardless of how or where the object is retrieved. Objects may become unavailable, but their contents do not change over time.

[0125] The object consists of two parts: metadata and a payload. The metadata is unencrypted and visible to the relay. The payload can be encrypted, in which case it is only visible to the original publisher and the final subscriber. The application or application function that generates the media is responsible for the content of the object's payload, as well as the underlying encoding, compression, and any end-to-end encryption or authentication. The relay will not combine, split, or otherwise modify the object's payload.

[0126] A sequence of one or more objects from the same group can be grouped into subgroups in ascending order by object ID. Objects within a subgroup have dependencies and priorities consistent with the shared QUIC stream. In some cases, more than one QUIC stream can be used to deliver groups most efficiently.

[0127] Each object within a group may belong to exactly one subgroup. Objects from two subgroups cannot be sent on the same QUIC stream. Objects from the same subgroup cannot be sent on different QUIC streams unless one of the streams is prematurely reset, or upstream conditions force objects from the subgroups to be sent out of order of object ID.

[0128] A group is a time sequence of objects and a sub-unit of a track. Objects within a group do not depend on objects in other groups. A group can act as a connection point for subscriptions; for example, a new subscriber might not want to receive the entire track but can choose to receive only the latest (or multiple) groups. The publisher then selectively sends objects based on their group membership.

[0129] A track is a sequence of groups. It is the entity to which a subscriber makes a subscription request. A subscriber can request to receive individual tracks starting from the group boundary, including any new objects pushed by the publisher when a track is active.

[0130] In MOQ, each track has a name (often called the track name) and a namespace associated with that name (often called the track namespace). The track name identifies the individual track within the track namespace. The track namespace can be an ordered N-tuple of bytes, where N can be between 1 and 32. The structured nature of the track namespace allows for the relaying and application manipulation of prefixes to the track namespace. The track name is a sequence of bytes.

[0131] An MOQ range is a set of servers (identified by their connection URIs) for which a tuple of track name and track namespace is guaranteed to be unique and identifies a specific track. The application using the MOQ defines how wide or narrow the MOQ range is. Applications handling connections between devices on a local network can limit their MOQ range to a single connection; in contrast, applications using multiple CDNs to serve media may require an MOQ range that includes all of those CDNs.

[0132] An HTTPS URI can be used to identify an MOQ server accessible via WebTransport. An MOQ session can be established by sending an extended connection request to the host along with the path indicated by the URI. An MOQ server accessible via local QUIC can be identified by a URI with the “moq” scheme. A URI with the “moq” scheme can be defined, for example, in Clause 3.1.2 of “Media over QUIC Transport” by Curley, L. et al., in progress, Internet Draft, draft-ietf-moq-transport-07, October 21, 2024.

[0133] MOQ defines a variety of control messages that are exchanged between a client (the party that initiates the MOQ session) and the MOQ server (the party that accepts incoming transport sessions) via a single bidirectional stream.

[0134] To establish an MOQ session, the client and server can exchange CLIENT_SETUP and SERVER_SETUP messages, enabling them to set up (e.g., establish) a mutually compatible MOQ session and agree on the initial configuration of the MOQ session before exchanging any objects between the client and server. CLIENT_SETUP and SERVER_SETUP messages can include a sequence of key-value pairs called setup parameters; their semantics and format can vary depending on whether the client or server is sending them.

[0135] Once an MOQ session has been established between the client and server (e.g., set up), a subscriber (the endpoint that subscribes to and receives tracks (e.g., the client)) can send a subscription message to the publisher (the endpoint that handles the subscription by sending the requested object of the requested track (e.g., the server)) to request the track. A subscriber can also send a SUBSCRIBE_UPDATE message to the publisher to request a change to the client's previous subscription on the server.

[0136] A subscriber can be a final subscriber (a subscriber who initiates a subscription but does not send data to other subscribers), or an intermediary or relay between a final subscriber and the original publisher (the initial publisher of a given track). When a subscriber is a relay, the relay can act as a subscriber relative to the original publisher (i.e., the relay can subscribe to the original publisher to request a track) and can act as a publisher relative to the final subscriber (i.e., the relay can publish a request for a track to the final subscriber).

[0137] Publishers can send "announcement" control messages to inform recipients where they can subscribe to track routing messages within the announced track namespace. Recipients can verify that the publisher is authorized to publish tracks under the announced track namespace.

[0138] MOQ requires long-lived, stateful sessions. However, service providers need the ability to shut down and / or restart servers without waiting for all sessions to run out naturally, which can take days for long-format media. MOQ avoids this by sending a "GOAWAY" message. The server can send a "GOAWAY" message to signal to clients that a new session should be established and any active subscriptions migrated to the new session. The "GOAWAY" message can include a new URI for the new session; otherwise, the current URI is reused. If there are still open subscriptions on the session, the server can terminate the session with a "GOAWAY timeout" message after a sufficient timeout period.

[0139] A "Leave" message may not immediately affect subscription status. Subscribers can unsubscribe from each existing subscription individually for the server, and the server can reject new subscription requests if it is in a state of exhaustion. When the server is a relay (i.e., both a publisher and a subscriber), it can send a "Leave" message before any "unsubscribe" message.

[0140] After receiving a "Leave" message, the client can wait until there are no more active subscriptions before closing the session. This can be transparent to applications using MOQ; for example, a new session can be established in the background, and active subscriptions and announcements can be migrated accordingly. If the client expects more objects to be delivered, it can choose to delay closing the session. If the client does not close the session quickly enough, the server can use a "Leave Timeout" message to close the session.

[0141] As previously mentioned, MOQ has not yet been adopted for use in 3GPP architectures for media delivery (e.g., media transport), such as 5GMS architecture or IMS-based architecture for media transport (e.g., media delivery). Communication systems with a 5GMS architecture for media transport are referred to herein as 5GMS systems, and communication systems with IMS-based architecture for media transport are referred to herein as IMS-based systems. Furthermore, communication systems with a general real-time communication (RTC) architecture based on a 5GMS architecture are referred to herein as RTC systems. The roles of the different MOQ entities and their interactions in the publish / subscribe model have not been disclosed, particularly in multi-UE use cases where each UE can operate as both a publisher and a subscriber.

[0142] Figure 4 A schematic diagram of a UE (e.g., UE1, UE2(1) and UE2(2)) communicating with an MOQ signaling server (SS) and an MOQ media server (MS) is shown.

[0143] The MOQ SS can be configured to enable the UE and MOQ MS to establish (e.g., create) an MOQ session between the UE. Session Initiation Protocol (SIP) signaling (e.g., a message) containing (e.g., including) a Session Description Protocol (SDP) message describing the MOQ session, or WebRTC Application Protocol (SWAP) signaling containing (e.g., including) a Session Description Protocol (SDP) message describing the MOQ session, can be used to establish (e.g., create) an MOQ session between the UE. The SDP message includes parameters for establishing (e.g., creating) the MOQ session.

[0144] The MOQ SS can be configured to provide authorization and / or authentication to establish an MOQ session. The MOQ SS can be configured to locate the UE to establish an MOQ session via the MOQ MS. The MOQ SS can be configured to locate the MOQ MS to establish an MOQ session.

[0145] The MOQ SS can be configured to control the MOQ session after it has been established (e.g., set up). For example, the MOQ SS can be configured to terminate the MOQ session in response to a request from a UE operating as a publisher (e.g., using a "leave" message). The MOQ SS can be configured to add a UE operating as a subscriber to the MOQ session in response to a request from a UE operating as a subscriber. The MOQ SS can be configured to suspend the MOQ session. The MOQ SS can be configured to resume the MOQ session.

[0146] The MOQ MS can be configured to operate as a selective forwarding unit. An MOQ MS configured to operate as a selective forwarding unit can transmit only media that can be published by a UE operating as a publisher active on the MOQ session. The MOQ MS can also be configured to operate as a multipoint control unit. An MOQ MS configured to operate as a multipoint control unit can perform mixing (e.g., combining multiple media into a single media to be transmitted through the MOQ session), transcoding (e.g., changing the format of a video stream), and rate conversion to optimize data transmission rates. For example, the MOQ MS can i) recode media received from one or more UEs using, for example, different resolutions, qualities, or bit rates to match the requirements of the UE and the network, ii) mix multiple media streams, for example, by encapsulating video from multiple UEs into a single frame.

[0147] The MOQ MS can be configured to operate as a publisher and / or subscriber via an MOQ session. Media transmitted by the MOQ MS can be initially generated by the UE (e.g., the MOQ MS is a relay) or by the MOQ MS (e.g., the MOQ MS is an endpoint).

[0148] The UE can be configured to operate as a publisher and / or subscriber via an MOQ session. The media transmitted by the UE can initially be generated by the UE (e.g., the UE is an endpoint).

[0149] The UE can be configured to send information to the MOQ SS indicating its ability to encode and / or decode media. The UE can be configured to send to the MOQ SS a media description of media that can be published by the UE. The UE can be configured to send to the MOQ SS information indicating the quality of the UE's radio link. The UE can be configured to send to the MOQ SS information indicating the quality of media that can be published by the UE. The UE can be configured to send to the MOS SS information indicating the user preferences of the UE's user. One or more of the following information—indicating the UE's capabilities, the media description of media that can be published by the UE, the quality of the UE's radio link, the quality of media that can be published by the UE, or the user preferences of the UE's user—can be sent by the UE to the MOQ SS out of band (i.e., not through the MOQ session). For example, one or more of the following information may be sent by the UE: information indicating the UE's capabilities, a media description of media that can be published by the UE, information indicating the quality of the UE's radio link, information indicating the quality of media that can be published by the UE, or information indicating the user's preferences. These information may be sent by the UE in SIP signaling (e.g., a SIP message) that also includes (e.g., SDP messages) or in SWAP signaling (e.g., a SWAP message) that includes (e.g., SDP messages), or may be included in the MOQ catalog sent by the UE to the MOQ SS. Alternatively, one or more of the following information may be sent by the UE to the MOQ SS in-band (i.e., via the MOQ session): information indicating the UE's capabilities, a media description of media that can be published by the UE, information indicating the quality of the UE's radio link, information indicating the quality of media that can be published by the UE, or information indicating the user's preferences. For example, the MOQ catalog may include one or more of the following: information indicating the UE's capabilities, a media description of media that can be published by the UE, information indicating the quality of the UE's radio link, information indicating the quality of media that can be published by the UE, or information indicating the user's preferences.

[0150] The MOQ SS can be configured to send information to the MOQ MS indicating the UE's ability to encode or decode media. The MOQ SS can be configured to send to the MOQ MS a media description of media that can be published by the UE. The MOQ SS can be configured to send to the MOQ MS information indicating the quality of the UE's radio link. The MOQ SS can be configured to send to the MOQ MS information indicating the quality of media that can be published by the UE. The MOQ SS can be configured to send to the MOQ MS information indicating the user preferences of the UE's user. One or more of the following information—indicating the UE's ability to encode or decode media, a media description of media that can be published by the UE, an indication of the quality of the UE's radio link, information indicating the quality of media that can be published by the UE, or information indicating the user preferences of the UE's user—can be sent by the MOQ SS out-of-band (i.e., not through the MOQ session).

[0151] The MOQ SS can be configured to send information to the MOQ MS indicating resources to be allocated by the MOQ MS to the MOQ session. Resources to be allocated by the MOQ MS to the MOQ session may include the MOQ MS's memory resources and / or processing resources to be allocated to the MOQ session.

[0152] The MOQ SS can be configured to send session information of the MOQ session to the MOQ MS. The session information of the MOQ session may include the identifier of the MOQ session and / or the identifier of the UE.

[0153] Media can be exchanged between UEs via the MOQ MS. The MOQ MS can relay the media exchanged between UEs with or without processing the media (e.g., transcoding or mixing media streams from the UE). Media processing at the MOQ MS may increase latency, but it can reduce media processing at the UE.

[0154] Figure 5 The MTSI protocol stack, including QUIC for MTSI clients, is shown. Note that MOQ can run on either QUIC or WebTransport. Additionally, WebTransport requires HTTP / 3 setup.

[0155] The QUIC layer can have MOQ, RTP over QUIC (ROQ) [draft-ietf-avtcore-rtp-over-quic-12], or WebTransport [draft-ietf-webtrans-http3-11] as a higher layer. HTTP / 3 can also be used (e.g., for non-real-time business over the same QUIC connection).

[0156] Figure 6 The signaling and operation diagrams for establishing an MOQ session and performing real-time communication using the MOQ media are shown. The process involves a first UE (shown and referred to as UE1), a second UE (shown and referred to as UE2), an MOQ SS (shown as SS), and an MOQ MS (shown as MS).

[0157] exist Figure 6 In the example process shown, SIP signaling (e.g., messages) is used to describe the establishment (e.g., creation) of an MOQ session. However, it should be understood that in an RTC system, the establishment (e.g., creation) of an MOQ session can be performed using a SWAP message on a websocket that follows the JavaScript Object Notation (JSON) session establishment protocol according to RFC 8829, as described in further detail below. The process of using MOQ for real-time media communication begins in step 1.

[0158] In step 1, UE1 sends a request to MOQ SS to establish a communication session with UE2.

[0159] It should be understood that, despite Figure 6 Only a single second UE (e.g., UE2) is shown, but UE1 may send a request to the MOQ SS to set up communication sessions with multiple second UEs (e.g., UE 2(1), UE 2(2), etc.). In the following, the steps are described as being performed by a single second UE (e.g., UE2); however, it should be understood that in the implementation, UE1 sends a request to the MOQ SS to set up communication sessions with multiple second UEs (e.g., UE2(1), UE2(2), etc.), and these steps may be performed by each of the multiple UE2s (e.g., UE2(1), UE2(2), etc.).

[0160] A communication session can be used for calls (e.g., audio / or video conferencing, webinars, game streaming, or event streaming). The request can instruct the MOQ transport protocol to be used for media transmission. The request may include a Session Description Protocol (SDP) proposal, which instructs the MOQ transport protocol to be used for media transmission. Figure 6 In the example shown, a Session Initiation Protocol (SIP) signaling (e.g., a SIP message) sent by UE1 to the MOQ SS can be used to carry an SDP proposal. In other words, the request sent by UE1 in step 1 can be SIP signaling (e.g., a SIP message) that includes an SDP proposal (in... Figure 6 (This is shown as a SIP proposal used to establish an MOQ call). As mentioned above, although... Figure 6The example shown is a SIP signaling message that includes an SDP proposal, but in other implementations, the request could be a Simple WebRTC Application Protocol (SWAP) message or a Hypertext Transfer Protocol (HTTP) message that includes an SDP proposal.

[0161] In step 2, the MOQ SS sends a request to UE2 to establish (e.g., set up) a communication session with UE2. This request may indicate that MOQ transport will be used for media transmission. The request may include an SDP proposal indicating that the MOQ transport protocol will be used for media transmission. Figure 6 In the example shown, SIP can be used to carry the SDP proposal. In other words, alternatively, the MOQ SS can use SWAP or HTTP to carry the SDP proposal.

[0162] At step 3, UE2 sends a response to the MOQ SS requesting the establishment of a communication session with UE2. This response may indicate acceptance of the request. The response may include an SDP response (e.g., OK) indicating acceptance of the SDP proposal. SIP can be used to carry the SDP response. In other words, the response may include SIP signaling (e.g., a SIP message) containing the SDP response. Alternatively, SWAP or HTTP can be used to carry the SDP proposal (e.g., OK).

[0163] At step 4, the MOQ SS selects the MOQ MS. The selection of the MOQ MS by the MOQ SS may be based on: information indicating the ability of UE1 to encode or decode media, information indicating the ability of UE2 to encode or decode media, information indicating the ability of the MOQ MS to encode or decode media, information indicating the user preferences of the user of UE1, information indicating the user preferences of UE2, information indicating the quality of the radio link of UE1, information indicating the quality of the radio link of UE2, information indicating the quality of media that can be published by UE1 through a first MOQ session with the MOQ MS, and / or information indicating the quality of media that can be published by UE2 through a second MOQ session with the MOQ MS.

[0164] The MOQ SS determines the resources to be allocated by the MOQ MS for a first MOQ session with the MOQ MS. The MOQ SS may also determine the resources to be allocated by the MOQ MS for a second MOQ session with the MOQ MS. Resources may include processing resources and / or memory resources.

[0165] The MOQ SS determines session information for a first MOQ session with the MOQ MS. This session information may include the identifier of the first MOQ session with the MOQ MS and / or the identifier of UE1. The MOQ SS can also determine session information for a second MOQ session with the MOQ MS. This session information may include the identifier of the second MOQ session with the MOQ MS and / or the identifier of UE2.

[0166] The MOQ SS sends one or more requests to the MOQ MS to allocate resources for a first MOQ session with the MOQ MS and for a second MOQ session with the MOQ MS. The one or more requests may include indications of the resources to be allocated by the MOQ MS for the first MOQ session with the MOQ MS. The one or more requests may include indications of the resources to be allocated by the MOQ MS for the second MOQ session with the MOQ MS. The one or more requests may include one or more SDP proposals. Here, SIP can be used to carry the one or more SDP proposals. Alternatively, SWAP or HTTP can be used to carry the SDP proposals.

[0167] The MOQ SS sends one or more messages to the MOQ MS, including indications of session information for a first MOQ session with the MOQ MS. The MOQ SS may also send indications of session information for a second MOQ session with the MOQ MS.

[0168] The MOQ SS sends one or more of the following messages to the MOQ MS: an indication of UE1's ability to encode or decode media, an indication of UE2's ability to encode or decode media, an indication of UE1's user preferences, an indication of UE2's user preferences, an indication of the quality of UE1's radio link, an indication of the quality of UE2's radio link, an indication of the quality of media that UE1 can publish through a first MOQ session with the MOQ MS, and an indication of the quality of media that UE2 can publish through a second MOQ session with the MOQ MS.

[0169] At step 5, the MOQ MS sends one or more responses (e.g., one or more acknowledgments) to the MOQ MS in response to one or more requests, to allocate resources for servicing the first MOQ session with the MOQ MS, and to allocate resources for the second MOQ session with the MOQ MS. The one or more responses include an indication that the resources for servicing the first MOQ session with the MOQ MS and the resources for the second MOQ session with the MOQ MS have been allocated by the MOQ MS.

[0170] At step 6, the MOQ SS sends a response to UE1 in response to a request to establish (e.g., set up) a communication session with UE2. This response may indicate acceptance of the request. The response may include the identity of the MOQ MS. The identity of the MOQ MS identifies the MOQ MS. The response may include an SDP response (e.g., OK) indicating acceptance of the SDP proposal. In some implementations, SIP signaling may be used to carry the SDP proposal. In other words, the response may be SIP signaling (e.g., a SIP message) including an SDP response. In some embodiments, a SWAP message or an HTTP message may be used to carry the SDP proposal. In other words, the response may be a SWAP message including an SDP response or an HTTP message including an SDP response.

[0171] At step 7, a first QUIC connection is established (e.g., established) between UE1 and MOQ MS.

[0172] At step 8, a second QUIC connection is established (e.g., a second QUIC connection is created) between UE2 and MOQ MS.

[0173] In some implementations, UE1 can trigger the establishment (e.g., establishment) of a QUIC connection with UE1. UE2 can trigger the establishment (e.g., establishment) of a QUIC connection with UE2.

[0174] In some implementations, MOQ MS can trigger the establishment (e.g., establishment) of the first QUIC connection with UE1. MOQMS can also trigger the establishment (e.g., establishment) of a QUIC connection with UE2.

[0175] It can be noted that the establishment (e.g., setup) of a QUIC connection is defined in RFC 9000.

[0176] At step 9, a first MOQ session is established (e.g., created) between UE1 and MOQ MS via a first QUIC connection.

[0177] UE1 sends a message (e.g., an MOQ setup message) to the MOQ MS, which includes instructions for UE1 to operate as a publisher of media through the first MOQ session and a subscriber of media through the first MOQ session.

[0178] UE1 receives a message (e.g., an MOQ setup message) from the MOQ MS, which includes instructions for the MOQ MS to operate as a publisher and subscriber of media through the first MOQ session.

[0179] At step 10, a second MOQ session is established (e.g., created) between UE2 and MOQ MS via a second QUIC connection.

[0180] Although not shown, during setup (e.g., establishing a second MOQ session), UE2 sends a message (e.g., an MOQ setup message) to the MOQ MS, which includes instructions for UE2 to operate as a publisher and subscriber of media through the second MOQ session.

[0181] UE2 receives a message (e.g., an MOQ setup message) from the MOQ MS, which includes instructions for the MOQ MS to operate as a publisher of media through the second MOQ session and a subscriber of media through the second MOQ session.

[0182] UE1 sends a message (e.g., an announcement message) to the MOQ MS that includes UE1's namespace.

[0183] UE2 sends a message (e.g., an announcement message) to the MOQ MS that includes UE2's namespace.

[0184] In this disclosure, the terms "namespace", "address" or "resource identifier" are used interchangeably.

[0185] UE1 can receive requests from the MOQ MS through the first MOQ session. This request may be a request to subscribe to receive the first MOQ catalog from UE1.

[0186] UE1 can receive requests from the MOQ MS through a second MOQ session. These requests can be requests to subscribe to receive a second MOQ catalog from UE2.

[0187] In step 11, UE1 sends a first MOQ directory to the MOQ MS via a first MOQ session. The first MOQ directory may include a media description of media that UE1 can publish via the first MOQ session. The first MOQ directory may include the namespace of the media that UE1 can publish via the first MOQ session. The first MOQ directory may include information indicating the media that UE1 is capable of encoding or decoding. The first MOQ directory may include information indicating the quality of UE1's radio link. The first MOQ directory may include information indicating the quality of the media that UE1 can publish via the first MOQ session. The first MOQ directory may include information indicating the user preferences of UE1's user.

[0188] At step 12, UE2 sends a second MOQ directory to UE1 via the MOQ MS through a second MOQ session. The second MOQ directory may include a media description of media that UE2 can publish through the MOQ session. The second MOQ directory may include the namespace of the media that UE2 can publish through the second MOQ session. The second MOQ directory may include information indicating that UE2 is capable of encoding or decoding media. The second MOQ directory may include information indicating the quality of UE2's radio link. The first MOQ directory may include information indicating the quality of media that UE2 can publish through the MOQ session. The second MOQ directory may include information indicating user preferences of UE2's user.

[0189] Media that can be published by UE1 through the first MOQ session may include tracks. Media that can be published by UE1 through the first MOQ session may include audio content and / or video content. Media that can be published by UE1 through the first MOQ session may include different versions of the same audio and / or video content. Different versions of the same audio and / or video content may have different qualities and / or may be encoded with different codecs.

[0190] Media that can be published by UE2 through a second MOQ session may include tracks. Media that can be published by UE2 through a second MOQ session may include audio content and / or video content. Media that can be published by UE2 through a second MOQ session may include different versions of the same audio and / or video content. Different versions of the same audio and / or video content may have different qualities and / or may be encoded using different codecs.

[0191] In step 13, UE1 sends a request to the MOQ MS through the first MOQ session. This request can be relayed to UE2 by the MOQ MS through the second MOQ session. The request can be a request to subscribe to media that can be published by UE2 through the second MOQ session.

[0192] In step 14, UE2 sends a request to the MOQ MS via the second MOQ session. This request can be relayed to UE1 by the MOQ MS via the first MOQ session. The request can be a request to subscribe to media that can be published by UE1 via the MOQ session.

[0193] In step 15, UE1 publishes (i.e., transmits) media to the MOQ MS through the first MOQ session. This media can then be published (i.e., relayed) to UE2 by the MOQ MS through the second session.

[0194] At step 16, UE2 publishes (i.e., transmits) media to the MOQ MS via the second MOQ session. This media can be published (i.e., relayed) to UE2 by the MOQ MS via the second session.

[0195] It should be understood that this is achievable. Figure 6 Variations of the process shown. For example, additions or omissions may be made. Figure 6 Some steps of the process shown are illustrated. Additionally or alternatively, the order of the steps may be changed.

[0196] It should be understood that MOQ SS and MOQ MS can be implemented in several ways.

[0197] In a 5GMS system, an MOQ SS can be a Media Application Function (AF) and / or a Media Application Server (AS), and an MOQ MS can be a Media AS as defined in 3GPP TS 26.501.

[0198] In IMS-based systems, the Call Session Control Function (CSCF) and / or IMS Application Server (AS) may include MOQ SS and Media Function (MF), or the Multimedia Resource Function (MRF) may include MOQ MS (such as...). Figure 8 (As shown). In some implementations, the IMS data channel signaling function may involve establishing (e.g., setting up) MOQ sessions between UE1 and UE2 and an external AS.

[0199] External ASs can operate as publishers and / or subscribers through MOQ sessions. Media sent by an external AS can initially be generated by another AS, in which case the external AS is a relay; or it can be generated by an external AS, in which case the external AS is an endpoint.

[0200] In an RTC system, the RTC AS can include MOQ MS and MOQ SS (such as...). Figure 9 (As shown).

[0201] MoQ can be used in 3GPP systems with real-time architectures (e.g., 5GMS systems, IMS-based systems, or RTC systems) to support multi-UE use cases for real-time multimedia communication. Multi-UE use cases include: symmetric scenarios, where the number of UEs operating as producers is the same as the number of UEs operating as subscribers (e.g., the number of UEs operating as producers and subscribers is equal); and asymmetric scenarios, where the number of UEs operating as producers differs from the number of UEs operating as subscribers (e.g., the number of UEs operating as producers is less than or greater than the number of UEs operating as subscribers).

[0202] Figure 7a and Figure 7b The signaling and operation diagrams for establishing an MOQ session and exchanging media between a first UE (shown as UE1) and a second UE (shown as UE2) are shown. Figure 7a and Figure 7b The process shown involves UE1, UE2, MOQ SS (shown as SS) and MOQ MS (shown as MS).

[0203] exist Figure 7a and Figure 7b The signaling shown is a SWAP message over a WebSocket. This process can be implemented in an RTC system.

[0204] In step 1, UE1 sends a request to MOQ SS to establish (e.g., establish) a communication session with UE2 (e.g., UE(1) or UE2(2)).

[0205] It should be understood that, despite Figure 7a and Figure 7b Only a single second UE (e.g., UE2) is shown, but UE1 can send a request to the MOQSS to set up communication sessions with multiple second UEs (e.g., UE2(1), UE2(2), etc.). In the following, the steps are described as being performed by a single second UE (e.g., UE2); however, it should be understood that in various implementations, UE1 sends a request to the MOQ SS to set up communication sessions with multiple second UEs (e.g., UE2(1), UE2(2), etc.), and these steps can be performed by each of the multiple UE2s (e.g., UE2(1), UE2(2), etc.).

[0206] A communication session can be used for calls (e.g., audio / or video conferencing, webinars, game streaming, or event streaming). The request can instruct the MOQ transport protocol to be used for media transmission. The request may include a Session Description Protocol (SDP) proposal, which instructs the MOQ transport protocol to be used for media transmission. Figure 7a and Figure 7b In the example shown, an SDP proposal can be carried using a Simple WebRTC Application Protocol (SWAP) message or a Hypertext Transfer Protocol (HTTP) message. In other words, the request sent by UE1 in step 1 can be either a SWAP message containing an SDP proposal or an HTTP message containing an SDP proposal.

[0207] In this disclosure, the terms “media,” “media track,” “track,” “media stream,” or “stream” are used interchangeably.

[0208] At step 2, the MOQ SS sends a request to UE2 to establish a communication session with UE2. This request may indicate that the MOQ transport will be used for media transmission. The request may include an SDP proposal indicating that the MOQ transport protocol will be used for media transmission. In some implementations, the SDP proposal may be carried using a SWAP message. Alternatively, SWAP or HTTP may be used to carry the SDP proposal.

[0209] At step 3, UE2 sends a response to the MOQ SS in response to the request to establish a communication session with UE2. This response may indicate acceptance of the request. The response may include an SDP response (e.g., OK) indicating acceptance of the SDP proposal. In some implementations, a SWAP message or an HTTP message may be used to carry the SDP proposal (e.g., OK). In other words, the response sent by UE2 to the MOQ SS is either a SWAP message including an SDP response or an HTTP message including an SDP response.

[0210] At step 4, the MOQ SS selects the MOQ MS. This selection may be based on: the ability of UE1 to encode or decode media, the ability of UE2 to encode or decode media, the ability of the MOQ MS to encode or decode media, the user preferences of the user of UE1, the user preferences of the user of UE2, the quality of the radio link of UE1, the quality of the radio link of UE2, the quality of the media that UE1 can publish through a first MOQ session with the MOQ MS, and / or the quality of the media that UE2 can publish through a second MOQ session with the MOQ MS.

[0211] The MOQ SS can determine the resources of the MOS MS to be allocated by the MOQ MS for a first MOQ session with the MOQ MS. The MOQ SS can also determine the resources of the MOS MS to be allocated by the MOQ MS for a second MOQ session with the MOQ MS. Resources may include the processing resources and / or memory resources of the MOQ MS.

[0212] The MOQ SS can determine session information for a first MOQ session with the MOQ MS. This session information may include an identifier identifying the first MOQ session with the MOQ MS and / or an identifier identifying UE1. The MOQ SS can also determine session information for a second MOQ session with the MOQ MS. This session information may include an identifier identifying the second MOQ session with the MOQ MS and / or an identifier identifying UE2.

[0213] The MOQ SS can send one or more requests to the MOQ MS to allocate resources for a first MOQ session with the MOQ MS and for a second MOQ session with the MOQ MS. The one or more requests may include indications to be allocated by the MOQ MS for the first MOQ session with the MOQ MS. The one or more requests may include indications to be allocated by the MOQ MS for the second MOQ session with the MOQ MS. The one or more requests may include one or more SDP proposals. In this example implementation, one or more SDP proposals can be carried using either a SWAP message or an HTTP message. In other words, each of the one or more requests may be a SWAP message including an SDP proposal indicating resources to be allocated by the MOQ MS, or an HTTP message including an SDP proposal indicating resources to be allocated by the MOQ MS.

[0214] The MOQ SS can send one or more messages to the MOQ MS, including indications of session information for a first MOQ session with the MOQ MS. The MOQ SS can also send indications of session information for a second MOQ session with the MOQ MS.

[0215] The MOQ SS can send one or more of the following messages to the MOQ MS: an indication of UE1's ability to encode or decode media, an indication of UE2's ability to encode or decode media, an indication of UE1's user preferences, an indication of UE2's user preferences, an indication of the quality of UE1's radio link, an indication of the quality of UE2's radio link, an indication of the quality of media that UE1 can publish through a first MOQ session with the MOQ MS, and an indication of the quality of media that UE2 can publish through a second MOQ session with the MOQ MS.

[0216] At step 5, the MOQ MS sends one or more responses (e.g., acknowledgments) to the MOQ MS in response to one or more requests to allocate resources for a first MOQ session with the MOQ MS and for a second MOQ session with the MOQ MS. The one or more responses include information indicating that the resources for the first MOQ session with the MOQ MS and the resources for the second MOQ session with the MOQ MS have been allocated by the MOQ MS.

[0217] In step 6, the MOQ SS sends a response to UE1 to a request to establish (e.g., establish) a communication session with UE2. This response may indicate acceptance of the request. The response may include the identity of the MOQ MS. The identity of the MOQ MS identifies the MOQ MS. The response may include an SDP response (e.g., OK) indicating acceptance of the SDP proposal. In some implementations, a SWAP message or an HTTP message may be used to carry the SDP proposal. In other words, the response sent by the MOQ SS to UE1 may be a SWAP message including the SDP proposal or an HTTP message including the SDP proposal.

[0218] At step 7, a first QUIC connection is established (e.g., established) between UE1 and MOQ MS.

[0219] At step 8, a second QUIC connection is established (e.g., a second QUIC connection is created) between UE2 and MOQ MS.

[0220] In some implementations, UE1 can trigger the establishment (e.g., establishment) of a QUIC connection with UE1. In some implementations, UE2 can trigger the establishment (e.g., establishment) of a QUIC connection with UE2.

[0221] In some implementations, the MOQ MS can trigger the establishment (e.g., establishment) of the first QUIC connection with UE1. In some implementations, the MOQ MS can trigger the establishment (e.g., establishment) of the QUIC connection with UE2.

[0222] At step 9, a first MOQ session is established (e.g., created) between UE1 and MOQ MS.

[0223] During the establishment (e.g., setup) of the first MOQ session, UE1 may send a message (e.g., MOQ setup message) to the MOQ MS, which includes instructions for UE1 to operate as a publisher and subscriber of media through the first MOQ session.

[0224] UE1 can also receive messages (e.g., MOQ establishment messages) from the MOQ MS, which include instructions for the MOQ MS to operate as a publisher and subscriber of media through the first MOQ session.

[0225] At step 10, a second MOQ session is established (e.g., a second MOQ session is created) between UE2 and MOQ MS.

[0226] During the establishment (e.g., setup) of the second MOQ session, UE2 may send a message (e.g., MOQ setup message) to the MOQ MS, which includes instructions for UE2 to operate as a publisher and subscriber of media through the second MOQ session.

[0227] UE2 can also receive messages (e.g., MOQ establishment messages) from the MOQ MS, which include instructions for the MOQ MS to operate as a publisher and subscriber of media through the second MOQ session.

[0228] It should be understood that, although not described in detail, a third QUIC connection and a third MOQ session can be established (e.g., created) between the AS and the MOQ MS in a manner similar to the first QUIC connection and the first MOQ session, as well as the second QUIC connection and the second MOQ session.

[0229] At step 11, UE1 sends a message (e.g., an announcement message) to the MOQ MS through the first MOQ session. This message may include the namespace of UE1.

[0230] UE1 may send messages (e.g., announcement messages) including its namespace to the MOQ MS only when UE1 is operating as a publisher of media through the first MOQ session. UE1 may not send messages (e.g., announcement messages) including its namespace to the MOQ MS only when it is not operating as a publisher of media through the first MOQ session.

[0231] The namespace of UE1 can be unique. The namespace of UE1 may include references to the identifier of UE1 included in the SWAP message and / or HTTP message sent by UE1 in step 1. In some implementations, the namespace of UE1 includes one or more elements of the original attributes (e.g., o=) in the SDP (according to RFC 4566). In some implementations, the namespace of UE1 includes the international subscriber directory number of UE1's mobile station. In some implementations, the namespace of UE1 includes a unique identifier assigned by the mobile network operator.

[0232] At step 12, UE2 sends a message (e.g., an announcement message) to the MOQ MS through the second MOQ session. This message may include the namespace of UE2.

[0233] UE2 may send a message (e.g., an announcement message) containing an indication of its namespace to the MOQ MS only when UE2 is operating as a publisher of media through the second MOQ session. UE2 may not send a message (e.g., an announcement message) containing an indication of its namespace to the MOQ MS only when UE2 is not operating as a publisher of media through the second MOQ session.

[0234] The namespace of UE2 can be unique. In some implementations, the namespace of UE2 includes references to the identifier of UE2 included in the SWAP message and / or HTTP message sent at step 3. In some implementations, the namespace of UE2 includes one or more elements of the original attributes (e.g., o=) in the SDP (according to RFC 4566). In some implementations, the namespace of UE2 includes the international subscriber directory number of UE2's mobile station. In some implementations, the namespace of UE2 includes a unique identifier assigned by the mobile network operator.

[0235] At step 13, UE1 receives a request from the MOQ MS through the first MOQ session. This request may be a subscription to receive the first MOQ catalog from UE1. UE1 may send a response to this request to the MOQ MS. The response may indicate acceptance of the request (e.g., subscription OK).

[0236] At step 14, UE1 can receive a request from the MOQ MS via a second MOQ session. This request could be a subscription to receive a second MOQ catalog from UE2. UE2 can send a response to the request to the MOQ MS. The response could indicate acceptance of the request (e.g., subscription OK).

[0237] At step 15, UE1 can send a first MOQ directory to the MOQ MS through a first MOQ session. The first MOQ directory may include a media description of media that UE1 can publish through the first MOQ session. The first MOQ directory may include the namespace of the media that UE1 can publish through the first MOQ session. The first MOQ directory may include information indicating the media that UE1 is capable of encoding or decoding. The first MOQ directory may include information indicating the quality of UE1's radio link. The first MOQ directory may include information indicating the quality of the media that UE1 can publish through the first MOQ session. The first MOQ directory may include information indicating the user preferences of UE1's user.

[0238] At step 16, UE2 sends a second MOQ directory to UE1 via the MOQ MS through a second MOQ session. The second MOQ directory may include media descriptions of media that UE2 can publish through the MOQ session. The second MOQ directory may include namespaces of media that UE2 can publish through the second MOQ session. The second MOQ directory may include information indicating that UE2 is capable of encoding or decoding media. The second MOQ directory may include information indicating the quality of UE2's radio link. The first MOQ directory may include information indicating the quality of media that UE2 can publish through the MOQ session. The second MOQ directory may include information indicating user preferences of UE2's user.

[0239] Media that can be published by UE1 through the first MOQ session may include tracks. Media that can be published by UE1 through the first MOQ session may include audio content and / or video content. Media that can be published by UE1 through the first MOQ session may include different versions of the same audio and / or video content. Different versions of the same audio and / or video content may have different qualities and / or may be encoded using different codecs.

[0240] Media that can be published by UE2 through a second MOQ session may include tracks. Media that can be published by UE2 through a second MOQ session may include audio content and / or video content. Media that can be published by UE2 through a second MOQ session may include different versions of the same audio and / or video content. Different versions of the same audio and / or video content may have different qualities and / or may be encoded using different codecs.

[0241] In step 17, MOQ MS creates a combined MOQ directory based on the first MOQ directory and the second MOQ directory.

[0242] The combined MOQ directory can include the namespace of MOQ MS.

[0243] The combined MOQ directory can include the UE1 namespace.

[0244] The combined MOQ directory can include UE2 namespaces.

[0245] The combined MOQ directory can include AS namespaces.

[0246] The combined MOQ catalog may include media descriptions of media that UE1 can publish through the first MOQ session.

[0247] The media description may include at least one of the following: track name, track type, track creation date, track modification date, track size, track frame rate, track codec, or track namespace.

[0248] The combined MOQ catalog may include media descriptions of media published by UE1 through the first MOQ session and processed by the MOQ MS.

[0249] Processing may include transcoding, compositing, encapsulation, combining, and / or rejection.

[0250] The combined MOQ catalog may include media descriptions of media that can be published by UE2 through a second MOQ session.

[0251] The combined MOQ catalog may include media descriptions of media published by UE2 through a second MOQ session and processed by the MOQ MS.

[0252] The combined MOQ catalog may include media descriptions of media that are publishable by AS through a third MOQ session.

[0253] The combined MOQ catalog may include media descriptions of media published by AS through a third MOQ session and processed by MOQ MS.

[0254] The combined MOQ catalog may include media descriptions of media published by UE1 through a first MOQ session and by UE2 through a second MOQ session and processed by the MOQ MS.

[0255] The combined MOQ catalog can include the namespace of media that can be published by UE1 through the first MOQ session.

[0256] The combined MOQ catalog can include the namespace of media published by UE1 through the first MOQ session and processed by the MOQ MS.

[0257] The combined MOQ catalog can include the namespace of media published by UE2 through a second MOQ session.

[0258] The combined MOQ catalog can include the namespace of media published by UE2 through a second MOQ session and processed by MOQ MS.

[0259] The combined MOQ catalog can include namespaces of media that can be published by AS through a third MOQ session.

[0260] The combined MOQ catalog can include namespaces of media published by AS through a third MOQ session and processed by MOQ MS.

[0261] The combined MOQ catalog may include the namespace of media published by UE1 through a first MOQ session and by UE2 through a second MOQ session and processed by the MOQ MS.

[0262] At step 18, UE2 receives a message (e.g., an announcement message) from the MOQ MS via a second MOQ session. This message may include the namespace of the MOQ MS.

[0263] At step 19, UE1 receives a message (e.g., an announcement message) from the MOQ MS through the first MOQ session. This message may include the namespace of the MOQ MS.

[0264] At step 20, UE2 sends a request to the MOQ MS via a second MOQ session. This request may be to subscribe to receive a combined catalog.

[0265] At step 21, UE1 can send a request to the MOQ MS through the first MOQ session. This request could be to subscribe to receive the combined catalog.

[0266] At step 22, the MOQ MS sends the combined MOQ catalog to UE2 through the second MOQ session.

[0267] At step 23, the MOQ MS sends the combined MOQ catalog to UE1 through the first MOQ session.

[0268] At step 24, the MOQ MS sends a request to UE1 through the first MOQ session. This request may be to subscribe to receive media that UE1 can publish through the first MOQ session.

[0269] A request to subscribe to receive media that can be published by UE2 through a second MOQ session can be based on: the ability of UE1 to encode or decode media, the ability of UE2 to encode or decode media, the ability of MOQ MS to encode or decode media, the user preferences of UE1, the user preferences of UE2, the quality of the radio link of UE1, the quality of the radio link of UE2, the quality of the media that can be published by UE1 through a first MOQ session with MOQ MS, and / or the quality of the media that can be published by UE2 through a second MOQ session with MOQ MS.

[0270] At step 25, the MOQ MS sends a request to UE2 via the second MOQ session. This request may be a request to subscribe to receive media that UE2 can publish via the second MOQ session.

[0271] A request to subscribe to receive media that can be published by UE2 through a second MOQ session can be based on: the ability of UE1 to encode or decode media, the ability of UE2 to encode or decode media, the ability of MOQ MS to encode or decode media, the user preferences of UE1, the user preferences of UE2, the quality of the radio link of UE1, the quality of the radio link of UE2, the quality of the media that can be published by UE1 through a first MOQ session with MOQ MS, and / or the quality of the media that can be published by UE2 through a second MOQ session with MOQ MS.

[0272] At step 26, UE1 sends a request to the MOQ MS through the first MOQ session. This request may be a request to subscribe to receive media from the combined catalog. For example, UE1 may send a subscription request to the MOQ MS to receive media that can be published by UE2 through the second MOQ session and processed by the MOQ MS.

[0273] At step 27, UE2 sends a request to the MOQ MS via the second MOQ session. This request could be a request to subscribe to receive media from the combined catalog. For example, UE2 could send a subscription request to the MOQ MS to receive media that can be published by UE1 via the first MOQ session and processed by the MOQ MS.

[0274] At step 28, UE1 sends (e.g., publishes) media to MOQ MS through the first MOQ session.

[0275] At step 29, UE2 sends (e.g., publishes) media to MOQ MS via a second MOQ session.

[0276] At step 30, the MOQ MS processes the media published by UE1 through the first MOQ session. The MOQ MS also processes the media published by UE2 through the second MOQ session.

[0277] At step 31, the MOQ MS sends (i.e., publishes) processing media to UE1 through the first MOQ session. The processing media may include media published by UE2 through the second MOQ session and processed by the MOQ MS.

[0278] At step 32, the MOQ MS sends (i.e., publishes) processing media to UE2 through the second MOQ session. The processing media may include media published by UE1 through the first MOQ session and processed by the MOQ MS.

[0279] It should be understood that this is achievable. Figure 7a and Figure 7b Variations of the process shown. For example, it can be omitted. Figure 7a and Figure 7b Some steps in the process, or Figure 7aand Figure 7b The process shown may include additional steps not shown. Alternatively or additionally, it may be modified. Figure 7a and Figure 7b The sequence of steps in the process shown.

[0280] In a symmetrical scenario, both UE1 and UE2 can operate as publishers and subscribers. The MOQ MS can also operate as a publisher and subscriber. UE1 and UE2 can be endpoints. The MOQ MS is a relay.

[0281] In an asymmetric scenario, UE1 can operate as both a publisher and a subscriber. UE2 can operate as a subscriber. The MOQ MS can operate as both a publisher and a subscriber. UE1 and UE2 can be endpoints. The MOQ MS is a relay.

[0282] In an asymmetric scenario, the external AS can operate as a publisher. UE1 can operate as a subscriber. UE2 can operate as a subscriber. The MOQ MS can operate as both a publisher and a subscriber. The external AS can send the MOQ catalog, which includes media descriptions of media that can be published by the external AS, to the MOQ MS. The external AS, UE1, and UE2 can be endpoints. The MOQ MS is a relay.

[0283] As mentioned above, it should be understood that MOQ SS and MOQ MS can be implemented in several ways.

[0284] In a 5GMS system, Media Application Function (AF) and / or Media Application Server (AS) may include or may be MOQ MS, and Media AS may include or may be MOQ SS.

[0285] In an IMS-based system, the Call Session Control Function (CSCF) and / or IMS Application Server (AS) may include or may be an MOQ SS, and the Media Function (MF) or Multimedia Resource Function (MRF) may include or may be an MOQ MS (such as...). Figure 8 (As shown). If the data channel function is used, the data channel signaling function may involve establishing an MOQ session between UE1 and UE2 and an external AS.

[0286] An external AS can operate as a publisher of media sent via an MOQ session and / or a subscriber of media received via an MOQ session. Media sent by an external application server may initially be generated by another AS (e.g., the external application server is a relay) or by an external AS (e.g., the external AS is an endpoint).

[0287] In an RTC system, the RTC AS can include MOQ MS and MOQ SS (such as...). Figure 9 (As shown).

[0288] Namespace Examples of namespaces for MOQ MS, UE1, UE2, media that can be published by UE1, and media published by UE2 in the combined MOQ catalog are as follows: MOQ MS namespace: myRTCservice / session1 UE1's namespace: myRTCservice / session1 / UE1 UE2's namespace: myRTCservice / session1 / UE2 The namespace for media that can be published by UE1 is: myRTCservice / session1 / UE1 / frontcamera The namespace for media that can be published by UE1 is: myRTCservice / session1 / UE2 / frontcamera MOQ Catalog It should be understood that the first or second MOQ directory can be sent in-band (e.g., as media over an MOQ session) or out-of-band (e.g., via the control plane or via Hypertext Transfer Protocol (HTTP)). Any out-of-band signaling (e.g., in the form of an MOQ directory or SDP) can be performed via the MOQ SS, thus allowing for the appropriate allocation of resources on the MOQ MS.

[0289] Below is an example of a combined MOQ catalog. A new parameter called appGroup can be included in a combined MOQ catalog. appGroup can have an integer value that identifies a group of tracks that are rendered one at a time based on application logic (e.g., user application logic). appGroup represents similar media content that the application can select based on, for example, user preferences or other application logic.

[0290] A combined MOQ catalog can include three video tracks: a video track from UE1 (e.g., UE1 / video_340), a video track from UE2 (UE2 / video_340), and a processed video track (e.g., video_gallery_1080) combining the video tracks from UE1 (e.g., UE1 / video_340) and UE2 (e.g., UE2 / video_340). The processed video track can be application-dependent (e.g., it can be a video of an active speaker, a gallery (all videos in a grid), or a presentation with thumbnails combined into a single video stream). An appGroup can define alternative options, where subscribers can subscribe to either the processed video track (e.g., video_gallery_1080) or a combination of the video tracks from UE1 (e.g., UE1 / video_340) and UE2 (UE2 / video_340).

[0291] { "version": 1, "streamingFormat": 1, "streamingFormatVersion": "0.2", "commonTrackFields": { "namespace": " myRTCservice / session1", "packaging": "cmaf", "renderGroup":1 }, "tracks": [ {"name": "video_gallery_1080", appGroup=1...}, {"name": "audio_aac", appGroup=2, ...}, { “appGroup”=1, {"name": "UE1 / video_340", appGroup=1...}, {"name": "UE2 / video_340", appGroup=1...}, } { “appGroup”=2, {"name": "UE1 / audio_aac", ...}, {"name": "UE2 / audio_aac", ...}, } ] SDP signaling for MOQ As described above, SDP signaling can be sent between UE1 and UE2 and the MOQ SS. SIP signaling including SDP messages can be sent by the MOQ SS to allocate MOQ MS or to assist in establishing MOQ sessions between UE1 and UE2 (directly or via other MOQ trunks). In the case of establishing Multimedia Telephony Service over IMS (MTSI), SIP signaling containing (e.g., including) SDP messages is the primary entry for establishing a telephone session, and such SIP / SDP signaling may also be useful.

[0292] An MOQ-MTSI client can refer to an MTSI client that supports MOQ via WebTransport or QUIC. MOQ-MTSI clients can initiate MOQ sessions using traditional SIP signaling. Below are some examples of SDP signaling used to indicate MOQ (with or without WebTransport) and media capabilities, as well as streaming formats (e.g., Low-Overhead Media Container (LOC) [LOC][WARP] or CMAF). Note that some MOQ configuration parameters are included in these examples because they can be used to allocate appropriate network resources (media functions, policies, and charging control rules, etc.).

[0293] Example 1 Use m=line, for example, m=video <port>MOQ / <streaming format>-webtransport <fmt> fmt is a media format specified in RFC 8866.

[0294] Example 2: Using web-transport settings, for example, m=application 10001 UDP / QUIC web-transport a=setup: <passive active both> a=wtmap:moq <version>SP <role>SP ext= <supported-extensions> The `web-transport` directive indicates that HTTP / 3 is used with webtransport. Establishment is set to passive for the server and active for the client. Relays can use both.

[0295] The attribute `a=moq` is used to negotiate moq-specific parameters. The version is the moq version. Roles can be "sub", "pub", or "pubsub". Supported extensions can be provided as a list. In the proposal response, the provider can list all supported moq options, and the responder will select the options it wants to retain.

[0296] Example 3: Using a generic quic channel with different subprotocols m=application 10001 UDP / QUIC quic-channel a=setup: <passive active both> a=quicmap: <subprotocol>SP <uri>SP v= <version>SP <role>SP ext= <supportedextensions> Establishing a QUIC connection is set to passive for the server receiving the connection (e.g., MOQ MS) and active for the client initiating the connection (e.g., UE). A relay can use "both" to indicate that it supports both active and passive QUIC connection establishment. The URI of the remote server (e.g., a URI identifying the remote server) can also be provided. The attribute a=quicmap is used to define the sub-protocol. For example, the attribute a=quicmap for MOQ and the attribute a=quicmap for HTTP3 are defined as follows: a=quicmap: moq-wt SP <uri>SP <version>SP <role>SP ext= <supported-extensions> <qsids> a=quicmap: http3 SP <uri>SP <version>SP <role>SP ext= <supported-extensions> <qsids> The parameter `qsids` can be used to optionally provide one or more QUIC stream identifiers (IDs) to be used for the subprotocol. The role for HTTP / 3 can be either "server" or "client". The URI can have, for example, the "https" or "moq" scheme, depending on whether WebTransport is used, as defined in Clause 3.1.2 of [MOQ]. Note that "moq-wt" is used in this example for MOQ with WebTransport. Alternatively, "moq" or "native-moq" can be used.

[0297] In some implementations, SDP messages from the UE (e.g., carried via SIP) may include an indication requesting the network to provide MoQ relay for a multi-party communication session. For example, in Figure 7, such an SDP message is sent from the UE to the MOQ SS in step 1. The SDP message may consist of an attribute "3gpp-req-mf" with the following parameters: protocol, protocol version, app-id, and app-info. The protocol is the protocol used for media transmission, such as QUIC-based media. The protocol version is the version of the media protocol, such as version 1.1. The app-id is an identifier for an application that will run on one or more of the UE and MF, such as echoConferencev5. The application information is any additional information related to the application that may also be used to extend the attributes. a=3gpp-req-mf: <protocol>;<protocol version>; <app-id> ; <app-info> SDP messages do not need to include the media description that will be carried over the QUIC connection, but they can. Since subscribers may not have an MOQ catalog when using SDP messages, the media description is primarily used to indicate the device's media capabilities. Protocol control and related semantics can also be used in SDP messages to indicate caching, roles, or other aspects, as shown in the example below, where "inband-protocol=moq" indicates that MOQ will be used for in-band signaling, and "inband=role, cache" indicates that the endpoint's role and cache configuration can both be set using this in-band signaling. a=quicmap: <subprotocol>SP v= <version>SP inband-protocol=moq:role,cache The parameter inband-protocol can be set to "none" to indicate that inband negotiation will not be used and that inband signaling cannot be used to change the protocol establishment indicated in the SDP. That is, any changes to the protocol establishment parameters (e.g., roles, caches) indicated in the SDP message must be renegotiated via SDP.

[0298] In implementation, the IMS AS receives an SDP proposal from the UE to establish (e.g., establish) an MOQ session as described above, and communicates with the DCSF to allocate an MF capable of MOQ transmission as an MOQ trunk for applications and / or calls. The MF initiates an MOQ transmission connection with a remote server, as indicated by the URI in the SDP, or with an alternative URI provided by the DCSF. Once the MOQ session has been successfully established (e.g., established), the MF provides a success response to the IMS AS, and the AS may send OK to the UE. Alternatively, the MF may establish (e.g., establish) the MOQ session after (e.g., establish) the MOQ session between the UE and the MF. The MF also establishes (e.g., establishes) a QUIC connection and MOQ session with the UE initiated by the UE or the MF. The IMS AS may provide the URI of the MF to the UE via an appropriate network function (e.g., NEF, SMF), so that the UE initiates a connection to the MF, but this is not usually done. Alternatively, the IMS AS may provide the connection address of the appropriate MF via an SDP response. In some applications, the MF instance that provides relay functionality may differ from the MF that uses it to establish the pilot data channel, which can be reflected in the SDP response.

[0299] The MF and UE establish (e.g., establish) a QUIC connection and establish (e.g., establish) an MOQ session, for example, through the MOQ control flow defined by the IETF for MOQ transport. If, for example, protocol control is allowed for roles and / or caches, the UE and MF use MOQ control messages to determine the role and cache configuration (e.g., no cache or cache lifetime) for each endpoint (e.g., relay, publisher, subscriber). If the in-band protocol is set to "none," this does not mean that in-band signaling is not used, and the MOQ control channel is still used to establish the MOQ session. However, the role and cache configuration indicated in the SDP are used for the MOQ connection, and the MF and / or UE will reject any MOQ control messages that attempt to change them to different values.

[0300] The IMS AS may also provide provision information to the application provider via the DCSF, so that the IMS AS can modify the MOQ directory accordingly, for example, to ensure that when the media capability is indicated, the encoded media meets the bit rate requirement of the UE or the UE capability. The UE downloads the MOQ directory via the MF. Then, the UE may subscribe to one or more media provided in the MOQ directory. If the MF needs to be pre-warmed for media delivery, the MF may subscribe to or obtain tracks from the MOQ publisher before receiving the subscription from the UE.

[0301] The above SDP messages (e.g., SDP offer and SDP answer) may be exchanged by including the SDP messages in the SWAP connect and SWAP answer messages. Alternatively, a new type of SWAP message that does not rely on SDP, called SWAP ConnectMoq, is defined below.

[0302] The SWAP ConnectMoq message includes (e.g., comprises) one or more of a media_protocol parameter and a matching_criteria parameter.

[0303] The media_protocol parameter is an object that defines the media delivery protocol to be used during the SWAP session and its configuration parameters. The media_protocol parameter consists of a list of type-value pairs, including one or more of the following: protocol: moqt protocol-version: <list of supported moqt versions> streaming-format: <one or more supported streaming formats> media-capabilities: <media description, including media types that can be sent or received and corresponding codec capabilities of the UE, etc. This parameter is an object with one or more entries for each media type.> inband-control: <none or role and / or cache> role: <pub or sub or pubsub> cache: <no cache or cache lifetime> The matching_criteria parameter is as follows: <matching_criteria of an endpoint> The AcceptMoq message is a response to the ConnectMoq message, which includes one or more of the media_protocol parameter and the matching_criteria parameter, and indicates which parameters and values in the received ConnectMoq message are acceptable to the receiver.

[0304] In some implementations, UE1 sends a SWAP ConnectMoq message to the MOQ SS to initiate a communication session with MOQ support instead of SDP, such as... Figure 6 and Figure 7a As shown in step 1. Upon receiving the SWAP ConnectMog message, the MOQ SS then sends a SWAP ConnectMoq message to the other party in the call (e.g., the UE), and if the other party (e.g., the UE) responds to the ConnectMog message, the other party (e.g., the UE) responds to the MOQ SS with an AcceptMoq message, and the MOQ SS sends the AcceptMoq message back to UE1.

[0305] ConnectMoq messages should carry (including) the matching_criteria parameter defined in 3GPP TS 26.113 to identify other parties (e.g., UE).

[0306] In some implementations, the ConnectMoq and AcceptMoq messages are connection and acceptance messages with additional parameters, respectively.

[0307] Figure 10 An example method for performing real-time communication using MOQ is shown. Figure 10 The method shown is executed by the first UE. The method starts at 1000.

[0308] At point 1000, the first UE can send a request to the MOQ SS to establish a communication session with one or more second UEs, the request indicating that the MOQ transport protocol will be used for media transmission.

[0309] At 1002, the first UE can receive a response to the request from the MOQ SS, which indicates acceptance of the request and includes the identifier of the MOQ MS.

[0310] At 1004, after receiving a response to the request, the first UE may send information to the MOQ MS to establish a first QUIC connection between the first UE and the MOQ media server and to establish a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the first UE.

[0311] At point 1006, the first UE may send a first MOQ catalog to the MOQ MS, which includes media descriptions of media that can be published by the first UE through the first MOQ session.

[0312] At 1008, the first UE can receive the namespace of the MOQ MS from the MOQ MS.

[0313] At 1010, the first UE can receive a combined MOQ catalog from the MOQ MS, which includes: a media description of media that can be published by the first UE, a media description of media that can be published by one or more second UEs, or a media description of media that can be published by the AS; and a namespace of the first UE, one or more namespaces of one or more second UEs, or a namespace of the AS.

[0314] Figure 11 Another example method for real-time communication using MOQ is shown. Figure 11 The method shown is executed by MOQ MS. The method begins at 1100.

[0315] At 1100, the MOQ MS can receive from the MOQ SS: an indication of resources to be allocated by the MOQ MS for serving a communication session with one or more second UEs using the MOQ transport protocol for media transmission; and an indication of session information for at least one of the following: a first MOQ session between the MOQ MS and a first UE, one or more second MOQ sessions between the MOQ MS and one or more second UEs, or a third MOQ session between the MOQ media server and the AS.

[0316] At 1102, the MOQ MS allocates resources to serve the first MOQ session, one or more second MOQ sessions, or the third MOQ session.

[0317] At 1104, the MOQ MS receives from the first UE information for establishing a first QUIC connection between the first UE and the MOQ MS and a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the first UE.

[0318] At 1106, the MOQ MS receives from each of one or more second UEs information for establishing a second QUIC connection between the second UE and the MOQ media server and a second MOQ session via the second QUIC connection, wherein the information includes the namespace of the second UE; At 1108, the MOQ MS receives a first MOQ directory from the first UE, the first MOQ directory including media descriptions of media that can be published by the first UE through the first MOQ session.

[0319] At 1110, the MOQ MS receives a second MOQ directory from each of one or more second UEs, the second MOQ directory including a media description of media that can be published by the second UE through a second MOQ session.

[0320] At 1112, the MOQ MS can send a combined MOQ catalog to the first UE, which includes: a media description of media that can be published by the first UE, a media description of media that can be published by one or more second UEs or media that can be published by the AS; and a namespace of media that can be published by the first UE, one or more namespaces of one or more second UEs, or a namespace of the AS.

[0321] Figure 12 Another example of a method for real-time communication using MOQ is shown. Figure 12 The method shown is executed by the first UE. The method begins at 1200.

[0322] At 1200, the first UE can receive a combined MOQ catalog from the MOQ MS, which includes: a media description of media that can be published by the first UE, a media description of media that can be published by one or more second UEs, or a media description of media that can be published by the AS; and a namespace of the first UE, one or more namespaces of one or more second UEs, or a namespace of the AS.

[0323] At 1202, the first UE can send a request to the MOQ MS to subscribe to receive media that can be published by one or more second UEs or ASs.

[0324] At 1204, the first UE can receive media that can be published by one or more second UEs or ASs from the MOQ MS.

[0325] Figure 13 Another example of a method for real-time communication using MOQ is shown. This method is executed by the MOQ MS. The method begins at 1300.

[0326] At 1300, the MOQ MS sends a combined MOQ catalog to the first UE, which includes: a media description of media that can be published by the first UE, a media description of media that can be published by one or more second UEs or media that can be published by the AS; and a namespace of media that can be published by the first UE, one or more namespaces of one or more second UEs, or a namespace of the AS.

[0327] At 1302, the MOQ MS receives a request from the first UE to subscribe to media that can be published by one or more second UEs or ASs.

[0328] At 1304, the MOQ MS sends media to the first UE that can be published by one or more second UEs or ASs.

[0329] While references to "a," "an," or "some" examples may be made throughout this disclosure, this does not necessarily mean that each reference is to the same example, or that a particular feature applies only to a single example. Individual features of different examples may also be combined to provide other examples. Furthermore, when a particular feature, structure, or property is described in conjunction with an example, whether explicitly stated or not, the application of such a feature, structure, or property in conjunction with other examples is within the knowledge of those skilled in the art. It should be understood that although the terms "first," "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another.

[0330] It should be understood that the device may include or be coupled to other units or modules, such as a radio section or radio head, for use or for transmitting and / or receiving. Although the device has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0331] Note that while some examples have been described regarding 5G networks, similar examples can be applied to other networks and communication systems. Therefore, although the example architectures for wireless networks, technologies, and standards described above are presented by way of example, other examples can be applied to any other suitable form of communication system besides those shown and described herein.

[0332] It should also be noted in this document that several variations and modifications may be made to the various examples described herein without departing from the scope of this disclosure.

[0333] As used herein, the phrases "at least one of A or B", "at least one of A and B", and "A and / or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrase "A, B, and / or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0334] As used herein, the term "or" means non-exclusive "or" unless otherwise stated (e.g., "otherwise" or "or in alternatives").

[0335] As used herein, unless explicitly stated otherwise, "responding to A" to perform a step does not indicate that the step is performed immediately after "A" occurs, and may include one or more intermediate steps. Similarly, "based on A" to perform a step or function does not indicate that the step or function is performed solely based on "A," as it may include one or more additional conditions.

[0336] In some examples, at least some of the processes described herein can be performed by means including components for performing at least some of the processes described herein. Components for performing the method steps disclosed herein may include software and / or hardware components. As used herein, the term "component" should be interpreted in the singular form, referring to a single element, or in the plural form, referring to a combination of single elements. Thus, the term "component for [performing A, B, C]" should be interpreted to cover means where only one component for performing A, B, and C is present, or where separate components for performing A, B, and C are present, or where components for performing A, B, and C partially or completely overlap. Furthermore, the terms "component for performing A, component for performing B, component for performing C" should be interpreted to cover means where only one component for performing A, B, and C is present, or where separate components for performing A, B, and C are present, or where components for performing A, B, and C partially or completely overlap.

[0337] The scope of protection sought by the various examples of this disclosure is set forth in the independent claims. Examples and features described in this disclosure that do not fall within the scope of the independent claims, and if any, are to be interpreted as examples useful for understanding the various examples of this disclosure.

[0338] Although examples of the invention have been described above with reference to the accompanying drawings, it is clear that the examples are not limited thereto, but can be modified in several ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate rather than limit the examples. It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. Furthermore, it will be clear to those skilled in the art that the described examples can, but are not required to, be combined with other examples in various ways.

[0339] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0340] Clause 1. A method performed by a first user equipment, comprising: receiving a combined MOQ catalog from a QUIC-based media MOQ server, the combined MOQ catalog including: media descriptions of media that can be published by the first user equipment, media descriptions of media that can be published by one or more second user equipments, or media descriptions of media that can be published by an application server; and a namespace of the first user equipment, one or more namespaces of the one or more second user equipments, or a namespace of the application server; sending a request to the MOQ media server for subscribing to receive media that can be published by the one or more second user equipments or the application server; and receiving the media that can be published by the one or more second user equipments or the application server from the MOQ media server.

[0341] Clause 2. The method according to Clause 1 includes at least one of the following: sending a request to an MOQ signaling server for establishing a communication session with the one or more second user equipments, the request indicating that the MOQ transport protocol will be used for media transmission; receiving a response to the request from the MOQ signaling server, the response indicating acceptance of the request, the response including an identifier of the MOQ media server; after receiving the response to the request, sending information to the MOQ media server for establishing a first QUIC connection between the first user equipment and the MOQ media server and a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the first user equipment; sending a first MOQ directory to the MOQ media server, the first MOQ directory including media descriptions of media that can be published by the first user equipment through the first MOQ session; or receiving the namespace of the MOQ media server from the MOQ media server.

[0342] Clause 3. The method according to Clause 2, wherein the information includes instructions for the first user equipment to operate as a publisher of media through the first MOQ session and a subscriber of media through the first MOQ session.

[0343] Clause 4. The method according to Clause 2 or Clause 3 includes: receiving from the MOQ media server information for establishing a first QUIC connection between the first user equipment and the MOQ server and a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the MOQ media server.

[0344] Clause 5. The method according to Clause 4, wherein the information includes instructions for the MOQ media server to operate as a publisher of media through the first MOQ session and a subscriber of media through the first MOQ session.

[0345] Clause 6. The method according to any one of Clauses 1 to 5, wherein the combined MOQ catalog includes the namespace of the MOQ media server.

[0346] Clause 7. The method according to any one of Clauses 1 to 6, wherein the media description of the media published by the first user equipment includes at least one of the following: a media description of media that can be published by the first user equipment through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the first user equipment through the first MOQ session but not processed by the MOQ media server; or the media description of the media that can be published by the second user equipment includes at least one of the following: a media description of media that the one or more second user equipments can publish through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the one or more second user equipments through the first MOQ session but not processed by the MOQ media server. The media description of media that can be published through the first MOQ session but is not processed by the MOQ media server; or the media description of media that can be published by the application server includes at least one of the following: a media description of media that can be published by the application server through a third MOQ session and processed by the MOQ media server; or a media description of media that can be published by the application server through the third MOQ session but is not processed by the MOQ media server; or the combined directory includes a media description of media that can be published by the first user equipment through the first MOQ session and by the one or more second user equipments through the one or more MOQ sessions and processed by the MOQ media server.

[0347] Clause 8. The method according to any one of Clauses 2 to 7 comprises: sending to the MOQ signaling server at least one of the following: an indication that the first user equipment is capable of encoding and decoding media, an indication of the quality of media that the first user equipment can publish, an indication of the quality of the radio link of the first user equipment, or an indication of user preferences of the first user equipment.

[0348] Clause 9. The method according to any one of Clauses 2 to 8 comprises: sending the first MOQ directory to the MOQ signaling server, the first MOQ directory including a media description of media that the first user equipment can publish through the first MOQ session and at least one of the following: an indication that the first user equipment is capable of encoding and decoding media, an indication of the quality of media that the first user equipment can publish, the quality of the radio link of the first user equipment, or the user preference of the first user equipment.

[0349] Clause 10. The method according to any one of Clauses 2 to 9, wherein sending the request for establishing the communication session with the one or more second user equipments comprises: sending a session description protocol proposal indicating that the MOQ transport protocol will be used for the transmission of media, and wherein receiving the response to the request comprises: receiving a session description protocol response indicating acceptance of the session description protocol proposal.

[0350] Clause 11. The method according to Clause 10, wherein the Session Description Protocol (STP) proposal and the STP response are carried using at least one of Session Initiation Protocol, Simple WebRTC Application Protocol, or Hypertext Transfer Protocol.

[0351] Clause 12. A method performed by a QUIC-based media MOQ server, the method comprising: sending a combined MOQ catalog to a first user equipment, the combined MOQ catalog including: media descriptions of media that can be published by the first user equipment, media descriptions of media that can be published by one or more second user equipments, or media descriptions of media that can be published by an application server; and namespaces of media published by the first user equipment, one or more namespaces of the one or more second user equipments, or the namespace of the application server; receiving from the first user equipment a request to subscribe to media that can be published by the one or more second user equipments or the application server; and sending the media that can be published by the one or more second user equipments or the application server to the first user equipment.

[0352] Clause 13. The method according to Clause 12 comprises at least one of the following: receiving from an MOQ signaling server: an indication of resources to be allocated by the MOQ media server for serving a communication session with one or more second user equipments using the MOQ transport protocol for media transmission; and an indication of session information for at least one of: a first MOQ session between the MOQ media server and the first user equipment, one or more second MOQ sessions between the MOQ media server and the one or more second user equipments, or a third MOQ session between the MOQ media server and an application server; allocating resources of the MOQ media server to serve the first MOQ session, the one or more second MOQ sessions, or the third MOQ session; and receiving from the first user equipment a first QUIC connection to establish between the first user equipment and the MOQ media server. And information about the first MOQ session connected via the first QUIC, wherein the information includes the namespace of the first user equipment; receiving information from each of one or more second user equipments for establishing a second QUIC connection between the second user equipment and the MOQ media server and a second MOQ session connected via the second QUIC, wherein the information includes the namespace of the second user equipment; receiving a first MOQ directory from the first user equipment, the first MOQ directory including media descriptions of media that the first user equipment can publish via the first MOQ session; or receiving a second MOQ directory from each of the one or more second user equipments, the second MOQ directory including media descriptions of media that the one or more second user equipments can publish via the second MOQ session.

[0353] Clause 14. The method according to Clause 13, wherein the information for establishing the first QUIC connection between the first user equipment and the MOQ media server and the first MOQ session via the first QUIC connection includes: an instruction for the first user equipment to operate as a publisher and subscriber of media via the first MOQ session; and wherein the information for establishing the second QUIC connection between the second user equipment and the MOQ media server and the second QUIC session via the second QUIC connection includes: an instruction for the second user equipment to operate as a publisher and subscriber of media via the second MOQ session.

[0354] Clause 15. The method according to Clause 13 or Clause 14 comprises: sending to the first user equipment information for establishing a first QUIC connection between the first user equipment and the MOQ media server and a first MOQ session through the first QUIC connection, wherein the information includes the namespace of the MOQ media server; and sending to each of the one or more second user equipments information for establishing a second QUIC connection between the second user equipment and the MOQ media server and a second MOQ session through the second QUIC connection, wherein the information includes the namespace of the MOQ media server.

[0355] Clause 16. The method according to Clause 15, wherein the information for establishing the first QUIC connection between the first user equipment and the MOQ media server and the first MOQ session via the first QUIC connection includes: an instruction for the MOQ media server to operate as a publisher and subscriber of media via the first MOQ session; and wherein the information for establishing the second QUIC connection between the second user equipment and the MOQ media server and the second MOQ session via the second QUIC connection includes: an instruction for the MOQ media server to operate as a publisher and subscriber of media via the second MOQ session.

[0356] Clause 17. The method according to any one of Clauses 12 to 16, wherein the combined MOQ catalog includes the namespace of the MOQ media server.

[0357] Clause 18. The method according to any one of Clauses 12 to 17, wherein the media description of media that can be published by the first user equipment includes at least one of the following: a media description of media that can be published by the first user equipment through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the first user equipment through the first MOQ session but not processed by the MOQ media server; or the media description of media that can be published by the second user equipment includes at least one of the following: a media description of media that can be published by the one or more second user equipments through the first MOQ session and processed by the MOQ media server; or a media description of media that can be published by the one or more second user equipments through the first MOQ session but not processed by the MOQ media server. The media description of media that can be published through the first MOQ session but is not processed by the MOQ media server; or the media description of media that can be published by the application server includes at least one of the following: a media description of media that can be published by the application server through the third MOQ session and processed by the MOQ media server; or a media description of media that can be published by the application server through the third MOQ session but is not processed by the MOQ media server; or the combined directory includes a media description of media that can be published by the first user equipment through the first MOQ session and by the one or more second user equipments through the one or more MOQ sessions and processed by the MOQ media server.

[0358] Clause 19. The method according to any one of Clauses 12 to 19 comprises: receiving from one or more second user devices a request to subscribe to receive media that can be published by the first user device or the application server; and sending the media that can be published by the first user device or the application server to the one or more second user devices.

[0359] Clause 20. The method according to any one of Clauses 12 to 19, wherein the MOQ media server includes at least one of the following: application functions of a cellular system; application servers of a real-time communication system; media functions of an Internet Protocol Multimedia Subsystem; or multimedia resource functions of an Internet Protocol Multimedia Subsystem.

[0360] Clause 21. A first user equipment comprising at least one processor and at least one memory storing instructions, said instructions, when executed by said at least one processor, causing the first user equipment to perform a method according to any one of Clauses 1 to 11.

[0361] Clause 22. A computer program comprising computer-executable code, which, when executed on at least one processor of a first user equipment, causes the first user equipment to perform the method according to any one of Clauses 1 to 11.

[0362] Clause 23. A computer-readable medium comprising instructions that, when executed by at least one processor of a first user equipment, cause the first user equipment to perform the method according to any one of Clauses 1 to 11.

[0363] Clause 24. A QUIC-based MOQ media server, comprising at least one processor and at least one memory storing instructions, said instructions, when executed by said at least one processor, causing the MOQ media server to perform the method according to any one of Clauses 12 to 20.

[0364] Clause 25. A computer program comprising computer-executable code, which, when run on at least one processor of a QUIC-based MOQ media server, causes the MOQ media server to perform the method according to any one of Clauses 12 to 20.

[0365] Clause 26. A computer-readable medium comprising instructions that, when executed by at least one processor of a QUIC-based MOQ media server, cause the MOQ media server to perform the method according to any one of Clauses 12 to 20.< / version> < / subprotocol> < / app-id> < / protocol> < / qsids> < / supported-extensions> < / role> < / version> < / uri> < / qsids> < / supported-extensions> < / role> < / version> < / uri> < / supportedextensions> < / role> < / version> < / uri> < / subprotocol> < / passive> < / role> < / version> < / passive> < / fmt> < / port>

Claims

1. A method performed by a first user equipment, comprising: Receive a combined MOQ catalog from a QUIC-based media MOQ server, the combined MOQ catalog comprising: Media descriptions of media that can be published by the first user equipment, media descriptions of media that can be published by one or more second user equipments, or media descriptions of media that can be published by the application server; and The namespace of the first user device, one or more namespaces of the one or more second user devices, or the namespace of the application server; Send a request to the MOQ media server to subscribe to receive media that can be published by the one or more second user devices or the application server; and Receive the media that can be published by the one or more second user devices or the application server from the MOQ media server.

2. The method according to claim 1, comprising at least one of the following: Send a request to the MOQ signaling server to establish a communication session with the one or more second user equipments, the request indicating that the MOQ transport protocol will be used for media transmission; Receive a response to the request from the MOQ signaling server, the response indicating acceptance of the request, the response including the identifier of the MOQ media server; After receiving the response to the request, information for establishing a first QUIC connection between the first user equipment and the MOQ media server and a first MOQ session through the first QUIC connection is sent to the MOQ media server, wherein the information includes the namespace of the first user equipment. Send a first MOQ directory to the MOQ media server, the first MOQ directory including media descriptions of media that the first user equipment can publish through the first MOQ session; or Receive the namespace of the MOQ media server from the MOQ media server.

3. The method of claim 2, wherein the information includes an indication that the first user equipment is operating as a publisher of media through the first MOQ session and a subscriber of media through the first MOQ session.

4. The method according to claim 2 or claim 3, comprising: The system receives information from the MOQ media server for establishing a first QUIC connection between the first user equipment and the MOQ server, and a first MOQ session via the first QUIC connection, wherein the information includes the namespace of the MOQ media server.

5. The method of claim 4, wherein the information includes instructions for the MOQ media server to operate as a publisher of media through the first MOQ session and a subscriber of media through the first MOQ session.

6. The method according to any one of claims 1 to 3, wherein the combined MOQ directory includes the namespace of the MOQ media server.

7. The method according to any one of claims 1 to 3, wherein The media description of the media published by the first user equipment includes at least one of the following: Media description of media that can be published by the first user equipment through the first MOQ session and processed by the MOQ media server; or Media descriptions of media that the first user equipment can publish through the first MOQ session but are not processed by the MOQ media server; or The media description of the media that the second user equipment can publish includes at least one of the following: Media descriptions of media that the one or more second user equipments can publish through the first MOQ session and that are processed by the MOQ media server; or Media descriptions of media that can be published by the one or more second user equipments through the first MOQ session but are not processed by the MOQ media server; or The media description of the media that the application server can publish includes at least one of the following: Media descriptions of media that can be published by the application server through a third MOQ session and processed by the MOQ media server; or Media descriptions of media that the application server can publish through the third MOQ session but are not processed by the MOQ media server; or The combined catalog includes media descriptions of media that can be published by the first user equipment through the first MOQ session and by the one or more second user equipments through the one or more MOQ sessions and processed by the MOQ media server.

8. The method according to claim 2 or 3, comprising: Send at least one of the following to the MOQ signaling server: an indication that the first user equipment is capable of encoding and decoding media, an indication of the quality of media that the first user equipment can publish, an indication of the quality of the radio link of the first user equipment, or an indication of the user preferences of the first user equipment.

9. The method according to claim 2 or 3, comprising: The first MOQ directory is sent to the MOQ signaling server. The first MOQ directory includes a media description of media that the first user equipment can publish through the first MOQ session and at least one of the following: an indication that the first user equipment can encode and decode media, an indication of the quality of media that the first user equipment can publish, the quality of the radio link of the first user equipment, or the user preference of the first user equipment.

10. The method of claim 2 or 3, wherein sending the request for establishing the communication session with the one or more second user equipments comprises: Sending a session description protocol proposal instructing the MOQ transport protocol to be used for media transmission, and wherein receiving a response to the request includes receiving a session description protocol response indicating acceptance of the session description protocol proposal.

Images