WO2014022968A1

WO2014022968A1 - Media service processing method and media service system

Info

Publication number: WO2014022968A1
Application number: PCT/CN2012/079775
Authority: WO
Inventors: 李勇; 施有铸
Original assignee: 华为技术有限公司
Priority date: 2012-08-07
Filing date: 2012-08-07
Publication date: 2014-02-13
Also published as: CN103748567A

Abstract

A media service processing method and a media service system, applicable in the technical field of information processing. A media service system comprises at least two task execution subsystems. Each task execution subsystem comprises a task policy device, a task data storage device and at least one task execution device, wherein the task execution device is used for obtaining first task data according to a task processing policy, and executing a task according to the first task data; and the task policy device is used for generating second task data comprising a service type, information about the execution object of second task and a second task type when needing to generate the second task data according to a second task generating policy and the task execution result by the task execution device of the first task data, and storing the second task data in a task data storage device of another task execution subsystem corresponding to the second task type, the second task generating policy comprising service processing logic corresponding to the service type. The present invention achieves the processing of a media service.

Description

Media business processing method and media business system

Technical field

The present invention relates to the field of information processing technologies, and in particular, to a media service processing method and a media service system.

Background technique

The existing media service system generally has two implementation modes when performing business processing: controlling the execution order between multiple media tasks by a workflow, or controlling the interaction between multiple media tasks by the solidified business logic. The order of execution can be thought of as a sequence of execution between a solidified workflow control media task. For example, in the media asset management system, firstly, the first executed media task is the media file acquisition, and the file that needs to be transcoded is acquired to the system; then the second executed media task is the media asset review, and the examiner is notified to review. Whether the file meets the technical and policy requirements; Finally, the third executed media task is the media asset archive, which archives the approved documents to the specified destination.

There is a service centralized control point in the above media service system. The service centralized control point sequentially calls the media task to be executed according to the requirements of the business processing, and waits for the execution of the invoked media task to execute the response, and then determines the next step according to the execution response. The media task called. This puts the media business at risk of a single point (ie, a centralized point of control in the system) failure.

Summary of the invention

The embodiment of the invention provides a media service processing method and a media service system, which avoids the risk of a single point failure caused by single point control in the system.

A first aspect of the embodiments of the present invention provides a media service system, including at least two task execution subsystems, where the task execution subsystem includes: a task policy device, a task data storage device, and at least one task execution device, where: The task data storage device acquires first task data and executes a task according to the first task data; the task processing policy includes a service type of the first task data and a first task type;

The task policy device is configured to store the task processing policy, and generate a policy according to the second task and a task execution result of the task execution device for the first task data, and generate the second task data when the second task data needs to be generated. Including the business type, the second task execution object information, and the second task type Two task data, and the second task data is stored in a task data storage device of another task execution subsystem corresponding to the second task type, the second task generation policy including a service corresponding to the service type Processing logic

The task data storage device is configured to receive first task data sent by the task policy device in the previous task execution subsystem, and store the first task data.

In a possible implementation manner of the first aspect of the embodiments of the present invention, the system further includes: at least one service request receiving device, configured to generate, according to the received service request, information including a service type, a first task execution object, and a First task data of a task type;

The task data storage device is further configured to store first task data generated by the service request receiving device.

A second aspect of the embodiments of the present invention provides a media service system, including: at least two task execution subsystems, where the task execution subsystem includes: a task data storage device and at least one task processing device, the task processing device And including a task policy module and a task execution module, where: the task execution module is configured to acquire first task data from the task data storage device according to the task processing policy stored in the task policy module, and according to the first a task data execution task; the task processing policy includes a service type of the first task data and a first task type; the task policy module is configured to store the task processing policy, and generate a policy according to the second task And executing, by the task execution module, the task execution result of the first task data, when the second task data needs to be generated, generating second task data including a service type, second task execution object information, and a second task type, and The second task data is stored to another one corresponding to the second task type Service task execution subsystem data storage device, the second task generates policy includes business logic corresponding to the service type;

The task data storage device is configured to receive first task data sent by the task processing device in the previous task execution subsystem, and store the first task data.

In a possible implementation manner of the second aspect of the embodiments of the present invention, the system further includes: at least one service request receiving device, configured to generate, according to the received service request, a service type, a first task execution object information, and a First task data of a task type;

The task data storage device is further configured to store first task data generated by the service request receiving device. A third aspect of the embodiments of the present invention provides a media service system, including: a data storage device, and at least two task execution subsystems, where the task execution subsystem includes: a task policy device and at least one task execution device, where Obtaining first task data from the data storage device and executing a task according to the first task data; the task processing policy includes a service type of the first task data and a first task type;

The task policy device is configured to store the task processing policy, and generate a policy according to the second task and a task execution result of the task execution device for the first task data, and generate the second task data when the second task data needs to be generated. Include a service type, a second task execution object information, and a second task type second task data, and store the second task data in the data storage device, where the second task generation policy includes the service Type of business processing logic;

The data storage device is configured to receive first task data sent by the task policy device in the previous task execution subsystem, and store the first task data.

In a possible implementation manner of the third aspect of the embodiments of the present invention, the system further includes: at least one service request receiving device, configured to generate, according to the received service request, information including a service type, a second task execution object, and the first First task data of the task type;

The data storage device is further configured to store first task data generated by the service request receiving device.

A fourth aspect of the embodiments of the present invention provides a media service system, including a data storage device, and at least one first task execution subsystem and at least one second task execution subsystem;

The first task execution subsystem includes: a task policy device and at least one task execution device; the second task execution subsystem includes: a task policy device, a task data storage device, and at least one task execution device; acquiring the first task And performing a task according to the first task data; the task processing policy includes a service type of the first task data and a first task type;

The task policy device is configured to store the task processing policy, and generate a policy according to the second task and a task execution result of the task execution device for the first task data, and generate the second task data when the second task data needs to be generated. Including the business type, the second task execution object information, and the second task type Two task data, and storing the second task data to the data storage device, or to a task data storage device in a second task execution subsystem corresponding to the second task type, the second The task generation policy includes business processing logic corresponding to the service type;

The task data storage device is configured to store the first task data acquired by the task execution device in the second task execution subsystem;

The data storage device is configured to store the first task data obtained by the task execution device in the first task execution subsystem.

In a possible implementation manner of the fourth aspect of the embodiments of the present invention, the system further includes: at least one service request receiving device, configured to generate, according to the received service request, information including a service type, a first task execution object, and a First task data of a task type;

The task data storage device or the data storage device is further configured to store first task data generated by the service request receiving device.

A fifth aspect of the embodiments of the present invention further provides a media service system, including: at least one first task execution subsystem and at least one second task execution subsystem, where:

The first task execution subsystem includes a task data storage device and at least one task processing device, the task processing device includes a task policy module and a task execution module; the second task execution subsystem includes a task policy device, and task data storage. The device and the at least one task execution device; the task execution module and the task execution device, configured to acquire the first task data according to the task processing policy and execute the task according to the first task data; the task processing policy includes the first task data Business type and first task type;

The task policy module and the task policy device are configured to store the task processing policy, and generate a policy according to the second task and a task execution result of the first task data, and generate, when the second task data needs to be generated, generate a service type, second task execution object information, and second task data of the second task type, and storing the second task data to task data storage in a second task execution subsystem corresponding to the second task type a device, or a task data storage device in the first task execution subsystem, the second task generation policy includes service processing logic corresponding to the service type; the task data storage device is configured to receive a previous task execution device The first task data sent by the system, and storing the first task data.

In a possible implementation manner of the fifth aspect of the embodiment of the present invention, the system further includes: Having one less service request receiving device, configured to generate, according to the received service request, first task data including a service type, first task execution object information, and a first task type;

A sixth aspect of the embodiments of the present invention provides a media service processing method, which is used for service processing of a task execution subsystem included in a media service system, including:

The task execution subsystem acquires a task processing policy, where the task processing policy includes a service type of the first task data and a first task type;

The task execution subsystem acquires corresponding first task data according to the task processing policy and executes a task according to the first task data;

The task execution subsystem generates a policy including a service type, a second task execution object information, and a second task type according to the second task generation policy and the task execution result of the first task data, when the second task data needs to be generated. Second task data, so that another task execution subsystem corresponding to the second task type performs a task according to the second task data, and the second task generation policy includes a business processing logic corresponding to the service type .

In a first possible implementation manner of the sixth aspect of the embodiments of the present invention, the task execution subsystem acquires a task processing policy, and further includes:

The task request receiving device in the media service system receives the task request, and generates first task data including the first task type and the service type according to the task request.

With reference to the sixth aspect of the embodiments of the present invention, or the first possible implementation manner of the sixth aspect, in a second implementation manner of the sixth aspect of the embodiments, the task execution policy further includes: when the task is Obtain task data when the load of the execution subsystem does not exceed the preset threshold;

The generated second task data further includes at least one of the following: a task identifier, a task execution parameter, and task control information.

With reference to the sixth aspect of the embodiments of the present invention, or the first possible implementation manner or the second possible implementation manner of the sixth aspect, in a third implementation manner of the sixth aspect of the embodiments of the present invention, the task executive The system generates a policy according to the second task and a task execution result of the task execution device for the first task data, and outputs a task execution result of the first task data when the second task data is not required to be generated. With reference to the sixth aspect of the embodiments of the present invention, or the first possible implementation manner of the sixth aspect, or the second possible implementation manner or the third implementation manner, in the fourth implementation manner of the sixth aspect of the embodiment of the present invention, The service processing logic includes at least two tasks, and an execution order relationship of the at least two tasks. The task execution result of the task execution subsystem to the first task data specifically includes: The instruction of the task execution completion of the first task type included in the first task type and the object data after execution;

Then, the second task execution object information in the second task data generated by the task execution subsystem includes the executed object data, and the second task type is a type of the next task corresponding to the first task type.

It can be seen that the media service system in this embodiment can be executed by multiple task execution subsystems, but there is no centralized control point to control the execution order between the task execution subsystems, but the function of controlling the execution order. Distributed to each task execution subsystem, the task execution subsystem generates second task data according to the current task execution result of the first task data and the second task generation policy, and is executed by another task execution subsystem according to the second Task data performs tasks to correlate tasks performed by multiple task execution subsystems to implement a specific media service, thereby avoiding the risk of single point of failure caused by a centralized control point to control the order of task execution . DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic structural diagram of a media service system according to an embodiment of the present invention;

2 is a schematic structural diagram of a transcoding service system according to an embodiment of the present invention;

3 is a schematic structural diagram of another media service system according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of another media service system according to an embodiment of the present invention; FIG. FIG. 6 is a schematic structural diagram of another media service system according to an embodiment of the present invention; FIG. 7 is a flowchart of a media service processing method according to an embodiment of the present invention;

FIG. 8 is a flowchart of another media service processing method according to an embodiment of the present invention. detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

The embodiment of the present invention provides a media service system, such as a transcoding service system or a media asset management system, and the schematic diagram is as shown in FIG. 1 , including: at least two task execution subsystems 100 (only two are shown in FIG. 1 ) The tasks performed by the plurality of task execution subsystems 100 are different, for example, one task execution subsystem 100 performs file uploading, another task execution subsystem 100 performs file segmentation, etc., and one task execution subsystem 100 can execute one or more tasks. .

For any of the task execution subsystems 100, the task management device 10, the task data storage device 11, and the at least one task execution device 12, wherein:

The task execution device 12 is configured to acquire the first task data from the task data storage device 11 according to the task processing policy stored in the task policy device 10, and execute the task according to the acquired first task data.

It can be understood that the task execution device 12 is a device that can perform certain tasks, such as a device that performs tasks such as file uploading, file sharding, or file transcoding. In a specific process of executing a task, the task executing device 12 can periodically actively submit tasks to the task. The data storage device 11 acquires the first task data, and then performs a certain task according to the first task data. The task processing policy refers to a policy for acquiring the first task data, which may be stored in the task policy device 10, and mainly specifies what tasks the task execution device 12 processes under what type of service, for example, the task processing policy indicates task execution. The device 12 may perform one or more or all tasks in one or more types of services, and may include a service type in the task processing policy, and further include a first task type in the service type, where The business type can be one type or multiple types. Here, the business and tasks are different. The business is composed of multiple tasks controlled by the solidified logic or workflow, and certain user requirements such as transcoding services or asset management services or rendering services can be realized, and the tasks are business processing. The function implementation in the process is the minimum unit for file execution. The above service type refers to the business attribute, and the task type refers to the function attribute of the task.

It can be understood that the task processing strategy can also specify under what circumstances the first task data is obtained, The first task data is acquired, for example, when the current load of the task execution device 12 does not exceed the preset threshold, otherwise the first task data is not acquired from the task data storage device 11. The task processing policy may further include other policies for acquiring the first task data, and the specific content may be preset by the user in the task policy device 10 according to actual needs. The first task data acquired by the task execution device 12 may include a service type, a first task type, and first task execution object information, where the first task execution object information refers to data information that is used when the task is executed, such as a source task object. That is, the task object that starts execution (such as the file after transcoding), or the task object that is the target task, that is, the task object that ends the execution.

It should be noted that each task execution subsystem 100 can deploy a plurality of task execution devices 12 (the plurality of task execution devices 12 are represented by interleaved overlapping boxes in FIG. 1), and each task execution device 12 They operate independently of each other without a coupling relationship, so that the plurality of task execution devices 12 can execute tasks concurrently, thereby shortening the completion time of the tasks, thereby improving the performance of the system; and when a certain task execution task device 12 fails due to a fault or overload When the task is executed, it can be executed by the other task execution device 12, thereby avoiding the risk of a single point of failure, thereby improving the reliability of the system.

The task policy device 10 is configured to store the foregoing task processing policy, and generate a policy and a task execution result of the task execution device 12 for the first task data according to the second task, and generate a service type, when the second task data needs to be generated. The second task executes the object information and the second task data of the second task type, and stores the generated second task data to the task data storage device 11 included in the other task execution subsystem 100 corresponding to the second task type. The task execution result of the first task data is output when the second task data is not required to be generated.

The task execution device 12 may send the task execution result to the task policy device 10 during the execution of the task, where the task execution result may include the first task data acquired by the task execution device 12, and the object after the task is executed (for example, transcoding) Subsequent files, etc.) and task execution status information (including states such as not yet started, executing, normal completion, or abnormal termination), etc. Further, if the task performed by the task execution device 12 is abnormally terminated, in addition to the task execution result In addition to the task execution status information, information such as the cause of the abnormal termination may also be included.

Here, the second task generation policy refers to a policy for generating the next task data of the task performed by the current task execution device 12, and may mainly include a policy of whether to generate the second task data, a policy of generating a type of task, etc., specifically In the second task generation policy, the service processing logic corresponding to the service type in the first task data is acquired by the task execution device 12, where the business processing logic Refers to the relationship between multiple tasks that implement a business.

Specifically, if the service processing logic includes at least two tasks included in the service corresponding to the service type, and an execution order relationship of the at least two tasks, the task execution device 12 performs a task execution result on the first task data. The method includes: an instruction to complete execution of the task of the first task type included in the first task data, and object data after execution, and the like. The second task execution object information in the second task data generated by the task policy device 10 may include the object data after execution in the task execution result, and the second task type is the type of the next task corresponding to the task in the first task type. .

For example: For the transcoding service, the business processing logic includes: file uploading - file fragmentation - file transcoding - file merging - file output, if the current task execution device 12 performs the task of file transcoding, and the task is completed normally, the task The second task type included in the second task data generated by the policy device 10 is file merge, and the service type is a transcoding service, and the second task execution object information is a transcoded file, and the second task data is It is stored in the task data storage device 11 of the task execution subsystem 100 that performs file merge.

If the current task execution device 12 performs the task of file output and is normally completed, the task policy device 10 determines that the second task data does not need to be generated.

It should be noted that, in addition to the service type, the second task execution object information, and the second task type, the second task data generated by the task policy device 10 may further include at least one of the following information: task identifier, task execution. Parameters and task control information, etc. The task execution parameter refers to specific requirements during the task execution process. For example, for the file transcoding task, the task execution parameter may include parameters such as a code rate, an encoding format, or a file encapsulation format; the task control information refers to the current task or The information required for subsequent task control, for example, for the task of file merging, the merging can be performed only after the transcoding task of all the partial files is completed, so all the file points in the task control information of the file merging task are required. The related information of the slice, such as the transcoding output identification information (such as a file name) list of the entire partial file, and the task execution device 12 may find the corresponding transcoded slice file according to the identification information list when performing file combination, and perform The file is merged, and the information about all the file fragments can be determined only when the file fragmentation task is executed. Therefore, the control information needs to be included when the subsequent task data is generated after the file fragmentation task is completed.

The task data storage device 11 is configured to store first task data, which may be generated and sent by the task policy device 10 of the previous task execution subsystem 100. The task data is stored The storage device 11 can provide management functions such as distributed access of the first task data, but does not provide a service control function, allowing the plurality of task execution devices 12 to concurrently acquire task data, specifically, based on an existing distributed file system or distribution. A technology such as a database is implemented, and a plurality of task data storage devices 11 can be deployed in each task execution subsystem 100 to avoid the risk of a single point of failure.

It should be noted that the first task data and the second task data, the first task execution object information and the second task execution object information, and the first task type and the second task type do not represent a sequential relationship, but represent Different task data, task execution object information, and task type.

It can be seen that the media service system of this embodiment includes multiple task execution subsystems 100, but there is no centralized control point to control the execution order between the task execution subsystems 100, but is distributed to each task execution subsystem. 100 includes a task policy device 10 for generating a next task data according to a task execution result of the task execution device 12 and a next task generation policy in the task execution subsystem 100, and storing the generated next task data to the next task Executing the task data storage device 11 of the subsystem 100, thereby associating the tasks performed by the plurality of task execution subsystems, realizing a specific media service, thereby avoiding controlling the task execution order through a centralized control point The risk of a single point of failure.

In addition, since each task execution subsystem always acquires task data through the task execution device actively polling when executing the task, so that there is no mutual dependency relationship between the plurality of task execution subsystems, thereby avoiding the single point control It brings the constraints of system performance expansion, which improves the performance of the system. For example: 1 media service request can be implemented by 5 tasks, that is, 5 tasks can be executed by 5 task execution subsystems 100, and 1 task execution device 12 in task execution subsystem 100 can achieve maximum processing performance. If it is 500 tasks/second, then the service processing performance of the system is 100 media service requests/second. If the deployment of the task execution device 12 is added to each task execution subsystem 100, the system performance can be improved to 200 media services. Request / sec.

Further, in a specific embodiment, the media service system may include at least one service request receiving device in addition to the plurality of task execution subsystems 100 as shown in FIG.

101. The method is configured to generate, according to the received service request, first task data including a service type, first task execution object information, and a first task type, and store the first task data to a task performer corresponding to the first task type. In the task data storage device 11 in the system 100, the task data storage device 11 is further configured to store the first task data generated by the service request receiving device 101. Which should A service request is a request for requesting the media service system to implement a certain service, such as a transcoding request for a file.

The service request receiving device 101 may generate the first task data according to the first task generation policy, where the first task generation policy includes service processing logic of the service type corresponding to the service request, for example, the service request is a transcoding service. The requesting, the generated first task type is a file uploading task, and the first task execution object information included in the generated first task data may include information such as a file to be uplinked. After the service request receiving device 101 receives the service request and generates the first task data, the first task data may be stored to the task execution subsystem corresponding to the first task type.

100 of the task data storage device 11 .

In a specific implementation, multiple service request receiving devices 101 may be deployed in the media service system.

(The plurality of service request receiving devices 101 are represented by interleaved blocks in Fig. 1), thereby avoiding the risk of a single point of failure and improving system performance.

It can be understood that the user interface, that is, the service request receiving device, can be included in the media service system.

101. Receive a service request triggered by a user, and generate first task data according to the service request. In this case, the service type corresponding to the service request, the first task execution object information, and the first task data. In addition to a task type, it may also include a service request identifier, a task identifier, a task execution parameter, and task control information. The following is a specific transcoding service system as an example. Referring to FIG. 2, the transcoding service system includes a transcoding service request receiving device 200, an upload task execution subsystem 201, a fragmentation task execution subsystem 202, and a transcoding task. An execution subsystem 203, a merge task execution subsystem 204, and an output task execution subsystem 205, wherein:

(1) The transcoding service request receiving device 200 receives the service request for transcoding, and generates the first task data according to the first task generation policy, that is, the service processing logic of the transcoding service, and sends the first task data to the uploading in the upload task execution subsystem 201. The task data storage device, wherein the first task data may include: a service type corresponding to the service request, that is, a transcoding, and the task type is a file uploading and task execution object information, that is, a file to be uploaded, and may also include information such as a service request identifier.

(2) The upload task execution subsystem 201 includes an upload task data storage device, an upload task execution device, and an upload task policy device, wherein the upload task execution device acquires a first task processing policy from the upload task policy device, and the first task processing Policy stipulates that the upload task execution device can handle If the service type is any type of service and the task type is a file uploading task, the uploading task executing device periodically and actively acquires the first task data from the uploading task data storage device according to the first task processing policy, and needs to be needed therein. The uploaded file is uploaded locally. During the process of acquiring the first task data, the upload task execution device may further determine whether the current load exceeds a threshold, and if not, remove the first task data from the upload task data storage device.

After the uploaded task execution device uploads the file, the upload task execution result is reported to the upload task policy device, which may include information such as whether to complete the upload or upload abnormal termination, and may also include the storage address of the uploaded file and the like.

The uploading task policy device generates a policy according to the second task (including the business processing logic of the transcoding service) and the uploading task execution result. If the uploading task execution result indicates that the uploading task is completed, the task type may be fragmented, and the service type is rotated. The code, and the task execution object is the second task data of the uploaded file, and the second task data is sent to the fragmentation task data storage device of the fragmentation task execution subsystem 202.

(3) The fragmentation task execution subsystem 202 includes a fragmentation task data storage device, a fragmentation task execution device, and a fragmentation task policy device, wherein the fragmentation task execution device acquires the second task processing from the fragmentation task policy device. a policy, the second task processing policy stipulates that the fragmentation task execution device can process the service type of the transcoding or rendering service, and the task type is a file fragmentation task, and the fragmentation task execution device periodically processes the policy according to the second task. The second task data is obtained from the fragmentation task data storage device, and the files that need to be sliced are fragmented. The shard task execution device may also determine whether the current load exceeds the threshold value during the process of acquiring the second task data, and if not, exceeds the second task data from the shard task data storage device.

The fragmentation task execution device reports the fragmentation task execution result to the fragmentation task policy device after the fragmentation of the file, and may include information such as whether the fragmentation or fragmentation is abnormally terminated, and may also include the identifier of the fragmented file. Or content and so on.

The fragmentation task policy device generates a policy and a fragmentation task execution result according to the third task. If the fragmentation task execution result indicates that the fragmentation task is completed, the generated task type and the service type are all transcoded, and the task execution object is a sub-division. The third task data of the transcoded file is required after the slice, and the third task data is sent to the transcoding task data storage device of the transcoding task execution subsystem 203. In the third task data, task control information including file fragmentation, such as a full partial slice file identifier list, all The fragment transcoding output file name list and the current fragment file identifier, etc., to facilitate the processing of subsequent tasks.

(4) The transcoding task execution subsystem 203 includes a transcoding task data storage device, a transcoding task execution device, and a transcoding task policy device, wherein the transcoding task execution device obtains a third task processing from the transcoding task policy device. a policy, the third task processing policy stipulates that the transcoding task execution device can process the task whose service type is a transcoding service and the task type is file transcoding, and the transcoding task execution device periodically actively takes the initiative according to the third task processing policy. The third task data is obtained in the transcoding task data storage device, and the fragmented file in which the transcoding needs to be transcoded is transcoded. The process of acquiring the third task data may further determine whether the current load exceeds a threshold value, and if not, the third task data is retrieved from the transcoding task data storage device.

It should be noted that, if the transcoding task execution device obtains a fragmented file from the transcoding task data storage device, the transcoding process can be started, and the transcoding process is not performed after all the fragmented files are obtained. In this way, the transcoding operations of multiple post-fragment files can be performed concurrently, which further improves the system processing performance.

After transcoding the file, the transcoding task execution device reports the execution result of the transcoding task to the transcoding task, and may also include the identifier or content of the file after transcoding.

The transcoding task policy device generates a policy and a transcoding task execution result according to the fourth task. If the transcoding task execution result indicates that all the fragments are transcoded, the generated task type is merged, and the task execution object is transcoded. The merged file is required, and the service type is the transcoded fourth task data, and the fourth task data is sent to the merge task data storage device of the merge task execution subsystem 204. In the fourth task data, task control information including file transcoding is also required, such as a list of all transcoded file identifiers, a list of all transcoded output file names, and a current transcoded file identifier, etc., to facilitate subsequent processing of the task.

(5) The merge task execution subsystem 204 includes a merge task data storage device, a merge task execution device, and a merge task policy device, wherein the merge task execution device obtains a fourth task processing policy from the merge task policy device, the fourth task The processing policy stipulates that the merge task execution device can process the task whose service type is transcoded or rendered and the task type is file merge, and the merge task execution device periodically and actively obtains from the merge task data storage device according to the fourth task processing policy. The fourth task data described above, and merges the transcoded files in which the merge is required. The merge task During the process of obtaining the fourth task data, the executing device may further determine whether the current load exceeds the threshold, and if not, remove the fourth task data from the merged task data storage device.

The merged task execution device reports the merged task execution result to the merged task policy device after the file is merged, and may include information such as whether to merge or merge the abnormally terminated transcoded files, and may also include the merged file. Logo or content, etc.

The merge task policy device generates a policy and merges the task execution result according to the fifth task. If the merge task execution result indicates that all the transcoded files are merged, the file may be generated including the task type as the output, and the task execution object is the file to be output after the merge. And the service type is the transcoded fifth task data, and the fifth task data is sent to the output task data storage device of the output task execution subsystem 205. In the fifth task data, it is also necessary to include the merged file, the destination address of the merged file, and the file identifier of the merged output.

(6) The output task execution subsystem 205 includes an output task data storage device, an output task execution device, and an output task policy device, wherein the output task execution device obtains a fifth task processing policy from the output task policy device, the fifth task The processing policy specifies that the output task execution device can process any service type and the task type is a file output task, and the output task execution device periodically and actively obtains the fifth task from the output task data storage device according to the fifth task processing policy. Data, and output the output file to the specified address. During the process of obtaining the fifth task data, the output task execution device may further determine whether the current load exceeds the threshold, and if not, remove the fifth task data from the output task data storage device.

After outputting the file, the output task execution device reports the output task execution result to the output task policy, including the identifier or content of the output file, and the like.

The output task policy device determines that the transcoding service request processing received by the transcoding service request receiving device 200 is completed according to the sixth task generating policy and the output task execution result, and determining that the sixth task data does not need to be generated. The embodiment of the present invention further provides another media service system, such as a transcoding service system or a media asset management system, and the schematic diagram is as shown in FIG. 3, including: at least two task execution subsystems 300 (only two are shown in FIG. 3) The tasks performed by the plurality of task execution subsystems 300 are different, for example, one task execution subsystem 300 performs file uploading, another task execution subsystem performs file segmentation, etc., and one Task execution subsystem 300 can perform one or more tasks.

For any one of the task execution subsystems 300, the task data storage device 30 and the at least one task processing device 31 may be included, wherein each task processing device 31 may include a task policy module 32 and a task execution module 33, specifically :

The task execution module 33 is configured to acquire the first task data from the task data storage device 30 according to the task processing policy stored in the task policy module 32, and execute the task according to the first task data; the task processing policy includes the first task data. Business type and first task type;

The task policy module 34 is configured to store a task processing policy, and generate a task execution result according to the second task according to the second task generation task and the task execution module 33, and generate a service type and a second when the second task data needs to be generated. The task execution object information and the second task data of the second task type, and storing the second task data in the task data storage device 30 of the other task execution subsystem 300 corresponding to the second task type; And the task execution result of the first task data is outputted by the second task generation policy, where the second task generation policy includes a service processing logic corresponding to the service type;

The task data storage device 30 is configured to store the first task data, where the first task data may be task data generated and sent by the task policy module 32 in the task processing device 31 of the previous task execution subsystem 300.

It should be noted that the media service system in this embodiment is similar to the system in the corresponding embodiment of FIG. 1. Specifically, the task policy module 32 in the system of this embodiment can implement the function of the task policy device 10 in the corresponding embodiment of FIG. The task execution module 33 can implement the functions of the task execution device 12 of the corresponding embodiment of FIG. 1, and details are not described herein. The difference is that the function of the next task data and the function of executing the task are generated in the system of this embodiment. Integration into one device, task processing device 31, can reduce deployment of devices in the media service system, and multiple task processing devices 31 can be deployed in task execution subsystem 300 (multiple task processing devices 31 in Figure 3 are interleaved) Overlapping boxes are used to avoid the risk of single point control and improve system performance.

Further, in a specific embodiment, the media service system may include at least one service request receiving device 301 for receiving services according to the plurality of task execution subsystems 300 as shown in FIG. Requesting, generating first task data including a service type, first task execution object information, and a first task type, and storing the first task data to a first task type pair In the task data storage device 30 in the task execution subsystem 300, the task data storage device 30 is further configured to store the first task data generated by the service request receiving device 301, wherein the function of the service request receiving device 301 is The functions of the task request receiving device 101 in the corresponding embodiment are similar, and are not described herein. In a specific implementation, multiple service request receiving devices 301 can be deployed in the media service system, thereby avoiding the risk of single point of failure. And can improve system performance. The embodiment of the present invention further provides another media service system, such as a transcoding service system or a media asset management system. The schematic diagram of the structure is as shown in FIG. 4, including: a data storage device 400 and at least two task execution subsystems 401 (FIG. 4 Only two of them are drawn, the tasks performed by the plurality of task execution subsystems 401 are different, and one task execution subsystem 401 can execute one or more tasks.

For any of the task execution subsystems 401, it may include: a task policy device

40 and at least one task execution device 41, wherein:

The task execution device 41 is configured to acquire the first task data from the data storage device 400 according to the task processing policy stored in the task policy device 40, and execute the task according to the first task data, where the task processing policy includes the first task data. Business type and first task type;

The task policy device 40 is configured to store a task processing policy, and generate a policy and a task execution result of the task execution device 41 for the first task data according to the second task, and generate a service type and a second when the second task data needs to be generated. The task execution object information and the second task data of the second task type, and storing the second task data in the data storage device 400; when the second task data is not required to be generated, outputting the task execution result of the first task data, The second task generation strategy includes business processing logic corresponding to the service type;

The data storage device 400 is configured to store the foregoing first task data, where the first task data may be task data generated and sent by the previous task execution subsystem 401. Specifically, the data storage device 400 may include multiple task data. The storage module is configured to separately store task data generated by the task policy device 40 in the plurality of task execution subsystems 401.

Further, in a specific embodiment, the media service system may include at least one service request receiving device 402, in addition to the data storage device 400 and the at least two task execution subsystems 401 as shown in FIG. The data storage device 400 may be further configured to store the first generated by the service request receiving device 402, according to the received service request, generating the first task data including the service type, the first task execution object information, and the first task type. Task data. The business request The function of the receiving device 402 is similar to that of the service request receiving device 101 in the corresponding embodiment of FIG. 1, and details are not described herein.

It should be noted that the media service system of this embodiment is similar to the media service system shown in FIG. 1 and is not described here. The difference is that the task policy device 40 in each task execution subsystem 401 is used in this embodiment. The generated next task data is placed in the same device, data storage device 400, so that these task data can be centrally managed. The embodiment of the present invention further provides another media service system, such as a transcoding service system or a media asset management system. The schematic diagram of the structure is as shown in FIG. 5, including: a data storage device 500 and at least one first task execution subsystem 501 (FIG. Draw two in 5) and at least one second task execution subsystem 502 (one in Figure 5), where:

The structure of the first task execution subsystem 501 is similar to that of the task execution subsystem 400 of FIG. 4, including the task policy device 50 and at least one task execution device 51, and the structure of the second task execution subsystem 502 is the same as that of FIG. The task execution subsystem 100 has a similar structure, including a task policy device 50, a task data storage device 52, and at least one task execution device 51, specifically:

The task execution device 51 is configured to acquire the first task data according to the task processing policy stored in the task policy device 50, and execute the task according to the first task data, where the task processing policy includes the service type of the first task data and the first task type. If it is the task execution device 51 in the first task execution subsystem 501, the first task data is acquired from the data storage device 500, and if it is the task execution device 51 in the second task execution subsystem 502, the slave task data The storage device 52 is used to acquire the first task data.

The task policy device 50 is configured to store the foregoing task processing policy, and generate a policy and a task execution result of the task execution device 51 for the first task data according to the second task, and generate a service type, when the second task data needs to be generated. The second task execution object information and the second task data of the second task type, if the second task data needs to be executed by the first task execution subsystem 501, storing the second task data into the data storage device 500, if The second task data needs to be executed by the second task execution subsystem 502, and the second task data is stored in the task data storage device 52 in another second task execution subsystem 502 corresponding to the second task type; When it is not necessary to generate the second task data, the task execution result of the first task data is output. The second task generation policy includes business processing logic corresponding to the service type. The task data storage device 52 is configured to store the first task data acquired by the task execution device 51 in the second task execution subsystem 502. The data storage device 500 is configured to store the task execution device 51 acquired by the task execution device 51 in the first task execution subsystem 501. The first task data, wherein the data storage device 500 can separately store the task data that the task execution device 51 needs to acquire in the different first task execution subsystem 501 through the plurality of task data storage modules. The first task data stored in the task data storage device 52 and the data storage device 500 may be task data generated by the task policy device 50 in the previous task execution subsystem (first or second task execution subsystem).

Further, in a specific embodiment, the media service system may include, in addition to the data storage device 500, the at least one first task execution subsystem 501, and the at least one second task execution subsystem 502 as shown in FIG. And the at least one service request receiving device 503 is further configured to generate the first task data including the service type, the second task execution object information, and the first task type according to the received service request, where the data storage device 500 or The task data storage device 52 is further configured to store the first task data generated by the service request receiving device 503.

It should be noted that, the first task execution subsystem and the second task execution subsystem, and the first task data and the second task data, and the first task type and the second task type are only for indicating different objects, and Indicates the order relationship.

It can be seen that, in this embodiment, the task data required by the task execution device 51 in the plurality of first task execution subsystems 501 to perform tasks is stored in the same device, that is, the data storage device 500, to facilitate unified management. The embodiment of the present invention further provides another media service system, such as a transcoding service system or a media asset management system. The structure diagram is as shown in FIG. 6, and includes: at least one first task execution subsystem 600 (drawn in FIG. 6) And at least one second task execution subsystem 601 (one drawn in Figure 6), wherein:

The structure of the first task execution subsystem 600, as shown in the structure of the task execution subsystem 300 in FIG. 3, includes a task data storage device 64 and at least one task processing device 61, wherein the task processing device 61, in turn, may include a task policy module. 62 and the task execution module 63; the structure of the second task execution subsystem 601, as shown in the structure of the task execution subsystem 100 in FIG. 1, includes a task policy device 65, a task data storage device 64, and at least one task execution device 51, specifically:

The functions of the task execution module 63 in the task processing device 61 are similar to those of the task execution device 66, Both are used to acquire the first task data from the task data storage device 64 according to the task processing policy and execute the task according to the first task data. The difference is that the task execution module 63 and the task execution module 63 in the task processing device 61 are different according to different tasks. The processing strategy is to obtain different first task data and perform different tasks according to the task processing policies stored in the task policy module 62 and the task policy device 65, respectively. The task processing policy may include a service type of the first task data and a first task type.

The function of the task policy module 62 in the task processing device 61 is similar to the function of the task policy device 65, and is used to store a task processing policy, and generate a policy according to the second task and a task execution result for the first task data. And when the second task data is generated, generating second task data including the service type and the second task type, and storing the second task data to the task data storage device 64 in the first task execution subsystem 600 corresponding to the second task type or The task data storage device 64 in the second task execution subsystem 601 is different in that the task policy module 62 and the task policy device 65 in the task processing device 61 use different second task generation strategies and different task execution results. Generate different second task data. The second task generation policy includes the service processing logic corresponding to the service type, and may also include other information, as described in the corresponding embodiment in FIG. 1, and details are not described herein.

The task data storage device 64 is configured to store first task data, where the first task data may be a previous task execution subsystem of the task execution subsystem where the task data storage device 64 is located (may be the first task execution subsystem 600) Or the task data generated and transmitted by the second task execution subsystem 601). The task data storage device 64 in the first task execution subsystem 600 is configured to store the first task data required by the task execution module 63 to execute the task, and to execute the child first task data for the second task.

Further, in a specific embodiment, the media service system may include at least one first task execution subsystem 600 and at least one second task execution subsystem 601 as shown in FIG. 6, and may further include at least A service request receiving device 602 is configured to generate first task data including a service type, first task execution object information, and a first task type according to the received service request, where the task data storage device 64 is further configured to store the service. The first task data generated by the device 602 is requested to be received.

It should be noted that the first task execution subsystem and the second task execution subsystem, and the first task data and the second task data, and the first task type and the second task type are only for indicating different The object, not the order relationship.

It can be seen that, in the media service system of the embodiment, the functions of executing the tasks and generating the next task data in the task execution subsystems of the certain task execution subsystems are integrated into the same device, that is, the task processing device 61, which can be reduced. The number of devices deployed in the system.

It should be noted that, in addition to the structures shown in FIG. 1 to FIG. 6 above, the media service system may have other function partitioning structures, as long as it can implement the periodic active acquisition of the first task data and perform tasks, and The second task generation strategy and the task execution result of the first task data generate second task data and store the function structure of the other storage device, and distribute the functional structure of the second task data to the media service system in different devices The structure will all fall within the scope of the embodiments of the present invention. The embodiment of the present invention further provides a media service processing method, which is mainly used in a media service system shown in FIG. 1 to FIG. 6 , a method performed by a task execution subsystem included in a media service system, and a flowchart, such as As shown in Figure 7, it includes:

Step 701: A task execution subsystem acquires a task processing policy, where the task processing policy may be preset in the task execution subsystem, and may specify what kind of tasks under the type of service performed by the task execution subsystem, specifically including the first The service type of the task data and the first task type, etc.; the task processing policy may also specify under what circumstances the first task data is acquired, specifically, when the load of the task execution subsystem does not exceed the preset threshold, Obtain the first task data, otherwise the first task data is not obtained.

Step 702: The task execution subsystem acquires the corresponding first task data according to the acquired task processing policy, and executes the task according to the first task data, where the acquired first task data includes data such as a service type and a first task type.

The first task data may be generated and sent by other task execution subsystems and stored in the task execution subsystem, or stored in another data storage device, and the task execution subsystem may periodically acquire the first task data. Specifically, the service type, the first task execution object information, and the executed first task type may be included, and the first task execution data may further include at least one of the following information: a task identifier, a task execution parameter, and a task. Control information and other information.

Step 703: The task execution subsystem generates a policy according to the second task and a task execution result of the first task data, and when the second task data needs to be generated, generates a service type and a second task execution. Object information and second task data of the second task type, so that another task execution subsystem corresponding to the second task type performs a task according to the second task data, and specifically performs a task according to the second task data and the above step 701 The method described in 703 is similar; it can be understood that, when the second task data is not required to be generated, the task execution result of the first task data is output, wherein the second task generation policy includes service processing logic corresponding to the service type.

The task execution result of the task execution subsystem for the first task data may include: first task data, object after task execution, and task execution state information, etc., if the task execution is abnormal, may also include information such as the cause of the task abnormality, Further, the task execution information may further include task control information, for example, after the file is fragmented, the task execution result may include an identifier list of the file after the fragment as the control information of the subsequent task (such as transcoding); The second task generation policy refers to a policy for generating the next task data of the current task, and may mainly include a strategy for generating the second task data, and a strategy for generating the type of task. If the task execution subsystem determines that the second task data needs to be generated according to the task execution result and the second task generation policy, the second task data is generated according to the business processing logic in the second task generation policy. The generated second task data may include at least one of the following information in addition to the service type, the second task execution object information, and the second task type: task identifier, task execution parameters, and task control information. .

Specifically, if the business processing logic includes at least two tasks, and an execution order relationship of the at least two tasks, the task execution result of the task execution subsystem for the first task data specifically includes the first included in the first task data. The task of the task type performs the instruction of the completion and the object data after the execution; the task execution subsystem, when the step 703 is executed, the second task execution object information in the generated second task data includes the object data after the execution, The second task type is a type of the next task corresponding to the first task type.

The task execution subsystem may store the generated second task data into another task execution subsystem corresponding to the second task type, or store it in a data storage device included in the media service system, such that another task performer The system periodically acquires the second task data to perform the task.

It can be seen that the media service system in this embodiment can be executed by multiple task execution subsystems, but there is no centralized control point to control the execution order between the task execution subsystems, but the function of controlling the execution order. Scattered into each task execution subsystem, by the task execution subsystem root Generating the second task data according to the current task execution result of the first task data and the second task generation strategy, and executing the task according to the second task data by another task execution subsystem, thereby executing the plurality of task execution subsystems The tasks performed are linked together to implement a specific media service, which avoids the risk of a single point of failure caused by a centralized control point to control the order of task execution.

In addition, since each task execution subsystem always actively polls and acquires task data when executing tasks, there is no mutual dependency between multiple task execution subsystems, thereby avoiding system performance expansion caused by single point control. Restrictions, thereby improving the performance of the media business system.

Referring to FIG. 8, in a specific embodiment, the task execution subsystem further needs to perform step 704 before performing the foregoing step 701, that is, the service request receiving device in the media service system can also receive the service request, and according to the service. The request generates the first task data including the first task type, the first task execution object information, and the service type, where the service request is used to request the media service system to complete a certain service, and specifically includes a service type such as transcoding or rendering. And the service request receiving device, when the first task data is generated, may be generated according to the first task generation policy, where the first task generation policy may include a service processing logic corresponding to the service type of the service request, that is, a service is implemented. Relationship between multiple tasks, etc. After the service request receiving device receives the service request and generates the first task data, the first task data may be stored in the task execution subsystem corresponding to the first task type, or stored in the data storage device in the media service system. Medium, thereby triggering the steps of steps 701 to 703 above.

A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: ROM, RAM, disk or CD, etc.

The above description of the media service system and the media service processing method provided by the embodiments of the present invention is only for helping to understand the method and core idea of the present invention. Meanwhile, for those skilled in the art, according to the present invention, The present invention is not limited by the scope of the present invention.

Claims

Rights request

1. A media business system, characterized in that it includes at least two task execution subsystems. The task execution subsystem includes: a task strategy device, a task data storage device and at least one task execution device, wherein: from the task The data storage device obtains the first task data and performs the task according to the first task data; the task processing policy includes the business type of the first task data and the first task type;

The task strategy device is used to store the task processing strategy, and according to the second task generation strategy and the task execution result of the task execution device on the first task data, when it is necessary to generate the second task data, generate including business type, second task execution object information and second task data of the second task type, and storing the second task data in a task data storage device of another task execution subsystem corresponding to the second task type , the second task generation strategy includes business processing logic corresponding to the business type;

The task data storage device is used to receive the first task data sent by the task strategy device in the previous task execution subsystem, and store the first task data.

2. The system according to claim 1, characterized in that the system further includes: at least one service request receiving device, configured to generate a service request including service type, first task execution object information and first task execution object information according to the received service request. The first task data of the task type;

The task data storage device is also used to store the first task data generated by the service request receiving device.

3. The system according to claim 1 or 2, wherein the task execution policy obtained by the task execution device further includes: when the load of the task execution device does not exceed a preset threshold, obtain the first mission data;

The second task data generated by the task policy device or the first task data generated by the service request receiving device also includes at least one of the following information: task identification, task execution parameters, and task control information.

4. The system according to any one of claims 1 to 3, characterized in that,

The task strategy device is also configured to output the second task data when there is no need to generate the second task data according to the second task generation strategy and the task execution result of the task execution device on the first task data. The task execution result of the first task data.

5. The system according to any one of claims 1 to 4, characterized in that,

The business processing logic includes at least two tasks and the execution sequence relationship of the at least two tasks;

The task execution result of the task execution device on the first task data specifically includes: an indication of completion of task execution of the first task type included in the first task data and the object data after execution; then the task strategy device The second task execution object information in the generated second task data includes the executed object data, and the second task type is the type of the next task corresponding to the first task type.

6. A media business system, characterized by: including at least two task execution subsystems, the task execution subsystem including: a task data storage device and at least one task processing device, the task processing device including a task strategy module and task execution module, where:

The task execution module is configured to obtain the first task data from the task data storage device according to the task processing strategy stored in the task strategy module, and execute the task according to the first task data; the task processing The strategy includes the business type of the first task data and the first task type; the task strategy module is used to store the task processing strategy, and process the first task data according to the second task generation strategy and the task execution module The task execution result, when it is necessary to generate the second task data, generate the second task data including the business type, the second task execution object information and the second task type, and store the second task data in the same file as the second task data. In the task data storage device of another task execution subsystem corresponding to the type, the second task generation strategy includes business processing logic corresponding to the business type;

The task data storage device is used to receive the first task data sent by the task processing device in the previous task execution subsystem, and store the first task data.

7. The system according to claim 6, characterized in that the system further includes: at least one service request receiving device, configured to generate a service request including service type, first task execution object information and first task execution object information according to the received service request. The first task data of the task type;

8. The system according to claim 6 or 7, wherein the task strategy module further Used to output the task execution result of the first task data according to the second task generation strategy and the task execution result of the first task data by the task execution module when there is no need to generate the second task data.

9. A media business system, characterized in that it includes: a data storage device, and at least two task execution subsystems. The task execution subsystem includes: a task strategy device and at least one task execution device, wherein: from all Obtain the first task data from the data storage device, and execute the task according to the first task data; The task processing strategy includes the business type of the first task data and the first task type;

The task strategy device is used to store the task processing strategy, and according to the second task generation strategy and the task execution result of the task execution device on the first task data, when it is necessary to generate the second task data, generate including business type, second task execution object information and second task data of the second task type, and storing the second task data in the data storage device; the second task generation strategy includes: The business processing logic corresponding to the type;

The data storage device is used to receive the first task data sent by the task strategy device in the previous task execution subsystem, and store the first task data.

10. The system according to claim 9, characterized in that the system further includes: at least one service request receiving device, configured to generate, according to the received service request, the service type, the second task execution object information and the first The first task data of the task type;

The data storage device is also used to store the first task data generated by the service request receiving device.

11. The system according to claim 9 or 10, wherein the task strategy device is further configured to generate a task execution result of the first task data according to a second task generation strategy and the task execution device, When there is no need to generate the second task data, the task execution result of the first task data is output.

12. A media business system, characterized in that it includes a data storage device, and at least one first task execution subsystem and at least one second task execution subsystem;

The first task execution subsystem includes: a task strategy device and at least one task execution device; the second task execution subsystem includes: a task strategy device, a task data storage device and at least one task execution device. A task execution device; obtains first task data and performs tasks according to the first task data; the task processing strategy includes the business type of the first task data and the first task type;

The task strategy device is used to store the task processing strategy, and according to the second task generation strategy and the task execution result of the task execution device on the first task data, when it is necessary to generate the second task data, generate The second task data includes the business type, the second task execution object information and the second task type, and stores the second task data in the data storage device or in the third task data corresponding to the second task type. In the task data storage device in the second task execution subsystem, the second task generation strategy includes business processing logic corresponding to the business type;

The task data storage device is used to store the first task data obtained by the task execution device in the second task execution subsystem;

The data storage device is used to store the first task data obtained by the task execution device in the first task execution subsystem.

13. The system according to claim 12, characterized in that the system further includes: at least one service request receiving device, configured to generate a service request including service type, first task execution object information and first task execution object information according to the received service request. The first task data of the task type;

The task data storage device or the data storage device is also used to store the first task data generated by the service request receiving device.

14. The system according to claim 12 or 13, wherein the task strategy device is further configured to generate a task execution result of the first task data according to a second task generation strategy and the task execution device, When there is no need to generate the second task data, the task execution result of the first task data is output.

15. A media business system, characterized by including: at least one first task execution subsystem and at least one second task execution subsystem, wherein:

The first task execution subsystem includes a task data storage device and at least one task processing device. The task processing device includes a task strategy module and a task execution module; the second task execution subsystem includes a task strategy device, a task data storage device, and a task execution module. equipment and at least one task execution device; the task execution module and task execution device are used to obtain the first task according to the task processing policy data and perform tasks according to the first task data; the task processing strategy includes the business type of the first task data and the first task type;

The task strategy module and task strategy device are used to store the task processing strategy, and according to the second task generation strategy and the task execution result of the first task data, when it is necessary to generate the second task data, generate the following: business type, second task execution object information and second task data of the second task type, and store the second task data in the task data storage in the second task execution subsystem corresponding to the second task type device, or a task data storage device in the first task execution subsystem, the second task generation strategy includes business processing logic corresponding to the business type; the task data storage device is used to receive the previous task execution subsystem The system sends the first task data and stores the first task data.

16. The system according to claim 15, characterized in that the system further includes: at least one service request receiving device, configured to generate a service request including service type, first task execution object information and first task execution object information according to the received service request. The first task data of the task type;

17. The system according to claim 15 or 16, wherein the task strategy device is further configured to generate a task execution result of the first task data according to a second task generation strategy and the task execution device, When there is no need to generate the second task data, the task execution result of the first task data is output.

18. A media business processing method, characterized in that it is used for business processing of the task execution subsystem included in the media business system, including:

The task execution subsystem obtains a task processing strategy, and the task processing strategy includes the business type of the first task data and the first task type;

The task execution subsystem obtains the corresponding first task data according to the task processing policy and executes the task according to the first task data;

The task execution subsystem generates, according to the second task generation strategy and the task execution result of the first task data, the business type, the second task execution object information and the second task type when it is necessary to generate the second task data. second task data, so that another task execution subsystem corresponding to the second task type performs a task according to the second task data, and the second task generates a policy package Include business processing logic corresponding to the business type.

19. The method of claim 18, wherein the task execution subsystem acquires the task processing strategy, which also includes:

The task request receiving device in the media service system receives the task request and generates first task data including a first task type and a service type according to the task request.

20. The method of claim 18 or 19, wherein the task execution strategy further includes: when the load of the task execution subsystem does not exceed a preset threshold, obtaining task data; the generating The second task data also includes at least one of the following information: task identification, task execution parameters and task control information.

21. The method according to any one of claims 18 to 20, further comprising: the task execution subsystem performs tasks on the first task data according to the second task generation strategy and the task execution device. Execution result: When there is no need to generate second task data, the task execution result of the first task data is output.

22. The method according to any one of claims 18 to 21, characterized in that: the business processing logic includes at least two tasks, and the execution sequence relationship of the at least two tasks; the task execution subsystem The task execution result of the first task data specifically includes: an indication of completion of task execution of the first task type included in the first task data and the object data after execution;

Then the second task execution object information in the second task data generated by the task execution subsystem includes the object data after execution, and the second task type is the type of the next task corresponding to the first task type.