Method and apparatus for providing service access information for uplink streaming in a 5G media network
The method and apparatus provide service access information for 5G media streaming uplink networks by defining media entry points, addressing the lack in the 3GPP standard, enabling efficient uplink streaming sessions and enhancing 5G media streaming systems.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-11-07
- Publication Date
- 2026-04-01
AI Technical Summary
The 3GPP TS26.501 standard defines a general uplink process for media streaming but lacks service access information for uplink streaming, which is essential for enabling efficient media streaming sessions.
A method and apparatus for providing service access information to a 5G media streaming uplink network by defining media entry points, including parameters and addresses necessary for activating and controlling uplink streaming sessions, using a 5GMSu application function to compile and transmit this information to user devices.
Enables efficient activation and control of uplink media streaming sessions by providing necessary service access information, allowing user devices to select media entry points and transmit content to a 5G media streaming application server, enhancing the functionality of 5G media streaming systems.
Smart Images

Figure 0007838886000009 
Figure 0007838886000010 
Figure 0007838886000011
Abstract
Description
Technical Field
[0002] , , ,
[0004] , , , , ,
[0003] , , , ,
[0001] Cross - reference to related applications This application claims priority to U.S. Provisional Application No. 63 / 423,406, filed on November 7, 2022, and U.S. Application No. 18 / 502,527, filed on November 6, 2023, with the United States Patent and Trademark Office, the disclosures of which are hereby incorporated by reference in their entirety.
[0002] This disclosure generally relates to fifth - generation (5G) media streaming (5GMS), and more particularly, to methods and apparatuses for providing service access information to an uplink streaming 5G network.
Background Art
[0003] The 3rd Generation Partnership Project (3GPP) TS26.501 defines a general architecture for uplink media streaming and downlink media streaming. This standard defines a general uplink process, unlike downlink streaming, but does not define service access information for uplink streaming.
Summary of the Invention
Means for Solving the Problems
[0004] According to one or more embodiments, a method performed by at least one processor of a user device (UE) includes the steps of: the UE receiving service access information including one or more media entry points for an uplink 5G media streaming uplink (5GMS) session; selecting one of the one or more media entry points; activating an uplink 5GMs session based on the selected one or more media entry points; and sending content to a 5G media streaming uplink (5GMSu) application server (AS) during the uplink media streaming session.
[0005] According to one or more embodiments, a method performed by at least one processor within a 5G media streaming uplink (5GMSu) application function (AF) to define one or more media entry points includes the steps of: creating a provisioning session with a 5GMSu application provider for an uplink 5G media streaming (5GMS) session; compiling service access information for an uplink 5GMS session including one or more media entry points; and sending the service access information to the 5GMSu application provider, the service access information being provided to a user device (UE) that selects one of the one or more media entry points.
[0006] According to one or more embodiments, a user device (UE) comprises 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 comprising: receive code configured to cause at least one processor to receive service access information including parameters for one or more media entry points for an uplink 5G media streaming (5GMS) session; select code configured to cause at least one processor to select one of the one or more media entry points; activate code configured to cause at least one processor to activate an uplink 5GMS session based on the selected one or more media entry points; and transmit code configured to cause at least one processor to transmit content to a 5G media streaming uplink (5GMSu) application server (AS) during an uplink media streaming session.
[0007] According to one or more embodiments, a 5G media streaming uplink (5GMSu) system performing an application function (AF) comprises at least one memory configured to store program code, and at least one processor configured to read the program code and act according to the instructions of the program code, the program code comprising creation code that causes at least one processor to create a provisioning session with a 5GMSu application provider for an uplink 5G media streaming (5GMS) session, compilation code that causes at least one processor to compile service access information for an uplink 5GMS session including one or more media entry points, and transmission code that causes at least one processor to transmit the service access information to a 5GMSu application provider, the service access information being provided to a user device (UE) that selects one of the one or more media entry points.
[0008] Further features, properties, and various advantages of the subject matter of this disclosure will become clearer in the following detailed description and accompanying drawings. [Brief explanation of the drawing]
[0009] [Figure 1] This figure shows an environment in which the methods, apparatus, and systems described herein may be implemented according to an embodiment. [Figure 2] This block diagram shows an example of the components of one or more devices in Figure 1. [Figure 3] This is a diagram of a media architecture for media uplink streaming according to an embodiment. [Figure 4] This is a diagram illustrating the operational flow for provisioning a 5GMS system for uplink streaming according to an embodiment. [Figure 5] This is a flowchart of an exemplary process performed by a user device (UE) according to an embodiment. [Figure 6] This is a flowchart of an exemplary process performed by a 5GMSu application function (AF) according to an embodiment. [Modes for carrying out the invention]
[0010] A detailed description of exemplary embodiments follows with reference to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar elements.
[0011] The foregoing disclosures provide examples and explanations, but are not intended to be exhaustive or to limit implementations to the exact forms disclosed. Modifications and alterations are possible in light of the foregoing disclosures, or may be derived from the practice of implementations. Furthermore, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). In addition, it should be understood that in the flowcharts and descriptions of operations provided below, one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least partially), and the order of one or more operations may be changed.
[0012] It will be apparent that the systems and / or methods described herein may be implemented in different forms, such as hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited to the implementation form. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it is understood that software and hardware may be designed to implement the systems and / or methods based on the descriptions herein.
[0013] Certain combinations of features are described in the claims and / or disclosed herein, but 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 described in the claims and / or disclosed in the specification. Each dependent claim listed below may directly depend on only one claim, but the disclosure of possible implementations includes each dependent claim combined with all other claims in the claim set.
[0014] Any elements, actions, or instructions used herein should not be construed as important or essential unless expressly stated otherwise. Furthermore, where used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” When only one item is intended, the term “one” or similar wording is used. Also, where used herein, terms such as “has,” “have,” “having,” “include,” and “including” are intended to be non-restrictive. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise specified. Furthermore, expressions such as “at least one of [A] and [B]” or “at least one of [A] or [B]” should be understood to include A only, B only, or both A and B.
[0015] Throughout this specification, any reference to “one embodiment,” “a certain embodiment,” or similar wording means that a particular feature, structure, or characteristic described in relation to the embodiment shown is included in at least one embodiment of the present solution. Therefore, throughout this specification, the phrases “in one embodiment,” “in a certain embodiment,” and similar wording may, but not necessarily, all refer to the same embodiment.
[0016] Furthermore, the features, advantages, and characteristics described herein may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the disclosure can be carried out even without one or more specific features or advantages of a particular embodiment. In other examples, additional features and advantages may be recognized in certain embodiments that are not present in all embodiments of the disclosure.
[0017] Figure 1 is a diagram of an environment 100 in which the methods, apparatus, and systems described herein may be implemented according to an embodiment. As shown in Figure 1, the environment 100 may include a user device 110, a platform 120, and a network 130. The devices in environment 100 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.
[0018] The user device 110 includes one or more devices capable of receiving, creating, storing, processing, and / or providing information related to the platform 120. For example, the user device 110 may include computing devices (e.g., desktop computers, laptop computers, tablet computers, handheld computers, smart speakers, servers, etc.), mobile phones (e.g., smartphones, wireless phones, etc.), wearable devices (e.g., smart glasses or smartwatches), and similar devices. In some implementations, the user device 110 may receive information from and / or transmit information to the platform 120.
[0019] Platform 120 includes one or more devices as described elsewhere in this specification. In some embodiments, platform 120 may include a cloud server or a group of cloud servers. In some embodiments, platform 120 can be designed to be modular such that software components can be swapped in and out as needed in that case. Thus, platform 120 may be easily and / or quickly reconfigured for different uses.
[0020] In some implementations, as illustrated, platform 120 may be hosted within cloud computing environment 122. In particular, the implementations described herein describe platform 120 as being hosted within cloud computing environment 122, but in some implementations, platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) and may be partially cloud-based.
[0021] Cloud computing environment 122 includes an environment that hosts platform 120. Cloud computing environment 122 may provide services such as computing, software, data access, storage, etc. that do not require end-user (e.g., user device 110) information about the physical location and settings of one or more systems and / or one or more devices that provide hosting for platform 120. As illustrated, cloud computing environment 122 may include a group of computing resources 124 (collectively referred to as "computing resources 124" and individually referred to as "computing resource 124").
[0022] Computing resource 124 includes one or more personal computers, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, computing resource 124 can host platform 120. Cloud resources may include computing instances running within computing resource 124, storage devices provided within computing resource 124, data transfer devices provided by computing resource 124, and the like. In some implementations, computing resource 124 may communicate with other computing resources 124 via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection.
[0023] As further shown in FIG. 1, computing resource 124 includes a group 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, and the like.
[0024] Application 124-1 includes one or more software applications that can be provided to user device 110 and / or platform 120 or accessed by user device 110 and / or platform 120. By using application 124-1, it is possible to eliminate the need to install software applications on user device 110 and run them on user device 110. For example, application 124-1 may include software related to platform 120 and / or any other software that can be provided via cloud computing environment 122. In some implementations, one application 124-1 can transmit and receive information to and from one or more other applications 124-1 via virtual machine 124-2.
[0025] The virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that runs programs like a physical machine. Depending on the intended use of the virtual machine 124-2 and its degree of correspondence to any physical machine, the virtual machine 124-2 may be either a system virtual machine or a process virtual machine. A system virtual machine may provide a complete system platform that supports the execution of a complete operating system (OS). A process virtual machine may run a single program and support a single process. In some implementations, the virtual machine 124-2 can run on behalf of a user (e.g., a user device 110) and manage the foundation of a cloud computing environment 122, such as data management, synchronization, or long-duration data transfer.
[0026] 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 the computing resource 124. In some embodiments, with respect to storage systems, the types of virtualization can be said to include block virtualization and file virtualization. Block virtualization can be said to refer to the extraction (or separation) of logical storage from physical storage so that the storage system can be accessed whether it is physical storage or a heterogeneous structure. Separation increases the degree of freedom by which the storage system administrator manages the storage for end users. File virtualization eliminates the dependency between the access of data at a given file level and the location where the file is physically stored. This can enable optimization of storage usage, server consolidation, and / or non-destructive file migration.
[0027] Hypervisor 124-4 may provide hardware virtualization technology that enables multiple operating systems (e.g., "guest operating systems") to run simultaneously on a host computer such as computing resource 124. Hypervisor 124-4 may present a virtual operating platform to the guest operating systems and may manage the execution of the guest operating systems. Multiple instances of various operating systems can share the virtualized hardware resources.
[0028] Network 130 includes one or more wired and / or wireless networks. For example, Network 130 may include cellular networks (e.g., fifth-generation (5G) networks, long-term evolution (LTE) networks, third-generation (3G) networks, code division multiple access (CDMA) networks, etc.), public land mobile networks (PLMN), local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), telephone networks (e.g., public switched telephone networks (PSTNs)), private networks, ad hoc networks, intranets, the Internet, optical fiber networks, etc., and / or combinations of the above types or other types of networks.
[0029] The number and arrangement of devices and networks shown in Figure 1 are provided as an example. In practice, there may be more devices and / or networks, fewer devices and / or networks, different devices and / or networks, or different arrangements of devices and / or networks compared to those shown in Figure 1. Furthermore, two or more devices shown in Figure 1 may be implemented in a single device, or one device shown in Figure 1 may be implemented as multiple distributed devices. As an addition or alternative, a set of devices in environment 100 (e.g., one or more devices) may perform one or more functions described as being performed by another set of devices in environment 100.
[0030] Figure 2 is a block diagram of exemplary components of one or more devices of Figure 1. Device 200 may correspond to user device 110 and / or platform 120. As shown in Figure 2, device 200 may include a bus 210, a processor 220, memory 230, storage components 240, input components 250, output components 260, and a communication interface 270.
[0031] Bus 210 includes components that enable communication between components of 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), graphics processing unit (GPU), accelerated processing unit (APU), microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or another type of processing component. In some embodiments, the processor 220 includes one or more processors that can be programmed to perform functions. Memory 230 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions used by the processor 220.
[0032] The storage component 240 stores information and / or software related to the operation and use of device 200. For example, the storage component 240 may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk and / or solid-state disk), a compact disk (CD), a digital multipurpose disk (DVD), a floppy disk, a cartridge, magnetic tape and / or another type of non-temporary computer-readable media, along with a corresponding drive.
[0033] The input component 250 includes elements that enable the device 200 to receive information, such as via user input (e.g., a touch screen display, keyboard, keypad, mouse, buttons, switches, and / or a microphone). In addition to or instead of this, the input component 250 may also include sensors that sense information (e.g., a global positioning system (GPS) element, an accelerometer, a gyroscope, and / or actuators). The output component 260 includes elements that provide output information from the device 200 (e.g., a display, a speaker, and / or one or more light-emitting diodes (LEDs)).
[0034] The communication interface 270 includes transceiver-like components (e.g., transceivers and / or separate receivers and transmitters) that enable device 200 to communicate with other devices via wired connections, wireless connections, or a combination of wired and wireless connections. The communication interface 270 may enable device 200 to receive information from and / or provide information to other devices. For example, the communication interface 270 may include Ethernet interfaces, optical interfaces, coaxial interfaces, infrared interfaces, radio frequency (RF) interfaces, Universal Serial Bus (USB) interfaces, Wi-Fi interfaces, cellular network interfaces, and the like.
[0035] Device 200 can perform one or more processes described herein. Device 200 may perform these processes in response to the processor 220 executing software instructions stored in a non-temporary computer-readable medium such as memory 230 and / or storage component 240. Computer-readable medium is defined herein as a non-temporary memory device. A memory device includes a memory space within a single physical storage device or a memory space that extends across multiple physical storage devices.
[0036] Software instructions may be read into memory 230 and / or storage component 240 from another computer-readable medium or from another device via the communication interface 270. During runtime, the processor 220 may execute one or more processes described herein using the software instructions stored in memory 230 and / or storage component 240. In addition to or instead of this, one or more processes described herein may be executed using hardwired circuits instead of software instructions, or using hardwired circuits in combination with software instructions. Therefore, the implementations described herein are not limited to any particular combination of hardware circuits and software.
[0037] The number and arrangement of components shown in Figure 2 are provided as an example. In practice, device 200 may include additional components, fewer components, different components, or components in different arrangements compared to those shown in Figure 2. As an addition or alternative, a set of components of device 200 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 200.
[0038] A 5G media streaming (5GMS) system may be a collection of application functions, application servers, and interfaces derived from a 5G media streaming architecture that supports either a downlink media streaming service, an uplink media streaming service, or both. A 5GMS application provider may include parties that interact with the functions of the 5GMS system and supply 5GMS-aware applications that interact with the functions of the 5GMS system. A 5GMS-aware application may refer to an application within a user device (UE) provided by a 5GMS application provider that includes 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 either a 5GMS downlink (5GMSd) client or a 5GMS uplink (5GMSu) client, or both.
[0039] A 5GMSd client can refer to a UE function that includes at least a 5G media streaming player and a media session handler for downlink streaming, and can be accessed via a clearly defined interface / API. A 5GMSu client can refer to a source of a 5GMSu service that can be accessed via a clearly defined interface / API. A 5GMSu media streamer can refer to a UE function that enables uplink delivery of streaming media content to the application server (AS) function of a 5GMS application provider and interacts with both a 5GMSu-aware application for media capture and subsequent streaming, and a media session handler for media session control.
[0040] A dynamic policy can refer to dynamic policy and billing control (PCC) rules for uplink or downlink application flows during a media session. An ingest session can refer to an uplink media streaming session from a 5GMS AS to a 5GMSu application provider. An ingest session can refer to a session for uploading media content to a 5GMSd AS. A policy template can refer to a set of (quasi-static) policies or control function (PCF) / network exposure function (NEF) API parameters specific to a 5GMS application provider, and the resulting PCC rules. A policy template ID can identify a 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 can 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 can refer to a pointer (e.g., in the form of a URL) that defines the entry point for an uplink media streaming session. A presentation entry can point to a document or a pointer to a document that defines an application presentation, such as an HTML5 document.
[0041] Provisioning Session can refer to a data structure supplied at the interface (M1d) by a 5GMSd application provider that constitutes a 5GMSd feature related to a set of 5GMSd-Aware applications. 5GMSd Media Player can refer to a UE function that enables playback and rendering of media presentations based on media playback entries, as well as exposure to 5GMSd-Aware applications of several basic controls such as play, pause, search, and stop. Server Access Information can refer to a set of parameters and addresses (including 5GMSd AF addresses and 5GMSd AS addresses) necessary to activate the acceptance of a streaming session. Service and Content Discovery can refer to functions and procedures provided to 5GMS-Aware applications by 5GMSd application providers that enable end users to discover available streaming services and content offerings and select specific services or content items for access. Service Announcement can refer to a procedure between a 5GMS-Aware application and a 5GMS application provider so that the 5GMS-Aware application can obtain access information for 5GMS services directly or in the form of a reference to that information.
[0042] A third-party player can refer to a part of an application that uses an API to perform selected 5GMSu functions and thereby plays media content. A third-party uplink streamer can refer to a part of an application that uses an API to perform selected 5GMSu functions and thereby ingests and streams media content.
[0043] Figure 3 shows a media architecture 300 for media uplink streaming according to an embodiment. A 5GMSu application provider 301 may use 5GMSu for an uplink streaming service. In one or more examples, the uplink streaming service may be a live video streaming session using a social media platform. The 5GMSu application provider 301 may be implemented as a server. The 5GMSu application provider 301 may provide a 5GMSu-aware application 302 on the UE 303 to utilize 5GMSu clients 304 and network functions using interfaces and APIs defined in 5GMSu. The 5GMSu application server (AS) 305 may be an AS dedicated to 5G media uplink streaming. The 5GMSu client 304 may be an internal function of the UE 303 dedicated to 5G media uplink streaming.
[0044] The 5GMSu application function (AF) 306 and 5GMSu AS 305 may also be data network (DN) 307 functions. The 5GMSu AF 306 may be implemented as a server. Functions within a trusted DN can be trusted by the operator's network. Therefore, AFs within a trusted DN can communicate directly with some or all 5G core functions. Functions within an external DN can communicate with 5G core functions only via a network exposure function (NEF) 308 using link 320. The NEF 308 facilitates secure access to exposed network services and functions of the 5G network.
[0045] The media architecture 300 can connect the internal functions of the UE 303 and related network functions for 5G media uplink streaming. Therefore, the media architecture 300 may include several functions. For example, a 5GMSu client 304 on the UE 303 may be the source of 5GMSu services that can be accessed through an interface / API. The 5GMSu client 304 may include two subfunctions, a media session handler 309 and a media streamer 310. The media session handler 309 may communicate with the 5GMSu AF 306 to establish, control, and support the distribution of media sessions. The media session handler 309 may expose an API that can be used by the 5GMSu-aware application 302. The media streamer 310 may communicate with the 5GMSu AS 305 to stream media content, serve the 5GMSu-aware application 302 for media capture and streaming, and serve the media session handler 309 for media session control. The 5GMSu-aware application 302 may control the 5GMSu client 304 by implementing logic specific to an external application or content service provider and enabling the establishment of a media session. The 5GMSu AS 305 may host 5G media functions, for example, by being implemented as a Content Delivery Network (CDN). The 5GMSu application provider 301 may be an external application or content-specific media function (e.g., media storage, consumption, transcoding, and redistribution) that streams media from the 5GMSu-aware application 302 using 5GMSu. The 5GMSu AF 306 may provide various control functions to the media session handler 309 and / or the 5GMSu application provider 301 on the UE 303. The 5GMSu AF 306 may relay or initiate requests for different policy control function (PCF) 311 processing or interact with other network functions.
[0046] The media architecture 300 may include several different interfaces. For example, link 321 may be related to M1u, which may be a 5GMSu provisioning API exposed by 5GMSu AF 306 for provisioning use of the media architecture 300 and obtaining feedback. Link 322 may be related to M2u, which may be a 5GMSu publish API exposed by 5GMSu AS 305 and used when 5GMSu AS 305 in a trusted DN such as DN 307 is selected to receive content for streaming services. Link 323 may be related to M3u, which may be an internal API used to exchange information for content hosting on 5GMSu AS 305 in a trusted DN such as DN 307. Link 324 may be related to M4u, which may be a media uplink streaming API exposed by 5GMSu AS 305 to media streamer 310 for streaming media content. Link 325 may be associated with M5u, which may be a media session handling API exposed to the media session handler by 5GMSu AF 305 for processing, controlling, and assisting media sessions, including appropriate security mechanisms (e.g., authorization and authentication). Link 326 may be associated with M6u, which may be a UE 303 media session handling API exposed to the 5GMSu-aware application 302 by the media session handler 309 for utilizing 5GMSu functionality. Link 327 may be associated with M7u, which may be a UE media streamer API exposed to the 5GMSu-aware application 302 and the media session handler 309 by the media streamer 310 for utilizing the media streamer 310.Link 328 may also 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, for example, to provide service access information to the 5GMSu-aware application 302. UE 303 may also be implemented self-contained so that interfaces M6u326 and M7u327 are not exposed.
[0047] The 3GPP TS26.501 standard defines a general uplink process, but unlike downlink streaming, it does not define service access information for uplink streaming.
[0048] For downlink streaming, TS26.501 defines service access information as a set of parameters and addresses delivered to the 5GMSd client for downlink streaming. Service access information includes, for example, the information in Tables 1 to 4 below.
[0049] Table 1 shows the parameters for downlink baseline service access information.
[0050] [Table 1]
[0051] Table 2 shows the downlink streaming access parameters.
[0052] [Table 2]
[0053] Table 3 shows the parameters for the downlink dynamic policy invocation configuration.
[0054] [Table 3]
[0055] Table 4 shows the parameters for a downlink AF-based network-assisted configuration.
[0056] [Table 4]
[0057] Embodiments of this disclosure relate to extending downlink streaming service access information for use with uplink streaming. Embodiments of this disclosure use the same data structure for both downlink and uplink streaming service access information. Embodiments of this disclosure extend media player entries to media entries to support downlink or uplink streaming, making the media entries an array of entry points rather than a single entry point. Embodiments of this disclosure provide associated parameters and identifiers for each entry point, allowing a 5GMS client to select one of them for uplink or downlink streaming. A media entry point is an example of a service access entry point.
[0058] According to one or more embodiments, service access information may include a set of parameters and addresses necessary for a 5GMSu client to activate and control an uplink streaming session. In one or more examples, service access information may be provided together with other service announcement information using M8u. In one or more examples, the 5GMSu client fetches service access information from the 5GMSu AF. For example, the 5GMSu client may send a request to the 5GMSu AF asking it to respond with service access information.
[0059] Regardless of how service access information is provided, it may contain different information depending on the collaboration model between the 5GMS system and the 5GMSu application provider, and further depending on the functionality provided. Table 5 shows an example of baseline parameters for service access information. A provisioning session may be established between the 5GMSu application provider 301 and the 5GMSu AF 306.
[0060] [Table 5]
[0061] Table 6 shows examples of streaming access parameters.
[0062] [Table 6]
[0063] In one or more examples, each entry point may be defined by associated parameters and identifiers. A set may have at least one element.
[0064] According to one or more embodiments, when the dynamic policy invocation feature is activated for an uplink streaming session, the parameters shown in Table 7 below may exist. Table 7 shows examples of parameters for a dynamic policy invocation configuration.
[0065] [Table 7]
[0066] According to one or more embodiments, when 5GMSu AF-based network assistance is activated for an uplink streaming session, the parameters in Table 8 may be present. Table 8 shows example parameters for a 5GMSu AF-based network assistance configuration.
[0067] [Table 8]
[0068] Figure 4 shows an operational flow 400 for provisioning a 5GMS system for uplink streaming according to an embodiment. The operational flow may be executed between a 5GMSu-aware application 402, a 5GMSu client 404, a 5GMSu AF 406, a 5GMSu AS 408, and a 5GMSu application provider 410. The 5GMSu-aware application 402 may correspond to a 5GMSu-aware application 302 (Figure 3). The 5GMSu client 404 may correspond to a 5GMSu client 304 (Figure 3). The 5GMSu AF 406 may correspond to a 5GMSu AF 306 (Figure 3). The 5GMSu AS 408 may correspond to a 5GMSu AS 305 (Figure 3). The 5GMSu application provider 410 may correspond to a 5GMSu application provider 301 (Figure 3).
[0069] Operation 412 may involve SLA negotiation or a self-onboarding procedure. During this operation, the 5GMSu application provider 410 discovers the address (e.g., URL) of the 5GMSdu AF(M1u) for session provisioning.
[0070] In operation 414, the 5GMSu application provider 410 authenticates itself with the system. In one or more examples, authentication is performed between the 5GMSu application provider 410 and the 5GMSu AF 406. This procedure can reuse existing authentication / authorization procedures, such as those defined in the Common API Framework (CAPIF).
[0071] In operation 416, the 5GMSu application provider 410 creates a provisioning session for the uplink streaming session. For example, in operation 416, the 5GMSu application provider 410 sends a message to the 5GMSu AF 406 to establish the provisioning session. This message may include an identifier for the 5GMSu application provider 410 identifier as input. In one or more examples, the 5GMSu application provider 410 queries for capabilities and authorized capabilities.
[0072] In operation 418, the 5GMSu application provider 410 specifies one or more 5GMSu features in the provisioning session. In one or more examples, the 5GMSu application provider 410 sends a request or message to the 5GMSu AF 406 specifying the selection of one or more 5GMSu features. Based on this request, a set of authorized features is activated, such as the content dynamic policy feature, network assistance features, and content publishing features including digest.
[0073] In one or more examples, a content publishing function is provided and, when selected as one of the 5GMSu functions, the 5GMS application provider 410 can configure the content publishing behavior of the 5GMSu AS 408, including the selection of the uplink ingestion protocol and format, content preparation, and the protocol and format for elution. In one or more examples, the content preparation function allows the 5GMS application provider 410 to specify content manipulation by the network-side components of the 5GMS system according to a provisioned content preparation template. When the 5GMSu application provider 410 provisions the content preparation function for uplink media streaming, the network-side components of the 5GMS system can manipulate media content ingested from the 5GMSu client 404 in the UE and cache the manipulated content before eluting it to the 5GMSu application provider 410.
[0074] In one or more examples, a dynamic policy feature is provided and, when selected as one of the 5GMSu features, the 5GMSu application provider 410 can specify a set of policies that can be invoked for uplink streaming sessions. In one or more examples, the UE becomes aware of the selected policies in the form of a list of valid policy template IDs. In one or more examples, when the dynamic policy feature is activated, the 5GMSu application provider 410 can provision one or more policy templates.
[0075] In one or more examples, edge computing capabilities are provided and, when selected as one of the 5GMSu capabilities, the 5GMSu application provider 410 may provide one or more edge resource capabilities that can be used to support either client-driven or application provider-driven management of edge resources associated with a provisioning session.
[0076] In one or more examples, network assistance features allow a UE's 5GMS client to query and manipulate network quality of service for an ongoing media streaming session. For example, network assistance features allow the UE to receive bitrate recommendations from a 5GMSu AF 406 providing network assistance server functionality. The 5GMS AF 406 can receive notifications of network QoS changes (e.g., throughput estimates, bitrate recommendations) using Npcf_PolicyAuthorization notifications or Nnef_MonitoringEvent procedures. The 5GMS AF 406 can receive these policy change notifications asynchronously.
[0077] In operation 420, if the content publishing function is selected, 5GMSu AF 406 executes operation 420A and interacts with 5GMSu AS 408 to allocate resources for the M2u digest protocol and format. Subsequently, in operation 420B, 5GMSu AS 408 responds with the M2u address.
[0078] In operation 422, the 5GMSu AF 406 performs one or more provisioning operations. For example, in operation 422A, the 5GMSu AF 406 compiles service access information. Service access information may include, for example, a provisioning session identifier, the M5u (Media Session Processing) address of the uplink entry point, dynamic policies, and network assistance, along with other access details and options. In one or more examples, the service access information may include a set of parameters and addresses necessary for a 5GMS client to activate receiving a downlink media streaming session or sending an uplink media streaming session, perform dynamic policy calls, consumption reports, and / or metrics reports, and request AF-based network assistance. In one or more examples, the service access information may include one or more of the parameters in Tables 5 to 8.
[0079] In operation 422B, the provisioned parameters and addresses are provided to the 5GMSu application provider 410. For example, the 5GMSu AF 406 may provide the 5GMSu application provider 410 with the results of the compiled service access information. In one or more examples, if the 5GMSu application provider selects full service access information, the results are provided in the form of addresses and configurations for M2u (Essert), M5u (Media Session Processing), and M4u (Media Uplink Streaming). In one or more examples, if the 5GMSu application provider delegates the processing of the service access information to the 5GMS system, a reference to the service access information (e.g., a URL) is provided. The media session handler 309 (Figure 3) later fetches the full service access information from the 5GMSu AF.
[0080] In operation 424, if the content publishing function is provided and selected in operation 418, the 5GMSu application provider 410 can begin retrieving content from the 5GMSu AS 408 via the M2u digest interface.
[0081] In operation 426, the 5GMSu application provider 410 performs a service announcement and updates the UE during the lifetime of the provisioning session. For example, the 5GMSu application provider 410 sends a service announcement message to the 5GMSu-aware application 402. In one or more examples, the service announcement message may include the provisioned parameters and / or addresses received in operation 422B.
[0082] In operation 428, the 5GMSu application provider 410 can update the provisioning session. For example, the 5GMSu application provider 410 can send a message to the 5GMSu AF 406 containing one or more updated parameters of the provisioning session.
[0083] In operation 430, the 5GMSu application provider 410 can terminate the provisioning session. For example, the 5GMSu application provider 410 can send a message to the 5GMSu 406 requesting the termination of the provisioning session. In one or more examples, the provisioning session can be terminated at any time. In one or more examples, the provisioning session can be terminated at a scheduled time or when certain conditions are met (for example, when network quality falls below a threshold). In one or more examples, during the termination of the provisioning session, all associated resources of the provisioning session may be released and the content may be deleted from the 5GMSu AS 408. The 5GMSu application provider 410 can configure a schedule for terminating the provisioning session.
[0084] In operation 432, the 5GMSu AF sends a notification to the 5GMSu application provider 410 indicating that the provisioning session has ended.
[0085] According to the embodiment, the 5GMSu AF 406 can request the creation or reuse of one or more network slices for ingesting the content of a provisioned session. In one or more examples, if multiple network slices are provisioned for ingesting the session content, a list of permitted single network slice selection assistance (S-NSSAI) may be communicated to the target UE (e.g., via the UE Route Selection Policy (URSP) or M5u, or M8u).
[0086] According to one or more embodiments, a method for defining service access entry points for uplink streaming, wherein a provisioning session is identified, one or more media entry points are defined, and optionally, dynamic policy configuration and network assistant configuration information are also provided. For each media entry point, the protocol and parameters are identified, or a pointer to a document containing this information is provided. A 5GMS client can select one of the entry points for uplink streaming of content.
[0087] Figure 5 is a flowchart of an exemplary process 500 performed by a UE such as UE 303 (Figure 3).
[0088] Process 500 can be initiated in operation S502, where the UE receives service access information containing one or more parameters for an uplink media streaming session. In one or more examples, the UE's 5GMSu-aware application receives service access information from the 5GMSu application provider via a service announcement through the M8u interface, in accordance with operation 426. In one or more examples, a 5GMSu client obtains access information from the 5GMSu AF. The service access information may contain one or more of the parameters in Tables 5 to 8.
[0089] The process then proceeds to operation S504, in which the UE activates and controls the uplink media streaming session based on one or more parameters included in the service access information.
[0090] The process then proceeds to operation S506, in which the UE sends content to the 5GMSu AS during the uplink media streaming session.
[0091] Figure 6 is a flowchart of an exemplary process 600 performed by a 5GMSu AF according to an embodiment. Process 600 may be performed by a 5GMSu AF 306 (Figure 3) or a 5GMSu AF 406 (Figure 4).
[0092] The process can be initiated with operation S602, which creates a provisioning session with the 5GMSu application provider for the uplink streaming session. For example, the provisioning session may be created according to operation S416 (Figure 4) described above.
[0093] The process can then proceed to operation S604, in which the 5GMSu AF compiles service access information for the uplink streaming session. For example, the 5GMSu AF 406 may compile service access information according to operation 422A (Figure 4) described above. As described above, operation 422A may be performed based on operations 416, 418, and 420. The service access information may include one or more of the parameters shown in Tables 5 to 8.
[0094] The process can proceed to step S606, in which the 5GMSu AF sends service access information to the 5GMSu application provider. For example, the 5GMSu AF 406 may send service access information to the 5GMSu application provider, which includes address information related to the uplink streaming session. For example, the 5GMSu AF 406 sends service access information to the 5GMSu application provider 410 in accordance with the operation 422B (Figure 4) described above.
[0095] Furthermore, the proposed methods may be implemented by a processing circuit (e.g., one or more processors or one or more integrated circuits). In one embodiment, one or more of the proposed methods are implemented by executing a program stored in a non-temporary computer-readable medium using one or more processors.
[0096] The techniques described above may be implemented as computer software using computer-readable instructions and may be physically stored on one or more computer-readable media.
[0097] The embodiments of this disclosure may be used individually or in any combination of any order. Furthermore, each of the embodiments (and methods thereof) may 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-temporary computer-readable medium.
[0098] While the foregoing disclosures provide examples and explanations, they are not intended to be exhaustive or to limit implementations to the exact forms disclosed. Modifications and adaptations are possible in light of the foregoing disclosures, or may be derived from the practice of implementations.
[0099] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software.
[0100] While combinations of features are enumerated in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of possible embodiments. In fact, many of these features may be combined in ways not specifically described in the claims and / or disclosed in the specification. Each dependent claim listed below may directly depend on only one claim, but the disclosure of possible implementations includes each dependent claim combined with all other claims in the claim set.
[0101] Any elements, actions, or instructions used herein should not be construed as important or essential unless expressly stated otherwise. Furthermore, where used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, where used herein, “set” is intended to include one or more things (e.g., related things, unrelated things, a combination of related and unrelated things) and may also be used in the sense of “one or more.” When only one item is intended, the term “one” or similar words should be used. Furthermore, terms such as “has,” “have,” and “having” as used herein are intended to be open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise specified.
[0102] The above disclosure also includes the embodiments listed below.
[0103] (1) A method performed by at least one processor of a user device (UE), comprising the steps of: receiving service access information by the UE, which includes one or more media entry points for an uplink 5G media streaming uplink (5GMS) session; selecting one of the one or more media entry points; activating an uplink 5GMs session based on the selected one or more media entry points; and sending content to a 5G media streaming uplink (5GMSu) application server (AS) during the uplink media streaming session.
[0104] (2) The method according to feature (1), wherein when the dynamic policy configuration function is activated for an uplink 5GMS session, the service access information further includes one or more of the following: (i) a list of 5GMSu application function AF addresses specifying application programming interfaces (APIs) for the dynamic policy invocation function sent by the 5GMS media session handler, (ii) a list of policy template identifiers, and (iii) a list of service data flow description methods.
[0105] (3) The method according to feature (1) or (2), wherein when the network assistance function is activated for an uplink 5GMS session, the service access information further includes the address of a 5GMSu AF that provides one or more application programming interfaces (APIs) for 5GMSu AF-based network assistance.
[0106] (4) Service access information is provided for each media entry point, comprising at least one protocol and one or more parameters, as described in any one of features (1) to (3).
[0107] (5) The method described in feature (4), wherein one or more media entry points include a Uniform Resource Locator (URL) endpoint of a 5GMSu Application Server (AS), and at the Uniform Resource Locator (URL) endpoint, content is uploaded to the 5GMSu AS via the M4u interface.
[0108] (6) The method according to feature (5), wherein one or more media entry points include a uniform resource locator (URL) for a document downloadable from a 5GMSu application server (AS), and the document includes one or more parameters for sending content to the 5GMSu AS via the M4u interface.
[0109] (7) The method according to any one of features (1) to (6), wherein the step of receiving service access information further includes the step of receiving a service announcement containing service access information from a 5GMSu application provider via the M8u interface by the UE's 5GMSu-aware application during the provisioning session.
[0110] (8) The method according to any one of features (1) to (7), wherein the step of receiving service access information further includes the step of obtaining service access information from a 5GMSu application function (AF) by the UE's 5GMSu client.
[0111] (9) The method according to any one of features (1) to (8), wherein the service access information includes a provisioning session identifier that identifies a provisioning session between the 5GMSu application provider and the 5GMSu application function (AF).
[0112] (10) Service access information is compiled by the 5GMSu application function (AF) in any one of the following ways: (1) to (9).
[0113] (11) A method performed by at least one processor within a 5G media streaming uplink (5GMSu) application function (AF) for defining one or more media entry points, comprising the steps of: creating a provisioning session with a 5GMSu application provider for an uplink 5G media streaming (5GMS) session; compiling service access information for an uplink 5GMS session including one or more media entry points; and sending the service access information to the 5GMSu application provider, wherein the service access information is provided to a user device (UE) that selects one of the one or more media entry points.
[0114] (12) The method according to feature (11), wherein when the dynamic policy configuration function is activated for an uplink 5GMS session, the service access information further includes (i) a list of 5GMSu application function AF addresses specifying application programming interfaces (APIs) for the dynamic policy invocation function sent by the 5GMS media session handler, (ii) a list of policy template identifiers, and (iii) a list of service data flow description methods.
[0115] (13) The method according to feature (11) or (12), wherein when a network assistance function is activated for an uplink 5GMS session, the service access information further includes the address of a 5GMSu AF that provides one or more application programming interfaces (APIs) for 5GMSu AF-based network assistance.
[0116] (14) The method according to any one of features (11) to (13), wherein the service access information includes at least one protocol and one or more parameters for each media entry point.
[0117] (15) The method of feature (14), wherein one or more media entry points include a Uniform Resource Locator (URL) endpoint of a 5GMSu Application Server (AS), and the Uniform Resource Locator (URL) endpoint uploads content to the 5GMSu AS via the M4u interface.
[0118] (16) The method according to feature (15), wherein one or more media entry points include a uniform resource locator (URL) for a document downloadable from a 5GMSu application server (AS), and the document includes one or more parameters for sending content to the 5GMSu AS via the M4u interface.
[0119] (17) A method according to any one of features (11) to (16), wherein a 5GMSu application provider provides service access information to the UE's 5GMSu-aware application in a service announcement via the M8u interface.
[0120] (18) The method according to any one of features (11) to (17), further comprising the step of receiving a request from a UE's 5GMSu client to obtain service access information.
[0121] (19) User equipment (UE) comprising at least one memory configured to store program code, and at least one processor configured to read program code and operate according to the instructions of the program code, wherein the program code includes receive code configured to cause at least one processor to receive service access information including parameters for one or more media entry points for an uplink 5G media streaming (5GMS) session, select code configured to cause at least one processor to select one of one or more media entry points, activate code configured to cause at least one processor to activate an uplink 5GMs session based on the selected media entry point, and transmit code configured to cause at least one processor to transmit content to a 5G media streaming uplink (5GMSu) application server (AS) during an uplink media streaming session.
[0122] (20) A 5G media streaming uplink (5GMSu) system that performs an application function (AF), the 5GMSu system comprising at least one memory configured to store program code, and at least one processor configured to read program code and operate according to the instructions of the program code, wherein the program code comprises creation code that causes at least one processor to create a provisioning session with a 5GMSu application provider for an uplink 5G media streaming (5GMS) session, compilation code that causes at least one processor to compile service access information for an uplink 5GMS session including one or more media entry points, and transmission code that causes at least one processor to transmit the service access information to a 5GMSu application provider, the service access information being provided to a user device (UE) that selects one of one or more media entry points. [Explanation of Symbols]
[0123] 100 Environment 110 User Devices 120 platforms 122 Cloud Computing Environment 124 Computing Resources 124-1 Application 124-2 Virtual Machine 124-3 Virtualized Storage 124-4 Hypervisor 130 Networks 200 devices 210 Bus 220 processors 230 memory 240 memory components 250 input components 260 Output Components 270 Communication Interfaces 300 Media Architectures 301 5GMSu Application Provider 302 5GMSu Aware Application 303 UE 304 5GMSu client 305 5GMSu Application Server (AS) 306 5GMSu Application Function (AF) 307 Data Network (DN) 308 Network Exposure Function (NEF) 309 Media Session Handler 310 Media Streamers 311 Policy Control Function (PCF) 320 links 321 links 322 links 323 links 324 links 325 links 326 links 327 links 328 links 400 Operation Flow 402 5GMSu Aware Application 404 5GMSu Client 406 5GMSu AF 408 5GMSU AS 410 5GMSu Application Provider 500 processes 600 processes
Claims
1. A method performed by at least one processor of a user device (UE), The steps include: receiving by the UE a pointer to a document containing service access information, which includes one or more media entry points for an uplink 5G media streaming uplink (5GMS) session, compiled by the 5G media streaming uplink (5GMSu) application function (AF) and sent to the 5GMSu application provider; The step of selecting one of the one or more media entry points, The steps of activating the uplink 5GMs session based on the selected one or more media entry points, During the aforementioned uplink media streaming session, the content is transmitted to the 5G media streaming uplink (5GMSu) application server (AS). Methods that include...
2. The method according to claim 1, wherein when the dynamic policy configuration function is activated for the uplink 5GMS session, the service access information further includes one or more of the following: (i) a list of 5GMSu application function AF addresses specifying application programming interfaces (APIs) for the dynamic policy invocation function transmitted by the 5GMS media session handler, (ii) a list of policy template identifiers, and (iii) a list of service data flow description methods.
3. The method according to claim 1, wherein when the network support function is activated for the uplink 5GMS session, the service access information further includes the address of a 5GMSu AF that provides one or more application programming interfaces (APIs) for 5GMSu AF-based network support.
4. The method according to claim 1, wherein the service access information includes at least one protocol and one or more parameters for each media entry point.
5. The method according to claim 4, wherein the one or more media entry points include a uniform resource locator (URL) endpoint of a 5GMSu application server (AS), and at the uniform resource locator (URL) endpoint, content is uploaded to the 5GMSu AS via an M4u interface.
6. The one or more media entry points include a uniform resource locator (URL) for a document downloadable from the 5GMSu application server (AS). The method according to claim 5, wherein the document includes one or more parameters for transmitting the content to the 5GMSu AS via the M4u interface.
7. The step of receiving the service access information is: During a provisioning session, the UE receives a service announcement, including the service access information, from the 5GMSu application provider via the M8u interface through the UE's 5GMSu-aware application. The method according to claim 1, further comprising:
8. The step of receiving the service access information is: The UE's 5GMSu client obtains the service access information from the 5GMSu application function (AF). The method according to claim 1, further comprising:
9. The method according to claim 1, wherein the service access information includes a provisioning session identifier that identifies a provisioning session between a 5GMSu application provider and a 5GMSu application function (AF).
10. A method for defining one or more media entry points, which is performed by at least one processor within a 5G media streaming uplink (5GMSu) application function (AF), wherein the method is: Steps include creating a provisioning session with a 5GMSu application provider for an uplink 5G media streaming (5GMS) session, The steps include compiling a document containing service access information for the uplink 5GMS session, which includes one or more media entry points, The steps include sending the aforementioned service access information to the 5GMSu application provider. Includes, A method in which a pointer to the document containing the service access information is provided to a user device (UE) that selects one of the one or more media entry points.
11. The method according to claim 10, wherein when the dynamic policy configuration function is activated for the uplink 5GMS session, the service access information further includes one or more of the following: (i) a list of 5GMSu application function AF addresses specifying an application programming interface (API) for the dynamic policy invocation function transmitted by the 5GMS media session handler, (ii) a list of policy template identifiers, and (iii) a list of service data flow description methods.
12. The method according to claim 10, wherein when the network assistance function is activated for the uplink 5GMS session, the service access information further includes the address of a 5GMSu AF that provides one or more application programming interfaces (APIs) for 5GMSu AF-based network assistance.
13. The method according to claim 10, wherein the service access information includes at least one protocol and one or more parameters for each media entry point.
14. The method according to claim 13, wherein the one or more media entry points include a uniform resource locator (URL) endpoint of a 5GMSu application server (AS), and at the uniform resource locator (URL) endpoint, content is uploaded to the 5GMSu AS via an M4u interface.
15. The one or more media entry points include a uniform resource locator (URL) for a document downloadable from the 5GMSu application server (AS). The method according to claim 14, wherein the document includes one or more parameters for transmitting the content to the 5GMSu AS via the M4u interface.
16. The method according to claim 10, wherein the 5GMSu application provider provides the service access information to the UE's 5GMSu-aware application in a service announcement via the M8u interface.
17. The method according to claim 10, further comprising the step of receiving a request from the UE's 5GMSu client to obtain the service access information.
18. A user device (UE) configured to perform the method described in any one of claims 1 to 9.
19. A 5G media streaming uplink (5GMSu) system configured to perform the method described in any one of claims 10 to 17.
20. A computer program comprising program code configured, when executed by at least one processor, to cause the at least one processor to perform the method according to any one of claims 1 to 9.
21. A computer program comprising program code configured, when executed by at least one processor, to cause the at least one processor to perform the method according to any one of claims 10 to 17.
Citation Information
Patent Citations
Network-based media processing (NBMP) deployment with framework for live uplink streaming (FLUS) and 5g application function (AF)
US20220182435A1