Method, manager and medium for managing network-based media processing workflow

By introducing continuity flags into MPEG network-based media processing specifications, the problem of data loss during updates is solved, seamless workflow updates and resource optimization are achieved, ensuring the continuity and efficient management of data flows.

CN115668373BActive Publication Date: 2024-11-15TENCENT AMERICA LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280003940.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2022-03-25
Filing Date
2022-03-28
Publication Date
2024-11-15
Estimated Expiration
2042-03-28

AI Technical Summary

Technical Problem

Existing MPEG network-based media processing specifications do not define whether the data flow needs to be continued when updating the workflow, and data may be lost during the update, lacking seamless continuity characteristics.

Method used

Ensure seamless switching between workflows by using continuity flags when workflow updates, providing a way to manage media processing entities, ensuring continuity and no data loss of data, including obtaining and updating workflow description documents , create and manage workflows, using continuity flags to indicate that the new workflow is a continuation of the old workflow.

Benefits of technology

It realizes seamless switching or updating cloud workflows during operation, avoids data flow interruption or data loss, and adds seamless continuity features to the MPEG specification, supporting accurate time switching and resource optimization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115668373B_ABST
    Figure CN115668373B_ABST
Patent Text Reader

Abstract

A method and system for managing a network-based media processing (NBMP) workflow are provided. The method includes: obtaining a first network-based media processing (NBMP) workflow description document (WDD); creating a first workflow corresponding to the first NBMP WDD; managing at least one media processing entity (MPE) according to the first workflow; obtaining an update to the first NBMP WDD, the update including a second NBMP WDD, wherein the second NBMP WDD includes a continuity flag, the continuity flag indicating that a second workflow corresponding to the second NBMP WDD is a continuation of the first workflow; creating a second workflow based on the second NBMP WDD; and in response to creating the second workflow, managing at least one MPE according to the second workflow.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 176,761, 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 allows for an update workflow, the NBMP current specification does not define whether the data flow needs to continue or whether any data should not be lost during the update. Summary of the invention

[0006] In an embodiment, a method performed by at least one processor of a workflow manager of a media system includes: obtaining a first network-based media processing (NBMP) workflow description document (WDD); creating a first workflow corresponding to the first NBMP WDD; managing at least one media processing entity (MPE) according to the first workflow; obtaining an update to the first NBMP WDD, the update including a second NBMP WDD, wherein the second NBMP WDD includes a continuity flag indicating that a second workflow corresponding to the second NBMP WDD is a continuation of the first workflow; creating a second workflow based on the second NBMP WDD; and in response to creating the second workflow, managing at least one MPE according to the second workflow.

[0007] In an embodiment, a workflow manager of a media system includes: at least one memory 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: a first acquisition code configured to cause the at least one processor to acquire a first network-based media processing (NBMP) workflow description document (WDD); a first creation code configured to cause the at least one processor to create a first workflow corresponding to the first NBMP WDD; a first management code configured to cause the at least one processor to manage at least one media processing entity (MPE) according to the first workflow; a second acquisition code configured to cause the at least one processor to acquire an update to the first NBMP WDD, the update including a second NBMP WDD, wherein the second NBMP WDD includes a continuity flag indicating that the second workflow corresponding to the second NBMP WDD is a continuation of the first workflow; a second creation code configured to cause the at least one processor to create a second workflow based on the second NBMP WDD; and a second management code configured to cause the at least one processor to manage at least one MPE according to the second workflow in response to the creation of the second workflow.

[0008] In an embodiment, a non-transitory computer-readable medium stores computer code, which is configured to, when executed by at least one processor of a workflow manager implementing a media system, cause the at least one processor to: obtain a first network-based media processing (NBMP) workflow description document (WDD); create a first workflow corresponding to the first NBMP WDD; manage at least one media processing entity (MPE) according to the first workflow; obtain an update to the first NBMP WDD, the update including a second NBMP WDD, wherein the second NBMP WDD includes a continuity flag indicating that a second workflow corresponding to the second NBMP WDD is a continuation of the first workflow; create a second workflow based on the second NBMP WDD; and in response to creating the second workflow, manage at least one MPE according to the second workflow. 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 environment of the storage system, the type 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 1 Two 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 a NBMP workflow application program interface (API) 392, and may communicate with the function repository 330 via a 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, the function being 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, the code being configured to cause the at least one processor to perform the functions 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 can use the API 394 to set, configure, manage, and supervise one or more tasks 352 in the tasks of the workflow that can be performed by one or more media processing entities 350. In one embodiment, the NBMP workflow manager 320 can use the API 394 to update and destroy the tasks 352. In order to configure, manage, and supervise the tasks 352 of the workflow, the NBMP workflow manager 320 can send messages such as requests to one or more media processing entities 350, where each message can have multiple descriptors and each descriptor has 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] Embodiments may provide a method for seamlessly switching or updating cloud workflows during operation without causing any interruption in the data flow or losing any data. Thus, embodiments may add seamless continuity features to the NBMP specification.

[0049] During the NBMP-related process, the workflow may have been running for a long time. Due to the increase in data volume, one or more tasks of the workflow may need to be split to cope with the increased load. In this case, it may be desirable not to lose data due to switching to a new workflow.

[0050] In some deployments, the current task is reusable. Therefore, the current task can be used in the updated workflow. In some applications, it may be necessary to switch to a new workflow at a precise time, such as for data collection or billing purposes.

[0051] The NBMP workflow API used to update a workflow in the current NBMP specification does not have any concept of continuity, which means that the NBMP workflow manager can stop the current workflow, update the workflow with a new workflow, and then restart the workflow, so data may be lost during this update.

[0052] Embodiments may add a continuity flag to the general descriptor, such as shown in Tables 1 and 2 below. In the case of continuity = true, the NBMP workflow manager can switch between the two workflows without losing any data. In addition, the switching time may be requested to be a certain time. For example, knowing the exact time of the switch is useful for reporting.

[0053] Table 1 - General Descriptors

[0054]

[0055]

[0056] Table 2 - General parameters

[0057]

[0058]

[0059]

[0060] In the tables herein, additions to the NBMP specification according to embodiments may be indicated by italics.

[0061] In an embodiment, two new parameters may be used for workflow updates or task updates.

[0062] In some cases, running a fully parallel workflow requires a lot of resources, and the cloud platform can prefer to keep some tasks in the workflow running during the update.

[0063] Because the NBMP client provides the new WDD, the workflow manager can identify the differences between the running workflow and the new WDD.

[0064] The NBMP client can assist in this task by providing the following information:

[0065] 1. A list of tasks that have changed.

[0066] 2. A list of connections that have changed.

[0067] Since each task has an identifier (id) in WDD, changing tasks (e.g., removing a task and replacing it with a new one) or introducing new tasks can be easily accomplished:

[0068] 1. In a running workflow, each existing task has an id.

[0069] 2. The position of the task in the running workflow is identified by the value of "instance" in the connection map.

[0070] 3. Any new tasks in the workflow update do not have an "instance" set.

[0071] Considering the above, the NBMP workflow manager can easily identify which task / function instances are new and which task / function instances are old in the updated workflow.

[0072] As for providing a list of connections, each workflow can be defined by an array of connection mapping objects. The workflow manager can compare each object in the array from workflow updates to running workflows and identify new or updated connection mapping objects. However, in order to simplify the process, in an embodiment, an id can be added to each connection mapping object.

[0073] Table 3 - Connection map array elements

[0074]

[0075]

[0076] Table 4 - Processing parameters

[0077]

[0078]

[0079]

[0080] As discussed above, in the tables herein, additions to the NBMP specification according to embodiments may be indicated by italics.

[0081] Thus, embodiments may provide a method for signaling seamless continuity of workflow operations during workflow updates, wherein no data is lost during the update, wherein a switching time is defined, and wherein, in case the requested switching time is not feasible, the actual switching time is provided in the response.

[0082] An embodiment may relate to a method for signaling old connections and new connections in a workflow update, wherein each connection has a unique identifier so that if the old connection disappears after the update, it means that the old connection is no longer valid, and the id of the new connection appearing in the workflow update indicates that the connection is a new connection, and connections with the same id are considered to be the same and do not need to be changed.

[0083] Embodiments may be directed to a method of using any of the methods described herein together to update a portion of a workflow without replacing all tasks or connections and maintaining continuity of data flow at the input and output of the workflow without loss of data.

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

[0085] Figure 4 is a flow diagram of an exemplary process 400 .

[0086] like Figure 4 As shown, process 400 may include obtaining a first network-based media processing (NBMP) workflow description document (WDD) (block 410).

[0087] Further Figure 4 As shown, process 400 may include creating a first workflow corresponding to a first NBMP WDD (block 420).

[0088] Further Figure 4 As shown, process 400 may include managing at least one media processing entity (MPE) according to a first workflow (block 430).

[0089] Further Figure 4 As shown, process 400 may include obtaining an update to a first NBMP WDD, the update including a second NBMP WDD, wherein the second NBMP WDD includes a continuity flag indicating that a second workflow corresponding to the second NBMP WDD is a continuation of the first workflow (block 440).

[0090] Further Figure 4 As shown, process 400 may include creating a second workflow based on the second NBMP WDD (block 450).

[0091] Further Figure 4 As shown, process 400 may include, when the second workflow is created, managing at least one MPE according to the second workflow (block 460).

[0092] In an embodiment, based on the continuity flag indicating that the second workflow is a continuation of the first workflow, all data corresponding to managing the at least one MPE according to the first workflow may be maintained during managing the at least one MPE according to the second workflow.

[0093] In an embodiment, the second NBMP WDD may further include a syntax element indicating a time to switch from managing the at least one MPE according to the first workflow to managing the at least one MPE according to the second workflow.

[0094] In an embodiment, the update may be one of a workflow update and a task update.

[0095] In an embodiment, a task of a first workflow may be represented by a first connection mapping object in a first NBMP WDD, wherein the first connection mapping object specifies a position of the task in a connection mapping corresponding to the first workflow and at least one connection to another element in the first workflow, and wherein the first connection mapping object includes a connection identifier that identifies the task.

[0096] In an embodiment, tasks may be maintained in the second workflow based on the connection identifier being included in the second connection mapping object in the second NBMP WDD.

[0097] In an embodiment, based on the continuity flag indicating that the second workflow is a continuation of the first workflow, all data corresponding to the execution of the task in the first workflow may be maintained in the second workflow.

[0098] Although Figure 4 An exemplary block diagram of process 400 is shown, but in some implementations, Figure 4 Process 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.

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

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

[0101] 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 a first acquisition code 510, a first creation code 520, a first management code 530, a second acquisition code 540, a second creation code 550, and a second management code 560.

[0102] In an embodiment, the first acquisition code 510, the first creation code 520, the first management code 530, the second acquisition code 540, the second creation code 550, and the second management code 560 may be respectively configured to enable the NBMP workflow manager 320 to execute the above reference Figure 4 Describe various aspects of the process.

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

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

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

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

[0107] 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 include: Acquire a first network-based media processing NBMP workflow description document WDD; Creating a first workflow corresponding to the first NBMP WDD; managing at least one media processing entity MPE according to the first workflow; Obtaining an update to the first NBMP WDD, the update comprising a second NBMP WDD, wherein the second NBMP WDD comprises a continuity flag, the continuity flag indicating that a second workflow corresponding to the second NBMP WDD is a continuation of the first workflow, and maintaining in the second workflow all data corresponding to tasks executed in the first workflow; The connection identifier indicates that when the first NBMP WDD is updated, the connection mapping element having the same connection identifier as the first NBMP WDD is the same, and if the first NBMP WDD is continuous, the data flow of the connection corresponding to the first NBMP WDD is not interrupted; creating the second workflow based on the second NBMP WDD; and In response to the second workflow being created, the at least one MPE is managed according to the second workflow.

2. The method according to claim 1, in, Based on the continuity flag indicating that the second workflow is a continuation of the first workflow, all data corresponding to managing the at least one MPE according to the first workflow is maintained during the management of the at least one MPE according to the second workflow.

3. The method according to claim 1 or 2, in, The second NBMP WDD further includes a syntax element indicating a time to switch from managing the at least one MPE according to the first workflow to managing the at least one MPE according to the second workflow.

4. The method according to claim 1 or 2, in, The update is one of a workflow update and a task update.

5. The method according to claim 1 or 2, in, The tasks of the first workflow are represented by a first connection mapping object in the first NBMP WDD, wherein the first connection map object specifies a position of the task in a connection map corresponding to the first workflow and at least one connection to another element in the first workflow, The first connection mapping object includes a connection identifier for identifying the task.

6. The method according to claim 5, in, The task is maintained in the second workflow based on the connection identifier being included in a second connection mapping object in the second NBMP WDD.

7. A workflow manager for a media system, the workflow manager include: at least one memory 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: a first acquisition code configured to enable the at least one processor to acquire a first network-based media processing NBMP workflow description document WDD; a first creation code configured to cause the at least one processor to create a first workflow corresponding to the first NBMP WDD; A first management code configured to enable the at least one processor to manage at least one media processing entity MPE according to the first workflow; a second acquisition code configured to cause the at least one processor to acquire an update to the first NBMP WDD, the update comprising a second NBMP WDD, wherein the second NBMP WDD comprises a continuity flag, the continuity flag indicating that a second workflow corresponding to the second NBMP WDD is a continuation of the first workflow, and all data corresponding to tasks executed in the first workflow are maintained in the second workflow; a connection identifier indicating that when the first NBMP WDD is updated, connection mapping elements having the same connection identifier as the first NBMP WDD are the same, and if the first NBMP WDD is continuous, a data flow of a connection corresponding to the first NBMP WDD is not interrupted; a second creation code configured to cause the at least one processor to create the second workflow based on the second NBMPWDD; and The second management code is configured to cause the at least one processor to manage the at least one MPE according to the second workflow in response to the second workflow being created.

8. The workflow manager according to claim 7, in, Based on the continuity flag indicating that the second workflow is a continuation of the first workflow, all data corresponding to managing the at least one MPE according to the first workflow is maintained during the management of the at least one MPE according to the second workflow.

9. The workflow manager according to claim 7 or 8, in, The second NBMPWDD further includes a syntax element indicating a time to switch from managing the at least one MPE according to the first workflow to managing the at least one MPE according to the second workflow.

10. The workflow manager according to claim 7 or 8, in, The update is one of a workflow update and a task update.

11. The workflow manager according to claim 7 or 8, in, The tasks of the first workflow are represented by a first connection mapping object in the first NBMPWDD, wherein the first connection map object specifies a position of the task in a connection map corresponding to the first workflow and at least one connection to another element in the first workflow, The first connection mapping object includes a connection identifier for identifying the task.

12. The workflow manager according to claim 11, in, The task is maintained in the second workflow based on the connection identifier being included in a second connection mapping object in the second NBMPWDD.

13. A computer-readable medium storing computer codes, wherein when the computer codes are executed by at least one processor implementing a workflow manager of a media system, the at least one processor is configured to perform the method according to any one of claims 1 to 6.

14. A workflow manager for a media system, include: A first acquisition module, used for acquiring a first network-based media processing NBMP workflow description document WDD; A first creation module, configured to create a first workflow corresponding to the first NBMP WDD; A first management module, configured to manage at least one media processing entity MPE according to the first workflow; a second acquisition module, configured to acquire an update to the first NBMP WDD, the update comprising a second NBMP WDD, wherein the second NBMP WDD comprises a continuity flag, the continuity flag indicating that a second workflow corresponding to the second NBMP WDD is a continuation of the first workflow, and all data corresponding to tasks executed in the first workflow are maintained in the second workflow; a connection identifier indicating that when the first NBMP WDD is updated, connection mapping elements having the same connection identifier as the first NBMP WDD are the same, and if the first NBMP WDD is continuous, a data flow of a connection corresponding to the first NBMP WDD is not interrupted; A second creation module, configured to create the second workflow based on the second NBMP WDD; and The second management module is configured to manage the at least one MPE according to the second workflow in response to the creation of the second workflow.