Method and system for managing network-based media processing workflow

Abstract

A method and system for managing a network-based media processing (NBMP) workflow are provided. The method includes: obtaining a syntax element from a descriptor corresponding to a network-based media processing (NBMP) workflow or a task included in the workflow, wherein the syntax element indicates a protocol feature of a protocol corresponding to an input or output of the task or the workflow; deriving a workflow based on the task; and managing at least one media processing entity according to the derived workflow, wherein the protocol feature includes at least one of the following items associated with the input or output: non-necessity, timing, sequence, quantity, delay, and size.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 176,799, filed on April 19, 2021, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] Embodiments of the present disclosure relate to Network Based Media Processing (NBMP) of the Moving Picture Experts Group (MPEG), and more particularly to managing NBMP workflows. Background Art

[0004] MPEG's Network-Based Media Processing (NBMP) project develops the concept of processing media on the cloud. The draft NBMP international specification shows great potential in improving media processing efficiency, deploying media services faster and at a lower cost, and providing the ability to deploy at scale by leveraging public, private or hybrid cloud services.

[0005] Although the NBMP current specification defines the general characteristics of any input or output of a workflow, the NBMP current specification does not define protocol characteristics. Summary of the invention

[0006] According to an embodiment, a method for managing a network-based media processing (NBMP) workflow, the method comprising: obtaining a syntax element from a descriptor corresponding to the NBMP workflow or a task included in the NBMP workflow, the syntax element indicating a protocol feature of a protocol corresponding to an input or output of the task or the NBMP workflow; deriving the NBMP workflow based on the task; and managing at least one media processing entity according to the derived workflow, wherein the protocol feature comprises at least one of the following associated with the input or output of the task or the NBMP workflow: non-necessity, timing, sequence, quantity, delay, and size.

[0007] According to an embodiment, a system for managing a network-based media processing (NBMP) workflow, the system includes a workflow manager, the workflow manager including: at least one memory for storing program code; and at least one processor configured to read the program code and operate according to the instructions of the program code, the program code including: an acquisition code configured to cause at least one processor to obtain a syntax element from a descriptor corresponding to the NBMP workflow or a task included in the NBMP workflow, the syntax element indicating a protocol feature of a protocol corresponding to an input or output of the task or the NBMP workflow; a derivation code configured to cause at least one processor to derive the NBMP workflow based on the task; and a management code configured to cause at least one processor to manage at least one media processing entity according to the derived workflow, wherein the protocol feature includes at least one of the following associated with the input or output of the task or the NBMP workflow: non-necessity, timing, sequence, quantity, delay, and size.

[0008] According to an embodiment, a non-transitory computer-readable medium stores computer code, and the computer code is configured to, when executed by at least one processor of a workflow manager, cause the at least one processor to perform the following: obtain syntax elements from a descriptor corresponding to a network-based media processing (NBMP) workflow or a task included in the NBMP workflow, the syntax elements indicating protocol characteristics of a protocol corresponding to the task or the input or output of the NBMP workflow; derive the NBMP workflow based on the task; and manage at least one media processing entity according to the derived workflow, wherein the protocol characteristics include at least one of the following associated with the input or output: non-necessity, timing, sequence, quantity, delay, and size. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] Figure 1 is a diagram of an environment in which the methods, apparatuses, and systems described herein may be implemented, according to an embodiment.

[0011] Figure 2 yes Figure 1 A block diagram of example components of one or more devices.

[0012] Figure 3 is a block diagram of a NBMP system according to an embodiment.

[0013] Figure 4 is a block diagram of an example of a workflow management process according to an embodiment.

[0014] Figure 5 is a block diagram of an example of computer code according to an embodiment. DETAILED DESCRIPTION

[0015] 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.

[0016] 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 radio phone, etc.), a wearable device (e.g., 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.

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

[0018] In some implementations, as shown, the platform 120 may be hosted in a cloud computing environment 122. It should be noted that although 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.

[0019] Cloud computing environment 122 includes an environment hosting platform 120. Cloud computing environment 122 can 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 can include a set of computing resources 124 (collectively referred to as "computing resources 124" and a single computing resource as "computing resource 124").

[0020] The computing resources 124 include one or more personal computers, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, the computing resources 124 may host the platform 120. Cloud resources may include computing instances running 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 may communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0021] like Figure 1 As further shown, the computing resources 124 include a set of cloud resources, such as one or more applications ("APP") 124-1, one or more virtual machines ("VM") 124-2, virtualized storage ("VS") 124-3, one or more hypervisors ("HYP") 124-4, etc.

[0022] The applications 124-1 include one or more software applications that may be provided to or accessed by the user device 110 and / or the platform 120. The applications 124-1 do not require software applications to be installed and run on the user device 110. For example, the applications 124-1 may 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 may send information to / receive information from one or more other applications 124-1 via the virtual machine 124-2.

[0023] The virtual machine 124-2 includes a software implementation of a machine (e.g., a computer) that executes programs similar to a physical machine. Depending on the degree of correspondence and purpose of the virtual machine 124-2 to any real machine, the virtual machine 124-2 can be a system virtual machine or a process virtual machine. A system virtual machine can provide a complete system platform that supports the operation of a complete operating system ("OS"). A process virtual machine can run a single program and can support a single process. In some implementations, the virtual machine 124-2 can run 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-term data transfer.

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

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

[0026] 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 (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-based network, etc., and / or a combination of these networks or other types of networks.

[0027] Figure 1 The number and arrangement of devices and networks shown 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. Figure 1Two or more of the devices shown may be implemented in a single device, or Figure 1 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, one set of devices (eg, one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.

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

[0029] 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.

[0030] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, 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 cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, and a corresponding drive.

[0031] Input components 250 include components that allow device 200 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, input 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)).

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

[0033] 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.

[0034] 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. When executed, the software instructions stored in the memory 230 and / or storage component 240 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. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

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

[0036] In an embodiment of the present disclosure, a NBMP system 300 is provided. Figure 3 , the NBMP system 300 includes a NBMP source 310, a NBMP workflow manager 320, a function repository 330, one or more media processing entities 350, a media source 360 ​​and a media sink 370.

[0037] The NBMP source 310 may receive instructions from a third-party entity, may communicate with the NBMP workflow manager 320 via the NBMP workflow API 392, and may communicate with the function repository 330 via the function discovery API 391. For example, the NBMP source 310 may send a workflow description document (WDD) to the NBMP workflow manager 320, and may read a function description of a function stored in the function repository 330, wherein the function is a media processing function stored in a memory of the function repository 330, such as a media decoding function, a feature point extraction function, a camera parameter extraction function, a projection method, a seam information extraction function, a mixing function, a post-processing function, and an encoding function. The NBMP source 310 may include at least one processor and a memory storing code, or may be implemented by at least one processor and a memory storing code, wherein the code is configured to cause the at least one processor to perform the function of the NBMP source 310.

[0038] NBMP source 310 may request NBMP workflow manager 320 to create a workflow by sending a workflow description document, the workflow including tasks 352 to be performed by one or more media processing entities 350. The workflow description document may include multiple descriptors, each of which may have multiple parameters.

[0039] For example, the NBMP source 310 may select functions stored in the function repository 330 and send a workflow description document including various descriptors for describing details such as input and output data, required functions, and requirements of the workflow to the NBMP workflow manager 320. The workflow description document may include a set of task descriptions and connection mappings of inputs and outputs of tasks 352 to be performed by one or more media processing entities 350. When the NBMP workflow manager 320 receives such information from the NBMP source 310, the NBMP workflow manager 320 may create a workflow by instantiating tasks based on the function names and connecting the tasks according to the connection mappings.

[0040] Alternatively or in addition, the NBMP source 310 may request the NBMP workflow manager 320 to create a workflow by using a set of keywords. For example, the NBMP source 310 may send a workflow description document including a set of keywords to the NBMP workflow manager 320, and the NBMP workflow manager 320 may use the set of keywords to find suitable functions stored in the function repository 330. When the NBMP workflow manager 320 receives such information from the NBMP source 310, the NBMP workflow manager 320 may create a workflow by searching for suitable functions using keywords that may be specified in a processing descriptor of the workflow description document, and use other descriptors in the workflow description document to configure tasks, and connect the tasks to create a workflow.

[0041] The NBMP workflow manager 320 may communicate with the function repository 330 via a function discovery API 393, which may be the same or different API from the function discovery API 391, and the NBMP workflow manager 320 may communicate with one or more media processing entities 350 via an API 394 (e.g., an NBMP task API). The NBMP workflow manager 320 may include or be implemented by at least one processor and a memory storing code, the code being configured to cause the at least one processor to perform the functions of the NBMP workflow manager 320.

[0042] The NBMP workflow manager 320 may use the API 394 to set, configure, manage, and detect one or more tasks 352 in the tasks of the workflow that may be performed by one or more media processing entities 350. In one embodiment, the NBMP workflow manager 320 may use the API 394 to update and destroy the tasks 352. In order to configure, manage, and detect the tasks 352 of the workflow, the NBMP workflow manager 320 may send messages such as requests to the one or more media processing entities 350, wherein each message may have multiple descriptors and each descriptor may have multiple parameters. Each task 352 may include a media processing function 354 and a configuration 353 of the media processing function 354.

[0043] In one embodiment, after receiving a workflow description document that does not include a task list (e.g., includes a keyword list but does not include a task list) from the NBMP source 310, the NBMP workflow manager 320 may select a task based on the description of the task in the workflow description document to search the function repository 330 through the function discovery API 393, thereby finding a suitable function to run as a task 352 of the current workflow. For example, the NBMP workflow manager 320 may select a task based on keywords provided in the workflow description document. After determining a suitable function by using keywords or a set of task descriptions provided by the NBMP source 310, the NBMP workflow manager 320 may configure the selected task in the workflow by using the API 394. For example, the NBMP workflow manager 320 may extract configuration data from the information received from the NBMP source, and configure the task 352 based on the configuration data.

[0044] The one or more media processing entities 350 may be configured to receive media content from a media source 360, process the media content according to a workflow including tasks 352 created by the NBMP workflow manager 320, and output the processed media content to a media receiver 370. Each of the one or more media processing entities 350 may include or be implemented by at least one processor and a memory storing code, the code being configured to cause the at least one processor to perform the functions of the media processing entity 350.

[0045] Media source 360 ​​may include a memory for storing media and may be integrated or separate from NBMP source 310. In one embodiment, NBMP workflow manager 320 may notify NBMP source 310 when the workflow is ready, and media source 360 ​​may send media content to one or more media processing entities 350 based on the notification that the workflow is ready.

[0046] The media receiver 370 may include or be implemented by at least one processor and at least one display configured to display media processed by the one or more media processing entities 350 .

[0047] As discussed above, messages arriving at the NBMP workflow manager 320 from the NBMP source 310 (e.g., a workflow description document for requesting the creation of a workflow) and messages from the NBMP workflow manager 320 to one or more media processing entities 350 (e.g., a message for causing a workflow to be executed) may include multiple descriptors, each of which may have multiple parameters. In an embodiment, communications between any components of the NBMP system 300 using an API may include multiple descriptors, each of which may have multiple parameters.

[0048] As discussed above, while the NBMP current specification defines the general characteristics of any input or output of a workflow, the NBMP current specification does not define protocol characteristics.

[0049] According to an embodiment, parameters such as protocol features may be added to the NBMP specification.

[0050] For example, in an embodiment, parameters such as those shown in Table 1 below may be used for the NBMP process.

[0051] Table 1

[0052]

[0053]

[0054] In the above Table 1, the part indicated by italics may represent newly added parameters according to an embodiment. In an embodiment, these parameters may be used for any suitable NBMP element. For example, in an embodiment, the parameters of Table 1 may be included in an input descriptor or an output descriptor (the input descriptor or the output descriptor may be included in a workflow description document (WDD), for example), or may be included in a descriptor such as a task descriptor, or may be included in any other descriptor discussed herein.

[0055] As can be seen in Table 1, the protocol parameters or protocol features may include, for example, a "nonessentiality" parameter. In an embodiment, if the value of this parameter is set to "true", then the input may not be required. In an embodiment, if the value of this parameter is set to "false", then the output may not be guaranteed to be available. The default value of this parameter may be "false".

[0056] As can be seen in Table 1, the protocol parameters or protocol features may include, for example, a "between-request" parameter. In an embodiment, this parameter may specify, for an output, the minimum possible duration between two issued pushes, or, for an input, the minimum allowed duration between two issued pushes. In an embodiment, this parameter may specify, for an input, the minimum possible duration between two issued pulls, or, for an output, the minimum allowed duration between two issued pulls.

[0057] As can be seen in Table 1, the protocol parameters or protocol features may include, for example, an "out-of-order" parameter. In an embodiment, this parameter may specify the maximum length of an out-of-order push or out-of-order pull. In an embodiment, the default value may be "0".

[0058] As can be seen in Table 1, the protocol parameters or protocol features may include, for example, a "parallel-requests" parameter. In an embodiment, this parameter may specify the maximum number of pushes that may be used for output, the maximum number of pulls that may be used for input, the maximum number of pushes allowed for input, or the maximum number of pulls allowed for output. In an embodiment, the default value may be "0".

[0059] As can be seen in Table 1, protocol parameters or protocol features may include, for example, a "duration" parameter. In an embodiment, this parameter may specify the availability of data (e.g., in milliseconds) from the time the data appears in the output when the data is pulled.

[0060] As can be seen in Table 1, the protocol parameters or protocol features may include, for example, a "response-latency" parameter. In an embodiment, this parameter may specify the maximum time to respond to a pull request or a push request.

[0061] As can be seen in Table 1, the protocol parameters or protocol features may include, for example, a "max-payload" parameter. In an embodiment, this parameter may specify a maximum size, such as a maximum payload size for a push request, or a maximum payload size for a response to a pull request.

[0062] In an embodiment, the parameter "nonessentiality" may correspond to a general characteristic of input and output and may not be directly related to a specific protocol.

[0063] Thus, an embodiment may involve defining a set of parameters by which general characteristics of a pull or push protocol for the input / output of a task or workflow may be defined in the NMBP standard, wherein the frequency of requests, the minimum duration between requests, the possibility of parallel and / or out-of-order requests, the maximum size of requests, response latency, and the maximum payload size may be defined.

[0064] Embodiments may further relate to non-essential parameters for inputs and outputs of an NBMP workflow or task, wherein, if the flag is set, it may mean that the availability of the input is not essential for the normal operation of the NBMP workflow or task, or that the output may sometimes be unavailable, and therefore the output should not be regarded as a necessary output for further processing or a necessary output of the NBMP workflow.

[0065] refer to Figure 3 and Figure 4 , the process 400 performed by the NBMP workflow manager 320 is described below.

[0066] Figure 4 is a flow diagram of an example process 400 .

[0067] like Figure 4 As shown, process 400 may include: obtaining a syntax element from a descriptor corresponding to a network-based media processing (NBMP) workflow or a task included in the NBMP workflow, the syntax element indicating a protocol feature of a protocol corresponding to an input or output of the task or the NBMP workflow (box 410).

[0068] Further Figure 4 As shown, process 400 may include deriving a NBMP workflow based on the tasks (block 420).

[0069] Further Figure 4As shown, process 400 may include managing at least one media processing entity according to the derived workflow (block 430).

[0070] In an embodiment, the descriptor may be one of: an input descriptor corresponding to a NBMP workflow, an output descriptor corresponding to a NBMP workflow, an input descriptor corresponding to a task, or an output descriptor corresponding to a task.

[0071] In an embodiment, a protocol feature may include non-necessity associated with an input or an output, wherein, based on the protocol feature corresponding to the input, the protocol feature specifies that the operation of the NBMP workflow or task does not require the input, and wherein, based on the protocol feature corresponding to the output, the protocol feature specifies that there is no guarantee that the output is available.

[0072] In an embodiment, a protocol feature may include timing associated with an input or an output, wherein, based on the protocol feature corresponding to the input, the protocol feature specifies a minimum possible duration between two issued pulls or a minimum allowed duration between two issued pushes, and wherein, based on the protocol feature corresponding to the output, the protocol feature specifies a minimum possible duration between two issued pushes or a minimum allowed duration between two issued pulls.

[0073] In an embodiment, a protocol signature may include an order associated with an input or output, and a protocol signature may specify a maximum length for an out-of-order push or out-of-order pull.

[0074] In an embodiment, a protocol feature may include a quantity associated with an input or an output, wherein based on the protocol feature corresponding to the input, the protocol feature specifies a maximum possible number of parallel pulls or a maximum allowed number of parallel pushes, and wherein based on the protocol feature corresponding to the output, the protocol feature specifies a maximum possible number of parallel pushes or a maximum allowed number of parallel pulls.

[0075] In an embodiment, a protocol characteristic may include timing corresponding to an input or an output, and based on the protocol characteristic corresponding to an input, the protocol characteristic may specify an amount of time before data is available after being pulled.

[0076] In embodiments, protocol characteristics may include latency for input or output, and protocol characteristics may specify a maximum time to respond to a push request or a pull request.

[0077] In embodiments, protocol characteristics may include the size of an input or output, and protocol characteristics may specify a maximum size for a response to a pull request or a push request.

[0078] Although Figure 4 An exemplary block diagram of process 400 is shown, but in some implementations, Figure 4Process 400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted. Additionally or alternatively, two or more blocks of process 400 may be performed in parallel.

[0079] Further, the proposed method can 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 a program stored in a non-transitory computer-readable medium to perform one or more proposed methods.

[0080] According to an embodiment of the present disclosure, at least one processor and a memory storing computer code or program code may be provided. The computer code may be configured to perform any number of aspects of the present disclosure when executed by the at least one processor.

[0081] For example, refer to Figure 5 , the computer code 500 may be implemented in the NBMP system 300. For example, the computer code may be stored in a memory of the NBMP workflow manager 320 and may be executed by at least one processor of the NBMP workflow manager 320. For example, the computer code may include an obtaining code 510, a deriving code 520, and a managing code 530.

[0082] In an embodiment, the acquisition code 510, the derivation code 520 and the management code 530 may be respectively configured to cause the NBMP workflow manager 320 to execute the above reference Figure 4 Describe various aspects of the process.

[0083] The embodiments of the present disclosure may be used alone or in any order. In addition, each embodiment (and method thereof) may be implemented by a processing circuit (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.

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

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

[0086] Although combinations of features are described 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 can be combined in ways that are not specifically described in the claims and / or disclosed in the specification. Although each dependent claim listed below may only be directly dependent on one claim, the disclosure of possible implementations includes the combination of each dependent claim with every other claim in the claim set.

[0087] Elements, actions or instructions used herein should not be understood as critical or necessary unless so clearly described. In addition, as used herein, the articles "one" and "an" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". In the case where the intention is only one item, the term "one" or similar language is used. In addition, as used herein, the term "having", "containing", "having" or similar terms are intended to be open terms. In addition, the phrase "based on" means "based on at least in part", unless otherwise explicitly stated.

Claims

1. A method for managing a network-based media processing NBMP workflow, the method comprising: Obtaining a syntax element from a descriptor corresponding to an NBMP workflow or a task included in the NBMP workflow, the syntax element indicating a protocol feature of a protocol corresponding to an input or output of the task or the NBMP workflow; Deriving the NBMP workflow based on the task; as well as managing at least one media processing entity according to the derived workflow, The protocol characteristics include at least one of the following associated with the input or the output of the task or the NBMP workflow: non-necessity, timing, sequence, quantity, delay and size; the size is used to specify the maximum payload size of a push request, or the maximum payload size of a response to a pull request.

2. The method according to claim 1, wherein: The descriptor is one of the following: an input descriptor corresponding to the NBMP workflow, an output descriptor corresponding to the NBMP workflow, an input descriptor corresponding to the task, or an output descriptor corresponding to the task.

3. The method according to claim 1 or 2, wherein: said protocol characteristic comprising said non-essentiality associated with said input or said output, wherein, based on the correspondence between the protocol feature and the input, the protocol feature specifies that the operation of the NBMP workflow or the task does not require the input, Wherein, based on the correspondence between the protocol feature and the output, the protocol feature specifies that there is no guarantee that the output is available.

4. The method according to claim 1 or 2, wherein: said protocol characteristics including said timing associated with said input or said output, wherein, based on the protocol feature corresponding to the input, the protocol feature specifies a minimum possible duration between two issued pulls or a minimum allowed duration between two issued pushes, Wherein, based on the protocol feature corresponding to the output, the protocol feature specifies a minimum possible duration between two issued pushes or a minimum allowed duration between two issued pulls.

5. The method according to claim 1 or 2, wherein: said protocol characteristics comprising said order associated with said input or said output, The protocol feature specifies the maximum length of an out-of-order push or out-of-order pull.

6. The method according to claim 1 or 2, wherein: said protocol characteristic comprising said quantity associated with said input or said output, wherein, based on the protocol feature corresponding to the input, the protocol feature specifies a maximum possible number of parallel pulls or a maximum allowed number of parallel pushes, Wherein, based on the correspondence between the protocol feature and the output, the protocol feature specifies a maximum possible number of parallel pushes or a maximum allowed number of parallel pulls.

7. The method according to claim 1 or 2, wherein: The protocol characteristics include the timing corresponding to the input or the output, Wherein, based on the protocol characteristic corresponding to the input, the protocol characteristic specifies an amount of time before data is available after being pulled.

8. A system for managing a network-based media processing NBMP workflow, the system comprising a workflow manager, the workflow manager comprising: at least one memory for storing program code; as well as At least one processor is configured to read the program code and operate according to the instructions of the program code, wherein the program code includes: Obtaining code configured to cause the at least one processor to obtain a syntax element from a descriptor corresponding to an NBMP workflow or a task included in the NBMP workflow, wherein the syntax element indicates a protocol feature of a protocol corresponding to an input or output of the task or the NBMP workflow; A derivation code configured to cause the at least one processor to derive the NBMP workflow based on the task; and management code configured to cause the at least one processor to manage at least one media processing entity according to the derived workflow, The protocol characteristics include at least one of the following associated with the input or output of the task or the NBMP workflow: non-necessity, timing, sequence, quantity, delay and size; the size is used to specify the maximum payload size of a push request, or the maximum payload size of a response to a pull request.

9. The system according to claim 8, wherein: The descriptor is one of the following: an input descriptor corresponding to the NBMP workflow, an output descriptor corresponding to the NBMP workflow, an input descriptor corresponding to the task, or an output descriptor corresponding to the task.

10. The system according to claim 8 or 9, wherein: said protocol characteristic comprising said non-essentiality associated with said input or said output, wherein, based on the correspondence between the protocol feature and the input, the protocol feature specifies that the operation of the NBMP workflow or the task does not require the input, Wherein, based on the correspondence between the protocol feature and the output, the protocol feature specifies that there is no guarantee that the output is available.

11. The system according to claim 8 or 9, wherein: said protocol characteristics including said timing associated with said input or said output, wherein, based on the protocol feature corresponding to the input, the protocol feature specifies a minimum possible duration between two issued pulls or a minimum allowed duration between two issued pushes, Wherein, based on the protocol feature corresponding to the output, the protocol feature specifies a minimum possible duration between two issued pushes or a minimum allowed duration between two issued pulls.

12. The system according to claim 8 or 9, wherein: said protocol characteristics comprising said order associated with said input or said output, The protocol feature specifies the maximum length of an out-of-order push or out-of-order pull.

13. The system according to claim 8 or 9, wherein: said protocol characteristic comprising said quantity associated with said input or said output, wherein, based on the protocol feature corresponding to the input, the protocol feature specifies a maximum possible number of parallel pulls or a maximum allowed number of parallel pushes, Wherein, based on the correspondence between the protocol feature and the output, the protocol feature specifies a maximum possible number of parallel pushes or a maximum allowed number of parallel pulls.

14. The system according to claim 8 or 9, wherein: The protocol characteristics include the timing corresponding to the input or the output, Wherein, based on the protocol characteristic corresponding to the input, the protocol characteristic specifies an amount of time before data is available after being pulled. 15 . A non-transitory computer readable medium storing computer code, wherein the computer code is configured to, when executed by at least one processor of a workflow manager, cause the at least one processor to perform the method according to any one of claims 1 to 7.

Images