Method for network-side and client-side activation of edge servers in a 5G media streaming architecture

Abstract

The present invention provides a computer-implemented method for provisioning edge resources, performed by a computing device in a 5G media streaming architecture. The computing device receives a new edge resource configuration request from a first device in relation to a 5G media streaming session. The computing device determines an edge management mode of the new edge resource configuration request. The computing device allocates edge resources for the 5G media streaming session based on the edge management mode, which can be driven by an application provider on the network side or by a media session handler on the client side. The computing device returns a response to the first device, the response including information of the allocated edge resources for the new edge resource configuration request.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority to U.S. Provisional Application No. 63 / 325,518, entitled "Method for Network-Side and Client-Side Activation of the Edge Servers in 5G Media Streaming Architecture," filed March 30, 2022, and is a continuation of and claims priority to U.S. Patent Application No. 18 / 120,878, entitled "Method for Network-Side and Client Side Activation of the Edge Servers in 5G Media Streaming Architecture," filed March 13, 2023, all of which are incorporated by reference in their entireties herein.

[0002] [Technical field] The disclosed implementations relate generally to a 5G media streaming (5GMS) architecture, and in particular to a method for activating an edge server in a 5G media streaming architecture using a 5GMS M1 provisioning interface. [Background technology]

[0003] The current 5G edge architecture defined in 3GPP TS 23.558 only defines the discovery of edge applications by application clients. The 5G media streaming architecture defined in 3GPP TS 26.501 has recently added, as an extension, the use of the TS 23.558 edge architecture as part of the 5G MS architecture. However, the actual method of providing such services is not currently defined. Summary of the Invention

[0004] According to some implementations of the present invention, a computer-implemented method for provisioning edge resources is performed by a computing device in a 5G media streaming (5GMS) architecture. The method includes receiving a new edge resource configuration request from a first device in association with a 5G media streaming session; determining an edge management mode of the new edge resource configuration request; allocating edge resources for the 5G media streaming session based on the edge management mode; and returning a response to the first device, the response including information of the allocated edge resources for the new edge resource configuration request.

[0005] According to some implementations of the present invention, a computing device comprises one or more processors; a memory; and one or more programs stored in the memory for executing the above-described computer-implemented method for provisioning edge resources.

[0006] According to some implementations of the present invention, a non-transitory computer-readable storage medium stores one or more programs configured for execution by a computing device including one or more processors and a memory storing one or more programs for performing the above-described computer-implemented method for provisioning edge resources. [Brief description of the drawings]

[0007] The foregoing implementations, as well as additional implementations, of the present invention will be more clearly understood as a result of the following detailed description of various aspects of the invention in conjunction with the drawings, in which like reference numerals refer to corresponding parts throughout the several views of the drawings. [Figure 1] FIG. 1 is a block diagram of an environment in which the methods, apparatus, and systems described herein may be implemented, according to an embodiment. [Diagram 2] FIG. 2 is a block diagram of example components of one or more devices of FIG. [Diagram 3] FIG. 3 is a block diagram of a 5G media streaming architecture with edge computing extensions for media uplink streaming, according to an embodiment. [Figure 4] FIG. 4 is a block diagram of a 5G media streaming architecture with edge computing extensions for media downlink streaming, according to an embodiment. [Diagram 5] FIG. 5 is a table of operations supported by the edge resource API, according to an embodiment. [Figure 6] FIG. 6 is a table of edge resource configuration property definitions, according to an embodiment. [Figure 7] FIG. 7 is a flowchart of a method for provisioning edge resources according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Figure 1 is a block 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 includes a user device 110, a platform 120, and a network 130. The devices of the environment 100 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0009] User device 110 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information related to platform 120. For example, user device 110 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smartphone, a wireless phone, etc.), a wearable device (e.g., smart glasses or a smart watch), or a similar device. User device 110 can receive and / or transmit information from platform 120.

[0010] Platform 120 includes one or more devices, as described elsewhere herein. In some implementations, platform 120 may include a cloud server or a group of cloud servers. In some implementations, platform 120 may be designed to be modular so that software components can be swapped in or out depending on particular needs. As such, platform 120 may be easily and / or quickly reconfigured for different uses.

[0011] In some implementations, as shown, platform 120 may be hosted in a cloud computing environment 122. Notably, although the implementations described herein describe platform 120 as being hosted within cloud computing environment 122, platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0012] Cloud computing environment 122 can provide services such as computing, software, data access, storage, etc., without requiring end-user (e.g., user device 110) knowledge of the physical location and configuration of the system(s) and / or device(s) hosting platform 120. As shown, cloud computing environment 122 can include a group of computing resources 124 (collectively referred to as “computing resources 124” and individually referred to as “computing resource 124”).

[0013] Computing resources 124 include one or more personal computers, workstation computers, servers, or other types of computational and / or communication devices required to host platform 120. Cloud resources 124 may include compute instances running within computing resources 124, storage devices provided within computing resources 124, data transfer devices provided by computing resources 124, etc. In some implementations, computing resources 124 may communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0014] As further shown in FIG. 1, computing resources 124 include a group of cloud resources, such as one or more applications (“APP”) 124-1, one or more virtual machines (“VM”) 124-2, a virtual storage device (“VS”) 124-3, and one or more hypervisors (“HYP”) 124-4.

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

[0016] Virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 124-2 may be either a system virtual machine or a process virtual machine, depending on the extent to which virtual machine 124-2 uses and corresponds to an actual machine. A system virtual machine can provide a complete system platform that supports the execution of a complete operating system ("OS"). A process virtual machine can execute a single program and support a single process. In some implementations, virtual machine 124-2 can run on behalf of a user (e.g., user device 110) and manage the infrastructure of cloud computing environment 122, such as data management, synchronization, or long-term data transfer.

[0017] Virtual storage 124-3 includes one or more storage systems and / or one or more devices that use virtualization techniques within storage systems or computing resources 124. In some implementations, within the context of storage systems, types of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to the specific physical storage or heterogeneous structure. This separation allows storage system administrators flexibility in how they manage storage for end users. File virtualization may eliminate the dependency between data accessed at the file level and the location where the file is physically stored. This may enable optimization of storage usage, server consolidation, and / or performance of non-destructive file migration.

[0018] The hypervisor 124-4 may provide hardware virtualization technology that allows multiple operating systems (e.g., "guest operating systems") to run simultaneously on a host computer, such as the computing resource 124. The 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 different operating systems may share virtualized hardware resources.

[0019] Network 130 may include one or more wired and / or wireless networks. For example, network 130 may include a cellular network (e.g., a fifth generation (5G) network, a long term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad-hoc network, an intranet, the Internet, a fiber optic based network, etc., and / or a combination of these or other types of networks.

[0020] The number and arrangement of devices and networks shown in Figure 1 are provided as an example. In some implementations, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks in a different arrangement than those shown in Figure 1. Furthermore, two or more devices shown in Figure 1 may be implemented within a single device, or a single device shown in Figure 1 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices (e.g., one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.

[0021] Figure 2 is a block diagram of example 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 240, input components 250, output components 260, and a communication interface 270.

[0022] The bus 210 includes components that enable communication between the components of the device 200. The processor 220 is implemented in hardware, firmware, or a combination of hardware and software. The processor 220 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other type of processing component. In some implementations, the processor 220 includes one or more processors that can be programmed to perform functions. The memory 230 includes 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 for use by the processor 220.

[0023] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, storage component 240 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, and / or solid state disks), compact disks (CDs), digital versatile disks (DVDs), floppy disks, cartridges, magnetic tapes, and / or other types of non-transitory computer readable media along with corresponding drives.

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

[0025] Communications interface 270 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communications interface 270 may enable device 200 to receive information from and / or provide information to other devices. For example, communications interface 270 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

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

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

[0028] The number and arrangement of components shown in Figure 2 are provided as an example. In some implementations, device 200 may include additional, fewer, different, or differently arranged components than those shown in Figure 2. Additionally or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions that are described as being performed by another set of components of device 200.

[0029] A 5G Media Streaming (5GMS) system may be an assembly of application functions, application servers, and interfaces from the 5G Media Streaming Architecture that support either downlink or uplink media streaming services, or both. A 5GMS application provider (e.g., a streaming service providing website) may include a party that interacts with the functions of the 5GMS system and supports 5GMS-aware applications that interact with the functions of the 5GMS system. A 5GMS-aware application (e.g., an application running on a mobile phone) may refer to an application in a user equipment (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.

[0030] A 5GMSd client may 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 through a well-defined interface / API. A 5GMSu client may refer to an originator of a 5GMSu service that can be accessed through a well-defined interface / API. A 5GMSu media streamer may refer to a UE function that enables uplink delivery of streaming media content to an application server (AS) function of a 5GMS application provider and interacts with both 5GMSu aware applications for media capture and subsequent streaming and a media session handler for media session control.

[0031] A dynamic policy may refer to a dynamic policy and charging control (PCC) rule for an uplink or downlink application flow during a media session. An egest session may refer to an uplink media streaming session from a 5GMS AS to a 5GMSu application provider. An ingest session may refer to a session for uploading media content to a 5GMSd AS. A policy template can refer to a collection of (semi-static) policy 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 the desired policy template 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 point 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 point to a pointer (e.g., in the form of a URL) that defines an entry point for an uplink media streaming session. A presentation entry can point to a document or a pointer to a document that defines an application presentation, such as an HTML5 document.

[0032] A provisioning session may refer to a data structure provided at an interface (M1d) by a 5GMSd application provider that configures 5GMSd functionality related to a set of 5GMSd-aware applications. A 5GMSd media player may refer to a UE function that allows the playback and rendering of media presentations based on media playback entries and exposes some basic controls such as play, pause, seek, stop to 5GMSd-aware applications. Server access information may refer to a set of parameters and addresses (including 5GMSd AF addresses and 5GMSd AS addresses) required to activate the reception of a streaming session. Service and content discovery may refer to functionality and procedures provided by a 5GMSd application provider to a 5GMS-aware application that allows an end user to discover available streaming services and content offerings and select a specific service or content item for access. A service announcement may refer to a procedure that takes place between a 5GMS-aware application and a 5GMS application provider so that the 5GMS-aware application can obtain 5GMS service access information directly or in the form of a reference to that information.

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

[0034] 3 is a block diagram of a 5G media streaming architecture 300 with edge computing extensions for media uplink streaming, according to an embodiment. A 5GMSu application provider 301 may use 5GMSu for uplink streaming services. The 5GMSu application provider 301 may provide a 5GMSu-aware application 302 on the UE 303 to utilize the 5GMSu client 304 and network functions using interfaces and APIs defined in 5GMSu. The 5GMSu AS may be an AS dedicated to 5G media uplink streaming. The 5GMSu client 304 may be a UE 303 internal function dedicated to 5G media uplink streaming.

[0035] The 5GMSu AF 306 and the 5GMSu AS 305 may be Data Network (DN) 307 functions. Functions in a trusted DN may be trusted by the operator's network. Thus, AFs in a trusted DN can communicate directly with all 5G core functions. Functions in external DNs can only communicate with the 5G core functions via the NEF 308 using link 320.

[0036] The media architecture 300 may connect the internal functions of the UE 303 and the related network functions for 5G media uplink streaming. Thus, the media architecture 300 may include several functions. For example, the 5GMSu client 304 on the UE 303 may be the originator of 5GMSu services that may be accessed through an interface / API. The 5GMSu client 304 may include two sub-functions, a media session handler 309 and a media streamer 310. The media session handler 309 may communicate with the 5GMSu AF06 to establish, control, and support the delivery of media sessions. The media session handler 309 may expose APIs that may be used by the 5GMSu-aware applications 302. The media streamer 310 may communicate with the 5GMSu AS 305 to stream media content, provide services to the 5GMSu-aware applications 302 for media capture and streaming, and provide services to the media session handler 309 for media session control. The 5GMSu aware application 302 can control the 5GMSu client 304 by implementing external application or content service provider specific logic and enabling the establishment of a media session. The 5GMSu AS 305 can host 5G media functions and can be implemented, for example, as a content delivery network (CDN). The 5GMSu application provider 301 can be an external application or content specific media function, for example media storage, consumption, transcoding, and redistribution, to stream media from the 5GMSu aware application 302 using 5GMSu. The 5GMSu AF 306 can provide various control functions to the media session handler 309 on the UE 303 and / or the 5GMSu application provider 301. The 5GMSu AF 306 can relay or initiate requests for different PCF 311 processing or interact with other network functions.

[0037] The media architecture 300 may include several different interfaces. For example, link 321 may relate to M1u, which may be a 5GMSu provisioning API exposed by the 5GMSu AF 306 to provision the use of the media architecture 300 and obtain feedback. Link 322 may relate to M2u, which may be a 5GMSu publishing API exposed by the 5GMSu AS 305 and used when a 5GMSu AS 305 in a trusted DN, such as DN 307, is selected to receive content for streaming services. Link 323 may relate to M3u, which may be an internal API used to exchange information for content hosting on the 5GMSu AS 305 in a trusted DN, such as DN 307. Link 324 may relate to M4u, which may be a media uplink streaming API exposed by the 5GMSu AS 323 to the media streamer 310 to stream media content. Link 325 may relate to M5u, which may be a media session processing API exposed by the 5GMSu AF 305 to the media session handler for media session processing, control and assistance, including appropriate security mechanisms, e.g., authorization and authentication. Link 326 may relate to M6u, which may be a UE 303 media session handling API exposed by the media session handler 309 to the 5GMSu aware application 302 to utilize the 5GMSu functionality. Link 327 may relate to M7u, which may be a UE media streamer API exposed by the media streamer 310 to the 5GMSu aware application 302 and the media session handler 309 to utilize the media streamer 310. Link 328 may relate to M8u, which may be an application API used for information exchange between the 5GMSu aware application 302 and the 5GMSu application provider 301, e.g., to provide service access information to the 5GMSu aware application 302.The UE 303 may also be implemented in a self-contained manner such that the interfaces M6u 326 and M7u 327 are not exposed.

[0038] 4 is a block diagram of a 5G media streaming architecture 400 with edge computing extensions for media downlink streaming, according to an embodiment. A 5GMSd application provider 401 can use 5GMSd for downlink streaming services. The 5GMSd application provider 401 can provide a 5GMSd aware application 402 on a UE 403 to utilize a 5GMSd client 404 and network functions using interfaces and APIs defined in 5GMSd. A 5GMSd AS can be an AS dedicated to 5G media downlink streaming. A 5GMSd client 404 can be a UE 403 internal function dedicated to 5G media downlink streaming.

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

[0040] The media architecture 400 may connect UE 403 internal functions and associated network functions for 5G media downlink streaming. Thus, the media architecture 400 may include several functions. For example, the 5GMSd client 404 on the UE 403 may be a receiver of 5GMSd services that may be accessed through an interface / API. The 5GMSd client 404 may include two sub-functions, a media session handler 409 and a media player 410. The media session handler 409 may communicate with the 5GMSd AF 406 to establish, control, and support the delivery of media sessions. The media session handler 409 may expose APIs that may be used by the 5GMSd-aware applications 402. The media player 410 may communicate with the 5GMSd AS 405 to stream media content and provide services to the 5GMSd-aware applications 402 for media playback and to the media session handler 409 for media session control. The 5GMSd aware application 402 can control the 5GMSd client 404 by implementing external application or content service provider specific logic and enabling the establishment of a media session. The 5GMSd AS 405 can host the 5G media functions. The 5GMSd application provisioning 401 can be external application or content specific media functions, e.g. media creation, encoding and formatting using the 5GMSd to stream media to the 5GMSd aware application 402. The 5GMSd AF 406 can provide various control functions to the media session handler 409 on the UE 403 and / or the 5GMSd application provider 401. The 5GMSd AF 406 can relay or initiate requests for different PCF 411 processing or interact with other network functions.

[0041] The media architecture 400 may include several different interfaces. For example, link 421 may relate to M1d, which may be a 5GMSd provisioning API exposed by the 5GMSd AF 406 to provision the use of the media architecture 400 and obtain feedback. Link 422 may relate to M2d, which may be a 5GMSd ingest API exposed by the 5GMSd AS 405 and used when a 5GMSd AS 405 in a trusted DN, such as DN 407, is selected to receive content for a streaming service. Link 423 may relate to M3d, which may be an internal API used to exchange information for content hosting on the 5GMSd AS 405 in a trusted DN, such as DN 407. Link 424 may relate to M4d, which may be a media downlink streaming API exposed by the 5GMSd AS 423 to the media player 410 to stream media content. Link 425 may relate to M5d, which may be a media session processing API exposed by the 5GMSd AF 405 to the media session handler for media session processing, control, and assistance, including appropriate security mechanisms, e.g., authorization and authentication. Link 426 may relate to M6d, which may be a UE 403 media session handling API exposed by the media session handler 409 to the 5GMSd-aware application 402 to utilize the 5GMSd functionality. Link 427 may relate to M7d, which may be a UE media player API exposed by the media player 410 to the 5GMSd-aware application 402 and the media session handler 409 to utilize the media player 410. Link 428 may relate to M8d, which may be an application API used for information exchange between the 5GMSd-aware application 402 and the 5GMSd application provider 401, for example, to provide service access information to the 5GMSd-aware application 402.

[0042] As shown in Figures 3 and 4, the 5G media streaming architecture with edge computing extension 300 (or 400) includes an edge enabler server (EES) 330 (or 430) in the 5GMSu AF 306 (or 5GMSd AF 406) and an edge application server (EAS) 335 (or 435) in the 5GMSu AF 305 (or 5GMSd AF 405), respectively. In some implementations, the EES 330 (or 430) is communicatively connected to the EAS 335 (or 435) via a link 333 (or 433). For example, the link 333 (or 433) may be an M1 interface.

[0043] The EES 330 (or 430) provides the necessary support functions for the EAS and Edge Enabler Client (EEC). In some implementations, the functions of the EES 330 (or 430) include, but are not limited to: a) provisioning of configuration information to the EEC, enabling exchange of application data traffic with the EAS 335 (or 435); b) providing API invoker and API publishing functions; c) interaction with the 3GPP core network to access network function capabilities directly (e.g., via PCF) or indirectly (i.e., SCEF / NEF / SCEF+NEF); d) publishing of events related to ACT; e) transfer of EEC context between EESs; e) support for external publishing of 3GPP network and service capabilities to the EAS(s) on EDGE-3; f) registration functions (i.e., registration, update, and deregistration) of the EEC(s) and the EAS(s); g) triggering of EAS instantiation on demand.

[0044] The EAS 335 (or 435) is an application server that resides in an edge data network (EDN) and performs server functions. An application client (AC) in the UE 303 (or 403) connects to the EAS 335 (435) or connects to utilize the services of an application that has edge computing benefits. In some implementations, the server functions of the application are available only as an EAS. In some other implementations, a particular server function is available both at the edge and in the cloud, as an EAS and an application server that resides in the cloud, respectively. The server functions provided by the EAS 335 (or 435) and its cloud application server counterpart may be the same or different, and when they are different, the application data traffic exchanged with the AC may also be different. In some implementations, the EAS 335 (or 435) consumes 3GPP core network capabilities in the following ways: a) invokes 3GPP core network capabilities via the edge enabler layer through the EES; b) directly invokes 3GPP core network function (e.g., PCF) APIs if it is an entity trusted by the 3GPP core network; c) invokes 3GPP core network capabilities through capability exposure functions, i.e., SCEF / NEF / SCEF+NEF.

[0045] Provisioning is the step that allows the 5GMS application provider 301 (or 401) to configure information about its edge processing requirements for a media streaming session. In some implementations, the following information is configurable by the 5GMS application provider via reference point M1: - Conditions for edge processing activation, e.g. traffic descriptors, application identifiers, geographic location of UE 303 (or 403), etc. - Choice of client-driven or application provider-driven management. - EAS profile information for each EAS 335 (or 435) that provides services to the application, such as service KPIs, geographic location, and service continuity support. - Application context relocation tolerances and requirements.

[0046] In case of client-driven edge processing, the edge-enabled 5GMS AF shall support sharing any necessary configuration information about edge processing with the media session handler via the service access information at reference point M5. This allows the EEC embedded in the media session handler to request edge processing for a streaming session from the EES embedded in the 5GMS AF, realizing reference point EDGE1. The service provisioning procedure supplies the information required by the UE to access the edge service. The procedure takes into account the UE's location, service requirements, service preferences, and connectivity information to provide the required configuration.

[0047] In some implementations, the application provider 301 (or 401) can provision a new EAS 335 (or 435) through the M1 interface. Using this interface, the application provider 301 (or 401) can create, update, and retrieve edge resource configurations using operations supported by the Edge Resource API as shown in FIG. 5, and the data sets used to support the operations are defined in FIG. 6.

[0048] The application provider 301 (or 401) instantiates a process for activating the EAS 335 (or 435) based on the received edge configuration resource request. The 5GMS application provider uses the HTTP POST method for this purpose, and the request message body shall include the EdgeResourcesConfiguration dataset. In some implementations, different processes may be initiated depending on the edge management mode, which may be network-side or client-side. Eligibility of the services provided by the EAS 335 (or 435) is based at least in part on the eligibility criteria properties. The process of discovering or instantiating one or more EAs is done through the EDGE API, and the process of updating the edge resource configuration is accomplished by including the activated edge server identifier.

[0049] The 5GMS AF306 (or 406), which is edge-enabled and supports EES functions, supports the following features: - Check for eligible new streams if all the conditions required in the eligibilityCriteria in the EdgeResourcesConfiguration dataset are met; - EDGE-1 API to support registration and provisioning of EEC capabilities and their discovery of EAS instances; - EDGE-3 API for EAS functionality of 5GMS AS instances; - EDGE-6 API for registering with ECS functionality; - EDGE-9 API for media session relocation; - Calculating resource allocation using the MnS-C interface.

[0050] A Media Session Handler (MSH) 309 (or 409) that is edge-aware and supports the EEC functionality supports the following functions: - Check for eligible new streams if all the conditions required in the eligibilityCriteria in the EdgeResourcesConfiguration dataset are met; - Call EES functions using EDGE-1 API; - Call ECS functions using EDGE-4 API; - Expose the EDGE-5 API to application clients.

[0051] In some implementations, if the edgeManagementMode property in the EdgeResourcesConfiguration request is set to EM_NETWORK_DRIVEN for network-driven edge resource management, the 5GMS AF 306 (or 406) is responsible for requesting and managing the required edge resources and handling EAS relocation for streaming sessions. For example, if the 5GMS AF 306 (or 406) does not meet the aforementioned edge enablement requirements, it can provide a response code for an unsuccessful request to the party submitting the request.

[0052] If not, the 5GMS AF 306 (or 406) may generate a resource identifier (e.g., edgeResourcesConfigurationId) representing the new edge resource configuration and provide it in a successful response to the requesting party. For each new eligible media stream, the 5GMS AF 306 (or 406) checks whether all conditions required in the eligibilityCriteria property are met. If the conditions in the easRequirements property are not met in the current 5GMS AS / EAS using the EDGE-3 API, the 5GMS AF 306 (or 406) searches or instantiates one or more 5GS AS / EAS that meet both the easRequirements property and the easRelocationRequirements property of the requested EdgeResourcesConfiguration dataset. If a new EAS is activated, the GMS AF 306 (or 406) may update the easId of the EdgeResourcesConfiguration with the EAS ID of the new EAS if the easIdFlag is "true".

[0053] If the edgeManagmentMode property of the EdgeResourcesConfiguration request is set to EM_APP_DRIVEN but the MSH does not meet the above requirements, the 5GMS AF306 (or 406) provides a response code for the failed request to the party submitting the request.

[0054] If not, the 5GMS AF 306 (or 406) generates a new resource identifier representing the new edge resource configuration and provides it to the requesting party in the successful response. In some implementations, the 5GMS AF 306 (or 406) only requests edge resources based on a request from an EEC instantiated in the MSH 309 (or 409). For each new eligible media stream, assuming all conditions required in the eligibilityCriteria are met, but if any conditions in the easRequirements property are not met in the current 5G MS AS / EAS using the EDGE-1 API, the MSH 309 (or 409) requests discovery of an eligible EAS via the EDGE-1 API for that EEC. In some embodiments, the MSH 309 (or 409) can provide the selected easId to the application provider via the M6 / EDGE-5 / EDGE-5 API.

[0055] In short, a method for activating an edge server based on an edge configuration request from another party is proposed using the 5G edge application API, which has two possible cases depending on the party submitting the request, which can be the 5G MS application provider 301 (or 401) or the UE 303 (or 403).

[0056] In the network-initiated case, i.e., when a request comes from the 5GMS application provider 301 (or 401), the 5GMS AF 306 (or 406) checks whether the new media streaming session meets the eligibility criteria and then communicates with the EAS 335 (or 435) using the edge application API. The 5GMS AF 306 (or 406) searches for currently active EAS profiles and then discovers or instantiates a new edge server depending on whether the profile meets the requested profile in the edge configuration request.

[0057] In the application-driven case, the client-side MSH 309 (or 409) first checks whether the new media streaming session meets the eligibility criteria, and then uses the edge application API via the Edge-1 interface. The 5GMS AF 306 (or 406) retrieves the currently active EAS profile, and then discovers or instantiates a new edge server depending on whether the profile meets the requested profile in the edge configuration request.

[0058] FIG. 7 is a flowchart of a method 800 for provisioning edge resources performed by a computing device acting as a 5GMS AF 306 (or 406) in a 5G media streaming (5GMS) architecture, according to an embodiment.

[0059] In operation 702, the computing device receives a new edge resource configuration request from a first device in association with a 5G media streaming session. As described above, the first device may be associated with a 5G MS application provider 301 (or 401) or a UE 303 (or 403).

[0060] At operation 704, the computing device determines an edge management mode of the new edge resource configuration request. At operation 706, the computing device allocates edge resources for the 5G media streaming session based on the edge management mode. At operation 708, the computing device returns a response to the first device, where the response includes information of the allocated edge resources for the new edge resource configuration request.

[0061] In some implementations, the edge management mode of the edge configuration request is a network-initiated mode, in which the computing device allocates edge resources for the streaming session based on the edge management mode by (i) generating a resource identifier for the new edge resource configuration request; (ii) identifying existing edge resources that satisfy one or more predetermined conditions in the new edge resource configuration request as edge resources allocated for the new edge resource configuration request; and (iii) including the resource identifier and information of the identified existing edge resources in a response to the first device.

[0062] In some implementations, the computing device determines that at least one of the predetermined conditions of the new edge resource configuration request is not satisfied by the existing edge resource. In this case, the computing device then instantiates a new edge resource that satisfies the predetermined condition for the new edge resource configuration request, and includes information of the newly instantiated edge resource in the response to the first device.

[0063] In some implementations, the edge management mode of the edge configuration request is an application-driven mode, in which the computing device allocates edge resources for the streaming session based on the edge management mode by (i) generating a resource identifier for the new edge resource configuration request; and upon receiving a second request from the client device: (ii) identifying existing edge resources that satisfy one or more predetermined conditions of the new edge resource configuration request as edge resources allocated for the new edge resource configuration request; and (iii) including the resource identifier and information of the identified existing edge resource in a response to the first device.

[0064] In some implementations, the computing device determines that at least one of the predetermined conditions of the new edge resource configuration request is not satisfied by the existing edge resource. In this case, the computing device then instantiates a new edge resource that satisfies the predetermined condition for the new edge resource configuration request and includes information of the newly instantiated edge resource in a response to the first device.

[0065] In some implementations, the existing edge resource identified in the response to the first device is based at least in part on a resource identifier in the second request from the client device.

[0066] In some implementations, the new edge resource configuration request includes an activation trigger element to restrict the edge resources allocated for the new edge resource configuration request to the media session. For example, the edge resources for the new edge resource configuration request to the media session may be allocated for a predetermined geographic region and / or for a predetermined time period.

[0067] Although specific embodiments have been described above, it will be understood that it is not intended to limit the invention to these specific embodiments. On the contrary, the invention includes alternatives, modifications, and equivalents that are within the spirit and scope of the appended claims. Numerous specific details are described in order to provide a thorough understanding of the subject matter presented herein. However, it will be apparent to those skilled in the art that the subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0068] Terms such as first, second, etc. may be used herein to describe various elements, but these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first ranking criterion can be referred to as a second ranking criterion, and similarly, a second ranking criterion can be referred to as a first ranking criterion, without departing from the scope of the present invention. Although the first ranking criterion and the second ranking criterion are both ranking criteria, they are not the same ranking criteria.

[0069] The terms used in the description of the invention herein are for the purpose of describing particular embodiments only and are not intended to be limiting of the invention. As used in the description of the invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of stated features, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, operations, elements, components, and / or groups thereof.

[0070] As used herein, the term "if" may be interpreted to mean "when" or "upon" or "in response to determining," "in accordance with a determination," or "in response to detecting" a stated stop condition is true, depending on the context. Similarly, the phrases "if it is determined that [a stated stop condition is true]" or "if [a stated stop condition is true]" or "when [a stated stop condition is true]" may be interpreted to mean "upon determining" or "in response to determining" or "in accordance with a determination" or "upon detecting" or "in response to detecting" that a stated stop condition is true, depending on the context.

[0071] While some of the various figures show some logical stages in a particular order, stages that are not order dependent may be rearranged and other stages may be combined or broken down. While some rearrangements or other groupings are specifically mentioned, others will be apparent to those of ordinary skill in the art, and thus this does not present an exhaustive list of alternatives. Additionally, it should be recognized that the stages may be implemented in hardware, firmware, software, or any combination thereof.

[0072] The above description has been set forth with reference to specific implementations for purposes of explanation. However, the above illustrative description is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments have been chosen and described to best explain the principles of the invention and its practical application, and thereby enable those skilled in the art to best utilize the invention and its various embodiments, with various modifications suited to the particular use contemplated. The implementations include alternatives, modifications, and equivalents that are within the spirit and scope of the appended claims. Numerous specific details are described in order to provide a thorough understanding of the subject matter presented herein. However, it will be apparent to those skilled in the art that the subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the implementations.

Claims

1. 1. A computer-implemented method for provisioning edge resources performed by a computing device in a 5G Media Streaming (5GMS) architecture, comprising: receiving a new edge resource configuration request from the first device in association with the 5G media streaming session; determining an edge management mode for the new edge resource configuration request; allocating edge resources for the 5G media streaming session based on the edge management mode; returning a response to the first device, the response including information of the edge resources allocated for the new edge resource configuration request. method.

2. the edge management mode of the edge resource configuration request is a network-driven mode; The step of allocating edge resources for the 5G media streaming session based on the edge management mode further includes: generating a resource identifier for the new edge resource configuration request; identifying existing edge resources that satisfy one or more predefined conditions in the new edge resource configuration request as the edge resources allocated for the new edge resource configuration request; and including the resource identifier and information of the identified existing edge resource in the response to the first device. The method of claim 1.

3. The method further comprises: Upon determining that at least one of the predetermined conditions of the new edge resource configuration request is not satisfied by the existing edge resources: instantiating new edge resources that satisfy the predetermined conditions for the new edge resource configuration request; A response to the first device includes information of the newly instantiated edge resource. The method of claim 2.

4. the edge management mode of the edge resource configuration request is an application-driven mode; The step of allocating edge resources for the 5G media streaming session based on the edge management mode further includes: generating a resource identifier for the new edge resource configuration request; Upon receiving a second request from the client device: identifying existing edge resources that satisfy one or more predefined conditions in the new edge resource configuration request as the edge resources allocated for the new edge resource configuration request; and including the resource identifier and information of the identified existing edge resource in the response to the first device. The method of claim 1.

5. The method further comprises: Upon determining that at least one of the predetermined conditions of the new edge resource configuration request is not satisfied by the existing edge resources: instantiating new edge resources that satisfy the predetermined conditions for the new edge resource configuration request; A response to the first device includes information of the newly instantiated edge resource. The method of claim 4.

6. the identified existing edge resource in the response to the first device is based at least in part on a resource identifier in the second request from the client device. The method of claim 4.

7. the first device is associated with an application provider or a media session handler associated with a user equipment; The method of claim 1.

8. the new edge resource configuration request includes an activation trigger element for restricting the edge resources allocated for the new edge resource configuration request to a media session. The method of claim 1.

9. one or more processors; Memory; and one or more executable instructions, The executable instructions are stored in the memory and configured to be executed by the one or more processors to cause the computing device to perform the computer-implemented method of any one of claims 1 to 8 for provisioning edge resources in a 5G Media Streaming (5GMS) architecture. Computing device.

10. A computer program comprising one or more executable instructions that, when executed by one or more processors of a computing device, causes the computing device to perform a computer-implemented method according to any one of claims 1 to 8 for provisioning edge resources in a 5G Media Streaming (5GMS) architecture.

Images