KR102565776B1 - Method and Apparatus for Cloud Service - Google Patents

Abstract

Aspects of this disclosure provide methods and apparatus for cloud service. For example, a device in a cloud for providing a cloud service includes processing circuitry. A processing circuit receives a request that includes at least first characteristics associated with the variable. In one example, the first properties include complete information to describe the variable. The processing circuitry generates a message containing the first characteristics associated with the variable and the updated value of the variable and transmits the message to the recipient.

Description

Method and Apparatus for Cloud Service

Inclusion by reference

This application claims the benefit of priority to U.S. Patent Application Serial No. 17/029,968, entitled "METHOD AND APPARATUS FOR CLOUD SERVICE," filed on September 23, 2020, which U.S. Patent Application filed on 2019 US Provisional Application No. 62/907,322, filed on September 27, entitled "SELF-CONTAINED REPORTING FOR CLOUD SERVICES", filed on September 27, 2019, entitled "SELF-CONTAINED MONITORING FOR U.S. Provisional Application No. 62/907,327, entitled "CLOUD SERVICES", and U.S. Provisional Application No. 62/907,312, filed on September 27, 2019, entitled "SELF-CONTAINED NOTIFICATION FOR CLOUD SERVICES." claim The entire disclosure of the prior application is hereby incorporated by reference in its entirety.

technical field

This disclosure generally describes embodiments relating to cloud services.

The background description provided herein is intended to generally present the context of the present disclosure. To the extent that the work of the presently named inventors is described in this background section, this work, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are either expressly or implicitly considered prior art to the present disclosure. not accepted

Various media applications and services require significant processing power. In some instances, cloud processing is preferred when workloads that would otherwise be performed on a client device can be offloaded to a remote server. Because the remote server has a much higher computational capacity, complex media processing tasks can be performed by the remote server, and then the final or near final result can be transmitted to the client device.

Aspects of the present disclosure provide methods and apparatus for cloud services. For example, a device in a cloud for providing a cloud service includes processing circuitry. A processing circuit receives a request that includes at least first characteristics associated with the variable. In one example, the first properties include complete information to describe the variable. The processing circuitry generates a message containing the first characteristics associated with the variable and the updated value of the variable and transmits the message to the recipient.

In one example, the first characteristics include at least a definition of the variable, a unit of the variable, a type of the variable, and a universal identifier of the variable.

In some examples, processing circuitry may establish and manage workflows for cloud services. In some other examples, processing circuitry may perform one or more tasks in a workflow for a cloud service.

In some embodiments, the request includes at least second characteristics associated with the event. The second properties contain complete information to describe the event. The processing circuitry can generate a message that includes first characteristics associated with the variable and an updated value of the variable, and second characteristics associated with the event to indicate the occurrence of the event. Note that a variable can be a function variable or a system variable and an event can be a function event or system event.

In some embodiments, the request includes at least a first variables descriptor object associated with variables, a first events descriptor object associated with events, and a first reporting descriptor object with a reporting interval. The processing circuitry has a second reporting descriptor object having a second events descriptor object associated with a subset of events and a second variables descriptor object having updated values for the variables at the time of the reporting interval for the previous message. Create a message containing

In some embodiments, the request includes at least a first notification descriptor object having a first variables descriptor object associated with the variables and a first events descriptor object associated with subscribed events. A processing circuit having, in response to the occurrence of at least one of the subscribed events, a second variables descriptor object having updated values for the variables and a second events descriptor object associated with the subset of subscribed events. 2 Creates a message containing a report descriptor object.

In some embodiments, the request includes at least a first monitoring descriptor object having a first variables descriptor object associated with variables and a first events descriptor object associated with events. The processing circuit receives a request transmitted from the monitoring entity and, in response to the request, a second variables descriptor object having updated values for the variables and a second events descriptor object associated with the subset of events. Creates a message containing a report descriptor object. The processing circuit then sends the message to the monitoring entity.

Note that in some embodiments, the message includes a request descriptor object that identifies the request.

Aspects of the present disclosure also provide a non-transitory computer readable medium storing instructions that, when executed by a computer for cloud services, cause the computer to perform a method for cloud services.

Additional features, nature and various advantages of the disclosed subject matter will become more apparent from the following detailed description and accompanying drawings.
1 illustrates an exemplary media processing system in accordance with an embodiment of the present disclosure.
2 shows an example of a graph according to an embodiment of the present disclosure.
3 shows a list of variables in a function according to some embodiments of the present disclosure.
4 shows a table of properties for a variable according to some embodiments of the present disclosure.
5 shows an example of a variables descriptor schema according to some embodiments of the present disclosure.
6 shows a list of events in a function according to some embodiments of the present disclosure.
7 shows a table of properties for an event according to some embodiments of the present disclosure.
8 shows an example of an events descriptor schema according to some embodiments of the present disclosure.
9 shows a table of parameters and corresponding types for parameters in a reporting descriptor.
10 illustrates an example reporting descriptor schema according to some embodiments of the present disclosure.
11 shows a table of parameters and corresponding types for parameters in a notification descriptor.
12A and 12B show examples of notification descriptor schemas according to some embodiments of the present disclosure.
13 shows a table of parameters and corresponding types for parameters in a monitoring descriptor.
14 illustrates an example of a monitoring descriptor schema according to some embodiments of the present disclosure.
15 shows a flowchart outlining a process according to an embodiment of the present disclosure.
16 is a schematic illustration of a computer system according to an embodiment.

Cloud computing refers to the practice of using a network of remote servers hosted on a network (eg, the Internet) to deliver information computing services (eg, cloud services). The network architecture (eg, including hardware and software) used to provide cloud services to service consumers (eg, clients) is referred to as a cloud. Cloud computing provides access to a wide range of services, such as data processing, media processing, servers, storage, networks, applications, online services, and the like. In some instances, media processing becomes computationally intensive, so media processing clouds are preferred to offload significant workloads to remote servers.

Generally, a cloud computing system includes a network, one or more servers, and one or more client devices. A network facilitates communication between a server and a client device. The client device may be, for example, a smart phone, tablet computer, laptop, personal computer, wearable device, head mounted display (HMD), or the like. A server may include any suitable computing or processing device capable of providing computing services to one or more client devices. For example, each server may include one or more processing devices, one or more memories to store instructions and data, and one or more network interfaces to facilitate communication over a network. In some embodiments, the server includes a workflow manager that can select functions and build workflow pipelines to perform processing tasks.

According to some embodiments of the present disclosure, when computation is offloaded to a remote server, the client device or service provider responsible for providing the service needs information about the processing status of the service, eg real-time information of the service, etc. can be done with In some examples, actions may be taken at the cloud computing system to provide status information to entities involved in the cloud service. In an example, reporting is an action that is performed regularly (eg, performed frequently based on time intervals) to provide a destination with information about events and variables during performance of a service. In another example, notification is an action that provides information to a destination when an event occurs. In another example, monitoring is an action by which an entity requests information and receives the requested information. For ease of explanation, in the description below, status information generated in response to an action (eg, reporting, notification, and monitoring) is referred to as a status report; Status information generated in response to a reporting action is referred to as a periodic report; Status information generated in response to a notification action is referred to as a notification report; Status information generated in response to a monitoring action is referred to as a monitoring report.

Aspects of this disclosure provide a framework for reporting, monitoring and notification in cloud computing systems. The framework can simplify the setup and processing of reporting, monitoring and notification actions. Specifically, some aspects of the present disclosure provide a self-contained reporting, monitoring and notification framework for cloud computing services. A self-contained framework can provide a recipient with a container (e.g., a message) that includes all necessary information in the container for the recipient to understand, so that the recipient can interact with information outside the container to understand the received information. no need to refer

In this disclosure, a media processing system (also referred to as a media processing cloud in some examples) that performs network-based media processing (NBMP) is used as an example to illustrate reporting, monitoring and notification frameworks; Note that reporting, monitoring and notification frameworks may be used in other suitable cloud computing systems.

In a media processing system, the NBMP source describes the requested media processing and provides information about the nature and format of the media data. Accordingly, the NBMP work flow manager establishes a media processing work flow and notifies the NBMP source that the work flow is ready, then media processing can begin. For example, the media source(s) can then begin sending media to the network for processing.

In some embodiments, a NBMP workflow includes media processing tasks that are linked based on input/output relationships between media processing tasks. Each of the media processing tasks performs a media processing operation, such as video decoding, video stitching, video encoding, and the like. In one example, a first media processing task performs a media processing operation based on an input and generates an output. An output of the first media processing task may be used as an input to a second media processing task coupled with the first media processing task. In other words, a NBMP workflow can be viewed as a connected graph of media processing tasks.

A workflow manager can ensure correct operation of a workflow by configuring and monitoring each task as well as the workflow output. In some examples, the workflow manager is configured to select media processing functions and instantiate them as tasks based on the workflow description received from the NBMP source.

Appropriate interactions may be performed at the media processing system to establish, load, instantiate and monitor media processing entities to execute media processing tasks. In some examples, between a NBMP source and a workflow manager; Application programming interfaces (APIs) may be defined between the workflow manager and the task(s); An API is defined to discover the appropriate function(s). In some examples, the media processing system is configured to be media format and protocol agnostic. A media processing system may identify and signal media, metadata, and auxiliary information types for data exchanged between media sources, workflow managers, and tasks.

In some examples, interfaces may be defined including both data formats and application programming interfaces (APIs) between entities that are connected through digital networks for media processing. Users can remotely access and configure user actions for efficient and intelligent processing. Workflows to be applied to media data can be described and managed. Media data can be uploaded to the network, and media processing tasks can be instantiated and configured. In some embodiments, dynamic creation of media processing pipelines is possible as well as real-time or deferred access to processed media data and metadata. Media and metadata formats used between the media source, workflow manager and media processing entities in the media processing pipeline are also specified.

In one example, clients (eg producers, service providers and consumers of digital media) may describe media processing operations to be performed by media processing entities in the network. A workflow may be described by making a set of media processing functions accessible through interfaces (eg, NBMP APIs). A media processing entity (MPE) may execute processing tasks applied to media and associated metadata received from media source(s) or other tasks. MPEs can provide the ability to configure, manage and monitor processing tasks. A media processing task can be a process that is applied to media and metadata input(s) to generate data and associated metadata output(s) to be consumed by a media sink or other media processing task.

A media processing system may support a variety of delivery methods such as streaming, file delivery, push-based incremental download, hybrid delivery, multi-path and heterogeneous network environments.

1 illustrates an exemplary media processing system (eg, NBMP system, NBMP reference architecture, NBMP architecture) 100 according to an embodiment of the present disclosure. The media processing system 100 includes a NBMP source 101, a workflow manager (eg, NBMP workflow manager) 103, a function repository 105, a media source 111, a media processing entity (MPE) ( 113), media sink 115, third party entities, and the like. Media processing system 100 may include additional media source(s), media sink(s), and/or media processing entities. Media processing system 100 may process media data across one or more processing entities within a network. Information such as various media and control information (or control data) for the media may be communicated between multiple entities within the media processing system 100 .

To provide context for the discussion, media processing system 100 is described below as NBMP system 100 . These descriptions can be adapted to suit any media processing system.

A NBMP source 101 may describe or otherwise represent media processing in a network. Function repository 105 may contain NBMP function descriptions of various NBMP functions. The NBMP source 101 and workflow manager 103 may retrieve NBMP function descriptions or functions from the function repository 105 . A NBMP function may refer to a corresponding description of the implementation and/or operation of standalone and self-contained media processing operations.

A processing task or task may refer to a runtime instance of NBMP functionality executed by MPE 113 . A NBMP workflow or workflow may be represented by a graph (eg, a directed acyclic graph (DAG)) of one or more connected task(s) that accomplish the requested media processing. Workflow manager 103 provisions task(s) and tasks for creating, controlling, managing, and monitoring workflows, based on, for example, a workflow description document (WDD). can be connected.

A media source 111 may provide media content (eg, media data, supplemental information) to be processed by the workflow. Supplemental information may include metadata or auxiliary information related to media data. A media source 111 may provide input to the workflow. Media sink 115 may consume the output of the workflow. MPE 113 may execute one or more media processing task(s) to process media content.

Different entities within the NBMP system 100 (eg, NBMP source 101, workflow manager 103, and MPE 113) may invoke and respond to media service requests using APIs. APIs may include NBMP Workflow API or Workflow API, Function Discovery API and Task API. A workflow API may provide an interface between the NBMP source 101 and the workflow manager 103 . A task API may provide an interface between workflow manager 103 and media processing tasks. A function discovery API may provide an interface between the Workflow Manager 103 / NBMP Source 101 and the Function Repository 105 .

The NBMP interfaces described above may be used to create and control media processing workflows in a network. The NBMP system 100 can be divided into a control plane and a media plane (or media data plane). The control plane can include workflow APIs, function discovery APIs, and task APIs.

Workflow APIs may be used by the NBMP source 101 to create and control media processing workflows. The NBMP source 101 may use a workflow API to communicate with the workflow manager 103 to configure and control media processing in the network. When the NBMP source 101 sends a request to the workflow manager 103 by including the workflow resource (WR) in the operation of the workflow API, the workflow manager 103 sends the WR, the included WDD and the corresponding parse the descriptor and take appropriate actions according to the requested action. Workflow manager 103 may then acknowledge the request in response. The workflow API operations are to create a workflow (eg CreateWorkflow), update a workflow (eg UpdateWorkflow), delete a workflow (eg DeleteWorkflow), Retrieve (eg, RetrieveWorkflow), and the like.

The function discovery API may provide a means for the workflow manager 103 and/or the NBMP source 101 to discover media processing functions that may be loaded as part of a media processing workflow.

The task API may be used by workflow manager 103 to configure and monitor task(s) (eg, task 1 and task 2 executed by MPE 113) at runtime. A task API may define interface(s) for configuration of media processing tasks by workflow manager 103, eg, after resources for the task are allocated to MPE 113. The Task API operations are to create a task (e.g. CreateTask), update a task (e.g. UpdateTask), get a task (e.g. GetTask), and delete a task (e.g. For example, DeleteTask) and the like.

At the media plane, media types, metadata and supplemental information types between tasks as well as between NBMP sources 111 and task(s) may be defined.

A Workflow Description (WD) may be passed from the NBMP Source 101 to the Workflow Manager 103 . A WD can describe information such as input data and output data, functions, and other requirements for a workflow.

The workflow manager 103 may receive the WDD from the NBMP source 101 and build a workflow for processing the requested media. In a workflow procedure, media processing functions may be selected, for example, from function repository 105, and then corresponding media processing tasks are constructed and a set of one or more MPEs (including MPEs 113, for example). ) can be distributed.

The set of functions provided by function repository 105 can be read by NBMP source 101 and workflow manager 103 . In one embodiment, the NBMP source 101 requests the creation of a workflow using a set of functions in the function repository 105 . Accordingly, the NBMP source 101 is configured to select functions for a work flow. The NBMP source 101 may request creation of a work flow as described below. The NBMP source 101 may use the description of media processing tasks used to create the workflow and may specify a connectivity map to define the connectivity of the inputs and outputs of the media processing tasks. When workflow manager 103 receives the above information from NBMP source 101, workflow manager 103 can instantiate media processing tasks based on respective function names and media processing tasks according to the connection map. can connect them.

Alternatively, the NBMP source 101 may request creation of a workflow using a set of keywords that the workflow manager 103 may use to configure the workflow. As such, the NBMP source 101 may not be aware of the set of functions to be inserted into the workflow. The NBMP source 101 may request creation of a work flow as described below. The NBMP source 101 may use a set of keywords that the workflow manager 103 may use to find suitable functions and may use an appropriate workflow description to specify the requirements of the workflow.

When the workflow manager 103 receives the information (eg, a set of keywords) from the NBMP source 101, the workflow manager 103 may use the keywords specified in the processing descriptor, for example, to generate the appropriate information. You can create a workflow by exploring features. Workflow manager 103 can then use other descriptors in the workflow description to provision media processing tasks and link media processing tasks to create a final workflow.

The processing model of the workflow manager 103 can be described as follows.

Workflow manager 103 may discover available media processing functions as follows. The NBMP function repository 105 may provide a function discovery interface (or API) to enable external entities to query for media processing functions capable of performing requested processing. Workflow manager 103 can access a directory service that provides a searchable list of media processing functions. Workflow manager 103 can use the description of media processing tasks in the workflow description to find the appropriate functions for the workflow.

The selection of media processing tasks for a workflow can be described below. When a request for media processing is received from the NBMP source 101, the workflow manager 103 can search the function repository 105 to find a list of all available functions that can perform the workflow. Using the workflow description from the NBMP source 101, the workflow manager 103 creates a function repository 105 that will implement the workflow, which can rely on information for media processing from the NBMP source 101. ) can be found from Information about media processing may include input and output descriptions, descriptions of requested processing, and information in other descriptors for functions in function directory 105 . Mapping source requests to the appropriate media processing tasks to be included in the workflow may be part of the implementation of NBMP in the network. Input ports and output ports can be used to reference input streams to reference and link input sources by input port names and output port names when creating a task.

The search for appropriate functions to be instantiated as tasks can be performed by the workflow manager 103 using the function discovery API. Alternatively, workflow manager 103 may use a function discovery API to retrieve details of some or all suitable functions from function repository 105 . Workflow manager 103 may then compare information about media processing from NBMP source 101 to different descriptors of each function.

Selected media processing tasks can be configured into a workflow. When functions to be included in the workflow are identified, the NBMP workflow manager 103 can instantiate those functions as respective tasks and compose the tasks so that they can be added to the workflow. The NBMP workflow manager 103 may extract configuration data from media processing information received from the NBMP source 101 and configure corresponding tasks. Configuration of tasks may be performed using a task API (eg, NBMP task API).

Task assignment and distribution may be described below. Workflow manager 103 can use workflows to perform processing distribution and organize media processing entities. In one example, for compute intensive media processing requests, workflow manager 103 may set up multiple compute instances and distribute the workload among the multiple compute instances. Thus, the workflow manager 103 can be configured by connecting multiple calculation instances as needed. In one example, the workflow manager 103 provisions a load balancer to assign the same task to multiple instances and distribute the workload among the multiple instances using a selected scheduling mechanism. In an alternative example, the workflow manager 103 assigns different operations of the same task to different instances (eg, parallel operations). In both examples described above, the workflow manager 103 can set up workflow paths between instances, so that appropriate workloads can be successfully realized. The workflow manager 103 can configure tasks to push the processed media data/streams to the next task in the workflow graph (or make them available via a pull mechanism).

When the workflow manager 103 receives the WDD from the NBMP source 101, the workflow manager 103 may perform selection of media processing functions to be inserted into the workflow. When the list of tasks to include in the workflow is created, the workflow manager 103 can then associate the tasks to prepare the workflow.

Workflow manager 103 may create a workflow, as represented by a graph (eg, DAG) from WDD, for example. 2 shows an example of a graph (eg, DAG) 200 according to an embodiment of the present disclosure. The DAG 200 may include a plurality of nodes T1 to T6 and a plurality of links (or connections) 202 to 208 . In one example, DAG 200 represents workflow 200 .

Each node of DAG 200 may represent a media processing task in workflow 200 . A link (eg, link 202) connecting a first node (eg, node T1) to a second node (eg, node T2) in the DAG 200 is the first node It may indicate that the output of (eg, node T1) is transmitted as an input to a second node (eg, node T2).

In general, a workflow may include any suitable number of input(s) (or workflow input(s)) and any suitable number of output(s) (or workflow output(s)). Workflow input(s) can be connected to media source 111, other workflow(s), etc., and workflow output(s) can be connected to media sink 115, other workflow(s), etc. Workflow 200 has an input 201 and outputs 209 and 210 . In some embodiments, task flow 200 may have one or more outputs from intermediate nodes.

According to some aspects of the present disclosure, status reports may include information of variables and information of events for functions. For example, a NBMP function is an implementation of a processing operation. In some embodiments, NBMP functions may be stand-alone and self-contained media processing operations and corresponding descriptions of processing operations. In some examples, for each NBMP function, two independent descriptors are used in the description. One of the two independent descriptors is for events of the NBMP function and is referred to as the events descriptor, and the other of the two independent descriptors is for variables and is referred to as the variables descriptor. Variables descriptors contain properties of variables, such as mathematical definitions, units, formats, universal identifiers, etc., used to understand the variables. Thus, in some examples, the variables descriptor can be self-explanatory, and the variables can be understood based on the variables descriptor without the need to reference other text from the variables descriptor. Similarly, the events descriptor contains properties of events used to understand the events. Thus, in some examples, the events descriptor can be self-describing, and events can be understood based on the events descriptor without the need to reference other text from the events descriptor.

According to an aspect of the present disclosure, the work flow of a service may be performed on different systems (also referred to as platforms, cloud systems). Each system can have system variables and system events. System variables and system events can be included in status reports.

In some embodiments, status reports are defined based on self-contained descriptors. In one example, periodic reports are defined based on self-contained descriptors referred to as reporting descriptors. For example, a periodic report may include an object defined based on a reporting descriptor, referred to as a reporting descriptor object. A reporting descriptor object allows periodic reports to include function variables and events as well as a subset of system variables and events. Variables (eg, functional variables and system variables) may be included in a form defined based on the variables descriptor, and events (eg, functional events and system events) may be events It can be included in a form defined based on these descriptors. Thus, periodic reports can be self-explanatory, and variables and events can be understood based on variables and events descriptors.

In another example, a notification report is defined based on a self-contained descriptor referred to as a notification descriptor. For example, a notification report may include an object defined based on a notification descriptor, and this object is referred to as a notification descriptor object. A notification descriptor object allows a notification report to include functional variables and events as well as a subset of system variables and events. Variables (eg, functional variables and system variables) may be included in a form defined based on the variables descriptor, and events (eg, functional events and system events) may be included in the events descriptor. can be included in a form defined on the basis of Thus, notification reports can be self-explanatory, and variables and events can be understood based on variables and events descriptors.

In another example, a monitoring report is defined based on a self-contained descriptor referred to as a monitoring descriptor. For example, the monitoring report may include an object defined based on the monitoring descriptor, and this object is referred to as a monitoring descriptor object. A monitoring descriptor object allows a monitoring report to include functional variables and events as well as a subset of system variables and events. Variables (eg, functional variables and system variables) may be included in a form defined based on the variables descriptor, and events (eg, functional events and system events) may be included in the events descriptor. can be included in a form defined on the basis of Thus, a monitoring report can be self-describing, and variables and events can be understood based on the variables and events descriptor.

Specifically, in some examples, each function may include a list of variables described according to a variables descriptor.

3 shows a list of variables in a function according to some embodiments of the present disclosure. As shown in FIG. 3, a function includes one or more variables, such as Variable-1, Variable-2, Variable-3, and the like. Variables or subsets of variables may be included in periodic reports in response to reporting actions. Variables or subsets of variables may be included in the monitoring report in response to the monitoring action. Variables or subsets of variables may be included in the notification report in response to the notification action.

In some embodiments, a variables descriptor object defined according to the variables descriptor may be included in the status report. A variables descriptor object can contain an array of objects associated with variables. An object associated with a variable may contain properties of the variable. For example, Object-1 contains the properties of Variable-1; Object-2 contains the properties of Variable-2; Object-3 contains the properties of Variable-3.

4 shows a table of properties for a variable according to some embodiments of the present disclosure. The table also contains descriptions of properties. For example, the object associated with a variable is the name for the variable, the definition for the variable, the value for the variable, the unit for the variable, the parameter type for the variable, and possibly the scope for the variable (min and max values for the variable), etc. includes

5 shows an example of a variables descriptor schema according to some embodiments of the present disclosure. As shown, the variables descriptor is an array of objects (eg, items) associated with the variables.

Additionally, in some examples, each function includes a list of events described according to an events descriptor.

6 shows a list of events in a function according to some embodiments of the present disclosure. As shown in FIG. 6, a function includes one or more events, such as Event-1, Event-2, and the like. Events or a subset of events may be included in the periodic report in response to the reporting action. Events or a subset of events may be included in the monitoring report in response to the monitoring action. Events or a subset of events may be included in a notification report in response to a notification action.

In some embodiments, an events descriptor object defined according to the events descriptor may be included in the status report. The events descriptor object can contain an array of objects associated with events. An object associated with an event may include properties of the event. For example, Object-1 contains the properties of Event-1; Object-2 contains the properties of Event-2.

7 shows a table of characteristics for an event according to some embodiments of the present disclosure. The table also contains descriptions of properties. For example, an object associated with an event includes a name of the event, a definition of the event, and the like.

8 shows an example of an events descriptor schema according to some embodiments of the present disclosure. As shown, the events descriptor may include an array of objects (items) associated with the events.

According to one aspect of the present disclosure, reporting is the act of periodically reporting information to a destination (eg, generating and transmitting a periodic report). In some embodiments, reporting may be set up in response to a request. In some examples, a requesting entity sends a request to a reporting entity. The request includes a first report descriptor object defined according to the report descriptor. The first report descriptor object may include a list of desired variables and events to be reported, a destination to which the report is to be transmitted, and the like. The reporting entity then transmits the events and variable values described in the first reporting descriptor object to the destination defined in the first reporting descriptor object. For example, a periodic report includes a second reporting descriptor object similar to the first reporting descriptor object. The second reporting descriptor object may include updated values of variables and occurrence information of events. Typically, the reporting descriptor also includes the frequency of reporting, the start time of reporting, and the delivery protocol of periodic reports. Note that the destination can be a requesting entity or a different entity than the requesting entity.

In the media processing system (100), the requesting entity may be a NBMP source (101) or a workflow manager (103). The reporting entity may be workflow manager 103 or media processing tasks.

In one example, workflow manager 103 may send a request for periodic reporting to a media processing task (eg, TASK 1 executed by MPE 113 ) via a task API. The workflow manager 103 can specify the desired variables and events, time interval, grouping, destination and protocol in the first reporting descriptor object in the request. The media processing task may then send periodic reports to the destination based on the time interval using the protocol specified in the first report descriptor object. A periodic report includes a second reporting descriptor object that conveys information about variables and events to be reported and other information, such as time interval, grouping, destination, protocol, and the like.

In another example, the NBMP source 101 may set up one or more reporting schemes and may send a request for periodic reporting to the workflow manager 103 via a workflow API. The workflow manager 103 can then generate periodic reports or the workflow manager 103 can request the media processing task to generate periodic reports. The NBMP source 101 may specify the desired variables and events, time interval, grouping, destination and protocol in the first reporting descriptor object in the request. The workflow manager 103 or media processing task can then send periodic reports to the destination based on the time interval using the protocol specified in the first report descriptor object. A periodic report includes a second reporting descriptor object that conveys information about variables and events to be reported and other information, such as time interval, grouping, destination, protocol, and the like.

In some embodiments, HTTP/1.1 is used as the protocol, and the POST method is used to send periodic reports in POST messages. For example, the body of a POST message contains a report descriptor object. In some examples, the body of the POST message also includes a request descriptor object to identify the report. In one example, the request descriptor object includes an identification (ID) of the request, a priority, and a task identification (ID) for the media processing task.

9 illustrates a table of parameters and corresponding types for parameters in a reporting descriptor, and FIG. 10 illustrates an example reporting descriptor schema according to some embodiments of the present disclosure. Note that system-events contains events belonging to the media processing system and can be provided by the cloud in the same format as the function's events. Also note that system-variables contains variables that belong to the media processing system and can be provided by the cloud in the same format as the function's variables. In some embodiments, (functional) variables may be included in a first variables descriptor object, and system variables may be included in a second variables descriptor object; (Functional) events may be included in the first events descriptor object, and system events may be included in the second events descriptor object.

According to another aspect of the present disclosure, notification is the act of reporting (eg, generating and sending a notification report) information to a destination when an event occurs. In some embodiments, notifications are set up in response to requests. In some examples, a requesting entity sends a request to a notification entity. The request includes a first notification descriptor object defined according to the notification descriptor. The first notification descriptor object may specify, for example, a list of desired variables and events, a destination to which a report is to be transmitted, and the like. Subsequently, when one or more of the events listed in the first notification descriptor object occurs, the notification entity transmits the events and variable values described in the first notification descriptor object to the destination defined in the first notification descriptor object. . For example, the notification report includes a second notification descriptor object similar to the first notification descriptor object. The second notification descriptor object may include updated values of variables and occurrence information of events. In general, the notification descriptor may also include other suitable information about the notification, such as start time, notification interval, delivery protocol, and the like. Note that the destination can be a requesting entity or a different entity than the requesting entity.

In the media processing system (100), the requesting entity may be a NBMP source (101) or a workflow manager (103). A notification entity may be a workflow manager 103 or media processing tasks.

In one example, workflow manager 103 may send a request for a notification to a media processing task (eg, TASK 1 executed by MPE 113 ) via a task API. The workflow manager 103 can specify the list of subscribed events, list of variables, destination, and protocol for the notification in the first notification descriptor object in the request. Subsequently, when one or more events in the list of subscribed events occur, the media processing task may send a notification report to the destination using the protocol specified in the notification descriptor. The notification report includes a second notification descriptor object carrying information of variables in the list of variables, information of events in the list of subscribed events, and other information.

In another example, the NBMP source 101 may set up one or more notification schemes and may send a request for notification to the workflow manager 103 via a workflow API. Workflow manager 103 may then generate notification reports or workflow manager 103 may request the media processing task to generate notification reports. The NBMP source 101 may specify a list of subscribed events, a list of variables, a destination and a protocol in the first notification descriptor object in the request. Then, when any of the events in the list of subscribed events occur, the workflow manager 103 or media processing task may send a notification report to the destination using the protocol specified in the notification descriptor. The notification report includes a second notification descriptor object carrying information of variables, information of events, and other information of the periodic report, such as destination, protocol, and the like.

In some embodiments, HTTP/1.1 is used as the protocol, and the POST method is used to send notification reports in POST messages. For example, the body of a POST message contains a notification descriptor object. In some examples, the body of the POST message also includes a request descriptor object to identify the notification. In one example, the request descriptor object includes an identification (ID) of the request, a priority, and a task identification (ID) for the media processing task.

11 shows a table of parameters and corresponding types for parameters in a notification descriptor, and FIGS. 12A and 12B show examples of notification descriptor schemas according to some embodiments of the present disclosure. Note that system-events contains events belonging to the media processing system and can be provided by the cloud in the same format as the function's events. Also note that system-variables contains variables that belong to the media processing system and can be provided by the cloud in the same format as the function's variables. In some embodiments, (functional) variables may be included in a first variables descriptor object, and system variables may be included in a second variables descriptor object; (Functional) events may be included in the first events descriptor object, and system events may be included in the second events descriptor object.

According to another aspect of the present disclosure, monitoring is the act of an entity requesting information and receiving the requested information. In some embodiments, monitoring may be performed in response to a request. In some examples, a monitoring entity (monitoring entity) sends a monitoring update request to a monitored entity (monitoring entity). The monitoring update request includes a first monitoring descriptor object defined according to the monitoring descriptor. The first monitoring descriptor object may specify, for example, a list of desired variables and events. In response to the monitoring update request, the monitored entity sends to the monitoring entity a monitoring report having a second monitoring descriptor object conveying the values of the requested variables and a subset of events from the desired events that occurred.

In the media processing system 100 , the monitoring entity may be a NBMP source 101 or a workflow manager 103 . The monitored entity may be the workflow manager 103 or media processing tasks.

In one example, workflow manager 103 may send a monitoring update request to a media processing task (eg, TASK 1 executed by MPE 113 ) via a task API. The workflow manager 103 can specify the desired variables and events in the first monitoring descriptor object in the monitoring update request. In response to the monitoring update request, the media processing task may send a monitoring report to workflow manager 103 . The monitoring report includes a second monitoring descriptor object that delivers information on variables and events to be reported.

In another example, the NBMP source 101 may send a monitoring update request to the workflow manager 103 via a workflow API. The NBMP source 101 may specify the desired variables and events in the first monitoring descriptor object in the monitoring update request. In response to the monitoring update request, workflow manager 103 may generate and send a monitoring report to NBMP source 101 . The monitoring report includes a second monitoring descriptor object that delivers information on variables and events to be reported.

13 shows a table of parameters and corresponding types for parameters in a monitoring descriptor, and FIG. 14 shows an example of a monitoring descriptor schema according to some embodiments of the present disclosure. Note that system-events contains events belonging to the media processing system and can be provided by the cloud in the same format as the function's events. Also note that system-variables contains variables that belong to the media processing system and can be provided by the cloud in the same format as the function's variables. In some embodiments, (functional) variables may be included in a first variables descriptor object, and system variables may be included in a second variables descriptor object; (Functional) events may be included in the first events descriptor object, and system events may be included in the second events descriptor object.

In some embodiments, HTTP/1.1 is used as the protocol, and the POST method is used to send monitoring reports in POST messages. For example, the body of a POST message contains a monitoring descriptor object. In some examples, the body of the POST message also includes a request descriptor object to identify monitoring reports.

15 shows a flowchart outlining a process 1500 according to an embodiment of the present disclosure. In one example, process 1500 is executed in the cloud, such as on media processing system 100 . In some embodiments, process 1500 is implemented as software instructions, so when processing circuitry executes the software instructions, processing circuitry performs process 1500. The process starts at (S1501) and proceeds to (S1510).

At S1510, a request including first characteristics associated with a variable is received. First characteristics associated with a variable may fully describe the variable. For example, the first characteristics include the definition of the variable, the unit of the variable, the type of the variable, the universal identifier of the variable, and the like. A variable can be understood based on the first characteristics without cross-referencing other texts from the first characteristics. In some embodiments, the first properties are part of a first variables descriptor object. The first variables descriptor object contains an array of objects each associated with variables. Variables can be functional variables or system variables. The request may also include a first events descriptor object containing an array of objects each associated with events. Events can be functional events or system events.

In one example, a request is sent from NBMP source 101 to workflow manager 103 . In another example, a request is sent from workflow manager 103 to a media processing task.

At S1520, a message is generated, and the message includes the first characteristics of the variable and the updated value of the variable.

In one embodiment, the request includes a first reporting descriptor object for requesting periodic reports. The first reporting descriptor object may include a first variables descriptor object associated with variables, a first events descriptor object associated with events, and a reporting interval. Based on the first reporting descriptor object, a message is created periodically according to the reporting interval. The message may include a second report descriptor object. For example, the second reporting descriptor object includes a second variables descriptor object similar to the first variables descriptor object with updated values for the variables. The second reporting descriptor object in the message may also include a second events descriptor object having a subset of events based on occurrences of the events.

In another embodiment, the request includes a first notification descriptor object to request a notification report triggered by occurrences of events. The first notification descriptor object may include a first variables descriptor object associated with variables and a first events descriptor object associated with events. Then, in response to the occurrence of at least one of the subscribed events, a message is generated. The message includes a second notification descriptor object similar to the first notification descriptor object. For example, the second notification descriptor object includes a second variables descriptor object similar to the first variables descriptor object but with updated values for the variables. The second notification descriptor object also includes a second events descriptor object with a subset of subscribed events.

In another embodiment, the request includes a first monitoring descriptor object for requesting a monitoring report. The first monitoring descriptor object may include a first variables descriptor object associated with variables and a first events descriptor object associated with events. Then, in response to the request, a message is generated. The message includes a second monitoring descriptor object similar to the first monitoring descriptor object. For example, the second monitoring descriptor object includes a second variables descriptor object similar to the first variables descriptor object but with updated values for the variables. The second monitoring descriptor object also includes a second events descriptor object having a subset of events.

In (S1530), the message is transmitted to the recipient, and the process proceeds to S1599 and ends.

In the example of a periodic report, the first and second report descriptor objects contain a destination (eg url), and a message is sent to the destination.

In the notification report example, the first and second notification descriptor objects include a destination (eg, url), and a message is sent to the destination.

In the monitoring report example, a message is sent to the entity that sent the request.

Process 1500 may be adapted as appropriate. Step(s) of process 1500 may be modified and/or omitted. Additional step(s) may be added. Any suitable order of implementation may be used.

The technology described above may be implemented as computer software using computer readable instructions and may be physically stored on one or more computer readable media.

The methods and embodiments of this disclosure may be used individually or combined in any order. Moreover, each of the methods (or embodiments), functions or tasks may be implemented by a processing circuit (eg, one or more processors or one or more integrated circuits). In one example, one or more processors execute programs stored on non-transitory computer readable media.

The technology described above may be implemented as computer software using computer readable instructions and may be physically stored on one or more computer readable media. For example, FIG. 16 depicts a computer system 1600 suitable for implementing certain embodiments of the disclosed subject matter.

Computer software is used to generate code containing instructions that can be executed directly or through interpretation, microcode execution, etc. by one or more computer central processing units (CPUs), graphics processing units (GPUs), etc. It may be coded using any suitable machine code or computer language that may undergo compilation, linking or similar mechanisms.

Instructions may be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smart phones, gaming devices, Internet of Things devices, and the like.

The components shown in FIG. 16 for computer system 1600 are illustrative in nature and are not intended to suggest any limitation as to the scope of use or functionality of computer software implementing embodiments of the present disclosure. The configuration of the components should not be construed as having any dependency or requirement relating to any of the components illustrated in the illustrative embodiment of computer system 1600 or any combination thereof.

Computer system 1600 may include certain human interface input devices. Such human interface input devices include, for example, tactile inputs (eg: keystrokes, swipes, data glove movements), audio inputs (eg voices, claps), visual inputs (eg gestures), olfactory inputs (eg not depicted) may respond to input by one or more human users. Human interface devices also include audio (eg: voice, music, ambient sound), images (eg: scanned images, photographic images obtained from a still image camera), video (eg two-dimensional video, stereoscopic video). It can be used to capture certain media that are not necessarily directly related to conscious input by humans, such as 3D video (including video).

Input human interface devices include keyboard 1601, mouse 1602, trackpad 1603, touch screen 1610, data glove (not shown), joystick 1605, microphone 1606, scanner 1607, may include one or more of the cameras 1608 (only one of each is depicted).

Computer system 1600 may also include certain human interface output devices. Such human interface output devices may stimulate the senses of one or more human users through, for example, tactile output, sound, light, and smell/taste. Such human interface output devices may include tactile output devices (e.g., tactile feedback by touch screen 1610, data glove (not shown) or joystick 1605, but not serving as input devices). devices), audio output devices (e.g., speakers 1609, headphones (not depicted)), visual output devices (e.g., including CRT screens, LCD screens, plasma screens, OLED screens) screens 1610, each with or without touch screen input capabilities, each with or without tactile feedback capabilities - some of which provide three-dimensional or higher output through means such as two-dimensional visual output or stereoscopic output. capable of printing - may include virtual reality glasses (not depicted), holographic displays and smoke tanks (not depicted)), and printers (not depicted).

Computer system 1600 includes optical media including CD/DVD ROM/RW 1620 with CD/DVD or similar media 1621, thumb drive 1622, removable hard drive or solid state drive 1623, tape and It may also include human accessible storage devices and their associated media, such as legacy magnetic media such as a floppy disk (not shown), special ROM/ASIC/PLD based devices such as security dongles (not shown), and the like.

Those skilled in the art should also understand that the term "computer readable medium" as used in connection with the presently disclosed subject matter does not include transmission media, carrier waves, or other transitory signals.

Computer system 1600 may also include interfaces to one or more communication networks. The network can be wireless, wired, optical, for example. Networks can also be local, wide area, metro, vehicular and industrial, real-time, delay tolerant, and the like. Examples of networks include local area networks such as Ethernet, wireless LANs, cellular networks including GSM, 3G, 4G, 5G, LTE, etc., TV wired or wireless wide area digital networks including cable TV, satellite TV and terrestrial broadcast TV; Including automotive and industrial applications including CANBus. A specific network typically requires a specific universal data port (eg, a USB port of computer system 1600) or an external network interface adapter connected to peripheral bus 1649; Other networks are typically incorporated into the core of computer system 1600 by being connected to a system bus as described below (e.g., an Ethernet interface integrated into a PC computer system or a cellular network interface integrated into a smart phone computer system). incorporated into). Using any of these networks, computer system 1600 can communicate with other entities. Such communication may be one-way, receive only (eg, broadcast TV), one-way transmit only (eg, from CANbus to specific CANbus devices), or two-way (eg, using local area or wide area digital networks to another computer). systems). As described above, specific protocols and protocol stacks may be used in respective networks and network interfaces.

The aforementioned human interface devices, human accessible storage devices and network interfaces may be coupled to core 1640 of computer system 1600 .

The core 1640 includes one or more central processing units (CPUs) 1641, graphics processing units (GPUs) 1642, specialized programmable processing units in the form of field programmable gate areas (FPGAs) 1643, and hardware for specific tasks. Accelerator 1644 and the like. Along with internal mass storage 1647 such as read-only memory (ROM) 1645, random access memory 1646, internal non-user accessible hard drives, SSDs, etc., these devices may be connected via system bus 1648. there is. In some computer systems, system bus 1648 may be accessible in the form of one or more physical plugs to enable expansion by additional CPUs, GPUs, and the like. Peripheral devices can be connected directly to the core's system bus 1648 or via a peripheral bus 1649 . Architectures for the peripheral bus include PCI, USB, etc.

CPU 1641 , GPU 1642 , FPGA 1643 , and accelerator 1644 may, in combination, execute specific instructions that may constitute the computer code described above. Corresponding computer code may be stored in ROM 1645 or RAM 1646. Transient data may also be stored in RAM 1646 while permanent data may be stored in internal mass storage 1647, for example. Fast storage and storage of any of the memory devices using cache memory, which may be closely associated with one or more of the CPU 1641, GPU 1642, mass storage 1647, ROM 1645, RAM 1646, etc. search may be possible.

A computer readable medium may have computer code for performing various computer implemented operations. The media and computer code may be specially designed and constructed for the purposes of this disclosure, or may be of the kind well known and available to those skilled in the art of computer software.

By way of example and not limitation, computer system 1600 having an architecture, particularly core 1640, is a processor(s) (including CPUs, GPUs, FPGAs, accelerators, etc.) implemented in one or more tangible computer readable media. It can provide functionality as a result of running the software. Such computer readable media may be media associated with specific storage of core 1640 having a non-transitory nature, such as core internal mass storage 1647 or ROM 1645, as well as user-accessible mass storage as introduced above. can Software implementing various embodiments of the present disclosure may be stored on such devices and executed by core 1640 . A computer readable medium may include one or more memory devices or chips, depending on the particular needs. Software is such that the core 1640 and in particular the processors therein (including CPU, GPU, FPGA, etc.) define the data structures stored in the RAM 1646 and the processes defined by the software. Including modifying data structures to cause execution of specific processes or specific portions of specific processes described herein. Additionally or alternatively, the computer system may include circuitry (e.g., accelerator 1644) that may operate in place of or in conjunction with software to carry out certain processes or particular portions of particular processes described herein. may provide functionality as a result of logic that is hardwired into or otherwise implemented. Any reference to software may include logic and vice versa where appropriate. Reference to a computer readable medium may include circuitry that stores software for execution (eg, an integrated circuit (IC)), circuitry that implements logic for execution, or, where appropriate, both. The present disclosure includes any suitable combination of hardware and software.

Although this disclosure has described several exemplary embodiments, there are alterations, substitutions, and various alternative equivalents that fall within the scope of this disclosure. It is therefore to be understood that those skilled in the art may devise numerous systems and methods that embody the principles of this disclosure and are therefore within its spirit and scope, although not explicitly shown or described herein. will be.

Claims (20)

As a method for a cloud service,
Receiving, by processing circuitry operating for a cloud service, a request comprising at least first characteristics associated with a variable, the first characteristics describing the variable, the request further comprising at least second characteristics associated with an event. wherein the second characteristics describe the event, the variable is one of a function variable and a system variable, and the event is one of a function event and a system event;
generating, by the processing circuitry, a message comprising the first characteristics associated with the variable, the updated value of the variable, and the second characteristics associated with the event to indicate occurrence of the event; and
transmitting, by the processing circuitry, the message to a recipient;
How to include. The method of claim 1 , wherein the first characteristics include at least one of a definition of the variable, a unit of the variable, a type of the variable, and a universal identifier of the variable. The method of claim 1 , wherein the processing circuitry is configured to establish and manage workflows for the cloud service. The method of claim 1 , wherein the processing circuitry is configured to perform one or more tasks within a workflow for the cloud service. According to claim 1,
the request includes at least a first variables descriptor object associated with variables, a first events descriptor object associated with events, and a first report descriptor object having a reporting interval;
Generating the message is:
A second reporting descriptor object having a second variables descriptor object having updated values for the variables and a second events descriptor object associated with a subset of the events, at the time of the reporting interval for the previous message. generating the message to
Including, method. According to claim 1,
The request includes a first notification descriptor object having at least a first variables descriptor object associated with variables and a first events descriptor object associated with subscribed events, and generating the message comprises:
In response to the occurrence of at least one of the subscribed events, a second variables descriptor object having updated values for the variables and a second events descriptor object associated with the subset of subscribed events. Generating the message including a reporting descriptor object.
Including, method. According to claim 1,
the request includes a first monitoring descriptor object having at least a first variables descriptor object associated with variables and a first events descriptor object associated with events;
The method is:
receiving the request sent from a monitoring entity;
In response to the request, generate the message comprising a second reporting descriptor object having a second variables descriptor object with updated values for the variables and a second events descriptor object associated with the subset of events. doing; and
sending the message to the monitoring entity;
Further comprising a, method. 2. The method of claim 1, wherein the message further comprises a request descriptor object identifying the request. As a device in the cloud for providing cloud services,
A processing circuit configured to perform the method of any one of claims 1 to 8.
Including, device. A computer readable medium having stored thereon instructions, which when executed by a computer for a cloud service causes the computer to perform the method of any one of claims 1 to 8.
delete delete delete delete delete delete delete delete delete delete

Images