Method, apparatus, computer device, and storage medium for managing the capabilities of a media stream transmission network

Abstract

The present application discloses a method, apparatus, computer device, and storage medium for managing the capabilities of a media stream transmission network. The method includes: receiving a capability request for the media stream processing capabilities of an edge data network (EDN); determining the media stream processing capabilities of the EDN; sending a capability response based on the determined media stream processing capabilities; receiving a media processing workflow request based on the capability response; establishing a media stream session according to the media processing workflow request; and performing stream transmission of media content based on the media stream session.

Description

[0001] Cross - reference to related applications

[0002] This application claims the priority of U.S. Provisional Application No. 63 / 021,411, filed with the U.S. Patent Office on May 7, 2020; U.S. Provisional Application No. 63 / 066,692, filed with the U.S. Patent Office on August 17, 2020; U.S. Provisional Application No. 63 / 075,461, filed with the U.S. Patent Office on September 8, 2020; U.S. Provisional Application No. 63 / 026,432, filed with the U.S. Patent Office on May 18, 2020; U.S. Provisional Application No. 63 / 052,104, filed with the U.S. Patent Office on July 15, 2020; and the priority of U.S. Non - provisional Application No. 17 / 213,679, filed with the U.S. Patent Office on March 26, 2020. The entire contents of each are incorporated herein by reference. Technical Field

[0003] Embodiments of the present application relate to media processing and streaming methods and systems, and in particular, to a method, apparatus, computer device, and storage medium for managing the capabilities of a media streaming network. Background Art

[0004] Networks and cloud platforms are used to run various applications. However, there is no standards - based solution to describe the characteristics of a network or cloud platform or its components.

[0005] The 3rd Generation Partnership Project (3GPP) TS26.501 defines a workflow for an external application server to establish network processing for uplink and downlink flow applications in a 5G network.

[0006] The European Telecommunications Standards Institute (ETSI) Multi - Access Edge Computing (MEC) standard defines an architecture for instantiating, running, and managing applications on a cloud platform.

[0007] The current 5G edge architecture defined in 3GPP TS23.558 only defines a general architecture and the hardware capabilities of discovering edge servers. It does not define how to discover the capabilities of edge servers for media processing, which are more than the original hardware capabilities. It also does not define the environmental characteristics of edge servers.

[0008] In the NBMP standard, the NBMP source is an entity that provides a workflow description to a workflow manager to create, run, manage, and monitor media workflows. The interaction between the NBMP source and the workflow manager is achieved through a set of NBMP operation APIs.

[0009] Under the 5G Media Streaming Architecture (5G MSA), the source device of the media stream establishes an uplink session with the Application Function / Application Server (AF / AS) pair in the network. The receiving device also establishes a downlink session with the AF / AS to stream / download content from the network.

[0010] However, there is no edge computing architecture in 5G MSA to allow the deployment of network and edge processing, or to use edge and network resources for split rendering of media streams. Summary of the Invention

[0011] According to an embodiment of the present application, a method for managing the capabilities of a media stream transmission network is provided. Using at least one processor, the method includes: receiving a capability request for the media stream processing capabilities of an Edge Data Network (EDN); determining the media stream processing capabilities of the EDN; sending a capability response based on the determined media stream processing capabilities; receiving a media processing workflow request based on the capability response; establishing a media stream session according to the media processing workflow request; and streaming media content based on the media stream session.

[0012] According to an embodiment of the present application, a device for managing the capabilities of a media stream transmission network is provided. The device includes: at least one memory for storing computer program code; at least one processor for reading the computer program code and operating according to the instructions of the computer program code. The computer program code includes: a first receiving code for causing the at least one processor to receive a capability request for the media stream processing capabilities of an Edge Data Network (EDN); a determining code for causing the at least one processor to determine the media stream processing capabilities of the EDN; a first sending code for causing the at least one processor to send a capability response based on the determined media stream processing capabilities; a second receiving code for causing the at least one processor to receive a media processing workflow request based on the capability response; a establishing code for causing the at least one processor to establish a media stream session according to the media processing workflow request; and a streaming code for causing the at least one processor to stream media content based on the media stream session.

[0013] According to an embodiment of the present application, there is also provided a non - volatile computer - readable medium, on which instructions are stored. The instructions include at least one instruction, and when the at least one instruction is executed by at least one processor of a device for managing the capabilities of a media - stream transmission network, the at least one processor is caused to: receive a capability request for the media - stream processing capabilities of an edge data network (EDN); determine the media - stream processing capabilities of the EDN; send a capability response based on the determined media - stream processing capabilities; receive a media - processing workflow request based on the capability response; establish a media - stream session according to the media - processing workflow request; and perform streaming transmission of media content based on the media - stream session.

[0014] According to an embodiment of the present application, there is also provided a computer device, including a processor and a memory. At least one instruction is stored in the memory, and the at least one instruction is loaded and executed by the processor to implement the above - mentioned method for managing the capabilities of a media - stream transmission network.

[0015] According to an embodiment of the present application, there is also provided a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer - readable storage medium. A processor of a computer device reads the computer instructions from the computer - readable storage medium, and the processor executes the computer instructions, causing the computer device to execute the above - mentioned method for managing the capabilities of a media - stream transmission network.

[0016] As can be seen from the above - mentioned technical solutions, the method provided by the embodiments of the present invention can discover the network - processing capabilities of a 5G edge network via an external application server, allowing the external application server to know the processing capabilities of the edge server, that is, the current capabilities of the 5G network, especially including environmental characteristics, throughput and latency ranges that the edge server can provide, and a media - processing function library, before requesting to establish any network - based processing. Then, using these processing capabilities, a media - stream session is established with an application client to perform streaming transmission of media content, thereby improving the efficiency of media - stream transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] From the following detailed description of the exemplary embodiments in conjunction with the accompanying drawings, further features, natures, and various advantages of the present application will become apparent:

[0018] Figure 1 A schematic diagram showing an example environment in the system and / or method implemented by the present application;

[0019] Figure 2 Showing Figure 1 example components of at least one device in

[0020] Figure 3Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0021] Figure 4 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0022] Figure 5 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0023] Figure 6 Shows a schematic diagram of an exemplary process for discovering network capabilities according to an embodiment of the present application;

[0024] Figure 7 Shows a schematic diagram of an exemplary process for discovering network capabilities according to an embodiment of the present application;

[0025] Figure 8 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0026] Figure 9 Shows a schematic diagram of an exemplary process for discovering network capabilities according to an embodiment of the present application;

[0027] Figure 10 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0028] Figure 11 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0029] Figure 12 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0030] Figure 13 Shows a schematic diagram of an exemplary process for discovering network capabilities according to an embodiment of the present application;

[0031] Figure 14 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0032] Figure 15 Shows a schematic diagram of a network architecture for media stream transmission according to an embodiment of the present application;

[0033] Figure 16 Shows a schematic diagram of an exemplary process for discovering network capabilities according to an embodiment of the present application;

[0034] Figure 17 Shows a schematic diagram of an exemplary process for discovering network capabilities according to an embodiment of the present application;

[0035] Figure 18 A schematic diagram showing an exemplary process for discovering network capabilities according to an embodiment of the present application;

[0036] Figure 19 A schematic diagram showing a network architecture for media stream transmission according to an embodiment of the present application;

[0037] Figure 20 A schematic diagram showing a network architecture for media stream transmission according to an embodiment of the present application;

[0038] Figure 21 A schematic diagram showing a network architecture for media stream transmission according to an embodiment of the present application;

[0039] Figure 22 A schematic diagram showing a network architecture for media stream transmission according to an embodiment of the present application;

[0040] Figure 23 A schematic diagram showing a network architecture for media stream transmission according to an embodiment of the present application;

[0041] Figure 24 An example flowchart showing the capabilities for managing a media stream transmission network according to an embodiment of the present application. Detailed implementation

[0042] Figure 1 A diagram of an example environment 100 in which the systems and / or methods described in the present application can be implemented. As Figure 2 shown, the environment 100 may include a user device 110, a platform 120, and a network 130. The devices in the environment 100 may be interconnected via a wired connection, a wireless connection, or a combination of wired and wireless connections.

[0043] The user device 110 includes at least one device capable of receiving, generating, storing, processing, and / or providing information associated with the platform 120. For example, the user device 110 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a 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, the user device 110 may receive information from the platform 120 and / or transmit information to the platform 120.

[0044] Platform 120 includes at least one device capable of generating an audio output signal via a multi-band synchronous neural vocoder, as described elsewhere in this application. 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 certain software components can be swapped in or out according to specific needs. In this way, platform 120 can be easily and / or quickly reconfigured for different uses.

[0045] In some implementations, as shown in the figure, platform 120 may be hosted in a cloud computing environment 122. It should be noted that although the implementations described in this application describe platform 120 as being hosted in cloud computing environment 122, in some implementations, platform 120 is not cloud-based (i.e., it can be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0046] Cloud computing environment 122 includes an environment that hosts platform 120. Cloud computing environment 122 may provide services such as computing, software, data access, storage, etc. without the end user (e.g., user device 110) having knowledge of the physical location and configuration of at least one system and / or device of the hosted platform 120. As shown in the figure, cloud computing environment 122 may include a group of computing resources 124 (collectively referred to as "computing resources 124" and individually referred to as "computing resource 124").

[0047] Computing resources 124 include at least one personal computer, workstation computer, server device, or other type of computing and / or communication device. In some implementations, computing resources 124 may be the hosted platform 120. Cloud resources may include computing instances executed in computing resources 124, storage devices provided in 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 a wired connection, wireless connection, or a combination of wired and wireless connections.

[0048] As Figure 1 further shown, computing resources 124 include a group of cloud resources, such as at least one application program ("APP") 124-1, at least one virtual machine ("VM") 124-2, virtualized storage ("VS") 124-3, at least one hypervisor ("HYP") 124-4, etc.

[0049] The application 124-1 includes at least one software application that can be provided to and / or accessed by the user device 110 and / or the sensor device 120. The application 124-1 can eliminate the need to install and execute software applications 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 / receive information to / from at least one other application 124-1 via the virtual machine 124-2.

[0050] The virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. The virtual machine 124-2 can be a system virtual machine or a process virtual machine, depending on the use of the virtual machine 124-2 and its correspondence to any real 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 can support a single process. In some implementations, the virtual machine 124-2 can execute on behalf of a user (e.g., the user device 110) and can manage the infrastructure of the cloud computing environment 122, such as data management, synchronization, or long-duration data transfer.

[0051] The virtualized storage 124-3 includes at least one storage system and / or at least one device that uses virtualization technology within a storage system or device of the computing resources 124. In some implementations, in the context of a storage system, the types of virtualization can include block virtualization and file virtualization. Block virtualization can refer to the abstraction (or separation) of logical storage from physical storage, such that the storage system can be accessed without regard to the physical storage or heterogeneous structure. The separation can allow the administrator of the storage system to have flexibility in how the administrator manages the storage of end users. File virtualization can eliminate the dependence between the data accessed at the file level and the location where the file is physically stored. This can enable optimization of storage usage, server consolidation, and / or performance of non-disruptive file migration.

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

[0053] Network 130 includes at least one wired and / or wireless network. For example, network 130 can 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.

[0054] Figure 1 The number and arrangement of the devices and networks shown are provided as examples. In practice, there may be more devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than Figure 1 shown. Additionally, Figure 1 two or more of the shown devices can be implemented within a single device, or Figure 1 a single shown device can be implemented as multiple distributed devices. Additionally or alternatively, a set of devices (e.g., at least one device) of environment 100 can perform at least one function described as being performed by another set of devices of environment 200.

[0055] Figure 2 is a diagram of example components of device 200. Device 200 can correspond to user device 110 and / or platform 120. As Figure 2 shown, device 200 can include a bus 210, a processor 220, a memory 230, a storage component 240, an input component 250, an output component 260, and a communication interface 270.

[0056] Bus 210 includes components that permit communication among the components of device 200. Processor 220 is implemented in hardware, firmware, or a combination of hardware and software. Processor 220 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, processor 220 includes at least one processor capable of being programmed to perform functions. Memory 230 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by processor 220.

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

[0058] The input component 250 includes components that allow the 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, the input component 250 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). The output component 260 includes components that provide output information from the device 200 (e.g., a display, a speaker, and / or at least one light emitting diode (LED)).

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

[0060] The device 200 may perform at least one of the processes described in this application. The device 200 may execute these processes in response to the processor 220 executing software instructions stored in a non-volatile computer-readable medium such as the memory 230 and / or the storage component 240. The computer-readable medium is defined in this application as a non-volatile memory device. The memory device includes a memory space within a single physical storage device or a memory space distributed across multiple physical storage devices.

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

[0062] Figure 2The number and arrangement of the components shown are provided as an example. In practice, device 200 may include more components, fewer components, different components, or components in a different arrangement than the Figure 2 components shown. Additionally or alternatively, a set of components (e.g., at least one component) of device 200 may perform at least one function described as being performed by another set of components of device 200.

[0063] Figure 3 is a diagram of a media architecture 300 for media streaming. In an embodiment of the present application, media architecture 300 may be used for uplink streaming or downlink streaming. A 5G Media Streaming Uplink (5GMS) application provider 301 may use 5GMS for streaming services. The 5GMS application provider 301 may provide a 5GMS-aware application 302 on a UE 303 to use the interfaces and APIs defined in 5GMS to utilize the 5GMS client 304 and network functions. The 5GMS Application Server (AS) may be an AS dedicated to 5G media streaming. The 5GMS client 304 may be an internal function of the UE 303 dedicated to 5G media streaming.

[0064] The 5GMS Application Function (AF) 306 and the 5GMS AS 305 may be Data Network (DN) 307 functions. The functions in the trusted DN may be trusted by the operator's network. Thus, the AF in the trusted DN may communicate directly with all 5G core functions. The functions in the external DN may communicate with the 5G core functions only via the Network Exposure Function (NEF) 308 using link 320.

[0065] The media architecture 300 can connect the internal functions of the UE 303 and the relevant network functions for 5G media uplink streaming. Therefore, the media architecture 300 can include multiple functions. For example, the 5GMS client 304 on the UE 303 can be the initiator of the 5GMS service and can access the 5GMS service through an interface / API. The 5GMS client 304 can include two sub-functions, the Media Session Handler (MSH) 309 and the Media Flusher 310. The MSH 309 can communicate with the 5GMS AF 306 to establish, control, and support the transmission of media sessions. The MSH 309 can expose the API used by the 5GMS-aware application 302. The Media Flusher 310 can communicate with the 5GMS AS 305 to stream media content and provide services to the 5GMS-aware application 302 for media capture and media streaming, and provide services for media session control to the MSH 309. The 5GMS-aware application 302 can control the 5GMS client 304 by implementing the logic specific to an external application or content service provider and establish a media session. The 5GMS AS 305 can host the 5G media functions. The 5GMS application provider 301 can be the media functionality specific to an external application or content, for example, media storage, consumption, transcoding, and redistribution for streaming media from the 5GMS-aware application 302 using 5GMS. The 5GMS AF 306 can provide various control functions to the MSH 309 on the UE 303 and / or to the 5GMS application provider 301. The 5GMS AF 306 can act as a relay, or initiate requests for processing towards different Policy or Charging Functions (PCF) 311, or interact with other network functions.

[0066] The media architecture 300 may include multiple different interfaces. For example, the link M1 may be a 5GMS provisioning API opened by the 5GMS AF 306 to provide the media architecture 300 for use and obtain feedback. The link M2 may be a 5GMS publishing API opened by the 5GMS AS 305 and used when the 5GMS AS 305 in a selected trusted DN (such as DN 307) receives the content of the streaming service. The link M3 may be an internal API for information exchange of the content hosted on the 5GMS AS 305 within a trusted DN such as DN 307. The link M4 may be a media uplink flow API opened by the 5GMS AS 323 to the media flusher 310 for streaming media content. The link M5 may be a media session handling API opened by the 5GMS AF 306 to the media session processor 309 for media session handling, control, and assistance, and the API also includes appropriate security mechanisms such as authorization and authentication. The link M6 may be a UE 303 media session handling API opened by the MSH 309 to the 5GMS-aware application 302 to use 5GMS functions. The link M7 may be a UE media flusher API opened by the media flusher 310 to the 5GMS-aware application 302 and the MSH 309 to use the media flusher 310. The link M8 may be an application API for information exchange between the 5GMS-aware application 302 and the 5GMS application provider 301, for example, providing service access information to the 5GMS-aware application 302.

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

[0068] EES 403 provides the support functions required by EAS 402 and EEC 407. The functionality of EES 403 may include: supplying configuration information to EEC 407 to enable the exchange of application data services with EAS 402; supporting the functionality of API call procedures and API open functions, for example, as specified in 3GPP TS 23.222; the ability to interact with the 3GPP core network 408 to access network functions directly (e.g., via PCF) or indirectly (e.g., via Service Capability Exposure Function (SCEF) / Network Exposure Function (NEF) / SCEF+NEF); supporting the functionality of application context transfer; supporting the exposure of 3GPP network and service capabilities to an external EAS 402 via link EDGE-3; supporting the registration (i.e., registration, update, and deregistration) functionality for EEC 407 and EAS 402; and supporting the functionality of triggering the instantiation of EAS 402 on demand.

[0069] EEC 407 provides the support functions required by AC 406. The functionality of EEC 407 may include: retrieving and supplying configuration information to enable the exchange of application data services with EAS 402; and discovering EAS 402 available in EDN 401.

[0070] ECS 404 provides the support functions required for the connection between EEC 407 and EES 403. The functionality of ECS 404 is: providing edge configuration information to EEC 407, such as information about the connection of EEC 407 to EES 403 (e.g., service area information applicable to LADN); and information for establishing a connection with EES 403 (such as a URI); supporting the registration (i.e., registration, update, and deregistration) functionality of EES 403; supporting the functionality of API call procedures and API open functions as specified in 3GPP TS 23.222; and the ability to interact with the 3GPP core network 408 to access network functions directly (e.g., PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF).

[0071] AC 406 is an application residing in UE 405 that performs client functions.

[0072] EAS 402 is an application server residing in EDN 401 that performs server functions. AC 406 is connected to EAS 402 to utilize the services of the application by taking advantage of the benefits of edge computing. It is possible that the server functions of an application are only served by EAS 402. However, some server functions may also be available both at the edge and in the cloud, served by EAS 402 and an application server residing in the cloud respectively. The server functions provided by EAS 402 and those provided by its corresponding cloud application server may be the same or different; if they are different, the application data traffic exchanged with the AC may also be different. EAS 402 can consume the capabilities of the 3GPP core network 408 in different ways, such as: if it is an entity trusted by the 3GPP core network 408, it can directly invoke the 3GPP core network 408 function APIs; it can invoke the 3GPP core network 408 capabilities through EES 403; and it can invoke the 3GPP core network 408 capabilities through the capability open function (i.e., SCEF or NEF).

[0073] The architecture 400 may include multiple different interfaces for using edge applications, which may be referred to as reference points. For example, the link EDGE-1 may be a reference point that supports the interaction between EES 403 and EEC 407. It supports: registering and deregistering EEC 407 with EES 403; obtaining and providing EAS 402 configuration information; and discovering EAS 402 available in EDN 401.

[0074] The link EDGE-2 may be a reference point that supports the interaction between EES 403 and the 3GPP core network 408. It supports: accessing the 3GPP core network 408 functions and APIs to obtain network capability information, such as accessing via the SCEF and NEF APIs defined in 3GPP TS 23.501, 3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; or, EES 403 deployed within the MNO trust domain (see 3GPP TS 23.501, clause 5.13, 3GPP TS 23.503, 3GPP TS 23.682). Considering different deployment models, the link EDGE-2 may reuse 3GPP reference points, or the interfaces of EPS or 5GS.

[0075] Link EDGE-3 can be a reference point that supports the interaction between EES 403 and EAS 402. It supports: registering EAS 402 with availability information (e.g., time constraints, location constraints); deregistering EAS 402 from EES 403; discovering target EAS402 information to support application context transfer; providing access to network capability information (e.g., location information, Quality of Service (QoS)-related information); and, requesting to establish a data session with specific QoS between AC 406 and EAS 402.

[0076] Link EDGE-4 can be a reference point that supports the interaction between ECS 404 and EEC 407. It supports: supplying edge configuration information to EEC 407.

[0077] Link EDGE-5 can be a reference point that supports the interaction between AC and EEC 407.

[0078] Link EDGE-6 can be a reference point that supports the interaction between ECS 404 and EES 403. It supports: registering EES 403 information with ECS 404.

[0079] Link EDGE-7 can be a reference point that supports the interaction between EAS 402 and 3GPP core network 408. It supports: 3GPP core network 408 functions and APIs to obtain network capability information, e.g., access via SCEF and NEF APIs defined in 3GPP TS 23.501, 3GPP TS23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; or EAS 402 deployed within the MNO trust domain (see 3GPP TS 23.501 clause 5.13, 3GPP TS 23.682). Considering different deployment models, Link EDGE-2 can reuse 3GPP reference points, or, interfaces of EPS or 5GS.

[0080] Link EDGE-8 can be a reference point that supports the interaction between the ECS 404 and the 3GPP core network 408. It supports: a) 3GPP core network 408 functions and APIs to obtain network capability information, such as accessing via the SCEF and NEF APIs defined in 3GPP TS 23.501, 3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; and, the ECS 404 deployed within the MNO trust domain (see 3GPP TS 23.501 clause 5.13, 3GPP TS 23.682). Considering different deployment models, Link EDGE-8 can reuse 3GPP reference points, or, interfaces of EPS or 5GS.

[0081] Corresponding to Figures 5 to 7 the embodiment of, which relates to the workflow and process of discovering the capabilities of a 5G network by an external entity in two phases. For example,

[0082] 1. Discover the hardware capabilities of the edge application server

[0083] 2. Discover the media-specific capabilities of the edge application server

[0084] Before establishing a media processing workflow on the edge server, the processing capabilities of the edge server must be discovered. These capabilities can include:

[0085] 1. Available hardware resources, including processing units, memory, and network elements

[0086] 2. Environmental characteristics, including the operating system (OS), OS version, and other parameters

[0087] 3. The throughput and latency ranges that the edge server can provide

[0088] 4. Media processing function libraries, function descriptions, and input / output formats for various functions such as the following

[0089] a. Encoding, transcoding, and multi-rate encoding into different formats

[0090] b. Presentation generation

[0091] c. Encryption and content protection

[0092] d. Content replacement, such as advertisement insertion

[0093] e. Adding media such as subtitles, object detection, content filtering, etc.

[0094] The current TS23.558 only addresses the first item. The embodiments of this application provide an architecture and method for discovering the second to fourth items.

[0095] Figure 5 The diagram shows the Figure 4 The architecture 400 elements are related to Figure 3 The components of the architecture 300 are combined into the architecture 500. In order to avoid unnecessary repetition, redundant descriptions are omitted.

[0096] like Figure 5 As shown, the media streamer 310 and the MSH 309 are included in the AC 406, and the 5GMS AS 305 and the 5GMS AF 306 are included in the EAS 402. The MSH 309 can communicate with the AC 406 through a link U1, the 5GMS AS 305 can communicate with the 5GMS AF 306 through a link N2, and the 5GMS AF 306 can communicate with the EAS 402 through a link N1.

[0097] Figure 6 Illustrated is a process 600 of a call flow for discovering edge data network capabilities. Process 600 can be performed using architecture 500 or any other desired architecture.

[0098] Process 600 may extend the TS23.558 API to enable discovery of media capabilities of an edge data network (EDN).

[0099] like Figure 6 As shown in , capability discovery is performed through link U1, link EDGE-7, link N1, and link N2 API requests and responses, and vice versa.

[0100] According to process 600, at operation 6010, MSH 309 may use link U1 to send a request for processing capability to AC 406. At operation 6020, AC 406 may use link EDGE-7 to send a request for processing capability to EAS 402. At operation 6030, EAS 402 may use link N1 to send a request for processing capability to 5GMS AF 306. At operation 6040, 5GMS AF 306 may use link N2 to send a request for processing capability to 5GMS AS 305, so that 5GMS AS 305 determines the media stream processing capability of EDN according to the request.

[0101] According to process 600, at operation 6050, 5GMS AS 305 can send a response including processing capabilities, i.e., a capabilities response, to 5GMS AF 306 using link N2. At operation 6060, 5GMS AF 306 can send a response including processing capabilities to EAS 402 using link N1. At operation 6070, EAS 402 can send a response including processing capabilities to AC 406 using link EDGE-7. At operation 6080, AC 406 can send a response including processing capabilities to MSH 309 using link U1.

[0102] The link EDGE-7 API is defined by TS23.558. To support the capabilities discovery shown herein, the link EDGE-7 API can be extended. Link U1, link N1, and link N2 can be internal APIs.

[0103] Figure 7 Process 700 is illustrated that can involve a call flow for discovering edge data network capabilities. Process 700 can be executed using architecture 500 or any other required architecture.

[0104] Process 700 can use the TS23.558 API to discover the hardware capabilities of the edge data network, but use a direct API to discover media-specific capabilities.

[0105] As Figure 7 shown, capabilities discovery is performed by requesting and responding in one phase via U1, EDGE-7 (operations 7010 - 7040) and in a second phase via M5 and N2 APIs (operations 7050 - 7080).

[0106] According to process 700, at operation 7010, MSH 309 can send a request for processing capabilities to AC 406 using link U1. At operation 7020, AC 406 can send a request for processing capabilities to EAS 402 using link EDGE-7. At operation 7030, EAS 402 can send a response including processing capabilities to AC 406 using link EDGE-7. At operation 7040, AC 406 can send a response including processing capabilities to MSH 309 using link U1.

[0107] According to process 700, at operation 7050, MSH 309 may send a request for processing capabilities to 5GMS AF 306 using link M5. At operation 7060, 5GMS AF 306 may send a request for processing capabilities to 5GMS AS 305 using link N2. At operation 7070, 5GMS AS 305 may send a response including processing capabilities to 5GMS AF 306 using link N2. At operation 7080, 5GMS AF 306 may send a response including processing capabilities to MSH 309 using link M5.

[0108] Link EDGE-7API is defined by TS23.558, and link M5 is defined by TS26.501. To support the capability discovery shown herein, link EDGE-7 and link M5 API may be extended.

[0109] In process 700, MSH 309 may discover hardware capabilities via link U1 and link EDGE-7API, and discover media-specific capabilities via link M5 API.

[0110] In all tables of this application, additional information is in italics. Further, the symbol "M" represents mandatory information, and the symbol "O" represents optional information. In this application, the terms "mandatory" and "optional" used in this way indicate that a particular element is in a particular embodiment, rather than being considered mandatory or optional in every embodiment.

[0111] Table 1 shows the extension of link EDGE-7API to support Figures 5 to 7 the media discovery function in

[0112] Table 1: Edge-7 Extension

[0113]

[0114]

[0115] Table 2 shows an example data extension embodiment of link M5 API to support Figures 5 to 7 the media discovery function in

[0116] Table 2: M5 Extension

[0117]

[0118] Tables 3 to 6 describe the parameters added to Figures 5 to 7 link EDGE-7 and link M5 API in

[0119] Table 3: Still Image Information Object

[0120] Name Definition os Operating System Version Operating System Version Number Architecture Hardware Architecture Environment Environment

[0121] Table 4: Flow control parameters

[0122]

[0123]

[0124] Table 5: Repository parameters

[0125]

[0126]

[0127] As shown in Table 5, the supported repositories are described. Each repository includes a list of the supported functions.

[0128] Table 6: Function description

[0129]

[0130]

[0131] As shown in Table 6, the function description describes the list of supported functions, and their characteristics can be retrieved.

[0132] These characteristics may include:

[0133] 1. Supported input formats, codecs and codec profiles / levels, resolution, frame rate

[0134] 2. Transcoding using formats, output codecs, codec profiles / levels, bit rate, etc.

[0135] 3. Reformatting in the output format

[0136] 4. Combination of input media streams, such as network-based splicing, mixing

[0137] 5. Identification or synthesis of media

[0138] Therefore, the embodiments of the present application provide a method for an application to discover 5G network capabilities and discover call flows through the 3GPP edge API. Among them, the 5G device collects currently available resources from an application server including media capabilities, and the 3GPP edge API is extended to provide the media capabilities of the edge network to the application.

[0139] An embodiment of the present application provides a method for an application to discover 5G network capabilities and a method for discovering a call flow. Among them, the discovery of 5G network capabilities by the application includes two phases. First, through the 3GPP Edge API, and then through the 3GPP 5G MSA API. When discovering the call flow, the 5G device collects currently available resources from an application server including media capabilities. Among them, the 3GPP Edge and 5G MSA APIs are extended to provide the media capabilities of the edge network to the application.

[0140] An embodiment of the present application provides a method for discovering 5G application server environment parameters. Among them, the application can discover information about the 5G application server operating system, environment parameters, and related information to run first-party applications, third-party applications, libraries, and functions on the 5G application server.

[0141] Corresponding to Figures 8 to 10 the embodiment, the above-discussed 5G edge architecture can be extended to allow the following:

[0142] 1. Discovery of available EAS 402 by 5GMS AP 301

[0143] 2. Discovery of any available EAS 402 capabilities by 5GMS AP 301

[0144] Figure 8 The architecture 800 is illustrated, where elements from Figure 4 the architecture 400 and elements from Figure 3 the architecture 300 are combined together. To avoid unnecessary repetition, redundant descriptions are omitted.

[0145] As Figure 8 shown, the link EDGE-9 allows communication between the EAS 402 and the 5GMS AP 301, the link EDGE-10 allows communication between the EES 403 and the 5GMS AP 301, and the link EDGE-11 allows communication between the ECS 404 and the 5GMS AP 301.

[0146] Figure 9 The process 900 for the call flow to discover the capabilities of the edge data network 401 is illustrated. The process 900 can be executed using the architecture 800, the architecture 1000 discussed below, or any other required architecture.

[0147] The process 900 can extend the TS23.558 API to enable the 5GMS AP 301 to discover the media capabilities of the edge data network.

[0148] According to process 900, at operation 9010, the 5GMS AP 301 may send a provisioning request to the ECS 404 using link EDGE-11, and this provisioning request is also a capability request for the media stream processing capability of the EDN. At operation 9020, the ECS 404 returns the provisioning to the 5GMS AP 301 using link EDGE-11 and provides a list of EESs 403. At operation 9030, the 5GMS AP 301 requests registration from one EES 403 included in the list of EESs 403 using link EDGE-10. At operation 9040, this EES 403 registers with the 5GMS AP 301 using link EDGE-10 and provides a list and location of EASs 402, and the list of EASs 402 includes the media stream processing capability of the EDN. At operation 9050, based on the determined media stream processing capability, the 5GMS AP 301 sends a capability response and may request a service from one EAS 402 included in the list of EASs 402 using link EDGE-9. At operation 9050, the EAS 402 starts running the service and confirms the service to the 5GMS AP 301 using link EDGE-9. Moreover, the 5GMS AP 301 connects to the EAS 402 and uses the service.

[0149] Figure 10 illustrates architecture 1000, in which, elements from Figure 4 of architecture 400 are combined with elements from Figure 3 of architecture 300. To avoid unnecessary repetition, redundant descriptions are omitted.

[0150] In Figure 10 , the 5GMS AS 305 and 5GMS AF 306, as well as the ECS 404 and EES 403, may be logical entities. In implementation, all or some of them may be combined. The EAS 402 may be multiple entities. From the perspective of the 5GMS AS 305, all EAS 402 entities are part of the 5GMS AP 301. Link M2 provides the media stream between the 5GMS AS 305 and the 5GMS AP 301. Since some or all applications may run on the EAS 402, the 5GMS AS 305 may connect to the EAS 402 through the 5GMS AP 301.

[0151] Therefore, in the embodiments of the present application, the 5GMS AP 301 may directly discover the list and location of the EAS 402.

[0152] In the embodiments of the present application, the 5GMS AP 301 may discover the capabilities of the EAS 402.

[0153] In an embodiment of the present application, the 5GMS AP 301 may directly request (multiple) services from the EAS 402, and instantiate and use these services.

[0154] In an embodiment of the present application, the 5GMS AP 301 may perform any of the above functions without going through the UE 303.

[0155] In an embodiment of the present application, the 5GMS AP 301 may use the same resources that the UE 303 uses to communicate with the EDN 401, and no new resources are required.

[0156] In an embodiment of the present application, the architecture 300 may be combined with the architecture 400 to provide a mechanism for establishing media services on the edge server and providing media streams between the 5GMS AS 305 and the EAS 402.

[0157] Therefore, an embodiment of the present application provides a method for the 5GMS AP 301 to discover the capabilities of the EDN 401 through new APIs and call flows, where the 5GMS AS 305 may discover a list of available edge servers, provision a subset of them, discover the locations and capabilities of the provisioned edge servers, discover more details about a specific EAS 402, and then request services from the server, where currently standardized resources may be used to perform the above operations.

[0158] An embodiment of the present application provides a method for combining a 5G edge data network and a 5G media data network, where two architectures are combined, and the control and data flows are arranged such that a part of the media application may run on the EAS 402, and sessions may be established using standard procedures of the 5G edge network and the 5G media stream architecture.

[0159] Corresponding to Figures 11 to 13 the embodiment of, the 5G edge architecture discussed above may be extended to allow the following:

[0160] 1. An extended edge platform architecture using the "pseudo" edge-enabled client 1201 in the 5GMS AP 301

[0161] 2. Instantiation of the 5GMS AF 305 and the 5GMS AS 305 in the EAS 402

[0162] 3. Support for similar functions in the MEC host 1202 or the EAS 402

[0163] Figures 11 to 12 Illustrates the architectures 1100 and 1200, where elements of the architecture 400 from Figure 4 and elements from the architecture 400 from Figure 3The components of the architecture 300 are combined, and additional components are added. To avoid unnecessary repetition, redundant descriptions are omitted.

[0164] In Figure 11 the Edge Discovery Function (EDF) 1101 enables the 5GMS AP 301 to discover the EAS 402 and its capabilities. One way to achieve this is to use the pseudo-EEC 1201 as the EDF 1101. Thus, EDGE-10, EDGE-11, and EDGE-12 are, for example, EDGE-1, EDGE-4, and EDGE-5 as shown in Figure 12 In an embodiment of the present application, the EDF 1101 can be implemented with the solution provided by SA2 or SA5. The Edge Orchestrator (EO) 1102 can be an orchestration service for requesting to run a specific application on the EAS 402. The EO 1101 can be provided by a 5G network operator. In an embodiment of the present application, the 5GMS AP 301 provider can include the EO service function. The Edge Host (EH) 1103 can be a service for managing a specific application running on the EAS 402.

[0165] Figure 12 FIG. shows an architecture 1200, which can be an example of the architecture 1100 implemented using MEC. In Figure 12 this, the EDF 1101 is implemented using the EEC functionality, and the link EDGE-1 is used for discovery. The MEC System Manager 1203 is used as the EO 1101. The MEC System Manager 1203 can be implemented by a 5G network operator or by the 5GMS AP 301. The link M1 interface is used as the link EDGE-9. The MEC Host 1202 is used as the EH 1103.

[0166] Figure 13 FIG. illustrates a process 1300 of a call flow for discovering edge data network capabilities. The process 1300 can be executed using the architecture 1200, architecture 1300, or any other architecture as needed.

[0167] According to process 1300, at operation 1310, 5GMS AP 301 may send a provisioning request to ECS 404 using EDF 1101 and link EDGE-1. At operation 1320, ECS 404 provisions 5GMS AP 301 using link EDGE-1 and provides a list of EESs 403. At operation 1330, 5GMS AP 301 requests registration from the EESs 403 included in the list of EESs 403 using link EDGE-4. At operation 1340, EES 403 registers with 5GMS AP 301 using link EDGE-4 via EDF 1101 and provides a list of EASs 402 and a location. At operation 1350, 5GMS AP 301 requests services from the EASs 402 included in the list of EASs 402 using EO 1101 and link EDGE-9. At operation 1350, EAS 402 starts running the service and confirms the service to 5GMS AP 301 using link EDGE-9, and 5GMS AP 301 connects to EAS 402 and uses the service. For example, EAS 402 starts instances of 5GMS AF 306 and 5GMS AS 305, MSH 309 and 5GMS AF 306 and 5GMS AS 305 establish a media session, and start transmitting a media stream.

[0168] In an embodiment of the present application, 5GMS AP 301 may directly use existing edge standards to discover the list, location, and capabilities of EAS 402.

[0169] In an embodiment of the present application, 5GMS AP 301 may directly use existing edge standards to discover the capabilities of EAS 402.

[0170] In an embodiment of the present application, 5GMS AP 301 may directly request (multiple) services from EAS 402 and instantiate and use these services using a standard such as MEC.

[0171] In an embodiment of the present application, 5GMS AP 301 may perform any of the above functions without going through UE 303.

[0172] In an embodiment of the present application, EAS 402 appropriately instantiates a single 5GMS AF 306 and 5GMS AS 305, so that media will flow through this EAS 402.

[0173] In an embodiment of the present application, 5GMS AP 301 may use the same resources that UE 303 uses to communicate with EDN 401 and does not require new resources.

[0174] In an embodiment of the present application, the architecture 300 can be combined with the architecture 400 to provide a mechanism for establishing a media service on an edge server and providing a media stream between the 5GMS AS 305 and the EAS 402.

[0175] Therefore, an embodiment of the present application provides a method for discovering 5G edge data network capabilities and call flows. When discovering 5G edge data network capabilities, the 5GMS AP 301 uses a pseudo-client in the application to implement through existing APIs. When sending a call flow, the 5GMS AP 301 can discover a list of available edge servers, supply a subset of them, discover the locations and capabilities of the supplied edge servers, discover more details about a specific edge application server, and then use a standard orchestration solution to request services from this server. The above operations can be performed using currently standardized resources.

[0176] An embodiment of the present application provides a method for combining a 5G edge data network, a 5G media data network, and an MEC architecture. In this method, these three architectures are combined, and the control and data flows are arranged such that a part of the media application can be run on the EAS 402, and a session can be established using standard processes of the 5G edge network and the 5G media stream architecture.

[0177] Corresponding to Figures 14 to 18 the embodiment, the 5G edge architecture discussed above can be extended to include a 5G Discovery Server (DS) 1401, which can include a list of 5GMS AS 305s and, in an embodiment of the present application, their capabilities. Figures 14 to 18 The embodiment of

[0178] 1. Discover a list of available 5GMS AF 306s in the DS 1401 (and 5GMS AS305 capabilities in some embodiments)

[0179] 2. Discover the media-specific capabilities of a specific 5GMS AS 305

[0180] Figure 14 The figure illustrates the architecture 1400, including some elements of the architecture 300 from Figure 3 and additional elements, the DS 1401. To avoid unnecessary repetition, redundant descriptions are omitted.

[0181] In Figure 14 the DS 1401 can be used to discover available 5GMS AS 305s. As Figure 14As shown, MSH 309 can communicate with the discovery server 1401 using link M10, and 5GMS AP 301 can communicate with DS 1401 using link M9. 5GMS AP 301 or an external application server can use DS 1401 to obtain a list of 5GMS AS 305. Each entry in DS 1401 can include some or all of the following information:

[0182] 1. The name and description of 5GMS AS 305

[0183] 2. The URL of the corresponding 5GMS AF 306

[0184] 3. The capabilities of the corresponding 5GMS AS 305

[0185] Figure 15 Illustrated is architecture 1500, including some components of architecture 300 from Figure 3 and DS 1401. To avoid unnecessary repetition, redundant descriptions are omitted.

[0186] Figures 16 to 18 Illustrated are processes 1600, 1700, and 1800 for the call flow of discovering network capabilities. Processes 1600, 1700, and 1800 can be executed using architecture 1400, architecture 1500, or any other architecture as needed.

[0187] Processes 1600, 1700, and 1800 can extend the TS26.501 API to be able to discover 5G application servers.

[0188] Process 1600 involves the call flow for 5GMS AP 301 to discover network capabilities. According to process 1600, at operation 1610, 5GMS AP 301 can send a request for an AF list to DS 1401 using link M9. At operation 1620, DS 1401 can provide a list of available AFs to 5GMS AP 301 using link M9. At operation 1630, 5GMS AP 301 can send a request for capabilities to 5GMS AF 306 using link M1. At operation 1640, 5GMS AF 306 can send a request for capabilities to 5GMS AS 305 using link M3. At operation 1650, 5GMS AS 305 can send a response including the capabilities to 5GMS AF 306 using link M3. At operation 1660, 5GMS AF 306 can send a response including the capabilities to 5GMS AP 301 using link M1.

[0189] In an embodiment of the present application, the 5GMS awareness application (AA) 302 included on the UE 303 may discover network capabilities through the 5GMS AP 301 (e.g., as shown in process 1700 of Figure 17 ), and the MSH 309 (e.g., as shown in process 1800 of Figure 18 ).

[0190] According to process 1700, at operation 1701, the 5GMS AA 302 may send a request for an AF list to the 5GMS AP 301 using link M8. At operation 1702, the 5GMS AP 301 may send a request for an AF list to the DS 1401 using link M9. At operation 1703, the DS 1401 may provide a list of available AFs to the 5GMS AP 301 using link M9. At operation 1704, the 5GMS AP 301 may provide a list of available AFs to the 5GMS AA 302 using link M8.

[0191] At operation 1705, the 5GMS AA 302 may send a request for capabilities to the 5GMS AP 301 using link M8. At operation 1706, the 5GMS AP 301 may send a request for capabilities to the 5GMS AF 306 using link M8. At operation 1707, the 5GMS AF 306 may send a request for capabilities to the 5GMS AS 305 using link M3. At operation 1708, the 5GMS AS 305 may send a response including the capabilities to the 5GMS AF 306 using link M3. At operation 1709, the 5GMS AF 306 may send a response including the capabilities to the 5GMS AP 301 using link M1. At operation 1710, the 5GMS AP 301 may send a response including the capabilities to the 5GMS AA 302 using link M8.

[0192] According to process 1800, at operation 1801, the 5GMS AA 302 may send a request for an AF list to the MSH 309 using link M6. At operation 1802, the MSH 309 may send a request for an AF list to the DS 1401 using link M10. At operation 1803, the DS 1401 may provide a list of available AFs to the MSH 309 using link M10. At operation 1804, the MSH 309 may provide a list of available AFs to the 5GMS AA 302 using link M6.

[0193] At operation 1805, the 5GMS AA 302 may send a request for capabilities to the MSH 309 using link M8. At operation 1806, the MSH 309 may send a request for capabilities to the 5GMS AF 306 using link M5. At operation 1806, the 5GMS AF 306 may send a request for capabilities to the 5GMS AS 305 using link M3. At operation 1808, the 5GMS AS 305 may send a response including the capabilities to the 5GMS AF 306 using link M3. At operation 1809, the 5GMS AF 306 may send a response including the capabilities to the MSH 309 using link M5. At operation 1810, the MSH 309 may send a response including the capabilities to the 5GMS AA 302 using link M6.

[0194] Table 7 shows the information of the entries in the DS 1401 according to an embodiment:

[0195] Table 7: Discovery Server Information

[0196]

[0197] Table 8 shows the information for the application server capabilities according to an embodiment:

[0198] Table 8: Application Server Capabilities

[0199]

[0200]

[0201] Therefore, the embodiments of the present application provide a method for the 5GMS AP 301 to discover the 5GMS AS 305 through the DS 1401. Through this method, the URLs of the 5GMS AF 306 and additional information including the capabilities of the corresponding application server can be listed.

[0202] The embodiments of the present application provide a method for the 5GMS AA 302 to discover the 5GMS AS 305 through the 5GMS AS 305. Through this method, the 5GMS AA 302 can discover the available 5GMS AS 305 and its capabilities.

[0203] The embodiments of the present application provide a method for the 5GMS AA 302 to discover the 5GMS AS 305 through the MSH 309. Through this method, the 5GMS AA 302 can discover the available 5GMS AS 305 and its capabilities.

[0204] An embodiment of the present application provides a method for transmitting application server and application function information in DS 1401, wherein the URL and other information of 5GMS AS 305 are listed in DS 1401.

[0205] An embodiment of the present application provides a method for discovering 5GMS AS 305 environment parameters, as well as built-in functions and supported repositories, wherein information about the 5GMS AS 305 operating system, environment parameters, and relevant information about running first-party applications, third-party applications, libraries, and functions on 5GMS AS 305 can be discovered.

[0206] Corresponding to Figures 19 to 23 the embodiments relate to various possible deployment scenarios of using networks and edge processing in the 5GMS architecture. The use of the NBMP standard as a specific case of network and edge processing is also proposed.

[0207] Referring to Figure 19 , the NBMP system 1900 includes an NBMP source 1910, an NBMP workflow manager 1920, a function repository 1930, at least one media processing entity 1950, a media source 1960, and a media receiver 1970.

[0208] The NBMP source 1910 can receive instructions from a third-party entity, communicate with the NBMP workflow manager 1920 via the NBMP workflow API 1992, and communicate with the function repository 1930 via the function discovery API 1991. For example, the NBMP source 1910 can send (a) workflow description document(s) (WDD) to the NBMP workflow manager 1920 and read the function descriptions of the functions stored in the function repository 1930, which are media processing functions stored in the memory of the function repository 1930, such as functions of media decoding, feature point extraction, camera parameter extraction, projection methods, seam information extraction, mixing, post-processing, and encoding. The NBMP source 1910 can include at least one processor and a memory, or be implemented by at least one processor and a memory, and the memory stores code that is configured to cause the at least one processor to execute the functions of the NBMP source 1910.

[0209] The NBMP source 1910 can request the NBMP workflow manager 1920 to create a workflow by sending a workflow description document, and the workflow includes tasks 1952 to be executed by at least one media processing entity 1950. The workflow description document can include several descriptors, and each descriptor has several parameters.

[0210] For example, the NBMP source 1910 can select functions stored in the function repository 1930 and send a workflow description document to the NBMP workflow manager 1920, which includes various descriptors for describing details such as input and output data, required functions, and requirements of the workflow. The workflow description document can include a set of task descriptions and a connection map of the inputs and outputs of task 1952, which is executed by at least one media processing entity 1950. When the NBMP workflow manager 1920 receives such information from the NBMP source 1910, the NBMP workflow manager 1920 can create a workflow by instantiating tasks based on function names and connecting the tasks according to the connection map.

[0211] Alternatively or additionally, the NBMP source 1910 can request the NBMP workflow manager 1920 to create a workflow by using a set of keywords. For example, the NBMP source 1910 can send a workflow description document to the NBMP workflow manager 1920, which can include a set of keywords that the NBMP workflow manager 1920 can use to find appropriate functions stored in the function repository 1930. When the NBMP workflow manager 1920 receives such information from the NBMP source 1910, the NBMP workflow manager 1920 can search for appropriate functions to create a workflow by using the keywords that can be specified in the processing descriptors of the workflow description document, and supply tasks and connect these tasks to create a workflow by using other descriptors in the workflow description document.

[0212] The NBMP workflow manager 1920 can communicate with the function repository 1930 via a function discovery API 1993 (which can be the same or different API as the function discovery API 1991), and can communicate with at least one media processing entity 1950 via an API 1994 (such as the NBMP task API). The NBMP workflow manager 1920 can include at least one processor and a memory, or be implemented by at least one processor and a memory, and the memory stores code that is configured to cause the at least one processor to execute the functions of the NBMP workflow manager 1920.

[0213] The NBMP workflow manager 1920 can use the API 1994 to set, configure, manage, and control at least one task 1952 of a workflow that is executed by at least one media processing entity 1950. In an embodiment of the present application, the NBMP workflow manager 1920 can use the API 1994 to update and destroy the task 1952. To configure, manage, and control the tasks 1952 of the workflow, the NBMP workflow manager 1920 can send messages such as requests to at least one media processing entity 1950, where each message can have several descriptors, and each descriptor has several parameters. The tasks 1952 can each include a media processing function 1954 and a configuration 1953 for the media processing function 1954.

[0214] In an embodiment of the present application, after receiving a workflow description document that does not include a task list (e.g., includes a keyword list instead of a task list) from the NBMP source 1910, the NBMP workflow manager 1920 can select tasks based on the task descriptions in the workflow description document to search the function repository 1930 via the function discovery API 1993 to find appropriate functions to run as the tasks 1952 of the current workflow. For example, the NBMP workflow manager 1920 can select tasks based on the keywords provided in the workflow description document. After identifying appropriate functions using the keywords or a set of task descriptions provided by the NBMP source 1910, the NBMP workflow manager 1920 can use the API 1994 to configure the selected tasks in the workflow. For example, the NBMP workflow manager 1920 can extract configuration data from the information received from the NBMP source and configure the task 1952 based on the configuration data.

[0215] At least one media processing entity 1950 can be configured to receive media content from a media source 1960, process the media content according to a workflow including the tasks 1952 created by the NBMP workflow manager 1920, and output the processed media content to a media receiver 1970. Each of the at least one media processing entity 1950 can include at least one processor and a memory, or be implemented by at least one processor and a memory, where the memory stores code that is configured to cause the at least one processor to execute the functions of the media processing entity 1950.

[0216] The media source 1960 can include a memory for storing media and can be integrated with or separated from the NBMP source 1910. In an embodiment of the present application, the NBMP workflow manager 1920 can notify the NBMP source 1910 when preparing the workflow, and the media source 1960 can send media content to at least one media processing entity 1950 based on the notification of preparing the workflow.

[0217] The media receiver 1970 may include or be implemented by at least one processor and at least one display, which is configured to display media processed by at least one media processing entity 1950.

[0218] As discussed above, messages from the NBMP source 1910 (e.g., a workflow description document for requesting creation of a workflow) to the NBMP workflow manager 1920 and messages from the NBMP workflow manager 1920 to at least one media processing entity 1950 (e.g., for causing the workflow to be executed) may include a number of descriptors, and each descriptor may have a number of parameters. In some cases, communication between any components of the NBMP system 1900 that uses the API may include a number of descriptors, and each descriptor may have a number of parameters.

[0219] Figures 20 to 23 Architectures 2000, 2100, 2200, and 2300 are illustrated, and elements from Figure 3 architecture 300 are combined with elements from system 1900, and additional elements are added. To avoid unnecessary repetition, redundant descriptions are omitted.

[0220] Figure 20 Architecture 2000 is illustrated, in which network processing is included in the application server. As Figure 20 shown, the NMBP source 1910, the NBMP workflow manager 1920, and at least one media processing entity (MPE) 1950 are located in the 5GMS AP 301.

[0221] The procedures for establishing, operating, and tearing down a session may include:

[0222] 1. The 5GMS AA 302 issues a request to the NMBP source 1910 via M8.

[0223] 2. The NMBP source 1910 establishes a workflow description (WD) and requests the NMBP source 1910 to instantiate the workflow.

[0224] 3. The NBMP workflow manager 1920 discovers various MPEs 1950 and finds a sufficient number of MPEs 1950 to run the workflow.

[0225] 4. The NBMP workflow manager 1920 instantiates the workflow.

[0226] 5. The NBMP workflow manager 1920 responds to the NMBP source 1910 with the updated WD.

[0227] 6. The NMBP source 1910 responds to the 5GMS AA 302 with 5GMS AF 306 and 5GMS AS 305 information.

[0228] 7. The 5GMS AA 302 requests the MSH 309 to establish a session.

[0229] 8. The MSH 309 establishes the session and acknowledges the 5GMS AA 302.

[0230] 9. The 5GMS AA 302 starts content ingestion.

[0231] 10. The session runs.

[0232] 11. The 5GMS AA 302 requests the NMBP source 1910 to end the session.

[0233] 12. The NMBP source 1910 requests the NMBP workflow manager 1920 to end the workflow.

[0234] 13. The NMBP workflow manager 1920 acknowledges the stop of the workflow.

[0235] 14. The NMBP source 1910 acknowledges that the 5GMS AA 302 stops the workflow.

[0236] 15. The 5GMS AA 302 requests the MSH 309 to stop the session.

[0237] Table 9 shows the standard interfaces required in this scenario:

[0238] Table 9: Standard APIs required for the entire workflow processing in the application server

[0239]

[0240] Figure 21 The architecture 2100 is illustrated, where the NMBP source 1910 and the NMBP workflow manager 1920 are included in the 5GMS AP 301. As Figure 21 shown, the NMBP source 1910 and the NMBP workflow manager 1920 are located in the 5GMS AP 301, and the MPE 1950 is located in the 5GMS AS 305.

[0241] The procedures for establishing, operating, and tearing down a session may include:

[0242] 1. The 5GMS AA 302 issues a request to the workflow source (NMBP source 1910) via M8.

[0243] 2. The NMBP source 1910 creates a Workflow Description (WD) and requests the NMBP Workflow Manager 1920 to instantiate the workflow.

[0244] 3. The NMBP Workflow Manager 1920 discovers a 5GMS AS 305 with a sufficient number of MPEs 1950 to run the workflow.

[0245] 4. The NMBP Workflow Manager 1920 instantiates the workflow via the 5GMS AS 305.

[0246] 5. The NMBP Workflow Manager 1920 responds to the NMBP source 1910 with the updated WD.

[0247] 6. The NMBP source 1910 responds to the 5GMS AA 302 with 5GMS AF 306 and 5GMS AS 305 information.

[0248] 7. The 5GMS AA 302 requests the MSH 309 to establish a session.

[0249] 8. The MSH 309 establishes the session and acknowledges the 5GMS AA 302.

[0250] 9. The 5GMS AA 302 starts ingesting content.

[0251] 10. The session runs.

[0252] 11. The 5GMS AA 302 requests the NMBP source 1910 to end the session.

[0253] 12. The NMBP source 1910 requests the NMBP Workflow Manager 1920 to end the workflow.

[0254] 13. The NMBP Workflow Manager 1920 requests the 5GMS AS 305 to stop the MPE 1950.

[0255] 14. The NMBP Workflow Manager 1920 acknowledges the stopping of the workflow.

[0256] 15. The NMBP source 1910 acknowledges that the 5GMS AA 302 has stopped the workflow.

[0257] 16. The 5GMS AA 302 requests the MSH 309 to stop the session.

[0258] Table 10 shows the standard interfaces required in this scenario:

[0259] Table 10: Standard APIs Required When the MPE 1950 Is in the 5GMS AS 305

[0260]

[0261] Note that N2 can be a closed API implemented by an AP operator agreement.

[0262] Figure 22 An architecture 2200 is illustrated, in which the NMBP workflow manager 1920 and the MPE 1950 are included in the 5GMS AS 305.

[0263] 1. The 5GMS AA 302 issues a request to the workflow source (NMBP source 1910) via M8.

[0264] 2. The NMBP source 1910 constructs a workflow description (WD) and discovers the 5GMS AS 305 that can execute the media.

[0265] 3. The NMBP source 1910 requests the appropriate 5GMS AS 305 NMBP workflow manager 1920 to instantiate the workflow.

[0266] 4. The NMBP workflow manager 1920 instantiates the workflow inside the 5GMS AS 305.

[0267] 5. The NMBP workflow manager 1920 responds to the NMBP source 1910 with the updated WD.

[0268] 6. The NMBP source 1910 responds to the 5GMS AA 302 with 5GMS AF 306 and 5GMS AS 305 information.

[0269] 7. The 5GMS AA 302 requests the MSH 309 to establish a session.

[0270] 8. The MSH 309 establishes the session and confirms the 5GMS AA 302.

[0271] 9. The 5GMS AA 302 starts to ingest content.

[0272] 10. The session runs

[0273] 11. The 5GMS AA 302 requests the NMBP source 1910 to end the session.

[0274] 12. The NMBP source 1910 requests the NMBP workflow manager 1920 of the 5GMS AS 305 to end the workflow.

[0275] 13. The NMBP workflow manager 1920 confirms the stop of the workflow.

[0276] 14. The NMBP source 1910 confirms that the 5GMS AA 302 stops the workflow.

[0277] 15. The 5GMS AA 302 requests the MSH 309 to stop the session.

[0278] …

[0279] Table 11 shows the standard interfaces required in this scenario:

[0280] Table 11: NMBP Workflow Manager 1920 and MPE 1950 in 5GMS AS 305

[0281]

[0282] Figure 23 The architecture 2300 is illustrated, where the NMBP source 1910 is included in the MSH 309, and the NMBP Workflow Manager 1920 and the MPE 1950 are included in the 5GMS AS 305.

[0283] The procedures for establishing, operating, and tearing down a session may include:

[0284] 1. The 5GMS AA 302 requests the MSH 309 to start a session via M6.

[0285] 2. The NMBP source 1910 constructs a Workflow Description (WD) and discovers that the 5GMS AS 305 for the media can be executed via M5 or other means.

[0286] 3. The NMBP source 1910 of the MSH 309 requests the NMBP Workflow Manager 1920 of the appropriate 5GMS AS 305 to instantiate the workflow.

[0287] 4. The NMBP Workflow Manager 1920 instantiates the workflow inside the 5GMS AS 305.

[0288] 5. The NMBP Workflow Manager 1920 responds to the MSH 309 with the updated WD.

[0289] 6. The MSH 309 responds to the 5GMS AA 302.

[0290] 7. The 5GMS AA 302 requests the MSH 309 to establish the session.

[0291] 8. The MSH 309 establishes the session and acknowledges the 5GMS AA 302.

[0292] 9. The 5GMS AA 302 starts ingesting content.

[0293] 10. The session runs.

[0294] 11. The 5GMS AA 302 requests the MSH 309 to end the session.

[0295] 12. The NMBP source 1910 of the MSH 309 requests the NMBP workflow manager 1920 of the 5GMS AS 305 to end the workflow.

[0296] 13. The NMBP workflow manager 1920 confirms the stopping of the workflow.

[0297] 14. The MSH 309 confirms that the 5GMS AA 302 stops the workflow.

[0298] Table 12 shows the standard interfaces required in this scenario:

[0299] Table 12: Workflow source in MSH 309, NMBP workflow manager 1920 and MPE 1950 in 5GMS AS 305

[0300]

[0301] Note that M5 has the support of the workflow manager API.

[0302] Table 13 shows an overview diagram of the deployment scenario.

[0303] Table 13: Overview diagram of the deployment scenario

[0304]

[0305] Note that N2 can be a closed API implemented by the AP operator protocol. Also, note that M5 is supported by the NBMP workflow manager API.

[0306] Other variations of the above scenario can be adopted. For example, the NMBP workflow manager 1920 and MPE 1950 can be supported in the 5GMS AS 305, while the NMBP source 1910 can be supported in the 5GMS AA 302, or all NMBP sources 1910, NMBP workflow managers 1920 and MPE 1950 can be supported in the 5GMS AS 305.

[0307] In the 5GMS general architecture (5GMSA), there can be more than one pair of 5GMS AF 306 and 5GMS AS 305. In these cases, the NMBP source 1910 and / or the NMBP workflow manager 1920 must discover the capabilities of multiple pairs of 5GMS AF 306 and 5GMS AS 305 for running the network media workflow on the most suitable 5GMS AS 305.

[0308] Accordingly, embodiments of the present application provide a method for deployment in any network or edge-based media processing, such as NBMP workflow management in a 5G S-MA environment, considering four different scenarios, including: implementing a) the entire network processing module in the application server; b) the media processing service in the 5G MSA 305; c) the workflow manager and media processing service in the 5G MSA 305; and d) the NBMP source 1910 in the MSH 309, and both the NBMP workflow manager 1920 and the MPE 1950 are in the 5G MSA 305. In each scenario, the workflow processing module can be implemented in different modules of the 5G S-MA architecture, where, for each scenario, an API between network processing and the 5G MSA is defined, and the API is divided into an API according to the 3GPP 3G S-MA standard, an internal API of each module, and a dedicated API between service providers and operators.

[0309] For each of the above four scenarios, embodiments of the present application provide respective methods, including call flows for establishment, management, tear-down of workflow processing, and 5G MSA federated sessions, where, in each case, call flows, workflow sessions, and FLUS sessions are established, and appropriate information is exchanged through the APIs defined in the methods to establish and manage the federated sessions, and the content is streamed from the device to the network using the 5G MSA and then processed using network workflow processing in the cloud or edge service.

[0310] Embodiments of the present application provide a method for implementing the NBMP standard as network workflow processing to deploy the 5G MSA.

[0311] Figure 24 is a flowchart of an example process 2400 for managing the capabilities of a media stream transmission network. In some implementations, Figure 24 at least one processing block can be performed by at least one element of any of the systems or architectures discussed above.

[0312] As Figure 24 shown, process 2400 can include receiving a capability request for the media stream processing capabilities of an edge data network (EDN) (block 2402). In embodiments of the present application, the EDN can correspond to the EDN 401 discussed above.

[0313] As Figure 24 further shown, process 2400 can include determining the media stream processing capabilities of the EDN (block 2404).

[0314] As Figure 24 further shown, process 2400 can include sending a capability response based on the determined media stream processing capabilities (block 2406).

[0315] As Figure 24 Figure 24 further shown, process 2400 may include receiving a media processing workflow request (block 2408) based on an ability response.

[0316] As Figure 24 Figure 24 further shown, process 2400 may include establishing a media stream session (block 2410) according to the media processing workflow request.

[0317] As Figure 24 Figure 24 further shown, process 2400 may include streaming media content (block 2412) based on the media stream session.

[0318] In an embodiment of the present application, the media stream processing capabilities include at least one of the following: available hardware resources, environmental characteristics of the EDN, current throughput of an edge server associated with the EDN, current latency range of the edge server, available media processing function libraries, functional descriptions of at least one function, and characteristics of the at least one function.

[0319] In an embodiment of the present application, the receiving of the ability request may include receiving a first ability request by an edge application server (EAS) from a media session processor of an application client, and determining the media stream processing capabilities, which may include sending a second ability request by the EAS to a media stream application function or a media stream application server included in the EAS, and determining the media stream processing capabilities of the EDN by the media stream application function or the media stream application server; sending an ability response based on the determined media stream processing capabilities, specifically including: sending a response including the media stream processing capabilities of the EDN by the EAS to the application client or the media session processor. In an embodiment of the present application, the EAS may correspond to the EAS 402 discussed above, the media stream application function may correspond to the 5GMS AF discussed above, and the media stream application server may correspond to the 5GMS AS discussed above.

[0320] In an embodiment of the present application, the first ability request may be sent using an edge application programming interface (API), and the second ability request may be sent using a media stream API.

[0321] In an embodiment of the present application, the ability request may be received by an edge configuration server (ECS) from a media stream application provider (AP). In an embodiment of the present application, the AP may correspond to the 5GMS AP 301 discussed above, and the ECS may correspond to the ECS 404 discussed above.

[0322] In an embodiment of the present application, the determination of media stream processing capabilities may include sending a list of multiple Edge-Enabled Servers (EESs) from the ECS to the AP; receiving, by the ECS, a registration request for one of the multiple EESs from the AP; and sending a list of multiple EASs from the EES to the AP, the list of multiple EASs including the media stream processing capabilities of the EDN. In an embodiment of the present application, the EES may correspond to the EES 403 discussed above.

[0323] In an embodiment of the present application, based on the determined media stream processing capabilities, a sending capability response may be sent, which may specifically include: transmitting a service request from the AP to one of the multiple EASs based on the list of multiple EASs. In an embodiment of the present application, the service request may correspond to the 9050 and 1350 discussed above.

[0324] In an embodiment of the present application, sending a list of multiple EASs from the EES to the AP may specifically include: sending the list of multiple EASs to the AP through an Edge Discovery Function (EDF). In an embodiment of the present application, the EDF may correspond to the EDF 1101 discussed above.

[0325] In an embodiment of the present application, the AP includes an EDF.

[0326] Although Figure 24 example boxes of process 2400 are shown, in some implementations, process 2400 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently compared to those depicted in Figure 24 . Additionally or alternatively, two or more boxes of process 2400 may be executed in parallel.

[0327] Furthermore, an example method according to an embodiment of the present application may be implemented by a processing circuit (e.g., at least one processor or at least one integrated circuit). In one example, at least one processor executes a program stored in a non-volatile computer-readable medium to perform at least one example method.

[0328] The techniques described above may be implemented as computer software using computer-readable instructions and physically stored in at least one computer-readable medium.

[0329] Embodiments of the present application may be used alone or in any combination. Further, each embodiment (and its method) may be implemented by a processing circuit (e.g., at least one processor or at least one integrated circuit). In one example, at least one processor executes a program stored in a non-volatile computer-readable medium.

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

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

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

[0333] Elements, acts, or instructions used herein should not be construed as critical or essential, unless explicitly described as such. Further, as used herein, the articles "a" and "an" are intended to include at least one item, and may be used interchangeably with "at least one." Also, as used herein, the term "group" is intended to include at least one item (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and may be used interchangeably with "at least one." The term "one" or similar language is used where only one item is meant. Further, as used herein, the terms "having," "comprising," "containing," etc. are intended to be open-ended terms. Additionally, the phrase "based on" is intended to mean "at least partially based on," unless otherwise explicitly stated.

Claims

1. A method for managing the capabilities of a media stream transmission network, characterized in that, the method includes: receiving, by an Edge Configuration Server (ECS), from a 5G media stream Application Provider (AP), through an Edge Discovery Function (EDF) included in the AP, a capability request for the media stream processing capabilities of an Edge Data Network (EDN), wherein a Pseudo Edge Enablement Client (EEC) is used as the EDF; sending, from the ECS to the AP, a list of multiple Edge Enablement Servers (EESs), and receiving, by the ECS from the AP, a registration request for one of the multiple EESs; sending, from the EES, through the Pseudo EEC, a list of multiple Edge Application Servers (EASs) to the AP, the list of multiple EASs including the media stream processing capabilities of the EDN; sending a capability response based on the media stream processing capabilities; receiving a media processing workflow request based on the capability response; establishing a media stream session according to the media processing workflow request; and performing streaming transmission of media content based on the media stream session.

2. The method according to claim 1, characterized in that, the media stream processing capabilities include at least one of the following: available hardware resources, environmental characteristics of the EDN, current throughput of multiple EASs, current latency range of multiple EASs, and available media processing function libraries.

3. The method according to claim 1, characterized in that, the sending a capability response based on the media stream processing capabilities includes: sending a service request from the AP to one of the multiple EASs based on the list of multiple EASs.

4. An apparatus for managing the capabilities of a media stream transmission network, characterized in that, it includes: a first receiving module, configured to receive, by an Edge Configuration Server (ECS), from a 5G media stream Application Provider (AP), through an Edge Discovery Function (EDF) included in the AP, a capability request for the media stream processing capabilities of an Edge Data Network (EDN), wherein a Pseudo Edge Enablement Client (EEC) is used as the EDF; a determination module, including: a second sending module, configured to send a list of multiple Edge Enablement Servers (EESs) from the ECS to the AP; a fourth receiving module, configured to receive, by the ECS from the AP, a registration request for one of the multiple EESs; a third sending module, configured to send a list of multiple Edge Application Servers (EASs) to the AP from the EES, through the Pseudo EEC, the list of multiple EASs including the media stream processing capabilities of the EDN; a first sending module, configured to send a capability response based on the media stream processing capabilities; a second receiving module, configured to receive a media processing workflow request based on the capability response; an establishment module, configured to establish a media stream session according to the media processing workflow request; and a streaming transmission module, configured to perform streaming transmission of media content based on the media stream session.

5. The apparatus according to claim 4, characterized in that, The media stream processing capabilities include at least one of the following: available hardware resources, the environmental characteristics of the EDN, the current throughput of multiple EASs, the current latency range of multiple EASs, and the available media processing function library.

6. The apparatus according to claim 4, wherein, the first sending module is configured to send a service request from the AP to one of the multiple EASs based on a list of the multiple EASs.

7. A computer device, wherein, it includes a processor and a memory, and at least one instruction is stored in the memory, and the at least one instruction is loaded and executed by the processor to implement the method according to any one of claims 1-3.

8. A non-volatile computer-readable medium, wherein, instructions are stored thereon, and the instructions include at least one instruction, and when the at least one instruction is executed by at least one processor of a device for managing the capabilities of a media stream transmission network, the at least one processor is caused to execute the method according to any one of claims 1-3.

Images