Digital work generation method and device, task release method and device, equipment and medium

Abstract

The invention discloses a digital work generation method and device, a task release method and device, equipment and a medium, which are used for realizing collaborative creation of a digital work added with a next-level subtask as required. The digital work generation method comprises the following steps: acquiring a first collaborative creation task comprising sub-tasks, wherein the sub-tasks comprise a first variable-length frame type sub-task and an amorphous first next-level sub-task; the first variable-length frame type sub-task has a second next-layer sub-task queue, and the second next-layer sub-tasks are sorted according to the receiving sequence; acquiring an instruction of a first creator for selecting a first target sub-task in the sub-tasks; the first target sub-task is an amorphous first next-layer sub-task; providing the first target subtask for the first creator according to the instruction; receiving first creation information of the first creator on the first target subtask; and determining the digital work content corresponding to the first creation information based on the first creation information and the sequence of the second next-layer subtask corresponding to the first creation information in the queue.

Description

Technical Field

[0001] The present application relates to the field of digital information technology, and in particular to methods, devices, equipment, and media for generating and publishing digital works and tasks. Background Art

[0002] To ensure collaborative creation of digital works is carried out in the correct order and based on complete basic information, the collaborative creation method breaks down collaborative creation tasks into multiple subtasks with dependencies, including subtask descriptions and creation status, for creators to work on. Creators participating in the collaborative creation input creative information, which is then used to generate the digital work, thus achieving collaborative creation of digital works. Summary of the Invention

[0003] The embodiments of the present application provide a method, apparatus, device and medium for generating digital works and issuing tasks, so as to realize the collaborative creation of digital works by adding next-level subtasks as needed.

[0004] In a first aspect, an embodiment of the present application provides a method for generating a digital work, comprising:

[0005] Obtaining a first collaborative creation task, the first collaborative creation task including one or more subtasks, the one or more subtasks including at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask having an indefinite-form first-lower-level subtask, the indefinite-form first-lower-level subtask being used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask having a second-lower-level subtask queue, the second-lower-level subtask queue sorting the second-lower-level subtasks in a received order;

[0006] Obtaining an instruction for a first target subtask selected by a first creator from among the one or more subtasks; the first target subtask is the indefinite first lower-level subtask;

[0007] According to the instruction, the first target subtask is provided to the first creator for execution of creation by the first creator;

[0008] receiving first creation information of the first target subtask from the first creator;

[0009] Based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask, the digital work content corresponding to the first creation information is determined.

[0010] The embodiment of the present application obtains a first collaborative creation task including one or more subtasks through the above method, wherein the one or more subtasks include at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask has an indefinite-form first-lower-level subtask, and the indefinite-form first-lower-level subtask is used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask has a second-lower-level subtask queue, and the second-lower-level subtask queue sorts the second-lower-level subtasks in the order of receipt; thereby, when obtaining the pointer to the first target subtask selected by the first creator in the one or more subtasks, After the instruction, wherein the first target subtask is the indefinite first-lower-level subtask, the first target subtask can be provided to the first creator according to the instruction, so that the first creator can perform the creation; further, after receiving the first creation information of the first target subtask from the first creator, the content of the digital work corresponding to the first creation information can be finally determined based on the first creation information and the sorting of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask, thereby realizing the collaborative creation of digital works with the next-level subtask added on demand.

[0011] In some embodiments, determining the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first variable-length frame-type subtask includes:

[0012] Submitting the first creation information;

[0013] Generate a second-level subtask corresponding to the first creative information according to the first target subtask, wherein the second-level subtask corresponding to the first creative information has the first creative information; and has a first variable-length frame-type subtask of the first target subtask and a second-level subtask corresponding to the first creative information;

[0014] Obtaining the order of the second-lower-layer subtask corresponding to the first creation information in the second-lower-layer subtask queue owned by the first variable-length frame-type subtask;

[0015] According to the sorting, the digital work content corresponding to the first creation information is determined.

[0016] In a second aspect, another method for generating a digital work provided by an embodiment of the present application includes:

[0017] Acquire a second collaborative creation task, the second collaborative creation task including one or more subtasks, the one or more subtasks including at least one second indefinite-length frame-type subtask and at least one indefinite-form third-lower-level subtask, the second indefinite-length frame-type subtask having second execution content, the second execution content having an indefinite-form third-lower-level subtask, the indefinite-form third-lower-level subtask being used to generate one or more fourth-lower-level subtasks; the second execution content of the second indefinite-length frame-type subtask having a fourth-lower-level subtask queue, the fourth-lower-level subtask queue sorting the fourth-lower-level subtasks in a received order;

[0018] Obtaining an instruction for a second target subtask selected by a second creator from among the one or more subtasks; the second target subtask is the indefinite third lower-level subtask;

[0019] According to the instruction, the second target subtask is provided to the creator for the second creator to perform creation;

[0020] receiving second creation information of the second target subtask from the second creator;

[0021] Based on the second creation information and the order of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue owned by the second execution content owned by the second indefinite-length frame-type subtask, the digital work content corresponding to the second creation information is determined.

[0022] The embodiment of the present application obtains a second collaborative creation task including one or more subtasks through the above method, wherein the one or more subtasks include at least one second indefinite-length frame-type subtask and at least one indefinite third-lower-level subtask, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-lower-level subtask, and the indefinite third-lower-level subtask is used to generate one or more fourth-lower-level subtasks; the second execution content owned by the second indefinite-length frame-type subtask has a fourth-lower-level subtask queue, and the fourth-lower-level subtask queue sorts the fourth-lower-level subtasks in the order of receipt; thereby, when obtaining the second collaborative creation task selected by the second creator in the one or more subtasks, After receiving the instruction of the target subtask, wherein the second target subtask is the indefinite third-lower-level subtask, the second target subtask can be provided to the creator according to the instruction, so that the second creator can perform the creation; further, after receiving the second creation information of the second target subtask from the second creator, the digital work content corresponding to the second creation information can be finally determined based on the second creation information and the sorting of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue of the second execution content owned by the second indefinite-length frame-type subtask, thereby realizing the collaborative creation of digital works with the next-level subtask added on demand.

[0023] In some embodiments, based on the second creative information and the ranking of the fourth lower-level subtask corresponding to the second creative information in the fourth lower-level subtask queue owned by the second execution content owned by the second variable-length frame-type subtask, determining the digital work content corresponding to the second creative information includes:

[0024] Submitting the second creation information;

[0025] A fourth lower-level subtask corresponding to the second creative information is generated according to the second target subtask, and the fourth lower-level subtask corresponding to the second creative information has the second creative information; has the second execution content owned by the second indefinite-length frame-type subtask of the second target subtask, and has the fourth lower-level subtask corresponding to the second creative information;

[0026] Obtaining the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content;

[0027] Based on the sorting, the digital work content corresponding to the second creation information is determined.

[0028] In a third aspect, an embodiment of the present application provides a task publishing method, including:

[0029] Obtaining task setting information input by the task publisher, wherein the task setting information corresponds to a task template;

[0030] Generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[0031] The one or more subtasks include: at least one indefinite-length frame-type subtask and at least one indefinite-type next-level subtask.

[0032] The embodiment of the present application can obtain the task setting information input by the task publisher through the above-mentioned task publishing method, wherein the task setting information corresponds to the task template; thereby, based on the task setting information and the task template, a target collaborative creation task including one or more subtasks can be generated and published, wherein the one or more subtasks include: at least one indefinite-length framework-type subtask and at least one indefinite next-level subtask, thereby correspondingly enabling the subsequent use of the method provided in the first aspect to realize the generation of digital works, providing a basis for realizing the collaborative creation of digital works by adding next-level subtasks on demand.

[0033] In some embodiments, the target collaborative creation task is a first collaborative creation task; the indefinite-length frame-type subtask is a first indefinite-length frame-type subtask; the indefinite next-level subtask is an indefinite first-next-level subtask, the first indefinite-length frame-type subtask has an indefinite first-next-level subtask, and the indefinite first-next-level subtask is used to generate one or more second-next-level subtasks; the first indefinite-length frame-type subtask has a second-next-level subtask queue, and the second-next-level subtask queue sorts the second-next-level subtasks in the order of receipt.

[0034] In a fourth aspect, another task publishing method provided by an embodiment of the present application includes:

[0035] Obtaining task setting information input by the task publisher, wherein the task setting information corresponds to a task template;

[0036] Generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[0037] The one or more subtasks include: at least one indefinite-length frame-type subtask.

[0038] The embodiment of the present application can obtain the task setting information input by the task publisher through the above-mentioned task publishing method, wherein the task setting information corresponds to the task template; thereby, a target collaborative creation task including one or more subtasks can be further generated and published based on the task setting information and the task template, wherein the one or more subtasks include: at least one indefinite-length framework-type subtask, thereby correspondingly enabling the subsequent use of the method provided in the second aspect to realize the generation of digital works, providing a basis for realizing the collaborative creation of digital works by adding the next-level subtasks as needed.

[0039] In some embodiments, the target collaborative creation task is the second collaborative creation task; the variable-length frame-type subtask is the second variable-length frame-type subtask;

[0040] When the creator creates second execution content for the second indefinite-length frame-type subtask by publishing the second collaborative creation task, the one or more subtasks further include: at least one indefinite-length third lower-level subtask;

[0041] Among them, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-level subtask, and the indefinite third-level subtask is used to generate one or more fourth-level subtasks; the second indefinite-length frame-type subtask has a second execution content with a fourth-level subtask queue, and the fourth-level subtask queue sorts the fourth-level subtasks in the order of receipt.

[0042] In a fifth aspect, an embodiment of the present application provides a digital work generation device, comprising:

[0043] A first task acquisition unit is configured to acquire a first collaborative creation task, the first collaborative creation task including one or more subtasks, the one or more subtasks including at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask having an indefinite-form first-lower-level subtask, the indefinite-form first-lower-level subtask being used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask having a second-lower-level subtask queue, the second-lower-level subtask queue sorting the second-lower-level subtasks in a received order;

[0044] A first instruction acquisition unit is configured to acquire an instruction for a first target subtask selected by a first creator from among the one or more subtasks; the first target subtask is the indefinite first lower-level subtask;

[0045] A first task providing unit is configured to provide the first target subtask to the first creator according to the instruction, so that the first creator performs creation;

[0046] A first creation information receiving unit, configured to receive first creation information of the first target subtask from the first creator;

[0047] The first work determination unit is used to determine the digital work content corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask.

[0048] In some embodiments, determining the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first variable-length frame-type subtask includes:

[0049] Submitting the first creation information;

[0050] Generate a second-level subtask corresponding to the first creative information according to the first target subtask, wherein the second-level subtask corresponding to the first creative information has the first creative information; and has a first variable-length frame-type subtask of the first target subtask and a second-level subtask corresponding to the first creative information;

[0051] Obtaining the order of the second-lower-layer subtask corresponding to the first creation information in the second-lower-layer subtask queue owned by the first variable-length frame-type subtask;

[0052] According to the sorting, the digital work content corresponding to the first creation information is determined.

[0053] In a sixth aspect, another digital work generation device provided by an embodiment of the present application includes:

[0054] A second task acquisition unit is configured to acquire a second collaborative creation task, the second collaborative creation task including one or more subtasks, the one or more subtasks including at least one second indefinite-length frame-type subtask and at least one indefinite-third-lower-level subtask, the second indefinite-length frame-type subtask having a second execution content, the second execution content having an indefinite-third-lower-level subtask, the indefinite-third-lower-level subtask being used to generate one or more fourth-lower-level subtasks; the second execution content of the second indefinite-length frame-type subtask having a fourth-lower-level subtask queue, the fourth-lower-level subtask queue sorting the fourth-lower-level subtasks in a received order;

[0055] A second instruction acquisition unit is configured to acquire an instruction for a second target subtask selected by a second creator from among the one or more subtasks; the second target subtask is the indefinite third lower-level subtask;

[0056] A second task providing unit is configured to provide the second target subtask to the creator according to the instruction, so that the second creator performs creation;

[0057] A second creation information receiving unit, configured to receive second creation information of the second target subtask from the second creator;

[0058] The second work determination unit is used to determine the digital work content corresponding to the second creation information based on the second creation information and the order of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue owned by the second execution content owned by the second indefinite-length frame-type subtask.

[0059] In some embodiments, based on the second creative information and the ranking of the fourth lower-level subtask corresponding to the second creative information in the fourth lower-level subtask queue owned by the second execution content owned by the second variable-length frame-type subtask, determining the digital work content corresponding to the second creative information includes:

[0060] Submitting the second creation information;

[0061] A fourth lower-level subtask corresponding to the second creative information is generated according to the second target subtask, and the fourth lower-level subtask corresponding to the second creative information has the second creative information; has the second execution content owned by the second indefinite-length frame-type subtask of the second target subtask, and has the fourth lower-level subtask corresponding to the second creative information;

[0062] Obtaining the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content;

[0063] Based on the sorting, the digital work content corresponding to the second creation information is determined.

[0064] In a seventh aspect, an embodiment of the present application provides a task issuing device, comprising:

[0065] A first task setting information acquisition unit is used to acquire task setting information input by a task publisher, wherein the task setting information corresponds to a task template;

[0066] A first publishing unit is configured to generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[0067] The one or more subtasks include: at least one indefinite-length frame-type subtask and at least one indefinite-type next-level subtask.

[0068] In some embodiments, the target collaborative creation task is a first collaborative creation task; the indefinite-length frame-type subtask is a first indefinite-length frame-type subtask; the indefinite next-level subtask is an indefinite first-next-level subtask, the first indefinite-length frame-type subtask has an indefinite first-next-level subtask, and the indefinite first-next-level subtask is used to generate one or more second-next-level subtasks; the first indefinite-length frame-type subtask has a second-next-level subtask queue, and the second-next-level subtask queue sorts the second-next-level subtasks in the order of receipt.

[0069] In an eighth aspect, another task issuing device provided by an embodiment of the present application includes:

[0070] A second task setting information acquisition unit is used to acquire task setting information input by the task publisher, wherein the task setting information corresponds to the task template;

[0071] A second publishing unit is configured to generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[0072] The one or more subtasks include: at least one indefinite-length frame-type subtask.

[0073] In some embodiments, the target collaborative creation task is the second collaborative creation task; the variable-length frame-type subtask is the second variable-length frame-type subtask;

[0074] When the creator creates second execution content for the second indefinite-length frame-type subtask by publishing the second collaborative creation task, the one or more subtasks further include: at least one indefinite-length third lower-level subtask;

[0075] Among them, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-level subtask, and the indefinite third-level subtask is used to generate one or more fourth-level subtasks; the second indefinite-length frame-type subtask has a second execution content with a fourth-level subtask queue, and the fourth-level subtask queue sorts the fourth-level subtasks in the order of receipt.

[0076] In the ninth aspect, another embodiment of the present application provides an electronic device, which includes a memory and a processor, wherein the memory is used to store program instructions, and the processor is used to call the program instructions stored in the memory and execute any of the above methods according to the obtained program.

[0077] In the tenth aspect, another embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute any of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0079] Figure 1A A flowchart of a method for generating a digital work provided in an embodiment of the present application;

[0080] Figure 1B A flowchart of another method for generating digital works provided in an embodiment of the present application;

[0081] Figure 2 A schematic diagram of digital work content corresponding to an indefinite-length framework-type subtask including two lower-level subtasks provided in an embodiment of the present application;

[0082] Figure 3A A flowchart of a task publishing method provided in an embodiment of the present application;

[0083] Figure 3B A flowchart of another task publishing method provided in an embodiment of the present application;

[0084] Figure 4 A schematic diagram of a task state diagram including a first variable-length frame-type subtask provided in an embodiment of the present application;

[0085] Figure 5 A schematic diagram of a task state diagram including a second variable-length frame-type subtask provided in an embodiment of the present application;

[0086] Figure 6 A schematic diagram of an overview of the initial task state diagram provided in Example 1 of the present application;

[0087] Figures 7 to 9 A schematic diagram of the next level of subtasks that are expanded after a user clicks on a framework-type subtask in the overview version of the initial task state diagram provided in Example 1 of the present application;

[0088] Figure 10 This is a schematic diagram of an example of reference creation information [T5.n, refer] of the execution content prepared by the template developer M for the second-level subtask T5.n "risk warning n" provided in the first embodiment of the present application;

[0089] Figure 11 A schematic diagram of a task status diagram provided in Example 1 of the present application;

[0090] Figure 12 、 Figure 13 A schematic diagram of a first process task state diagram provided in Example 1 of the present application;

[0091] Figure 14 A schematic diagram of a content block object provided in Example 1 of the present application;

[0092] Figure 15 This is a schematic diagram of the subtask creation information input by the user in the creation content block object of subtask T1.1 "Basic Situation and Historical Evolution" provided in Example 1 of the present application;

[0093] Figure 16 A schematic diagram of the second process task state diagram of the collaborative creation task of the "Enterprise Research Report" provided in Example 1 of this application;

[0094] Figure 17 Provided in Example 1 of this application Figure 16 A schematic diagram of an information snapshot corresponding to the second process task state diagram shown;

[0095] Figure 18 This is a schematic diagram of the task status diagram when the "T5 Risk Prompt" provided in Example 1 of this application enters the creation state;

[0096] Figure 19 This is a schematic diagram of the system provided in Example 1 of the present application pushing a creative content block object of subtask T5.n to a user;

[0097] Figure 20 This is a schematic diagram of subtask creation information input by a user in the creation content block object of subtask T5.n "Risk Warning n" provided in Example 1 of the present application;

[0098] Figure 21 A schematic diagram of another second process task state diagram of the collaborative creation task of the "Enterprise Research Report" provided in Example 1 of the present application;

[0099] Figure 22 Provided in Example 1 of this application Figure 21 A schematic diagram of an information snapshot corresponding to the second process task state diagram shown;

[0100] Figure 23 Provided in Example 1 of this application Figure 21 A schematic diagram of a digital work corresponding to the second process task state diagram shown;

[0101] Figure 24Provided in Example 1 of this application Figure 21 A schematic diagram of part of the content of the composite digital work corresponding to the second process task state diagram shown;

[0102] Figure 25 A schematic diagram of another second process task state diagram of the collaborative creation task of the "Enterprise Research Report" provided in Example 1 of the present application;

[0103] Figure 26 Provided in Example 1 of this application Figure 25 A schematic diagram of an information snapshot corresponding to the second process task state diagram shown;

[0104] Figure 27 Provided in Example 1 of this application Figure 25 A schematic diagram of a digital work corresponding to the second process task state diagram shown;

[0105] Figure 28 Provided in Example 1 of this application Figure 25 A schematic diagram of part of the content of the composite digital work corresponding to the second process task state diagram shown;

[0106] Figure 29 This is a schematic diagram of the system provided in Example 2 of the present application pushing a creative content block object of subtask T5 to a user;

[0107] Figure 30 This is a schematic diagram of a user inputting subtask creation information into a creation content block object of a framework-type subtask "T5 Risk Reminder" provided in Example 2 of the present application;

[0108] Figure 31 A schematic diagram of the second process task state diagram of the collaborative creation task of "Enterprise Research Report" provided in Example 2 of this application;

[0109] Figure 32 Provided for Example 2 of this application Figure 31 A schematic diagram of an information snapshot corresponding to the second process task state diagram is shown;

[0110] Figure 33 Provided for Example 2 of this application Figure 31 A schematic diagram of a digital work corresponding to the second process task state diagram shown;

[0111] Figure 34 Provided for Example 2 of this application Figure 31 A schematic diagram of a composite digital work corresponding to the second process task state diagram shown;

[0112] Figure 35 Schematic diagram of the system provided in Example 2 of the present application pushing the creation content block object of subtask T5.d(1).n to the user;

[0113] Figure 36 A schematic diagram of a user inputting subtask creation information into a creation content block object of subtask T5.d(1).n “Risk Warning n” provided in Example 2 of the present application;

[0114] Figure 37 A schematic diagram of another second process task state diagram of the collaborative creation task of "Enterprise Research Report" provided in Example 2 of this application;

[0115] Figure 38 Provided for Example 2 of this application Figure 37 A schematic diagram of an information snapshot corresponding to the second process task state diagram is shown;

[0116] Figure 39 Provided for Example 2 of this application Figure 37 A schematic diagram of a digital work corresponding to the second process task state diagram shown;

[0117] Figure 40 A schematic diagram of another second process task state diagram of the collaborative creation task of "Enterprise Research Report" provided in Example 2 of this application;

[0118] Figure 41 Provided for Example 2 of this application Figure 40 A schematic diagram of an information snapshot corresponding to the second process task state diagram is shown;

[0119] Figure 42 Provided for Example 2 of this application Figure 40 A schematic diagram of a digital work corresponding to the second process task state diagram shown;

[0120] Figure 43 A schematic diagram of a first process task state diagram provided in Example 3 of the present application;

[0121] Figure 44 A schematic diagram of a content block object created in a task state diagram provided in Example 3 of the present application;

[0122] Figure 45 A schematic diagram of subtask creation information input into a creation content block object for a user-framed subtask T5.n “Risk Warning n” provided in Example 3 of the present application;

[0123] Figure 46 A schematic diagram of the second process task state diagram of the collaborative creation task of "Enterprise Research Report" provided in Example 3 of this application;

[0124] Figure 47 Provided for Example 3 of this application Figure 46 A schematic diagram of an information snapshot corresponding to the second process task state diagram shown;

[0125] Figure 48 Provided for Example 3 of this application Figure 46 A schematic diagram of a digital work corresponding to the second process task state diagram shown;

[0126] Figure 49 Provided for Example 3 of this application Figure 46 A schematic diagram of a composite digital work corresponding to the second process task state diagram shown;

[0127] Figure 50 This is a schematic diagram of a user inputting subtask creation information in a drag-and-drop manner in a creation content block object of a framework-type subtask T5 "Risk Reminder" provided in Example 4 of the present application;

[0128] Figure 51 A schematic diagram of the second process task state diagram of the collaborative creation task of "Enterprise Research Report" provided in Example 4 of this application;

[0129] Figure 52 Provided for Example 4 of this application Figure 51 A schematic diagram of an information snapshot corresponding to the task state diagram shown;

[0130] Figure 53 A schematic diagram of a system provided in Example 4 of the present application pushing a creative content block object of subtask T5.h(1).n to a user;

[0131] Figure 54 A schematic diagram of subtask creation information input by a user in a creation content block object of a framework-type subtask T5.h(1).n “Risk Warning n” provided in Example 4 of the present application;

[0132] Figure 55 A schematic diagram of the second process task state diagram of the collaborative creation task of "Enterprise Research Report" provided in Example 4 of this application;

[0133] Figure 56 Provided for Example 4 of this application Figure 55 A schematic diagram of an information snapshot corresponding to the task state diagram shown;

[0134] Figure 57 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0135] Figure 58A A schematic diagram of the structure of a digital work generation device provided in an embodiment of the present application;

[0136] Figure 58B A schematic diagram of the structure of another digital work generation device provided in an embodiment of the present application;

[0137] Figure 59A A schematic diagram of the structure of a task issuing device provided in an embodiment of the present application;

[0138] Figure 59B A schematic diagram of the structure of another task issuing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0139] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0140] The embodiments of the present application provide a method, apparatus, device and medium for generating digital works and issuing tasks, so as to realize the collaborative creation of digital works by adding next-level subtasks as needed.

[0141] Among them, the method and the device, equipment, and medium are based on the same application concept. Since the principles of solving problems by the method and the device, equipment, and medium are similar, the implementation of the device, equipment, medium, and method can refer to each other, and the repeated parts will not be repeated.

[0142] The terms "first", "second", etc. (if any) in the specification and claims of the embodiments of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0143] The following examples and embodiments are to be understood as illustrative examples only. Although this specification may refer to "one," "an," or "some" examples or embodiments at several places, this does not mean that each such reference relates to the same example or embodiment, nor does it mean that the feature applies only to a single example or embodiment. Individual features of different embodiments may also be combined to provide further embodiments. Furthermore, terms such as "comprises" and "comprising" should be understood as not limiting the described embodiments to consisting only of those features already mentioned; such examples and embodiments may also include features, structures, units, modules, etc. that are not specifically mentioned.

[0144] The following describes in detail the various embodiments of the present application in conjunction with the accompanying drawings. It should be noted that the order in which the embodiments of the present application are presented only represents the order of the embodiments, and does not represent the advantages or disadvantages of the technical solutions provided by the embodiments.

[0145] The collaborative creation of digital works can decompose the collaborative creation task into multiple subtasks with dependencies and subtask description information. The task can be split into finer-grained subtasks with dependencies for creators to create.

[0146] To achieve better task decomposition and process management, the subtasks formed after task decomposition can be divided into two categories. One category is subtasks that do not include the next-level subtasks, which can be called atomic subtasks. The other category is subtasks that include the next-level subtasks, which can be called framework subtasks.

[0147] In collaborative creation communities, the demand for framework-type subtasks comes from three aspects.

[0148] Aspect 1: Task hierarchical planning requirements.

[0149] Many collaborative digital creation tasks often involve multiple disciplines and need to be broken down into numerous, finer-grained sub-goals. If all these sub-goals and their dependencies were incorporated into a task state diagram in a flat format, the diagram would become extremely complex.

[0150] To avoid overly complex task state graphs, it's necessary to appropriately aggregate certain sub-goals and their dependencies to form framework sub-tasks and their own sub-tasks, thus implementing hierarchical task planning. Hierarchical task planning can create a hierarchical structure for the sub-goal system, thereby avoiding the problem of overly complex task state graphs caused by flattening sub-goals.

[0151] The benefits of hierarchical planning of task state diagrams to avoid the complexity of subtask systems include:

[0152] For human users, complex task state diagrams are difficult to fit on the screens of smart devices, making them difficult to access and process. By layering the task state diagram, each layer can be more concise and intuitive, thus facilitating the collaborative creation of digital works: enabling experts from various fields to participate in collaborative creation in their fragmented time.

[0153] For machine intelligence users, complex tasks not only reduce machine intelligence processing efficiency but also lower the quality of processing results. Hierarchical planning of the task state graph not only simplifies each layer, but also allows for further granularity of subtasks through layered iteration, making the scenarios of the next-level subtasks more specific, the tasks more defined, and the prerequisites more complete. This improves machine intelligence processing efficiency, making processing costs more economical and energy-efficient, while also enhancing the quality of machine intelligence processing, making processing results more effective and reliable.

[0154] To meet the needs of hierarchical task planning, in the task template, the framework subtask can pre-set the next level of subtasks.

[0155] Sometimes, digital works contain certain sub-goals and their dependencies that are industry standards or rigid requirements for the digital work. Therefore, the task template developer or task publisher may want to set these standard and rigid-need sub-goals in a fixed manner to avoid the situation where the digital work completed by collaborative creation fails to meet the standard requirements and rigid requirements. In this case, the framework subtask should be able to directly have the next-level subtask. Framework subtasks that directly set the next-level subtask in the task template without the need for execution content can be called "direct framework subtasks." Framework subtasks that indirectly set the next-level subtask through execution content can be called "indirect framework subtasks." "Indirect framework subtasks" eliminate the need for all-in-one task planning at the initial stage of the task, and instead empower task executors to gradually refine and improve the task plan during the task execution process.

[0156] In related technologies, framework-type subtasks in subtask systems can pre-set next-level subtasks, and content block clustering systems can pre-set next-level content block clusters. However, according to existing technologies, framework-type subtasks must first have execution content, which then creates next-level subtasks. In other words, according to existing technologies, framework-type subtasks are all "indirect framework-type subtasks" and cannot directly create next-level subtasks.

[0157] The second aspect: the creation requirements of the next-level sub-task system.

[0158] During the collaborative creation of digital works, participating creators may have different understandings and ideas about the creation and classification of collaborative task sub-goals than those who created the task template. If the task template sets all sub-goals and their dependencies, the task decomposition method will be too rigid, and the corresponding task state diagram will lack flexibility, making it difficult to better adapt to the specific needs of each digital work creation task.

[0159] In order to avoid the task decomposition method of collaborative creation of digital works being too rigid, after the collaborative creation task is released, it is necessary to give the creators participating in the collaborative creation a certain degree of task decomposition creation ability.

[0160] To meet this need, in the task template, the framework-type subtask may not pre-set the next-level subtask. After the collaborative creation task is released, the creator inputs the creation information of the framework-type subtask to form the execution content of the framework-type subtask, thereby creating the next-level subtask of the framework-type subtask and its dependencies. This type of framework-type subtask that indirectly has the next-level subtask through the execution content of the framework-type subtask is an "indirect framework-type subtask." "Indirect framework-type subtasks" give subtask creators the ability to gradually refine the task planning plan during the task execution process.

[0161] In the related art, the solution of creating execution content for framework-type subtasks to meet the creation requirements of the next-level subtask system has been fully described and will not be repeated here.

[0162] Thirdly, the number of next-level subtasks can be increased as needed.

[0163] For certain collaborative digital work creation tasks, there exists a special type of framework subtask whose number of subtasks is undefined and must be added as needed by the creator of the subtask. This type of framework subtask is referred to as a variable-length framework subtask. Framework subtasks whose number of subtasks is determined by the task template or the execution content of the framework subtask are referred to as fixed-length framework subtasks.

[0164] For example, the "risk warning" framework subtask of the collaborative creation task of an enterprise research report belongs to an indefinite-length framework subtask. Each next-level subtask of this framework subtask corresponds to a risk warning. However, before a corporate research report is finalized, it is uncertain how many risk warnings there will be in the risk warning chapter of the report. When formulating the task template, the task template developer cannot determine the number of risk warnings in advance. Even the creator of the "risk warning" framework subtask cannot determine the number of risk warnings in advance when creating the execution content of the "risk warning" framework subtask, that is, it is impossible to determine the number of next-level subtasks that the "risk warning" framework subtask has. Therefore, the collaborative creation method needs to propose a solution, whereby the creator of the next-level subtask of the "risk warning" framework subtask adds the next-level subtask as needed during the creation process.

[0165] However, the existing technology has not yet provided a solution for how to realize the requirement of adding the next-level subtasks of indefinite-length framework-type subtasks on demand. That is, the existing technology cannot support the situation where there are indefinite-length framework-type subtasks in certain collaborative creation tasks, that is, the number of its next-level subtasks is uncertain. When formulating the task template, the task template developer cannot determine in advance the number of next-level subtasks that the indefinite-length framework-type subtask has. Even the creator of the framework-type subtask cannot determine in advance the number of next-level subtasks that the framework-type subtask has when creating the execution content of the framework-type subtask. The existing technology cannot allow the creator of the next-level subtask of the framework-type subtask to add the next-level subtask on demand during the creation process, which brings difficulties to the execution of the indefinite-length framework-type subtask.

[0166] Therefore, in order to enhance the ability of subtask creators to gradually refine task planning schemes during task execution, it is necessary to solve the problem that existing technologies cannot allow creators of subtasks of indefinite-length framework-type subtasks to add subtasks of the next level as needed during the creation process, thereby achieving better hierarchical task planning. Figure 1A , the embodiment of the present application provides a method for generating a digital work, including:

[0167] S101. Acquire a first collaborative creation task, the first collaborative creation task including one or more subtasks, the one or more subtasks including at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask having an indefinite-form first-lower-level subtask, the indefinite-form first-lower-level subtask used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask having a second-lower-level subtask queue, the second-lower-level subtask queue sorting the second-lower-level subtasks in a received order;

[0168] The digital work generation method provided in the embodiment of the present application can be implemented on the user terminal side, for example, and of course can also be implemented on the network side.

[0169] S102: Obtain an instruction for a first target subtask selected by a first creator from among the one or more subtasks; the first target subtask is the indefinite first lower-level subtask;

[0170] The instruction may be, for example, a user's click, voice, or other target subtask selection instruction. For example, it may also be an instruction sent by a machine intelligence user through a program interface.

[0171] S103. According to the instruction, provide the first target subtask to the first creator, so that the first creator can perform creation;

[0172] S104: Receive first creation information of the first target subtask from the first creator;

[0173] The second lower-level subtask corresponding to the first creation information has the first creation information.

[0174] S105. Determine the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask.

[0175] The content of the digital work corresponding to the creation information includes, for example: the creation information input by the creator, and the position number of the creation information in the entire target digital work.

[0176] For example Figure 2 The digital work content shown in the figure, in which "5. Risk Warning" is the digital work content corresponding to the indefinite length frame type subtask, has two subtasks under it before the creation of the work, namely "5.1 Risk Warning 1" and "5.2 Risk Warning 2". In the subtask queue corresponding to "5. Risk Warning", "5.1 Risk Warning 1" is ranked first and "5.2 Risk Warning 2" is ranked last. The letters in it represent the creative information entered by the creator. Finally, the following is generated: Figure 2 The content of the digital work shown.

[0177] It should be noted that the next-layer subtask of any of the variable-length frame-type subtasks described in the embodiments of the present application can be an atomic subtask or a frame-type subtask.

[0178] In some embodiments, determining the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first variable-length frame-type subtask includes:

[0179] Submitting the first creation information;

[0180] Generate a second-level subtask corresponding to the first creative information according to the first target subtask, wherein the second-level subtask corresponding to the first creative information has the first creative information; and has a first variable-length frame-type subtask of the first target subtask and a second-level subtask corresponding to the first creative information;

[0181] Obtaining the order of the second-lower-layer subtask corresponding to the first creation information in the second-lower-layer subtask queue owned by the first variable-length frame-type subtask;

[0182] According to the sorting, the digital work content corresponding to the first creation information is determined.

[0183] Based on the same concept, see Figure 1B , this embodiment of the application provides another method for generating a digital work, including:

[0184] S201. Acquire a second collaborative creation task, the second collaborative creation task including one or more subtasks, the one or more subtasks including at least one second indefinite-length frame-type subtask and at least one indefinite-third-lower-level subtask, the second indefinite-length frame-type subtask having second execution content, the second execution content having an indefinite-third-lower-level subtask, the indefinite-third-lower-level subtask being used to generate one or more fourth-lower-level subtasks; the second execution content of the second indefinite-length frame-type subtask having a fourth-lower-level subtask queue, the fourth-lower-level subtask queue sorting the fourth-lower-level subtasks in a received order;

[0185] S202: Obtain an instruction for a second target subtask selected by a second creator from among the one or more subtasks; the second target subtask is the indefinite third-lower-level subtask;

[0186] S203: providing the second target subtask to the creator according to the instruction, so that the second creator can perform creation;

[0187] S204: Receive second creation information of the second target subtask from the second creator;

[0188] The fourth lower-level subtask corresponding to the second creation information has the second creation information.

[0189] S205. Determine the digital work content corresponding to the second creation information based on the second creation information and the order of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue owned by the second execution content owned by the second indefinite-length frame-type subtask.

[0190] It should be noted that the next-layer subtask of any of the variable-length frame-type subtasks described in the embodiments of the present application can be an atomic subtask or a frame-type subtask.

[0191] In some embodiments, based on the second creative information and the ranking of the fourth lower-level subtask corresponding to the second creative information in the fourth lower-level subtask queue owned by the second execution content owned by the second variable-length frame-type subtask, determining the digital work content corresponding to the second creative information includes:

[0192] Submitting the second creation information;

[0193] A fourth lower-level subtask corresponding to the second creative information is generated according to the second target subtask, and the fourth lower-level subtask corresponding to the second creative information has the second creative information; has the second execution content owned by the second indefinite-length frame-type subtask of the second target subtask, and has the fourth lower-level subtask corresponding to the second creative information;

[0194] Obtaining the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content;

[0195] Based on the sorting, the digital work content corresponding to the second creation information is determined.

[0196] That is, in the embodiment of the present application, for the indefinite-length frame-type subtask, for example, the following two specific implementation methods can be adopted:

[0197] The first implementation method: for a direct frame-type subtask (ie, the first indefinite-length frame-type subtask), it is implemented by a task template.

[0198] Second implementation method: For the indirect frame-type subtask (ie, the second indefinite-length frame-type subtask), it is implemented by the execution content of the frame-type subtask.

[0199] Among them, regarding the first implementation:

[0200] For direct variable-length frame subtasks:

[0201] First, the task template developer defines the subtask as a direct frame subtask in the task template, and at the same time, a variable-length frame subtask, which can be called a "direct variable-length frame subtask".

[0202] Furthermore, the task template determines, for the direct indefinite-length frame-type subtask, the composition of the next-level subtasks, the content block clusters corresponding to the next-level subtasks, and the frame-type content block clusters corresponding to the frame-type subtasks. However, the task template does not determine the number of the next-level subtasks, and therefore, the number of content block clusters corresponding to the next-level subtasks.

[0203] After the task is released, the creator of the next-level subtask of the framework-type subtask creates execution content for the next-level subtask.

[0204] During the creative process, in the snapshot of the digital work process information, the number of current second-level subtasks in the second-level subtask queue owned by the direct indefinite-length frame-type subtask is the number of second-level subtasks currently owned by the direct indefinite-length frame-type subtask.

[0205] After the creation is completed, in the finalized information snapshot of the digital work, the number of current second-lower-level subtasks in the second-lower-level subtask queue owned by the direct indefinite-length frame-type subtask is the number of second-lower-level subtasks owned by the direct indefinite-length frame-type subtask in the finalized work.

[0206] The next-level subtask directly following a variable-length frame-type subtask can be either an atomic subtask, the business process of which is described in Example 1, or a frame-type subtask, the business process of which is described in Example 3. Similarly, the next-level subtask directly following a variable-length frame-type subtask can also be partially atomic and partially frame-type.

[0207] Regarding the second implementation:

[0208] For indirect variable-length frame subtasks:

[0209] First, the task template developer defines the subtask as an indirect frame-type subtask in the task template, and at the same time, an indefinite-length frame-type subtask, which can be called an "indirect indefinite-length frame-type subtask".

[0210] After the task is released, the creator of the framework-type subtask creates execution content for the subtask.

[0211] The execution content determines the composition of the next-level subtasks, the content block clusters corresponding to the next-level subtasks, and the framework-type content block clusters corresponding to the framework-type subtasks. However, the execution content does not determine the number of the next-level subtasks, and therefore does not determine the number of content block clusters corresponding to the next-level subtasks.

[0212] After the framework-type subtask execution content is published, the creator of the next-level subtask owned by the execution content creates the execution content for the next-level subtask.

[0213] During the creative process, in the snapshot of the digital work process information, the number of current fourth-level subtasks in the fourth-level subtask queue of the second execution content owned by the indirect indefinite-length frame-type subtask is the number of fourth-level subtasks owned by the second execution content owned by the current indirect indefinite-length frame-type subtask.

[0214] After the creation is completed, in the snapshot of the finalized information of the digital work, the number of current fourth-level subtasks in the fourth-level subtask queue of the second execution content owned by the indirect indefinite-length frame-type subtask is the number of fourth-level subtasks owned by the second execution content owned by the indirect indefinite-length frame-type subtask in the finalized version.

[0215] The next-level subtasks owned by the second execution content of an indirect variable-length frame-type subtask can be atomic subtasks, the business process of which is described in the subsequent Example 2, or framework subtasks, the business process of which is described in the subsequent Example 4. Similarly, the next-level subtasks owned by the second execution content of an indirect variable-length frame-type subtask can also be partially atomic subtasks and partially framework subtasks.

[0216] Corresponding to the first method of generating digital works, see Figure 3A , an embodiment of the present application provides a task publishing method, including:

[0217] S301: Acquire task setting information input by a task publisher, where the task setting information corresponds to a task template;

[0218] The task template developer creates the task template, which provides an initial collaborative plan for the collaborative creation of the task and is the basis for task publishing. The task template includes one or more initial subtasks, one or more initial content clusters, and the dependencies between these initial subtasks and initial content clusters.

[0219] The task publisher selects a task template, enters task setting information in the task template, generates a collaborative creation task, and publishes it.

[0220] It should be noted that the task template developers, task publishers, and collaborative creators (also referred to as creators) described in the embodiments of this application refer to user roles in the collaborative creation process of digital works. The template developer refers to the user role that creates the template, the task publisher refers to the user role that publishes the collaborative creation task, and the collaborative creator refers to the role that creates the published collaborative creation task. Template developers, task publishers, and collaborative creators may include but are not limited to at least one of individual users, group users, AI users, machine intelligence users, etc., and the embodiments of this application do not limit this.

[0221] S302. Generate and publish a target collaborative creation task based on the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks; wherein the one or more subtasks include: at least one indefinite-length frame-type subtask and at least one indefinite next-level subtask (corresponding to the above-mentioned direct indefinite-length frame-type subtask, i.e., the first indefinite-length frame-type subtask).

[0222] In some embodiments, the target collaborative creation task is a first collaborative creation task; the indefinite-length frame-type subtask is a first indefinite-length frame-type subtask; the indefinite next-level subtask is an indefinite first-next-level subtask, the first indefinite-length frame-type subtask has an indefinite first-next-level subtask, and the indefinite first-next-level subtask is used to generate one or more second-next-level subtasks; the first indefinite-length frame-type subtask has a second-next-level subtask queue, and the second-next-level subtask queue sorts the second-next-level subtasks in the order of receipt.

[0223] Corresponding to the second method of generating digital works, see Figure 3B Another task publishing method provided in an embodiment of the present application includes:

[0224] S401: Acquire task setting information input by a task publisher, where the task setting information corresponds to a task template;

[0225] S402. Generate and publish a target collaborative creation task based on the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks; wherein the one or more subtasks include: at least one indefinite-length frame-type subtask (corresponding to the above-mentioned indirect indefinite-length frame-type subtask, i.e., the second indefinite-length frame-type subtask).

[0226] In some embodiments, the target collaborative creation task is the second collaborative creation task; the variable-length frame-type subtask is the second variable-length frame-type subtask;

[0227] When the creator creates second execution content for the second indefinite-length frame-type subtask by publishing the second collaborative creation task, the one or more subtasks further include: at least one indefinite-length third lower-level subtask;

[0228] Among them, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-level subtask, and the indefinite third-level subtask is used to generate one or more fourth-level subtasks; the second indefinite-length frame-type subtask has a second execution content with a fourth-level subtask queue, and the fourth-level subtask queue sorts the fourth-level subtasks in the order of receipt.

[0229] That is to say, in the embodiment of the present application, for a direct indefinite-length frame-type subtask, when the task is released, the direct indefinite-length frame-type subtask can have an indefinite lower-level subtask. Figure 4In the task status diagram shown, the "T5 Risk Warning" is the first indefinite-length frame-type subtask, and the "T5.n Risk Warning n" is the indefinite first-level subtask owned by the first indefinite-length frame-type subtask "T5 Risk Warning". The indefinite first-level subtask "T5.n Risk Warning n" is used to generate one or more second-level subtasks, that is, the creator can add new next-level subtasks (i.e., second-level subtasks) as needed.

[0230] However, for indirect variable-length frame-type subtasks, when the task is released, it does not have indefinite subtasks at the next level. Instead, it can only indirectly have indefinite subtasks at the next level through the second execution content after the subsequent creator creates execution content (i.e., the second execution content) for the indirect variable-length frame-type subtask. For example Figure 5 In the task status diagram shown, the "T5 Risk Warning" is the second indefinite-length frame-type subtask. When the creator d creates the second execution content [T5, d(1)] for the second indefinite-length frame-type subtask "T5 Risk Warning" through the published second collaborative creation task, the one or more subtasks also include: an indefinite third-lower-level subtask "T5.d(1).n Risk Warning n", wherein the second indefinite-length frame-type subtask "T5 Risk Warning" has the second execution content [T5, d(1)], and the second execution content [T5, d(1)] has the indefinite third-lower-level subtask "T5.d(1).n Risk Warning n", and the indefinite third-lower-level subtask "T5.d(1).n Risk Warning n" is used to generate one or more fourth-lower-level subtasks, that is, the creator can add new next-level subtasks (i.e., the fourth-lower-level subtask) as needed.

[0231] Four specific embodiments are given below as examples.

[0232] It should be noted that although the following embodiments take the collaborative creation task of text-based digital works (corporate research reports) as an example, the technical solutions provided in the embodiments of this application are also applicable to the collaborative creation tasks of other types of digital works, such as the collaborative creation of multimedia digital works such as metaverse theme parks and theme short plays, or the collaborative creation of hybrid digital works that serve embodied intelligence, including text, multimedia, and physical world models, etc.

[0233] Example 1:

[0234] This first embodiment takes the enterprise research report and the first implementation method (corresponding to a direct indefinite-length framework-type subtask) as an example to introduce a collaborative creation method for digital works that can add atomic next-level subtasks as needed.

[0235] 1.1 Develop and publish collaborative creation task templates.

[0236] Step M.1: Assume that the task template developer M inputs the creation information of the task template α(m), including: template description information, the initial task state diagram of the collaborative creation task (subtask system), the content block clustering system, reference creation information, and task setting objects.

[0237] 1.1.1 Set the template description information.

[0238] The template description information is used to describe the task template.

[0239] An example of the description of this template is as follows: This task template is used to complete a corporate research report through collaborative authoring.

[0240] 1.1.2 Set the task setting object.

[0241] The task setting object TaskSet in the task template is used to provide task publishers with input of task setting information.

[0242] The following is an example of the task setting object TaskSet of this template:

[0243] Information Block 1 of the TaskSet object: Enterprise Research Report Number. Note: Optional. This number can be assigned automatically by the system, rather than set by the task issuer.

[0244] Information Block 2 of the TaskSet object: The full name of the company being studied. Note: Required. The full name uniquely identifies the company being studied.

[0245] 1.1.3 Set up the initial task state diagram.

[0246] How to set the initial task state diagram can be implemented using existing related technologies and will not be described in detail in this embodiment.

[0247] 1.1.3.1 Set subtasks and node relationships.

[0248] The node relationships between the nodes in the initial task state diagram may include ownership-attribution relationships and derived-dependency relationships.

[0249] The ownership-attribution relationship between nodes defines the hierarchical relationship of nodes in the topology of the task state graph. In a task template, these relationships include the ownership-attribution relationship between a framework-type subtask and its owned default-type execution content, the ownership-attribution relationship between default-type execution content and its owned next-level subtasks, and the ownership-attribution relationship between a framework-type subtask and its owned next-level subtasks.

[0250] Derivation-dependency relationships between nodes define the sequential relationship between nodes in the creation process of a task state diagram. In a task template, derivation-dependency relationships between nodes include derivation-dependency relationships between subtask nodes and derivation-dependency relationships between subtask nodes and the execution content nodes of other subtasks. These dependencies between subtasks are used to set the subtask's creation status. Before creating a subtask, the creator must first obtain the subtask's creation status. The creation status includes a createable state and a non-createable state, which are set based on the dependency relationships between the subtasks. For example, subtask T2 depends on subtask T1. In other words, T1 derives T2. A derivation-dependency relationship exists between T1 and T2. Because T2 depends on T1, T2 is in a non-createable state until T1 has completed execution content and its basic information is complete. Only when T1 has completed execution content and its basic information is complete can T2 enter a createable state. Creators can only generate execution content for subtasks that are in a createable state.

[0251] Based on the collaborative creation task decomposition and process management requirements, the template developer M developed an example of the node relationship settings (initial subtask system) for each node in the initial task state diagram for the "Enterprise Research Report" task template, as shown in Table 1 below:

[0252]

[0253]

[0254]

[0255] Table 1

[0256] Note 1:

[0257] The next-level subtasks of a direct fixed-length frame-type subtask are fixed-type next-level subtasks.

[0258] The next-level subtask of an indirect fixed-length frame-type subtask is a conditional next-level subtask.

[0259] The next-level subtasks of a direct indefinite-length frame-type subtask are indefinite-type next-level subtasks. The next-level subtasks of the execution content of an indirect indefinite-length frame-type subtask are indefinite-type next-level subtasks.

[0260] Note 2: For direct or indirect variable-length frame-type subtasks, the variable length variable n is included in their own variable-length subtasks. In the task template and when the task is published, the initial value of the length variable n is n = 0. After the task is published, during the creation process, if T5 has one new subtask, n = 1. If T5 has two new subtasks, n = 2. And so on.

[0261] 1.1.3.2 AI user operation of task state diagram.

[0262] In some embodiments, for AI or machine intelligence users, through the data structure of the initial task state diagram in the task template, the user device can read, operate, and maintain the initial task state diagram of the task template in its running memory.

[0263] The user device where the AI user or machine intelligence user is located can be a computing device or computing facility with information processing capabilities such as a computer / server / computing platform, and the present invention does not limit this.

[0264] 1.1.3.3Task status diagram overview version.

[0265] In some embodiments, in addition to using a data structure to operate and maintain the initial task state diagram of the task template in its running memory, the user device can also display the initial task state diagram in the interactive interface of the user device so that human users can intuitively obtain relevant information.

[0266] In the collaborative creation task template of "Enterprise Research Report", the initial task status diagram overview version is as follows: Figure 6 shown.

[0267] 1.1.3.4 Partially expanded version of the task status diagram.

[0268] In the "Corporate Research Report" collaborative creation task template, users can click on the framework subtask in the overview version of the initial task status diagram to view the next level of subtasks.

[0269] Take the next level subtask of checking the situation of T1 company as an example, Figure 7 shown.

[0270] Take the next level subtask of T2 industry analysis subtask as an example, the following is shown: Figure 8 shown.

[0271] Take the next level subtask of viewing T5 risk warning subtask as an example, the following is shown: Figure 9 shown.

[0272] 1.1.4 Develop a content block clustering system.

[0273] In the embodiment of the present application, the digital work is generated by assembling one or more first-level content block clusters according to the "overall content block cluster composition method".

[0274] Each first-level content block cluster can be a framework-type content block cluster or a classic-type content block cluster. Each framework-type content block cluster is generated by assembling one or more lower-level content block clusters. Each classic-type content block cluster can be generated by assembling one or more content blocks from the original content block, setting content block, default content block, or reference content block.

[0275] Each next-level content block cluster can be a next-level framework-type content block cluster or a next-level classic-type content block cluster. Each next-level framework-type content block cluster is generated by assembling one or more next-level content block clusters. Each next-level classic-type content block cluster can be generated by assembling one or more content blocks from among the original content blocks, setting content blocks, default content blocks, and reference content blocks.

[0276] It should be noted that the levels, layers and levels described in the embodiments of the present application have the same meaning.

[0277] The initial content block clustering system, or the initial set of content block cluster composition methods, is based on the collaborative authoring task requirements. In the "Enterprise Research Report" collaborative authoring task template, the initial set of content block cluster composition methods includes an overall content block cluster composition method and several first-level content block cluster composition methods. In this embodiment, the initial set of content block cluster composition methods includes one overall content block cluster composition method and eight first-level content block cluster composition methods.

[0278] For the specific definitions of the creation content block, setting content block, default content block, and reference content block, please refer to the existing related technologies and will not be repeated in this embodiment.

[0279] 1.1.4.1 Overall content block clustering composition method.

[0280] Based on the collaborative creation task's requirement to assemble the content of each subtask into a digital work, the template developer M developed an example of the overall content block clustering composition for the "Enterprise Research Report" task template, as shown in Table 2 below:

[0281]

[0282] Table 2

[0283] in:

[0284] BlockCluster (1) "report header", BlockCluster (T6) "report highlights", and BlockCluster (2) "report footer" are classic content block clusters.

[0285] BlockCluster (T1) "Company Profile" to BlockCluster (T4) "Profit Forecast and Investment Advice" are fixed-length framework-type content block clusters.

[0286] BlockCluster (T5) "Risk Warning" is a direct indefinite-length frame-type content block clustering.

[0287] In this embodiment, the digital work of "Enterprise Research Report" is generated by assembling eight first-level content block clusters according to the above "overall content block cluster composition method". The "Enterprise Research Report" task template also includes the composition method of the above eight first-level content block clusters, as shown below.

[0288] 1.1.4.2 The initial composition of the first-level content block cluster BC(1) “report header” is BC(1,M).

[0289] An example of the initial composition BlockCluster(1,M) formulated by the template developer M for the “report header” of the classic content block cluster BlockCluster(1) is shown in Table 3 below:

[0290]

[0291] Table 3

[0292] 1.1.4.3 The initial composition of the first-level content block cluster BC(T6) “Report highlights” BC(T6,M).

[0293] An example of the initial composition BlockCluster(T6,M) formulated by the template developer M for the classic content block cluster BlockCluster(T6) "Report Key Points" is shown in Table 4 below:

[0294]

[0295] Table 4

[0296] 1.1.4.4 The initial composition of the first-level content block cluster BC(T1) “Company situation” is BC(T1,M).

[0297] An example of the initial content block cluster composition BlockCluster(T1,M) (Template Maker Responsibility 4) created by the template creator M for the direct fixed-length frame-type content block cluster BlockCluster(T1) "Company Profile" is shown in Table 5 below:

[0298]

[0299]

[0300] Table 5

[0301] 1.1.4.5 The initial composition of the first-level content block clustering BC(T2) “Industry Analysis” is BC(T2,M).

[0302] The template developer M creates the composition BlockCluster{T2,[T2,M]} (Template developer responsibility 5) for the indirect fixed-length framework content block cluster BlockCluster(T2) "Industry Analysis". An example is shown in Table 6 below:

[0303]

[0304]

[0305] Table 6

[0306] BlockCluster (T3) "Competitiveness Analysis" and BlockCluster (T4) "Profit Forecast and Investment Advice" are both direct fixed-length framework-type content block clusters. Their composition follows the same rules as BlockCluster (T1) "Company Profile" and will not be repeated here.

[0307] 1.1.4.6 The initial composition of the first-level content block cluster BC(T5) “Risk Warning” is BC(T5,M).

[0308] The template developer M creates the initial composition BlockCluster(T5,M)(n=0) for the direct variable-length frame-type content block cluster "Risk Warning" and has DCBlock_f(T5.head), DCBlock_u(T5.0), and CCBlock_u(T5.n)(n>0). The specific description is shown in Table 7 below:

[0309]

[0310] Table 7

[0311] Rule description 1: In the task template, the initial value of the length variable n included in the direct indefinite-length frame-type subtask T5 is n=0.

[0312] When the task is released, n=0, and T5 does not have a new level 2 subtask.

[0313] At this time, the default execution content [T5,M](n=0) of the direct indefinite-length frame-type subtask T5 "Risk Prompt" corresponds to the initial composition mode BC(T5,M)(n=0) of the direct indefinite-length frame-type content block cluster BlockCluster(T5) "Risk Prompt".

[0314] Among them, BC(T5,M)(n=0) consists of the following content chunk clusters:

[0315] Fixed default content block DCBlock_f (T5.head);

[0316] Undefined default content block DCBlock_u (T5.0);

[0317] Undefined creative content block header CCBlock_u (T5.n.head);

[0318] Undefined creative content block body CCBlock_u (T5.n.body).

[0319] Rule Description 2: When T5 has a new second-level subtask, n = 1. The new second-level subtask is T5.1, and the execution content of T5.1 is [T5.1, x1(1)], where x1 is the user who created the execution content for T5.1.

[0320] At this time, the current execution content of the direct indefinite-length frame-type subtask T5 "Risk Prompt" is [T5, [T5.1, x1(1)]] (n=1),

[0321] Corresponding to the execution composition method BC(T5,[T5.1,x1(1)])(n=1) of the direct indefinite-length frame-type content block cluster BlockCluster(T5) "Risk Prompt".

[0322] Among them, BC(T5,[T5.1,x1(1)])(n=1) consists of the following content block clusters:

[0323] Fixed default content block DCBlock_f (T5.head);

[0324] Undefined execution creation content block header CCBlock_u(T5.1.head,

[0325] [T5.1.head,x1(1)]);

[0326] Undefined execution creation content block body CCBlock_u(T5.1.body,

[0327] [T5.1.body,x1(1)]);

[0328] Undefined creative content block header CCBlock_u (T5.n.head);

[0329] Undefined creative content block body CCBlock_u (T5.n.body).

[0330] Rule Description 3: When T5 has two new second-level subtasks, n = 2. The new second-level subtasks are T5.1 and T5.2. The execution content of T5.1 is [T5.1, x1(1)], and the execution content of T5.2 is [T5.2, x2(1)], where x1 and x2 are the users who created the execution content for T5.1 and T5.2, respectively.

[0331] At this time, the current execution content of the direct indefinite-length frame-type subtask T5 "Risk Prompt" [T5, [T5.1, x1(1)][T5.2, x2(1)]] (n = 2) corresponds to the current execution composition mode BC(T5, [T5.1, x1(1)][T5.2, x2(1)]) (n = 2) of the direct indefinite-length frame-type content block cluster BC(T5) "Risk Prompt".

[0332] Among them, BC(T5,[T5.1,x1(1)][T5.2,x2(1)])(n=2) consists of the following content blocks:

[0333] Fixed default content block DCBlock_f (T5.head);

[0334] Undefined execution creation content block header CCBlock_u(T5.1.head,

[0335] [T5.1.head,x1(1)]);

[0336] Undefined execution creation content block body CCBlock_u(T5.1.body,

[0337] [T5.1.body,x1(1)]);

[0338] Undefined execution creation content block header CCBlock_u(T5.2.head,

[0339] [T5.2.head,x2(1)]);

[0340] Undefined execution creation content block body CCBlock_u(T5.2.body,

[0341] [T5.2.body,x2(1)]);

[0342] Undefined creative content block header CCBlock_u (T5.n.head);

[0343] Undefined creative content block body CCBlock_u (T5.n.body).

[0344] And so on.

[0345] Rule 4: When T5 has N new second-level subtasks, n = N (N > 0). The new second-level subtasks are T5.1, ..., and T5.N. The execution content owned by T5.1 is [T5.1, x1(1)], ..., and the execution content owned by T5.N is [T5.N, xN(1)]. Where xN is the user who created the execution content for T5.N.

[0346] At this time, the current execution content of the direct indefinite-length frame-type subtask T5 "Risk Prompt" [T5, [T5.1, x1(1)]......[T5.N, xN(1)]] (n=N) corresponds to the execution composition method BC(T5, [T5.1, x1(1)]......[T5.N, xN(1)])(n=N) of the direct indefinite-length frame-type content block cluster BC(T5) "Risk Prompt".

[0347] Among them, BC(T5,[T5.1,x1(1)]......[T5.N,xN(1)])(n=N) is composed of the following content block clusters:

[0348] Fixed default content block DCBlock_f (T5.head);

[0349] Undefined execution creation content block header CCBlock_u(T5.1.head,

[0350] [T5.1.head,x1(1)]);

[0351] Undefined execution creation content block body CCBlock_u(T5.1.body,

[0352] [T5.1.body,x1(1)]);

[0353] ......

[0354] Undefined execution creation content block header CCBlock_u(T5.N.head,

[0355] [T5.N.head,xN(1)]);

[0356] Undefined execution creation content block body CCBlock_u(T5.N.body,

[0357] [T5.N.body,xN(1)]);

[0358] Undefined creative content block header CCBlock_u (T5.n.head);

[0359] Undefined creative content block body CCBlock_u (T5.n.body).

[0360] Rule Description 5: Unformed creative content blocks are divided into two types: title part and main body part. The title part of an unformed creative content block provides a title function for the main body part of an unformed creative content block. The main body part of an unformed creative content block provides main content for the title part of an unformed creative content block. The main body part of an unformed creative content block can be associated with the title part of an unformed creative content block, and the two correspond to the same next-level subtask. The next-level subtask belongs to the creative execution content of the framework-type subtask. In addition, for the content block clustering of certain tasks, the main body part of an unformed creative content block can also exist independently without being associated with the title part.

[0361] 1.1.5 Develop reference creation information.

[0362] When developing a task template α(m), creator m can also create reference creation information for the subtasks within that template. This allows creators of these subtasks to more easily create based on the reference creation information, rather than starting from scratch. This increases the appeal of the task template α(m) to creators, making it more likely to be adopted by task issuers and to result in finalized digital works, thereby potentially generating more copyright revenue.

[0363] 1.1.5.1 Prepare reference information for T2 “Industry Analysis”.

[0364] The first-level subtask, T2 (Industry Analysis), corresponds to a content block clustering subtask and is an indirect fixed-length framework subtask. According to the task template, T2's first mapping is T2~BlockCluster(T2), and the default execution context of T2, [T2,M], corresponds to [T2.M]~BlockCluster{T2,[T2,M]}.

[0365] The reference creation information prepared by the template developer M for the first-level subtask T2 includes: execution content reference creation information [T2, refer], execution content block cluster reference creation information BlockCluster{T2,[T2, refer]}, and execution correspondence reference creation information [T2, refer]~BlockCluster{T2,[T2, refer]}.

[0366] 1.1.5.1.1T2 execution content references creation information [T2, refer] (give an example of how to use it).

[0367] An example of the execution content reference creation information [T2, refer] prepared by the template developer M for the first-level subtask T2 "industry analysis" is shown in Table 8 below.

[0368]

[0369] Table 8

[0370] 1.1.5.1.2 T2 performs content block clustering with reference to the authoring information BlockCluster{T2,[T2,refer]}.

[0371] An example of the execution content block cluster reference creation information BlockCluster{T2,[T2,refer]} created by the template creator M for the first-level subtask T2 “industry analysis” is shown in Table 9 below:

[0372]

[0373]

[0374] Table 9

[0375] 1.1.5.2 Develop reference information for T5.n “Risk Warning n”.

[0376] The second-level subtask, T5.n ("Risk Warning n"), corresponds to a content block cluster and is a direct, indefinite-length framework. According to the task template, T5.n has three second-level relationships: T5.n to DCBlock_u (T5.0), T5.n.head to CCBlock_u (T5.n.head), and T5.n.body to CCBlock_u (T5.n.body).

[0377] The reference creation information prepared by the template developer M for the second-level subtask T5.n includes: execution content reference creation information [T5.n,refer], execution creation content block reference creation information CCBlock_u{T5.n.head,[T5.n,refer]} and CCBlock_u{T5.n.body,[T5.n,refer]}, and execution correspondence relationship reference creation information [T5.n.head,refer]~CCBlock_u{T5.n.head,[T5.n,refer]} and [T5.n.body,refer]~CCBlock_u{T5.n.body,[T5.n,refer]}.

[0378] 1.1.5.2.1 T5.n performs content reference creation information [T5.n, refer] (give an example of how to use it).

[0379] The template developer M prepares the execution content reference creation information [T5.n,refer] for the second-level subtask T5.n "risk warning n" as follows: Figure 10 shown.

[0380] In the task template, the initial value of n is n = 0. After the task is published, during the creation process, if T5 has one new execution content, n = 1. If T5 has two new execution contents, n = 2. And so on. The new execution contents mentioned here do not include revised execution contents. In the row containing CCBlock_u(T5.n.head), enter the title content of the "Risk Warning n" section. In the input box containing CCBlock_u(T5.n.body), enter the body content of the "Risk Warning n" section.

[0381] 1.1.5.2.2T5.n executes the creation content block reference creation information CCBlock{T5.n,[T5.n,refer]}.

[0382] Examples of the execution creation content block reference creation information CCBlock_u{T5.n.head,[T5.n,refer]} and CCBlock_u{T5.n.body,[T5.n,refer]} created by the template creator M for the second-level subtask T5.n "Risk Warning n" are shown in Table 10 below.

[0383]

[0384] Table 10

[0385] 1.1.6 Generate task template data block.

[0386] Step M.2: Receive the task template α(M) creation information input by the task template creator M and generate the task template data block DB{α(M)} corresponding to α(M). This includes:

[0387] ●Template content information, task template information developed by template developer M, including various creation information generated by the aforementioned step M.1, such as: template description information, task setting object, subtask system (initial task state diagram), content block clustering system, reference creation information, etc.

[0388] ●Task template identifier: α(M). This is the globally unique task template identifier generated by the system for the current task template, which can be a string or binary code string.

[0389] ●Template creator identity information, including user ID of user M and / or user public key.

[0390] ●The data block identifier of this task template is DB[α(M)].

[0391] Step M.3: The server or user device generates a digital fingerprint of the task template data block based on the task template data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the task template data block.

[0392] Step M.4: The server stores the task template data block and generates an access address for the task template data block.

[0393] 1.1.7 Release the task template data package.

[0394] Step M.5: The user device or server generates a task template data packet, which includes the following contents: digital fingerprint of the task template data block, access address of the task template data block, and identity information of the task template developer (such as the user's public key).

[0395] Step M.6: The user device or server publishes the task template data package so that users related to the collaborative creation community can access or be pushed to the task template data package.

[0396] Step M.6.1: The user terminal or server may publish the task template data package to a suitable blockchain and obtain the blockchain access address as the index of the task template data package for authorization. This may include the following steps:

[0397] The collaborative community selects the appropriate blockchain, public chain, consortium chain or private chain.

[0398] Collaboratively develop a task template data package on the blockchain to publish a smart contract and deploy it on the blockchain.

[0399] The task template publisher initiates a task template data package publishing transaction, calls the task template data package publishing smart contract on the blockchain, publishes the task template data package to the blockchain, and obtains the corresponding blockchain access address as the task template data package index for recording rights.

[0400] Step M.6.2: The user terminal or server can upload the task template data package "Enterprise Research Report Collaborative Creation Task Template α(M)" to the task template library. Through the task template library, collaborative creation community users can browse this task template on demand. Furthermore, the system can push this task template to appropriate collaborative creation community users.

[0401] 1.1.8 Review the initial digital draft.

[0402] The digital work draft corresponding to the task template of the collaborative creation task is called the initial digital work draft.

[0403] Based on the user's viewing request, this system can generate an initial digital work draft.

[0404] The initial digital draft of the "Enterprise Research Report" is generated by assembling the 8 first-level content block clusters in the aforementioned Table 2 "Overall content block cluster composition method".

[0405] 1.2 Set up and publish collaborative creation tasks.

[0406] After the task template is released, users can access the task template library through their user devices and select a suitable collaborative creation task template based on their own collaborative creation needs for digital works.

[0407] For human users, the user device may be a mobile phone, computer, or other terminal device. For AI or machine intelligence users, the user device may be a terminal or server device running AI software.

[0408] After the user device obtains the task template, the user can input task setting information into the task setting object of the task template through the user device according to the user's collaborative creation needs of the digital work.

[0409] The task setting information is used to be provided to the creator, and the creator inputs creation information based on the task setting information and related information such as related subtask description information.

[0410] The task setting information is further used to generate setting content block execution content by a setting content block generation method.

[0411] 1.2.1 Enter task setting information.

[0412] Step R1: User A accesses the task template library through the user device and selects a suitable collaborative creation task template α(M) of “Enterprise Research Report”.

[0413] Note: For human users, the user device is a mobile phone app or computer application software, etc. For AI or machine intelligence users, the user device is a terminal or server device running AI or machine intelligence software.

[0414] Step R2: The user terminal obtains the task template content.

[0415] Step R3: User A enters the task setting information [TaskSet, A] in the task setting object TaskSet of the task template. Specifically, it may include the following information blocks:

[0416] √Task setting information block 1: Enterprise research report number "ERR100068".

[0417] √Task setting information block 2: "Beijing Qisui Technology Co., Ltd."

[0418] 1.2.2 Generate task data block.

[0419] Step R4: Receive the task setting information [TaskSet, A] input by user A and generate the task data block DB {Task_ID(N)} corresponding to the collaborative creation task Task_ID(N). This includes:

[0420] ●Task template used: Task template identifier α(M).

[0421] ●Task setting information [TaskSet, A]: various setting information generated in the aforementioned step R3.

[0422] ●Globally unique task identifier Task_ID(N): This is the globally unique task identifier generated by the system for the current task, which can be a string or binary code string.

[0423] ●Task issuer identity information, including user A’s user ID and / or user public key.

[0424] ●Data block identifier of this task, DB[Task_ID(N)].

[0425] Step R5: The server or user device generates a digital fingerprint of the task data block based on the task data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the task data block.

[0426] Step R6: The server or user device stores the task data block and generates an access address for the task data block.

[0427] 1.2.3 Release the task data package.

[0428] Step R7: The server or user device generates a task data packet DP[Task_ID(N)], which includes the following contents: task data block access address, task publisher identity information (such as user public key), and task data block digital fingerprint.

[0429] Step R8: The server or user device publishes the task data package so that relevant users with access rights in the collaborative creation community can access or be pushed to the task data package.

[0430] Step R.8.1: The user terminal or server may publish the task data packet to a suitable blockchain and obtain the blockchain access address as the task data packet index for authorization. This may include the following steps: The collaborative community selects the appropriate blockchain, public chain, consortium chain or private chain.

[0431] Assist the community to develop task data packages on the blockchain and publish smart contracts, and deploy them on the blockchain.

[0432] The task publisher initiates a task data package publishing transaction, calls the task data package publishing smart contract on the blockchain, publishes the task data package to the blockchain, and obtains the corresponding blockchain access address as the task data package index for recording rights.

[0433] Step R.8.2: The user terminal or server can upload the task data packet DP[Task_ID(N)] to the task library. Through the task library, collaborative creation community users can browse the task on demand. In addition, the system can also push the task to appropriate collaborative creation community users.

[0434] 1.2.4 Set the task status diagram.

[0435] 1.2.4.1 Set up a diagram of the task state diagram.

[0436] After the task publisher publishes the task, the task status diagram of "Enterprise Research Report Collaborative Creation Task Task_ID(N)" is the set task status diagram, for example Figure 11 shown.

[0437] like Figure 11 As shown, compared with the initial task status diagram in the task template, the set task status diagram formed after the task publisher enters the task setting information has undergone one modification: "Task setting object" is updated to "Task setting information".

[0438] 1.2.4.2 Set the data settings of the task status diagram.

[0439] The node types, node relationships, and node states in the task state diagram can be set and maintained and operated in the running memory of the device using corresponding data structures in both the user device and the server device.

[0440] In some embodiments, for AI or machine intelligence users, the user device can read, operate, and maintain the task state diagram through the data structure of the task state diagram in its running memory, thereby participating in collaborative creation and following corresponding process rules.

[0441] The user device where the AI user or machine intelligence user is located can be a computing device or computing facility with information processing capabilities such as a computer / server / computing platform, and the embodiments of the present application do not limit this.

[0442] 1.2.5 Review and set up the digital work draft.

[0443] The digital work draft corresponding to the collaborative creation task is called the set digital work draft.

[0444] Note: It is understood that after setting the collaborative creation task, the task publisher can also view the digital work draft before publishing it. The main implementation steps are consistent with those described in this section.

[0445] Based on the viewing request of user X, the system can generate a set digital work draft. The main implementation steps include:

[0446] 1) Receive viewing request from user X.

[0447] 2) Generate an execution setting content block.

[0448] 3) Generate a set of initial composition modes for content block clusters. Specifically, according to the execution setting of the content block, the set of initial composition modes for content block clusters in the task template is updated to a set of set composition modes for content block clusters.

[0449] 4) Generate and set a digital work draft. Specifically, according to the clustering and setting composition mode set of the content blocks, assemble and generate the digital work draft.

[0450] 5) Feedback the set digital work draft to user X.

[0451] 1.2.5.1 Receive user viewing request.

[0452] The system receives a request from user X to view the corresponding set digital work draft after the collaborative creation task is released.

[0453] 1.2.5.2 Generate and execute the setting content block.

[0454] The system generates an execution setting content block corresponding to the task setting information based on the task template of the collaborative creation task and the setting content block generation method included in the task template. Specifically, the system includes the following implementation steps.

[0455] 1.2.5.2.1Step 1: Obtain the task template and task setting information.

[0456] Obtain the task template α(M) and task setting information [TaskSet, A] through the task data block DB{Task_ID(N)}.

[0457] 1.2.5.2.2 Step 2: Obtain a set of initial composition methods for content block clustering.

[0458] The initial composition mode set of content block clustering of the task is obtained through the task template α(M).

[0459] In this embodiment, the initial set of content block cluster composition modes includes one content block cluster overall composition mode and eight first-level content block cluster composition modes.

[0460] 1.2.5.2.3 Step 3: Obtain the setting content block (including the corresponding setting content block generation method).

[0461] The set content blocks are obtained by clustering the initial content blocks.

[0462] In this embodiment, there is a first-level content block clustering method including setting content blocks, which are listed as follows:

[0463] BlockCluster(1), report header, classic content block clustering.

[0464] These include:

[0465] The content block SCBlock (100) is set to correspond to "Task Setting Information Block 1: Enterprise Research Report Number" in the task setting object, and the generation method is copying.

[0466] The content block SCBlock (101) is set to correspond to "Task Setting Information Block 2: Full Name of the Enterprise to be Researched" in the task setting object, and the generation method is copying.

[0467] 1.2.5.2.4 Step 4: Generate execution setting content block.

[0468] Based on the task setting information, the execution setting content block corresponding to the task setting information is generated according to the generation method of each setting content block.

[0469] The task setting information is [TaskSet, A], which includes the following:

[0470] Information block 1 of the task setting object: Enterprise research report number "ERR100068".

[0471] Information block 2 of the task setting object: "Beijing Qisui Technology Co., Ltd."

[0472] The execution of the setting content block SCBlock (100) sets the content information of the setting content block SCBlock {100, [TaskSet, A]}: "ERR100068".

[0473] The execution of the set content block SCBlock (101) sets the content information of the content block SCBlock {101, [TaskSet, A]}: "Beijing Qisui Technology Co., Ltd."

[0474] 1.2.5.3 Generate a content block clustering and set the composition method set.

[0475] According to the execution setting of the content block, the content block cluster initial composition mode set in the task template is updated to the content block cluster setting composition mode set.

[0476] In this embodiment, the set of initial composition modes of content block clusters includes one overall composition mode of content block clusters and eight initial composition modes of first-level content block clusters. Among them, one initial composition mode of first-level content block clusters, BlockCluster (1), includes a setting content block. After the setting content block has an execution setting content block, the initial composition mode of the first-level content block clusters needs to be updated to the setting composition mode of the first-level content block clusters. The remaining seven initial composition modes of the first-level content block clusters remain unchanged.

[0477] The initial composition method of the first-level content block clusters needs to be updated to the set composition method of the first-level content block clusters, which is specifically listed as follows.

[0478] 1.2.5.3.1 The initial composition mode BC(1,M) of the first-level content block cluster is updated to the set composition mode BC(1){1.M,[TaskSet,A]}.

[0479] The first-level content block cluster BlockCluster (1) "report header" is a classic content block cluster, and its initial composition BlockCluster (1, M) is shown in the following Table 11:

[0480] Content block identifier Content block type Content of the content block DCBlock_f(100) Fixed default content block Text: Report Number: SCBlock(100) Set content block Content block object of SCBlock(100) DCBlock_f(101) Fixed default content block Text: Enterprise Research Report SCBlock(101) Set content block Content block object of SCBlock(101)

[0481] Table 11

[0482] After the update, the first-level content block cluster setting composition BlockCluster{1.M,[TaskSet,A]} is shown in the following Table 12:

[0483]

[0484] Table 12

[0485] An example of the content of the fixed default content block DCBlock_f(100) is shown in Table 13 below:

[0486]

[0487] Table 13

[0488] An example of executing the content of the setting content block SCBlock{100,[TaskSet,A]} is shown in Table 14 below:

[0489]

[0490] Table 14

[0491] An example of the content of the fixed default content block DCBlock_f(101) is shown in Table 15 below:

[0492]

[0493] Table 15

[0494] An example of the content of the execution setting content block SCBlock{101,[TaskSet,A]} is shown in Table 16 below:

[0495]

[0496] Table 16

[0497] 1.2.5.4 Generate and set up digital work draft.

[0498] According to the set of clustering composition methods of the set content blocks, the server or user equipment of the system assembles and generates the set digital work draft.

[0499] The digital draft of the "Enterprise Research Report" is assembled by the aforementioned 8 first-level content block clustering setting composition methods according to the overall composition method of the content block clustering.

[0500] 1.2.5.5 Provide feedback on the digital work draft.

[0501] The system server or user device feeds back the set digital work draft to user X.

[0502] 1.3 Carry out collaborative creation: First process task status diagram.

[0503] Step S1: The user obtains the collaborative creation task Task_ID (N) through the user terminal.

[0504] At this point, no subtasks (including subtasks at the next level) have been created by any co-authors for Task_ID(N), meaning there is no creative execution content. Therefore, the task state diagram for Task_ID(N) obtained by the user is the first-stage task state diagram.

[0505] Step S2: The user terminal obtains the creation status of the subtask.

[0506] The user end obtains the creation status of each subtask through the task status diagram.

[0507] Note: Depending on the hierarchy of the subtask system formed after task decomposition, the term "subtask" may also refer to the next-level subtask, the next-level subtask of the next level, and the subtask execution content may also refer to the next-level subtask execution content, the next-level subtask execution content of the next level, and so on. This analogy also applies to the following references to "subtask" and "subtask execution content."

[0508] Step S3: providing the subtasks and next-level subtasks in a creative state to the creator, so that the creator can input creative information based on the relevant information of the subtasks.

[0509] The relevant information of the subtask includes the task setting information and the description information of the subtask.

[0510] Note 1: The process rules of a subtask (and the next-level subtask) can also be considered as part of the subtask description information. That is, it can be considered that the broad subtask description information includes the process rules of the subtask.

[0511] Note 2: In some embodiments, the creator inputs the creation information based on the task setting information and the description information of the subtask.

[0512] In the first process task status diagram, subtask T1 "Company Situation", the next-level subtask (T1.1) "Basic Situation and Historical Evolution", subtask T2 "Industry Analysis", and the next-level subtask (T2.M.1) "Industry Panorama" do not depend on other subtasks, so they are all in the "creatable" state.

[0513] For subtasks in the "creatable" state, relevant creators in the collaborative creation community can select the corresponding subtask, input creation information according to the subtask description information, and then generate the execution content of the subtask.

[0514] In the first process task status diagram, the next-level subtasks (T1.2), (T1.3), (T2.M.2), subtasks T3 to T5 and their own next-level subtasks, and subtask T6 are all subtasks that depend on other subtasks, and therefore are all in the "uncreatable" state.

[0515] For subtasks in the "unauthorizable" state, relevant creators in the collaborative creation community cannot generate execution content for these subtasks.

[0516] In summary, when user a is pushed this task Task_ID(N) as a candidate creator with a high matching degree with (T1.1) "Basic Situation and Historical Evolution", the first process task status diagram of task Task_ID(N) obtained by user a is as follows: Figure 12 shown.

[0517] In summary, when user b is pushed this task Task_ID(N) as a candidate creator with a high matching degree with (T2.M.1) "Industry Panorama", the first process task status diagram of task Task_ID(N) obtained by user b's user terminal is as follows: Figure 13 shown.

[0518] 1.3.1 Data setting of task status diagram.

[0519] After the user equipment generates the task status diagram or the user terminal device receives the first process task status diagram, the user equipment maintains the first process task status diagram in its running memory.

[0520] The node types, node relationships, and node states in the initial task state diagram of the task template can be maintained and operated in the running memory of both the user device and the server device using corresponding data structures.

[0521] 1.3.2 AI user operation of task state diagram.

[0522] In some embodiments, for AI or machine intelligence users, the user device can read, operate, and maintain the task state diagram through the data structure of the task state diagram in its running memory, thereby participating in collaborative creation and following corresponding process rules.

[0523] The user device where the AI user or machine intelligence user is located can be a computing device or computing facility with information processing capabilities such as a computer / server / computing platform, and the embodiments of the present application do not limit this.

[0524] 1.3.3 Interactive interface display of task status diagram.

[0525] In some embodiments, after a task state diagram is generated, the user-side device can not only maintain the task state diagram in its runtime memory using the aforementioned data structure, but also display it in the user-side interactive interface. In other words, the task state diagram can graphically present the creation status, such as node types, node relationships, process rules, and creation information, making it easier for human users to intuitively obtain relevant information.

[0526] 1.3.4 Review the first-stage digital work draft.

[0527] After a collaborative creation task is released, when no subtask has been created by the collaborative creators, the digital work draft corresponding to the task is called the first-process digital work draft.

[0528] According to the user's viewing request, the embodiment of the present application can generate a first-process digital work draft.

[0529] The first step of the collaborative creation task, the digital work draft, is the same as the setting digital work draft.

[0530] 1.4 Example 1: The execution content of the atomic subtask has a ~-belonging content relationship (step S4).

[0531] The next level subtask includes description information of the next level subtask, which is used to provide the creator with input of creation information based on the description information of the next level subtask;

[0532] an ownership relationship between the next-level subtask and the execution content of the subtask, wherein the ownership relationship is used to indicate that the execution content of the subtask owns the next-level subtask;

[0533] And / or, the dependency relationship between the next-level subtasks is used to set the creation status of the next-level subtasks.

[0534] 1.4.1 Enter creation information.

[0535] Step S4.1: Creator a selects subtask T1.1 “Basic Situation and Historical Evolution” and enters creation information.

[0536] Creator a selects subtask T1.1 "Basic Situation and Historical Evolution" and issues a creation request.

[0537] The system pushes the creation content block object of subtask T1.1 "Basic Situation and Historical Evolution" to user a, such as Figure 14 shown.

[0538] User a enters subtask creation information in the creation content block object of subtask T1.1 "Basic Situation and Historical Evolution", such as Figure 15 shown.

[0539] Submit the creation information of each subtask generated by the above-mentioned previous actions. If user a is a human user, by clicking Figure 15 The submit button on the upper right corner triggers this action. If user a is an AI (machine intelligence) user, this action is triggered by program instructions.

[0540] Set the current execution content [T1, [T1.1, a(1)]] and the next-level subtask information of the direct fixed-length frame-type subtask T1 "Company Status".

[0541] In this step, the default execution content [T1.M] of the direct fixed-length frame-type subtask T1 "Company Status" is updated to the creative execution content [T1, [T1.1, a(1)]].

[0542] T1 and its execution content [T1,[T1.1,a(1)]] are described in detail in Table 17 below:

[0543]

[0544] Table 17

[0545] In Table 17, the second-level subtask T1.1 and its execution content [T1.1,a(1)] are described in detail in Table 18 below:

[0546]

[0547] Table 18

[0548] Set the current execution composition mode BC{T1,[T1.1,a(1)]} of the direct fixed-length frame type content block cluster BC(T1) "Company situation".

[0549] At this point, the execution content [T1, [T1.1, a(1)]] corresponds to the execution composition method BC(T1, [T1.1, a(1)]) of the direct fixed-length frame-type content block cluster. The initial composition method BC(T1, M) of the direct fixed-length frame-type content block cluster BC(T1) "Company Information" is updated to the execution composition method BC(T1, [T1.1, a(1)]).

[0550] Among them, BC(T1,[T1.1,a(1)]) consists of the following content chunk clusters:

[0551] Fixed default content block DCBlock_f(T1.head);

[0552] Fixed default content block DCBlock_f (T1.1.head);

[0553] Fixed execution creation content block CCBlock{T1.1.body,[T1.1,a(1)]}

[0554] Fixed default content block DCBlock_f (T1.2.head);

[0555] Fixed creative content block CCBloc (T1.2.body);

[0556] Fixed default content block DCBlock_f (T1.3.head);

[0557] Fixed creative content block CCBloc (T1.3.body).

[0558] The specific description of BC(T1,[T1.1,a(1)]) is shown in Table 19 below:

[0559]

[0560] Table 19

[0561] Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. If user a is a human user, by clicking Figure 15 Click the confirmation button in the upper right corner to trigger this action. If user a is an AI (machine intelligence) user, this action is triggered by program instructions.

[0562] 1.4.2 Generate creation information data block.

[0563] Step S4.2: Receive the creation information of subtask T1.1 from creator a and generate a creation information data block DB{T1,[T1.1,a(1)]} corresponding to the creation information. Including:

[0564] 1) Creation content information, including the various creation information generated in the aforementioned step S4.1, such as:

[0565] ●Execute the content identifier {T1,[T1.1,a(1)]} and its creation information.

[0566] ●Direct fixed-length frame-type content block clustering execution composition method BC(T1,[T1.1,a(1)]) and its creation information.

[0567] 2) Task ID, Task_ID(N).

[0568] 3) Creator identity information, including user a’s user ID and / or user public key.

[0569] 4) The data block identifier of this creation information, DB{T1,[T1.1,a(1)]}.

[0570] Step S4.3: The server or user device generates a digital fingerprint of the creation information data block based on the creation information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creation information data block.

[0571] Step S4.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[0572] Step S4.5: The user device or server generates a creation information data packet DP{Task_ID(N).{T1,[T1.1,a(1)]}}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[0573] Step S4.6: The user device or server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[0574] Step S4.6.1: The user terminal or server may publish the creation information data package to a suitable blockchain and obtain the blockchain access address as the index of the creation information data package for recording rights. Specifically, the following steps may be included:

[0575] The collaborative community selects the appropriate blockchain, public chain, consortium chain or private chain.

[0576] The collaborative community develops and creates information data packages on the blockchain, publishes smart contracts, and deploys them on the blockchain.

[0577] The creator initiates a creative information data package publishing transaction, calls the creator publishing smart contract on the blockchain, publishes the creative information data package to the blockchain, and obtains the corresponding blockchain access address as the creative information data package index for recording rights.

[0578] Step S4.6.2: The user terminal or server can upload the creative information data package to the task library. Through the task library, collaborative creative community users can browse the creative information data package and corresponding tasks as needed. Furthermore, the system can push the creative information data package and corresponding tasks to appropriate collaborative creative community users.

[0579] 1.4.3 Second process task status diagram.

[0580] When a new creative execution content is added to the task Task_ID(N), a new second-process task state diagram can be generated.

[0581] The node types, node relationships, and node states in the task state diagram can be maintained and operated in the running memory of both the user device and the server device using corresponding data structures.

[0582] In some embodiments, for AI or machine intelligence users, the user device or server can perform read and write operations based on the data structure of the task state diagram in its running memory, thereby maintaining the task state diagram, thereby participating in collaborative creation and following corresponding process rules.

[0583] In some embodiments, in addition to operating the task state diagram in its running memory using the corresponding data structure, the user device can also display the task state diagram in the interactive interface of the user device so that human users can intuitively obtain relevant information.

[0584] After step S4 is completed, the second process task status diagram of the collaborative creation task of "Enterprise Research Report" is as follows Figure 16 shown.

[0585] 1.4.4 Review the second-stage digital work draft.

[0586] The information snapshot of the second process task state diagram of this collaborative creation task currently has 1 version. The information snapshot includes T1 and its execution content {T1, [T1.1, a(1)]}. This information snapshot example is as follows Figure 17 shown.

[0587] The information snapshot includes the execution content {T1,[T1.1,a(1)]}.

[0588] {T1,[T1.1,a(1)]} corresponds to the current execution composition mode BC(T1,[T1.1,a(1)]) of the direct fixed-length frame-type content block cluster BC(T1) "Company situation".

[0589] According to the information snapshot and the current content block cluster composition mode set (the second process content block cluster composition mode set), the current execution composition mode BC(T1,[T1.1,a(1)]) and the current composition modes of other content block clusters in the Task_ID(N) overall content block cluster composition mode are assembled to generate a composite digital work.

[0590] As collaborative creation progresses, all the atomic subtasks of T4 "Profit Forecast and Investment Advice" have execution content. T5 "Risk Warning" enters the creation state, and the task status diagram is as follows: Figure 18 shown.

[0591] 1.5 Example 2: The execution content of the atomic subtask has a ~-belonging content relationship (step S5).

[0592] 1.5.1 Enter creation information.

[0593] Step S5.1: Creator b selects subtask T5.n “Risk Warning n” and enters creation information.

[0594] 1) Creator b selects subtask T5.n “Risk Warning n” and issues a creation request.

[0595] 2) The system pushes the creation content block object of subtask T5.n to user b, such as Figure 19 shown.

[0596] 3) User b enters subtask creation information in the creation content block object of subtask T5.n “Risk Warning n”, such as Figure 20 shown.

[0597] 4) Submit the creation information of each subtask generated by the above-mentioned previous actions. If user b is a human user, by clicking Figure 20 The submit button on the upper right corner triggers this action. If user b is an AI (machine intelligence) user, this action is triggered by program instructions.

[0598] 5) After the system receives the subtask creation information submitted by user b, it puts the received subtask creation information into the next-level subtask queue of subtask T5 "Risk Warning".

[0599] 6) The system determines that the received subtask creation information is ranked 1 in the next-level subtask queue of subtask T5 "Risk Warning", and then determines that n=1 in T5.n "Risk Warning n".

[0600] 7) Set the execution content of the direct indefinite-length frame-type subtask T5 and the next-level subtask information.

[0601] At this time, the execution content of subtask T5 [T5, [T5.1, b(1)]] (n=1) has two second-level subtasks T5.1 and T5.n. Subtask T5.1 has the execution content [T5.1, b(1)].

[0602] The subtask T5 and its execution content [T5, [T5.1, b(1)]] (n=1) are described in detail in Table 20 below:

[0603]

[0604] Table 20

[0605] 8) Set the current execution composition mode BC{T5,[T5.1,b(1)]}(n=1) of the direct indefinite-length frame-type content block cluster BC(T5) “risk warning”.

[0606] At this point, the execution content of subtask T5 [T5, [T5.1, b(1)]] (n=1) corresponds to the content block cluster execution composition method BC{T5, [T5.1, b(1)]} (n=1). The initial composition method BC(T5, M) (n=0) of the direct variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated to the execution composition method BC(T5, [T5.1, b(1)]) (n=1).

[0607] Among them, BC{T5,[T5.1,b(1)]}(n=1) consists of the following content chunk clusters:

[0608] Fixed default content block DCBlock_f (T5.head);

[0609] Undefined execution creation content block header CCBlock_u(T5.1.head,

[0610] [T5.1.head,b(1)]);

[0611] Undefined execution creation content block body CCBlock_u(T5.1.body,

[0612] [T5.1.body,b(1)]);

[0613] Undefined creative content block header CCBlock_u (T5.n.head);

[0614] Undefined creative content block body CCBlock_u (T5.n.body).

[0615] The specific description of BC{T5,[T5.1,b(1)]}(n=1) is shown in Table 21 below:

[0616]

[0617] Table 21

[0618] 9) Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. If user b is a human user, by clicking Figure 20 Click the confirmation button in the upper right corner to trigger this action. If user b is an AI (machine intelligence) user, this action is triggered by program instructions.

[0619] 1.5.2 Generate creation information data block.

[0620] Step S5.2: Receive the creation information of subtask T5.n from creator b, and generate a creation information data block DB[T5,[T5.1,b(1)]](n=1) corresponding to the creation information. This includes:

[0621] 1) Creation content information, including the various creation information generated in the aforementioned step S5.1, such as:

[0622] ●Execute content identification [T5, [T5.1, b(1)]] (n=1) and its creation information.

[0623] ●Direct indefinite-length frame-type content block clustering execution composition method BC(T5,[T5.1,b(1)])(n=1) and its creation information.

[0624] 2) Task ID, Task_ID(N).

[0625] 3) Creator identity information, including user b’s user ID and / or user public key.

[0626] 4) The data block identifier of this creation information is DB[T5,[T5.1,b(1)]](n=1).

[0627] Step S5.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[0628] Step S5.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[0629] Step S5.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,[T5.1,b(1)]](n=1)}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[0630] Step S5.6: The user device or the server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[0631] The specific content of this step S5.6 is the same as that of the above step S4.6 and will not be repeated here.

[0632] 1.5.3 Second process task status diagram.

[0633] When a new creative execution content is added to the task Task_ID(N), a new second-process task state diagram can be generated.

[0634] In some embodiments, in addition to using the corresponding data structure to operate the task status diagram in its running memory, the user device can also display the task status diagram in the interactive interface of the user device so that human users other than machine intelligence users can intuitively obtain relevant information.

[0635] After step S5 is completed, the second process task status diagram of the collaborative creation task of "Enterprise Research Report" is as follows Figure 21 As shown, it includes the indefinite first-level subtask “T5.n Risk Warning n” and its generated second-level subtask “T5.1 Risk Warning 1”. Among them, the second-level subtask “T5.1 Risk Warning 1” has the execution content [T5, 1, b(1)].

[0636] 1.5.4 Review the second-stage digital work draft.

[0637] The information snapshot of the second process task state diagram of this collaborative creation task currently has one version. The information snapshot includes the execution content of the next-level subtasks T1 to T4, as well as T5 and its execution content [T5, [T5.1, b(1)]] (n = 1). This information snapshot is an example of Figure 22 shown.

[0638] The information snapshot includes the execution content [T5, [T5.1, b(1)]] (n=1).

[0639] [T5, [T5.1, b(1)]] (n = 1) corresponds to the current execution composition mode BC(T5, [T5.1, b(1)]) (n = 1) of the direct indefinite-length frame-type content block cluster BC(T5) "Risk Warning".

[0640] The digital work corresponding to BC(T5,[T5.1,b(1)])(n=1) is as follows Figure 23 shown.

[0641] According to the information snapshot and the current content block cluster composition mode set (the second process content block cluster composition mode set), the current execution composition mode BC(T5,[T5.1,b(1)])(n=1) and other current content block cluster composition modes in the Task_ID(N) overall content block cluster composition mode are assembled to generate a composite digital work. An example of some contents of the composite digital work is as follows: Figure 24 shown.

[0642] 1.6 Example 3: The execution content of the atomic subtask has a ~-belonging content relationship (step S6).

[0643] 1.6.1 Enter creation information.

[0644] Step S6.1: Creator c selects subtask T5.n “Risk Warning n” and enters creation information.

[0645] 1) Creator c selects subtask T5.n “Risk Warning n” and issues a creation request.

[0646] 2) The system pushes the creation content block object of subtask T5.n to user c, such as Figure 19 shown.

[0647] 3) User c enters subtask creation information in the creation content block object of subtask T5.n “Risk Warning n”, such as Figure 20 shown.

[0648] 4) Submit the creation information of each subtask generated by the above-mentioned previous actions. If user c is a human user, by clicking Figure 20 The submit button on the upper right corner triggers this action. If user c is an AI (machine intelligence) user, this action is triggered by program instructions.

[0649] 5) After the system receives the subtask creation information submitted by user c, it puts the received subtask creation information into the subtask queue of subtask T5.n "Risk Warning n".

[0650] 6) The system determines that the received subtask creation information is ranked 2 in the next-level subtask queue of subtask T5 "Risk Warning", and then determines that n=2 in T5.n "Risk Warning n".

[0651] 7) Set the execution content of the direct indefinite-length frame-type subtask T5 and the next-level subtask information.

[0652] At this time, the execution content of subtask T5 [T5, [T5.1, b(1)] [T5.2, c(1)]] (n=2) has three second-level subtasks T5.1, T5.2, and T5.n. Subtask T5.1 has the execution content [T5.1, b(1)], and subtask T5.2 has the execution content [T5.2, c(1)].

[0653] Subtask T5 and its execution content [T5, [T5.1, b(1)] [T5.2, c(1)]] (n=2) are described in detail in Table 22 below:

[0654]

[0655]

[0656] Table 22

[0657] 8) Set the current execution composition mode BC[T5,[T5.1,b(1)][T5.2,c(1)]](n=2) of the direct indefinite-length frame-type content block cluster BC(T5) “risk warning”.

[0658] At this time, the execution content of subtask T5 [T5, [T5.1, b(1)][T5.2, c(1)]] (n=2) corresponds to the content block cluster execution composition method BC[T5, [T5.1, b(1)][T5.2, c(1)]] (n=2). The original execution composition method BC(T5, [T5.1, b(1)]) (n=1) of the direct variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated to the current execution composition method BC[T5, [T5.1, b(1)][T5.2, c(1)]] (n=2).

[0659] Among them, BC[T5,[T5.1,b(1)][T5.2,c(1)]] (n=2) consists of the following content chunk clusters:

[0660] Fixed default content block DCBlock_f (T5.head);

[0661] Undefined execution creation content block header CCBlock_u(T5.1.head,

[0662] [T5.1.head,b(1)]);

[0663] Undefined execution creation content block body CCBlock_u(T5.1.body,

[0664] [T5.1.body,b(1)]);

[0665] Undefined execution creation content block header CCBlock_u(T5.2.head,

[0666] [T5.2.head,c(1)]);

[0667] Undefined execution creation content block body CCBlock_u(T5.2.body,

[0668] [T5.2.body,c(1)]);

[0669] Undefined creative content block header CCBlock_u (T5.n.head);

[0670] Undefined creative content block body CCBlock_u (T5.n.body).

[0671] The specific description of BC[T5,[T5.1,b(1)][T5.2,c(1)]](n=2) is shown in Table 23 below:

[0672]

[0673]

[0674] Table 23

[0675] 9) Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. If user c is a human user, by clicking Figure 20 Click the confirmation button in the upper right corner to trigger this action. If user c is an AI (machine intelligence) user, this action is triggered by program instructions.

[0676] 1.6.2 Generate creation information data block.

[0677] Step S6.2: Receive the creation information of the subtask T5.n from the creator c, and generate a creation information data block DB[T5,[T5.1,b(1)][T5.2,c(1)]](n=2) corresponding to the creation information. This includes:

[0678] 1) Creation content information, including the various creation information generated in the aforementioned step S6.1, such as:

[0679] ●Execute content identification [T5, [T5.1, b(1)] [T5.2, c(1)]] (n=2) and its creation information.

[0680] ●Direct indefinite-length frame-type content block clustering execution composition method BC[T5,[T5.1,b(1)][T5.2,c(1)]](n=2) and its creation information.

[0681] 2) Task ID, Task_ID(N).

[0682] 3) Creator identity information, including user ID and / or user public key of user c.

[0683] 4) The data block identifier of this creation information is DB[T5,[T5.1,b(1)][T5.2,c(1)]](n=2).

[0684] Step S6.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[0685] Step S6.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[0686] Step S6.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,[T5.1,b(1)][T5.2,c(1)]](n=2)}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[0687] Step S6.6: The user device or server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[0688] The specific content of this step S6.6 is the same as that of the above step S4.6 and will not be repeated here.

[0689] 1.6.3 Second process task status diagram.

[0690] When a new creative execution content is added to the task Task_ID(N), a new second-process task state diagram can be generated.

[0691] In some embodiments, in addition to using the corresponding data structure to operate the task status diagram in its running memory, the user device can also display the task status diagram in the interactive interface of the user device so that human users other than machine intelligence users can intuitively obtain relevant information.

[0692] After step S6 is completed, the second process task status diagram of the collaborative creation task of "Enterprise Research Report" is as follows Figure 25 As shown, Figure 21 In comparison, this time it also includes the second lower-level subtask "T5.2 Risk Warning 2" and its execution content [T5,2,c(1)].

[0693] 1.6.4 Review the second-stage digital work draft.

[0694] The information snapshot of the second process task state diagram of this collaborative creation task currently has one version. The information snapshot includes the execution content of the next-level subtasks T1 to T4, as well as T5 and its execution content [T5, [T5.1, b(1)] [T5.2, c(1)]] (n=2). This information snapshot is an example of Figure 26 shown.

[0695] The information snapshot includes the execution content [T5, [T5.1, b(1)] [T5.2, c(1)]] (n=2).

[0696] [T5,[T5.1,b(1)][T5.2,c(1)]](n=2) corresponds to the current execution composition mode BC[T5,[T5.1,b(1)][T5.2,c(1)]](n=2) of the direct indefinite-length frame-type content block cluster BC(T5) "Risk Warning".

[0697] The digital works corresponding to BC[T5,[T5.1,b(1)][T5.2,c(1)]](n=2) are as follows Figure 27 shown.

[0698] According to the information snapshot and the current content block cluster composition mode set (the second process content block cluster composition mode set), the current content block cluster execution composition mode BC[T5,[T5.1,b(1)][T5.2,c(1)]](n=2) and other content block cluster current composition modes in the Task_ID(N) overall content block cluster composition mode are assembled to generate a composite digital work. In summary, some content examples of the composite digital work are as follows: Figure 28 shown.

[0699] It should be noted that the explanations and examples of some technical features in Example 1 are similarly applicable to other embodiments and will not be repeated hereafter.

[0700] Example 2:

[0701] The next-level subtask of an indirect indefinite-length frame-type subtask can be an atomic subtask or a frame-type subtask.

[0702] This embodiment takes the enterprise research report and the second implementation method (corresponding to the indirect variable-length framework-type subtask) as an example to introduce a collaborative creation method for digital works that can add atomic next-level subtasks as needed.

[0703] 2.1 Develop and publish collaborative creation task templates.

[0704] Step M.1: The task template creator M inputs the creation information of the task template α(m).

[0705] 2.1.1 Set the template description information.

[0706] 2.1.2 Set the task setting object.

[0707] 2.1.3 Set up the initial task state diagram.

[0708] The contents of 2.1.1 to 2.1.3 above are the same as those described in 1.1.1 to 1.1.3 above and will not be repeated here.

[0709] 2.1.3.1 Set subtasks and node relationships.

[0710] The node relationships between the nodes in the initial task state diagram may include ownership-attribution relationships and derived-dependency relationships.

[0711] According to the requirements of collaborative creation task decomposition and process management, in the initial task status diagram developed by template developer M for the "Enterprise Research Report" task template, an example of the node relationship setting (initial subtask system) of each node is shown in Table 24 below.

[0712]

[0713] Table 24

[0714] Note 1: The next-level subtask of an indirect indefinite-length frame-type subtask is an indefinite next-level subtask.

[0715] Note 2: For indirect indefinite-length frame-type subtasks, there is no next-level subtask in the task template.

[0716] 2.1.3.2 AI User Operations in Task State Diagram.

[0717] 2.1.3.3Task status diagram overview version.

[0718] 2.1.3.4 Partially expanded version of the task status diagram.

[0719] The contents of 2.1.3.2 to 2.1.3.4 above are the same as 1.1.3.2 to 1.1.3.4, except that after T5 "Risk Warning" is expanded, there is no execution content and no next-level subtasks.

[0720] 2.1.4 Develop a content block clustering system.

[0721] 2.1.4.1 Overall content block clustering composition method.

[0722] Based on the collaborative creation task's requirement to assemble the content of each subtask into a digital work, the template developer M developed an example of the overall content block clustering composition for the "Enterprise Research Report" task template as shown in Table 25 below:

[0723]

[0724] Table 25

[0725] in:

[0726] BlockCluster (1) "report header", BlockCluster (T6) "report highlights", and BlockCluster (2) "report footer" are classic content block clusters.

[0727] BlockCluster (T1) "Company Profile" to BlockCluster (T4) "Profit Forecast and Investment Advice" are fixed-length framework-type content block clusters.

[0728] BlockCluster (T5) "Risk Warning" is an indirect indefinite-length frame-type content block cluster.

[0729] In this embodiment, the digital work of "Enterprise Research Report" is generated by assembling eight first-level content block clusters according to the "overall content block clustering method" described above. The "Enterprise Research Report" task template also includes the above eight first-level content block clustering method, as shown below (Template Maker M Responsibility 3).

[0730] 2.1.4.2 The initial composition of the first-level content block cluster BC(1) “report header” is BC(1,M).

[0731] 2.1.4.3 The initial composition of the first-level content block cluster BC(T6) “Report highlights” BC(T6,M).

[0732] 2.1.4.4 The initial composition of the first-level content block cluster BC(T1) “Company situation” is BC(T1,M).

[0733] 2.1.4.5 The initial composition of the first-level content block cluster BC(T2) “Industry Analysis” is BC(T2,M).

[0734] The contents of 2.1.4.2 to 2.1.4.5 above are the same as those of 1.1.4.2 to 1.1.4.5 and will not be repeated here.

[0735] 2.1.4.6 The initial composition of the first-level content block cluster BC(T5) “Risk Warning” is BC(T5,M).

[0736] The template creator M creates the initial composition BlockCluster(T5,M) for the indirect variable-length frame-type content block cluster "Risk Tip" of BlockCluster(T5), which has DCBlock_f(T5.head) and BC(T5.body). The specific description is shown in Table 26 below:

[0737]

[0738] Table 26

[0739] 2.1.5 Develop reference creation information.

[0740] 2.1.6 Generate task template data block.

[0741] 2.1.7 Release the task template data package.

[0742] 2.1.8 Review the initial digital draft.

[0743] The contents of 2.1.5 to 2.1.8 above are the same as those of 1.1.5 to 1.1.8 and will not be repeated here.

[0744] 2.2 Set and publish collaborative creation tasks.

[0745] The above 2.2 content is the same as 1.2 content and will not be repeated here.

[0746] 2.3 Carry out collaborative creation: first process task status diagram.

[0747] 2.4 Example 1: The execution content of the atomic subtask has a ~-belonging content relationship (step S4).

[0748] The above contents of 2.3 to 2.4 are the same as those of 1.3 to 1.4 and will not be repeated here.

[0749] 2.5 Example 2: The execution content of the framework-type subtask has a ~-belonging content relationship (step S5).

[0750] 2.5.1 Enter creation information.

[0751] Step S5.1: Creator d selects subtask T5 “Risk Warning” and enters creation information.

[0752] 1) Creator d selects subtask T5 “Risk Warning” and issues a creation request.

[0753] 2) The system pushes the creation content block object of subtask T5 to user d, such as Figure 29 shown.

[0754] 3) User d enters subtask creation information in the creation content block object of the framework subtask T5 “Risk Warning”, such as Figure 30 shown.

[0755] 4) Submit the creation information of each subtask generated by the above-mentioned previous actions. For human users, user d clicks Figure 30 Click the Submit button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[0756] 5) Set the execution content of the indirect variable-length frame-type subtask T5 and the next-level subtask information, as shown in Table 27 below.

[0757]

[0758] Table 27

[0759] Rule description 1: The execution content of an indirect indefinite-length frame-type subtask has an indefinite next-level subtask.

[0760] Rule 2: For indirect, indefinite-length frame-type subtask execution content, the indefinite-length subtasks it possesses include a length variable n. When the execution content is published, the initial value of the length variable n is n = 0. After the execution content is published, during the authoring process, if the execution content has one new subtask, n = 1. If the execution content has two new subtasks, n = 2. And so on.

[0761] 6) Set the current execution composition mode BC{T5,[T5,d(1)]}(n=0) of the indirect variable-length frame-type content block cluster BC(T5) "risk warning".

[0762] The initial composition mode BC(T5,M) of the indirect variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated to the execution composition mode BC(T5,[T5,d(1)])(n=0).

[0763] Currently, BC(T5,[T5,d(1)])(n=0) consists of the following content chunk clusters:

[0764] Fixed default content block DCBlock_f (T5.head);

[0765] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,d(1)]}(n=0).

[0766] BC{T5.body,[T5,d(1)]}(n=0) consists of the following content chunks:

[0767] Undefined default content block DCBlock_u(T5.d(1).0);

[0768] Undefined creative content block CCBlock_u(T5.d(1).n).

[0769] CCBlock_u{T5.d(1).n]} consists of the following content block clusters:

[0770] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0771] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0772] In summary, the indirect variable-length frame-type content block cluster BC(T5) "Risk Prompt" execution composition method BC(T5,[T5,d(1)])(n=0) includes DCBlock_f(T5.head), DCBlock_u(T5.d(1).0), CCBlock_u(T5.d(1).n.head), and CCBlock_u(T5.d(1).n.body), as shown in Table 28 below:

[0773]

[0774]

[0775] Table 28

[0776] Rule Description 1: When the execution content [T5, d(1)] is released, n=0, and [T5, d(1)] does not have a new second-level subtask.

[0777] At this time, the execution content [T5, d(1)] corresponds to the indirect variable-length frame-type content block cluster execution composition mode BC{T5, [T5, d(1)]} (n=0).

[0778] Among them, BC(T5,[T5,d(1)])(n=0) consists of the following content chunk clusters:

[0779] Fixed default content block DCBlock_f (T5.head);

[0780] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,d(1)]}(n=0).

[0781] BC{T5.body,[T5,d(1)]}(n=0) consists of the following content chunks:

[0782] Undefined default content block DCBlock_u(T5.d(1).0);

[0783] Undefined creative content block CCBlock_u(T5.d(1).n).

[0784] CCBlock_u{T5.d(1).n]} consists of the following content block clusters:

[0785] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0786] Undefined creation content block body CCBlock_u (T5.h(1).n.body).

[0787] In summary, BC(T5,[T5,d(1)])(n=0) consists of the following content chunks:

[0788] Fixed default content block DCBlock_f (T5.head);

[0789] Undefined default content block DCBlock_u(T5.d(1).0);

[0790] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0791] Undefined creation content block body CCBlock_u (T5.h(1).n.body).

[0792] Rule Description 2: When the execution content [T5, d(1)] has a new second-level subtask, n = 1. The new second-level subtask is T5.d(1).1, and the execution content owned by T5.d(1).1 is [T5.d(1).1, x1(1)], where x1 refers to the user who created the execution content of T5.d(1).1.

[0793] At this time, the execution content [T5, d(1)] (n=1, [T5.d(1).1, x1(1)]) corresponds to the indirect variable-length frame-type content block cluster execution composition method BC{T5, [T5, d(1)]} (n=1, [T5.d(1).1, x1(1)]).

[0794] Among them, BC(T5,[T5,d(1)])(n=1,[T5.d(1).1,x1(1)]) consists of the following content chunk clusters:

[0795] Fixed default content block DCBlock_f (T5.head).

[0796] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,d(1)]}(n=1,[T5.d(1).1,x1(1)]).

[0797] BC{T5.body,[T5,d(1)]}(n=1,[T5.d(1).1,x1(1)]) consists of the following content chunks:

[0798] Undefined execution creation content block CCBlock_u(T5.d(1).1,[T5.d(1).1,x1(1)]);

[0799] Undefined creative content block CCBlock_u(T5.d(1).n).

[0800] CCBlock_u(T5.d(1).1,[T5.d(1).1,x1(1)]) consists of the following content block clusters:

[0801] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,x1(1)]};

[0802] The undefined execution creates the content block body CCBlock_u(T5.h(1).1.body,[T5.d(1).1,x1(1)]).

[0803] CCBlock_u{T5.d(1).n]} consists of the following content block clusters:

[0804] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0805] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0806] In summary, BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,x1(1)]) consists of the following content chunks:

[0807] Fixed default content block DCBlock_f (T5.head);

[0808] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,x1(1)]};

[0809] The undefined execution creates the content block body CCBlock_u(T5.d(1).1.body,[T5.d(1).1,x1(1)]).

[0810] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0811] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0812] Rule Description 3: When the execution content [T5, d(1)] has two new second-level subtasks, n = 2. The new second-level subtasks are T5.d(1).1 and T5.d(1).2. The execution content owned by T5.d(1).1 is [T5.d(1).1, x1(1)], and the execution content owned by T5.d(1).2 is [T5.d(1).2, x2(1)]. Where x2 is the user who created the execution content for T5.d(1).2.

[0813] At this time, the execution content [T5,d(1)](n=2,[T5.d(1).1,x1(1)][T5.d(1).2,x2(1)]) corresponds to the execution composition BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,x1(1)][T5.d(1).2,x2(1)]) of the indirect variable-length frame-type content block cluster BC(T5) "Risk Warning".

[0814] Among them, BC(T5,[T5,d(1)])(n=2(n=2,[T5.d(1).1,x1(1)][T5.d(1).2,x2(1)])) consists of the following content chunk clusters:

[0815] Fixed default content block DCBlock_f (T5.head);

[0816] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,d(1)]}(n=2(n=2,[T5.d(1).1,x1(1)][T5.d(1).2,x2(1)])).

[0817] BC{T5.body,[T5,d(1)]}(n=2(n=2,[T5.d(1).1,x1(1)][T5.d(1).2,x2(1)])) consists of the following content chunks:

[0818] Undefined execution creation content block CCBlock_u(T5.d(1).1,[T5.d(1).1,x1(1)]);

[0819] The undefined execution creates the content block CCBlock_u(T5.d(1).2, [T5.d(1).2, x2(1)]).

[0820] Undefined creative content block CCBlock_u(T5.d(1).n).

[0821] CCBlock_u(T5.d(1).1,[T5.d(1).1,x1(1)]) consists of the following content block clusters:

[0822] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,x1(1)]};

[0823] The undefined execution creates the content block body CCBlock_u(T5.d(1).1.body,[T5.d(1).1,x1(1)]).

[0824] CCBlock_u(T5.d(1).2,[T5.d(1).2,x2(1)]) consists of the following content block clusters:

[0825] Undefined execution creation content block header part CCBlock_u{T5.d(1).2.head,[T5.d(1).2,x2(1)]};

[0826] The undefined execution creates the content block body CCBlock_u(T5.d(1).2.body,[T5.d(1).2,x2(1)]).

[0827] CCBlock_u{T5.d(1).n]} consists of the following content block clusters:

[0828] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0829] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0830] In summary, BC{T5,[T5,d(1)]}(n=2(n=2,[T5.d(1).1,x1(1)][T5.d(1).2,x2(1)])) consists of the following content chunks:

[0831] Fixed default content block DCBlock_f (T5.head);

[0832] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,x1(1)]};

[0833] The undefined execution creates the content block body CCBlock_u(T5.d(1).1.body,[T5.d(1).1,x1(1)]).

[0834] Undefined execution creation content block header part CCBlock_u{T5.d(1).2.head,[T5.d(1).2,x2(1)]};

[0835] The undefined execution creates the content block body CCBlock_u(T5.d(1).2.body,[T5.d(1).2,x2(1)]).

[0836] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0837] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0838] And so on.

[0839] Rule Description 4: When the execution content [T5, d(1)] has N new second-level subtasks, n = N (N>0). The new second-level subtasks are T5.d(1).1, ..., T5.d(1).N. The execution content owned by T5.d(1).1 is [T5.d(1).1, x1(1)], ..., and the execution content owned by T5.d(1).N is [T5.d(1).N, xN(1)]. Where xN is the user who created the execution content for T5.d(1).N.

[0840] At this time, the execution content [T5,d(1)](n=N,[T5.d(1).1,x1(1)]...[T5.d(1).N,xN(1)]) corresponds to the execution composition method BC{T5,[T5,d(1)]}(n=N,[T5.d(1).1,x1(1)]...[T5.d(1).N,xN(1)]) of the indirect indefinite-length frame-type content block cluster BC(T5) "Risk Warning".

[0841] Among them, BC(T5,[T5,d(1)])(n=N,[T5.d(1).1,x1(1)]...[T5.d(1).N,xN(1)]) consists of the following content block clusters:

[0842] Fixed default content block DCBlock_f (T5.head);

[0843] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,d(1)]}(n=N,[T5.d(1).1,x1(1)]...[T5.d(1).N,xN(1)]).

[0844] BC{T5.body,[T5,d(1)]}(n=N,[T5.d(1).1,x1(1)]...[T5.d(1).N,xN(1)]) consists of the following content chunks:

[0845] Undefined execution creation content block CCBlock_u(T5.d(1).1,[T5.d(1).1,x1(1)]);

[0846] ......

[0847] The undefined execution creates the content block CCBlock_u(T5.d(1).N, [T5.d(1).N, xN(1)]).

[0848] Undefined creative content block CCBlock_u(T5.d(1).n).

[0849] CCBlock_u(T5.d(1).1,[T5.d(1).1,x1(1)]) consists of the following content block clusters:

[0850] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,x1(1)]};

[0851] The undefined execution creates the content block body CCBlock_u(T5.d(1).1.body,[T5.d(1).1,x1(1)]). ......

[0853] CCBlock_u(T5.d(1).N,[T5.d(1).N,xN(1)]) consists of the following content block clusters:

[0854] Undefined execution creation content block header part CCBlock_u{T5.d(1).N.head,[T5.d(1).N,xN(1)]};

[0855] The undefined execution creates the content block body CCBlock_u(T5.d(1).N.body,[T5.d(1).N,xN(1)]).

[0856] CCBlock_u{T5.d(1).n]} consists of the following content block clusters:

[0857] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0858] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0859] In summary, BC{T5,[T5,d(1)]}(n=N,[T5.d(1).1,x1(1)]...[T5.d(1).N,xN(1)]) consists of the following content chunks:

[0860] Fixed default content block DCBlock_f (T5.head);

[0861] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,x1(1)]};

[0862] The undefined execution creates the content block body CCBlock_u(T5.d(1).1.body,[T5.d(1).1,x1(1)]).

[0863] ......

[0864] Undefined execution creation content block header part CCBlock_u{T5.d(1).N.head,[T5.d(1).N,xN(1)]};

[0865] The undefined execution creates the content block body CCBlock_u(T5.d(1).N.body,[T5.d(1).N,xN(1)]).

[0866] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0867] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0868] Rule Description 5: Unformed creative content blocks are divided into two types: title part and main body part. The title part of an unformed creative content block provides a title function for the main body part of an unformed creative content block. The main body part of an unformed creative content block provides main content for the title part of an unformed creative content block. The main body part of an unformed creative content block can be associated with the title part of an unformed creative content block, and the two correspond to the same next-level subtask. The next-level subtask belongs to the creative execution content of the framework-type subtask. In addition, the main body part of an unformed creative content block can also exist independently without being associated with the title part.

[0869] 7) Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. For human users, user d clicks Figure 30 Click the confirmation button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[0870] 2.5.2 Generate creation information data block.

[0871] Step S5.2: Receive the creation information of the subtask T5 from the creator d, and generate a creation information data block DB[T5,d(1)](n=0) corresponding to the creation information. This includes:

[0872] 1) Creation content information, including the various creation information generated in the aforementioned step S5.1, such as:

[0873] ●Execute content identification [T5, d(1)] (n=0) and its creation information.

[0874] ●Content block clustering execution composition mode BC(T5,[T5,d(1)])(n=0) and its creation information.

[0875] 2) Task ID, Task_ID(N).

[0876] 3) Creator identity information, including user ID and / or user public key of user d.

[0877] 4) The data block identifier of this creation information, DB[T5,d(1)](n=0).

[0878] Step S5.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[0879] Step S5.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[0880] Step S5.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,d(1)](n=0)}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[0881] Step S5.6: The user device or the server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[0882] The specific content of this step S5.6 is the same as that of the above step S4.6 and will not be repeated here.

[0883] 2.5.3 Second process task status diagram.

[0884] After step S5 is completed, the second process task status diagram of the collaborative creation task of "Enterprise Research Report" is as follows Figure 31 shown.

[0885] 2.5.4 Review the second-stage digital work draft.

[0886] The information snapshot of the second process task state diagram of this collaborative creation task currently has 1 version. The information snapshot includes the execution content of the next-level subtasks T1 to T4, and the execution content of T5 [T5, d (1)] (n = 0). This information snapshot is an example of Figure 32 shown.

[0887] The information snapshot includes execution content [T5, d(1)] (n=0).

[0888] [T5, d(1)](n=0) corresponds to the execution composition mode BC(T5, [T5, d(1)])(n=0) of the content block cluster BC(T5) “risk warning”.

[0889] Examples of digital works corresponding to BC(T5,[T5,d(1)])(n=0) are as follows Figure 33 shown.

[0890] According to the information snapshot and the current content block cluster composition mode set (the second process content block cluster composition mode set), the current composition mode BC(T5,[T5,d(1)])(n=0) and other current content block cluster composition modes in the Task_ID(N) overall content block cluster composition mode are assembled to generate a composite digital work. In summary, some content examples of the composite digital work are as follows: Figure 34 shown.

[0891] 2.6 Example 3: The execution content of the atomic subtask has a ~-belonging content relationship (step S6).

[0892] 2.6.1 Enter creation information.

[0893] Step S6.1: Creator e selects subtask T5.d(1).n "Risk Warning n" and enters creation information. Creator e enters creation information based on the description of subtask T5.d(1).n, the task template, task setting information, descriptions of previous subtasks and parent subtasks, and their execution contents, etc.

[0894] 1) Creator e selects subtask T5.d(1).n “Risk Warning n” and issues a creation request.

[0895] 2) The system pushes the creation content block object of subtask T5.d(1).n to user e, such as Figure 35 shown.

[0896] 3) User e enters subtask creation information in the creation content block object of subtask T5.d(1).n “Risk Warning n”, such as Figure 36 shown.

[0897] 4) Submit the creation information of each subtask generated by the above-mentioned previous actions. For human users, user e clicks Figure 36 Click the Submit button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[0898] 5) After the system receives the subtask creation information submitted by user e, it puts the received subtask creation information into the subtask queue of subtask T5.d(1).n "Risk Warning n".

[0899] 6) The system determines that the received subtask is ranked 1 in the subtask queue of subtask T5.d(1).n "Risk Warning n", and then determines that n=1 in T5.d(1).n "Risk Warning n".

[0900] 7) Set the execution content of the indirect variable-length frame-type subtask T5 and the next-level subtask information.

[0901] At this time, the execution content of subtask T5 [T5, d(1)] (n=1, [T5.d(1).1, e(1)]) has two second-level subtasks T5.d(1).1 and T5.d(1).n. Subtask T5.d(1).1 has the execution content [T5.d(1).1, e(1)].

[0902] The specific description of subtask T5 and its execution content [T5,d(1)] (n=1, [T5.d(1).1,e(1)]) is shown in Table 29 below.

[0903]

[0904] Table 29

[0905] 8) Set the current execution composition mode BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) of the indirect variable-length frame-type content block cluster BC(T5) "Risk Prompt".

[0906] At this time, the execution content [T5, d(1)] (n=1, [T5.d(1).1, e(1)]) corresponds to the indirect variable-length frame-type content block cluster execution composition method BC{T5, [T5, d(1)]} (n=1, [T5.d(1).1, e(1)]). The execution composition method of the indirect variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated from BC(T5, [T5, d(1)]) (n=0) to BC(T5, [T5, d(1)]) (n=1, [T5.d(1).1, e(1)]).

[0907] Among them, BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) consists of the following content chunk clusters:

[0908] Fixed default content block DCBlock_f (T5.head);

[0909] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]).

[0910] BC{T5.body,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) consists of the following content chunks:

[0911] Undefined execution creation content block CCBlock_u(T5.d(1).1,[T5.d(1).1,e(1)]);

[0912] Undefined creative content block CCBlock_u(T5.d(1).n).

[0913] CCBlock_u(T5.d(1).1,[T5.d(1).1,e(1)]) consists of the following content block clusters:

[0914] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,e(1)]};

[0915] The undefined execution creates the content block body CCBlock_u (T5.d(1).1.body, [T5.d(1).1, e(1)]).

[0916] CCBlock_u{T5.d(1).n]} consists of the following content block clusters:

[0917] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0918] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0919] In summary, BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) consists of the following content chunks:

[0920] Fixed default content block DCBlock_f (T5.head);

[0921] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,e(1)]};

[0922] Undefined execution creation content block body CCBlock_u(T5.d(1).1.body,[T5.d(1).1,e(1)]);

[0923] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0924] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0925] The specific description of BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) is shown in Table 30 below.

[0926]

[0927] Table 30

[0928] 9) Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. If user e is a human user, by clicking Figure 36 Click the confirmation button in the upper right corner to trigger this action. If user e is an AI (machine intelligence) user, this action is triggered by program instructions.

[0929] 2.6.2 Generate creation information data block.

[0930] Step S6.2: Receive the creation information of the subtask T5.d(1).n from the creator e, and generate the creation information data block DB[T5,d(1)](n=1,[T5.d(1).1,e(1)]), including:

[0931] 1) Creation content information, including the various creation information generated in the aforementioned step S6.1, such as:

[0932] ●Execute content identification [T5,d(1)](n=1,[T5.d(1).1,e(1)]) and its creation information.

[0933] ●Content block clustering execution composition method BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)])

[0934] and its creation information.

[0935] 2) Task ID, Task_ID(N).

[0936] 3) Creator identity information, including user e’s user ID and / or user public key.

[0937] 4) The data block identifier of this creation information is DB[T5,d(1)](n=1,[T5.d(1).1,e(1)]).

[0938] Step S6.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[0939] Step S6.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[0940] Step S6.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,d(1)](n=1,[T5.d(1).1,e(1)])}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[0941] Step S6.6: The user device or server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[0942] The specific content of this step S6.6 is the same as that of the above step S4.6 and will not be repeated here.

[0943] 2.6.3 Second process task status diagram.

[0944] After step S6 is completed, the second process task status diagram of the collaborative creation task of "Enterprise Research Report" is as follows Figure 37 shown.

[0945] 2.6.4 Review the second-stage digital work draft.

[0946] The information snapshot of the second process task state diagram of this collaborative creation task currently has 1 version. The information snapshot includes the execution content of the next-level subtasks T1 to T4, as well as T5 and its execution content [T5,d(1)] (n=1, [T5.d(1).1,e(1)]). This information snapshot is an example of Figure 38 shown.

[0947] The information snapshot includes the execution content [T5, d(1)] (n=1, [T5.d(1).1, e(1)]).

[0948] [T5,d(1)](n=1,[T5.d(1).1,e(1)]) corresponds to the current execution composition mode BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) of the content block cluster BC(T5) “Risk Warning”.

[0949] The digital work corresponding to BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) is as follows Figure 39 shown.

[0950] According to the information snapshot and the current content block clustering composition mode set (the second process content block clustering composition mode set), the current composition mode BC{T5,[T5,d(1)]}(n=1,[T5.d(1).1,e(1)]) and other current content block clustering composition modes in the Task_ID(N) overall content block clustering composition mode are assembled to generate a composite digital work.

[0951] 2.7 Example 4: The execution content of the atomic subtask has a ~-belonging content relationship (step S7).

[0952] 2.7.1 Enter creation information.

[0953] Step S7.1: Creator f selects subtask T5.d(1).n "Risk Warning n" and enters creation information. Creator f enters creation information based on the description of subtask T5.d(1).n, the task template, task setting information, descriptions of previous subtasks and parent subtasks, and their execution contents, etc.

[0954] 1) Creator f selects subtask T5.d(1).n “Risk Warning n” and issues a creation request.

[0955] 2) The system pushes the creation content block object of subtask T5.d(1).n to user f, such as Figure 35 shown.

[0956] 3) User f enters subtask creation information in the creation content block object of subtask T5.d(1).n “Risk Warning n”, such as Figure 36 shown.

[0957] 4) Submit the creation information of each subtask generated by the above-mentioned previous actions. For human users, user f clicks Figure 36 Click the Submit button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[0958] 5) After the system receives the subtask creation information submitted by user f, it puts the received subtask creation information into the subtask queue of subtask T5.d(1).n "Risk Warning n".

[0959] 6) The system determines that the received subtask is ranked 2 in the subtask queue of subtask T5.d(1).n "Risk Warning n", and then determines that n=2 in T5.d(1).n "Risk Warning n".

[0960] 7) Set the execution content of the indirect variable-length frame-type subtask T5 and the next-level subtask information.

[0961] At this time, the execution content of subtask T5 [T5,d(1)] (n=2, [T5.d(1).1,e(1)][T5.d(1).2,f(1)]) has three second-level subtasks T5.d(1).1, T5.d(1).2, and T5.d(1).n. Subtask T5.d(1).1 has the execution content [T5.d(1).1,e(1)], and subtask T5.d(1).2 has the execution content [T5.d(1).2,f(1)].

[0962] Subtask T5 and its execution content [T5, d(1)] (n=2, [T5.d(1).1, e(1)][T5.d(1).2, f(1)]) are described in detail in Table 31 below:

[0963]

[0964] Table 31

[0965] 8) Set the current execution composition mode BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) of the indirect variable-length frame-type content block cluster BC(T5) "Risk Prompt".

[0966] At this time, the execution content [T5, d(1)] (n = 2, [T5.d(1).1, e(1)][T5.d(1).2, f(1)]) corresponds to the indirect variable-length frame-type content block cluster execution composition method BC{T5, [T5, d(1)]} (n = 2, [T5.d(1).1, e(1)][T5.d(1).2, f(1)]). The execution composition method of the indirect variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated from BC(T5, [T5, d(1)]) (n = 1, [T5.d(1).1, e(1)]) to BC{T5, [T5, d(1)]} (n = 2, [T5.d(1).1, e(1)][T5.d(1).2, f(1)]).

[0967] Among them, BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) consists of the following content chunk clusters:

[0968] Fixed default content block DCBlock_f (T5.head);

[0969] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]).

[0970] BC{T5.body,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) consists of the following content chunks:

[0971] Undefined execution creation content block CCBlock_u(T5.d(1).1,[T5.d(1).1,e(1)]);

[0972] Undefined execution creation content block CCBlock_u(T5.d(1).2, [T5.d(1).2, f(1)]);

[0973] Undefined creative content block CCBlock_u(T5.d(1).n).

[0974] CCBlock_u(T5.d(1).1,[T5.d(1).1,e(1)]) consists of the following content block clusters:

[0975] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,e(1)]};

[0976] The undefined execution creates the content block body CCBlock_u (T5.d(1).1.body, [T5.d(1).1, e(1)]).

[0977] CCBlock_u(T5.d(1).2,[T5.d(1).2,f(1)]) consists of the following content block clusters:

[0978] Undefined execution creation content block header part CCBlock_u{T5.d(1).2.head,[T5.d(1).2,f(1)]};

[0979] The undefined execution creates the content block body CCBlock_u(T5.d(1).2.body,[T5.d(1).2,f(1)]).

[0980] CCBlock_u{T5.d(1).n]} consists of the following content block clusters:

[0981] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0982] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0983] In summary, BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) consists of the following content chunks:

[0984] Fixed default content block DCBlock_f (T5.head);

[0985] Undefined execution creation content block header part CCBlock_u{T5.d(1).1.head,[T5.d(1).1,e(1)]};

[0986] Undefined execution creation content block body CCBlock_u(T5.d(1).1.body,[T5.d(1).1,e(1)]);

[0987] Undefined execution creation content block header part CCBlock_u{T5.d(1).2.head,[T5.d(1).2,f(1)]};

[0988] Undefined execution creation content block body CCBlock_u(T5.d(1).2.body,[T5.d(1).2,f(1)]);

[0989] Undefined creative content block header CCBlock_u(T5.d(1).n.head);

[0990] Undefined creative content block body CCBlock_u (T5.d(1).n.body).

[0991] BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) is specifically described in Table 32 below:

[0992]

[0993]

[0994] Table 32

[0995] 9) Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. For human users, user f clicks Figure 36 Click the confirmation button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[0996] 2.7.2 Generate creation information data block.

[0997] Step S7.2: Receive the creation information of the subtask T5.d(1).n by the creator f, and generate the creation information data block DB[T5,d(1)](n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) corresponding to the creation information. This includes:

[0998] 1) Creation content information, including the various creation information generated in the aforementioned step S7.1, such as:

[0999] ●Execution content identification [T5,d(1)](n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]), and its creation information.

[1000] ●Content block clustering execution composition method BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) and its creation information.

[1001] 2) Task ID: Task_ID (N).

[1002] 3) Creator identity information, including: user ID of user f, and / or user public key.

[1003] 4) Identification of this creation information data block:

[1004] DB[T5,d(1)](n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]).

[1005] Step S7.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[1006] Step S7.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[1007] Step S7.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,d(1)](n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)])}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[1008] Step S7.6: The user device or server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[1009] The specific content of this step S7.6 is the same as that of the above step S4.6 and will not be repeated here.

[1010] 2.7.3 Second process task status diagram.

[1011] After step S7 is completed, the second process task status diagram of the collaborative creation task of "Enterprise Research Report" is as follows Figure 40 shown.

[1012] 2.7.4 Review the second-stage digital work draft.

[1013] The information snapshot of the second process task state diagram of this collaborative creation task currently has one version. The information snapshot includes the execution content of the next-level subtasks of T1 to T4, as well as the execution content of the next-level subtasks of T5 and its execution content [T5,d(1)] (n=2, [T5.d(1).1,e(1)][T5.d(1).2,f(1)]) [T5.d(1).1,e(1)], [T5.d(1).2,f(1)]. This information snapshot example is as follows Figure 41 shown.

[1014] The information snapshot includes the execution content [T5, d(1)] (n=2, [T5.d(1).1, e(1)][T5.d(1).2, f(1)]).

[1015] [T5,d(1)](n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) corresponds to the execution composition method BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) of the content block cluster BC(T5) “Risk Warning”.

[1016] The digital work corresponding to BC{T5,[T5,d(1)]}(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) is as follows Figure 42 shown.

[1017] According to the information snapshot and the current content block clustering composition method set (the second process content block clustering composition method set), BC(T5,[T5,d(1)])(n=2,[T5.d(1).1,e(1)][T5.d(1).2,f(1)]) and other current content block clustering composition methods in the Task_ID(N) overall content block clustering composition method are assembled to generate a composite digital work.

[1018] Example 3:

[1019] The next level subtask of the indefinite-length frame-type subtask can be an atomic subtask, whose business process is described in the first embodiment; or it can be a frame-type subtask, whose business process is described in the third embodiment.

[1020] This embodiment takes the enterprise research report and the first implementation method (corresponding to a direct indefinite-length framework-type subtask) as an example to introduce a collaborative creation method for digital works that can add framework-type next-level subtasks as needed.

[1021] 3.1 Develop and publish collaborative creation task templates.

[1022] Step M.1: The task template developer M inputs the creation information of the task template α(m), including: template description information, the initial task state diagram of the collaborative creation task (subtask system), the content block clustering system, reference creation information, and the task setting object.

[1023] 3.1.1 Set the template description information.

[1024] 3.1.2 Set the task setting object.

[1025] 3.1.3 Set up the initial task state diagram.

[1026] 3.1.3.1 Set subtasks and node relationships.

[1027] Based on the collaborative creation task decomposition and process management requirements, the template developer M developed an example of the node relationship settings (initial subtask system) for each node in the initial task state diagram for the "Enterprise Research Report" task template, as shown in Table 33 below:

[1028]

[1029]

[1030] Table 33

[1031] Rule Description 1:

[1032] The next-level subtasks of a direct fixed-length frame-type subtask are fixed-type next-level subtasks.

[1033] The next-level subtask of an indirect fixed-length frame-type subtask is a conditional next-level subtask.

[1034] The next-level subtasks of a direct indefinite-length frame-type subtask are indefinite-type next-level subtasks. The next-level subtasks of the execution content of an indirect indefinite-length frame-type subtask are indefinite-type next-level subtasks.

[1035] Rule 2: For direct, indefinite-length frame-type subtasks, the indefinite-length subtasks they possess include a length variable, n. In the task template, the initial value of the length variable, n, is n = 0. After the task is published, during the creation process, if T5 has one new subtask, n = 1. If T5 has two new subtasks, n = 2. And so on.

[1036] 3.1.3.2 AI User Operations in Task State Diagram.

[1037] 3.1.3.3Task status diagram overview version.

[1038] 3.1.3.4 Partially expanded version of the task status diagram.

[1039] The above 3.1.3.2~3.1.3.4 contents are the same as 1.1.3.2~1.1.3.4 contents, so they will not be repeated here. Only the overview of the T5 "Risk Warning" subtask is different. In this embodiment, for example Figure 43 shown.

[1040] 3.1.4 Develop a content block clustering system.

[1041] 3.1.4.1 Overall content block clustering composition method.

[1042] 3.1.4.2 The initial composition of the first-level content block cluster BC(1) “report header” is BC(1,M).

[1043] 3.1.4.3 The initial composition of the first-level content block cluster BC(T6) “Report highlights” BC(T6,M).

[1044] 3.1.4.4 The initial composition of the first-level content block cluster BC(T1) “Company situation” is BC(T1,M).

[1045] 3.1.4.5 The initial composition of the first-level content block cluster BC(T2) “Industry Analysis” is BC(T2,M).

[1046] The contents of 3.1.4.1 to 3.1.4.5 above are the same as those of 1.1.4.1 to 1.1.4.5 and will not be repeated here.

[1047] 3.1.4.6 The initial composition of the first-level content block cluster BC(T5) “Risk Warning” is BC(T5,M).

[1048] Template creator M created the initial structure for the "Risk Warning" direct variable-length frame-type content block cluster BlockCluster (T5). BlockCluster (T5, M) (n = 0) has DCBlock_f (T5.head), DCBlock_u (T5.0), and BC_u (T5.n) (n > 0). BC_u (T5.n) (n > 0) has CCBlock_u (T5.n.head) (n > 0) and BC_u (T5.n.body) (n > 0).

[1049] The detailed description of BlockCluster (T5, M) (n=0) is shown in Table 34 below (Template Maker Responsibility 6):

[1050]

[1051]

[1052] Table 34

[1053] Rule description 1: In the task template, the initial value of the length variable n included in the direct indefinite-length frame-type subtask T5 is n=0.

[1054] When the task is released, n=0, and T5 does not have a new level 2 subtask.

[1055] At this time, the default execution content [T5,M](n=0) of the direct indefinite-length frame-type subtask T5 "Risk Prompt" corresponds to the initial composition mode BC(T5,M)(n=0) of the direct indefinite-length frame-type content block cluster BlockCluster(T5) "Risk Prompt".

[1056] Among them, BC(T5,M)(n=0) consists of the following content chunk clusters:

[1057] Fixed default content block DCBlock_f (T5.head);

[1058] Undefined default content block DCBlock_u (T5.0);

[1059] Undefined creative content block header CCBlock_u (T5.n.head);

[1060] The main body of the amorphous creative content block and the indirect fixed-length frame-type content block cluster BC_u (T5.n.body).

[1061] Rule Description 2: When T5 has a new second-level subtask, n = 1. The new second-level subtask is T5.1, and the execution content of T5.1 is [T5.1, x1(1)], where x1 is the user who created the execution content for T5.1.

[1062] At this time, the current execution content of the direct indefinite-length frame-type subtask T5 "Risk Prompt" is [T5, [T5.1, x1(1)]] (n=1),

[1063] Corresponding to the execution composition method BC(T5,[T5.1,x1(1)])(n=1) of the direct indefinite-length frame-type content block cluster BlockCluster(T5) "Risk Prompt".

[1064] Among them, BC(T5,[T5.1,x1(1)])(n=1) consists of the following content block clusters:

[1065] Fixed default content block DCBlock_f (T5.head);

[1066] Undefined execution creation content block header CCBlock_u(T5.1.head,

[1067] [T5.1.head,x1(1)]);

[1068] The main body of the amorphous execution creation content block and the indirect fixed-length frame-type content block cluster execution composition method BC_u (T5.1.body, [T5.1.body, x1 (1)]);

[1069] Undefined creative content block header CCBlock_u (T5.n.head);

[1070] The main body of the amorphous creative content block and the indirect fixed-length frame-type content block cluster BC_u (T5.n.body).

[1071] Rule Description 3: When T5 has two new second-level subtasks, n = 2. The new second-level subtasks are T5.1 and T5.2. The execution content of T5.1 is [T5.1, x1(1)], and the execution content of T5.2 is [T5.2, x2(1)], where x1 and x2 are the users who created the execution content for T5.1 and T5.2, respectively.

[1072] At this time, the current execution content of the direct indefinite-length frame-type subtask T5 "Risk Prompt" [T5, [T5.1, x1(1)][T5.2, x2(1)]] (n = 2) corresponds to the current execution composition mode BC(T5, [T5.1, x1(1)][T5.2, x2(1)]) (n = 2) of the direct indefinite-length frame-type content block cluster BC(T5) "Risk Prompt".

[1073] Among them, BC(T5,[T5.1,x1(1)][T5.2,x2(1)])(n=2) consists of the following content blocks:

[1074] Fixed default content block DCBlock_f (T5.head);

[1075] Undefined execution creation content block header CCBlock_u(T5.1.head,

[1076] [T5.1.head,x1(1)]);

[1077] The main body of the amorphous execution creation content block and the indirect fixed-length frame-type content block cluster execution composition method BC_u (T5.1.body, [T5.1.body, x1 (1)]);

[1078] Undefined execution creation content block header CCBlock_u(T5.2.head,

[1079] [T5.2.head,x2(1)]);

[1080] The main body of the amorphous execution creation content block and the indirect fixed-length frame-type content block cluster execution composition method BC_u (T5.2.body, [T5.2.body, x2 (1)]);

[1081] Undefined creative content block header CCBlock_u (T5.n.head);

[1082] The main body of the amorphous creative content block and the indirect fixed-length frame-type content block cluster BC_u (T5.n.body).

[1083] And so on.

[1084] Rule 4: When T5 has N new second-level subtasks, n = N (N > 0). The new second-level subtasks are T5.1, ..., and T5.N. The execution content owned by T5.1 is [T5.1, x1(1)], ..., and the execution content owned by T5.N is [T5.N, xN(1)]. Where xN is the user who created the execution content for T5.N.

[1085] At this time, the current execution content of the direct indefinite-length frame-type subtask T5 "Risk Prompt" [T5, [T5.1, x1(1)]......[T5.N, xN(1)]] (n=N) corresponds to the current execution composition mode BC(T5, [T5.1, x1(1)]......[T5.N, xN(1)])(n=N) of the direct indefinite-length frame-type content block cluster BC(T5) "Risk Prompt".

[1086] Among them, BC(T5,[T5.1,x1(1)]......[T5.N,xN(1)])(n=N) is composed of the following content block clusters:

[1087] Fixed default content block DCBlock_f (T5.head);

[1088] Undefined execution creation content block header CCBlock_u(T5.1.head,

[1089] [T5.1.head,x1(1)]);

[1090] The main body of the amorphous execution creation content block and the indirect fixed-length frame-type content block cluster execution composition method BC_u (T5.1.body, [T5.1.body, x1 (1)]);

[1091] ......

[1092] Undefined execution creation content block header CCBlock_u(T5.N.head,

[1093] [T5.N.head,xN(1)]);

[1094] The main body of the amorphous execution creation content block and the indirect fixed-length frame type content block cluster execution composition method BC_u (T5.N.body, [T5.N.body, xN (1)]);

[1095] Undefined creative content block header CCBlock_u (T5.n.head);

[1096] The main body of the amorphous creative content block and the indirect fixed-length frame-type content block cluster BC_u (T5.n.body).

[1097] Rule Description 5: Unformed creative content blocks are divided into two types: title part and main body part. The title part of an unformed creative content block provides a title function for the main body part of an unformed creative content block. The main body part of an unformed creative content block provides main content for the title part of an unformed creative content block. The main body part of an unformed creative content block can be associated with the title part of an unformed creative content block, and the two correspond to the same next-level subtask. The next-level subtask belongs to the creative execution content of the framework-type subtask. In addition, the main body part of an unformed creative content block can also exist independently without being associated with the title part.

[1098] 3.1.5 Develop reference creation information.

[1099] 3.1.6 Generate task template data block.

[1100] 3.1.7 Release the task template data package.

[1101] 3.1.8 Review the initial digital draft.

[1102] The contents of 3.1.5 to 3.1.8 above are the same as those of 1.1.5 to 1.1.8 and will not be repeated here.

[1103] 3.2 Set and publish collaborative creation tasks.

[1104] 3.3 Carry out collaborative creation: first process task status diagram.

[1105] The above contents of 3.2 to 3.3 are the same as those of 1.2 to 1.3 and will not be repeated here.

[1106] 3.4 Example 1: The execution content of the atomic subtask has a ~-belonging content relationship (step S4).

[1107] The above 3.4 content is the same as 1.4 content and will not be repeated here.

[1108] 3.5 Example 2: The execution content of the framework-type subtask has a ~-belonging content relationship (step S5).

[1109] 3.5.1 Enter creation information.

[1110] Step S5.1: Creator g selects the framework subtask T5.n “Risk Warning n” and enters the creation information.

[1111] 1) Creator g selects subtask T5.n “Risk Warning n” and issues a creation request.

[1112] 2) The system pushes the creation content block object of subtask T5.n to user g, for example Figure 44 shown.

[1113] 3) User g enters subtask creation information in the creation content block object of the framework subtask T5.n “Risk Warning n”, for example Figure 45 shown.

[1114] 4) Submit the subtask creation information generated by the above-mentioned previous actions. If user g is a human user, by clicking Figure 45 The submit button on the upper right corner triggers this action. If user g is an AI (machine intelligence) user, this action is triggered by program instructions.

[1115] 5) After the system receives the subtask creation information submitted by user g, it puts the received subtask creation information into the next-level subtask queue of subtask T5 "Risk Warning".

[1116] 6) The system determines that the received subtask creation information is ranked 1 in the next-level subtask queue of subtask T5 "Risk Warning", and then determines that n=1 in T5.n "Risk Warning n".

[1117] 7) Set the execution content of the direct indefinite-length frame-type subtask T5 and the next-level subtask information.

[1118] At this time, the execution content of subtask T5 [T5, [T5.1, g(1)]] (n=1) has two second-level subtasks T5.1 and T5.n. Subtask T5.1 has the execution content [T5.1, g(1)].

[1119] The detailed description of subtask T5 and its execution content [T5, [T5.1, g(1)]] (n=1) is shown in Table 35 below:

[1120]

[1121] Table 35

[1122] Rule Description 1: The next level subtask of a direct indefinite-length frame-type subtask is an indefinite-length next level subtask. Moreover, in this embodiment, the indefinite-length next level subtask is also an indirect fixed-length frame-type subtask.

[1123] Rule Description: For a direct indefinite-length frame-type subtask, its indefinite-length subtasks include a length variable n. When the execution content is published, the initial value of the length variable n is n = 0. After the execution content is published, during the authoring process, if the execution content has one new subtask, n = 1. If the execution content has two new subtasks, n = 2. And so on, as shown in Table 36 below.

[1124]

[1125] Table 36

[1126] 8) Set the current execution composition mode BC{T5,[T5.1,g(1)]}(n=1) of the direct indefinite-length frame-type content block cluster BC(T5) “risk warning”.

[1127] At this point, the execution content of subtask T5 [T5, [T5.1, g(1)]] (n=1) corresponds to the content block cluster execution composition BC{T5, [T5.1, g(1)]} (n=1). The initial composition BC(T5, M) (n=0) of the direct variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated to the execution composition BC(T5, [T5.1, g(1)]) (n=1).

[1128] Among them, BC{T5,[T5.1,g(1)]}(n=1) consists of the following content chunk clusters:

[1129] Fixed default content block DCBlock_f (T5.head);

[1130] Undefined execution creation content block header CCBlock_u(T5.1.head,

[1131] [T5.1.head,g(1)]);

[1132] The main body of the amorphous execution creation content block and the indirect fixed-length frame-type content block cluster execution composition method BC_u (T5.1.body, [T5.1.body, g(1)]);

[1133] Undefined creative content block header CCBlock_u (T5.n.head);

[1134] The main body of the amorphous creative content block and the indirect fixed-length frame-type content block cluster BC_u (T5.n.body).

[1135] In summary, the specific description of BC{T5,[T5.1,g(1)]}(n=1) is shown in Table 37 below:

[1136]

[1137] Table 37

[1138] In Table 37 above, the unstructured execution creation content block body and the indirect fixed-length frame type content block cluster execution composition method BC_u (T5.1.body, [T5.1.body, g(1)]) is composed of the following content block clusters:

[1139] Conditional creative content block CCBlock (T5.1.g(1).1);

[1140] Conditional creative content block CCBlock (T5.1.g(1).2);

[1141] CCBlock (T5.1.g(1).1) consists of the following content block clusters:

[1142] Conditional creative content block header CCBlock (T5.1.g(1).1.head);

[1143] Conditional creation content block body CCBlock (T5.1.g(1).1.body).

[1144] CCBlock (T5.1.g(1).2) consists of the following content block clusters:

[1145] Conditional creative content block header CCBlock (T5.1.g(1).2.head);

[1146] Conditional creation content block body CCBlock (T5.1.g(1).2.body).

[1147] In summary, the specific description of BC_u(T5.1.body, [T5.1.body, g(1)]) is shown in Table 38 below:

[1148]

[1149] Table 38

[1150] 9) Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. If user g is a human user, by clicking Figure 45 Click the confirmation button in the upper right corner to trigger this action. If user g is an AI (machine intelligence) user, this action is triggered by program instructions.

[1151] 3.5.2 Generate creation information data block.

[1152] Step S5.2: Receive the creation information of the subtask T5.n from the creator g, and generate a creation information data block DB[T5,[T5.1,g(1)]](n=1) corresponding to the creation information. This includes:

[1153] 1) Creation content information, including the various creation information generated in the aforementioned step S5.1, such as:

[1154] ●Execute content identification [T5, [T5.1, g(1)]] (n=1) and its creation information.

[1155] ●Content block clustering execution composition method BC_u[T5,[T5.1,g(1)]](n=1) and its creation information.

[1156] 2) Task ID, Task_ID(N).

[1157] 3) Creator identity information, including user ID and / or user public key of user g.

[1158] 4) The data block identifier of this creation information is DB[T5,[T5.1,g(1)]](n=1).

[1159] Step S5.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[1160] Step S5.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[1161] Step S5.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,[T5.1,g(1)]](n=1)}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[1162] Step S5.6: The user device or the server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[1163] The specific content of this step S5.6 is the same as that of the above step S4.6 and will not be repeated here.

[1164] 3.5.3 Second process task status diagram.

[1165] After step S5 is completed, the second process task status diagram of the collaborative creation task of "Enterprise Research Report" is as follows Figure 46 shown.

[1166] 3.5.4 Review the second-stage digital work draft.

[1167] The information snapshot of the second process task state diagram of this collaborative creation task currently has one version. The information snapshot includes the execution content of the next-level subtasks T1 to T4, as well as T5 and its execution content [T5, [T5.1, g(1)]] (n = 1). This information snapshot is an example of Figure 47 The information snapshot includes the execution content [T5, [T5.1, g(1)]] (n=1).

[1168] [T5, [T5.1, g(1)]] (n=1) corresponds to the current execution composition mode BC[T5, [T5.1, g(1)]] (n=1) of the direct indefinite-length frame-type content block cluster BC(T5) "Risk Warning".

[1169] The digital works corresponding to BC[T5,[T5.1,g(1)]](n=1) are as follows Figure 48 shown.

[1170] According to the information snapshot and the current content block cluster composition mode set (the second process content block cluster composition mode set), the current execution composition mode BC[T5,[T5.1,g(1)]](n=1) and the other content block cluster current composition modes in the Task_ID(N) overall content block cluster composition mode are assembled to generate a composite digital work. In summary, some content examples of the composite digital work, such as Figure 49 shown.

[1171] Example 4:

[1172] The next level subtask of the indirect variable-length frame-type subtask can be an atomic subtask, whose business process is described in the second embodiment; or it can be a frame-type subtask, whose business process is described in the fourth embodiment.

[1173] This embodiment takes the enterprise research report and the second implementation method (corresponding to the indirect variable-length framework-type subtask) as an example to introduce a collaborative creation method for digital works that can add framework-type next-level subtasks as needed.

[1174] 4.1 Develop and publish collaborative creation task templates.

[1175] Step M.1: The task template creator M inputs the creation information of the task template α(m).

[1176] Section 4.1 is the same as Section 2.1.

[1177] 4.2 Set and publish collaborative creation tasks.

[1178] The content of 4.2 is the same as that of 2.2 and will not be repeated here.

[1179] 4.3 Carry out collaborative creation: First process task status diagram.

[1180] 4.4 Example 1: The execution content of the atomic subtask has a ~-belonging content relationship (step S4).

[1181] The above contents of 4.3 to 4.4 are the same as those of 2.3 to 2.4 and will not be repeated here.

[1182] 4.5 Example 2: The execution content of the framework-type subtask has a ~-belonging content relationship (step S5).

[1183] 4.5.1 Enter creation information.

[1184] Step S5.1: Creator h selects subtask T5 "Risk Warning" and enters creation information. Creator h enters creation information based on the description of subtask T5, as well as the task template, task setting information, descriptions of previous subtasks and their execution content, etc.

[1185] 1) Creator h selects subtask T5 “Risk Warning” and issues a creation request.

[1186] 2) The system pushes the creation content block object of subtask T5 to user h, for example Figure 29 shown.

[1187] 3) User h uses dragging to input subtask creation information in the creation content block object of the framework subtask T5 “Risk Warning”, for example Figure 50 shown.

[1188] 4) Submit the creation information of each subtask generated by the above-mentioned previous actions. For human users, the user clicks Figure 50 Click the Submit button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[1189] 5) Set the next-level subtask information of the indirect variable-length frame-type subtask T5, as shown in Table 39 below.

[1190]

[1191] Table 39

[1192] Rule Description 1: The execution content of an indirect indefinite-length frame-type subtask has a next-level subtask that is an indefinite-type next-level subtask. In addition, in this embodiment, the indefinite-type next-level subtask is also an indirect fixed-length frame-type next-level subtask.

[1193] Rule 2: For indirect, indefinite-length frame-type subtask execution content, the indefinite-length subtasks it possesses include a length variable n. When the execution content is published, the initial value of the length variable n is n = 0. After the execution content is published, during the authoring process, if the execution content has one new subtask, n = 1. If the execution content has two new subtasks, n = 2. And so on.

[1194] 6) Set the current execution composition mode BC(T5,[T5,h(1)])(n=0) of the indirect variable-length frame-type content block cluster BC(T5) "risk warning".

[1195] The initial composition mode BC(T5,M) of the indirect variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated to the execution composition mode BC(T5,[T5,h(1)])(n=0).

[1196] Currently, BC(T5,[T5,h(1)])(n=0) consists of the following content chunk clusters:

[1197] Fixed default content block DCBlock_f (T5.head);

[1198] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,h(1)]}(n=0).

[1199] BC{T5.body,[T5,h(1)]}(n=0) consists of the following content chunks:

[1200] Undefined default content block DCBlock_u(T5.h(1).0);

[1201] Unstructured frame type content block cluster BC_u (T5.h(1).n).

[1202] BC_u{T5.h(1).n]} consists of the following content chunk clusters:

[1203] Undefined creation content block header CCBlock_u (T5.h(1).n.head);

[1204] Undefined frame type content block cluster BC_u(T5.h(1).n.body).

[1205] In summary, the execution composition of the indirect variable-length frame-type content block cluster BC(T5) "Risk Prompt" BC(T5,[T5,h(1)])(n=0) includes: DCBlock_f(T5.head), DCBlock_u(T5.h(1).0), CCBlock_u(T5.h(1).n.head), BC_u(T5.h(1).n.body), and the specific description is shown in Table 40 below:

[1206]

[1207] Table 40

[1208] Rule Description 1: When the execution content [T5, h(1)] is released, n=0, and [T5, h(1)] does not have a new level 2 subtask.

[1209] At this time, the execution content [T5, h(1)] corresponds to the indirect variable-length frame-type content block cluster execution composition mode BC{T5, [T5, h(1)]} (n=0).

[1210] Among them, BC(T5,[T5,h(1)])(n=0) consists of the following content chunk clusters:

[1211] Fixed default content block DCBlock_f (T5.head);

[1212] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,h(1)]}(n=0).

[1213] BC{T5.body,[T5,h(1)]}(n=0) consists of the following content chunks:

[1214] Undefined default content block DCBlock_u(T5.h(1).0));

[1215] Unstructured frame type content block cluster BC_u (T5.h(1).n).

[1216] BC_u (T5.h(1).n) consists of the following content chunk clusters:

[1217] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1218] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1219] In summary, BC{T5,[T5,h(1)]}(n=0) consists of the following content chunks:

[1220] Fixed default content block DCBlock_f (T5.head);

[1221] Unstructured default content block DCBlock_u (T5.h(1).0).

[1222] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1223] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1224] Rule Description 2: When the execution content [T5, h(1)] has a new second-level subtask, n = 1. The new second-level subtask is T5.h(1).1, and the execution content owned by T5.h(1).1 is [T5.h(1).1, x1(1)], where x1 refers to the user who created the execution content of T5.h(1).1.

[1225] At this time, the execution content [T5, h(1)] (n=1, [T5.h(1).1, x1(1)]) corresponds to the indirect variable-length frame-type content block cluster execution composition method BC{T5, [T5, h(1)]} (n=1, [T5.h(1).1, x1(1)]).

[1226] Among them, BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,x1(1)]) consists of the following content chunk clusters:

[1227] Fixed default content block DCBlock_f (T5.head);

[1228] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,h(1)]}(n=1,[T5.h(1).1,x1(1)]).

[1229] BC{T5.body,[T5,h(1)]}(n=1,[T5.h(1).1,x1(1)]) consists of the following content chunks:

[1230] The indefinite frame type content block clustering execution composition method BC_u{T5.h(1).1,[T5.h(1).1,x1(1)]};

[1231] Unstructured frame type content block cluster BC_u (T5.h(1).n).

[1232] BC_u{T5.h(1).1,[T5.h(1).1,x1(1)]} consists of the following content chunks cluster:

[1233] Undefined execution creation content block header part CCBlock_u{T5.h(1).1.head,[T5.h(1).1,x1(1)]};

[1234] The amorphous frame type content block clustering execution composition method is BC_u{T5.h(1).1.body,[T5.h(1).1,x1(1)]}.

[1235] BC_u (T5.h(1).n) consists of the following content chunk clusters:

[1236] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1237] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1238] In summary, BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,x1(1)]) consists of the following content chunks:

[1239] Fixed default content block DCBlock_f (T5.head);

[1240] Undefined creative content block header not CCBlock_u{T5.h(1).1.head,[T5.h(1).1,x1(1)]};

[1241] The amorphous frame type content block clustering execution composition method is BC_u{T5.h(1).1.body,[T5.h(1).1,x1(1)]}.

[1242] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1243] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1244] Rule Description 3: When the execution content [T5, h(1)] has two new second-level subtasks, n = 2. The new second-level subtasks are T5.h(1).1 and T5.h(1).2. The execution content owned by T5.h(1).1 is [T5.h(1).1, x1(1)], and the execution content owned by T5.h(1).2 is [T5.h(1).2, x2(1)]. Where x2 is the user who created the execution content for T5.h(1).2.

[1245] At this time, the execution content [T5,h(1)](n=2,[T5.h(1).1,x1(1)][T5.h(1).2,x2(1)]) corresponds to the indirect variable-length frame-type content block clustering execution composition method BC{T5,[T5,h(1)]}(n=2,[T5.h(1).1,x1(1)][T5.h(1).2,x2(1)]).

[1246] Among them, BC(T5,[T5,h(1)])(n=2,[T5.h(1).1,x1(1)][T5.h(1).2,x2(1)]) is composed of the following content block clusters:

[1247] Fixed default content block DCBlock_f (T5.head);

[1248] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,h(1)]}(n=2,[T5.h(1).1,x1(1)][T5.h(1).2,x2(1)]).

[1249] BC{T5.body,[T5,h(1)]}(n=2,[T5.h(1).1,x1(1)][T5.h(1).2,x2(1)]) consists of the following content chunks:

[1250] Amorphous frame type content block clustering execution composition method BC_u(T5.h(1).1,

[1251] [T5.h(1).1,x1(1)]);

[1252] Amorphous frame type content block clustering execution composition method BC_u(T5.h(1).2,

[1253] [T5.h(1).2,x2(1)]).

[1254] Unstructured frame type content block cluster BC_u (T5.h(1).n).

[1255] BC_u{T5.h(1).1,[T5.h(1).1,x1(1)]} consists of the following content chunks cluster:

[1256] Undefined execution creation content block header part CCBlock_u{T5.h(1).1.head,[T5.h(1).1,x1(1)]};

[1257] The amorphous frame type content block clustering execution composition method is BC_u{T5.h(1).1.body,[T5.h(1).1,x1(1)]}.

[1258] BC_u{T5.h(1).2,[T5.h(1).2,x2(1)]} consists of the following content chunks cluster:

[1259] Undefined execution creation content block header part CCBlock_u{T5.h(1).2.head,[T5.h(1).2,x2(1)]};

[1260] The amorphous frame type content block clustering execution composition method is BC_u{T5.h(1).2.body,[T5.h(1).2,x2(1)]}.

[1261] BC_u (T5.h(1).n) consists of the following content chunk clusters:

[1262] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1263] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1264] In summary, BC(T5,[T5,h(1)])(n=2,[T5.h(1).1,x1(1)][T5.h(1).2,x2(1)]) consists of the following content chunks:

[1265] Fixed default content block DCBlock_f (T5.head);

[1266] Undefined execution creation content block header part CCBlock_u{T5.h(1).1.head,[T5.h(1).1,x1(1)]};

[1267] The indefinite frame type content block clustering execution composition method is BC_u{T5.h(1).1.body,[T5.h(1).1,x1(1)]};

[1268] Undefined execution creation content block header part CCBlock_u{T5.h(1).2.head,[T5.h(1).2,x2(1)]};

[1269] The indefinite frame type content block clustering execution composition method is BC_u{T5.h(1).2.body,[T5.h(1).2,x2(1)]};

[1270] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1271] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1272] And so on.

[1273] Rule 4: When the execution content [T5, h(1)] has N new second-level subtasks, n = N (N>0). The new second-level subtasks are T5.h(1).1, ..., T5.h(1).N. The execution content owned by T5.h(1).1 is [T5.h(1).1, x1(1)], ..., and the execution content owned by T5.h(1).N is [T5.h(1).N, xN(1)]. Where xN is the user who created the execution content for T5.h(1).N.

[1274] At this time, the execution content [T5,h(1)](n=N,[T5.h(1).1,x1(1)]...[T5.h(1).N,xN(1)]) corresponds to the indirect variable-length frame-type content block clustering execution composition method BC{T5,[T5,h(1)]}(n=N,[T5.h(1).1,x1(1)]...[T5.h(1).N,xN(1)]).

[1275] Among them, BC{T5,[T5,h(1)]}(n=N,[T5.h(1).1,x1(1)]...[T5.h(1).N,xN(1)]) consists of the following content block clusters:

[1276] Fixed default content block DCBlock_f (T5.head);

[1277] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,h(1)]}(n=N,[T5.h(1).1,x1(1)]...[T5.h(1).N,xN(1)]).

[1278] BC{T5.body,[T5,h(1)]}(n=N,[T5.h(1).1,x1(1)]...[T5.h(1).N,xN(1)]) consists of the following content chunks:

[1279] Amorphous frame type content block clustering execution composition method BC_u(T5.h(1).1,

[1280] [T5.h(1).1,x1(1)]);

[1281] ......

[1282] Amorphous frame type content block clustering execution composition method BC_u(T5.h(1).N,

[1283] [T5.h(1).N,xN(1)]);

[1284] Unstructured frame type content block cluster BC_u (T5.h(1).n).

[1285] BC_u{T5.h(1).1,[T5.h(1).1,x1(1)]} consists of the following content chunks cluster:

[1286] Undefined execution creation content block header part CCBlock_u{T5.h(1).1.head,[T5.h(1).1,x1(1)]};

[1287] The amorphous frame type content block clustering execution composition method is BC_u{T5.h(1).1.body,[T5.h(1).1,x1(1)]}.

[1288] …

[1289] BC_u{T5.h(1).N,[T5.h(1).n,xN(1)]} consists of the following content chunks cluster:

[1290] Undefined execution creation content block header part CCBlock_u{T5.h(1).N.head,[T5.h(1).N,xN(1)]};

[1291] The amorphous frame type content block clustering execution composition method is BC_u{T5.h(1).N.body,[T5.h(1).N,xN(1)]}.

[1292] BC_u (T5.h(1).n) consists of the following content chunk clusters:

[1293] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1294] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1295] In summary, BC(T5,[T5,h(1)])(n=N,[T5.h(1).1,x1(1)]...[T5.h(1).N,xN(1)]) consists of the following content chunks:

[1296] Fixed default content block DCBlock_f (T5.head);

[1297] Undefined execution creation content block header part CCBlock_u{T5.h(1).1.head,[T5.h(1).1,x1(1)]};

[1298] The indefinite frame type content block clustering execution composition method is BC_u{T5.h(1).1.body,[T5.h(1).1,x1(1)]};

[1299] …

[1300] Undefined execution creation content block header part CCBlock_u{T5.h(1).N.head,[T5.h(1).N,xN(1)]};

[1301] The indefinite frame type content block clustering execution composition method BC_u{T5.h(1).N.body,[T5.h(1).N,xN(1)]};

[1302] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1303] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1304] Rule Description 5: Unformed creative content blocks are divided into two types: title part and main body part. The title part of an unformed creative content block provides a title function for the main body part of an unformed creative content block. The main body part of an unformed creative content block provides main content for the title part of an unformed creative content block. The main body part of an unformed creative content block can be associated with the title part of an unformed creative content block, and the two correspond to the same next-level subtask. The next-level subtask belongs to the creative execution content of the framework-type subtask. In addition, the main body part of an unformed creative content block can also exist independently without being associated with the title part.

[1305] 7) Send the creation information of each subtask generated by the above-mentioned previous actions and confirm it. For human users, the user clicks Figure 50 Click the confirmation button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[1306] 4.5.2 Generate creation information data block.

[1307] Step S5.2: Receive the creation information of the subtask T5 from the creator h, and generate a creation information data block DB[T5,h(1)](n=0) corresponding to the creation information. This includes:

[1308] 1) Creation content information, including the various creation information generated in the aforementioned step S5.1, such as:

[1309] ●Execute content identification [T5,h(1)](n=0) and its creation information.

[1310] ●Execute the content block clustering composition method BC(T5,[T5,h(1)])(n=0) and its creation information.

[1311] 2) Task ID, Task_ID(N).

[1312] 3) Creator identity information, including user b’s user ID and / or user public key.

[1313] 4) The data block identifier of this creation information, DB[T5,h(1)](n=0).

[1314] Step S5.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[1315] Step S5.4: The server stores the creation information data block and generates an access address for the creation information data block.

[1316] Step S5.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,h(1)](n=0)}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[1317] Step S5.6: The user device or the server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[1318] The specific content of this step S5.6 is the same as that of the above step S4.6 and will not be repeated here.

[1319] 4.5.3 Second process task status diagram.

[1320] After step S5 is completed, the second process task state diagram of the collaborative creation task of "Enterprise Research Report" is as follows: Figure 51 shown.

[1321] 4.5.4 Review the second-stage digital work draft.

[1322] The information snapshot of the second process task state diagram of this collaborative creation task currently has 1 version. The information snapshot includes the execution content of the next-level subtasks T1 to T4, as well as T5 and its execution content [T5,h(1)] (n=0). This information snapshot example, for example Figure 52 The information snapshot includes the execution content [T5, h(1)] (n=0).

[1323] [T5,h(1)](n=0) corresponds to the execution composition mode BC(T5,[T5,h(1)])(n=0) of the content block cluster BC(T5) “risk warning”.

[1324] The digital works corresponding to BC(T5,[T5,h(1)])(n=0) are, for example Figure 33 shown.

[1325] According to the information snapshot and the current content block cluster composition mode set (the second process content block cluster composition mode set), the current composition mode BC(T5,[T5,h(1)])(n=0) and other current content block cluster composition modes in the Task_ID(N) overall content block cluster composition mode are assembled to generate a composite digital work, such as Figure 34 shown.

[1326] 4.6 Example 3: The execution content of the next-level framework-type subtask has a ~-belonging content relationship (step S6).

[1327] 4.6.1 Enter creation information.

[1328] Step S6.1: Creator j selects the next subtask T5.h(1).n under subtask T5 "Risk Warning" and enters the creation information. Creator j enters the creation information based on the following: the task template, task setting information, descriptions of the previous subtasks and their execution contents, descriptions of subtask T5 and its execution contents, descriptions of T5.h(1).n, etc.

[1329] 1) Creator j selects subtask T5.h(1).n “Risk Warning n” and issues a creation request.

[1330] 2) The system pushes the creation content block object of subtask T5.h(1).n to user j, for example Figure 53 shown.

[1331] 3) User j enters subtask creation information in the creation content block object of the next-level framework subtask T5.h(1).n “Risk Warning n”, for example Figure 54 shown.

[1332] 4) Submit the creation information of each subtask generated by the above-mentioned previous actions. For human users, user j clicks Figure 54 Click the Submit button in the upper right corner to trigger this action. For AI (machine intelligence) users, this action is triggered by program instructions.

[1333] 5) After the system receives the subtask creation information submitted by user j, it puts the received subtask creation information into the next-level subtask queue of subtask T5 "Risk Warning".

[1334] 6) The system determines that the received subtask creation information is ranked as 1 in the next-level subtask queue of subtask T5 "Risk Warning".

[1335] 7) Set the execution content of the indirect variable-length frame-type subtask T5 and the next-level subtask information.

[1336] At this time, the execution content of subtask T5 [T5,h(1)] (n=1, [T5.h(1).1,j(1)]) has two second-level subtasks T5.h(1).1 and T5.h(1).n. Subtask T5.h(1).1 has the execution content [T5.h(1).1,j(1)].

[1337] The specific description of subtask T5 and its execution content [T5,h(1)] (n=1,[T5.h(1).1,j(1)]) is shown in Table 41 below:

[1338]

[1339] Table 41

[1340] Rule Description 1: The execution content of an indirect indefinite-length frame-type subtask has a next-level subtask that is an indefinite-length next-level subtask. In addition, in this embodiment, the indefinite-length next-level subtask is also an indirect fixed-length frame-type subtask.

[1341] Rule Description 2:

[1342] The next-level subtasks of a direct fixed-length frame-type subtask are fixed-type next-level subtasks.

[1343] The next-level subtask of an indirect fixed-length frame-type subtask is a conditional next-level subtask.

[1344] The next-level subtasks of a direct indefinite-length frame-type subtask are indefinite-type next-level subtasks. The next-level subtasks of the execution content of an indirect indefinite-length frame-type subtask are indefinite-type next-level subtasks.

[1345] Rule 3: For the execution content of an indirect, indefinite-length frame-type subtask, the indefinite-length subtasks it possesses include a length variable n. When the execution content is published, the initial value of the length variable n is n = 0. After the execution content is published, during the authoring process, if the execution content has one new subtask, n = 1. If the execution content has two new subtasks, n = 2. And so on.

[1346] The second-level subtask T5.h(1).1 in Table 41 and its execution content [T5.h(1).1,j(1)] are described, for example, as shown in Table 42 below:

[1347]

[1348] Table 42

[1349] 8) Set the current execution composition mode BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,j(1)]) of the indirect variable-length frame-type content block cluster BC(T5) "Risk Prompt".

[1350] At this time, the execution content [T5, h(1)] (n=1, [T5.h(1).1, j(1)]) corresponds to the indirect variable-length frame-type content block cluster execution composition method BC{T5, [T5, h(1)]} (n=1, [T5.h(1).1, j(1)]). The execution composition method of the indirect variable-length frame-type content block cluster BC(T5) "Risk Warning" is updated from BC(T5, [T5, h(1)]) (n=0) to BC(T5, [T5, h(1)]) (n=1, [T5.h(1).1, j(1)]).

[1351] Among them, BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,j(1)]) consists of the following content chunk clusters:

[1352] Fixed default content block DCBlock_f (T5.head);

[1353] The indirect variable-length frame-type content block clustering execution composition method is BC{T5.body,[T5,h(1)]}(n=1,[T5.h(1).1,j(1)]).

[1354] BC{T5.body,[T5,h(1)]}(n=1,[T5.h(1).1,j(1)]) consists of the following content chunks:

[1355] The indefinite frame type content block clustering execution composition method BC_u{T5.h(1).1,[T5.h(1).1,j(1)]};

[1356] Unstructured frame type content block cluster BC_u (T5.h(1).n).

[1357] BC_u{T5.h(1).1,[T5.h(1).1,j(1)]} consists of the following content chunks cluster:

[1358] Undefined execution creation content block header part CCBlock_u{T5.h(1).1.head,[T5.h(1).1,j(1)]};

[1359] The amorphous frame type content block clustering execution composition method is BC_u{T5.h(1).1.body,[T5.h(1).1,j(1)]}.

[1360] BC_u{T5.h(1).1.body,[T5.h(1).1,j(1)]} consists of the following content chunks:

[1361] Conditional creation content block CCBlock(T5.h(1).1.j(1).1);

[1362] Conditional creation content block CCBlock (T5.h(1).1.j(1).2).

[1363] The amorphous frame type content block cluster BC_u (T5.h(1).n) consists of the following content block clusters:

[1364] Undefined creative content block header CCBlock_u{T5.h(1).n.head};

[1365] Unstructured frame type content block cluster BC_u{T5.h(1).n.body}.

[1366] In summary, the execution composition of the indirect variable-length frame-type content block cluster BC(T5) "risk warning" BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,j(1)]) includes: DCBlock_f(T5.head), CCBlock_u{T5.h(1).1.head,[T5.h(1).1,j(1)]}、CCBlock(T5.h(1).1.j(1).1), CCBlock(T5.h(1).1.j(1).2), CCBlock_u(T5.h(1).n.head)(n>1), BC_u(T5.h(1).n.body)(n>1), and the specific description is shown in Table 43 below:

[1367]

[1368]

[1369] Table 43

[1370] 4.6.2 Generate creation information data block.

[1371] Step S6.2: Receive the creation information of the subtask T5.h(1).n by the creator j, and generate a creation information data block DB[T5,h(1)](n=1,[T5.h(1).1,j(1)]) corresponding to the creation information, including:

[1372] 1) Creation content information, including the various creation information generated in the aforementioned step S6.1, such as: execution content identifier [T5, h(1)] (n=1, [T5.h(1).1, j(1)]) and its creation information; current content block cluster execution composition mode BC_u{T5, [T5, h(1)]} (n=1, [T5.h(1).1, j(1)]) and its content information; etc.

[1373] 2) Task ID, Task_ID(N).

[1374] 3) Creator identity information, including user ID and / or user public key of user j.

[1375] 4) The data block identifier of this creation information is DB[T5,h(1)](n=1,[T5.h(1).1,j(1)]).

[1376] Step S6.3: The server or user device generates a digital fingerprint of the creative information data block based on the creative information data block. Specifically, the digital fingerprint can be generated by the user using a private key to digitally sign the creative information data block.

[1377] Step S6.4: The server or user device stores the creation information data block and generates an access address for the creation information data block.

[1378] Step S6.5: The user device or server generates a creation information data packet DP{Task_ID(N).[T5,h(1)](n=1,[T5.h(1).1,j(1)])}, which includes the following contents: creation information data block storage address, creation information data block data fingerprint, and creation information publisher identity information (such as user public key).

[1379] Step S6.6: The user device or server publishes the creation information data package so that relevant users in the collaborative creation community can access the creation information data package.

[1380] The specific content of this step S6.6 is the same as that of the above step S4.6 and will not be repeated here.

[1381] 4.6.3 Second process task status diagram.

[1382] After step S6 is completed, the second process task state diagram of the collaborative creation task of "Enterprise Research Report" is as follows, for example Figure 55 shown.

[1383] 4.6.4 Review the second-stage digital work draft.

[1384] The information snapshot of the second process task state diagram of this collaborative creation task currently has 1 version. The information snapshot includes the execution content of the next-level subtasks T1 to T4, as well as T5 and its execution content [T5,h(1)] (n=1,[T5.h(1).1,j(1)]). This information snapshot example, for example Figure 56 shown.

[1385] The information snapshot includes the execution content [T5,h(1)](n=1,[T5.h(1).1,j(1)]).

[1386] [T5,h(1)](n=1,[T5.h(1).1,j(1)]) corresponds to the execution composition method BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,j(1)]) of the content block cluster BC(T5) “Risk Warning”.

[1387] The digital work corresponding to BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,j(1)]) is, e.g. Figure 48 shown.

[1388] According to the information snapshot and the current content block cluster composition mode set (the second process content block cluster composition mode set), the current composition mode BC(T5,[T5,h(1)])(n=1,[T5.h(1).1,j(1)]) and other current content block cluster composition modes in the overall content block cluster composition mode of Task_ID(N) are assembled to generate a composite digital work, such as Figure 49 shown.

[1389] The following is an introduction to the equipment or device provided in the embodiments of the present application, in which the explanations or examples of technical features that are the same as or corresponding to those described in the above method are not repeated hereafter.

[1390] An electronic device provided in an embodiment of the present application, see Figure 57 , for example, including: a processor 600 and a memory 620; wherein:

[1391] When the electronic device provided in the embodiment of the present application is used to generate a digital work through the first variable-length frame-type subtask, the processor 600 is configured to read the program in the memory 620 and execute the following process:

[1392] Obtaining a first collaborative creation task, the first collaborative creation task including one or more subtasks, the one or more subtasks including at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask having an indefinite-form first-lower-level subtask, the indefinite-form first-lower-level subtask being used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask having a second-lower-level subtask queue, the second-lower-level subtask queue sorting the second-lower-level subtasks in a received order;

[1393] Obtaining an instruction for a first target subtask selected by a first creator from among the one or more subtasks; the first target subtask is the indefinite first lower-level subtask;

[1394] According to the instruction, the first target subtask is provided to the first creator for execution of creation by the first creator;

[1395] receiving first creation information of the first target subtask from the first creator;

[1396] Based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask, the digital work content corresponding to the first creation information is determined.

[1397] In some embodiments, determining the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first variable-length frame-type subtask includes:

[1398] Submitting the first creation information;

[1399] Generate a second-level subtask corresponding to the first creative information according to the first target subtask, wherein the second-level subtask corresponding to the first creative information has the first creative information; and has a first variable-length frame-type subtask of the first target subtask and a second-level subtask corresponding to the first creative information;

[1400] Obtaining the order of the second-lower-layer subtask corresponding to the first creation information in the second-lower-layer subtask queue owned by the first variable-length frame-type subtask;

[1401] According to the sorting, the digital work content corresponding to the first creation information is determined.

[1402] When the electronic device provided in the embodiment of the present application is used to generate a digital work through the second variable-length frame-type subtask, the processor 600 is configured to read the program in the memory 620 and execute the following process:

[1403] Acquire a second collaborative creation task, the second collaborative creation task including one or more subtasks, the one or more subtasks including at least one second indefinite-length frame-type subtask and at least one indefinite-form third-lower-level subtask, the second indefinite-length frame-type subtask having second execution content, the second execution content having an indefinite-form third-lower-level subtask, the indefinite-form third-lower-level subtask being used to generate one or more fourth-lower-level subtasks; the second execution content of the second indefinite-length frame-type subtask having a fourth-lower-level subtask queue, the fourth-lower-level subtask queue sorting the fourth-lower-level subtasks in a received order;

[1404] Obtaining an instruction for a second target subtask selected by a second creator from among the one or more subtasks; the second target subtask is the indefinite third lower-level subtask;

[1405] According to the instruction, the second target subtask is provided to the creator for the second creator to perform creation;

[1406] receiving second creation information of the second target subtask from the second creator;

[1407] Based on the second creation information and the order of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue owned by the second execution content owned by the second indefinite-length frame-type subtask, the digital work content corresponding to the second creation information is determined.

[1408] In some embodiments, based on the second creative information and the ranking of the fourth lower-level subtask corresponding to the second creative information in the fourth lower-level subtask queue owned by the second execution content owned by the second variable-length frame-type subtask, determining the digital work content corresponding to the second creative information includes:

[1409] Submitting the second creation information;

[1410] A fourth lower-level subtask corresponding to the second creative information is generated according to the second target subtask, and the fourth lower-level subtask corresponding to the second creative information has the second creative information; has the second execution content owned by the second indefinite-length frame-type subtask of the second target subtask, and has the fourth lower-level subtask corresponding to the second creative information;

[1411] Obtaining the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content;

[1412] Based on the sorting, the digital work content corresponding to the second creation information is determined.

[1413] When the electronic device provided in the embodiment of the present application is used to implement task release for the first variable-length frame-type subtask, the processor 600 is configured to read the program in the memory 620 and execute the following process:

[1414] Obtaining task setting information input by the task publisher, wherein the task setting information corresponds to a task template;

[1415] Generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[1416] The one or more subtasks include: at least one indefinite-length frame-type subtask and at least one indefinite-type next-level subtask.

[1417] In some embodiments, the target collaborative creation task is a first collaborative creation task; the indefinite-length frame-type subtask is a first indefinite-length frame-type subtask; the indefinite next-level subtask is an indefinite first-next-level subtask, the first indefinite-length frame-type subtask has an indefinite first-next-level subtask, and the indefinite first-next-level subtask is used to generate one or more second-next-level subtasks; the first indefinite-length frame-type subtask has a second-next-level subtask queue, and the second-next-level subtask queue sorts the second-next-level subtasks in the order of receipt.

[1418] When the electronic device provided in the embodiment of the present application is used to implement task release for the second variable-length frame-type subtask, the processor 600 is configured to read the program in the memory 620 and execute the following process:

[1419] Obtaining task setting information input by the task publisher, wherein the task setting information corresponds to a task template;

[1420] Generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[1421] The one or more subtasks include: at least one indefinite-length frame-type subtask.

[1422] In some embodiments, the target collaborative creation task is the second collaborative creation task; the variable-length frame-type subtask is the second variable-length frame-type subtask;

[1423] When the creator creates second execution content for the second indefinite-length frame-type subtask by publishing the second collaborative creation task, the one or more subtasks further include: at least one indefinite-length third lower-level subtask;

[1424] Among them, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-level subtask, and the indefinite third-level subtask is used to generate one or more fourth-level subtasks; the second indefinite-length frame-type subtask has a second execution content with a fourth-level subtask queue, and the fourth-level subtask queue sorts the fourth-level subtasks in the order of receipt.

[1425] The transceiver 610 is configured to receive and send data under the control of the processor 600 .

[1426] Among them, Figure 57 In the embodiment, the bus architecture may include any number of interconnected buses and bridges to link together various circuits of one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not described further herein. The bus interface provides an interface. The transceiver 610 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. For different user devices, the user interface 630 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[1427] The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 600 when performing operations.

[1428] In some embodiments, the processor 600 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[1429] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[1430] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[1431] See also Figure 58A , an embodiment of the present application provides a digital work generation device, comprising:

[1432] A first task acquisition unit 11 is configured to acquire a first collaborative creation task, the first collaborative creation task including one or more subtasks, the one or more subtasks including at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask having an indefinite-form first-lower-level subtask, the indefinite-form first-lower-level subtask being used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask having a second-lower-level subtask queue, the second-lower-level subtask queue sorting the second-lower-level subtasks in a received order;

[1433] A first instruction acquisition unit 12 is configured to acquire an instruction for a first target subtask selected by a first creator from among the one or more subtasks; the first target subtask is the indefinite first lower-level subtask;

[1434] A first task providing unit 13 is configured to provide the first target subtask to the first creator according to the instruction, so that the first creator can perform creation;

[1435] A first creation information receiving unit 14 is configured to receive first creation information of the first target subtask from the first creator;

[1436] The first work determination unit 15 is used to determine the digital work content corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask.

[1437] In some embodiments, determining the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first variable-length frame-type subtask includes:

[1438] Submitting the first creation information;

[1439] Generate a second-level subtask corresponding to the first creative information according to the first target subtask, wherein the second-level subtask corresponding to the first creative information has the first creative information; and has a first variable-length frame-type subtask of the first target subtask and a second-level subtask corresponding to the first creative information;

[1440] Obtaining the order of the second-lower-layer subtask corresponding to the first creation information in the second-lower-layer subtask queue owned by the first variable-length frame-type subtask;

[1441] According to the sorting, the digital work content corresponding to the first creation information is determined.

[1442] See also Figure 58B Another digital work generation device provided in an embodiment of the present application includes:

[1443] A second task acquisition unit 21 is configured to acquire a second collaborative creation task, the second collaborative creation task including one or more subtasks, the one or more subtasks including at least one second indefinite-length frame-type subtask and at least one indefinite-third-lower-level subtask, the second indefinite-length frame-type subtask having a second execution content, the second execution content having an indefinite-third-lower-level subtask, the indefinite-third-lower-level subtask being used to generate one or more fourth-lower-level subtasks; the second execution content of the second indefinite-length frame-type subtask having a fourth-lower-level subtask queue, the fourth-lower-level subtask queue sorting the fourth-lower-level subtasks in a received order;

[1444] A second instruction acquisition unit 22 is configured to acquire an instruction for a second target subtask selected by a second creator from among the one or more subtasks; the second target subtask is the indefinite third lower-level subtask;

[1445] A second task providing unit 23 is configured to provide the second target subtask to the creator according to the instruction, so that the second creator can perform creation;

[1446] A second creation information receiving unit 24 is configured to receive second creation information of the second target subtask from the second creator;

[1447] The second work determination unit 25 is used to determine the digital work content corresponding to the second creation information based on the second creation information and the order of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue owned by the second execution content owned by the second indefinite-length frame-type subtask.

[1448] In some embodiments, based on the second creative information and the ranking of the fourth lower-level subtask corresponding to the second creative information in the fourth lower-level subtask queue owned by the second execution content owned by the second variable-length frame-type subtask, determining the digital work content corresponding to the second creative information includes:

[1449] Submitting the second creation information;

[1450] A fourth lower-level subtask corresponding to the second creative information is generated according to the second target subtask, and the fourth lower-level subtask corresponding to the second creative information has the second creative information; has the second execution content owned by the second indefinite-length frame-type subtask of the second target subtask, and has the fourth lower-level subtask corresponding to the second creative information;

[1451] Obtaining the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content;

[1452] Based on the sorting, the digital work content corresponding to the second creation information is determined.

[1453] See also Figure 59A , an embodiment of the present application provides a task issuing device, comprising:

[1454] A first task setting information acquisition unit 31 is used to acquire task setting information input by a task publisher, wherein the task setting information corresponds to a task template;

[1455] A first publishing unit 32 is configured to generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[1456] The one or more subtasks include: at least one indefinite-length frame-type subtask and at least one indefinite-type next-level subtask.

[1457] In some embodiments, the target collaborative creation task is a first collaborative creation task; the indefinite-length frame-type subtask is a first indefinite-length frame-type subtask; the indefinite next-level subtask is an indefinite first-next-level subtask, the first indefinite-length frame-type subtask has an indefinite first-next-level subtask, and the indefinite first-next-level subtask is used to generate one or more second-next-level subtasks; the first indefinite-length frame-type subtask has a second-next-level subtask queue, and the second-next-level subtask queue sorts the second-next-level subtasks in the order of receipt.

[1458] See also Figure 59B Another task issuing device provided in an embodiment of the present application includes:

[1459] The second task setting information acquisition unit 41 is used to acquire the task setting information input by the task publisher, wherein the task setting information corresponds to the task template;

[1460] A second publishing unit 42 is configured to generate and publish a target collaborative creation task based on the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks;

[1461] The one or more subtasks include: at least one indefinite-length frame-type subtask.

[1462] In some embodiments, the target collaborative creation task is the second collaborative creation task; the variable-length frame-type subtask is the second variable-length frame-type subtask;

[1463] When the creator creates second execution content for the second indefinite-length frame-type subtask by publishing the second collaborative creation task, the one or more subtasks further include: at least one indefinite-length third lower-level subtask;

[1464] Among them, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-level subtask, and the indefinite third-level subtask is used to generate one or more fourth-level subtasks; the second indefinite-length frame-type subtask has a second execution content with a fourth-level subtask queue, and the fourth-level subtask queue sorts the fourth-level subtasks in the order of receipt.

[1465] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[1466] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[1467] Any of the devices or apparatuses provided in the embodiments of the present application may specifically be a desktop computer, a portable computer, a smart phone, a tablet computer, a personal digital assistant (PDA), etc. They may include a central processing unit (CPU), a memory, input / output devices, etc. Input devices may include a keyboard, a mouse, a touch screen, etc. Output devices may include a display device, such as a liquid crystal display (LCD), a cathode ray tube (CRT), etc.

[1468] The memory may include a read-only memory (ROM) and a random access memory (RAM), and provides program instructions and data stored in the memory to the processor. In an embodiment of the present application, the memory may be used to store the program of any of the methods provided in the embodiments of the present application.

[1469] The processor calls the program instructions stored in the memory, and the processor is used to execute any of the methods provided in the embodiments of the present application according to the obtained program instructions.

[1470] The present application embodiment also provides a computer program product or computer program, which includes computer instructions, which are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the computer device performs any of the methods described in the above embodiments. The program product can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[1471] The present invention provides a computer-readable storage medium for storing computer program instructions used by the apparatus provided in the above embodiments of the present invention, which includes a program for executing any of the methods provided in the above embodiments of the present invention. The computer-readable storage medium may be a non-transitory computer-readable medium.

[1472] The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NANDFLASH), solid-state drives (SSDs)), etc.

[1473] It should be understood that:

[1474] The access technology through which entities in the communication network transmit traffic can be any suitable current or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, 5G, Bluetooth, infrared, etc.; in addition, the embodiments can also apply wired technology, for example, IP-based access technology, such as a wired network or a fixed line.

[1475] Embodiments suitable for being implemented as software code or a portion thereof and run using a processor or processing functionality are independent of the software code and may be specified using any known or future developed programming language, such as a high-level programming language such as objective-C, C, C++, C#, Java, Python, Javascript, other scripting languages, etc., or a low-level programming language such as machine language or assembler.

[1476] The implementation of the embodiments is hardware independent and may be implemented using any known or future developed hardware technology or any mixture thereof, such as a microprocessor or CPU (Central Processing Unit), MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic) and / or TTL (Transistor-Transistor Logic).

[1477] Embodiments may be implemented as separate devices, apparatuses, units, components or functions, or in a distributed manner, for example, one or more processors or processing functions may be used or shared in a process, or one or more processing segments or processing portions may be used and shared in a process, where one physical processor or more than one physical processor may be used to implement one or more processing portions dedicated to a particular process as described.

[1478] The apparatus may be implemented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset.

[1479] The embodiments may also be implemented as any combination of hardware and software, such as ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field Programmable Gate Array) or CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components.

[1480] The embodiments may also be implemented as a computer program product including a computer usable medium having computer readable program code embodied therein, the computer readable program code being adapted to perform the processes as described in the embodiments, wherein the computer usable medium may be a non-transitory medium.

[1481] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.

[1482] The present application is described with reference to the flow chart and / or block diagram of the method, device (system), and computer program product according to the embodiment of the present application. It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processing machine or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one flow chart flow or multiple flows and / or one box or multiple boxes of the block diagram.

[1483] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[1484] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[1485] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A method for generating a digital work, characterized in that: The method comprises: Obtaining a first collaborative creation task, the first collaborative creation task including one or more subtasks, the one or more subtasks including at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask having an indefinite-form first-lower-level subtask, the indefinite-form first-lower-level subtask being used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask having a second-lower-level subtask queue, the second-lower-level subtask queue sorting the second-lower-level subtasks in a received order; Obtaining an instruction for a first target subtask selected by a first creator from among the one or more subtasks; the first target subtask is the indefinite first lower-level subtask; According to the instruction, the first target subtask is provided to the first creator for execution of creation by the first creator; receiving first creation information of the first target subtask from the first creator; Based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask, the digital work content corresponding to the first creation information is determined.

2. The method according to claim 1, characterized in that Determining the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue of the first variable-length frame-type subtask includes: Submitting the first creation information; Generate a second-lower-level subtask corresponding to the first creative information according to the first target subtask, wherein the second-lower-level subtask corresponding to the first creative information has the first creative information; and has a first variable-length frame-type subtask of the first target subtask and a second-lower-level subtask corresponding to the first creative information; Obtaining the order of the second-lower-layer subtask corresponding to the first creation information in the second-lower-layer subtask queue owned by the first variable-length frame-type subtask; According to the sorting, the digital work content corresponding to the first creation information is determined.

3. A method for generating digital works, characterized in that: The method comprises: Acquire a second collaborative creation task, the second collaborative creation task including one or more subtasks, the one or more subtasks including at least one second indefinite-length frame-type subtask and at least one indefinite-form third-lower-level subtask, the second indefinite-length frame-type subtask having second execution content, the second execution content having an indefinite-form third-lower-level subtask, the indefinite-form third-lower-level subtask being used to generate one or more fourth-lower-level subtasks; the second execution content of the second indefinite-length frame-type subtask having a fourth-lower-level subtask queue, the fourth-lower-level subtask queue sorting the fourth-lower-level subtasks in a received order; Obtaining an instruction for a second target subtask selected by a second creator from among the one or more subtasks; the second target subtask is the indefinite third lower-level subtask; According to the instruction, the second target subtask is provided to the creator for the second creator to perform creation; receiving second creation information of the second target subtask from the second creator; Based on the second creation information and the order of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue owned by the second execution content owned by the second indefinite-length frame-type subtask, the digital work content corresponding to the second creation information is determined.

4. The method according to claim 3, characterized in that Determining the digital work content corresponding to the second creation information based on the second creation information and the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content owned by the second variable-length frame-type subtask includes: Submitting the second creation information; A fourth lower-level subtask corresponding to the second creative information is generated according to the second target subtask, and the fourth lower-level subtask corresponding to the second creative information has the second creative information; has the second execution content owned by the second indefinite-length frame-type subtask of the second target subtask, and has the fourth lower-level subtask corresponding to the second creative information; Obtaining the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content; Based on the sorting, the digital work content corresponding to the second creation information is determined.

5. A task publishing method, characterized in that: The method comprises: Obtaining task setting information input by the task publisher, wherein the task setting information corresponds to a task template; Generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks; The one or more subtasks include: at least one indefinite-length frame-type subtask and at least one indefinite-type next-level subtask.

6. The method according to claim 5, characterized in that The target collaborative creation task is a first collaborative creation task; the indefinite-length frame-type subtask is a first indefinite-length frame-type subtask; the indefinite-type next-level subtask is an indefinite-type first-next-level subtask, the first indefinite-length frame-type subtask has an indefinite-type first-next-level subtask, and the indefinite-type first-next-level subtask is used to generate one or more second-next-level subtasks; The first variable-length frame-type subtask has a second-lower-layer subtask queue, and the second-lower-layer subtask queue sorts the second-lower-layer subtasks in a receiving order.

7. A task publishing method, characterized in that: The method comprises: Obtaining task setting information input by the task publisher, wherein the task setting information corresponds to a task template; Generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks; The one or more subtasks include: at least one indefinite-length frame-type subtask.

8. The method according to claim 7, characterized in that The target collaborative creation task is the second collaborative creation task; the variable-length frame-type subtask is the second variable-length frame-type subtask; When the creator creates second execution content for the second indefinite-length frame-type subtask by publishing the second collaborative creation task, the one or more subtasks further include: at least one indefinite-length third lower-level subtask; Among them, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-level subtask, and the indefinite third-level subtask is used to generate one or more fourth-level subtasks; the second indefinite-length frame-type subtask has a second execution content with a fourth-level subtask queue, and the fourth-level subtask queue sorts the fourth-level subtasks in the order of receipt.

9. A digital work generating device, characterized in that: The device comprises: A first task acquisition unit is configured to acquire a first collaborative creation task, the first collaborative creation task including one or more subtasks, the one or more subtasks including at least one first indefinite-length frame-type subtask and at least one indefinite-form first-lower-level subtask, the first indefinite-length frame-type subtask having an indefinite-form first-lower-level subtask, the indefinite-form first-lower-level subtask being used to generate one or more second-lower-level subtasks; the first indefinite-length frame-type subtask having a second-lower-level subtask queue, the second-lower-level subtask queue sorting the second-lower-level subtasks in a received order; A first instruction acquisition unit is configured to acquire an instruction for a first target subtask selected by a first creator from among the one or more subtasks; the first target subtask is the indefinite first lower-level subtask; A first task providing unit is configured to provide the first target subtask to the first creator according to the instruction, so that the first creator performs creation; A first creation information receiving unit, configured to receive first creation information of the first target subtask from the first creator; The first work determination unit is used to determine the digital work content corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue owned by the first indefinite-length frame-type subtask.

10. The device according to claim 9, characterized in that Determining the content of the digital work corresponding to the first creation information based on the first creation information and the order of the second-lower-level subtask corresponding to the first creation information in the second-lower-level subtask queue of the first variable-length frame-type subtask includes: Submitting the first creation information; Generate a second-level subtask corresponding to the first creative information according to the first target subtask, wherein the second-level subtask corresponding to the first creative information has the first creative information; and has a first variable-length frame-type subtask of the first target subtask and a second-level subtask corresponding to the first creative information; Obtaining the order of the second-lower-layer subtask corresponding to the first creation information in the second-lower-layer subtask queue owned by the first variable-length frame-type subtask; According to the sorting, the digital work content corresponding to the first creation information is determined.

11. A digital work generating device, characterized in that: The device comprises: A second task acquisition unit is configured to acquire a second collaborative creation task, the second collaborative creation task including one or more subtasks, the one or more subtasks including at least one second indefinite-length frame-type subtask and at least one indefinite-third-lower-level subtask, the second indefinite-length frame-type subtask having a second execution content, the second execution content having an indefinite-third-lower-level subtask, the indefinite-third-lower-level subtask being used to generate one or more fourth-lower-level subtasks; the second execution content of the second indefinite-length frame-type subtask having a fourth-lower-level subtask queue, the fourth-lower-level subtask queue sorting the fourth-lower-level subtasks in a received order; A second instruction acquisition unit is configured to acquire an instruction for a second target subtask selected by a second creator from among the one or more subtasks; the second target subtask is the indefinite third lower-level subtask; A second task providing unit is configured to provide the second target subtask to the creator according to the instruction, so that the second creator performs creation; A second creation information receiving unit, configured to receive second creation information of the second target subtask from the second creator; The second work determination unit is used to determine the digital work content corresponding to the second creation information based on the second creation information and the order of the fourth-lower-level subtask corresponding to the second creation information in the fourth-lower-level subtask queue owned by the second execution content owned by the second indefinite-length frame-type subtask.

12. The device according to claim 11, characterized in that Determining the digital work content corresponding to the second creation information based on the second creation information and the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content owned by the second variable-length frame-type subtask includes: Submitting the second creation information; A fourth lower-level subtask corresponding to the second creative information is generated according to the second target subtask, and the fourth lower-level subtask corresponding to the second creative information has the second creative information; has the second execution content owned by the second indefinite-length frame-type subtask of the second target subtask, and has the fourth lower-level subtask corresponding to the second creative information; Obtaining the order of the fourth lower-level subtask corresponding to the second creation information in the fourth lower-level subtask queue owned by the second execution content; Based on the sorting, the digital work content corresponding to the second creation information is determined.

13. A task issuing device, characterized in that: The device comprises: A first task setting information acquisition unit is used to acquire task setting information input by a task publisher, wherein the task setting information corresponds to a task template; A first publishing unit is configured to generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks; The one or more subtasks include: at least one indefinite-length frame-type subtask and at least one indefinite-type next-level subtask.

14. The device according to claim 13, characterized in that The target collaborative creation task is a first collaborative creation task; the indefinite-length frame-type subtask is a first indefinite-length frame-type subtask; the indefinite-type next-level subtask is an indefinite-type first-next-level subtask, the first indefinite-length frame-type subtask has an indefinite-type first-next-level subtask, and the indefinite-type first-next-level subtask is used to generate one or more second-next-level subtasks; The first variable-length frame-type subtask has a second-lower-layer subtask queue, and the second-lower-layer subtask queue sorts the second-lower-layer subtasks in a receiving order.

15. A task issuing device, characterized in that: The device comprises: A second task setting information acquisition unit is used to acquire task setting information input by the task publisher, wherein the task setting information corresponds to the task template; A second publishing unit is configured to generate and publish a target collaborative creation task according to the task setting information and the task template, wherein the target collaborative creation task includes one or more subtasks; The one or more subtasks include: at least one indefinite-length frame-type subtask.

16. The device according to claim 15, characterized in that The target collaborative creation task is the second collaborative creation task; the variable-length frame-type subtask is the second variable-length frame-type subtask; When the creator creates second execution content for the second indefinite-length frame-type subtask by publishing the second collaborative creation task, the one or more subtasks further include: at least one indefinite-length third lower-level subtask; Among them, the second indefinite-length frame-type subtask has a second execution content, the second execution content has an indefinite third-level subtask, and the indefinite third-level subtask is used to generate one or more fourth-level subtasks; the second indefinite-length frame-type subtask has a second execution content with a fourth-level subtask queue, and the fourth-level subtask queue sorts the fourth-level subtasks in the order of receipt.

17. An electronic device, characterized in that: include: a memory for storing program instructions; A processor is configured to call the program instructions stored in the memory and execute the method according to any one of claims 1 to 8 according to the obtained program.

18. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the method according to any one of claims 1 to 8.

Images