Live streaming transmission method, device, electronic device and computer readable medium

Abstract

The present application provides a method, device, electronic device and computer-readable storage medium for live streaming of user-generated content through a media streaming network. The method includes: sending a live streaming request corresponding to the user-generated content to a 5GMS application provider (AP) through a fifth generation media streaming (5GMS) aware application; receiving an edge application server (EAS) description corresponding to the live streaming request from a 5GMS AP through a 5GMS aware application, wherein the EAS description indicates a service category (SC) corresponding to the live streaming request in multiple SCs; selecting a 5GMS application server (AS) based on the SC through a 5GMS aware application; and performing live streaming of the user-generated content to the 5GMS AS through a 5GMS network according to the SC.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 187,820 filed in the U.S. Patent and Trademark Office on May 12, 2021, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to fifth generation media streaming (5 th The present invention relates to 5GMS (5 Generation Media Streaming), and in particular, to a method, device, electronic device and computer-readable medium for live streaming of user-generated content through a media streaming network. Background Art

[0004] Networks and cloud platforms are used to run various applications. However, there are no existing standards for describing the characteristics of networks or cloud platforms or their elements.

[0005] Third Generation Partnership Project (3 rd 3GPP TS23.558 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture for implementing edge applications (Release 17), V2.0.0) defines a general architecture for implementing edge applications, including discovering the hardware capabilities of edge elements. 3GPP TS26.501 (3GPP TS26.501, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G Media Streaming (5GMS); General Description and Architecture (Release 16), V16.3.1) defines a general architecture for 5G media streaming applications, and TS26.512 defines the application programming interface (API) calls for the architecture. 3GPP TR 26.803 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on 5G Media Streaming Extensions for Edge Processing (Release 17) V1.5.1) also covers the fifth generation of media streaming (5 th Generation Media Streaming, 5GMS) and edge processing.

[0006] The current 5G edge architecture defined in 3GPP TS23.558 only defines the discovery of edge applications by application clients. 3GPP TS26.501 only defines the media streaming architecture. However, there is no definition for the discovery, instantiation and management of media services on edge resources for 5GMS application service providers. Summary of the invention

[0007] According to one or more embodiments, a method for live streaming of user-generated content through a media streaming network is provided, comprising: sending a live streaming request corresponding to the user-generated content to a 5GMS application provider (AP) through a fifth generation media streaming (5GMS)-aware application; receiving an edge application server (EAS) description (Profile) corresponding to the live streaming request from the 5GMS AP through the 5GMS-aware application, wherein the EAS description indicates a service category (SC) corresponding to the live streaming request among multiple SCs; selecting a 5GMS application server (AS) based on the SC through the 5GMS-aware application; and live streaming the user-generated content to the 5GMS AS through the 5GMS network according to the SC.

[0008] According to one or more embodiments, a device for live streaming of user-generated content through a media streaming network is provided, including: a sending module, which sends a live streaming request corresponding to the user-generated content to a 5GMS application provider (AP) through a fifth-generation media streaming (5GMS)-aware application; a receiving module, which receives an edge application server (EAS) description corresponding to the live streaming request from a 5GMS AP through a 5GMS-aware application, wherein the EAS description indicates a service category (SC) corresponding to the live streaming request among multiple SCs; a selection module, which selects a 5GMS application server (AS) based on the SC through the 5GMS-aware application; and an execution module, which is used to perform live streaming of the user-generated content to the 5GMS AS through the 5GMS network according to the SC.

[0009] According to one or more embodiments, an electronic device is provided, comprising: at least one memory for storing program code; and at least one processor for implementing the aforementioned method for live streaming of user-generated content through a media streaming network when executing the program code.

[0010] According to one or more embodiments, a non-transitory computer-readable medium storing instructions is provided, and when the instructions are executed by a processor, the instructions are used to implement the aforementioned method of live streaming of user-generated content through a media streaming network.

[0011] It can be seen that the method for live streaming of user-generated content through a media streaming network provided in the present application can obtain the category of service required by the live stream according to the edge application server (EAS) description corresponding to the live stream request, and then determine the 5GMS application server used for live streaming according to the service category. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Additional features, properties, and various advantages of the disclosed subject matter will become more apparent from the following detailed description and accompanying drawings, in which:

[0013] Figure 1 It is a diagram of an environment in which the methods, devices, and systems described herein can be implemented according to an embodiment of the present application.

[0014] Figure 2 yes Figure 1 A block diagram of example components of one or more devices of the present invention.

[0015] Figure 3 It is a block diagram of a media architecture for media streaming according to an embodiment of the present application.

[0016] Figure 4 The fifth generation (5 th Figure 1. Diagram of 5G (5G) edge network architecture.

[0017] Figure 5 This is a diagram of a 5G media streaming architecture for implementing edge applications according to an embodiment of the present application.

[0018] Figure 6 The signaling flow chart of an example process of performing live streaming of user-generated content through a media streaming network according to an embodiment of the present application.

[0019] Figure 7 4 is a flowchart of an example process of performing live streaming of user-generated content through a media streaming network according to an embodiment of the present application. Specific embodiments

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

[0021] The user device 110 includes one or more devices 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 smart phone, 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 can receive information from the platform 120 and / or send information to the platform 120.

[0022] The platform 120 includes one or more devices as described elsewhere herein. In some implementations, the platform 120 may include a cloud server or cloud server group. In some implementations, the platform 120 may be designed to be modular so that software components may be swapped in or out according to specific needs. Thus, the platform 120 may be easily and / or quickly reconfigured for different uses.

[0023] In some implementations, as shown, the platform 120 can be hosted in a cloud computing environment 122. It is worth noting that while the implementations described herein describe the platform 120 as being hosted in a cloud computing environment 122, in some implementations, the platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0024] Cloud computing environment 122 includes an environment hosting platform 120. Cloud computing environment 122 may provide computing, software, data access, storage, and other services that do not require end users (e.g., user devices 110) to be aware of the physical location and configuration of the systems and / or devices hosting platform 120. As shown, cloud computing environment 122 may include a set of computing resources 124 (collectively, “computing resources 124” and individually, “computing resource 124”).

[0025] The computing resources 124 include one or more personal computers, workstation computers, server devices, or other types of computing devices and / or communication devices. In some implementations, the computing resources 124 can host the platform 120. Cloud resources may include: computing instances executed in the computing resources 124, storage devices provided in the computing resources 124, data transmission devices provided by the computing resources 124, etc. In some implementations, the computing resources 124 can communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0026] If further Figure 1As shown in the figure, the computing resources 124 include a group of cloud resources, such as one or more applications ("Application, APP") 124-1, one or more virtual machines ("Virtual Machine, VM") 124-2, virtualized storage devices ("Virtualized Storage, VS") 124-3, one or more hypervisors ("Hypervisor, HYP") 124-4, etc.

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

[0028] 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 and correspondence of the virtual machine 124-2 to any real machine. The system virtual machine can provide a complete system platform that supports the execution of a complete operating system ("Operating System, OS"). The 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., a user device 110) and can manage the infrastructure of the cloud computing environment 122, such as data management, synchronization, or long-duration data transfer.

[0029] The virtualized storage device 124-3 includes one or more storage systems and / or one or more devices using virtualization technology within the storage system or device of the computing resource 124. In some implementations, within the context of the storage system, the types of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the extraction (or separation) of logical storage from physical storage, so that the storage system can be accessed without considering physical storage or heterogeneous structures. Separation may allow managers of storage systems flexibility in how managers manage storage for end users. File virtualization may eliminate the dependency between data accessed at the file level and the location where the file is physically stored. This may enable optimization of storage usage, server consolidation, and / or performance of non-disruptive file migration.

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

[0031] The network 130 includes one or more wired networks and / or wireless networks. For example, the network 130 may include a cellular network (e.g., a fifth generation (Fifth Generation, 5G) network, a long-term evolution (Long-Term Evolution, LTE) network, a third generation (Third Generation, 3G) network, a code division multiple access (Code Division Multiple Access, CDMA) network, etc.), a public land mobile network (Public Land Mobile Network, PLMN), a local area network (Local Area Network, LAN), a wide area network (Wide Area Network, WAN), a metropolitan area network (Metropolitan Area Network, MAN), a telephone network (e.g., a public switched telephone network (Public Switched Telephone Network, PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-based network, etc. and / or a combination of these or other types of networks.

[0032] Figure 1 The number and arrangement of devices and networks shown in FIG. 1 are provided as examples. Figure 1 There may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than those shown in FIG. Figure 1 Two or more devices shown in the figure may be implemented in a single device, or Figure 1 A single device shown in the environment 100 may be implemented as multiple distributed devices. Additionally or alternatively, one or more devices of a group of devices (eg, one or more devices) of the environment 100 may perform one or more functions described as being performed by another group of devices of the environment 100.

[0033] Figure 2 yes Figure 1 Device 200 may correspond to user device 110 and / or platform 120. Figure 2As shown, device 200 may 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 .

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

[0035] 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, a magnetic tape, and / or another type of non-transitory computer-readable medium and a corresponding drive.

[0036] Input components 250 include components that allow device 200 to receive information, for example, via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, input components 250 may include sensors for sensing information (e.g., a Global Positioning System (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 260 include components that provide output information from device 200 (e.g., a display, a speaker, and / or one or more light-emitting diodes (LEDs)).

[0037] The communication interface 270 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable the device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection. The communication interface 270 can 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.

[0038] Device 200 may perform one or more processes described herein. Device 200 may perform these processes in response to processor 220 executing software instructions stored by non-transitory computer-readable media such as memory 230 and / or storage component 240. Computer-readable media is defined herein as non-transitory memory devices. Memory devices include memory space within a single physical storage device or memory space distributed across multiple physical storage devices.

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

[0040] Figure 2 The number and arrangement of components shown in FIG. 1 are provided as examples. In practice, Figure 2Device 200 may include additional components, fewer components, different components, or differently arranged components than the components shown in . Additionally or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.

[0041] The 5G Media Streaming (5GMS) system may be a component of application functions, application servers, and interfaces from the 5G Media Streaming architecture, which supports downlink media streaming services or uplink media streaming services, or both downlink media streaming services and uplink media streaming services. A 5GMS application provider may include a party that interacts with the functions of the 5GMS system and provides a 5GMS-aware application that interacts with the functions of the 5GMS system. A 5GMS-aware application may refer to an application provided by a 5GMS application provider in a user equipment (UE), which contains the service logic of the 5GMS application service and interacts with other 5GMS clients and network functions via interfaces and application programming interfaces (APIs) defined in the 5GMS architecture. The 5GMS client may refer to a UE function that is a 5GMS downlink (5GMS Downlink, 5GMSd) client or a 5GMS uplink (5GMS Uplink, 5GMSu) client, or both a 5GMS downlink client and a 5GMS uplink client.

[0042] 5GMSd client may refer to such UE functionality, which includes at least a 5G media streaming player and a media session processor for downlink streaming, and which can be accessed through a well-defined interface / API. 5GMSu client may refer to the initiator of a 5GMSu service that can be accessed through a well-defined interface / API. 5GMSu media streamer may refer to such UE functionality, which enables uplink delivery of streaming media content to the Application Server (AS) function of the 5GMS application provider, and which interacts with both the 5GMSu aware application for media capture and subsequent streaming and the media session processor for media session control.

[0043] Dynamic policy may refer to dynamic policy and charging control (PCC) rules for uplink or downlink application flows during a media session. A drain session may refer to an uplink media streaming session from a 5GMS AS to a 5G MSu application provider. An intake session may refer to a session in which media content is uploaded to a 5GMSd AS. A policy template may refer to a set of (semi-static) policy or control function (PCF) / network exposure function (NEF) API parameters that are specific to a 5GMS application provider and the resulting PCC rules. A policy template ID may identify the desired policy template, which is used by a 5GMSd application function (AF) to select the appropriate PCF / NEF API for the 5G system so that the PCF can compile the desired PCC rules. A media player entry may refer to a document defining a media presentation or a pointer to the document (e.g., a Media Presentation Description (MPD) of DASH (Dynamic Adaptive Streaming over Hypertext Transfer Protocol, DASH) or a Uniform Resource Locator (URL) of a video clip file). A media streamer entry may refer to a pointer (e.g., in the form of a URL) defining an entry point for an uplink media streaming session. A presentation entry may refer to a document defining an application presentation, such as an HTML5 document, or a pointer to the document.

[0044] A provisioning session may refer to a data structure provided by a 5GMSd application provider at an interface (M1d) that configures 5GMSd features related to a set of 5GMSd-aware applications. A 5GMSd media player may refer to a UE function that enables playback and presentation of media presentations based on media playback entries, and opens some basic controls such as play, pause, seek, stop to 5GMSd-aware applications. Server access information may refer to a set of parameters and addresses (including 5GMSd AF addresses and 5GMSd AS addresses) required to activate the reception of a streaming session. Service and content discovery may refer to functions and processes provided by a 5GMSd application provider to a 5GMS-aware application that enables an end user to discover available streaming services and content offers and select a specific service or content item for access. Service notification may refer to a process conducted between a 5GMS-aware application and a 5GMS application provider that enables a 5GMS-aware application to obtain 5GMS service access information directly or in the form of a reference to the information.

[0045] A third party player may refer to a portion of an application that uses an API to exploit selected 5GMSd functionality to playback media content. A third party uplink streamer may refer to a portion of an application that uses an API to exploit selected 5GMSu functionality to capture and stream media content.

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

[0047] 5GMS AF 306 and 5GMS AS 305 can be data network (DN) 307 functions. Functions in trusted DNs can be trusted by the operator network. Therefore, AFs in trusted DNs can communicate directly with all 5G core functions. Functions in external DNs can communicate only with 5G core functions via NEF (Network Exposure Function, NEF) 308 using link 320.

[0048] The media architecture 300 can connect the UE 303 internal functions and related network functions for 5G media uplink streaming. Therefore, the media architecture 300 can include many functions. For example, the 5GMS client 304 on the UE 303 can be the initiator of the 5GMS service that can be accessed through the interface / API. The 5GMS client 304 can include two sub-functions: a media session processor 309 and a media streamer 310. The media session processor 309 can communicate with the 5GMS AF 306 to establish, control and support the delivery of media sessions. The media session processor 309 can open an API that can be used by the 5GMS-aware application 302. The media streamer 310 can communicate with the 5GMS AS 305 to stream media content and provide services for media capture and streaming to the 5GMS-aware application 302, and provide services for media session control to the media session processor 309. The 5GMS-aware application 302 can control the 5GMS client 304 by implementing external application or content service provider specific logic and enabling the establishment of a media session. For example, the 5GMS AS 305 can host 5G media functions and can be implemented as a content delivery network (CDN). The 5GMS application provider 301 can be an external application or content-specific media function that uses 5GMS to stream media from a 5GMS-aware application 302, such as media storage, consumption, transcoding, and redistribution. The 5GMS AF 306 can provide various control functions to the media session processor 309 on the UE 303 and / or to the 5GMS application provider 301. The 5GMS AF 306 can relay or initiate requests for different PCF 311 processing, or interact with other network functions. The 5GMS AF 306 can be connected to the PCF 311 via the N5 interface 319.

[0049] The media architecture 300 may include many different interfaces. For example, link 321 may be associated with M1u, which may be a 5GMS supply API opened by 5GMS AF 306 to supply the use of the media architecture 300 and obtain feedback. Link 322 may be associated with M2u, which may be a 5GMS release API opened by 5GMS AS 305 and used when a 5GMS AS 305 in a trusted DN such as DN 307 is selected to receive content for a streaming service. Link 323 may be associated with M3u, which may be an internal API for exchanging information for content hosted on 5GMS AS 305 within a trusted DN such as DN 307. Link 324 may be associated with M4u, which may be a media uplink streaming API opened by 5GMS AS 305 to the media streamer 310 to stream media content. Link 325 may be associated with M5u, which may be a media session handling API opened by the 5GMS AF 306 to the media session processor for media session handling, control and assistance, and also include appropriate security mechanisms such as authorization and authentication. Link 326 may be associated with M6u, which may be a UE 303 media session handling API opened by the media session processor 309 to the 5GMS-aware application 302 to utilize 5GMS functions. Link 327 may be associated with M7u, which may be a UE media streamer API opened by the media streamer 310 to the 5GMS-aware application 302 and the media session processor 309 to utilize the media streamer 310. Link 328 may be associated with M8u, which may be an application API for information exchange between the 5GMS-aware application 302 and the 5GMS application provider 301, for example to provide service access information to the 5GMS-aware application 302. UE 303 may also be implemented in a self-contained manner such that interfaces M6u and M7u are not disclosed.

[0050] Figure 4401 is a diagram of a 5G edge network architecture 400 according to an embodiment. Edge Data Network (EDN) 401 is a local data network. EDN 401 includes an Edge Application Server (EAS) 402 and an Edge Enabler Server (EES) 403. Edge Configuration Server (ECS) 404 provides configuration related to EES 403, including details of EDN 401 hosting EES 403. User Equipment (UE) 405 includes an Application Client (AC) 406 and an Edge Enabler Client (EEC) 407. EAS 402, EES 403, and ECS 404 can interact with a 3GPP core network 408.

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

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

[0053] ECS 404 provides support functions required for EEC 407 to connect with EES 403. The functions of ECS 404 are: supplying edge configuration information to EEC 407, such as information for EEC 407 to connect to EES 403 (e.g., service area information applicable to LADN (Local Area Data Network, LADN)); and information for establishing a connection with EES 403 (e.g., URI); supporting registration functions for EES 403 (i.e., registration, update, and deregistration); supporting functions of API call procedures and API open functions as specified in 3GPP TS23.222; and the ability to interact with 3GPP core network 408 to access network functions directly (e.g., PCF) or indirectly (e.g., via SCEF / NEF / SCEF+NEF).

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

[0055] EAS 402 is an application server that resides in EDN 401 and performs server functions. AC 406 is connected to EAS 402 to take advantage of application services with edge computing advantages. The server functions of the application may be available only as EAS 402. However, some server functions may also be available both at the edge and in the cloud, as EAS 402 and application servers residing in the cloud, respectively. The server functions provided by EAS 402 and its cloud application server counterparts may be the same or may be different; if the server functions provided by EAS 402 and its cloud application server counterparts are different, the application data services exchanged with the AC may also be different. EAS 402 can use the capabilities of 3GPP core network 408 in different ways, for example: if EAS 402 is an entity trusted by 3GPP core network 408, EAS 402 can directly call the 3GPP core network 408 function API; EAS 402 can call the 3GPP core network 408 capabilities through EES 403; and EAS 402 can call the 3GPP core network 408 capabilities through a capability exposure function such as SCEF or NEF.

[0056] The architecture 400 may include a plurality of different interfaces for enabling edge applications, which may be referred to as reference points. For example, the link EDGE-1 may be a reference point for enabling interaction between the EES 403 and the EEC 407. The link EDGE-1 supports: registration and deregistration of the EEC 407 to the EES 403; retrieval and provisioning of EAS 402 configuration information; and discovery of EAS 402 available in the EDN 401.

[0057] The link EDGE-2 may be a reference point that enables interaction between the EES 403 and the 3GPP core network 408. The link EDGE-2 supports: for example, accessing the 3GPP core network 408 functions and APIs via the SCEF API and NEF API defined in 3GPP TS23.501, 3GPP TS23.502, 3GPP TS29.522, 3GPP TS23.682, 3GPP TS29.122 to retrieve network capability information; or the EES 403 deployed in the MNO (Mobile Network Operator, MNO) trust domain (see 3GPP TS23.501 Section 5.13, 3GPP TS23.503, 3GPP TS23.682). Considering different deployment models, the link EDGE-2 may reuse the 3GPP reference points or interfaces of EPS (Evolved Packet System, EPS) or 5GS (5G System, 5GS).

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

[0059] Link EDGE-4 may be a reference point that enables interaction between ECS 404 and EEC 407. Link EDGE-4 supports: Supplying edge configuration information to EEC 407.

[0060] Link EDGE-5 may be a reference point that enables interaction between the AC and the EEC 407 .

[0061] The link EDGE-6 may be a reference point that enables interaction between the ECS 404 and the EES 403. The link EDGE-6 supports: Registration of EES 403 information to the ECS 404.

[0062] The link EDGE-7 may be a reference point that enables interaction between the EAS 402 and the 3GPP core network 408. The link EDGE-7 supports: for example, accessing the 3GPP core network 408 functions and APIs to retrieve network capability information via the SCEF API and NEF API defined in 3GPP TS23.501, 3GPP TS23.502, 3GPP TS29.522, 3GPP TS23.682, 3GPP TS29.122; or the EAS 402 deployed within the MNO trust domain (see 3GPP TS23.501 Section 5.13, 3GPP TS 23.682). Considering different deployment models, the link EDGE-7 may reuse the 3GPP reference points or interfaces of EPS or 5GS.

[0063] The link EDGE-8 may be a reference point that enables interaction between the ECS 404 and the 3GPP core network 408. The link EDGE-8 supports: a) access to the 3GPP core network 408 functions and APIs to retrieve network capability information, for example, via the SCEF API and NEF API defined in 3GPP TS23.501, 3GPP TS23.502, 3GPP TS29.522, 3GPP TS23.682, 3GPP TS29.122; and the ECS 404 deployed within the MNO trust domain (see 3GPP TS23.501 Section 5.13, 3GPP TS23.682). Considering different deployment models, the link EDGE-8 may reuse the 3GPP reference points or interfaces of EPS or 5GS.

[0064] AC 406 may send a query to EES 403 through EEC 407 to discover a suitable EAS. In the query, AC 406 includes an EAS discovery filter that defines the desired characteristics of a suitable EAS. In response, EEC 407 provides AC 406 with a list of matching EASs and some of the characteristics of the matching EASs. AC 406 then selects the best EAS from the list.

[0065] Figure 55GMS application provider 501, 5GMS aware application 502, UE 503, 5GMS client 504, 5GMS AS 505, 5GMS AF 506, DN 507, NEF 508, media session processor 509, media streamer 510 and PCF 511 and interfaces M1 521, M2 522, M3 523, M4 524, M5 525, M6 526, M7 527, M8 528, N5 519 and N33 520 with them in Figure 3 The counterparts in are similar, and therefore a detailed description of these components will be omitted.

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

[0067] exist Figure 5 In the 5GMS Application Provider (AP), the 5GMS AF requests a session using the M1 interface. Then, through the same interface, the AP requests different session functions, including server certificates, content preparation, content hosting configuration, reporting, consumption reporting, policies, etc.

[0068] exist Figure 5 In the 5GMS application provider (AP), the M1 interface is used to request the provision of a session from the 5GMS AF. Then, through the same interface, the AP requests the provision of different session functions, including server certificates, content preparation, content hosting configuration, reporting, consumption reporting, policies, etc.

[0069] As mentioned above, the current 5G edge architecture defined in 3GPP TS23.558 only defines the discovery of edge applications through application clients. 3GPP TS26.501 only defines the media streaming architecture. 3GPP SWG (Sub Work Group, SWG) 4 recently developed an architecture for running 5G media applications on 5G edge servers by combining these two architectures.

[0070] Therefore, embodiments may provide a method of running a live streaming service for user-generated content using the above-described architecture.

[0071] In an embodiment, an example use case may correspond to a user-generated live stream. The use case may be summarized as follows. A social influencer initiates a live captured media session and publishes content via 5G media uplink streaming. The content is then distributed in real time to several or more viewers via 5G media downlink streaming.

[0072] Embodiments may provide several usage scenarios with various configuration options that can be changed during a live session. For example:

[0073] 1) Social influencers can:

[0074] a) is static, occasionally mobile or highly mobile, such as in a vehicle, on skis or on a bicycle;

[0075] b) Produce content of varying quality depending on lighting conditions, speed, and based on the quality of the camera and available uplink bandwidth;

[0076] c) Produce very valuable content that requires additional content protection;

[0077] d) Want to exploit the stream by allowing advertisements to be inserted into the content (targeted pre-roll and / or mid-roll).

[0078] 2) The audience is likely to be quite diverse and changing because:

[0079] a) Viewers may dynamically join or leave the live stream;

[0080] b) the number of viewers may be just a few, or the number of viewers may be quite large, such as in the range of tens of thousands or more for popular influencers;

[0081] c) viewers may be geographically distributed in different densities across regions, and

[0082] The density of viewers may vary during a session;

[0083] d) Viewers may use the Service on different devices with different operating systems, DRM (Digit Rights Management) capabilities, and different codec hardware capabilities, such as using the Service on a 4K TV, mobile phone, car receiver, or tablet computer;

[0084] e) some of the viewers may be mobile, i.e., in a car or on public transport;

[0085] f) Viewers may react to the content or to previous reactions of viewers who have previously watched the content (smileys, comments, likes, voiceovers, images, avatars, and animations).

[0086] 3) Service requirements may be very different. Content may need to:

[0087] a) can be used in real time and / or on demand;

[0088] b) available for use only after the live uplink session has ended, i.e. fully uploaded before being made available to followers;

[0089] c) be available with a desired target delay ranging from as low as 1 second up to tens of seconds between capture and display;

[0090] d) dubbing in the same or different languages,

[0091] e) Automatically extract and add captions / subtitles from audio;

[0092] f) post-processing to improve audio and / or visual quality;

[0093] g) processing by adding covers and content labels and other enhancements,

[0094] h) indexing, including adding thumbnail navigation in real time;

[0095] i) Provide specific metadata to regional agents, such as stop information, advertising insertion opportunities, language settings, or other service metadata;

[0096] j) Check for profanity and make appropriate changes before distribution;

[0097] k) Available for a period of time (from a few minutes to forever) after the live session ends

[0098] View inside.

[0099] According to an embodiment, in a simple reference scenario of 5G media uplink and downlink streaming, one or more of the following aspects may be supported:

[0100] 1) Application management services: Server applications can be run by external application providers, by MNOs, or through the collaboration of application providers and MNOs.

[0101] 2) Provide uplink streams to applications through 5G media uplink streaming.

[0102] 3) The application may perform one or more of the following processes:

[0103] a) The application decodes the received content

[0104] b) The application applies various processing to the content, such as:

[0105] i) Line doubling

[0106] ii) Light correction

[0107] iii) Stabilization

[0108] iv) Dubbing

[0109] v) Add explanatory text

[0110] vi) Covering and marking

[0111] vii) Indexing

[0112] viii) Navigation improvements.

[0113] c) The application encodes the uploaded content into 5GMS downlink streaming format.

[0114] d) The application packages the content and adds appropriate advertising metadata.

[0115] e) Applications enforce content protection and DRM.

[0116] 4) Once the content becomes available, the server application uses downlink streaming for distribution.

[0117] a) The server application provides 5GMS downlink streaming services.

[0118] b) The server application ingests the content into the 5GMS streaming service.

[0119] c) The server application gets feedback from the usage reports about what content is used and changes the encoded streaming format.

[0120] In an embodiment, one or more of the following aspects may be important to the service:

[0121] 1) Considering the dynamic aspects of the service, such as when a highly mobile edge media streaming client transitions between two edge processing environments, can the service be provided uninterrupted throughout the session?

[0122] 2) Can the expected end-to-end delay be met in the reference scenario case, and if it cannot be met, what are possible ways to recognize this?

[0123] 3) Is the content generation flexible and fast enough to satisfy different user groups, but the utilization rate is very high, that is, changes in the content are used by one or more viewers and shared by as many viewers as possible?

[0124] 4) Are there benefits to pushing some processing closer to the influencers, some viewers, or somewhere in between (in terms of bandwidth, latency, and processing requirements)?

[0125] Service Type

[0126] Thus, embodiments may utilize service classes that may define a set of services provided to a user. For example, a user-generated live streaming use case covers scenarios where various processing may occur depending on the service class requested. In many sessions, services may occur in the cloud or at the edge close to the capture device. In this use case, an application provider, such as 5GMS application provider 501, may define various service classes.

[0127] Each service class, which may be referred to as a service class, may provide content preparation processing that supports one or more specific features from the following list:

[0128] 1) Quality improvement, e.g.

[0129] a) Line doubling

[0130] b) Light correction

[0131] c) Stabilization

[0132] d) Audio quality improvement

[0133] 2) Enrich and add interactive functions, such as

[0134] a) Dubbing and adding captions

[0135] b) Covering and marking

[0136] c) Indexing and key feature detection

[0137] d) Navigation improvements

[0138] 3) Multi-rate encoding of content

[0139] a) Content-aware encoding

[0140] b) Low latency

[0141] c) On-the-fly encoding and transcoding

[0142] d) Multi-path encoding of on-demand content

[0143] 4) Splicing and advertising insertion

[0144] a) Splicing content and manifest signaling

[0145] b) Ad insertion queue and information

[0146] c) Language settings and other service metadata

[0147] 5) Application content protection and DRM

[0148] Service Category Requirements

[0149] For each SC, a set of service class requirements (SCR) may be defined for the 5GMS AS running the service, and the set of service class requirements may include one or more of the following aspects:

[0150] 1) EAS Type

[0151] 2) Hardware resources:

[0152] a) Calculation

[0153] b) Graphics computing

[0154] c) Memory

[0155] d) Storage device

[0156] 3) Connectivity

[0157] a) Bandwidth

[0158] b) Delay

[0159] c) Maximum request rate

[0160] d) Maximum response time

[0161] 4) Availability

[0162] 5) Functional support

[0163] a) Accelerated encoder / transcoder

[0164] b) Quality improvement function

[0165] c) Enrich content and increase interactivity

[0166] d) Splicing and ad insertion tools

[0167] e) Stabilization

[0168] To build a service, an application provider can maintain three objects:

[0169] 1. Service Class (SC)

[0170] 2. Service Class Requirement (SCR)

[0171] 3. Scale and Geographical Distribution (SGD)

[0172] Figure 6 An example of a high-level call flow for the above use case is shown.

[0173] First, at operation 602, the 5GMS application provider (AP) 501 requests a session to be provided for a user-generated live streaming service.

[0174] At operation 604 , the 5GMS-aware application 502 starts by requesting service from the 5GMS AP 501 .

[0175] At operation 606, the 5GMS AP 501, using the user's SC, SCR, and SGD in its database and the current user location, may send an EAS description (e.g., as defined in TS 23.558 Section 8.2.4) to the 5GMS-aware application.

[0176] At operation 608, the 5GMS-aware application 502 requests to locate a server that can provide the service category registered by the user. And the media session processor 509 and the EEC 554 can help locate such a server.

[0177] At operation 610, a new 5GMS AS may be provided if necessary. Operation 610 may be performed by one or more of the 5GMS AF 506, the EES 550, and the ECS 556.

[0178] At operation 612 , the 5GMS AF may provide a list of suitable 5GMS ASs and their information to one or more of the media session processor 509 , the EEC 554 , and the 5GMS-aware application 502 .

[0179] At operation 614, one or more of the media session processor 509, the EEC 554, and the 5GMS-aware application 502 may select a preferred 5GMS AS instance based on, for example, the user service class or SC and the user's location.

[0180] At operation 616, uplink streaming may be performed. The media may be uplink streamed to the 5G MSAS, the content may be prepared according to the SCR and delivered to a Content Delivery Network (CDN).

[0181] In an embodiment corresponding to this use case, the relocation of the 5GMS AS may occur due to various reasons, such as:

[0182] 1. User relocation.

[0183] 2. Audience diversity / geographic changes may require additional transcoders.

[0184] 3. Changes in service categories, which require more computing resources

[0185] In any of the above cases, it may be necessary to transfer the service to a new 5GMS AS. The relocation may be performed using the ACR detection entity in Table 1 according to TS23.558.

[0186] Table 1: ACR detection entities for each relocation reason

[0187]

[0188]

[0189] Thus, embodiments may relate to a method for live streaming of user-generated content over a 5G network, wherein content preparation is performed on a 5G edge server, wherein various service categories are provided, wherein in each service category, a set of content preparation processes are defined and for that service category, a set of service category requirements are defined, wherein applications on user devices use these requirements to locate and discover appropriate 5G edge servers to run services, and the best 5G edge server is selected based on additional information provided by the 5G edge servers, such as the location, efficiency, cost and other parameters of the 5G edge servers, wherein services may be relocated to new edge servers based on various reasons.

[0190] Figure 7 is a flow chart of an example process 700 for enabling edge applications according to an embodiment. In some implementations, Figure 7 One or more processing blocks in may be formed by the above Figures 1 to 6 Any of the elements discussed may be performed.

[0191] like Figure 7 As shown, process 700 may include transmitting the content of the content of the content to the user through fifth generation media streaming (5 th The 5GMS (5GMS)-aware application sends a live streaming request corresponding to the user-generated content to the 5GMS application provider (AP) (block 702).

[0192] like Figure 7As further shown, processing 700 may include receiving an edge application server (EAS) description corresponding to a live stream request from a 5GMS AP via a 5GMS-aware application, wherein the EAS description indicates a service class (SC) corresponding to the live stream request among multiple SCs (block 704).

[0193] like Figure 7 As further shown, the process 700 may include selecting a 5GMS application server (Application Server, AS) based on the SC by the 5GMS-aware application (block 706).

[0194] like Figure 7 As further shown, process 700 may include live streaming of user-generated content to a 5GMS AS via a media streaming network, such as a 5GMS network, based on the SC (block 708).

[0195] In an embodiment, the selection may also include: sending a request for locating at least one AS corresponding to the SC to a 5GMS application function (AF) through a 5GMS awareness application; receiving a list of at least one 5GMS AS corresponding to the SC from the 5GMS AF through the 5GMS awareness application; and selecting a 5GMS AS from the list based on the SC.

[0196] In an embodiment, the SC may specify content preparation processing that supports at least one of the following: upscaling, light correction, stabilization, audio quality improvement, dubbing, adding captions, overlays, tagging, indexing, key feature detection, navigation improvements, multi-rate encoding, content-aware encoding, low-latency encoding, just-in-time encoding, multi-path encoding for transcoding on-demand content, splicing content, manifest signaling, ad insertion queues, ad insertion information, language settings, service metadata, content protection, and digital rights management.

[0197] In an embodiment, the EAS description may also indicate a service class requirement (SCR) corresponding to the SC, and the 5GMS AS may be selected based on the SCR.

[0198] In an embodiment, the SC and SCR may be stored in a database corresponding to the 5GMS AP.

[0199] In an embodiment, the SCR may specify at least one of hardware resources corresponding to the SC, connectivity parameters corresponding to the SC, availability corresponding to the SC, and functions corresponding to the SC.

[0200] In an embodiment, the EAS description may further indicate a scale and geographic distribution (SGD) corresponding to the SC, wherein the SGD indicates at least one of an audience scale and an audience location, and wherein a 5GMS AS may be selected based on the SGD corresponding to the live stream request and the location of the user.

[0201] In an embodiment, based on the 5GMS-aware application determining that the SC is changed to a new SC, process 700 may also include: selecting a new 5GMS AS corresponding to the new SC; and performing live streaming of user-generated content to the new 5GMS AS according to the new SC.

[0202] Although Figure 6 Example blocks of process 600 are shown, but in some implementations, Figure 6 Process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks compared to the blocks depicted in . Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0203] In addition, the proposed method can be implemented by a processing circuit system (e.g., one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-transitory computer readable medium to perform one or more of the proposed methods.

[0204] The above-described techniques may be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media.

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

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

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

[0208] Even if 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 that are not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly refer to only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.

[0209] Unless explicitly stated, the elements, actions or instructions used herein should not be interpreted as key or necessary elements, actions or instructions. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the term "group" is intended to include one or more items (such as related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". In the case of only meaning an item, the term "one (one)" or similar language is used. In addition, as used herein, the terms "have", "have", "with" etc. are intended to be open terms. In addition, unless explicitly stated otherwise, the phrase "based on" is intended to mean "based at least in part on".

Claims

1. A method for live streaming of user-generated content via a media streaming network, characterized in that: include: Sending a live streaming request corresponding to the user-generated content to a 5GMS application provider AP through a fifth generation media streaming 5GMS aware application; Receiving, through the 5GMS awareness application, an edge application server EAS description corresponding to the live streaming request from the 5GMS AP, wherein the EAS description indicates a service category SC corresponding to the live streaming request among a plurality of service categories SC; Selecting a 5GMS application server AS based on the SC through the 5GMS-aware application; and Performing live streaming transmission of the user-generated content to the 5GMS AS through the 5GMS network according to the SC; The EAS description also indicates the size and geographical distribution SGD corresponding to the SC, wherein the SGD indicates at least one of audience size and audience location, and The 5GMS AS is also selected based on the location of the user corresponding to the live stream request and the SGD.

2. The method according to claim 1, characterized in that Selecting a 5GMS application server AS based on the SC by the 5GMS-aware application includes: Sending, through the 5GMS awareness application, a request for locating at least one AS corresponding to the SC to a 5GMS application function AF; receiving, by the 5GMS awareness application, from the 5GMS AF a list of at least one 5GMS AS corresponding to the SC; and The 5GMS AS is selected from the list based on the SC.

3. The method according to claim 1, characterized in that The SC specifies content preparation processing that supports at least one of the following: upscaling, light correction, stabilization, audio quality improvement, dubbing, adding captions, overlays, tagging, indexing, key feature detection, navigation improvements, multi-rate encoding, content-aware encoding, low-latency encoding, just-in-time encoding, multi-path encoding for transcoding on-demand content, splicing content, manifest signaling, ad insertion queues, ad insertion information, language settings, service metadata, content protection, and digital rights management.

4. The method according to claim 1, characterized in that: The EAS description also indicates a service class requirement SCR corresponding to the SC, and Wherein, the 5GMS AS is selected based on the SCR.

5. The method according to claim 4, characterized in that The SCR specifies at least one of a hardware resource corresponding to the SC, a connectivity parameter corresponding to the SC, an availability corresponding to the SC, and a function corresponding to the SC.

6. The method according to claim 1, characterized in that Based on the 5GMS-aware application determining that the SC is changed to a new SC, the method also includes: selecting a new 5GMS AS corresponding to the new SC; and performing live streaming of the user-generated content to the new 5GMS AS according to the new SC.

7. An apparatus for live streaming of user-generated content via a media streaming network, characterized in that: The device comprises: A sending module, configured to send a live streaming request corresponding to the user-generated content to a 5GMS application provider AP through a fifth generation media streaming 5GMS awareness application; A receiving module, configured to receive an edge application server EAS description corresponding to the live streaming request from the 5GMS AP through the 5GMS awareness application, wherein the EAS description indicates a service category SC corresponding to the live streaming request among multiple service categories SC; A selection module is configured to select a 5GMS application server AS based on the SC through the 5GMS-aware application; and An execution module, configured to perform live streaming transmission of the user-generated content to the 5GMS AS through a 5GMS network; The EAS description also indicates the size and geographical distribution SGD corresponding to the SC, wherein the SGD indicates at least one of audience size and audience location, and The 5GMS AS is also selected based on the location of the user corresponding to the live stream request and the SGD.

8. The device according to claim 7, characterized in that The sending module is further used to send a request for locating at least one AS corresponding to the SC to the 5GMS application function AF through the 5GMS awareness application, The receiving module is further configured to receive a list of at least one 5GMS AS corresponding to the SC from the 5GMS AF through the 5GMS awareness application; and The selection module is further used to select the 5GMS AS from the list based on the SC.

9. The device according to claim 7, characterized in that The SC specifies content preparation processing that supports at least one of the following: upscaling, light correction, stabilization, audio quality improvement, dubbing, adding captions, overlays, tagging, indexing, key feature detection, navigation improvements, multi-rate encoding, content-aware encoding, low-latency encoding, just-in-time encoding, multi-path encoding for transcoding on-demand content, splicing content, manifest signaling, ad insertion queues, ad insertion information, language settings, service metadata, content protection, and digital rights management.

10. The device according to any one of claims 7 to 9, characterized in that The EAS description also indicates a service class requirement SCR corresponding to the SC, and Wherein, the 5GMS AS is selected based on the SCR.

11. The device according to claim 10, characterized in that The SCR specifies at least one of a hardware resource corresponding to the SC, a connectivity parameter corresponding to the SC, an availability corresponding to the SC, and a function corresponding to the SC.

12. The device according to any one of claims 7 to 9, characterized in that Based on the 5GMS-aware application, it is determined that the SC is changed to a new SC, the selection module is also used to select a new 5GMS AS corresponding to the new SC, and the execution module is also used to perform live streaming of the user-generated content to the new 5GMS AS according to the new SC.

13. An electronic device comprising at least one memory and at least one processor, characterized in that: The at least one memory is used to store program code; and When the at least one processor runs the program code, it is used to implement the method according to any one of claims 1 to 6.

14. A non-transitory computer readable medium storing instructions, characterized in that: When the instructions are executed by a processor, they are used to implement the method according to any one of claims 1 to 6.

Images