Patent Description:
Embodiments of this disclosure are directed to media processing and streaming methods and systems, more particularly to discovery of media service entry for uplink and downlink streaming in <NUM>th generation (<NUM>) networks.

The current <NUM> media streaming architecture defined in <NPL>) defines the general architecture for uplink and downlink media streaming.

<NPL>) defines the concept of uplink streaming where the content is streamed from the device to an external Service Provider, but does not define a service entry for uplink streaming. In addition, the service entry for downlink streaming is very limited.

<CIT> discloses a media distribution system and method wherein a media streaming network includes a media ingest network portion configured to provide low latency uploading of media fragments of a segmented live media stream using HTTP chunked transfer encoding (CTE). <CIT> discloses a method for selecting a network slice instantiation in a communication network for the transmission of uplink data from a user terminal. The method includes, subsequent to receipt of an uplink packet by a communication module of the user terminal, verification of a correspondence between this uplink packet and at least one rule designating a network slice instantiation able to transmit the uplink packet in the communication network and, when the uplink packet corresponds to a rule designating a network slice instantiation, transmission of the uplink packet to an entity for access to the user plane of the designated network slice instantiation.

One aspect of the invention is defined as a method, according to independent claim <NUM>, of managing capabilities of a <NUM> media streaming (5GMS) network using at least one processor includes obtaining a streaming access object corresponding to 5GMS media content; obtaining a media service entry based on the streaming access object, wherein the media service entry includes a protocol identifier corresponding to the media service entry, and a service entry uniform resource locator (URL) corresponding to the media service entry; and performing at least one of uplink streaming or downlink streaming of the 5GMS media content based on the media service entry, wherein the media service entry is consistent with a 5GMS M5 interface regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content.

According to another aspect of the invention, it is defined as a device, according to independent claim <NUM>, for managing capabilities of a 5GMS network includes at least one memory configured to store program code; and at least one processor configured to read the program code and operate as instructed by the program code, the program code including: first obtaining code configured to cause the at least one processor to obtain a streaming access object corresponding to 5GMS media content; second obtaining code configured to cause the at least one processor to obtain a media service entry based on the streaming access object, wherein the media service entry includes a protocol identifier corresponding to the media service entry, and a service entry uniform resource locator (URL) corresponding to the media service entry; and performing code configured to cause the at least one processor to perform at least one of uplink streaming or downlink streaming of the 5GMS media content based on the media service entry, wherein the media service entry is consistent with a 5GMS M5 interface regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content.

According to another aspect of the invention, it is defined as a non-transitory computer-readable medium, according to independent claim <NUM>, which stores instructions including one or more instructions that, when executed by one or more processors of a device for managing capabilities of a 5GMS network, cause the one or more processors to: obtain a streaming access object corresponding to 5GMS media content; obtain a media service entry based on the streaming access object, wherein the media service entry includes a protocol identifier corresponding to the media service entry, and a service entry uniform resource locator (URL) corresponding to the media service entry; and perform at least one of uplink streaming or downlink streaming of the 5GMS media content based on the media service entry, wherein the media service entry is consistent with a 5GMS M5 interface regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content.

<FIG> is a diagram of an environment <NUM> in which methods, apparatuses, and systems described herein may be implemented, according to embodiments. As shown in <FIG>, the environment <NUM> may include a user device <NUM>, a platform <NUM>, and a network <NUM>. Devices of the environment <NUM> may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

The user device <NUM> includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with platform <NUM>. For example, the user device <NUM> may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device. In some implementations, the user device <NUM> may receive information from and/or transmit information to the platform <NUM>.

The platform <NUM> includes one or more devices as described elsewhere herein. In some implementations, the platform <NUM> may include a cloud server or a group of cloud servers. In some implementations, the platform <NUM> may be designed to be modular such that software components may be swapped in or out depending on a particular need. As such, the platform <NUM> may be easily and/or quickly reconfigured for different uses.

In some implementations, as shown, the platform <NUM> may be hosted in a cloud computing environment <NUM>. Notably, while implementations described herein describe the platform <NUM> as being hosted in the cloud computing environment <NUM>, in some implementations, the platform <NUM> may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

The cloud computing environment <NUM> includes an environment that hosts the platform <NUM>. The cloud computing environment <NUM> may provide computation, software, data access, storage, etc. services that do not require end-user (e.g. the user device <NUM>) knowledge of a physical location and configuration of system(s) and/or device(s) that hosts the platform <NUM>. As shown, the cloud computing environment <NUM> may include a group of computing resources <NUM> (referred to collectively as "computing resources <NUM>" and individually as "computing resource <NUM>").

The computing resource <NUM> includes one or more personal computers, workstation computers, server devices, or other types of computation and/or communication devices. In some implementations, the computing resource <NUM> may host the platform <NUM>. The cloud resources may include compute instances executing in the computing resource <NUM>, storage devices provided in the computing resource <NUM>, data transfer devices provided by the computing resource <NUM>, etc. In some implementations, the computing resource <NUM> may communicate with other computing resources <NUM> via wired connections, wireless connections, or a combination of wired and wireless connections.

As further shown in <FIG>, the computing resource <NUM> includes a group of cloud resources, such as one or more applications ("APPs") <NUM>-<NUM>, one or more virtual machines ("VMs") <NUM>-<NUM>, virtualized storage ("VSs") <NUM>-<NUM>, one or more hypervisors ("HYPs") <NUM>-<NUM>, or the like.

The application <NUM>-<NUM> includes one or more software applications that may be provided to or accessed by the user device <NUM> and/or the platform <NUM>. The application <NUM>-<NUM> may eliminate a need to install and execute the software applications on the user device <NUM>. For example, the application <NUM>-<NUM> may include software associated with the platform <NUM> and/or any other software capable of being provided via the cloud computing environment <NUM>. In some implementations, one application <NUM>-<NUM> may send/receive information to/from one or more other applications <NUM>-<NUM>, via the virtual machine <NUM>-<NUM>.

The virtual machine <NUM>-<NUM> includes a software implementation of a machine (e.g. a computer) that executes programs like a physical machine. The virtual machine <NUM>-<NUM> may be either a system virtual machine or a process virtual machine, depending upon use and degree of correspondence to any real machine by the virtual machine <NUM>-<NUM>. A system virtual machine may provide a complete system platform that supports execution of a complete operating system ("OS"). A process virtual machine may execute a single program, and may support a single process. In some implementations, the virtual machine <NUM>-<NUM> may execute on behalf of a user (e.g. the user device <NUM>), and may manage infrastructure of the cloud computing environment <NUM>, such as data management, synchronization, or long-duration data transfers.

The virtualized storage <NUM>-<NUM> includes one or more storage systems and/or one or more devices that use virtualization techniques within the storage systems or devices of the computing resource <NUM>. In some implementations, within the context of a storage system, types of virtualizations may include block virtualization and file virtualization. Block virtualization may refer to abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to physical storage or heterogeneous structure. The separation may permit administrators of the storage system flexibility in how the administrators manage storage for end users. File virtualization may eliminate dependencies between data accessed at a file level and a location where files are physically stored. This may enable optimization of storage use, server consolidation, and/or performance of non-disruptive file migrations.

The hypervisor <NUM>-<NUM> may provide hardware virtualization techniques that allow multiple operating systems (e.g. "guest operating systems") to execute concurrently on a host computer, such as the computing resource <NUM>. The hypervisor <NUM>-<NUM> may present a virtual operating platform to the guest operating systems, and may manage the execution of the guest operating systems. Multiple instances of a variety of operating systems may share virtualized hardware resources.

The network <NUM> includes one or more wired and/or wireless networks. For example, the network <NUM> may include a cellular network (e.g. a fifth generation (<NUM>) network, a long-term evolution (LTE) network, a third generation (<NUM>) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g. the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.

Additionally, or alternatively, a set of devices (e.g. one or more devices) of the environment <NUM> may perform one or more functions described as being performed by another set of devices of the environment <NUM>.

<FIG> is a block diagram of example components of one or more devices of <FIG>. The device <NUM> may correspond to the user device <NUM> and/or the platform <NUM>. As shown in <FIG>, the device <NUM> may include a bus <NUM>, a processor <NUM>, a memory <NUM>, a storage component <NUM>, an input component <NUM>, an output component <NUM>, and a communication interface <NUM>.

The bus <NUM> includes a component that permits communication among the components of the device <NUM>. The processor <NUM> is implemented in hardware, firmware, or a combination of hardware and software. The processor <NUM> is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, the processor <NUM> includes one or more processors capable of being programmed to perform a function. The memory <NUM> includes a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g. a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by the processor <NUM>.

The storage component <NUM> stores information and/or software related to the operation and use of the device <NUM>. For example, the storage component <NUM> may include a hard disk (e.g. a magnetic disk, an optical disk, a magneto-optic disk, and/or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive.

The input component <NUM> includes a component that permits the device <NUM> to receive information, such as via user input (e.g. a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone). Additionally, or alternatively, the input component <NUM> may include a sensor for sensing information (e.g. a global positioning system (GPS) component, an accelerometer, a gyroscope, and/or an actuator). The output component <NUM> includes a component that provides output information from the device <NUM> (e.g. a display, a speaker, and/or one or more light-emitting diodes (LEDs)).

The communication interface <NUM> includes a transceiver-like component (e.g., a transceiver and/or a separate receiver and transmitter) that enables the device <NUM> to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface <NUM> may permit the device <NUM> to receive information from another device and/or provide information to another device. For example, the communication interface <NUM> may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.

The device <NUM> may perform one or more processes described herein. The device <NUM> may perform these processes in response to the processor <NUM> executing software instructions stored by a non-transitory computer-readable medium, such as the memory <NUM> and/or the storage component <NUM>. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

Software instructions may be read into the memory <NUM> and/or the storage component <NUM> from another computer-readable medium or from another device via the communication interface <NUM>. When executed, software instructions stored in the memory <NUM> and/or the storage component <NUM> may cause the processor <NUM> to perform one or more processes described herein.

In practice, the device <NUM> may include additional components, fewer components, different components, or differently arranged components than those shown in <FIG>. Additionally, or alternatively, a set of components (e.g. one or more components) of the device <NUM> may perform one or more functions described as being performed by another set of components of the device <NUM>.

A <NUM> media streaming (5GMS) system may be an assembly of application functions, application servers, and interfaces from the <NUM> media streaming architecture that support either downlink media streaming services or uplink media streaming services, or both. A 5GMS Application Provider may include a party that interacts with functions of the 5GMS system and supplies a 5GMS Aware Application that interacts with functions of the 5GMS system. The 5GMS Aware Application may refer to an application in the user equipment (UE), provided by the 5GMS Application Provider, that contains the service logic of the 5GMS application service, and interacts with other 5GMS Client and Network functions via the interfaces and application programming interfaces (APIs) defined in the 5GMS architecture. A 5GMS Client may refer to a UE function that is either a 5GMS downlink (5GMSd) Client or a 5GMS uplink (5GMSu) Client, or both.

The 5GMSd Client may refer to a UE function that includes at least a <NUM> media streaming player and a media session handler for downlink streaming and that may be accessed through well-defined interfaces/APIs. The 5GMSu Client may refer to an originator of a 5GMSu service that may be accessed through well-defined interfaces/APIs. A 5GMSu media streamer may refer to a UE function that enables uplink delivery of streaming media content to an Application Server (AS) function of the 5GMS Application Provider, and which interacts with both the 5GMSu Aware Application for media capture and subsequent streaming, and the Media Session Handler for media session control.

A dynamic policy may refer to a dynamic policy and charging control (PCC) rule for an uplink or downlink application flow during a media session. An egest session may refer to an uplink media streaming session from the 5GMS AS towards the 5GMSu Application Provider. An ingest session may refer to a session to upload the media content to a 5GMSd AS. A policy template may refer to a collection of (semi-static) Policy or Control Function (PCF)/Network Exposure Function (NEF) API parameters which are specific to the 5GMS Application Provider and also the resulting PCC rule. A policy template ID may identify the desired policy template, which is used by the 5GMSd Application Function (AF) to select the appropriate PCF/NEF API towards the <NUM> system so that the PCF can compile the desired PCC rule. The Media Player Entry may refer to a document or a pointer to a document that defines a media presentation (e.g., a media presentation description (MPD) for DASH or a uniform resource locator (URL) to a video clip file). A Media Streamer Entry may refer to a pointer (e.g., in the form of a URL) that defines an entry point of an uplink media streaming session. A presentation entry may refer to a document or a pointer to a document that defines an application presentation, such as an HTML5 document.

A Provisioning Session may refer to a data structure supplied at an interface (M1d) by a 5GMSd Application provider that configures the 5GMSd features relevant to a set of 5GMSd Aware Applications. A 5GMSd Media Player may refer to a UE function that enables playback and rendering of a media presentation based on a media play entry and exposing some basic controls such as play, pause, seek, stop, to the 5GMSd Aware Application. Server Access Information may refer to a set of parameters and addresses (including 5GMSd AF and 5GMSd AS addresses) which are needed to activate the reception of a streaming session. A Service and Content Discovery may refer to functionality and procedures provided by a 5GMSd Application Provider to a 5GMS Aware Application that enables the end user to discover the available streaming service and content offerings and select a specific service or content item for access. A Service Announcement may refer to procedures conducted between the 5GMS Aware Application and the 5GMS Application Provider such that the 5GMS Aware Application is able to obtain 5GMS Service Access Information, either directly or in the form of a reference to that information.

A third party player may refer to a part of an application that uses APIs to exercise selected 5GMSd functions to play back media content. A third party uplink streamer may refer to a part of an application that uses APIs to exercise selected 5GMSu functions to capture and stream media content.

A <NUM> media-streaming architecture for downlink and uplink streaming is shown in <FIG> and <FIG>.

<FIG> is a diagram of a media architecture <NUM> for media uplink streaming. A <NUM> media streaming uplink (5GMSu) Application Provider <NUM> may use 5GMSu for uplink streaming services. 5GMSu Application provider <NUM> may provide a 5GMSu Aware Application <NUM> on the UE <NUM> to make use of 5GMSu Client <NUM> and network functions using interfaces and APIs defined in 5GMSu. 5GMSu Application Server (AS) may be an AS dedicated to <NUM> Media Uplink Streaming. 5GMSu Client <NUM> may be a UE <NUM> internal function dedicated to <NUM> Media Uplink Streaming.

5GMSu Application Function (AF) <NUM> and 5GMSu AS <NUM> may be Data Network (DN) <NUM> functions. Functions in trusted DNs may be trusted by the operator's network. Therefore, AFs in trusted DNs may directly communicate with all <NUM> Core functions. Functions in external DNs may only communicate with <NUM> Core functions via the Network Exposure Function (NEF) <NUM> using link <NUM>.

The media architecture <NUM> may connect UE <NUM> internal functions and related network functions for <NUM> Media Uplink Streaming. Accordingly, media architecture <NUM> may include a number of functions. For example, 5GMSu Client <NUM> on UE <NUM> may be an originator of 5GMSu service that may be accessed through interfaces/APIs. 5GMSu Client <NUM> may include two sub-functions, media session handler <NUM> and media streamer <NUM>. Media session handler <NUM> may communicate with the 5GMSu AF <NUM> in order to establish, control and support the delivery of a media session. The Media Session Handler <NUM> may expose APIs that can be used by the 5GMSu Aware Application <NUM>. Media Streamer <NUM> may communicate with 5GMSu AS <NUM> in order to stream the media content and provide a service to the 5GMSu Aware Application <NUM> for media capturing and streaming, and the Media Session Handler <NUM> for media session control. 5GMSu Aware Application <NUM> may control 5GMSu Client <NUM> by implementing external application or content service provider specific logic and enabling the establishment of a media session. 5GMSu AS <NUM> may host <NUM> media functions. 5GMSu Application Provide <NUM> may be an external application or content specific media functionality, e.g., media storage, consumption, transcoding and redistribution that uses 5GMSu to stream media from 5GMSu Aware Application <NUM>. 5GMSu AF <NUM> may provide various control functions to the Media Session Handler <NUM> on the UE <NUM> and/or to 5GMSu Application Provider <NUM>. 5GMSu AF <NUM> may relay or initiate a request for different Policy or Charging Function (PCF) <NUM> treatment or interact with other network functions.

Media architecture <NUM> may include a number of different interface. For example, link <NUM> may relate to M1u, which may be a 5GMSu Provisioning API exposed by 5GMSu AF <NUM> to provision usage of media architecture <NUM> and to obtain feedback. Link <NUM> may relate to M2u, which may be a 5GMSu Publish API exposed by 5GMSu AS <NUM> and used when 5GMSu AS <NUM> in trusted DN, such as DN <NUM>, is selected to receive content for streaming service. Link <NUM> may relate to M3u, which may be an internal API used to exchange information for content hosting on 5GMSu AS <NUM> within a trusted DN such as DN <NUM>. Link <NUM> may relate to M4u, which may be a Media Uplink Streaming API exposed by 5GMSu AS <NUM> to Media Streamer <NUM> to stream media content. Link <NUM> may relate to M5u, which may be a Media Session Handling API exposed by 5GMSu AF <NUM> to Media Session Handler for media session handling, control and assistance that also include appropriate security mechanisms e.g. authorization and authentication. Link <NUM> may relate to M6u, which may be a UE <NUM> Media Session Handling API exposed by Media Session Handler <NUM> to 5GMSu Aware Application <NUM> to make use of 5GMSu functions. Link <NUM> may relate to M7u, which may be a UE Media Streamer API exposed by Media Streamer <NUM> to 5GMSu Aware Application <NUM> and Media Session Handler <NUM> to make use of Media Streamer <NUM>. Link <NUM> may relate to M8u, , which may be an Application API which is used for information exchange between 5GMSu Aware Application <NUM> and 5GMSu Application Provider <NUM>, for example to provide service access information to the 5GMSu Aware Application <NUM>.

<FIG> is a diagram of a media architecture <NUM> for media downlink streaming. A <NUM> media streaming downlink (5GMSd) Application Provider <NUM> may use 5GMSd for downlink streaming services. 5GMSd Application provider <NUM> may provide a 5GMSd Aware Application <NUM> on the UE <NUM> to make use of 5GMSd Client <NUM> and network functions using interfaces and APIs defined in 5GMSd. 5GMSd Application Server (AS) may be an AS dedicated to <NUM> Media Downlink Streaming. 5GMSd Client <NUM> may be a UE <NUM> internal function dedicated to <NUM> Media Downlink Streaming.

5GMSd Application Function (AF) <NUM> and 5GMSd AS <NUM> may be Data Network (DN) <NUM> functions. Functions in trusted DNs may be trusted by the operator's network. Therefore, AFs in trusted DNs may directly communicate with all <NUM> Core functions. Functions in external DNs may only communicate with <NUM> Core functions via the Network Exposure Function (NEF) <NUM> using link <NUM>.

The media architecture <NUM> may connect UE <NUM> internal functions and related network functions for <NUM> Media Downlink Streaming. Accordingly, media architecture <NUM> may include a number of functions. For example, 5GMSd Client <NUM> on UE <NUM> may be a receiver of 5GMSd service that may be accessed through interfaces/APIs. 5GMSd Client <NUM> may include two sub-functions, media session handler <NUM> and media Player <NUM>. Media session handler <NUM> may communicate with the 5GMSd AF <NUM> in order to establish, control and support the delivery of a media session. The Media Session Handler <NUM> may expose APIs that can be used by the 5GMSd Aware Application <NUM>. Media Player <NUM> may communicate with 5GMSd AS <NUM> in order to stream the media content and provide a service to the 5GMSd Aware Application <NUM> for media playback, and the Media Session Handler <NUM> for media session control. 5GMSd Aware Application <NUM> may control 5GMSd Client <NUM> by implementing external application or content service provider specific logic and enabling the establishment of a media session. 5GMSd AS <NUM> may host <NUM> media functions. 5GMSd Application Provide <NUM> may be an external application or content specific media functionality, e.g., media creation, encoding, and formatting that uses 5GMSd to stream media to 5GMSd Aware Application <NUM>. 5GMSd AF <NUM> may provide various control functions to the Media Session Handler <NUM> on the UE <NUM> and/or to 5GMSd Application Provider <NUM>. 5GMSd AF <NUM> may relay or initiate a request for different Policy or Charging Function (PCF) <NUM> treatment or interact with other network functions.

Media architecture <NUM> may include a number of different interfaces. For example, link <NUM> may relate to M1d, which may be a 5GMSd Provisioning API exposed by 5GMSd AF <NUM> to provision usage of media architecture <NUM> and to obtain feedback. Link <NUM> may relate to M2d, which may be a 5GMSd Ingest API exposed by 5GMSd AS <NUM> and used when 5GMSd AS <NUM> in trusted DN, such as DN <NUM>, is selected to receive content for streaming service. Link <NUM> may relate to M3d, which may be an internal API used to exchange information for content hosting on 5GMSd AS <NUM> within a trusted DN such as DN <NUM>. Link <NUM> may relate to M4d, which may be a Media Downlink Streaming API exposed by 5GMSd AS <NUM> to Media Player <NUM> to stream media content. Link <NUM> may relate to M5d, which may be a Media Session Handling API exposed by 5GMSd AF <NUM> to Media Session Handler for media session handling, control and assistance that also include appropriate security mechanisms e.g. authorization and authentication. Link <NUM> may relate to M6d, which may be a UE <NUM> Media Session Handling API exposed by Media Session Handler <NUM> to 5GMSd Aware Application <NUM> to make use of 5GMSd functions. Link <NUM> may relate to M7d, which may be a UE Media Player API exposed by Media Player <NUM> to 5GMSd Aware Application <NUM> and Media Session Handler <NUM> to make use of Media Player <NUM>. Link <NUM> may relate to M8d, which may be an Application API which is used for information exchange between 5GMSd Aware Application <NUM> and 5GMSd Application Provider <NUM>, for example to provide service access information to the 5GMSd Aware Application <NUM>.

As discussed above, while 3GPP TS26. <NUM> defines the general uplink process, it does not define a service entry for uplink streaming. In addition, the service entry for downlink streaming is very limited.

For downlink streaming, TS26. <NUM> defines a StreamingAccess object as part of ServiceAccessInfromation resource. As is shown in the following table, the StreamingAccess object includes a URL string that points to a URL for downloading a media or a manifest that describe the media presentation.

In the case of uplink streaming, it is not clear what uplink ingest protocols are supported by TS26. Furthermore, it is not clear how the MSH would retrieve the entry point for uplink streaming (e.g. a URL for posting the media segments). Finally, only one URL is allowed. Therefore, even for download streaming, only one entry point is allowed, and alternative protocols are not possible to be offered.

Accordingly, embodiments may extend the Streaming Access object in at least one of the following ways:.

An example of the above design is shown in Table <NUM>.

In Table <NUM>, the underlined rows show the design according to embodiments. The StreamingAccess object may be an array of objects, each of which has two items: mediaServiceName which uniquely identifies the used protocol (for example Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) Media Presentation Description (MPD), HTTP Live Streaming (HLS) m3u8, DASH-Industry Forum (IF) ingest), and mediaEntry which defines the URL for accessing that service.

Because the StreamingAccess object may be an array, multiple objects may represent an equivalent service, i.e. a UE can use any of them to access the same service.

Example <NUM> may relate to downlink streaming with DASH and HLS using common media application format (CMAF) segments. In this example, two StreamingAccess objects are defined:.

In this example, two manifests are provided each of which is identified with a URN. Additionally, each manifest has a link to be downloaded. Both manifests point to the same CMAF content. Because the MPD link is listed first, it may be the preferred service to be used by the UE.

Example <NUM> may relate to uplink streaming with DASH-IF ingest protocol profile <NUM> and profile <NUM>:.

In this example, two profiles of the same protocol are provided for upload along with a separate URL for each profile. Because profile <NUM> is listed first, it may be the preferred profile to be used by UE.

Accordingly, embodiments may provide a method for defining media service entry for uplink and downlink streaming wherein both the protocol identifier as well as the service entry URL are signaled, wherein multiple protocols and/or service entry points can be described in the media service entry, wherein the client can use any of them to access the service using different protocols and/or different entry points, wherein the order of service entry points define the preference order provided by the Application Service Provider and/or by the <NUM> network, wherein a single data structure is used cross 5GMS M5 interface for indicating the media service entry for both uplink and downlink.

<FIG> is a flowchart of example process <NUM> of managing capabilities of a media streaming network, for example a 5GMS network. In some implementations, one or more process blocks of <FIG> may be performed by any of the elements discussed above with respect to <FIG>.

As shown in <FIG>, process <NUM> may include obtaining a streaming access object corresponding to media content, for example 5GMS media content (block <NUM>).

As further shown in <FIG>, process <NUM> may include obtaining a media service entry based on the streaming access object, wherein the media service entry includes a protocol identifier corresponding to the media service entry, and a service entry uniform resource locator (URL) corresponding to the media service entry (block <NUM>).

As further shown in <FIG>, process <NUM> may include performing at least one of uplink streaming or downlink streaming of media content, for example the 5GMS media content, based on the media service entry (block <NUM>). In embodiments, the media service entry may be consistent with a 5GMS M5 interface regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content.

In embodiments, the protocol identifier may include a uniform resource name (URN) identifying the media service entry.

In embodiments, the URN may identify the media service entry as one from among a Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) Media Presentation Description (MPD) protocol, an HTTP Live Streaming (HLS) m3u8 protocol, and a DASH-Industry Forum (IF) ingest protocol.

In embodiments, the streaming access object may be included in an array of streaming access objects.

In embodiments, each streaming access object of the array of streaming access objects may identify a corresponding media service entry from among a plurality of media service entries.

In embodiments, a priority of the plurality of media service entries may be determined based on an order of the streaming access objects within the array of streaming access objects.

In embodiments, the streaming access object may correspond to a 5th generation media streaming (SGMS) M5 interface.

Further, the proposed methods may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program that is stored in a non-transitory computer-readable medium to perform one or more of the proposed methods.

The techniques described above can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.

Embodiments of the present disclosure may be used separately or combined in any order. Further, each of the embodiments (and methods thereof) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program that is stored in a non-transitory computer-readable medium.

Modifications and variations are only possible within the scope of the appended claims.

Claim 1:
A method of managing capabilities of a <NUM> media streaming, 5GMS, network using at least one processor, comprising:
obtaining (<NUM>) a streaming access object corresponding to 5GMS media content;
obtaining (<NUM>) a media service entry based on the streaming access object, wherein the media service entry includes a protocol identifier corresponding to the media service entry, and a service entry uniform resource locator, URL, corresponding to the media service entry;
performing (<NUM>) at least one of uplink streaming or downlink streaming of the 5GMS media content based on the media service entry, wherein the media service entry is consistent with a 5GMS M5 interface regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content, and
characterized in that
the streaming access object is included in an array of streaming access objects such that each streaming access object of the array of streaming access objects identifies a corresponding media service entry from among a plurality of media service entries.