Media Streaming with Edge Computing
The 5G media streaming system addresses latency and bandwidth challenges by selecting and instantiating edge application servers based on user device location and capabilities, enhancing media streaming efficiency in 5G networks.
Patent Information
- Application Number
- JP2022561025
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-09-28
- Filing Date
- 2021-09-30
- Publication Date
- 2024-12-04
- Estimated Expiration
- 2041-09-30
AI Technical Summary
Existing media streaming systems face challenges in efficiently utilizing edge computing to reduce latency and bandwidth requirements, particularly in 5G networks, due to the lack of effective methods for selecting and instantiating edge application servers based on device location and capabilities.
The implementation of a 5G media streaming system that utilizes edge computing by enabling a processing circuit to send requests to a 5GMS application function, which determines an edge application server based on user device location and capabilities, and instantiates a 5GMS application server for media streaming services.
This approach reduces latency and enhances bandwidth utilization by optimizing the selection and instantiation of edge application servers, thereby improving the efficiency of media streaming services in 5G networks.
Smart Images

Figure 0007594605000001 
Figure 0007594605000002 
Figure 0007594605000003
Abstract
Description
[Technical field]
[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims benefit of priority to U.S. Provisional Application No. 63 / 142,384, entitled "A METHOD FOR EDGE RESOURCE DISCOVERY, MANAGEMENT AND PROCESSING SUPPORT IN 5G MEDIA STREAMING," filed on January 27, 2021, which claims benefit of priority to U.S. Provisional Application No. 17 / 488,049, entitled "MEDIA STREAMING WITH EDGE COMPUTING," filed on September 28, 2021. The entire disclosure of the prior application is incorporated by reference in its entirety.
[0002] [Technical field] This disclosure describes embodiments generally relating to edge computing in media streaming. [Background technology]
[0003] The background discussion provided herein is intended to generally present the context of the present disclosure, and the inventors' work is not expressly or impliedly admitted as prior art to the present disclosure, either to the extent that such work is described in this background section, or in any aspect of the description that may not qualify as prior art at the time of filing.
[0004] Various media applications and services require significant processing power. In some instances, cloud processing is preferred when workloads that would otherwise be performed on the client device can be offloaded to a remote server. Because the remote server has very high computing power, complex media processing tasks can be performed by the remote server and then final or near-final results can be sent to the client device.
[0005] Edge computing provides a network architecture that enables the deployment of cloud computing services closer to user devices, achieving lower latency, higher bandwidth, and reduced backhaul traffic. Summary of the Invention
[0006] Aspects of the present disclosure provide a method and apparatus for 5G media streaming (5GMS). In some examples, a user device includes a processing circuit. The processing circuit sends a request from a 5GMS service client of the user device to a 5GMS application function of a 5G data network. The request can request a 5GMS service. The processing circuit then receives an acknowledgement from the 5GMS application function along with information of a 5GMS application server instantiated by an edge application server. The processing circuit can then perform 5G media streaming based on the information of the 5GMS application server.
[0007] In some examples, the edge application server can be selected based on at least one of the location of the user device, the location of the edge application server, and the capabilities of the edge application server.
[0008] In some examples, the processing circuitry sends the request in response to a media request from a 5G MS-aware application in the user device.
[0009] In some examples, the processing circuitry sends the request via an edge enabler client interface of the 5GMS service client to an edge enabler server in the 5GMS application function.
[0010] In some examples, the edge application server is determined by the edge enabler server. In one example, the edge enabler server determines the edge application server based on filtering information in the request. In another example, the edge enabler server determines the edge application server based on a location of the user device. In another example, the edge enabler server determines the edge application server based on an acknowledgement from the edge application server in response to a discovery request from the edge enabler server.
[0011] In some examples, the 5GMS application function requests an edge application server to instantiate a 5GMS application server and requests the 5GMS application server to provide a 5GMS service.
[0012] According to some aspects of the present disclosure, a processing circuit for a 5GMS application function in a 5G data network can receive a request for a 5GMS service. The processing circuit for the 5GMS application function can request an edge application server to instantiate a 5GMS application server to provide the 5GMS service. The processing circuit can then respond to the request with information of the 5GMS application server.
[0013] In some examples, the processing circuitry for the 5G MS application function receives the request from a 5G MS application provider in the 5G data network. In some examples, the processing circuitry for the 5G MS application function receives the request from a user device.
[0014] In some examples, the processing circuitry for the 5GMS application function can perform the functions of an edge enabler server and determine the edge application server. In one example, the processing circuitry for the 5GMS application function determines the edge application server based on filtering information in the request, such as required capabilities, features, etc.
[0015] In another example, the processing circuit for the 5GMS application function determines the edge application server based on location information of the user device and location information of the edge application server.
[0016] In another example, the processing circuitry for the 5GMS application function can determine the edge application server based on an acknowledgement from the edge application server in response to a discovery request from the edge enabler server.
[0017] In some examples, the processing circuitry for the 5GMS application function can request an edge application server to instantiate a 5GMS application server, and then request the 5GMS application server to provide a 5GMS service.
[0018] Aspects of the present disclosure also provide a non-transitory computer-readable medium having stored thereon instructions that, when executed by a computer, cause the computer to perform a method for media processing. [Brief description of the drawings]
[0019] Further features, nature and various advantages of the disclosed subject matter will become more apparent from the following detailed description and the accompanying drawings. [Figure 1] 1 illustrates an exemplary media processing system according to one embodiment of the present disclosure. [Diagram 2] 1 illustrates an example of a graph according to an embodiment of the present disclosure. [Diagram 3] FIG. 1 illustrates a block diagram of a 5G media streaming (5GMS) system in some examples. [Figure 4] FIG. 1 illustrates a block diagram of an edge computing system in some examples. [Diagram 5]1 illustrates a block diagram of an edge-enabled media streaming system according to some embodiments of the present disclosure. [Figure 6] 1 shows a diagram illustrating a process flow for performing a media service according to some embodiments of the present disclosure. [Figure 7] FIG. 13 shows another diagram illustrating a process flow for executing a media service according to some embodiments of the present disclosure. [Figure 8] 1 shows a flowchart outlining an example process according to some embodiments of the present disclosure. [Figure 9] 1 shows a flowchart outlining an example process according to some embodiments of the present disclosure. [Figure 10] FIG. 1 is a schematic diagram of a computer system according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0020] Cloud computing refers to the use of a network of remote servers over a network (e.g., the Internet) to deliver information computing services (e.g., cloud services). The network architecture (e.g., including hardware and software) through which cloud services are provided to service consumers (e.g., clients) is called a cloud. Cloud computing provides access to a wide range of services such as data processing, media processing, servers, storage, networks, applications, online services, etc. In some instances, media processing can be computationally intensive, and therefore, media processing clouds can be used to offload significant media processing workloads to remote servers.
[0021] Generally, a cloud computing system includes a network, one or more servers, and one or more client devices. The network facilitates communication between the server and the client devices. The client devices may be, for example, smartphones, tablet computers, laptops, personal computers, wearable devices, head-mounted displays (HMDs), etc. The servers may include any suitable computing or processing devices capable of providing computing services for one or more client devices. For example, each server may include one or more processing devices, one or more memories for storing instructions and data, and one or more network interfaces for facilitating communication over the network. In some embodiments, the server includes a workflow manager capable of selecting functions to perform processing tasks and building a workflow pipeline.
[0022] A media processing system may include various entities with different functions, such as a workflow manager, a capability repository, a media processing entity (MPE), a network based media processing (NBMP) source, and so on.
[0023] In a media processing system, an NBMP source describes the requested media processing and provides information about the nature and format of the media data. Thus, the NBMP workflow manager can establish a media processing workflow and notify the NBMP source that the workflow is ready, and then the media processing can begin. For example, the media source can start sending media to the network for processing.
[0024] In some embodiments, an NBMP workflow includes media processing tasks that are connected based on input / output relationships between the media processing tasks. Each of the media processing tasks performs a media processing operation, such as video decoding, video stitching, video encoding, etc. In one example, a first media processing task performs a media processing operation based on an input and generates an output. The output of the first media processing task can be used as an input to a second media processing task connected to the first media processing task. In other words, the NBMP workflow can be thought of as a connection graph of media processing tasks.
[0025] The workflow manager can ensure correct operation of the workflow by configuring and monitoring each task and workflow output. In some examples, the workflow manager is configured to select a media processing function as a task based on the workflow description received from the NBMP source and instantiate the media processing function.
[0026] In the media processing system, appropriate interactions can be performed to establish, load, instantiate, and monitor media processing entities that perform media processing tasks. In some examples, application programming interfaces (APIs) can be defined between the NBMP source and the workflow manager, and between the workflow manager and the tasks, and APIs are defined to discover appropriate functions. In some examples, the media processing system is configured to be media format and protocol agnostic. The media processing system can identify and convey media, metadata, and auxiliary information formats for data exchanged between the media source, the workflow manager, and the tasks.
[0027] In some examples, interfaces can be defined for media processing, including both data formats and application programming interfaces (APIs) between entities connected through a digital network. Users can access and configure user operations remotely for efficient and intelligent processing. Workflows to be applied to media data can be described and managed. Media data can be uploaded to the network and media processing tasks can be instantiated and configured. In some embodiments, dynamic creation of media processing pipelines and access to processed media data and metadata in real-time or delayed manner is possible. Media and metadata formats used between media sources, workflow managers and media processing entities in the media processing pipeline are also specified.
[0028] In one example, a client (e.g., a creator, service provider, consumer of digital media) can describe media processing operations to be performed by media processing entities in a network. The workflow can be described by configuring a set of media processing functions accessible through an interface (e.g., NBMP API). A media processing entity (MPE) can perform processing tasks that are applied to media and associated metadata received from a media source, or other tasks. An MPE can provide capabilities to configure, manage, and monitor processing tasks. A media processing task can be a process that is applied to media and metamedia inputs and produces data and associated metadata outputs that can be consumed by a media sink or other media processing tasks.
[0029] The media processing system can support a variety of delivery methods, such as streaming, file delivery, push-based progressive download, hybrid delivery, multi-path and heterogeneous network environments.
[0030] FIG. 1 illustrates an exemplary media processing system (e.g., NBMP system, NBMP reference architecture, NBMP architecture) (100) according to an embodiment of the present disclosure. The media processing system (100) can include multiple entities, such as a media source (101), a workflow manager (e.g., NBMP workflow manager) (103), a capability repository (105), a media source (111), a media processing entity (MPE) (113), a media sink (115), a third party entity, etc. The media processing system (100) can include additional media sources, media sinks, and / or media processing entities. The media processing system (100) can process media data between one or more processing entities in a network. Various media and control information (or control data) for media, etc. can be communicated between multiple entities in the media processing system (100).
[0031] To provide context for discussion purposes, the media processing system (100) is described below as an NBMP system (100), although the description may apply to any media processing system, as appropriate.
[0032] The NBMP source (101) can describe or alternatively represent media processing in a network. The capability repository (105) can contain NBMP function descriptions of various NBMP functions. The NBMP source (101) and the workflow manager (103) can retrieve NBMP function descriptions or functions from the capability repository (105). The NBMP functions can represent implementations of standalone self-contained media processing operations and / or corresponding descriptions of the operations.
[0033] A processing task or tasks may represent run-time instances of NBMP functionality executed by the MPE (113). An NBMP workflow or workflows may be represented by a graph (e.g., a directed acyclic graph (DAG)) of one or more connected tasks that accomplish the requested media processing. A workflow manager (103) may provide tasks and connect tasks to create, control, manage, and monitor workflows, for example based on a workflow description document (WDD).
[0034] A media source (111) can provide media content (e.g., media data, supplemental information) to be processed by a workflow. The supplemental information can include metadata or auxiliary information related to the media data. The media source (111) can provide input to the workflow. A media sink (115) can consume the output of the workflow. The MPE (113) can perform one or more media processing tasks to process the media content.
[0035] Different entities in the NBMP system (100) (e.g., NBMP source (101), workflow manager (103), MPE (113)) can use APIs to invoke and respond to media service requests. The APIs can include NBMP workflow APIs or workflow APIs, capability discovery APIs, and task APIs. The workflow APIs can provide an interface between the NBMP source (101) and the workflow manager (103). The task APIs can provide an interface between the workflow manager (103) and media processing tasks. The capability discovery APIs can provide an interface between the workflow manager (103) / NBMP source (101) and the capability repository (105).
[0036] The above NBMP interface can be used to create and control media processing workflows in a network. The NBMP system (100) can be divided into a control plane and a media plane (or media data plane). The control plane can include a workflow API, a function discovery API, and a task API.
[0037] The workflow API can be used by the NBMP source (101) to create and control media processing workflows. The NBMP source (101) can communicate with the workflow manager (103) using the workflow API to configure and control media processing in the network. By including a workflow resource (WR) in the workflow API operation, when the NBMP source (101) sends a request to the workflow manager (103), the workflow manager (103) can parse the WR, the included WDD and the corresponding descriptors, and take appropriate action according to the requested operation. The workflow manager (103) can then confirm the request with a response. The workflow API operations can include creating a workflow (e.g., CreateWorkflow), updating a workflow (e.g., UpdateWorkflow), deleting a workflow (e.g., DeleteWorkflow), retrieving a workflow (RetrieveWorkflow), etc.
[0038] The capability discovery API can provide a means for a workflow manager (103) and / or an NBMP source (101) to discover media processing capabilities that can be loaded as part of a media processing workflow.
[0039] The Task API can be used by the Workflow Manager (103) to configure and monitor tasks (e.g., Task 1 and Task 2 executed by the MPE (113)) at runtime. The Task API can define an interface for configuration of a media processing task by the Workflow Manager (103), for example, after resources for the task have been allocated in the MPE (113). Task API operations can include creating a task (e.g., CreateTask), updating a task (e.g., UpdateTask), retrieving a task (e.g., GetTask), deleting a task (e.g., DeleteTask), etc.
[0040] In the media plane, media formats, metadata and supplemental information formats can be defined between NBMP sources (111) and tasks, and between tasks.
[0041] A workflow description (WD) can be passed from an NBMP source (101) to a workflow manager (103). The WD can describe information such as input and output data, functions, and other requirements for a workflow.
[0042] A workflow manager (103) can receive the WDD from the NBMP source (101) and construct a workflow for the requested media processing. In the procedure of the workflow, media processing functions can be selected, for example, from a function repository (105), and then corresponding media processing tasks can be composed and distributed to a set of one or more MPEs (including, for example, MPE (113)).
[0043] The set of functions provided by the function repository (105) can be read by the NBMP source (101) and the workflow manager (103). In an embodiment, the NBMP source (101) requests the creation of a workflow using the set of functions in the function repository (105). Thus, the NBMP source (101) is configured to select functions for the workflow. The NBMP source (101) can request the creation of a workflow as described below. The NBMP source (101) can use a description of the media processing task for which the workflow is to be created and can specify a connection map to define the input and output connections of the media processing task. When the workflow manager (103) receives the above information from the NBMP source (101), the workflow manager (103) can instantiate the media processing tasks based on their respective function names and can connect the media processing tasks according to the connection map.
[0044] Alternatively, the NBMP source (101) can request the creation of a workflow using a set of keywords that the workflow manager (103) can use to build the workflow. Thus, the NBMP source (101) does not need to know the set of functions to be inserted into the workflow. The NBMP source (101) can request the creation of a workflow as described below. The NBMP source (101) can use a set of keywords that allows the workflow manager (103) to find the appropriate functions and specify the requirements of the workflow using an appropriate workflow description.
[0045] When the workflow manager (103) receives the above information (e.g., a set of keywords) from the NBMP source (101), the workflow manager (103) can create a workflow, for example, by searching for appropriate functions using the keywords specified in the processing descriptor. The workflow manager (103) can then use other descriptors in the workflow description to provide media processing tasks and connect the media processing tasks to create the final workflow.
[0046] The processing model of the workflow manager (103) can be described as follows.
[0047] The workflow manager (103) can discover available media processing capabilities as follows: The NBMP capability repository (105) can provide a capability discovery interface (or API) to allow external entities to query for media processing capabilities that can fulfill processing requests. The workflow manager (103) can access a directory service that provides a searchable list of media processing capabilities. The workflow manager (103) can use the description of the media processing tasks in the workflow description to find appropriate capabilities for the workflow.
[0048] The selection of a media processing task for a workflow can be described as follows: When a request for media processing is received from an NBMP source (101), the workflow manager (103) can search the feature repository (105) to find a list of all available features that can fulfill the workflow. Using the workflow description from the NBMP source (101), the workflow manager (103) can find features in the feature repository (105) to implement the workflow, which can rely on information for media processing from the MBMP source (101). The information for media processing can include information on input and output descriptions, descriptions of the required processing, and other descriptions of the features in the feature directory (105). The mapping of source requests to appropriate media processing tasks to be included in the workflow can be part of the implementation of the NBMP in the network. The input and output ports can be used to make references to the input streams, in order to reference and link the input sources with the input and output port names during task creation.
[0049] The search for suitable features to be instantiated as tasks can be performed by the workflow manager (103) using a feature discovery API. Alternatively, the workflow manager (103) can use the feature discovery API to retrieve detailed information of all or some suitable features in the feature repository (105). The workflow manager (103) can then compare the information for media processing from the NBMP source (101) with the different descriptors of each feature.
[0050] The selected media processing tasks can be configured in a workflow. When a function to be included in the workflow is identified, the NBMP workflow manager (103) can instantiate the function as a respective task and configure the task, so that the task can be added to the workflow. The NBMP workflow manager (103) can extract configuration data from the media processing information received from the NBMP source (101) and configure the corresponding task. Task configuration can be performed using a task API (e.g., the NBMP task API).
[0051] Task allocation and distribution can be described as follows: The workflow manager (103) can use workflows to perform processing deployment and configure media processing entities. In one example, for computationally intensive media processing requests, the workflow manager (103) can configure multiple computation instances and distribute the workload among the multiple computation instances. Thus, the workflow manager (103) can connect and configure multiple computation instances as needed. In one example, the workflow manager (103) provides a load balancer that assigns the same task to multiple instances and distributes the workload among the multiple instances using a selected scheduling mechanism. In an alternative example, the workflow manager (103) assigns different operations of the same task to different instances (e.g., parallel operations). In both of the above examples, the workflow manager (103) can set up workflow paths between the instances, thus allowing for a good workload implementation. The workflow manager (103) can configure tasks to push the processed media data / streams to the next task in the workflow graph (or make them available through a pull mechanism).
[0052] When the workflow manager (103) receives a WDD from the NBMP source (101), the workflow manager (103) can perform a selection of media processing functions to be inserted into the workflow. When a list of tasks to be included in the workflow has been compiled, the workflow manager (103) can connect the tasks to prepare the workflow.
[0053] The workflow manager (103) can generate a workflow, for example, as represented by a graph (e.g., DAG) from the WDD. Figure 2 illustrates an example of a graph (e.g., DAG) (200) according to an embodiment of the present disclosure. The DAG (200) can include multiple nodes (T1)-(T6) and multiple links (or connections) (202)-(208). In one example, the DAG (200) represents a workflow (200).
[0054] Each node of the DAG (200) may represent a media processing task in the workflow (200). A link (e.g., link (202)) connecting a first node (e.g., node (T1)) to a second node (e.g., node (T2)) in the DAG (200) may represent the transmission of an output of the first node (e.g., node (T1)) as an input to the second node (e.g., node (T2)).
[0055] In general, a workflow may include any suitable number of inputs (or workflow inputs) and any suitable number of outputs (or workflow outputs). Workflow inputs may connect to media sources (111), other workflows, etc., and workflow outputs may connect to media sinks (115), other workflows, etc. The workflow (200) has an input (201) and outputs (209) and (210). In some embodiments, the workflow (200) may have one or more outputs from intermediate nodes.
[0056] In some examples, media streaming applications can run on a cloud platform. For example, a 5G media streaming (5GMS) system can support services including mobile network operator (MNO) and third-party downlink or uplink media streaming services. The 5GMS system can provide related network, UE functions and APIs. The 5GMS system can be divided into functionally independent components, enabling different deployments with varying degrees of integration between 5G MNOs and content providers.
[0057] In general, streaming can be defined as the time-continuous delivery of media content as mainstream media. Media content is primarily transmitted in one direction and is available as it is received. Furthermore, streaming media content can be streamed as it is being generated, and the streaming can be called live streaming. If streaming content is already generated, the streaming can be called on-demand streaming.
[0058] FIG. 3 shows a block diagram of a 5GMS system (300) in some examples. The 5GMS system (300) may include a user equipment (UE) (301) and a data network (DN) (302). The 5GMS system (300) may be an assembly of application functions (AFs), application servers (ASs), clients (e.g., UE internal functions), and interfaces that support downlink media streaming services or uplink media streaming services or both. In downlink streaming, the DN (302) is the origin of the media and the UE (301) acts as the consuming device. In uplink streaming, the UE (301) is the origin of the media and the DN (302) acts as the consuming entity. The components of the 5GMS system (300) may be provided by the MNO as part of 5GS and / or may be provided by a 5GMS application provider.
[0059] In some examples, the UE (301) may include a 5GMS aware application (310) and a 5GMS client (320). The 5GMS client (320) may include a media session handler (321) and a media streamer (322). The DN (302) may include a 5GMS application provider (330), a 5GMS application function (AF) (340), and a 5GMS application server (AS) (350). The 5GMS system (300) may include two 5G functions (e.g., as specified by the 3GPP 5G standard), namely, a network exposure function (NEF) (361) and a policy control function (PCF) (362). These elements are coupled to each other as shown in FIG. 3.
[0060] The 5GMS application provider (330) uses the 5GMS system (300) for streaming services. The 5GMS application provider (330) provides or is associated with a 5GMS-aware application (310) on the UE (301) to utilize the 5GMS client (320) and network functions (340 and 350) using interfaces and APIs defined in the 5GMS system (300). For example, the 5GMS client (320) is typically controlled by a 5GMS-aware application (310) (e.g., an application) that implements application or content service provider specific logic to enable a media session to be established. For example, the 5GMS application provider (330) can be an application or content specific media function (e.g., media storage, utilization, transcoding, and redistribution) that streams media from the 5GMS-aware application using the 5GMS system (300).
[0061] The 5GMS AF (340) may be an application function similar to that dedicated to 5G media streaming defined in section 6.2.10 of 3GPP TS 23.501, “System architecture for the 5G System (5GS)”. In some examples, the 5GMS AF (340) supports application-related control functions that can affect traffic routing, access to network exposure functions (NEFs), interaction with policy frameworks for policy control, etc. For example, the 5GMS AF (340) may be an application function that provides various control functions to the media session handler (321) and / or 5GMS application providers in the UE. The 5GMS AF (340) may also relay or initiate requests for different policy or charging function (PCF) processing or interact with other network functions via the NEF (361). There may be multiple 5GMS AFs, each exposing one or more APIs, present in a deployment and present in the DN (302).
[0062] The 5GMS AS (350) can be an application server dedicated to 5G media streaming, such as an application server hosting media function. In various examples, there may be different realizations of the 5GMS AS, such as a content delivery network (CDN). The 5GMS AF (340) and the 5GMS AS (350) are data network (DN) functions and communicate with the UE (301) via the N6 interface as defined in TS 23.501.
[0063] The 5G MS Client (320) may be a UE internal function dedicated to 5G media streaming.
[0064] The 5GMS Media Streamer (322) can be a UE function that enables uplink delivery of streaming media content to the AS function (350) of the 5GMS Application Provider (330). The 5GMS Media Streamer (322) can interact with both the 5GMS-aware application (310) for media capture and subsequent streaming, and the Media Session Handler (321) for media session control. For example, the 5GMS Media Streamer (322) captures media on a provided input device. The 5GMS Media Streamer (322) exposes some basic controls, such as capture, pause, and stop, to the 5GMS-aware application (310). In one example, the 5GMS AF (340) can interact with the NEF (361) for NEF-enabled API access. For example, the 5GMS AF (340) can interact with the PCF (362) using the NEF (361).
[0065] The Media Session Handler (321) may be a function on the UE (301) that communicates with the 5GMS AF (340) to establish, control and support the delivery of media sessions. The Media Session Handler (321) exposes an API that can be used by 5GMS-aware applications (310).
[0066] In some examples, the 5GMS system (300) includes various interfaces, such as M1, M2, M3, M4, M5, M6, M7, M8, etc., and descriptions of the interfaces can be provided as follows:
[0067] M1 (5GMS Provisioning API): An external API exposed by the 5GMS AF (340) to provide usage of the 5G media streaming system and obtain feedback.
[0068] M2 (5GMS Publish API): An optional external API exposed by the 5GMS AS (350) that is used when a 5GMS AS (350) in a trusted DN is selected to receive / host content for a streaming service.
[0069] M3 (Internal): An internal API used to exchange information for hosting content in the 5GMS AS (350) within a trusted DN.
[0070] M4 (Media Streaming API): An API exposed by the 5GMS AS (350) to the media streamer (322) for streaming media content.
[0071] M5 (Media Session Handling API): An API exposed by the 5GMS AF (340) to the Media Session Handler (321) for media session handling, control and support, including appropriate security mechanisms (e.g., authentication and authorization and QoE metric reporting).
[0072] M6 (UE Media Session Handling API): An API that can be exposed by the Media Session Handler (321) to 5GMS aware applications to take advantage of 5GMS capabilities.
[0073] M7 (UE Media Streamer API): An API that can be exposed by the Media Streamer (322) to 5G MS-aware applications (310) and Media Session Handlers (321) for utilizing the Media Streamer (322), including configuration of QoE metrics to be measured and recorded and collection of metric measurement logs.
[0074] M8 (Application API): An application interface used for information exchange between a 5GMS-aware application (310) and a 5GMS application provider (330), for example to provide service access information to the 5GMS-aware application.
[0075] 4 shows a block diagram of an edge computing system (400) having an architecture for enabling edge applications. The edge computing system (400) includes an edge data network (410), an edge configuration server (490), a core network (430), and a UE (represented by UE (440)) coupled together as shown in FIG.
[0076] In some examples, the edge data network (410) is a local data network. The edge data network (EDN) (410) may include one or more edge application servers (485) and one or more edge enabler servers (480). The edge configuration server (490) may provide configuration related to the edge enabler server (EES) (480), including, for example, details of the edge data network (410) that hosts the edge enabler server (480). The UE (440) may include an application client (441) and an edge enabler client (470). The edge application server (485), edge enabler server (480), and edge configuration server (490) may interact with the core network (430).
[0077] The various components within the edge computing system (400) are suitably configured with functionality to enable edge applications.
[0078] In some examples, the edge enabler server 480 can provide necessary support functions for the edge application server 485 and the edge enabler client 470. For example, the edge enabler server 480 can provide configuration information to the edge enabler client 470 to enable the exchange of application data traffic with the edge application server 485. In addition, the edge enabler server 480 can support API caller and API exposure functions. The edge enabler server 480 can also interact with the core network 430 to access network function capabilities directly (e.g., via a PCF) or indirectly (e.g., via a service capability exposure function (SCEF) / network exposure function (NEF) / SCEF+NEF). In some examples, the edge enabler server 480 can support application context transfer functions. Additionally, the edge enabler server (480) can support the external exposure of the 3GPP network and the service capability to the edge application server, for example on EDGE-3 in FIG. 4. In some examples, the edge enabler server (480) can support the functionality of registering (e.g., registering, updating, and deregistering) the edge enabler client (470) and the edge application server (485). Additionally, the edge enabler server (480) can support the functionality of triggering edge application server (EAS) instantiation on demand.
[0079] In some examples, an edge enabler client (EEC) (470) can provide necessary support functions to the application client (441). In some examples, the edge enabler client (EEC) (470) can obtain and provide configuration information to enable the exchange of application data traffic between the application client (441) and the edge application server (485). Additionally, the edge enabler client (EEC) (470) can discover available edge application servers (485) within the edge data network (410).
[0080] An edge configuration server (ECS) (490) can provide support functions necessary for the edge enabler client (470) to connect with the edge enabler server (480). In some examples, the edge configuration server (490) can provide edge configuration information to the edge enabler client (470). The edge configuration information can include information for the edge enabler client (470) to connect to the edge enabler server (480) (e.g., service area information applicable to a local area data network (LADN)) and information for establishing a connection with the edge enabler server (480) (e.g., a URI).
[0081] Note that the edge configuration server (490) can be deployed in the MNO domain or can be deployed in a third party domain by the service provider.
[0082] The edge configuration server (490) can support registration (i.e., register, update, and de-register) functions of the edge enabler server (480). The edge configuration server (490) can support API caller and API publishing functions. The edge configuration server (490) can interact with the core network (430) to access network function capabilities directly (e.g., via PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF).
[0083] The application client (441) can be an application that resides in the UE 440 and can perform client functions.
[0084] An edge application server (EAS) (485) is an application server that resides in the edge data network (410) and can perform server functions. In some examples, an application client (441) can connect to the edge application server (485) to utilize the services of an application with the benefits of edge computing.
[0085] In some examples, the server functionality of the application is only available in the edge application server (485). In some examples, certain server functionality is available in both the edge and the cloud, such as other application servers, such as the edge application server (485) and application servers (not shown) that reside in the cloud, respectively. The server functionality provided by the edge application server (485) and its cloud application server counterparts may be the same or different. When the server functionality is different, the application data traffic exchanged with the application clients may also be different.
[0086] The edge application server (485) may utilize the core network capabilities in various ways. In one example, if the edge application server (485) is an entity trusted by the core network (430), the edge application server (485) may directly call the core network capability API. In another example, the edge application server (485) may call the core network capability through the edge enabler server (480). In another example, the edge application server (485) may call the core network capability through a capability exposure function, i.e., a SCEF or a NEF.
[0087] FIG. 4 also illustrates reference points between functional elements within the edge computing system (400), such as reference points EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, and EDGE-8 in FIG. 4.
[0088] In some examples, reference point EDGE-1 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between the EES (480) and the EEC (470). Reference point EDGE-1 may support a variety of functions. In one example, reference point EDGE-1 is configured to support registration and deregistration of edge enabler clients to an edge enabler server. In another example, reference point EDGE-1 is configured to support retrieval and provision of edge application server configuration information. In another example, reference point EDGE-1 is configured to support discovery of available edge application servers in the edge data network (410).
[0089] In some examples, reference point EDGE-2 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between the edge enabler server and the core network. In some examples, reference point EDGE-2 is configured to support access to core network functions and APIs for retrieval of network capability information.
[0090] In some examples, the reference point EDGE-3 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between the EES (480) and the EAS (485). In one example, the reference point EDGE-3 is configured to support registration of an edge application server with availability information (e.g., time constraints, location constraints). In another example, the reference point EDGE-3 is configured to support deregistration of an edge application server (485) from the edge enabler server (480). In another example, the reference point EDGE-3 is configured to support discovery of target edge application server information to support application context transfer. In another example, the reference point EDGE-3 is configured to support providing access to network capability information (e.g., location information, QoS related information). In another example, the reference point EDGE-3 is configured to support requesting establishment of a data session between an application client, such as the application client (441), and the EAS (485) with a particular QoS.
[0091] In some examples, reference point EDGE-4 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between an edge configuration server (490) and an edge enabler client (470). In some examples, reference point EDGE-4 is configured to support providing edge configuration information to edge enabler client (470).
[0092] In some examples, reference point EDGE-5 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between application clients (441) and edge enabler clients (470).
[0093] In some examples, reference point EDGE-6 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between the edge configuration server (490) and the edge enabler server (480). In some examples, reference point EDGE-6 is configured to support registration of edge enabler server information with the edge configuration server (490).
[0094] In some examples, reference point EDGE-7 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between edge application servers (485) and the core network (430). In some examples, reference point EDGE-7 is configured to support access to core network functions and APIs for retrieval of network capability information.
[0095] In some examples, reference point EDGE-8 may include appropriate interface components (hardware components, software components, etc.) that enable interaction between the edge configuration server (490) and the core network (430). In some examples, reference point EDGE-8 is configured to support access to core network functions and APIs for retrieval of network capability information.
[0096] Certain aspects of the present disclosure provide a media streaming system with edge computing capabilities.
[0097] 5 illustrates a block diagram of an edge-enabled media streaming system (500) according to some embodiments of the present disclosure. The edge-enabled media streaming system (500) includes components that are similarly configured as components in the 5GMS system (300) and the edge computing system (400). For example, the 5GMS-aware application (510) is equivalent to the 5GMS-aware application (310), the media session handler (521) is equivalent to the media session handler (321), the media streamer (522) is equivalent to the media streamer (322), the 5GMS client (520) is equivalent to the 5GMS client (320), the 5GMS AF (540) is equivalent to the 5GMS AF (340), the 5GMS AS (550) is equivalent to the 5GMS AF (340), and the 5GMS AS (550) is equivalent to the 5GMS AF (340). AF (350), 5GMS application provider (530) is equivalent to 5GMS application provider (530), NEF (561) is equivalent to NEF (361), PCF (562) is equivalent to PCF (362), EEC (570) is equivalent to EEC (470), EES (580) is equivalent to EAS (485), EAS (585) is equivalent to EAS (485), ECS (590) is equivalent to ECS (490), DN (502) is equivalent to DN (302), and includes edge data network. M1 to M8 in FIG. 5 are equivalent to M1 to M8 in FIG. 3, respectively, and EDGE-1, EDGE-3 to EDGE-6 in FIG. 5 are equivalent to EDGE-1, EDGE-3 to EDGE-6 in FIG. 4, respectively. A description of these components is provided above and is omitted here for clarity.
[0098] In the example of FIG. 5, the EES (580) can discover multiple EASs (585), and the EASs (585) are considered separate entities from the 5GMS AS (550). In some examples, the EASs (585) can instantiate the 5GMS AS (550). The 5GMS AF (540) includes the functionality of an edge enabler server, for example, the 5GMS AF (540) can include an EES (580). The 5GMS AF (540) can discover and select the EAS (585) using the EES (580). The EASs (585) can instantiate the 5GMS AS (550). The 5GMS AS (550) can then execute processing on the corresponding hardware defined by the EES (580).
[0099] Further referring to FIG. 5, in some examples, the 5GMS AF (540) includes an EES (580), such that the 5GMS AF (540) can support EDGE-2 as part of the EES (580).
[0100] In some examples, the EAS (585) can support an EDGE-7. In some examples, an EDGE-3 can be configured to provide media processing support.
[0101] In some examples, M1 can be configured to include further information. In one example, the 5GMS AF (540) can use M1 to indicate support for an edge enabler server (EES) and an edge application server (EAS) to the 5GMS application provider 530, thus informing the 5GMS application provider 530 that the data network (502) is edge-enabled. In another example, M1 can expose further information related to the EES (580) to the 5GMS application provider (530). For example, the further information can indicate the current availability of the EES (580).
[0102] In some examples, M6 can be configured to include additional information. In one example, the media session handler (521) can use M6 to indicate that the media session handler (521) supports the functionality of an EEC. For example, the media session handler (521) includes an EEC (570). In another example, M6 can be configured to include information about the EDGE-5, such as the address of the EDGE-5, etc.
[0103] 6 shows a diagram illustrating a process flow (600) for executing a media service in an edge-enabled media streaming system (500) according to some embodiments of the present disclosure. In the example of FIG. 6, the media service is requested by a 5GMS application provider (530).
[0104] At (S610), the 5GMS application provider (530) sends a request to the 5GMS AF (540) to request the provision of a particular media service from the 5GMS AF (540). In some examples, the 5GMS application provider (530) sends a request to the 5GMS AF (540). The request may include usage features, capabilities, and detailed configurations for the particular media service. In one example, the request may include information that can be used to determine the location of the user device.
[0105] At (S620), the 5GMS AF (540) can discover an available EAS (585) through the functionality of an edge enabler server. For example, the 5GMS AF (540) can include an EES (580), and the EES (580) can send a discovery request to the EAS (585) to discover an available EAS (585). In some examples, the discovery request can include a location of the user device. In one example, the location of the user device is from the request. In another example, the EES (580) can detect the location of the user device, for example, from a 3GPP system.
[0106] At (S630), the available EASs (585) can each respond to the discovery request with a discovery acknowledgement to the EES (580). The discovery acknowledgement from the available EASs (585) can include information of the available EASs (585). The EES (580) and the 5GMS AF (540) can receive the information of the available EASs (585).
[0107] At (S640), the 5GMS AF (540) can select one of the available EASs (585) and send a request to the selected EAS (585) to instantiate an application server such as a 5GMS AS (550) for providing a particular media service. In some examples, steps (S620)-(S630) can be optional, and the EES (580) can determine the available EASs (585) and select one of the available EASs (585) according to previously stored information of the EASs (585), such as the capabilities, location, and other suitable information of the EASs (585).
[0108] At (S650), the EAS (585) can instantiate an application server and send an acknowledgement about the instantiated application server. The acknowledgement can include information of the instantiated application server, called the 5GMS AS (550).
[0109] At (S660), based on the information of the 5GMS AS (550), the 5GMS AF (540) can send a request to the 5GMS AS (550) to perform a specific media service.
[0110] At (S670), the 5GMS AS (550) executes the specific media service and sends an acknowledgement to the 5GMS AF (540) for confirmation.
[0111] At (S680), the 5GMS AF (540) can send a confirmation response to the 5GMS application provider (530) to confirm that the media service is running.
[0112] At (S690), a media streaming session begins.
[0113] 7 shows a diagram illustrating a process flow (700) for executing a media service in an edge-enabled media streaming system (500) according to some embodiments of the present disclosure. In FIG. 7, a media service is requested by a 5GMS-aware application (510).
[0114] At (S710), a 5G MS-aware application (510) can send a request to a media session handler (MSH) (521) to request the provision of a particular media service.
[0115] At (S715), the MSH (521) can send a request to the 5GMS AF (540) for a particular media service through the EEC (570). For example, the request is sent from the EEC (570) to the EES (580) by EDGE-1. The request includes information about the UE (501), such as the location of the UE (501), EAS discovery filters (e.g., capabilities), ESA category (e.g., gaming application, etc.), etc.
[0116] At (S720), the 5GMS AF (540) can discover an available EAS. For example, the EES (580) in the 5GMS AF (540) can send a discovery request. For example, the EES (580) can send a discovery request to the EAS (585) to discover an available EAS (585). In some examples, the discovery request can include the location of the UE (501). In one example, the location of the UE (501) is received from the EEC (570). In another example, the EES (580) can detect the location of the UE (501), for example, from a 3GPP system.
[0117] At (S725), the available EASs (585) can each respond to the discovery request with a discovery acknowledgement to the EES (580). The discovery acknowledgement from the available EASs (585) can include information of the available EASs (585). The EES (580) and the 5GMS AF (540) can receive the information of the available EASs (585).
[0118] At (S730), the 5GMS AF (540) can select one of the available EASs (585) and send a request to the selected EAS (585) to instantiate an application server such as a 5GMS AS (550) for providing a particular media service. Note that in some examples, steps (S720)-(S725) can be optional. The EES (580) can include information of previously stored EASs (585) and can determine available EASs (585) and select one of the available EASs (585) based on the information of the previously stored EASs (585).
[0119] At (S735), the EAS (585) can instantiate an application server and send an acknowledgement about the instantiated application server. The acknowledgement can include information of the instantiated application server, called the 5GMS AS (550).
[0120] At (S740), based on the information of the 5GMS AS (550), the 5GMS AF (540) can send a request to the 5GMS AS (550) to perform a specific media service.
[0121] At (S745), the 5GMS AS (550) executes the specific media service and sends an acknowledgement to the 5GMS AF (540) for confirmation.
[0122] At (S750), the 5GMS AF (540) can send a confirmation response of the media service to the MSH (521), and the MSH (521) can then send a confirmation response of the media service to the 5GMS-aware application (510).
[0123] At (S755), a media streaming session begins.
[0124] As shown in Figures 5-7, the edge-enabled media streaming system (500) can use some existing application programming interfaces in 5GMS systems and edge computing systems to execute media services on the edge network. Furthermore, some application programming interfaces such as M1, M6, EDGE-3, etc. are extended to support more information required to utilize edge computing. The ability to discover various edge application servers and select one of the edge application servers can be based on capabilities, location, and possibly other information. Furthermore, media services can be requested by applications on the user device or by application (service) providers.
[0125] 8 shows a flow chart outlining a process (800) according to one embodiment of the present disclosure. In one example, the process (800) is performed by a processing circuit of a user device, such as a UE (501) in an edge-enabled media streaming system (500). In some embodiments, the process (800) is implemented with software instructions, such that the processing circuit executes the software instructions to cause the processing circuit to perform the process (800). The process begins at (S801) and proceeds to (S810).
[0126] At (S810), a request is sent from a media service client of a user device to an application function of a data network. The request can request an edge-enabled media service.
[0127] In one example, the request is sent by a media service client in response to a media request by a media application in a user device.
[0128] In some examples, the request is sent via an interface of an edge enabler client of the media service client with an edge enabler server of the application functionality.
[0129] At (S820), an acknowledgement is received from the application function along with information of the application server instantiated by the edge application server.
[0130] In some examples, the edge application server is determined by the edge enabler server. In one example, the edge enabler server determines the edge application server based on filtering information such as the type of media stream in the request, capability requirements, feature requirements, etc. In another example, the edge enabler server determines the edge application server based on location information of the user device and the location of the edge application server. In another example, the edge enabler server determines the edge application server based on an acknowledgement from the edge application server in response to the discovery request from the edge enabler server.
[0131] In some examples, the application function requests an application server to instantiate an application server and requests the application server to provide a media service.
[0132] At (S830), media streaming is performed based on the information of the application server.Then, the process proceeds to (S899) and ends.
[0133] The process 800 may be adapted as appropriate. Steps within the process 800 may be modified and / or omitted. Additional steps may be added. Any suitable order of execution may be used.
[0134] 9 shows a flow chart outlining a process (900) according to one embodiment of the present disclosure. In one example, the process (900) is performed by a processing circuit of an application functional entity in a cloud, such as the 5GMS AF (540) in the edge-enabled media streaming system (500). In some embodiments, the process (900) is implemented with software instructions, such that the processing circuit executes the process (900) when the processing circuit executes the software instructions. The process begins at (S901) and proceeds to (S910).
[0135] At (S910), an application function in a data network receives a request for a media service. In some examples, the request is from an application provider in the data network, such as process flow (600) in Figure 6. In some examples, the request is from a user device, such as process flow (700) in Figure 7.
[0136] At (S920), the application function requests the edge application server to instantiate an application server for providing the media service. In some examples, the edge enabler server in the application function determines the edge application server. In one example, the edge enabler server in the application function determines the edge application server based on filtering information such as the type of media stream, capability requirements, feature requirements, etc. in the request. In another example, the edge enabler server in the application function determines the edge application server based on location information of the user device and the location of the edge application server. In another example, the edge enabler server in the application function determines the edge application server based on an acknowledgement response from the edge application server in response to the discovery request from the edge enabler server.
[0137] In some examples, the application function requests an edge application server to instantiate an application server, and further, the application function requests an application server to provide a media service.
[0138] At (S930), the application function responds to the request with the application server's information. The process then proceeds to (S999) and ends.
[0139] The process 900 may be adapted as appropriate. Steps within the process 900 may be modified and / or omitted. Additional steps may be added. Any suitable order of execution may be used.
[0140] The techniques described above can be implemented as computer software using computer readable instructions and physically stored on one or more computer readable mediums.
[0141] The methods and embodiments in this disclosure may be used separately or combined in any order. Furthermore, each of the methods (or embodiments), functions or tasks may be performed by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program stored on a non-transitory computer-readable medium.
[0142] The techniques described above can be implemented as computer software using computer readable instructions and physically stored on one or more computer readable media. For example, Figure 10 illustrates a computer system (1000) suitable for implementing certain embodiments of the disclosed subject matter.
[0143] Computer software may be coded using any suitable machine code or computer language, and may be subject to assembly, compilation, linking, or similar mechanisms to produce code containing instructions that can be executed by one or more computer central processing units (CPUs), graphics processing units (GPUs), or the like, either directly, or through interpretation, microcode execution.
[0144] The instructions may be executed in various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smart phones, gaming devices, Internet of Things, etc.
[0145] 10 for computer system (1000) are exemplary in nature and are not intended to suggest any limitation as to the scope of use or functionality of the computer software implementing the embodiments of the present disclosure, nor should the arrangement of components be interpreted as having any dependency or requirement with respect to any one or combination of components shown in the exemplary embodiment of computer system (1000).
[0146] The computer system (1000) may include certain human interface input devices. Such human interface input devices may respond to input by one or more human users through, for example, tactile input (e.g., keystrokes, swipes, data glove movements), audio input (e.g., voice, clapping), visual input (e.g., gestures), olfactory input (not shown). Human interface devices may also be used to capture certain media that are not necessarily directly related to conscious human input, such as audio (e.g., speech, music, ambient sounds), images (e.g., scanned images, photographic images obtained from still image cameras), and video (e.g., two-dimensional video, three-dimensional video including stereoscopic video).
[0147] The input human interface devices may include one or more (only one of each is shown) of a keyboard (1001), a mouse (1002), a trackpad (1003), a touch screen (1010), a data glove (not shown), a joystick (1005), a microphone (1006), a scanner (1007), and a camera (1008).
[0148] The computer system (1000) may also include certain human interface output devices that may stimulate one or more of the senses of a human user, for example, through tactile output, sound, light, and smell / taste. Such human interface output devices may include haptic output devices (e.g., haptic feedback via a touch screen (1010), data gloves (not shown), or joystick (1005), although there may be haptic feedback devices that do not function as input devices), audio output devices (e.g., speakers (1009), headphones (not shown)), visual output devices (e.g., screens (1010) including CRT screens, LCD screens, plasma screens, OLED screens (each of which may or may not have touch screen input capability, each of which may or may not have haptic feedback capability, some of which may be capable of outputting two-dimensional visual output or three-dimensional output through means such as stereoscopic output), virtual reality glasses (not shown), holographic displays, and smoke tanks (not shown)), and printers (not shown).
[0149] The computer system (1000) may also include human accessible storage devices and their associated media, such as optical media (1021), including CD / DVD ROM / RW (1020) with CD / DVD or similar media (1021), thumb drives (1022), removable hard drives or solid state drives (1023), legacy magnetic media such as tape and floppy disks (not shown), specialized ROM / ASIC / PLD based devices such as security dongles (not shown), etc.
[0150] Those skilled in the art should also understand that the term "computer-readable medium" as used with respect to the subject matter disclosed herein does not encompass transmission media, carrier waves, or other transitory signals.
[0151] The computer system (1000) may also include an interface (1054) to one or more communication networks (1055). The networks may be, for example, wireless, wired, or optical. Furthermore, the networks may be local, wide area, metropolitan, vehicular and industrial, real-time, delay tolerant, and the like. Examples of networks include local area networks such as Ethernet, wireless LAN, cellular networks (including GSM, 3G, 4G, 5G, LTE, and the like), TV wired or wireless wide area digital networks (including cable TV, satellite TV, and terrestrial TV), vehicular and industrial (including CANBus), and the like. Certain networks typically require an external network interface adapter that is attached to a particular general-purpose data port or peripheral bus (1049) (e.g., a USB port of the computer system (1000) or the like), while other networks are typically integrated into the core of the computer system (1000) by attachment to a system bus (e.g., an Ethernet interface to a PC computer system or a cellular network interface to a smartphone computer system) as described below. Using any of these networks, the computer system (1000) can communicate with other entities. Such communications can be unidirectional receive-only (e.g., broadcast television), unidirectional transmit-only (e.g., a CANbus to a specific CANbus device), or bidirectional (e.g., to other computer systems using local or wide area digital networks). Specific protocols and protocol stacks can be used in these networks and those of the network interfaces, as described above.
[0152] The above human interface devices, human accessible storage devices and network interfaces may be attached to the core (1040) of the computer system (1000).
[0153] The core (1040) may include one or more central processing units (CPUs) (1041), graphics processing units (GPUs) (1042), dedicated programmable processing devices in the form of field programmable gate arrays (FPGAs) (1043), task specific hardware accelerators (1044), graphics adapters (1050), etc. These devices may be connected through a system bus (1048) along with read-only memory (ROM) (1045), random access memory (1046), internal mass storage (1047) such as internal non-user accessible hard drives, SSDs, etc. In some computer systems, the system bus (1048) may be accessible in the form of one or more physical plugs to allow expansion with additional CPUs, GPUs, etc. Peripheral devices may be attached directly to the core's system bus (1048) or through a peripheral bus (1049). In one example, the screen (1010) can be connected to a graphics adapter (1050). Peripheral bus architectures include PCI, USB, etc.
[0154] The CPU (1041), GPU (1042), FPGA (1043) and accelerator (1044) can execute certain instructions that, in combination, can constitute the above-mentioned computer code. The computer code can be stored in ROM (1045) or RAM (1046). Temporary data can also be stored in RAM (1046), while persistent data, for example, can be stored in internal mass storage (1047). Rapid storage and retrieval from any of the memory devices is made possible through the use of cache memory, which can be closely associated with one or more of the CPU (1041), GPU (1042), mass storage (1047), ROM (1045), RAM (1046), etc.
[0155] The computer-readable medium can bear computer code for performing various computer-implemented operations. The medium and computer code can be those specially designed and constructed for the purposes of the present disclosure, or they can be of the kind well known and available to those skilled in the computer software arts.
[0156] By way of example and not limitation, a computer system having the architecture (1000), and in particular the core (1040), can provide functionality as a result of a processor (including a CPU, GPU, FPGA, accelerator, etc.) executing software embodied in one or more tangible computer-readable media. Such computer-readable media can be media associated with mass storage accessible to a user as described above, as well as the core's (1040) specific storage of a non-transitory nature, such as mass storage (1047) within the core or ROM (1045). Software implementing various embodiments of the present disclosure can be stored in such devices and executed by the core (1040). The computer-readable media can include one or more memory devices or chips according to particular needs. The software can include defining data structures stored in RAM (1046) and modifying such data structures according to processes defined by the software, causing the core (1040) and in particular the processor therein (including a CPU, GPU, FPGA, etc.) to execute particular processes or particular portions of particular processes described herein. Additionally or alternatively, the computer system may provide functionality as a result of logic hardwired or otherwise embodied in circuitry (e.g., accelerator (1044)), which may operate in place of or in conjunction with software to perform particular processes or particular portions of particular processes described herein. References to software may include logic, and vice versa, as appropriate. References to computer-readable media may include circuitry (e.g., integrated circuits (ICs)) that store software for execution, circuitry embodying logic for execution, or both, as appropriate. The present disclosure encompasses any appropriate combination of hardware and software.
[0157] While this disclosure describes several exemplary embodiments, there are alterations, permutations, and various substitute equivalents that fall within the scope of this disclosure. It will thus be recognized that those skilled in the art will be able to devise many systems and methods that, although not explicitly shown or described herein, embody the principles of the present disclosure and are therefore within the spirit and scope of the present disclosure.
Claims
1. 1. A method for 5G media streaming performed by a user device, comprising: Sending a request from a 5G Media Streaming (5GMS) service client of the user device to a 5G MS application function of a 5G data network, the request including filtering information including capabilities of an edge application server, and requesting a 5G Media Streaming (5GMS) service; sending a discovery request to one or more edge application servers, and if a discovery acknowledgement is received from an available edge application server among the one or more edge application servers, receiving an acknowledgement from the 5GMS application function together with information of a 5GMS application server instantiated by an edge application server selected from the available edge application servers, the edge application server being selected based on the capabilities of the edge application server; performing the 5G media streaming based on the information of the 5G MS application server; The method includes:
2. 10. The method of claim 1, further comprising sending the request in response to a media request from a 5G MS-aware application in the user device.
3. The method according to claim 1 or 2, further comprising the step of sending the request via an edge enabler client interface of the 5GMS service client to an edge enabler server in the 5GMS application function.
4. The method of claim 3 , wherein the edge application server is selected by the edge enabler server.
5. The method of claim 4 , wherein the edge enabler server selects an edge application server further based on a location of the user device and a location of the edge application server.
6. The method of claim 4 , wherein the edge enabler server selects the edge application server based on an acknowledgement from the edge application server in response to a discovery request from the edge enabler server.
7. 7. A method according to claim 4, wherein the 5GMS application function requests the edge application server to instantiate the 5GMS application server and requests the 5GMS application server to provide the 5GMS service.
8. 1. An apparatus including a processing circuit, Apparatus, wherein the processing circuitry is configured to perform a method according to any one of claims 1 to 7.
9. A program causing a processor to carry out the method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Content supply device, content supply method, program, terminal device, and content supply system
JP2015002513A
Framework for computing in radio access network (RAN)
US20200404069A1
