Method, device and computer program for event-driven provisioning of new edge server in 5g media streaming architecture

Abstract

To provide a method for event-driven provisioning of edge servers in a 5G Media Streaming (5GMS) architecture.SOLUTION: A method includes: setting, by a 5GMS application provider (AP), during provisioning or updating of a first edge application server (EAS), one or more event trigger conditions; determining, by a 5GMS application function (AF), based on an indicator event associated with the first EAS, that at least one of the one or more event trigger conditions of the first EAS is satisfied; generating, by the 5GMS AP, a trigger event in response; setting, during the provisioning or updating of a second EAS, one or more activating conditions for activating the second EAS; determining that the generated trigger event is associated with at least one of the activating conditions for activating the second EAS; and transmitting a message causing activation of the second EAS.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority from U.S. Provisional Patent Application No. 63 / 307,546, filed in the U.S. Patent and Trademark Office on February 7, 2022, and U.S. Patent Application No. 18 / 080,195, filed on December 13, 2022, the entire disclosures of which are incorporated herein by reference.

[0002]

[0002] TECHNICAL FIELD The present disclosure relates generally to fifth generation (5G) media streaming (5GMS), and more particularly to provisioning new edge application servers based on set events. [Background technology]

[0003]

[0003] The 3rd Generation Partnership Project (3GPP) recently provided extensions for the use of edge servers in the 5G Media Streaming (5GMS) architecture, but the detailed methodology for provisioning these edge servers has not yet been defined.

[0004]

[0004] 3rd Generation Partnership Project (3GPP) TS 23.558 defines a general architecture for enabling edge applications, including discovery of hardware capabilities of edge elements and discovery of edge applications by application clients. 3GPP TS 26.501 defines a general architecture for 5G media streaming applications. It recently added an extension to use the TS 23.558 edge architecture as part of the 5G MSA architecture.

[0005]

[0005] However, the actual method for providing such a service has not been defined. This disclosure defines a method for provisioning a new edge server based on a trigger event of an active edge server. Summary of the Invention

[0006]

[0006] According to one or more embodiments, it is possible to provide a method for event-driven provisioning of edge servers in a 5G Media Streaming (5GMS) architecture. The method may be executed by at least one processor and may include: a 5GMS Application Provider (AP) setting one or more event trigger conditions during provisioning or updating of a first Edge Application Server (EAS); a 5GMS Application Function (AF) determining in the first EAS that at least one of the one or more event trigger conditions of the first EAS is satisfied based on an indicator event related to the first EAS; in response to determining that at least one of the event trigger conditions of the first EAS is satisfied, the 5GMS AP generating a trigger event; the 5GMS AP setting one or more activation conditions for activating a second EAS during provisioning or updating of a second EAS; the 5GMS AP determining that the generated trigger event is related to at least one of the one or more activation conditions for activating the second EAS; and transmitting a message related to the generated trigger event to an EAS in the 5GMS architecture, the message causing activation of the second EAS.

[0007] According to one or more embodiments, a device for event-driven provisioning of an edge server in a 5G Media Streaming (5GMS) architecture may be provided. The device may include at least one memory configured to store program code; and at least one processor configured to read the program code and operate as directed by the program code. The program code includes: a first setting code configured to cause at least one processor by a 5GMS application provider (AP) to set one or more event trigger conditions during provisioning or updating of a first edge application server (EAS); a first determining code configured to cause at least one processor by a 5GMS application function (AF) to determine in the first EAS that at least one of the one or more event trigger conditions of the first EAS is satisfied based on an indicator event associated with the first EAS; a generating code configured to cause the at least one processor by the 5GMS AP to generate a trigger event in response to determining that at least one of the event trigger conditions of the first EAS is satisfied; a second setting code configured to cause the at least one processor by the 5GMS AP to set one or more activation conditions for activating a second EAS during provisioning or updating of a second EAS; The AP may include a second determination code configured to cause the at least one processor to determine that the generated trigger event is associated with at least one of one or more activation conditions for activating a second EAS; and a transmission code configured to cause the at least one processor to transmit a message associated with the generated trigger event, the message causing activation of the second EAS, to an EAS in the 5GMS architecture.

[0008]

[0008] According to one or more embodiments, it is possible to provide a non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a device for event-driven provisioning of an edge server in a 5G Media Streaming (5GMS) architecture, cause the one or more processors to: set, by a 5GMS Application Provider (AP), one or more event trigger conditions during preparation or update of a first Edge Application Server (EAS); determine, by a 5GMS Application Function (AF), in the first EAS, based on an indicator event associated with the first EAS, that at least one of the one or more event trigger conditions of the first EAS is satisfied; generate, by the 5GMS AP, a trigger event in response to determining that at least one of the event trigger conditions of the first EAS is satisfied; set, by the 5GMS AP, one or more activation conditions for activating a second EAS during preparation or update of a second EAS; and generate, by the 5GMS Application Provider (AP), one or more activation conditions for activating a second EAS during preparation or update of the second EAS. The method includes one or more instructions that cause the AP to determine that the generated trigger event is associated with at least one of one or more activation conditions for activating a second EAS; and transmit a message associated with the generated trigger event to an EAS in the 5GMS architecture, the message causing activation of the second EAS. [Brief description of the drawings]

[0009] 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]

[0010] FIG. 1 illustrates an embodiment of an environment in which the methods, apparatus, and systems described herein may be implemented. [Diagram 2]

[0011] FIG. 2 is a block diagram of example components of one or more devices of FIG. [Diagram 3]

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

[0013] FIG. 4 is a diagram of a fifth generation (5G) edge network architecture according to an embodiment. [Diagram 5]

[0014] FIG. 5 is a diagram of a 5G media streaming architecture for enabling edge applications according to an embodiment. [Figure 6]

[0015] FIG. 6 is a flowchart of an exemplary process for event-driven provisioning of edge servers in a media streaming network. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010]

[0016] Figure 1 illustrates an environment 100 in which embodiments of the methods, apparatus, and systems described herein may be implemented. As shown in Figure 1, environment 100 may include a user device 110, a platform 120, and a network 130. The devices in environment 100 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0011]

[0017] 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., a pair of smart glasses or a smart watch), or a similar device. In some implementations, user device 110 can receive information from platform 120 and / or transmit information to platform 120.

[0012]

[0018] 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, such that software components can be swapped out depending on particular needs. In this manner, platform 120 can be easily and / or quickly reconfigured for a variety of uses.

[0013]

[0019] 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 in a cloud computing environment 122, in some implementations platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0014]

[0020] Cloud computing environment 122 includes an environment that hosts platform 120. Cloud computing environment 122 can provide services such as computing, software, data access, storage, etc., that do not require end users (e.g., user devices 110) to have knowledge of the physical location and configuration of the systems and / or devices that host 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”).

[0015]

[0021] Computational resources 124 may include one or more personal computers, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, computational resources 124 may host platform 120. Cloud resources may include computing instances executing on computational resources 124, storage devices provided on computational resources 124, data transfer devices provided by computational resources 124, etc. In some implementations, computational resources 124 may communicate with other computational resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0016]

[0022] As further shown in FIG. 1, the 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, virtualized storage (“VS”) 124-3, one or more hypervisors (“HYP”) 124-4, etc.

[0017]

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

[0018]

[0024] 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 can be either a system virtual machine or a process virtual machine, depending on the use and extent of correspondence of virtual machine 124-2 to any real-world 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 322, such as data management, synchronization, or long-term data transfer.

[0019]

[0025] Virtualized storage 124-3 includes one or more storage systems and / or one or more devices that use virtualization techniques within the storage systems or devices of the computing 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 that allows the storage system to be accessed regardless of the physical storage or heterogeneous structure. This separation may allow the administrator of the storage system flexibility in how the administrator manages the storage for the end user. File virtualization may eliminate the dependency between data accessed at the file level and where the file is physically stored. This may allow for optimization of storage usage, server consolidation, and / or performance of non-disruptive file movement.

[0020]

[0026] 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 the virtualized hardware resources.

[0021]

[0027] Network 130 may include one or more wired and / or wireless networks, such as, for example, 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, an optical fiber-based network, etc., and / or a combination of these or other types of networks.

[0022]

[0028] The number and arrangement of devices and networks shown in Figure 1 are provided as an example. In practice, there may be additional, fewer, different, or otherwise arranged devices and / or networks relative to those shown in Figure 1. Further, 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.

[0023]

[0029] Figure 2 is a block diagram of example components of one or more devices of Figure 1. Device 200 may correspond to user equipment 110 and / or platform 120. As shown in Figure 2, device 200 may include a bus 210, a processor 220, a memory 230, a storage element 240, an input element 250, an output element 260, and a communication interface 270.

[0024]

[0030] 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 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or another type of processing element. 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.

[0025]

[0031] The storage element 240 stores information and / or software related to the operation and use of the device 200. For example, the storage element 240 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cartridge, a magnetic tape, and / or other type of non-transitory computer-readable medium along with a corresponding drive.

[0026]

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

[0027]

[0033] 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 enables device 200 to receive information from other devices 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.

[0028]

[0034] Device 200 can perform one or more 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 element 240. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space distributed across multiple physical storage devices.

[0029]

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

[0030]

[0036] The number and arrangement of components shown in Figure 2 are provided as an example. In practice, device 200 may include additional, fewer, different, or differently arranged components relative to 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.

[0031]

[0037] 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 downlink or uplink media streaming services or both. A 5GMS Application Provider may include a party that interacts with the functions of the 5GMS system and provides a 5GMS Aware Application that interacts with the functions of the 5GMS system. A 5GMS Aware Application may refer to an application in a User Equipment (UE) provided by a 5GMS Application Provider that contains the service logic of a 5GMS Application Service and interacts with other 5GMS Clients and network functions via interfaces and Application Programming Interfaces (APIs) defined in the 5GMS Architecture. A 5GMS Client may refer to a UE function that is either a 5GMS Downlink (5GMSd) Client or a 5GMS Uplink (5GMSu) Client, or both.

[0032]

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

[0033]

[0039] A dynamic policy may refer to dynamic policy and charging control (PCC) rules for uplink or downlink application flows during a media session. An egest session may refer to an uplink media streaming session from a 5GMS AS to a 5GMSu application provider. An ingest session may refer to a session that uploads media content to a 5GMSd AS. A policy template may refer to a collection of (semi-static) Policy or Control Function (PCF) / Network Exposure Function (NEF) API parameters that are specific to a 5GMS application provider and the resulting PCC rules. A policy template ID may identify the desired policy template, which is used by the 5GMSd Application Function (AF) to select the appropriate PCF / NEF API for the 5G system so that the PCF can compile the desired PCC rules. A media player entry may 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 may point to a pointer (e.g., in the form of a URL) that defines an entry point of an uplink media streaming session. A presentation entry may point to a document or a pointer to a document that defines an application presentation, such as an HTML5 document.

[0034]

[0040] Provisioning session may refer to a data structure provided by a 5GMSd application provider on the interface (M1d) that configures 5GMSd capabilities related to a set of 5GMSd-aware applications. 5GMSd media player may refer to a UE function that allows playing and rendering of media presentations based on media playback entries and exposes some basic controls like play, pause, seek and stop to 5GMSd-aware applications. Server access information may refer to a set of parameters and addresses (including 5GMSd AF and 5GMSd AS addresses) required to activate reception of a streaming session. Service and content discovery may refer to functions and procedures provided by a 5GMSd application provider to a 5GMS-aware application that enable an end user to discover available streaming services and content offerings and select a particular service or content item for access. Service Notification may refer to a procedure between a 5GMS-aware Application and a 5GMS Application Provider that enables the 5GMS-aware Application to obtain 5GMS service access information directly or in a form that references that information.

[0035]

[0041] A Third Party Player may refer to a portion of an application that uses the API and performs selected 5GMSd functions to play media content. A Third Party Uplink Streamer may refer to a portion of an application that uses the API and performs selected 5GMSd functions to capture and stream media content.

[0036]

[0042] FIG. 3 is a diagram of a media architecture 300 for media streaming according to an embodiment. A 5GMSu application provider 301 can use 5GMSu for uplink streaming services or downlink streaming services. The 5GMSu application provider 301 can provide a 5GMS aware application 302 to a UE 303 to utilize a 5GMS client 304 and network functions using interfaces defined in 5GMS. The 5GMS aware application 302 can include service logic for 5GMS application services and can interact with other 5GMS clients and network functions via interfaces and APIs defined in the 5GMS architecture. The 5GMS AS 305 can be an AS dedicated to 5G media uplink streaming. The 5GMS client 304 can be an internal function of the UE 303 dedicated to 5G media uplink streaming.

[0037]

[0043] The 5GMS AF 306 and the 5GMS 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 the link 320.

[0038]

[0044] The media architecture 300 can connect the internal functions of the UE 303 with the relevant network functions for 5G media uplink streaming. Thus, the media architecture 300 can include multiple functions. For example, the 5GMS client 304 in the UE 303 can be an originator of 5GMS services that can be accessed via an interface / API. The 5GMS client 304 can include two sub-functions: a media session handler 309 and a media streamer 310. The media session handler 309 can communicate with the 5GMS AF 306 to establish, control, and support the delivery of media sessions. The media session handler 309 can expose APIs that can be used by the 5GMS aware applications 302. The media streamer 310 can communicate with the 5GMS AS 305 to stream media content and provide services to the 5GMS aware applications 302 for media capture and streaming and the media session handler 309 for media session control. The 5GMS aware applications 302 can implement external application or content service provider specific logic and control the 5GMS clients 304 by enabling the establishment of media sessions. The 5GMS AS 305 can host 5G media functions and can be implemented as a content delivery network (CDN), for example. The 5GMS application provider 301 can be an external application or content specific media function, such as media storage, consumption, transcoding, and redistribution, that uses the 5GMS to stream media from the 5GMS aware applications 302.The 5GMS AF 306 may provide various control functions to the Media Session Handler 309 and / or the 5GMS Application Provider 301 in the UE 303. The 5GMS AF 306 may relay or initiate requests for processing by various PCFs 311 or interact with other network functions. The 5GMS AF 306 may be connected to the PCF 311 by an N5 interface 319.

[0039]

[0045] The media architecture 300 may include a number of different interfaces. For example, link 321 may relate to M1u, which may be a 5GMS provisioning API exposed by the 5GMS AF 306 to prepare for use of the media architecture 300 and to obtain feedback. Link 322 may relate to M2u, which may be a 5GMS publishing API exposed by the 5GMS AS 305, which may be used if the 5GMS 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 about content hosted in the 5GMS 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 5GMS AS 323 to the media streamer 310 to stream media content. Link 325 may relate to M5u, which may be a media session handling API exposed by the 5GMS AF 305 to the media session handler for media session processing, control and assistance, including appropriate security mechanisms such as 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 5GMS aware application 302 to utilize the 5GMS capabilities. Link 327 may relate to M7u, which may be a media streamer API exposed by the media streamer 310 to the 5GMS aware application 302 and the media session handler 309 to utilize the media streamer 310.The link 328 may relate to M8u, which may be an application API used for example for information exchange between the 5GMS Aware Application 302 and the 5GMS Application Provider 301, for example to provide service access information to the 5GMS Aware Application 302. Also, the UE 303 may be implemented in a self-contained manner such that the interfaces M6u 326 and M7u 327 are not revealed.

[0040]

[0046] FIG. 4 is a diagram of a 5G edge network architecture 400 according to an embodiment. An edge data network (EDN) 401 is a local data network. An edge application server (EAS) 402 and an edge enabler server (EES) 403 are included within the EDN 401. An edge configuration server (ECS) 404 provides configuration related to the EES 403, including details of the EDN 401 hosting the EES 403. A user equipment (UE) 405 includes an application client (AC) 406 and an edge enabler client (EEC) 407. The EAS 402, EES 403, and ECS 404 are capable of interworking with a 3GPP core network 408.

[0041]

[0047] The EES 403 provides the supporting functions required by the EAS 402 and the EEC 407. The functions of the EES 403 may include: providing configuration information to the EEC 407; enabling exchange of application data traffic with the EAS; supporting API invoker and API exposing functions as specified, for example, in 3GPP TS 23.222; interacting with the 3GPP core network 408 to access network function capabilities directly (e.g., via a PCF) or indirectly (e.g., via a Service Capability Exposure Function (SCEF) / NEF / SCEF+NEF); supporting application context transfer functionality; supporting external exposure of service capabilities and 3GPP network to the EAS 402 via link EDGE-3; supporting registration functions (i.e., registration, update, and deregistration) for the EEC 407 and the EAS; and supporting the functionality of triggering instantiation of the EAS 402 on request.

[0042]

[0048] The EEC 407 provides the support functions required for the AC. The functions of the EEC 407 may include: extracting and preparing configuration information to enable the exchange of application data traffic with the EAS 402; discovering available EASs 402 in the EDN 401;

[0043]

[0049] The ECS 404 provides the support functions required for the EEC 407 to connect with the EES 403. The functions of the ECS 404 are: preparing edge configuration information for the EEC 407, such as information for the EEC 407 to connect to the EES 403 (e.g., service area information applicable to the LADN) and information for establishing a connection with the EES 403 (e.g., URI); supporting registration functions (i.e., register, update, and de-register) for the EES 403; supporting API invoker and API exposing function functions as specified in 3GPP TS 23.222; and interacting with the 3GPP core network 408 to access network function capabilities directly (e.g., PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF).

[0044]

[0050] The AC 406 is an application resident in the UE 405 that performs client functions.

[0045]

[0051] The EAS 402 is an application server that resides in the EDN 401 and performs server functions. The AC 406 connects to the EAS 402 to utilize the services of the application with the benefits of edge computing. It is possible that the server functions of the application are only available as an EAS 402. However, it is also possible that a particular server function is available both at the edge and in the cloud as an EAS 402 and an application server that resides in the cloud, respectively. The server functions provided by the EAS 402 and its cloud application server counterpart may be the same or different; if they are different, the application data traffic exchanged with the AC may also be different. The EAS 402 may consume the capabilities of the 3GPP core network 408 in various ways, for example: if the EAS 402 is an entity trusted by the 3GPP core network 408, it may directly call the capability APIs of the 3GPP core network 408; the EAS 402 may call the capabilities of the 3GPP core network 408 via the EES 403; the EAS 402 may consume the capabilities of the 3GPP core network 408 via the capability exposure function. functions), for example via the SCEF or NEF.

[0046]

[0052] The architecture 400 may include a number of different interfaces to enable edge applications, which are referred to as reference points. For example, link EDGE-1 may be a reference point that allows interaction between the EES 403 and the EEC 407. It supports the registration and deregistration of the EEC 407 to the EES 403; the retrieval and provisioning of EAS 402 configuration information; and the discovery of available EAS 402s within the EDN 401.

[0047]

[0053] Link EDGE-2 can be a reference point enabling interaction between the EES 403 and the 3GPP Core Network 408. It supports access to the 3GPP Core Network 408 functions and APIs to retrieve network capability information: for example via SCEF and NEF APIs as defined in 3GPP TS 23.501, 3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; or with an EES 403 deployed in the MNO Trust Domain (see clause 5.13 of 3GPP TS 23.501, 3GPP TS 23.503, 3GPP TS 23.682). Link EDGE-2 can reuse 3GPP reference points or interfaces of EPS or 5GS to allow for different deployment models.

[0048]

[0054] Link EDGE-3 may be a reference point enabling interaction between the EES 403 and the EAS 402. It supports: registration of the EAS 402 with availability information (e.g., time constraints, location constraints); deregistration of the EAS 402 from the EES 403; discovery of target EAS 402 information to support application context transfer; providing access to network capability information (e.g., location information, Quality of Service (QoS) related information); and requesting the setup of a data session between the AC and the EAS 402 with a specific QoS.

[0049]

[0055] Link EDGE-4 can be a reference point enabling interaction between ECS 404 and EEC 407. It supports: provisioning edge configuration information to EEC 407.

[0050]

[0056] Link EDGE-5 can be considered as a reference point allowing interaction between AC and EEC 407.

[0051]

[0057] Link EDGE-6 may be a reference point enabling interaction between the ECS 404 and the EES 403. It supports: the registration of EES 403 information to the ECS 404.

[0052]

[0058] Link EDGE-7 can be a reference point enabling interaction between the EAS 402 and the 3GPP Core Network 408. It supports access to the 3GPP Core Network 408 functions and APIs to retrieve network capability information: for example via SCEF and NEF APIs as defined in 3GPP TS 23.501, 3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; or with the EAS 402 deployed in the MNO Trust Domain (see clause 5.13 of 3GPP TS 23.501, 3GPP TS 23.682). Link EDGE-7 can reuse 3GPP reference points or interfaces of EPS or 5GS to allow for different deployment models.

[0053]

[0059] Link EDGE-8 may be a reference point enabling interaction between ECS 404 and 3GPP Core Network 408. It supports: a) accessing 3GPP Core Network 408 functions and APIs to retrieve network capability information, e.g. via SCEF and NEF APIs as defined in 3GPP TS 23.501, 3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; and with ECS 404 deployed within the MNO Trust Domain (see clause 5.13 of 3GPP TS 23.501, 3GPP TS 23.682). Link EDGE-8 may reuse 3GPP reference points or interfaces of EPS or 5GS, taking into account different deployment models.

[0054]

[0060] The AC 406 can send a query to the EES 403 via the EEC 407 to find a suitable EAS. In this query, the AC 406 includes an EAS discovery filter that defines the desired characteristics of a suitable EAS. In response, the EEC 407 provides the AC 406 with a list of matching EASs and some of their characteristics. The AC 406 then selects the best EAS from the list.

[0055]

[0061] 5 is a diagram of a 5G media streaming architecture 500 with edge extensions to enable edge applications according to an embodiment. The 5GMS application provider 501, 5GMS aware application 502, UE 503, 5GMS client 504, 5GMS AS 505, 5GMS AF 506, DN 507, NEF 508, media session handler 509, media streamer 510, and PCF 511, along with interfaces M1 521, M2 522, M3 523, M4 524, M5 525, M6 526, M7 527, M8 528, N5 519, and N33 520 are similar to their counterparts in FIG. 3, and therefore a detailed description of these components is omitted.

[0056]

[0062] The architecture 500 includes an EES 550 as part of a 5GMS AF 506, an EAS 522 in a DN 507, an EEC 554 as part of a media session handler 509, and an ECS 556. The EEC 554 is connected to the EES 550 by an Edge-1 interface 570. The EAS 552 is connected to the EES 550 by an Edge-3 interface 572. The EEC 554 is connected to the ECS 556 by an Edge-4 interface 574. The EEC 554 is connected to the 5GMS aware application 502 by an Edge-5 interface 576. The ECS 556 is connected to the EES 550 by an Edge-6 interface 578. Finally, an Edge-9 interface 580 is connected to the EES Connected to 550.

[0063] In Figure 5, the 5GMS Application Provider (AS) uses the M1 interface to request session provisioning from the 5GMS AF, and then through the same interface the AP requests the provisioning of various session features including server certificate, content provisioning, content hosting configuration, reporting, consumption reporting, policies, and others.

[0057]

[0064] In Figure 5, the 5GMS Application Provider (AS) uses the M1 interface to request session provisioning from the 5GMS AF, and then through the same interface the AP requests the provisioning of various session features including server certificate, content provisioning, content hosting configuration, reporting, consumption reporting, policies, and others.

[0058]

[0065] As mentioned above, the current 5G Edge architecture defined in 3GPP TS 23.558 only defines the discovery of edge applications by application clients. 3GPP TS 26.501 only defines the media streaming architecture. It recently added the use of the TS 23.558 Edge architecture as part of the 5G MSA architecture as an extension. However, the actual method of providing such services is not defined.

[0059]

[0066] Therefore, an embodiment of the present disclosure provides a method for provisioning a new edge server based on a trigger event of a running edge server.

[0060]

[0067] Aspects of the present disclosure are directed to extending the 5GMS M1 interface. Embodiments of the present disclosure allow for setting events for an existing EAS server so that one or more events are issued when an EAS profile reaches a certain condition. Embodiments of the present disclosure allow for subscribing and receiving events from another EAS server to activate a new EAS server.

[0061]

[0068] The characteristics of an EAS are defined by its profile, known in 29.55 as EASProfile. An EAS profile may change during its operation. Some of these service KPIs are defined as follows: Table 1: Definition of type EASServiceKPI

[0062] [Table 1]

[0069] An embodiment of the present disclosure defines an event based on one or more KPI parameters, including the KPI parameters from Table 1. When one or more parameters reach a certain value, the 5 GMS AS / EAS may generate a corresponding event, which may be collected using the Data Collection AF.

[0063]

[0070] A 5GMS Application Service Provider (AP) may set an event trigger condition when provisioning a new EAS. The event trigger condition may be carried in the activation trigger parameter. In one embodiment, the event may be set by adding a parameter to the EdgeResourcesConfiguration document and / or descriptor. In one embodiment, a 5GMS Application Service Provider may set an event trigger condition when provisioning a new EAS. The event trigger condition may be carried in the activation trigger parameter. As an example, a new property and / or parameter known as "TriggeringEvents" may be added to the EdgeResourcesConfiguration resource as detailed in Table 2 below.

[0064] Table 2: EdgeResourcesConfiguration resource definition

[0065] [Table 2]

[0071] In the same or another embodiment, events can be set using the event preparation API (R1).

[0066]

[0072] According to one aspect, the 5GMS application provider can set conditions for starting a new edge server by the 5GMS AF. The application provider can set conditions for generating an event in the running edge server E1 while updating or creating the provisioning of the edge server through the M1 interface. The application provider can also set activation conditions for activating a new edge server E2 while updating or creating the provisioning of the edge server through the M1 interface. The 5GMS AF can subscribe to events defined by E1 during its provisioning. When any of the conditions in E1 reach a set limit or any condition is met, the 5GMS AF / EAS can issue an event. In some embodiments, the 5GMS AF can be subscribed to E1 events and therefore receives events issued by E1. The 5GMS AF can check that the particular event received meets some activation condition for E2. If the condition is met, the 5GMS AF can activate the E2 server.

[0067]

[0073] FIG. 6 is a flow chart of an example process 600 for event-driven provisioning of edge servers in a 5G media streaming network.

[0068]

[0074] In operation 605, during provisioning or updating of the first edge application server, a 5GMS application provider (AP) may configure one or more event trigger conditions. In some embodiments, the one or more event trigger conditions may be based on one or more dynamic parameters of the first edge application server. In some embodiments, the one or more event trigger conditions may be based on a maximum request rate from an application client (AC) supported by the first edge application server. The one or more event trigger conditions may be based on a maximum response time reported by an application client (AC) for a service request. In some embodiments, the one or more event trigger conditions may be based on at least one of: a maximum percentage of time available on the first edge application server for use by an application client (AC); a maximum computing resources available on the first edge application server for use by the AC; a maximum graphical computing resources available on the first edge application server for use by the AC; a maximum memory resources available on the first edge application server for use by the AC; a maximum storage resources available on the first edge application server for use by the AC; or a maximum connection bandwidth available on the first edge application server for use by the AC.

[0075] In operation 610, an indicator event associated with the first edge application server is determined by a 5GMS Application Function (AF) to indicate that at least one of the event trigger conditions of the first EAS is satisfied based on the indicator event associated with the first EAS, the determining step including issuing, by the first edge application server, a trigger event indicating that at least one of the one or more event trigger conditions of the first edge application server is satisfied; and listening, by the 5GMS AF, to the trigger event of the first edge application server.

[0069]

[0076] In operation 615, during preparation or updating of the second edge application server, the 5GMS AP may set one or more activation conditions for activating the second edge application server. In some embodiments, the one or more activation conditions may be set based on adding a trigger event parameter to an edge resource configuration descriptor. In some embodiments, the one or more activation conditions may be set using an event preparation application programming interface (API).

[0070]

[0077] At operation 620, in response to determining that at least one of the first EAS event trigger conditions is satisfied, the 5GMS AP may generate a trigger event.

[0071]

[0078] In operation 625, the 5GMS AP determines that the generated trigger event is associated with at least one of the activation conditions for activating a second EAS, and / or the second edge application server can be activated based on a message to an EAS in the 5GMS architecture associated with the generated trigger event, the message causing activation of the second EAS.

[0072]

[0079] 6 illustrates example blocks of process 600, in some implementations process 600 may include additional, fewer, different, or differently arranged blocks relative to those illustrated in FIG 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0073]

[0080] Additionally, the proposed methods may be implemented by a processing circuit (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 to perform one or more of the proposed methods.

[0074]

[0081] The techniques described above may be implemented as computer software using computer readable instructions and physically stored on one or more computer readable mediums.

[0075]

[0082] The embodiments of the present disclosure may be used separately or in combination in any order. Furthermore, each of the embodiments (and their methods) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program stored on a non-transitory computer-readable medium.

[0076]

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

[0077]

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

[0078]

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

[0079]

[0086] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Also, as used herein, the indefinite article terms "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with "one or more." When only one item is intended, the term "a" or similar language is used. Also, as used herein, the terms "has," "have," "having," and the like are intended to be open-ended terms. Additionally, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise.

[0080]

[0087] Additional Notes (Appendix 1) 1. A method for event-driven provisioning of an edge application server in a 5G Media Streaming (5GMS) architecture, the method being executed by at least one processor, the method comprising: A 5GMS application provider (AP) configuring one or more event trigger conditions during provisioning or updating of a first edge application server (EAS); a 5GMS application function (AF) determining, in a first EAS, that at least one of the one or more event trigger conditions of the first EAS is satisfied based on an indicator event associated with the first EAS; generating, by the 5GMS AP, a trigger event in response to the first EAS determining that at least one of the event trigger conditions is satisfied; The 5GMS AP sets one or more activation conditions for activating the second EAS during preparation or updating of the second EAS; determining, by the 5GMS AP, that the generated trigger event is associated with at least one of one or more activation conditions for activating the second EAS; and transmitting a message related to the generated trigger event, the message causing activation of the second EAS, to an EAS within the 5GMS architecture; The method includes:

[0081] (Appendix 2) 2. The method of claim 1, wherein the one or more activation conditions are configured based on adding a trigger event parameter to an edge resource configuration descriptor.

[0082] (Appendix 3) 2. The method of claim 1, wherein the one or more activation conditions are set using an event preparation application programming interface (API).

[0083] (Appendix 4) 2. The method of claim 1, wherein the one or more event trigger conditions are based on one or more dynamic parameters of the first EAS satisfying one or more respective criteria.

[0084] (Appendix 5) 5. The method of claim 4, wherein the one or more event trigger conditions are based on a maximum request rate from an application client (AC) supported by the first EAS.

[0085] (Appendix 6) 5. The method of claim 4, wherein the one or more event trigger conditions are based on a maximum response time reported by an application client (AC) for a service request.

[0086] (Appendix 7) 5. The method of claim 4, wherein the one or more event trigger conditions include: the maximum percentage of time available on said first EAS for use by an Application Client (AC); the maximum computing resources available in the first EAS for use by the AC; the maximum graphical computing resources available in the first EAS for use by the AC; the maximum memory resources available in said first EAS for use by said AC; the maximum storage resources available in said first EAS for use by said AC, or The maximum connection bandwidth available in the first EAS for use by the AC. The method is based on at least one of the following:

[0087] (Appendix 8) 9. The method according to claim 8, wherein the 5GMS AF determines: issuing a trigger event by the first EAS indicating that at least one of the one or more event trigger conditions of the first EAS is satisfied; and the 5GMS AF listening to the trigger event of the first EAS; A method comprising:

[0088] (Appendix 9) A device for event-driven provisioning of an edge application server in a 5G media streaming (5GMS) architecture, the device comprising: at least one memory configured to store program code; and at least one processor configured to read said program code and to operate as directed by said program code; the program code comprising: a first configuration code configured to cause the at least one processor to configure, by a 5GMS application provider (AP), one or more event trigger conditions during provisioning or updating of a first edge application server (EAS); a first determination code configured to cause the at least one processor to determine, in a first EAS, that at least one of the one or more event trigger conditions of the first EAS is satisfied based on an indicator event associated with the first EAS; generation code configured to cause the at least one processor to generate a trigger event in response to the first EAS determining that at least one of the event trigger conditions is satisfied; a second setting code configured to cause the at least one processor to set, during preparation or updating of the second EAS, one or more activation conditions for activating the second EAS; second determination code configured to cause the at least one processor to determine that the generated trigger event is associated with at least one of one or more activation conditions for activating the second EAS; and a transmission code configured to cause the at least one processor to transmit a message associated with the generated trigger event, the message causing activation of the second EAS, to an EAS within the 5GMS architecture; Including, the device.

[0089] (Appendix 10) 10. The device of claim 9, wherein the one or more activation conditions are configured based on adding a trigger event parameter to an edge resource configuration descriptor.

[0090] (Appendix 11) 10. The device of claim 9, wherein the one or more activation conditions are set using an event preparation application programming interface (API).

[0091] (Appendix 12) 10. The device of claim 9, wherein the one or more event trigger conditions are based on one or more dynamic parameters of the first EAS satisfying one or more individual criteria.

[0092] (Appendix 13) 13. The device of claim 12, wherein the one or more event trigger conditions are based on a maximum request rate from an application client (AC) supported by the first EAS.

[0093] (Appendix 14) 13. The device of claim 12, wherein the one or more event trigger conditions are based on a maximum response time reported by an application client (AC) for a service request.

[0094] (Appendix 15) 13. The device of claim 12, wherein the one or more event trigger conditions include: the maximum percentage of time available on said first EAS for use by an Application Client (AC); the maximum computing resources available in the first EAS for use by the AC; the maximum graphical computing resources available in the first EAS for use by the AC; the maximum memory resources available in said first EAS for use by said AC; the maximum storage resources available in said first EAS for use by said AC, or The maximum connection bandwidth available in the first EAS for use by the AC. The device is based on at least one of the following:

[0095] (Appendix 16) 10. The device of claim 9, wherein the first decision code further comprises: an issuing code configured to cause the at least one processor to issue, by the first EAS, a trigger event indicating that at least one of the one or more event trigger conditions of the first EAS is satisfied; and listening code configured to cause the at least one processor to listen to the trigger event of the first EAS; Including, the device.

[0096] (Appendix 17) A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a device for event-driven provisioning of an edge server in a 5G Media Streaming (5GMS) architecture, cause the one or more processors to: A 5GMS application provider (AP) configures one or more event trigger conditions during provisioning or updating of a first edge application server (EAS); A 5GMS application function (AF) determines, in a first EAS, that at least one of the one or more event trigger conditions of the first EAS is satisfied based on an indicator event associated with the first EAS; generating, by the 5GMS AP, a trigger event in response to the first EAS determining that at least one of the event trigger conditions is satisfied; The 5GMS AP sets one or more activation conditions for activating the second EAS during preparation or updating of the second EAS; the 5GMS AP determining that the generated trigger event is associated with at least one of one or more activation conditions for activating the second EAS; and transmitting a message related to the generated trigger event to an EAS within the 5GMS architecture, the message causing activation of the second EAS; A non-transitory computer-readable storage medium comprising one or more instructions for causing a (Appendix 18) 18. The non-transitory computer-readable storage medium of claim 17, wherein the one or more activation conditions are configured based on adding a trigger event parameter to an edge resource configuration descriptor.

[0097] (Appendix 19) 18. The non-transitory computer-readable storage medium of claim 17, wherein the one or more activation conditions are set using an event preparation application programming interface (API).

[0098] (Appendix 20) 18. The non-transitory computer-readable storage medium of claim 17, wherein the one or more event trigger conditions are based on one or more dynamic parameters of the first EAS satisfying one or more respective criteria.

Claims

1. 1. A method for event-driven provisioning of an edge application server in a 5G Media Streaming (5GMS) architecture, executed by at least one processor, the method comprising: A 5GMS application provider (AP) sets one or more event trigger conditions during provisioning or updating of a first edge application server (EAS); The 5GMS AP sets one or more activation conditions for activating the second EAS during the preparation or update of the second EAS; the first EAS issuing a trigger event indicating that at least one of the one or more event trigger conditions of the first EAS is satisfied; A step in which the 5GMS application function (AF) determines that the trigger event issued in the issuing step satisfies one or more activation conditions for activating the second EAS; and activating the second EAS by the 5GMS AF in response to determining that one or more activation conditions for activating the second EAS are satisfied; A method comprising:

2. The method of claim 1 , wherein the one or more activation conditions are set based on adding a trigger event parameter to an edge resource configuration descriptor.

3. The method of claim 1 , wherein the one or more activation conditions are set using an event preparation application programming interface (API).

4. 10. The method of claim 1, wherein the one or more event trigger conditions are based on one or more dynamic parameters of the first EAS satisfying one or more respective criteria.

5. 5. The method of claim 4, wherein the one or more event trigger conditions are based on a maximum request rate from an application client (AC) supported by the first EAS.

6. 5. The method of claim 4, wherein the one or more event trigger conditions are based on a maximum response time reported by an application client (AC) for a service request.

7. 5. The method of claim 4, wherein the one or more event trigger conditions include: the maximum percentage of time available in said first EAS for use by an application client (AC); the maximum computing resources available in the first EAS for use by the AC; the maximum graphical computing resources available in the first EAS for use by the AC; the maximum memory resources available in the first EAS for use by the AC; the maximum storage resources available in the first EAS for use by the AC; or the maximum connection bandwidth available in the first EAS for use by the AC; The method is based on at least one of the following:

8. The method of claim 1 , wherein the one or more activation conditions are included in an activation trigger parameter of an edge resource configuration descriptor.

9. 1. A device for event-driven provisioning of an edge application server in a 5G media streaming (5GMS) architecture, the device comprising: at least one memory configured to store program code; and at least one processor configured to read said program code and to act as directed by said program code; the program code causing the at least one processor to execute a method, the method comprising: The 5GMS AP sets one or more activation conditions for activating the second EAS during the preparation or update of the second EAS; the first EAS issuing a trigger event indicating that at least one of the one or more event trigger conditions of the first EAS is satisfied; A step in which the 5GMS application function (AF) determines that the trigger event issued in the issuing step satisfies one or more activation conditions for activating the second EAS; and activating the second EAS by the 5GMS AF in response to determining that one or more activation conditions for activating the second EAS are satisfied; Including, the device.

10. A computer program product that causes a computer to carry out the method according to any one of claims 1 to 8.

Images