Method, device and storage medium for managing capabilities of 5GMS network

Abstract

A method, system and device for managing the capabilities of a 5G media streaming (5GMS) network, the method comprising 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, regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content, the media service entry is consistent with the 5GMS M5 interface.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 187,811 filed in the U.S. Patent and Trademark Office on May 12, 2021, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments of the present disclosure relate to media processing, streaming methods and systems, and more particularly, to discovering media service portals for uplink and downlink streaming in a 5G network. Background Art

[0004] The current 5G media streaming architecture defined in 3GPP TS26.501 (3GPP TS26.501, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G Media Streaming (5GMS); General description and architecture (Release 16), V16.3.1) defines the general architecture of uplink media streaming and downlink media streaming.

[0005] The 3rd Generation Partnership Project (3GPP) TS26.512 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G Media Streaming (5GMS); Protocols (Release 16), V1.1.0) defines the concept of uplink streaming of content from a 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. Summary of the invention

[0006] According to one or more embodiments, a method for managing the capabilities of a 5G 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, based on the media service entry, performing at least one of uplink streaming or downlink streaming of the 5GMS media content, wherein, regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content, the media service entry is consistent with the 5GMS M5 interface.

[0007] According to one or more embodiments, a device for managing the 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 according to the instructions of the program code, the program code including: a first acquisition code configured to enable at least one processor to acquire a streaming access object corresponding to 5GMS media content; a second acquisition code configured to enable at least one processor to acquire 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 an execution code configured to enable at least one processor to execute at least one of uplink streaming or downlink streaming of 5GMS media content based on the media service entry, wherein, regardless of whether the media service entry is used for uplink streaming or downlink streaming of 5GMS media content, the media service entry is consistent with the 5GMS M5 interface.

[0008] According to one or more embodiments, a non-transitory computer-readable medium storing instructions includes one or more instructions, which, when executed by one or more processors of a device for managing the capabilities of a 5G media streaming (5GMS) network, causes 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, regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content, the media service entry is consistent with the 5GMS M5 interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Further features, properties and various advantages of the disclosed subject matter will become more apparent from the following detailed description and the accompanying drawings, in which:

[0010] Figure 1 is a schematic diagram of an environment in which the described methods, apparatuses, and systems may be implemented according to an embodiment.

[0011] Figure 2 yes Figure 1 A block diagram of example components of one or more devices in.

[0012] Figure 3 is a block diagram of a media architecture for media uplink streaming according to an embodiment.

[0013] Figure 4 is a block diagram of a media architecture 400 for media downlink streaming, according to an embodiment.

[0014] Figure 5 is a flow chart of an example process for content preparation for a media streaming network, according to an embodiment. DETAILED DESCRIPTION

[0015] Figure 1 1 is a schematic diagram of an environment 100 in which the methods, apparatuses, and systems described herein may be implemented according to an embodiment. Figure 1 As shown, environment 100 may include user device 110, platform 120, and network 130. The devices of environment 100 may be interconnected in a wired connection, a wireless connection, or a combination of wired and wireless connections.

[0016] The user device 110 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information associated with the platform 120. For example, the user device 110 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 wireless phone, 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 110 can receive information from the platform 120 and / or send information to the platform 120.

[0017] The platform 120 includes one or more devices as described elsewhere herein. In some implementations, the platform 120 may include a cloud server or a group of cloud servers. In some embodiments, the platform 120 may be designed to be modular so that software components can be swapped in or out according to specific needs. Thus, the platform 120 may be easily and / or quickly reconfigured for different uses.

[0018] In some implementations, as shown, the platform 120 can be hosted in a cloud computing environment 122. It is worth noting that although the implementations described herein describe the platform 120 as being hosted in a cloud computing environment 122, in some implementations, the platform 120 may not be based on a cloud computing environment (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0019] Cloud computing environment 122 includes an environment that hosts platform 120. Cloud computing environment 122 may provide computing, software, data access, storage, and the like services without requiring end users (e.g., user devices 110) to be aware of the actual location and configuration of devices and / or systems used to host platform 120. As shown, cloud computing environment 122 may include a set of computing resources 124 (collectively, “computing resources 124” and individually, “computing resources 124”).

[0020] The computing resources 124 include one or more personal computers, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, the computing resources 124 can host the platform 120. Cloud resources may include computing entities executed in the computing resources 124, storage devices provided in the computing resources 124, data transmission devices provided by the computing resources 124, etc. In some implementations, the computing resources 124 can communicate with other computing resources 124 in a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection.

[0021] Further Figure 1 As shown, the computing resources 124 include a set of cloud resources, such as one or more applications ("APP") 124-1, one or more virtual machines ("VM") 124-2, virtualized storage ("VS") 124-3, one or more hypervisors ("HYP") 124-4, etc.

[0022] The applications 124-1 include one or more software applications that can be provided to or accessed by the user device 110 and / or the platform 120. The applications 124-1 can eliminate the need to install and execute software applications on the user device 110. For example, the applications 124-1 can include software associated with the platform 120 and / or any other software that can be provided via the cloud computing environment 122. In some implementations, one application 124-1 can send information to / receive information from one or more other applications 124-1 via the virtual machine 124-2.

[0023] Virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Depending on the degree of correspondence and purpose of virtual machine 124-2 to any real machine, virtual machine 124-2 can be a system virtual machine or a process virtual machine. A system virtual machine can provide a complete system platform that supports execution of a complete operating system ("OS"). A process virtual machine can execute a single program and can support a single process. In some implementations, virtual machine 124-2 can execute on behalf of a user (e.g., user device 110) and can manage the infrastructure of cloud computing environment 122, such as data management, synchronization, or long-term data transfer.

[0024] Virtualized storage 124-3 includes one or more storage systems and / or one or more devices that use virtualization technology within the storage system or device of computing resource 124. In some implementations, in the context of a storage system, the types of virtualization may include block virtualization and file virtualization. Block virtualization may refer to extracting (or separating) logical storage from physical storage so that the storage system can be accessed without considering physical storage or heterogeneous structures. This separation may allow administrators of storage systems to have flexibility in how the administrator manages storage for end users. File virtualization may eliminate the dependency between data accessed at the file level and the location of the physical storage file. This may optimize the performance of storage usage, server consolidation, and / or non-disruptive file migration.

[0025] Hypervisor 124-4 can provide hardware virtualization technology that enables multiple operating systems (e.g., "guest operating systems") to execute concurrently on a host computer (e.g., computing resource 124). Hypervisor 124-4 can present a virtual operating platform to the guest operating systems and can manage the execution of the guest operating systems. Multiple instances of various operating systems can share virtualized hardware resources.

[0026] The network 130 includes one or more wired and / or wireless networks. For example, the network 130 may include a cellular network (e.g., a fifth generation (5G) network, a long term evolution (LTE) network, a third generation (3G) 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., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-based network, etc., and / or a combination of these or other types of networks.

[0027] Figure 1 The number and arrangement of devices and networks shown are provided as an example. Figure 1There may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than those shown. Figure 1 Two or more of the devices shown may be implemented in a single device, or Figure 1 The single device shown may also be implemented as multiple distributed devices. Additionally, or alternatively, one or more devices of one set of devices (eg, one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.

[0028] Figure 2 yes Figure 1 Device 200 may correspond to user device 110 and / or platform 120. Figure 2 As shown, device 200 may include a bus 210 , a processor 220 , a memory 230 , a storage component 240 , an input component 250 , an output component 260 , and a communication interface 270 .

[0029] The bus 210 includes components that allow communication between components of the device 200. The processor 220 is implemented in hardware, firmware, or a combination of hardware and software. The processor 220 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 220 includes one or more processors that can be programmed to perform functions. The memory 230 includes a random access memory (RAM), a read-only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, and / or optical memory) that store information and / or instructions used by the processor 220.

[0030] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, storage component 240 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a film cartridge, a magnetic tape, and / or other types of non-transitory computer-readable media, and corresponding drives.

[0031] Input components 250 include components that allow device 200 to receive information, for example, via input from a user (e.g., a touch screen display, a keyboard, keys, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, input components 250 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 260 include components that provide output information from device 200 (e.g., a display, a speaker, and / or one or more light emitting diodes (LEDs)).

[0032] The communication interface 270 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable the device 200 to communicate with other devices, for example, via a wired connection, a wireless connection, or a combination of a wired and wireless connection. The communication interface 270 can allow the device 200 to receive information from another device and / or provide information to another device. For example, the communication interface 270 can 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, etc.

[0033] Device 200 may perform one or more of the processes described herein. Device 200 may perform these processes in response to processor 220 executing software instructions stored by a non-transitory computer-readable medium such as memory 230 and / or storage component 240. Computer-readable media is defined herein as a non-transitory storage device. A storage device includes storage space in a single physical storage device or storage space distributed in multiple physical storage devices.

[0034] The software instructions may be read into the memory 230 and / or storage component 240 from another computer-readable medium or from another device via the communication interface 270. When executed, the software instructions stored in the memory 230 and / or storage component 240 may cause the processor 220 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used or combined with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0035] Figure 2 The number and arrangement of components shown are provided as an example. Figure 2 Compared to the components shown in , device 200 may have additional components, fewer components, different components, or differently distributed components. Additionally, or alternatively, a set of components (e.g., one or more components) of device 200 can perform one or more functions described as being performed by another set of components of device 200.

[0036] The 5G Media Stream (5GMS) system may be an assembly of application functions, application servers, and interfaces from a 5G Media Stream architecture that supports downlink media stream services or uplink media stream services or both downlink media stream services and uplink media stream services. A 5GMS application provider may include a party that interacts with the functions of a 5GMS system and provides a 5GMS-aware application that interacts with the functions of a 5GMS system. A 5GMS-aware application may refer to an application in a user equipment (UE) provided by a 5GMS application provider that contains the service logic of a 5GMS application service and interacts with other 5GMS clients and network functions via interfaces and application programming interfaces (APIs) defined in the 5GMS architecture. A 5GMS client may refer to a UE function that is a 5GMS downlink (5GMSd) client, or a 5GMS uplink (5GMSuplink, 5GMSu) client, or both a 5GMSd client and a 5GMSu client.

[0037] 5GMSd Client may refer to a UE functionality that includes at least a 5G Media Streamer and a Media Session Processor for downlink streaming and that can be accessed through a well-defined interface / API. 5GMSu Client may refer to the initiator of a 5GMSu service that can be accessed through a well-defined interface / API. 5GMSu Media Streamer may refer to a UE functionality that enables uplink delivery of streaming media content to the Application Server (AS) function of a 5GMS Application Provider and interacts with both the 5GMSu Aware Application for media capture and subsequent streaming and the Media Session Processor for media session control.

[0038] Dynamic policy may refer to dynamic policy and charging control (PCC) rules for uplink or downlink application flows during a media session. An egest session may refer to an uplink media flow session from a 5GMS AS to a 5G MSu application provider. An ingest session may refer to a session that uploads media content to a 5GMSd AS. A policy template may refer to a set of (semi-static) policy or control function (PCF) / network exposure function (NEF) API parameters that are specific to a 5GMS application provider and the generated PCC rules. 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 for the 5G system so that the PCF can compile the desired PCC rules. A 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 segment file). A media streamer entry may refer to a pointer (e.g., in the form of a URL) that defines an entry point for 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.

[0039] A Provisioning Session may refer to a data structure provided at an interface (M1d) by a 5GMSd application provider that configures 5GMSd features associated with a set of 5GMSd-aware applications. A 5GMSd Media Player may refer to a UE function that enables playback and rendering of media presentations based on a media playback portal, and exposes some basic controls such as play, pause, search, and stop to 5GMSd-aware applications. Server Access Information may refer to a set of parameters and addresses (including 5GMSd AF and 5GMSd AS addresses) required to activate the reception of a streaming session. Service and Content Discovery may refer to functions and processes provided by a 5GMSd application provider to a 5GMS-aware application that enables an end user to discover available streaming services and content offerings, and select specific services or content items for access. Service Announcement may refer to a process conducted between a 5GMS-aware application and a 5GMS application provider that enables a 5GMS-aware application to obtain 5GMS service access information directly or in the form of a reference to the information.

[0040] A third-party player may refer to the portion of an application that uses the API to perform selected 5GMSd functions to play back media content. A third-party uplink streamer may refer to the portion of an application that uses the API to perform selected 5GMSd functions to capture and stream media content.

[0041] Figure 3 and 4 The 5G media streaming architecture for downlink and uplink streaming is shown.

[0042] Figure 3 Schematic diagram of a media architecture 300 for media uplink streaming. A 5G Media Streaming Uplink (5GMSu) application provider 301 may use 5GMSu for uplink streaming services. The 5GMSu application provider 301 may provide a 5GMSu-aware application 302 on a UE 303 to use a 5GMSu client 304 and network functions using interfaces and APIs defined in 5GMSu. A 5GMSu Application Server (AS) may be an AS dedicated to 5G media uplink streaming. A 5GMSu client 304 may be an internal function of a UE 303 dedicated to 5G media uplink streaming.

[0043] 5GMSu Application Function (AF) 306 and 5GMSu AS 305 may be Data Network (DN) 307 functions. Functions in a trusted DN may be trusted by the operator's network. Therefore, the AF in a trusted DN may communicate directly with all 5G Core functions. Functions in an external DN may communicate with the 5G Core functions via Network Exposure Function (NEF) 308 using only link 320.

[0044] The media architecture 300 may connect UE 303 internal functions and related network functions for 5G media uplink streaming. Accordingly, the media architecture 300 may include multiple functions. For example, the 5GMSu client 304 on the UE 303 may be the initiator of a 5GMSu service, which may be accessed through an interface / API. The 5GMSu client 304 may include two sub-functions, a media session processor 309 and a media streamer 310. The media session processor 309 may communicate with the 5GMSu AF 306 to establish, control and support the delivery of media sessions. The media session processor 309 may open an API that may be used by the 5GMSu-aware application 302. The media streamer 310 may communicate with the 5GMSu AS 305 to stream media content and provide services to the 5GMSu-aware application 302 for media capture and streaming and the media session processor 309 for media session control. The 5GMSu aware application 302 may control the 5GMSu client 304 by implementing external application or content service provider specific logic and enabling establishment of media sessions. The 5GMSu AS 305 may host the 5G media functions. The 5GMSu application provider 301 may be an external application or content specific media function such as media storage, consumption, transcoding and redistribution of media streamed from the 5GMSu aware application 302 using 5GMSu. The 5GMSu AF 306 may provide various control functions to the media session processor 309 and / or the 5GMSu application provider 301 on the UE 303. The 5GMSu AF 306 may relay or initiate requests for different Policy or Charging Function (PCF) 311 processing or interaction with other network functions.

[0045] The media architecture 300 may include a number of different interfaces. For example, link 321 may be associated with M1u, which may be a 5GMSu provisioning API that is opened by the 5GMSu AF 306 to provision the use of the media architecture 300 and obtain feedback. Link 322 may be associated with M2u, which may be a 5GMSu publishing API that is opened by the 5GMSu AS 305 and used when the 5GMSu AS 305 in a trusted DN such as DN 307 is selected to receive content for streaming services. Link 323 may be associated with M3u, which may be an internal API used to exchange information about content hosted on the 5GMSu AS 305 within a trusted DN such as DN 307. Link 324 may be associated with M4u, which may be a media uplink streaming API opened by the 5GMSu AS 305 to the media streamer 310 for streaming media content. Link 325 may be associated with M5u, which may be a media session handling API exposed by the 5GMSu AF 306 to the media session processor for media session handling, control and assistance, which may also include appropriate security mechanisms such as authorization and authentication. Link 326 may be associated with M6u, which may be a UE 303 media session handling API exposed by the media session processor 309 to the 5GMSu aware application 302 to use the 5GMSu functionality. Link 327 may be associated with M7u, which may be a UE media streamer API exposed by the media streamer 310 to the 5GMSu aware application 302 and the media session processor 309 to use the media streamer 310. Link 328 may be associated with M8u, which may be an application API used for information exchange between the 5GMSu-aware application 302 and the 5GMSu application provider 301 , such as providing service access information to the 5GMSu-aware application 302 .

[0046] Figure 4 4 is a schematic diagram of a media architecture 400 for media downlink streaming. A 5G media stream downlink (5GMSd) application provider 401 may use 5GMSd for downlink streaming services. The 5GMSd application provider 401 may provide a 5GMSd-aware application 402 on a UE 403 to use 5GMSd client and network functions using interfaces and APIs defined in 5GMSd. A 5GMSd application server (AS) may be an AS dedicated to 5G media downlink streaming. A 5GMSd client 404 may be a UE 403 internal function dedicated to 5G media downlink streaming.

[0047] 5GMSd application function (AF) 406 and 5GMSd AS 405 can be data network (DN) 407 functions. Functions in a trusted DN can be trusted by the operator's network. Therefore, the AF in the trusted DN can communicate directly with all 5G core functions. Functions in external DNs can communicate with 5G core functions via network exposure function (NEF) 408 using only link 420.

[0048] The media architecture 400 can connect the internal functions of the UE 403 and the related network functions for 5G media downlink streaming. Accordingly, the media architecture 400 may include multiple functions. For example, the 5GMSd client 404 on the UE 403 may be a receiver of 5GMSd services that can be accessed through an interface / API. The 5GMSd client 404 may include two sub-functions, a media session processor 409 and a media player 410. The media session processor 409 may communicate with the 5GMSd AF 406 to establish, control and support the delivery of media sessions. The media session processor 409 may open an API that can be used by the 5GMSd aware application 402. The media player 410 may communicate with the 5GMSd AS 405 to stream media content and provide services to the 5GMSd aware application 402 for media playback and the media session processor 409 for media session control. The 5GMSd aware application 402 may control the UE 403 by implementing external application or content service provider specific logic and enabling the establishment of a media session. The 5GMSd AS 405 may host the 5G media functions. The 5GMSd application provider 401 may be an external application or content specific media function, such as media creation, encoding, and formatting for streaming media to the 5GMSd aware application 402 using 5GMSd. The 5GMSd AF 406 may provide various control functions to the media session processor 409 on the UE 403 and / or the 5GMSd application provider 401. The 5GMSd AF 406 may relay or initiate requests for different policy or charging functions (PCFs) 411 processing or interaction with other network functions.

[0049] The media architecture 400 may include a number of different interfaces. For example, link 421 may be associated with M1d, which may be a 5GMSd-supplied API that is exposed by the 5GMSd AF 406 to supply the use of the media architecture 400 and obtain feedback. Link 422 may be associated with M2d, which may be a 5GMSd ingestion API that is exposed by the 5GMSd AS 405 and used when the 5GMSd AS 405 in a trusted DN such as DN 407 is selected to receive content for streaming services. Link 423 may be associated with M3d, which may be an internal API used to exchange information about content hosted on the 5GMSd AS 405 within a trusted DN such as DN 407. Link 424 may be associated with M4d, which may be a media downlink streaming API that is opened by the 5GMSd AS 405 to the media player 410 for streaming media content. Link 425 may be associated with M5d, which may be a media session handling API that is opened by the 5GMSd AF 406 to the media session processor for media session handling, control and assistance, which also includes appropriate security mechanisms such as authorization and authentication. Link 426 may be associated with M6d, which may be a UE 403 media session handling API that is opened by the media session processor 409 to the 5GMSd aware application 402 to use the 5GMSd functionality. Link 427 may be associated with M7d, which may be a UE media player API that is opened by the media player 410 to the 5GMSd aware application 402 and the media session processor 409 to use the media player 410. Link 428 may be related to M8d, which may be an application API used for information exchange between the 5GMSd aware application 402 and the 5GMSd application provider 401, such as providing service access information to the 5GMSd aware application 402.

[0050] As described above, although 3GPP TS26.512 defines a general uplink procedure, it does not define a service entry for uplink streaming. In addition, the service entry for downlink streaming is very limited.

[0051] For downlink streaming, TS26.512 defines a StreamingAccess object as part of the ServiceAccessInformation resource. As shown in the following table, the StreamingAccess object includes a URL string that points to a URL for downloading media or a manifest describing a media presentation.

[0052] Table 1: Service entries for downlink streaming in TS 26.512

[0053]

[0054]

[0055] In the case of uplink streaming, it is not clear which uplink ingest protocols are supported by TS26.512. Furthermore, it is not clear how MSH will retrieve the entry point (e.g., the URL for publishing media segments) for uplink streaming. Ultimately, only one URL is allowed. Therefore, even for download streaming, only one entry point is allowed, and it is not possible to provide alternative protocols.

[0056] Thus, embodiments may extend the streaming access object in at least one of the following ways:

[0057] 1. Add a uniform resource name (URN) to each uniform resource locator (URL) to signal the protocol.

[0058] 2. Allow multiple stream access objects, by, for example, making the stream access an array of objects, where each element defines an equivalent service entry point.

[0059] 3. The order of StreamingAccess objects can show the priority of the service entries, for example, a service entry that appears before another service entry in the array is the preferred service between the two.

[0060] An example of the above design is shown in Table 2.

[0061] Table 2: Extended service entry

[0062]

[0063]

[0064] In Table 2, the underlined content shows the design of an embodiment. The StreamingAccess object can be an array of objects, each object having two items: mediaServiceName, which uniquely identifies the protocol used (e.g., Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) Media Presentation Description (MPD), HTTP Live Streaming (HLS) m3u8, and DASH-Industry Forum (IF) ingest), and mediaEntry, which defines the URL used to access the service.

[0065] Because the StreamingAccess object can be an array, multiple objects can represent equivalent services, ie, the UE can use any of them to access the same service.

[0066] Example 1

[0067] Example 1 may involve downlink streaming with DASH and HLS using common media application format (CMAF) fragments. In this example, two StreamingAccess objects are defined:

[0068] {[urn.iso.mpeg.dash.2012,http: / / companyA.com / manifest.mpd],

[0069] [urn.apple.hls.2015,http: / / companyA.com / manifest.m3u]}

[0070] In this example, two manifests are provided, each identified by a URN. In addition, each manifest has a link available for download. Both manifests point to the same CMAF content. Since the MPD link is listed first, it may be the preferred service used by the UE.

[0071] Example 2

[0072] Example 2 may involve uplink streaming with DASH-IF ingest protocol profile 1 and profile 2:

[0073] {[urn:3gpp:5gms:content-protocol:dash-if-ingest:p1,http: / / companyA.com / profile1 / ],

[0074] [urn:3gpp:5gms:content-protocol:dash-if-ingest:p2,http: / / companyA.com / profile2 / ]}

[0075] In this example, two configuration files of the same protocol are provided for upload with separate URLs for each configuration file. Since Configuration File 1 is listed first, it may be the preferred configuration file to be used by the UE.

[0076] Accordingly, in an embodiment, a method for defining a media service entry for uplink and downlink streaming may be provided, wherein a protocol identifier and a service entry URL are signaled, wherein the media service entry may describe multiple protocols and / or service entry points, wherein a client may utilize any of them to access services using different protocols and / or different entry points, wherein the order of the service entry points defines a preferred order provided by an application service provider and / or by a 5G network, and wherein a single data architecture is used in the 5GMS M5 interface to indicate the media service entry for both uplink and downlink.

[0077] Figure 5 is a flow chart of an example process 500 for managing the capabilities of a media streaming network, such as a 5G MS network. In some implementations, Figure 5 One or more processing blocks may be formed by the above Figures 1 to 4 Any one of the elements discussed may be performed.

[0078] like Figure 5 As shown, process 500 may include obtaining a streaming access object corresponding to media content (e.g., 5GMS media content) (block 502).

[0079] like Figure 5 As further shown, process 500 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 504).

[0080] like Figure 5 As further shown, process 500 may include performing at least one of uplink streaming or downlink streaming of media content (e.g., 5GMS media content) based on the media service entry (block 506). In an embodiment, regardless of whether the media service entry is for uplink streaming or downlink streaming of 5GMS media content, the media service entry is consistent with the 5GMS M5 interface.

[0081] In an embodiment, the protocol identifier may include a uniform resource name (URN) identifying the media service portal.

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

[0083] In an embodiment, the streaming access object may be contained in an array of streaming access objects.

[0084] In an embodiment, each streaming access object in the array of streaming access objects may identify a corresponding media service portal from among a plurality of media service portals.

[0085] In an embodiment, the priorities of the multiple media service entries may be determined based on the order of the streaming access objects in the streaming access object array.

[0086] In an embodiment, the streaming access object may correspond to the 5GMS M5 interface.

[0087] although Figure 5 5 shows example blocks of process 500. However, in some implementations, process 500 may include Figure 5 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those shown. Additionally, or alternatively, two or more blocks of process 500 may be performed in parallel.

[0088] In addition, the proposed method can be implemented by a processing circuit (eg, one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-transitory computer-readable medium to perform one or more of the proposed methods.

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

[0090] The embodiments of the present application can be used separately or in combination in any order. In addition, each embodiment (and method thereof) can be implemented by a processing circuit (e.g., one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-transitory computer-readable medium.

[0091] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0092] As used herein, the term component is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software.

[0093] Even though combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.

[0094] Unless explicitly described, any element, behavior or instruction used herein should not be interpreted as critical or essential. In addition, as used herein, the articles "a" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the term "set" is intended to include one or more items (such as related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is intended, the term "one" or similar wording is used. In addition, as used herein, the terms "has", "have", "having", etc. are intended to be open terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part on".

Claims

1. A method for managing the capabilities of a 5G Media Streaming (5GMS) network using at least one processor, characterized in that The method comprises: Get the streaming access object corresponding to the 5GMS media content; Acquiring 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, the streaming access object being included in an array of streaming access objects, each of the streaming access objects in the array of streaming access objects identifying a corresponding media service entry from a plurality of media service entries; and At least one of uplink streaming or downlink streaming of the 5GMS media content is performed based on the media service entry, wherein, regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content, the media service entry is consistent with the 5GMS M5 interface.

2. The method according to claim 1, characterized in that: The protocol identifier includes a uniform resource name (URN) identifying the media service portal.

3. The method according to claim 2, characterized in that The URN identifies the media service entry as one of 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.

4. The method according to claim 1, characterized in that: The priorities of the multiple media service entries are determined based on the order of the streaming access objects in the streaming access object array.

5. The method according to any one of claims 1 to 3, characterized in that The streaming access object corresponds to the 5GMS M5 interface.

6. A device for managing the capabilities of a 5G media stream (5GMS) network, characterized in that The device comprises: at least one memory configured to store program code; and At least one processor is configured to read the program code and perform the following operations: Get the streaming access object corresponding to the 5GMS media content; Acquiring 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, the streaming access object being included in an array of streaming access objects, each of the streaming access objects in the array of streaming access objects identifying a corresponding media service entry from a plurality of media service entries; and At least one of uplink streaming or downlink streaming of the 5GMS media content is performed based on the media service entry, wherein, regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content, the media service entry is consistent with the 5GMS M5 interface.

7. The device according to claim 6, characterized in that The protocol identifier includes a uniform resource name (URN) identifying the media service portal.

8. The device according to claim 7, characterized in that The URN identifies the media service entry as one of 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.

9. The device according to claim 6, characterized in that The priorities of the multiple media service entries are determined based on the order of the streaming access objects in the streaming access object array.

10. The device according to any one of claims 6 to 8, characterized in that The streaming access object corresponds to the 5GMSM5 interface.

11. A non-transitory computer-readable medium storing instructions, characterized in that: The instructions include: one or more instructions, which, when executed by one or more processors of a device for managing capabilities of a 5G media streaming (5GMS) network, cause the one or more processors to perform a method according to any one of claims 1 to 5.

Images