Method and computing device for processing subtasks in collaborative community

Abstract

The invention provides a method for processing subtasks in a cooperative community and computing equipment. The method comprises the steps that a first sub-task in a first cooperative task is obtained, the first cooperative task comprises a plurality of sub-tasks, the sub-tasks comprise the first sub-task, the first sub-task is used for deriving one or more groups of follow-up sub-tasks with the undetermined number, and the first cooperative task is provided with a first task template associated with the first cooperative task; the first task template comprises first task constraint information, and the first task constraint information comprises corresponding information between the first subtask and the subsequent subtask; providing the first subtask for a first task creator; obtaining first subtask creation information completed by the first task creator; and submitting the first subtask creation information. According to the technical scheme, a collaboration method for generating subsequent sub-tasks in the task proceeding process is provided for collaboration creation, so that better task dynamic hierarchical planning is achieved.

Description

Technical Field

[0001] This invention relates to the field of network collaboration and knowledge management technology, and specifically to a method and computing device for processing subtasks in a collaborative community. Background Technology

[0002] Since the Third Industrial Revolution, represented by the information age, the amount of information in human society has experienced an exponential growth of "information explosion," and the human knowledge system has become increasingly vast. Furthermore, constrained by diverse data asset rights and data privacy barriers, data localization is also widespread. Along with this, the division of labor in human society has become increasingly refined, and the number of professional fields has proliferated. Faced with this situation, it is neither feasible nor economical for either human experts or machine intelligence to process the entirety of human civilization's knowledge single-handedly. In terms of knowledge processing capabilities, both human experts and machine intelligence possess unique areas of expertise and advantageous application scenarios. Therefore, when facing complex tasks involving multiple professional fields, both human experts and machine intelligence have a need for collaboration.

[0003] The collaborative methods disclosed in Chinese patent publications CN114595673A ("Method for Collaborative Creation of Digital Works, Method for Task Issuance, and Device") and CN118365070A ("Method for Collaborative Creation of Digital Works, Method for Task Issuance, and Device Including Framework-Type Subtasks") decompose collaborative tasks into multiple subtasks with dependencies and including subtask description information. Through framework-type subtasks, the disclosed collaborative methods can further break down subtasks into more granular lower-level subtasks with dependencies for creators to work on. Furthermore, to ensure that tasks are collaboratively created in the correct order and based on complete basic information, creators must first obtain the creation status of the subtasks before participating in collaborative creation. The creation status includes a creative state and a non-creative state. Only for subtasks in a creative state can creators input creation information based on the subtask description information to generate the subtask's execution content. Through the above task decomposition, hierarchical planning, and process management, collaborative creation of digital works is achieved.

[0004] Better task decomposition, coupled with hierarchical planning and process management, can effectively improve the digital production efficiency of the entire society. For example, firstly, it allows human experts or machine intelligence creators to more fully leverage their comparative advantages in their professional fields or scenario orientations; secondly, it enables experts from various fields to participate in collaborative creation using fragmented time.

[0005] However, in some applications, the number and relationships of subtasks cannot be predetermined. For example, in collaborative film and television creation tasks, we cannot determine the number of scenes in a film or television production before the task begins, and therefore cannot determine the number of subtasks required to write the scripts for each scene or the number of subtasks required to shoot / generate the scripts for each scene. Similarly, in collaborative film and television creation tasks, we cannot determine the number of shots in a scene beforehand, and therefore cannot determine the number of subtasks required to shoot / generate the scripts for each shot in a scene. Furthermore, in collaborative scientific and technological invention tasks, we cannot determine the number of modules required for the development of a prototype product of a scientific and technological invention and their relationships before the task begins, and therefore cannot determine the number and relationships of subtasks related to module development.

[0006] Therefore, in some applications, it is necessary to introduce a dynamic hierarchical planning method for tasks, so that the number and relationships of subsequent subtasks can be determined during the collaborative task process, thereby enabling collaborative creation in these applications.

[0007] Currently, two patents, one with publication number "CN114595673A" and titled "Digital Works Collaborative Creation Method, Task Publishing Method and Device," and the other with publication number "CN118365070A" and titled "Collaborative Creation Method, Task Publishing Method and Device Including Framework-Type Subtasks," both disclose a method and device for determining the number and relationship of subtasks during task execution. However, the methods disclosed in these two patents are limited to a "ownership-attribution" relationship, where the creator of the upper-level (or higher-level) framework-type subtask in the "ownership" position generates the number and relationship of the lower-level (or lower-level) subtasks in the "attribution" position by creating framework-type execution content.

[0008] In particular, the large-scale commercialization of collaborative community technologies disclosed in the following invention patents will stimulate collective intelligence, including human experts and various general AI and professional AI, further accelerating implementation efficiency and improving implementation quality.

[0009] Chinese patent publication number "CN120494767A" entitled "Digital Work Generation, Task Publishing Method, Device, Equipment and Medium" discloses another method for dynamic hierarchical planning of tasks. However, this method is limited to a "ownership-belonging" relationship, where the creator of the next-level sub-task in the "belonging" position gradually adds the next-level sub-tasks belonging to the framework sub-task as needed during the creation process.

[0010] In summary, existing technologies are limited to situations where, within an ownership-belonging relationship, the creator of a framework-type subtask in the "ownership" position generates a next-level subtask "belonging" to themselves by creating framework-type execution content, or the creator of a next-level subtask in the "belonging" position gradually adds the next-level subtasks "owned" by the framework-type subtask as needed. Summary of the Invention

[0011] The present invention aims to provide a method and computing device for processing subtasks in a collaborative community, and to provide a collaborative method for generating one or more sets of subsequent subtasks during the process of collaborative creation, so as to achieve better dynamic hierarchical planning of tasks.

[0012] According to one aspect of the present invention, a method for processing subtasks in a collaborative community is provided, the method comprising: Obtain the first subtask in the first collaborative task. The first collaborative task includes multiple subtasks, and the multiple subtasks include the first subtask. The first subtask is used to derive one or more sets of subsequent subtasks of undetermined quantity. The first collaborative task has a first task template associated with it. The first task template includes first task constraint information. The first task constraint information includes the correspondence information between the first subtask and the subsequent subtasks. Provide the first subtask to the creator of the first task; Obtain the creation information of the first subtask completed by the creator of the first task; Submit the creation information for the first subtask. The first subtask creation information is used to derive one or more sets of subsequent subtasks of a determined quantity based on the first task constraint information.

[0013] According to some embodiments, the first subtask creation information is also used to supplement the subtask description information of any of the subsequent subtasks.

[0014] According to some embodiments, the first subtask creation information is also used to supplement the description of the relationship between the subsequent subtasks in any group of subsequent subtasks.

[0015] According to some embodiments, the first subtask creation information includes one or more first creation modules and quantity information of the one or more first creation modules, wherein the quantity information is used to determine the number of subsequent subtasks in any group of subsequent subtasks based on the first task constraint information.

[0016] According to some embodiments, the one or more first creation modules have content information, which is used to supplement the subtask description information of the subsequent subtasks.

[0017] According to some embodiments, when the first subtask creation information includes multiple first creation modules, the first subtask creation information also includes the association relationship between the first creation modules, and the association relationship is used to describe the association relationship between subsequent subtasks in any group of subsequent subtasks.

[0018] According to some embodiments, the first task constraint information includes the following conventions: The number of subsequent subtasks is determined by the number of corresponding modules included in the creation information of the first subtask; and / or The relationships between subsequent subtasks are determined by the relationships between the corresponding modules included in the creation information of the first subtask; and / or The subtask description information of the subsequent subtasks is supplemented based on the content information of the corresponding modules included in the creation information of the first subtask.

[0019] According to some embodiments, the plurality of subtasks further includes a second subtask derived from the first subtask, the second subtask having at least one set of subsequent subtasks from the set or plurality of subsequent subtasks.

[0020] According to another aspect of the present invention, a method for processing subtasks in a collaborative community is provided, the method comprising: Obtain a third subtask for a first collaborative task, the first collaborative task including multiple subtasks, the multiple subtasks including a first subtask, the first subtask being used to derive a number of third subtasks to be determined, the first collaborative task having a first task template associated with it, the first task template including first task constraint information, the first task constraint information including correspondence information between the first subtask and the third subtask; Provide the third subtask to the third task creator; Obtain the creation information of the third sub-task completed by the creator of the third task; Submit the creation information for the third subtask. The step of obtaining a third subtask for the first collaborative task includes: obtaining subtask description information for the third subtask, wherein the subtask description information of the third subtask includes information corresponding to the content information included in the creation information of the first subtask completed by the creator of the first subtask, according to the first task constraint information.

[0021] According to some embodiments, the first subtask creation information includes multiple first creation modules, wherein... The quantity information of the plurality of first creation modules is used to determine the quantity of the third sub-task based on the first task constraint information; and / or The content information from the multiple first creation modules is used to supplement the subtask description information of the third subtask; and / or The relationships between the multiple first creation modules are used to describe the relationships between the third sub-tasks.

[0022] According to some embodiments, the plurality of subtasks further includes a second subtask derived from the first subtask, and the second subtask has the third subtask.

[0023] According to another aspect of the present invention, a method for processing subtasks in a collaborative community is provided, the method comprising: The first subtask in the first collaborative task is provided to the creator of the first task. The first collaborative task includes multiple subtasks, and the multiple subtasks include the first subtask. The first subtask is used to derive one or more sets of subsequent subtasks of an undetermined number. The first collaborative task has a first task template associated with it. The first task template includes first task constraint information. The first task constraint information includes the correspondence information between the first subtask and the subsequent subtasks. The system receives creation information for a first subtask completed by the creator of the first task. This first subtask creation information includes multiple first creation modules, specifically the first creation modules and their quantity information. The quantity information is used to determine the quantity of the third subtask based on the first task constraint information. Based on the first task relationship constraint information and the first subtask creation information, one or more sets of subsequent subtasks of a determined quantity are derived.

[0024] According to some embodiments, the first subtask creation information includes the first creation module and the quantity information of the first creation module; Based on the first task relationship constraint information and the first subtask creation information, derive one or more sets of subsequent subtasks with a determined quantity, including: determining the number of subsequent subtasks in any set of subsequent subtasks according to the quantity information and the first task constraint information.

[0025] According to some embodiments, the first creation module has content information; Based on the first task relationship constraint information and the first subtask creation information, derive one or more sets of subsequent subtasks of a determined quantity, including: supplementing one or more sets of subtask description information of the subsequent subtasks using the content information.

[0026] According to some embodiments, when the first subtask creation information includes multiple first creation modules, the first subtask creation information also includes the association relationship between the multiple first creation modules. Based on the first task constraint information and the first subtask creation information, derive one or more sets of subsequent subtasks of a determined quantity, including: using the association relationship to describe the association relationship between multiple subsequent subtasks in any set of subsequent subtasks.

[0027] According to some embodiments, the first task constraint information includes the following conventions: The number of subsequent sub-tasks is determined by the number of corresponding modules included in the creation information of the first sub-task; The relationships between the subsequent sub-tasks are determined by the relationships between the corresponding modules included in the creation information of the first sub-task; The subtask description information of the subsequent subtasks is supplemented based on the content information of the corresponding modules included in the creation information of the first subtask.

[0028] According to some embodiments, the plurality of subtasks further includes a second subtask derived from the first subtask, the second subtask having at least one set of subsequent subtasks from the set or plurality of subsequent subtasks.

[0029] According to another aspect of the present invention, a computer program product is provided, comprising: Includes a computer program that, when executed by a processor, implements the method as described in any of the preceding methods.

[0030] According to another aspect of the present invention, a computing device is provided, comprising: Processor; and A memory storing a computer program that, when executed by the processor, causes the processor to perform the method described in any of the preceding methods.

[0031] According to embodiments of the present invention, the limitations of the prior art are overcome, enabling the creator of the prior atomic subtask in the "derived" position to determine the number and relationship of one or more subsequent subtasks in the "dependent" position through creation information, and to supplement the subtask description information of the corresponding subsequent subtasks.

[0032] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit the invention. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0034] Figure 1 A flowchart illustrating a method for handling subtasks in a collaborative community, according to an example embodiment, is shown.

[0035] Figure 2 A schematic diagram of an apparatus for completing sub-tasks in a collaborative community, according to an example embodiment, is shown.

[0036] Figure 3 A flowchart illustrating a method for processing subtasks in a collaborative community, according to another embodiment, is shown.

[0037] Figure 4 A flowchart illustrating a method for processing subtasks in a collaborative community, according to another embodiment, is shown.

[0038] Figure 5 This diagram illustrates an example of an overview of the initial task state diagram according to some embodiments.

[0039] Figure 6 The diagram illustrates a scenario based on some implementation examples, showing how a script is generated to expand to the next level of subtasks.

[0040] Figure 7 This diagram illustrates the creation information for the execution content, created by template creator T2.1 according to the example embodiment.

[0041] Figure 8 This diagram illustrates the implementation content reference creation information created by the template creator for T2.2 according to some embodiments.

[0042] Figure 9 The task status diagram of the "Remembering A" collaborative creation task is shown as a task status diagram after the task publisher publishes the task according to some embodiments.

[0043] Figure 10 This diagram illustrates the first process task state of a task with Task_ID (3396815520) obtained by the user client according to some embodiments.

[0044] Figure 11 The diagram illustrates that after T1 "Synopsis" has executable content according to some embodiments, T2 "Script" enters a creative state.

[0045] Figure 12 The diagram shows the state of the content creation block object of the system pushing subtask T2.1 to user b according to some embodiments.

[0046] Figure 13 The diagram illustrates, according to some embodiments, user b inputting subtask creation information into the creation content block object of subtask T2.1.

[0047] Figure 14 The diagram shows the second process task state diagram of the collaborative creation task Task_ID (3396815520) of "Remembering A" according to some embodiments.

[0048] Figure 15 The diagram illustrates the generation of a new second process task state diagram after adding creative execution content to Task_ID(3396815520) according to some embodiments.

[0049] Figure 16 This diagram illustrates the creation content block object of the subtask T2.2.1{[T2.1,b(1)]} that the system pushes to the user according to some embodiments.

[0050] Figure 17 This diagram illustrates how a user inputs subtask creation information into the creation content block object of subtask T2.2.1{[T2.1,b(1)]} according to some embodiments.

[0051] Figure 18 The second process task state diagram is shown according to some embodiments of Task_ID (3396815520).

[0052] Figure 19 The diagram illustrates the creative state diagrams for each scenario script according to some embodiments T3.3.

[0053] Figure 20 The diagram illustrates the generation of a new second process task state diagram after adding creative execution content to Task_ID(3396815520) according to some embodiments.

[0054] Figure 21 This diagram illustrates the creative state of the framework T3.3.1.3 "Scene 1 Shot Script Creation" according to some embodiments.

[0055] Figure 22 The diagram illustrates the generation of a new second process task state diagram after adding creative execution content to Task_ID(3396815520) according to some embodiments.

[0056] Figure 23 This diagram illustrates the creation content block object of the user device that invokes the subtask T3.3.1.3.3{[T2.2.1, Wang(1)][T2.1, b(1)]}} according to some embodiments.

[0057] Figure 24 This diagram illustrates the state of the input content block object of a script file created according to some embodiments.

[0058] Figure 25 The diagram illustrates the generation of a new second process task state diagram after adding creative execution content to Task_ID(3396815520) according to some embodiments.

[0059] Figure 26 This diagram illustrates the framework subtask T3.3.1.3 "Script Creation for Each Shot in Scene 1" according to some embodiments, and its execution content is not shown in the task state diagram.

[0060] Figure 27 The diagram shows a snapshot of the current information in the task state diagram of Task_ID(3396815520) "Remembering A" according to some embodiments, where T3.3.1.3.3, T3.3.2.3.1, and T3.3.2.3.4 have execution content.

[0061] Figure 28 This is a snapshot diagram illustrating the information of a complete draft formed according to some embodiments of Task_ID (3396815520) "Remembering A".

[0062] Figure 29 This diagram illustrates a first-level subtask of an initial task state diagram co-created according to some embodiments.

[0063] Figure 30 This diagram illustrates the second-layer subtask of the T4 prototype product development, which was collaboratively created based on some embodiments.

[0064] Figure 31 The task state diagram shown is the task state diagram for the collaborative creation task Task_ID(928527) of "Automatic Bass Brushing Technique Toothbrush" according to some embodiments.

[0065] Figure 32 This diagram illustrates the creative state of subtask T4.1 "Overall Development Plan" of T4 "Prototype Product Development" according to some embodiments.

[0066] Figure 33 The diagram shows a related explanatory page illustrating the creation of content block objects according to some embodiments of subtask T4.1.

[0067] Figure 34 This diagram illustrates the input page prepared for the subtask state diagram of subtask T4.1 "Creating Content Block Object" under subtask T4.2 "Development Collaboration" according to some embodiments.

[0068] Figure 35 This diagram illustrates, according to some embodiments, user b inputting subtask creation information into the creation content block object of subtask T4.1.

[0069] Figure 36 This shows the next-level task status diagram according to some embodiments T4.2.

[0070] Figure 37 The second process task state diagram is shown for the collaborative creation task Task_ID(928527) of "Automatic Bass Brushing Technique Toothbrush" according to some embodiments.

[0071] Figure 38 The diagram shows the state of a new second process task generated after adding creative execution content to Task_ID(928527) according to some embodiments.

[0072] Figure 39 A block diagram of a computing device according to an exemplary embodiment is shown. Detailed Implementation

[0073] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that the invention will be thorough and complete, and the concept of the exemplary embodiments will be fully conveyed to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0074] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a full understanding of embodiments of the invention. However, those skilled in the art will recognize that the technical solutions of the invention can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of the invention.

[0075] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0076] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0077] It should be understood that although the terms first, second, third, etc., may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Therefore, the first component discussed below may be referred to as the second component without departing from the teachings of the present invention. As used herein, the term "and / or" includes all combinations of any one and more of the associated listed items.

[0078] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this invention are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0079] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of exemplary embodiments, and the modules or processes in the drawings are not necessarily essential for implementing the present invention, and therefore cannot be used to limit the scope of protection of the present invention.

[0080] The main limitation of existing technologies lies in their restriction to establishing task constraints between subtasks with an "ownership-ownership" relationship. Existing technologies lack the technical means to establish task constraint relationships between subtasks with a dependency-derivation relationship.

[0081] However, in some applications, within a "derivative-dependency" relationship, the creator of the preceding subtask in the "derivative" position needs to determine the number and relationships of one or more subsequent subtasks in the "dependency" position by executing the content. For example, in a film / television collaborative creation task, the creator of the preceding script overall planning subtask determines the number of scenes in the film / television when creating the content, thus determining the number of subsequent scene scripts and scene generation-related subtasks. Similarly, in a film / television collaborative creation task, the creator of the preceding global resource planning subtask determines the number and relationships of various resources required for the film / television when creating the content, thus determining the number and relationships of subsequent resource generation-related subtasks. Furthermore, in a scientific and technological innovation R&D collaborative task, the creator of the preceding solution overall architecture subtask determines the number and relationships of modules in the overall solution when creating the content, thus determining the number and relationships of module development-related subtasks.

[0082] Furthermore, while some existing workflow applications offer flexible customization, they are not suitable for iterative creation of collaborative tasks. For example, workflow applications focus on the flow of operational tasks rather than iteratively completing pre-defined and subsequent sub-tasks around a single creative theme. In workflows, task relationships and flows are often pre-defined or fixed, and the personnel handling tasks are also pre-defined or implicitly designated, which fails to meet the flexibility and constraints required for collaborative tasks in a community.

[0083] Therefore, in some applications, it is necessary to introduce a dynamic hierarchical planning method for tasks, so that the number of subtasks, their relationships, and / or content can be determined during the task process, thereby enabling collaborative creation in these applications.

[0084] To address this, the present invention proposes a method for handling subtasks in a collaborative community, aiming to provide a collaborative method and apparatus for dynamically determining subsequent subtasks during the task execution process, thereby achieving better dynamic hierarchical planning of tasks. This overcomes the limitations of existing technologies, enabling creators of earlier subtasks in a "derived" position to determine the number and relationships of subsequent subtasks in a "dependent" position through content execution.

[0085] Before describing the embodiments of the present invention, some terms or concepts involved in the embodiments of the present invention will be explained.

[0086] In some applications, the number and relationships of one or more sets of subtasks need to be determined within a "derivative-dependency" relationship. The creator of the preceding atomic subtask, which is in a "derivative" position, determines the number and relationships of one or more subsequent subtasks, which are in a "dependent" position, by creating atomic execution content. For example, in a collaborative film and television production, the head screenwriter must first create the execution content of the atomic subtask "Overall Script Planning" to determine the number of scenes in the film or television production. Then, based on the number of scenes determined in the "Overall Script Planning" execution content, the number of subsequent subtasks required to write the scripts for each scene can be determined during the scriptwriting process; furthermore, the number of subsequent subtasks required to shoot / generate the scripts for each scene can also be determined during the script shooting / generation process. In a collaborative film and television production, the writer of the nth scene script also needs to first create the execution content of the atomic subtask "Nth Scene Script," determining the number of shots for that scene within the execution content. Then, based on the number of shots determined in the "Scene n Script" execution content, the number of subsequent subtasks required for shooting / generating each shot script in Scene n can be determined during the script shooting / generation process. For example, in a collaborative scientific and technological invention task, the chief engineer first needs to create the execution content of the atomic subtask "Overall Solution Architecture," determining the number of modules required for product development, the relationships between modules, and providing module description information. Then, based on the execution content of the atomic subtask "Overall Solution Architecture," the number of subsequent subtasks required for developing each module of the prototype product can be determined during the prototype product development process, along with their relationships, and the corresponding subtask description information can be added. This is not limited to collaborative tasks involving audiovisual works and scientific and technological inventions. It also includes various types of collaborative tasks such as the design and production of metaverse works, the design and programming of various game works, the formulation of various survey / evaluation / research reports, the design and development of various software products, the work and development of various scientific research projects, the research and writing of various academic issues, the research and development of various new drug products, and the research and design of various engineering solutions. All of these collaborative tasks have the following dynamic hierarchical planning requirements: During the collaborative task, the creator of the prior atomic subtask, which is in a "derived" position, determines the number and / or relationship of one or more subsequent subtasks in a "dependent" position by creating atomic execution content, and / or supplementing the corresponding subtask description information, thereby dynamically determining the one or more subsequent subtasks.

[0087] Subtasks can include framework-type subtasks and atomic subtasks. Framework-type subtasks can include subtasks at the next level. Atomic subtasks, on the other hand, cannot include subtasks at the next level. Subtasks include content clustering non-corresponding subtasks and content clustering corresponding subtasks. Content clustering non-corresponding subtasks do not have a corresponding content cluster or content block. For content clustering corresponding subtasks, the content cluster corresponding to a framework-type subtask is a framework-type content cluster, and the content cluster corresponding to an atomic subtask is a creative content block. Content clustering can be understood as a "group" or "cluster" that organizes one or more content blocks or content block groups together. The content clusters can be divided into two categories: framework-type content clusters and atomic-type content clusters. Content clustering corresponding subtasks refer to subtasks that have a correspondence with at least one content cluster.

[0088] Based on the hierarchy of the sub-goal system formed after task decomposition, a subtask also refers to the next level of subtask (or the next-level subtask), and the next level of subtask. The execution content of a subtask can also refer to the execution content of the next level of subtask, the next level of subtask, and so on. This same logic applies when referring to "subtask" and "subtask execution content" later in the text.

[0089] This invention aims to provide a collaborative method for generating one or more sets of subsequent subtasks during the collaborative creation process, thereby achieving better dynamic hierarchical planning of tasks and overcoming the limitations of existing technologies. It allows creators of earlier atomic subtasks (which are in a "derived" position) to determine the number and relationships of subsequent subtasks (which are in a "dependent" position) through the content they create, and to supplement the subtask description information of the corresponding subsequent subtasks. The invention is described below with reference to specific embodiments.

[0090] Figure 1 The diagram illustrates a method for processing subtasks in a collaborative community, according to an example embodiment.

[0091] See Figure 1 In S101, obtain the first subtask in the first collaborative task.

[0092] According to some embodiments, the first collaborative task includes multiple subtasks, the multiple subtasks including the first subtask, the first subtask being used to derive one or more sets of subsequent subtasks of undetermined quantity, the first collaborative task having a first task template associated with it, the first task template including first task constraint information, the first task constraint information including correspondence information between the first subtask and the subsequent subtasks.

[0093] According to some embodiments, the first task constraint information stipulates that the number of subsequent subtasks is determined by the number information of the corresponding modules included in the first subtask creation information, the relationship between the subsequent subtasks is determined by the relationship between the corresponding modules included in the first subtask creation information, and / or the subtask description information of the subsequent subtasks is supplemented according to the content information of the corresponding modules included in the first subtask creation information.

[0094] According to some embodiments, the first task template further includes template content information, such as: a first task template task description, used to describe the first task template; a first task setting object set, used to set task setting information; a first task state diagram, used to describe the state of the plurality of subtasks and the relationships between the plurality of subtasks; and / or a content block clustering organization method, used to describe the organization of one or more content blocks corresponding to the plurality of subtasks. According to some embodiments, the relationships include nesting, serial connection, and parallel connection, and the first task state diagram is structured and dynamically evolves into a corresponding process task state diagram according to the state of the plurality of subtasks, etc.

[0095] According to some embodiments, the first task state diagram and the corresponding process task state diagram can be maintained and operated in the runtime memory of the user equipment and / or server equipment using corresponding data structures, and can also be displayed in the human-computer interaction interface, but the present invention is not limited thereto.

[0096] According to some embodiments, the first subtask also has first subtask description information and / or identification information.

[0097] According to some embodiments, the first task template also includes one or more reference creation information, which is used as a creation reference for the corresponding sub-task.

[0098] According to some embodiments, the association relationship includes nesting, serial connection, and parallel connection, and the first task state diagram is structured and dynamically evolves into a corresponding process task state diagram according to the state of the multiple sub-tasks, etc. According to some embodiments, the first subtask creation information is used to derive one or more sets of subsequent subtasks of a determined quantity based on the first task constraint information. The first subtask creation information is also used to supplement the subtask description information of any of the subsequent subtasks, and further to supplement the description of the relationships between the subsequent subtasks in any set of subsequent subtasks.

[0099] In S103, the first subtask is provided to the first task creator. For example, the first subtask is provided to the first task creator in the collaborative community through a web application or APP, or the first subtask is provided to the machine intelligence user or intelligent agent (AI AGENT) who is the first task creator through a standard or proprietary protocol.

[0100] In S105, obtain the creation information of the first subtask completed by the creator of the first task.

[0101] According to some embodiments, the first subtask creation information includes one or more first creation modules and quantity information of the one or more first creation modules. The quantity information is used to determine the number of subsequent subtasks in any group of subsequent subtasks based on the first task constraint information. The one or more first creation modules have content information, which is used to supplement the subtask description information of the subsequent subtasks.

[0102] According to some embodiments, when the first subtask creation information includes multiple first creation modules, the first subtask creation information also includes the association relationship between the first creation modules. The association relationship is used to describe the association relationship between subsequent subtasks in any group of subsequent subtasks. For example, according to some embodiments, the association relationship may include dependency relationship and / or process.

[0103] In S107, submit the creation information for the first subtask.

[0104] According to some embodiments, a web application or app can submit the creation information for the first subtask in response to a user confirmation. According to other embodiments, a machine intelligence user or intelligent agent can submit the creation information for the first subtask after completing the task.

[0105] According to some embodiments, the plurality of subtasks also includes a second subtask derived from the first subtask, the second subtask having at least one set of subsequent subtasks from the set or sets of subsequent subtasks. As described later, the system can complete the second subtask directly or through a machine intelligence user / intelligent agent, for example, by generating one or more subsequent third subtasks that the second subtask has, and may provide them, as appropriate, to a creator who is ready to complete the subsequent third subtask.

[0106] Figure 2 A schematic diagram of an apparatus for completing sub-tasks in a collaborative community, according to an example embodiment, is shown.

[0107] According to some embodiments, an apparatus for completing sub-tasks in a collaborative community includes a first acquisition module, a second acquisition module, a sending module, and a submission module. Specifically, the first acquisition module acquires a first sub-task from a first collaborative task; the second acquisition module acquires the creation information of the first sub-task completed by the creator of the first task; the sending module provides the first sub-task to the creator of the first task; and the submission module submits the creation information of the first sub-task. Figure 2 The device shown is Figure 1 The methods shown correspond to each other, and the same content will not be repeated.

[0108] Figure 3 A flowchart illustrating a method for handling subtasks in a collaborative community, according to another example embodiment, is shown.

[0109] See Figure 3 In S201, obtain the third subtask used in the first collaborative task.

[0110] According to some embodiments, the first collaborative task includes multiple subtasks, the multiple subtasks including a first subtask, the first subtask being used to derive a number of third subtasks to be determined, the first collaborative task having a first task template associated with it, the first task template including first task constraint information, the first task constraint information including correspondence information between the first subtask and the third subtask.

[0111] According to some embodiments, when obtaining a third subtask for a first collaborative task, subtask description information for the third subtask is obtained. This subtask description information includes information corresponding to the content information included in the creation information of the first subtask completed by the creator of the first subtask, according to the first task constraint information. For example, as mentioned above, the first task constraint information stipulates that the subtask description information of subsequent subtasks is supplemented based on the content information of the corresponding modules included in the creation information of the first subtask.

[0112] According to some embodiments, as previously described, the plurality of subtasks also includes a second subtask derived from the first subtask, the second subtask having the third subtask.

[0113] According to some embodiments, the first subtask creation information includes a plurality of first creation modules, wherein the quantity information of the plurality of first creation modules is used to determine the quantity of the third subtask based on the first task constraint information. According to some embodiments, the content information of the plurality of first creation modules is used to supplement the subtask description information of the third subtask. According to other embodiments, the association relationship between the plurality of first creation modules is used to describe the association relationship between the third subtasks, as described below with reference to embodiments.

[0114] In S203, the third subtask is provided to the third task creator. This step is similar to S103 above and will not be described again.

[0115] In S205, the creation information of the third sub-task completed by the third task creator is obtained.

[0116] According to some embodiments, a web application or app can respond to user actions and obtain creation information for a third sub-task completed by a third-task creator. According to other embodiments, a smart agent invocation module can obtain creation information for a third sub-task completed by a smart agent.

[0117] In S207, the creation information for the third subtask is submitted. According to some embodiments, a web application or app may submit the creation information for the first subtask in response to a user confirmation. According to other embodiments, a smart agent invoking module or a smart agent may submit the creation information for the first subtask.

[0118] Figure 4 A flowchart illustrating a method for handling subtasks in a collaborative community, according to another example embodiment, is shown.

[0119] See Figure 4 In S301, the first subtask in the first collaborative task is provided to the creator of the first task.

[0120] According to some embodiments, the first collaborative task includes multiple subtasks, the multiple subtasks including the first subtask, the first subtask being used to derive one or more sets of subsequent subtasks of undetermined quantity, the first collaborative task having a first task template associated with it, the first task template including first task constraint information, the first task constraint information including correspondence information between the first subtask and the subsequent subtasks. For example, according to some embodiments, the first task constraint information stipulates that the number of subsequent subtasks is determined by the quantity information of the corresponding modules included in the first subtask creation information, the association between the subsequent subtasks is determined by the association between the corresponding modules included in the first subtask creation information, and / or the subtask description information of the subsequent subtasks is supplemented based on the content information of the corresponding modules included in the first subtask creation information.

[0121] In S303, the creation information of the first subtask completed by the creator of the first task is received.

[0122] According to some embodiments, the first subtask creation information includes multiple first creation modules, wherein the first subtask creation information includes the first creation modules and the quantity information of the first creation modules; the quantity information is used to determine the quantity of the third subtask based on the first task constraint information.

[0123] According to some embodiments, the first subtask creation information includes a first creation module and information on the number of the first creation modules. When deriving one or more sets of subsequent subtasks with determined quantities based on the first task relationship constraint information and the first subtask creation information, the number of subsequent subtasks in any set of subsequent subtasks can be determined according to the quantity information and the first task constraint information.

[0124] According to some embodiments, the first creation module has content information. When deriving one or more sets of subsequent sub-tasks of a determined quantity based on the first task relationship constraint information and the first sub-task creation information, the content information can be used to supplement one or more sets of sub-task description information for the subsequent sub-tasks.

[0125] In S305, based on the first task relationship constraint information and the first subtask creation information, one or more sets of subsequent subtasks of a determined quantity are derived.

[0126] According to some embodiments, the first subtask creation information includes a first creation module and information on the number of the first creation modules. When deriving one or more sets of subsequent subtasks with a determined number based on the first task relationship constraint information and the first subtask creation information, the number of subsequent subtasks in any set of subsequent subtasks can be determined according to the number information and the first task constraint information.

[0127] According to some embodiments, when the first subtask creation information includes multiple first creation modules, the first subtask creation information also includes the association relationships between the multiple first creation modules. When deriving one or more sets of subsequent subtasks of a determined quantity based on the first task constraint information and the first subtask creation information, the association relationships can be used to describe the association relationships between multiple subsequent subtasks in any set of subsequent subtasks.

[0128] According to some embodiments, the plurality of subtasks further includes a second subtask derived from the first subtask, the second subtask having at least one set of subsequent subtasks from the set or plurality of subsequent subtasks. In this case, the second subtask may include the content completed in step S305.

[0129] According to some embodiments, after deriving subsequent subtasks, such as a third subtask, the subsequent subtasks can be assigned to the appropriate task creator.

[0130] The following describes an example of how to complete subtasks in a collaborative community.

[0131] This embodiment takes a collaborative creation task for a themed film and television work as an example to introduce a collaborative method for generating two sets of subsequent sub-tasks during the collaborative creation of audiovisual works.

[0132] Based on some implementation examples, collaborative creation task templates are developed and published.

[0133] Step M.1: The task template creator M inputs the creation information of the task template α(m), including: template description information, initial task status diagram of collaborative creation task (sub-task system), content clustering system, reference creation information, and task setting object.

[0134] The template description information is used to describe the task template. An example of this template description information is as follows: Task Template Name: Theme Film and Television Type II Task Template.

[0135] Task Template Description: This task template is for smart community users to collaboratively create themed films and TV shows in a Type II manner.

[0136] According to some embodiments, a task setting object, TaskSet, is set up in the task template to provide task publishers with inputting task setting information. Before publishing a task, the task publisher must first input the task setting information according to the requirements of the task setting object. An example of the TaskSet object in this template is as follows: Information Block 1: In which community was this task posted?

[0137] Information Block 2: Film / TV Show Theme (Film / TV Show Title or describe the film / TV show theme in the shortest possible words).

[0138] Information Block 3: Film and TV-related information.

[0139] Information Block 4: Whether the task tagging system (including the task revenue distribution plan) will be adjusted, and how.

[0140] According to some embodiments, setting the initial task state diagram includes setting sub-tasks and node relationships. Based on the collaborative creation task decomposition and process management requirements, template creator M sets up an initial task state diagram for the theme film and television drama type II task template. An example of setting up the task state diagram in the form of a data table is shown below. The data table format settings for the first-level sub-tasks (T1, T2, T3, T4) of the task state diagram are shown in Table 1. The data table format settings for the second-level sub-tasks (T2.2 "Scene Scripts" and T3.3 "Scene Script Production") of the task state diagram are shown in Tables 2.1 and 2.2.

[0141] Table 1

[0142]

[0143] In this embodiment, the next-level subtask of a directly fixed-length frame type subtask is a fixed-type next-level subtask, the next-level subtask of an indirectly fixed-length frame type subtask is a conditional next-level subtask, and the next-level subtask of a variable-length frame type subtask is a variable-type next-level subtask.

[0144] Table 2.1 Data table format settings for the second-level subtasks in the task status diagram (T2.2 "Scene Scripts")

[0145] Table 2.2 Data table format settings for the second-level subtask in the task status diagram (T3.3 "Script Creation for Each Scene")

[0146] For the dependent variable-length framework subtasks T2.2 "Scene Scripts" and T3.3 "Scene Script Production", based on the execution content of the prior subtask T2.1 "Overall Script Planning" that T2.2 and T3.3 depend on, determine the number and relationship of the variable-length next-level subtasks T2.2.n "Scene n Script" and T3.3.n "Scene n Script Production" that T2.2 and T3.3 possess.

[0147] According to some embodiments, the data table format settings for the third-level subtask of the task state diagram (T3.3.n "Script Creation for the nth Scene") are shown in Table 3.

[0148] Table 3. Data table format settings for the third-level subtask in the task status diagram (T3.3.n "Script Creation for the nth Scene").

[0149] For the 4th layer subtask in the task state diagram, the number of dependent indeterminate subtasks T3.3.n.3 "Script production for each shot in scene n" is determined based on the execution content of the prior subtask T2.1 "Overall script planning" that T3.3 depends on.

[0150] According to some embodiments, the data table format settings for the fourth-level subtask of the task state diagram (T3.3.n "Nth Scene Creation") are shown in Table 4.

[0151] Table 4

[0152] For the 4th layer subtask in the task state diagram, the dependency-dependent variable-length frame type subtask T3.3.n.3 "Shot scripts for the nth scene", based on the execution content of the prior subtask T2.2.n "Scene script for the nth scene" that T3.3.n.3 depends on, determine the number and relationship of the 5th layer subtask and the dependency-dependent variable-length next layer subtask T3.3.n.3.m "Shot script for the mth scene of the nth scene" that T3.3.n.3 has.

[0153] In some embodiments, for AI or machine intelligence users, the user equipment can read, operate, and maintain the initial task state diagram of the task template in its runtime memory through the data structure of the initial task state diagram in the task template. The user equipment 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.

[0154] Figure 5 This diagram illustrates an example of an overview of the initial task state diagram according to some embodiments.

[0155] 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 runtime memory, the user equipment can also display the initial task state diagram in the user equipment's interactive interface to facilitate human users to intuitively obtain relevant information. For example, in the Theme Movie / TV Show Type II task template, an overview version of the initial task state diagram is shown below. Figure 5 .

[0156] According to some embodiments, in the Theme Movie / TV Show Type II task template, users can click on the frame-type sub-tasks in the initial task status overview to view the next level of sub-tasks.

[0157] According to some embodiments, the T2 "script" and T3 "generation" unfold the next level of sub-tasks. (See also...) Figure 6 .

[0158] A content clustering system and overall content clustering composition method were established. Based on the requirement of assembling the content created by each sub-task into a digital work for the collaborative creation task, the overall content clustering composition method developed by template creator M for the Theme Film & Drama Type II task template is shown in Table 5 below: Table 5

[0159] According to the example embodiment, based on this template, the digital works created for the Theme Film and Drama Type II task are assembled and generated from a framework-type content cluster BC(T3) according to the above "Overall Content Clustering Composition Method".

[0160] According to some embodiments, the content clustering composition of the initial content clustering composition BC(T3, M) "generated" by the template builder M for the framework-type content clustering BlockCluster(T3) is shown in Table 6 below: Table 6

[0161] According to the example embodiment, the initial content clustering composition BC(T3, M) of the frame-type content cluster BC(T3) is generated by assembling one frame-type content cluster BC(T3.3) according to this template.

[0162] The initial composition method of the Level 2 content clustering BC(T3.3, M) "Script Production for Each Scene" is BC(T3.3, M). The template creator M is the initial content clustering composition method of the framework-type content clustering BC(T3.3, M). The content clustering composition method of BC(T3.3, M) is as follows: Table 7

[0163] According to this template, the initial content clustering composition BC(T3.3, M) of the framework-type content clustering BC(T3.3) is generated by assembling N framework-type content clustering BC(T3.3.n) (1≤n≤N). The value of N is determined according to the execution content of subtask T2.1 "Overall Script Planning".

[0164] The initial composition method BC(T3.3.n, M) of the Level 3 content cluster BC(T3.3.n) "Creating the nth Scene", with template setter M, is the content clustering composition method of the initial content clustering composition method BC(T3.3.n, M) of the framework-type content cluster BC(T3.3.n) "Creating the nth Scene". The content clustering composition method is shown in Table 8 below: Table 8

[0165] According to this template, the initial content clustering composition BC(T3.3.n, M) of the frame-type content clustering BC(T3.3.n.3) includes one frame-type content clustering BC(T3.3.n.3).

[0166] According to some embodiments, the initial composition method BC(T3.3.n.3, M) of the fourth-level content cluster BC(T3.3.n.3) "Script Production for Each Shot in the nth Scene", with template creator M being the initial content cluster composition method BC(T3.3.n.3, M) of the frame-type content cluster BC(T3.3.n.3) "Script Production for Each Shot in the nth Scene", is as follows: Table 9 below: Table 9

[0167] According to this template, the initial content clustering composition BC(T3.3.n.3, M) of the framework-type content clustering BC(T3.3.n.3) "Script Production for Each Shot in Scene n" is composed of M. n A content creation block CCBlock(T3.3.n.3.m) (1≤m≤M) n ) is assembled and generated. Where M n The value is determined based on the execution content of subtask T2.2.n "Scene Script".

[0168] According to some embodiments, when creating a task template α(m), the creator m can also create reference creation information for the subtasks of the task template α(m). This allows the creators of the subtasks to create more conveniently based on the reference creation information, rather than starting from scratch. This increases the attractiveness of the task template α(m) to creators, making it more likely to be adopted by the task publisher and finalized as a digital work, thus potentially generating more copyright revenue.

[0169] The reference creative information for developing T2.1 "Overall Script Planning" is as follows: Based on the execution content of T1's story synopsis, provide the ideas and explanations for the overall script planning. Furthermore, specify the number of scenes included in the script using an incremental selection method, and provide an explanation for each scene. After incremental selection, the total number of scenes in T2.1 is determined to be N. The creators of subtask T2.1 are the general director and the creator of T4 final product delivery.

[0170] According to some embodiments, T2.1 is an atomic subtask, and the content clustering is a non-corresponding subtask. The fixed-type next-level subtask belongs to T2, depends on T1, and derives from T2.2. The template creator M defines the execution content reference creation information [T2.1, refer] for T2.1, as shown in the example. Figure 7 As shown.

[0171] The reference creation information for T2.2.n "Scene N script" is formulated. The subtask description information for the third-level subtask T2.2.n "Scene N script" is as follows: Based on the execution content of T2.1 "Overall script planning", provide the script content and related explanations for scene n. Furthermore, specify which shots are included in this scene using incremental selection, and provide the content and related explanations for each shot. After incremental selection, the execution content of T2.2.n determines that the total number of shots in scene n is M. n .

[0172] T2.2.n is an atomic subtask. It's a content clustering non-corresponding subtask. It's a dependency-indeterminate next-level subtask. It belongs to T2, [T2,M], T2.M.2, and [T2.M.2,M]. When n=1, T2.2.1 depends on T2.1 and derives from T2.2.2; when 1<n<N, T2.2.n depends on T2.2.n-1 and derives from T2.2.n+1; when n=N, T2.2.N depends on T2.2.N-1 and derives from T3. The template maker M defines the execution content reference creation information [T2.2.n, refer] for T2.2.n. An example is shown below. Figure 8 As shown.

[0173] According to some embodiments, task template data blocks are generated and task template data packages are published. For details, please refer to the relevant patent applications filed by the applicant in the background section, which will not be repeated here.

[0174] According to some implementation methods, collaborative creation tasks are set up and published. After the task template is published, users can access the task template library through their user devices and select a suitable collaborative creation task template based on their collaborative creation needs for digital works.

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

[0176] After acquiring the task template, the user device can input task setting information into the task setting object of the task template based on their collaborative creation needs for their digital works. This task setting information is provided to the creator, who then inputs creation information based on the task setting information and related sub-task descriptions. The task setting information is also used by the content block generation method to generate the execution content of the content block.

[0177] According to some embodiments, task setting information is entered.

[0178] Step R1: User A accesses the task template library through the user device and selects the theme movie / drama type II task template α(M)15800573.

[0179] Step R2: User A's device obtains the task template content.

[0180] Step R3: User A enters task setting information [TaskSet, A] in the TaskSet object of the task template. This may include the following information blocks: Information Block 1: In which community was this task posted?

[0181] Input: Creative Short Drama Public Group 2

[0182] Information Block 2: Film / TV Show Theme. Include the film / TV show title or a brief description of the theme.

[0183] Input: Missing A.

[0184] Information Block 3: General description of the film and television series.

[0185] Input: Please, all-powerful group, make a short drama.

[0186] Information Block 4: Adjustments to the task tagging system (including the task revenue distribution scheme).

[0187] Input: No adjustments will be made; the default settings for each task tag (including the tags corresponding to the task profit distribution plan) in the task template will be maintained.

[0188] According to some embodiments, task data blocks are generated and task data packets are published. For details, please refer to the relevant patent applications filed by the applicant in the background section, which will not be repeated here.

[0189] According to some embodiments, a task state diagram is set. For example, after a task publisher publishes a task, the task state diagram for the collaborative creation task Task_ID(3396815520) in "Remembering A" is set as the task state diagram. See the example below. Figure 9 Compared to the initial task status diagram in the task template, the task status diagram generated after the task publisher enters the task setting information has been modified in one aspect: "Task setting object" has been updated to "Task setting information".

[0190] According to some embodiments, the data settings of the task state diagram are set, and the node types, node relationships, and node states in the task state diagram are set. For machine intelligence users, the corresponding data structures can be used in the user device and server device to maintain and operate in the device's runtime memory, including the collaborative creation method of the next layer of sub-tasks.

[0191] Viewing the set digital artwork draft: The digital artwork draft corresponding to the collaborative creation task after it has been published is called the set digital artwork draft. It can be understood that the task publisher can also view the set digital artwork draft after setting the collaborative creation task, but before publishing it. The main implementation steps are consistent with those described in this section.

[0192] According to some embodiments, the first process task state diagram for collaborative creation is as follows: Step S1: The user obtains the collaborative creation task Task_ID (3396815520) through the user terminal.

[0193] At this point, Task_ID(n) has no subtasks (including lower-level subtasks) yet being created by collaborating creators; that is, there is no creative content yet being executed. Therefore, the task state diagram of Task_ID(n) obtained by the user at this time is the first-stage task state diagram.

[0194] Step S2: The user client obtains the creation status of the subtask.

[0195] The user client obtains the creation status of each subtask through the task status diagram.

[0196] Based on the hierarchy of the sub-objective system formed after task decomposition, the term "subtask" can also refer to the next level of subtask, the next level of subtask, and so on. The execution content of a subtask can also refer to the execution content of the next level of subtask, the next level of subtask, and so on. This same principle applies when referring to "subtask" and "subtask execution content" later in the text.

[0197] Step S3: Provide the creator with the sub-tasks and the next-level sub-tasks that are in the creative state, so that the creator can input creative information based on the description information of the sub-tasks.

[0198] According to some embodiments, when user a is pushed this task Task_ID (3396815520) as a candidate creator with a high match with T1 "Synopsis", the first process task status diagram of the task Task_ID (3396815520) obtained by user a's client is as follows: Figure 10 As shown.

[0199] Compared to the task status diagram, the first process task status diagram adds a sub-task creation status. Furthermore, for the sub-task T1 "Story Synopsis" which is in the creation state, the top 5 candidate creators with the highest matching degree are set, including users "a, Zou, Ma, Liu, Yang".

[0200] Example 1: Execution content of the plot summary of the atomic subtask T1 (step S4).

[0201] According to some implementation examples, input creation information.

[0202] Step S4.1: Creator a selects subtask T1 "Story Summary" and enters the creation information.

[0203] Creator A selects subtask T1.1 "Plot Summary" and issues a creation request.

[0204] According to some embodiments, a creation information data block is generated and a creation information data packet is published. For details, please refer to the relevant patent applications filed by the applicant in the background section, which will not be repeated here.

[0205] In some embodiments, after the task state diagram is generated, in addition to using the aforementioned data structure to operate and maintain the task state diagram in its runtime memory, the user equipment can also display it in the user's interactive interface. Once T1 "Plot Summary" has executable content, T2 "Script" enters the creation state. See the task state diagram for details. Figure 11 .

[0206] Example 2: User b is the execution content of the overall script plan for the atomic subtask T2.1 (step S5).

[0207] According to some implementation examples, input creation information.

[0208] Step S5.1: Creator b selects subtask T2.1 "Script Overall Planning" and enters the creation information.

[0209] 1) Creator b selects subtask T2.1 and issues a creation request.

[0210] 2) The system pushes the creation content block object of subtask T2.1 to user b, see [link / reference]. Figure 12 .

[0211] 3) User B inputs subtask creation information into the creation content block object of subtask T2.1, see [link / reference]. Figure 13 The number of scenes is N=4.

[0212] 4) Submit the creation information for each sub-task generated by the aforementioned prior actions. For user b, who is a human user, this is done by clicking... Figure 13 The submit button in the upper right corner triggers this action. For user b who is an AI (machine intelligence) user, this action is triggered via program commands.

[0213] 5) Set the current execution content [T2.1,b(1)] of the atomic subtask T2.1 "Overall Script Planning".

[0214] In this step, T2.1 and its execution content [T2.1,b(1)] are specifically described in Table 10 below: Table 10

[0215] Confirm the creation information of each subtask generated by the aforementioned prior actions. If user b is a human user, this is done by clicking... Figure 13 The confirmation button in the upper right corner triggers this action. For user b who is an AI (machine intelligence) user, this action is triggered via program commands.

[0216] According to some embodiments, a creation information data block is generated and a creation information data packet is published. For details, please refer to the relevant patent applications filed by the applicant in the background section, which will not be repeated here.

[0217] According to some embodiments, when Task_ID(n) adds new creative execution content, a new second-process task state diagram can be generated. In some embodiments, in addition to manipulating the task state diagram in its runtime memory using appropriate data structures, the user device can also display the task state diagram in the user device's interactive interface to allow human users to intuitively obtain relevant information.

[0218] After step S5 is completed, see the second-stage task status diagram for the collaborative creation task Task_ID(3396815520) of "Remembering A". Figure 14 .

[0219] According to some implementations, machine intelligence automatically generates T2.2 "Scene Script" creation information.

[0220] Steps S5.1 and T2.2 are completed automatically by machine intelligence. After the execution content [T2.1,b(1)] is published and T2.2 becomes a creative state, the task scheduling subsystem assigns the task of generating the execution content of the framework subtask T2.2 derived from the execution content [T2.1,b(1)] to the process management subsystem according to the task template setting.

[0221] The process management subsystem reads the framework-type subtask T2.2 "Overall Script Planning", inputs the creative information derived from the execution content [T2.1, b(1)], and generates a set of subsequent subtasks, as described in detail below: Subtask identifier: T2.M.2.System(1).n{[T2.1,b(1)]}, which can be abbreviated as T2.2.n{[T2.1,b(1)]}, the script for the nth scene. n is a natural number, 1≤n≤4.

[0222] According to some embodiments, the subtask description is as follows: Based on the execution content of the overall script plan in T2.1, provide the script and description for the nth scene. Furthermore, specify which shots are included in this scene using an incremental selection method, and provide a description for each shot, including dialogue. The execution content of T2.2.n{[T2.1,b(1)]} determines that the total number of shots in the nth scene is M. n .

[0223] Atomic subtasks, content clustering non-corresponding subtasks, and dependency-indeterminate next-level subtasks.

[0224] Belongs to T2, [T2,M], T2.M.2, [T2.M.2,system(1)].

[0225] When n=1, T2.2.1{[T2.1,b(1)]} depends on T2.1 and [T2.1,b(1)], and derives T2.2.2{[T2.1,b(1)]}; When 1 < n < 4, T2.2.n{[T2.1,b(1)]} depends on T2.2.n-1{[T2.1,b(1)]} and derives from T2.2.n+1{[T2.1,b(1)]}; When n=4, T2.2.4 depends on T2.2.3{[T2.1,b(1)]} and derives from T3.

[0226] Step S5.3: The collaborative community receives the creation information of subtask T2.2 from the process management subsystem and generates the creation information data block DB[T2.2, system (1)] corresponding to the creation information.

[0227] Step S5.4: The process management subsystem stores the creation information data block DB[T2.2, system (1)] and generates the creation information data block access address.

[0228] Step S5.5: The user device or server generates a creation information data packet DP{[T2.2,System1)]{[T2.1,b(1)]}.Task_ID(3396815520)}, which includes the following: the storage address of the creation information data block, the data fingerprint of the creation information data block, and the creator's identity information.

[0229] Step S5.6: The process management subsystem publishes the creation information data packet, so that relevant users in the collaborative creation community can access or be pushed to the creation information data packet.

[0230] After adding the execution content [T2.2,System(1)]{[T2.1,b(1)]} to Task_ID(3396815520), a new second process task state diagram can be generated. See [T2.2,System(1)]{[T2.1,b(1)]}. Figure 15 .

[0231] Depend on Figure 15 As can be seen, the execution content [T2.2, System] is not shown in the task state diagram. However, the next level of subtasks of the execution content [T2.2, System] is determined to be N=4 items, namely T2.2.1{[T2.1,b(1)]} Scene 1 script to T2.2.4{[T2.1,b(1)]} Scene 4 script.

[0232] Example 3: Atomic subtask T2.2.1{[T2.1,b(1)]} Scenario 1 script execution content (step S6)

[0233] According to some implementation examples, input creation information.

[0234] Step S6.1: Creator "Wang" selects subtask T2.2.1{[T2.1,b(1)]} Scene 1 script and inputs creation information.

[0235] 1) After the execution content [T2.2, Machine Tool (1)] is published, in the second task status diagram of the collaborative creation task Task_ID (3396815520), the T2 script has the third-level sub-tasks T2.2.1{[T2.1,b(1)]} Scene 1 script to T2.2.4{[T2.1,b(1)]} Scene 4 script. Among them, T2.2.1{[T2.1,b(1)]} Scene 1 script is in the creative state. The task scheduling subsystem pushes this sub-task to the five users with the highest matching degree: Sun, Wang, Zhou, Wu, and Zheng.

[0236] 2) Creator Wang selects the subtask T2.2.1{[T2.1,b(1)]} “Scene 1 script” and issues a creation request.

[0237] 3) User King's user device retrieves the content block object created by subtask T2.2.1{[T2.1,b(1)]}, such as Figure 16 As shown.

[0238] 4) User Wang inputs the subtask creation information into the creation content block object of subtask T2.2.1{[T2.1,b(1)]}, such as... Figure 17 As shown.

[0239] 5) Set the current execution content [T2.2.1, Wang(1)]{[T2.1, b(1)]} of the atomic subtask T2.2.1{[T2.1, b(1)]} "Scene 1 Script" as shown in Table 11 below: Table 11

[0240] Save the creation information of each subtask generated by the aforementioned prior actions. User Wang is a human user who clicks... Figure 17 The save button in the upper right corner triggers this action.

[0241] Send and confirm the creation information of each subtask generated by the aforementioned prior actions, and user Wang clicks... Figure 17 Click the confirmation button in the upper right corner to trigger this action.

[0242] According to some embodiments, a creation information data block is generated and a creation information data packet is published. For details, please refer to the relevant patent applications filed by the applicant in the background section, which will not be repeated here.

[0243] Figure 18The second process task state diagram is shown according to some embodiments of Task_ID (3396815520).

[0244] According to some embodiments, after step S6 is completed, the second process task state diagram of task Task_ID (3396815520) is shown in Figure 18.

[0245] With the development of collaborative creation, the next-level sub-tasks of the framework sub-tasks T2 "Script" and T3 "Generation," namely T3.1 "Global Resource Planning" and T3.2 "Global Resource Generation," all have executable content. T3.3 "Scene Script Creation" changes from a non-creative state to a creative state. Figure 19 As shown.

[0246] Example 4: Execution content of each scenario script in framework subtask T3.3 (step S7).

[0247] According to some implementation examples, input creation information.

[0248] Step S7.1: After T3.3 "Script Creation for Each Scene" changes from an uncreative state to a creative state, T3.3 is automatically completed by machine intelligence according to the task template settings. The task scheduling subsystem assigns the task of generating the subtask T3.3 execution content derived from the execution content [T2.1,b(1)] to the process management subsystem with the username "Machine Engineer".

[0249] Step S7.2: The machine intelligence user "Machine Engineer" reads the framework subtask T3.3 "Script Creation for Each Scene" and inputs the creation information derived from the execution content [T2.1,b(1)].

[0250] 1) The machine intelligence user "Machine Engineer" reads subtask T3.3 and issues a creation request to derive the execution content of T3.3 based on the execution content [T2.1,b(1)].

[0251] 2) The system pushes a subtask T3.3 creation content block object (based on the T3.3 data table format settings in section 5.1.3.1) to the user "Machine". The creation content block object is derived from the execution content [T2.1,b(1)].

[0252] 3) The user "Mechanic" inputs the subtask creation information (that is, the creation content information of the execution content [T3.3,Mechanic(1)]{[T2.1,b(1)]} of the framework subtask) into the creation content block object of subtask 3.3. Among them, according to the execution content [T2.1,b(1)], the number of scenes N=4, as shown in Table 12 below.

[0253] The data table format of the second-level subtask in the task status diagram (T3.3 "Script Creation for Each Scene") is set according to the execution content [T3.3, Machinist (1)]{[T2.1,b (1)]} derived from the execution content [T2.1,b(1)].

[0254] Table 12

[0255] Set the current execution composition of the framework-type content clustering BC(T3.3) "Each Scene Production" as BC{T3.3,[T3.3,Mechanical Industry (1)]{[T2.1,b(1)]}}.

[0256] The content clustering composition method BC{T3.3,[T3.3,Mechanic(1)]{[T2.1,b(1)]}} formulated by user "Mechanic" for the framework-type content clustering BC(T3.3) "Production of Various Scenes" is shown in Table 13 below: Table 13

[0257] According to the example embodiment, the current execution composition BC{T3.3,[T3.3,machine(1)]{[T2.1,b(1)]}} formulated by user "mechanic" for the frame-type content cluster BC(T3.3) is generated by assembling 4 frame-type content clusters BC(T3.3.n){[T2.1,b(1)]} (1≤n≤4).

[0258] The user "mechanic" triggers the submission of the creation information of each sub-task generated by the aforementioned prior actions through program instructions, and the user "mechanic" confirms the creation information of each sub-task generated by the aforementioned prior actions through program instructions.

[0259] According to some embodiments, a creation information data block is generated and a creation information data packet is published. For details, please refer to the relevant patent applications filed by the applicant in the background section, which will not be repeated here.

[0260] According to some embodiments, after adding creative execution content [T3.3, mechanics(1)]{[T2.1, b(1)]} to task_ID(3396815520), a new second process task state diagram can be generated. See Figure 20 .

[0261] With the commencement of collaborative creation, the atomic subtask T3.3.1.1 "Scene 1 Planning" has executable content [T3.3.1.1, Peng (1)], and the lower-level atomic subtasks of the framework subtask T3.3.1.2 "Scene 1 Resource Generation" also have executable content. At this time, the framework subtask T3.3.1.3 "Scene 1 Shot Script Production" is in a creative state, such as Figure 21 As shown.

[0262] Example 5: Execution content of framework subtask T3.3.1.3 (step S8).

[0263] According to some implementation examples, input creation information.

[0264] Step S8.1: After the script production for each shot in Scene 1 (T3.3.1.3) changes from a non-creative state to a creative state, T3.3.1.3 is automatically completed by machine intelligence according to the task template settings. The task scheduling subsystem assigns the task of generating the subtask T3.3.1.3 derived from the execution content of Scene 1 script [T2.2.1, Wang (1)]{[T2.1, b (1)]} to the process management subsystem with the username "Mechanic".

[0265] Step S8.2: The machine intelligence user "Machine Engineer" reads the framework subtask T3.3.1.3 "Creation of scripts for each shot in the first scene", and inputs the creation information derived from the execution content [T2.2.1, Wang (1)]{[T2.1, b (1)]}.

[0266] 1) The machine intelligence user "Jigong" reads the subtask T3.3.1.3 and issues a creation request to derive the execution content of T3.3.1.3 based on the execution content [T2.2.1, Wang (1)]{[T2.1, b (1)]}.

[0267] 2) The system pushes the subtask T3.3.1.3 creation content block object to the user "Machinery" (formed based on the T3.3.n.3 data table format set in section 5.1.3.1), and the creation content block object is derived from the execution content [T2.2.1, Wang (1)]{[T2.1, b (1)]}.

[0268] 3) User "Mechanic" inputs the subtask creation information (i.e., the creation content information of the execution content [T3.3.1.3,Mechanic(1)]{[T2.2.1,Wang(1)]{[T2.1,b(1)]}}) in the creation content block object of subtask 3.3.1.3. In this case, according to the execution content {[T2.2.1,Wang(1)]{[T2.1,b(1)]}}, the number of shots M1=3, as shown in Table 14 below.

[0269] The 4th layer subtask T3.3.1.3 "Script creation for each shot in scene 1" is set up with the data table format of the execution content [T3.3.1.3, Machine Worker (1)]{[T2.2.1, Wang (1)][T2.1, b (1)]} derived from the execution content [T2.2.1, Wang (1)][T2.1, b (1)]}.

[0270] Table 14

[0271] Set the current execution composition mode BC of the framework content clustering BC (T3.3.1.3) "Scene 1 Each Shot Script" as BC{T3.3.1.3, [T3.3.1.3, machinist (1)]{[T2.2.1, Wang (1)][T2.1, b (1)]}}.

[0272] The current execution composition mode BC{T3.3.1.3, [T3.3.1.3, machinist (1)]{[T2.2.1, Wang (1)][T2.1, b (1)]}} formulated by the user "machinist" for the framework content clustering BC (T3.3.1.3) "Scene 1 Each Shot Production" is as follows in Table 15: Table 15

[0273] According to the exemplary embodiment, the current execution composition mode BC{T3.3.1.3, [T3.3.1.3, machinist (1)]{[T2.2.1, Wang (1)][T2.1, b (1)]}} formulated by the user "machinist" for the framework content clustering BC (T3.3.1.3) "Shot Script Production for Each Shot in the First Scene" is composed of M 1 creative content blocks CCBlock (T3.3.1.3.m) (1 ≤ m ≤ M 1 ). Among them, the value of M 1 is determined according to the execution content [T2.2.1, Wang (1)][T2.1, b (1)] of the subtask T2.2.1 "First Scene Script", and it is determined that M 1 = 3.

[0274] The user "machinist" triggers and submits the creation information of each subtask generated by the foregoing prior actions through program instructions, and the user "machinist" confirms the creation information of each subtask generated by the foregoing prior actions through program instructions.

[0275] According to some embodiments, a creative information data block is generated and a creative information data packet is published. For details, reference can be made to the relevant patent applications filed by the present applicant in the background art, which will not be elaborated herein.

[0276] According to some embodiments, refer to Figure 22 , after the task Task_ID(3396815520) adds the creative execution content [T3.3.1.3, machinist (1)]{[T2.2.1, Wang (1)][T2.1, b (1)]}, a new second process task status diagram can be generated.

[0277] Example 6: Execution content (step S9) of the atomic subtask T3.3.1.3.3, the 3rd shot script of the 1st scene.

[0278] According to some embodiments, input creation information.

[0279] Step S9.1: The creator "Luo" selects the subtask T3.3.1.3.3 {[T2.2.1, Wang (1)][T2.1, b (1)]} "the 3rd shot script of the 1st scene" and inputs creation information.

[0280] 1) After the execution content [T3.3.1.3, Machinist (1)] {[T2.2.1, Wang (1)][T2.1, b (1)]} is released, in the second task status diagram of the collaborative creation task Task_ID(3396815520), T3.3.1.3 "production of each shot script of the 1st scene" has the 5th layer subtasks: T3.3.1.3.1 {[T2.2.1, Wang (1)][T2.1, b (1)]} "the 1st shot script of the 1st scene" to T3.3.1.3.3 {[T2.2.1, Wang (1)][T2.1, b (1)]} "the 3rd shot script of the 1st scene". These 5th layer subtasks are all in the creatable state. Among them, the task scheduling subsystem pushes the subtask T3.3.1.3.3 {[T2.2.1, Wang (1)][T2.1, b (1)]} "the 3rd shot script of the 1st scene" to the top five users with high matching degrees: Liu, Zhang, Luo, Meng, Duan.

[0281] 2) The creator Luo selects the subtask T3.3.1.3.3 {[T2.2.1, Wang (1)][T2.1, b (1)]} "the 3rd shot script of the 1st scene" and sends a creation request. The user device of user Luo retrieves the creation content block object of the subtask T3.3.1.3.3 {[T2.2.1, Wang (1)][T2.1, b (1)]}, such as Figure 23 shown.

[0282] 3) User Luo creates the 3rd shot script of the 1st scene according to the task objective, the execution content of each prior subtask and the description information of this subtask, and inputs the created script file (such as a video file in MP4 format) to the above creation content block object, such as Figure 24 shown.

[0283] 4) Set the current execution content [T3.3.1.3.3, Luo (1)] {[T2.2.1, Wang (1)].[T2.1, b (1)]} information of the atomic subtask T3.3.1.3.3 {[T2.2.1, Wang (1)][T2.1, b (1)]} "the 3rd shot script of the 1st scene", see Table 16.

[0284] Table 16

[0285] 5) Set the current execution creation content block CCBlock(T3.3.1.3.3) corresponding to the creation content block CCBlock(T3.3.1.3.3){[T2.2.1, Wang(1)][T2.1, b(1)]}, see Table 17 for the information of the current execution creation content block CCBlock(T3.3.1.3.3,[T3.3.1.3.3, Luo(1)]){[T2.2.1, Wang(1)][T2.1, b(1)]}.

[0286] Table 17

[0287] User Luo clicks Figure 24 the confirmation button in the upper right corner to confirm the creation information of each subtask generated by the above prior actions, and confirm the creation information of each subtask generated by the above prior actions.

[0288] According to some embodiments, a creation information data block is generated and a creation information data packet is published. For details, reference can be made to the relevant patent applications filed by the applicant in the background art, which will not be elaborated here.

[0289] According to some embodiments, after the task Task_ID(3396815520) adds the creative execution content [T3.3.1.3.3, Luo(1)]{[T2.2.1, Wang(1)].[T2.1, b(1)]}, a new second process task status diagram can be generated, see Figure 25 .

[0290] In practical applications, the framework subtask T3.3.1.3 "Production of Shot Scripts for Each Scene in the First Scene" and the execution content [T3.3.1.3, Machinist(1)]{[T2.2.1, Wang(1)][T2.1, b(1)]} may not be displayed in the task status diagram, as shown Figure 26 as follows.

[0291] According to some embodiments, viewing digital works: 1) During the collaborative creation task, the user can click "View Work" above the task status diagram to trigger the process of viewing the work, so as to view the work that has been formed for Task_ID(3396815520) "Missing A". For machine intelligent users, the process of viewing the work can be triggered through the program interface.

[0292] 2) After the process of viewing the work is triggered, the system first generates an information snapshot of Task_ID(3396815520) "Missing A". The information snapshot is a subset of the task status diagram, which includes the execution content of each content clustering corresponding subtask.

[0293] For example, among the various subtasks included in Task_ID(3396815520), the content clustering corresponding subtasks include the framework subtask T3 "Generate", the framework subtask T3.3 "Production of scripts for each scenario", the framework subtask T3.3.n "Production of the script for the nth scenario" (1 ≤ n ≤ N, where the value of N is determined according to the execution content of T2.1 "Overall script planning"), the framework subtask T3.3.n.3 "Production of scripts for each shot in the nth scenario", and the atomic subtask T3.3.n.3.m "Production of the script for the mth shot in the nth scenario" (1 ≤ m ≤ M n , M n whose value is determined according to the execution content of T2.2.n "Script for the nth scenario"). Among them, the execution content of each framework subtask includes content blocks, but does not directly correspond to content blocks; the execution content of each atomic subtask directly corresponds to creative content blocks.

[0294] When the process of viewing a work is triggered, in the task status diagram of Task_ID(3396815520) "Missing A", assuming that T3.3.1.3.3 "Production of the script for the 3rd shot in the 1st scenario", T3.3.2.3.1 "Production of the script for the 1st shot in the 2nd scenario", and T3.3.2.3.4 "Production of the script for the 4th shot in the 2nd scenario" have execution content, the current information snapshot is as Figure 27 shown.

[0295] 3) Based on the information snapshot, the system presents the current digital work to the user. Specifically, the system presents two work segments that have been formed in Task_ID(3396815520) "Missing A" to the user.

[0296] Work segment 1 is formed by continuously assembling the work content included in the creative content block CCBlock(T3.3.1.3.3, [T3.3.1.3.3, Luo(1)]){[T2.2.1, Wang(1)][T2.1, b(1)]} corresponding to the execution content [T3.3.1.3.3, Luo(1)]{[T2.2.1, Wang(1)].[T2.1, b(1)]} and the work content included in the creative content block CCBlock(T3.3.2.3.1, [T3.3.2.3.1, Meng(1)]){[T2.2.1, Wang(1)][T2.1, b(1)]} corresponding to the execution content [T3.3.2.3.1, Meng(1)]{[T2.2.1, Wang(1)].[T2.1, b(1)]}.

[0297] Work Fragment 2 is formed by the work content included in the creation content block CCBlock(T3.3.2.3.4,[T3.3.2.3.4,Huang(1)]{[T2.2.1,Wang(1)].[T2.1,b(1)]} corresponding to the execution content [T3.3.2.3.4,Huang(1)]){[T2.2.1,Wang(1)][T2.1,b(1)]}}.

[0298] According to some implementations, users can independently view the two existing work fragments of Task_ID(3396815520) "Remembering A".

[0299] Example 7: View the complete digital work (step S10).

[0300] As collaborative creation progresses, the lower-level subtasks of the framework subtask T3.3 for each scene script production, including the atomic subtasks T3.3.n.3.m "Script Production for Scene n, Shot m" (1≤n≤N, where the value of N is determined based on the execution content of T2.1 "Overall Script Planning"; 1≤m≤M) are implemented. n M n The value of is determined based on the execution content of T2.2.n "Scene n script" and all have execution content. At this point, Task_ID(3396815520) "Remembering A" has formed a complete draft.

[0301] 1) Users can click "View Works" above the task status diagram to trigger the process of viewing works, thereby viewing the currently created work for Task_ID(3396815520) "Remembering A". For machine intelligence users, the process of viewing works can be triggered through the program interface.

[0302] 2) After the process of viewing the work is triggered, the system first generates a snapshot of the information for Task_ID(3396815520) "Remembering A". Currently, Task_ID(3396815520) "Remembering A" has a complete draft, and the snapshot is as follows. Figure 28 As shown.

[0303] Based on the information snapshot, the system presents the current digital work to the user. Specifically, the system presents the user with the complete manuscript currently created for Task_ID(3396815520) "Remembering A".

[0304] The complete manuscript consists of one fragment, which is formed by assembling the content of the creation content block CCBlock(T3.3.1.3.1,[T3.3.1.3.1,Zou(1)]{[T2.2.1,Wang(1)].[T2.1,b(1)]} corresponding to the executed content [T3.3.1.3.1,Zou(1)]){[T2.2.1,Wang(1)][T2.1,b(1)]}} according to the content block relationship attributes.

[0305] This invention takes a collaborative creation task for scientific and technological innovation as an example to introduce a collaborative method for handling a set of subsequent sub-tasks during the collaborative creation task. The intelligent community has a user service subsystem responsible for user registration, login, user identity information management, and user intelligent tag management. Users in the intelligent community include various identity types, such as: human expert users, machine intelligence community users, machine intelligence resource users, and platform support users.

[0306] According to some implementation examples, user E initiates a scientific and technological invention creation task. User E feels that an idea about a braces-style toothbrush is very good and decides to initiate a collaborative scientific and technological invention creation task to make a product based on this idea.

[0307] Step R1: To initiate this collaborative creation task for scientific and technological inventions, user E first selects the "Collaborative Creation of Scientific and Technological Inventions K" task template (task template number 83965) through the user device.

[0308] The task template includes task template description information, initial task status diagram for collaborative creation (sub-task system), task tag system (including task revenue distribution plan), content clustering system, reference creation information, and task setting object.

[0309] According to some embodiments, the task template description information is a task template prepared for the Kth type of collaborative creation activity for scientific and technological innovation. The task template provides process management services for collaborative creation activities for scientific and technological innovation, from ideation to seed round financing, including market research and demand analysis, solution development, patent mining and application, prototype verification product development, and business plan writing.

[0310] Based on the requirements of collaborative creation task decomposition and process management, the template creator M created an initial task status diagram for the "Science and Technology Innovation and Invention Collaborative Creation K" task template, which was set up in the form of a data table.

[0311] For the data table format settings of the first-level subtasks (T1, T2, T3, T4, T5) in the task status diagram, please refer to Table 18.

[0312] Table 18

[0313]

[0314] The data table format settings for the second-level subtask in the task status diagram (T4.2 "Development Division of Labor and Collaboration") are shown in Table 19.

[0315] Table 19

[0316] The initial task state diagram (sub-task system) for collaborative creation: Level 1 sub-tasks are as follows: Figure 29 The initial task state diagram (sub-task system) for collaborative creation; the second-level sub-tasks in T4 prototype product development are as follows: Figure 30 .

[0317] According to some embodiments, task setting information is entered.

[0318] Step R2: User E's user device obtains the task template content.

[0319] Step R3: User E enters task setting information [TaskSet,E] in the TaskSet object of the task template. This may include the following information blocks: Information Block 1: In which community was this task posted?

[0320] Input: Public community for scientific and technological innovation and invention.

[0321] Information Block 2: Scientific and Technological Invention Theme. Invention name or describe the invention theme in the shortest possible terms.

[0322] Input: A toothbrush with a ferrule that automatically performs the Bass brushing technique.

[0323] Information block 3: General description of the invention.

[0324] Input: For over a thousand years, from manual to electric toothbrushes, all toothbrushes in the world have operated with all bristles moving in the same uniform way. If we could invent a toothbrush where each bristle automatically performs a personalized Bass brushing motion according to its corresponding tooth area, we would have reinvented the toothbrush, benefiting humanity. We eagerly await the creation of such a toothbrush by the all-powerful group.

[0325] Information Block 4: Task Tagging System (including Task Reward Distribution Scheme).

[0326] Input: No adjustments will be made; the default settings for each task tag (including the tags corresponding to the task profit distribution plan) in the task template will be maintained.

[0327] According to some embodiments, a task data block is generated. After the task setting subsystem confirms that the task setting information is complete and valid, the task management subsystem generates a system-wide unique task number Task_ID (928527) for this task and generates the corresponding task data block DB{Task_ID(928527)}.

[0328] The task data block DB{Task_ID(928527)} includes the following: Task template information. "Science and Technology Innovation and Invention Collaborative Creation K" task template, task template number 83965.

[0329] Task setting information. This section contains various blocks of information related to the task settings entered by the user.

[0330] The Task ID (928527) is unique across the entire system.

[0331] The task publisher's identity information, including the user identifier and / or the user's public key.

[0332] The data block identifier for this task is DB[Task_ID(928527)].

[0333] According to some embodiments, a task release request is submitted. After user E inputs task setting information and generates task data blocks, the task release request is submitted.

[0334] After receiving the task release application submitted by user E, the smart community needs to review whether the content in the task data block meets the task release conditions.

[0335] After review, the task data block DB{Task_ID(928527)} meets the task release requirements and has been approved.

[0336] According to some embodiments, a task data package is generated and published based on the task data block, as can be seen in the relevant patent application filed by the applicant in the background art, which will not be repeated here.

[0337] According to some embodiments, after the task publisher releases the task, the task status diagram of the collaborative creation task "Automatic Bass Brushing Technique Toothbrush Task_ID(928527)" is the task status diagram, see [link to relevant documentation]. Figure 31 ...

[0338] According to some implementation examples, collaborative creation can be carried out.

[0339] After the task is released, relevant users in the smart community can access or be pushed to the task, obtain the task, and participate in collaborative creation. As collaborative creation progresses, each lower-level atomic subtask of subtask T4 "Patent Mining and Application" also has its own execution content. At this time, subtask T4.1 "Overall Development Planning" of T4 "Prototype Product Development" is in a creative state, such as... Figure 32 As shown.

[0340] Step S1: Execution of the overall development plan for the atomic subtask T4.1

[0341] According to some implementation examples, input creation information.

[0342] Step S1.1: Creator b selects subtask T4.1 "Development Master Plan" and enters the creation information.

[0343] 1) Creator b selects subtask T4.1 and issues a creation request.

[0344] 2) User b's user device retrieves the creation content block object of subtask T4.1.

[0345] For details on the creation of content block objects in subtask T4.1, please refer to the relevant page. Figure 33 and Figure 34 Based on the content block object created in subtask T4.1, the creator of this subtask is required to propose an overall plan for the development of the prototype product, taking the role of the chief engineer, and determine the number of modules required for the prototype product development, the content information of each module, and the relationships between the modules. The creation information in T4.1 will be used to determine the next subtask in the subsequent subtask T4.2 "Development Division of Labor and Collaboration".

[0346] 3) User B inputs subtask creation information into the creation content block object of subtask T4.1, where the total number of development subtasks Y=9, see... Figure 35 .

[0347] 3.1) User b inputs creation information into subtask T4.1 "Overall Development Plan". See the example of some content on the relevant instructions page. Figure 36 .

[0348] 3.2) The creation information that user b inputs into subtask T4.1 "Overall Development Plan" may also include other tag information set for the next level of subtasks in T4.2 "Development Division of Labor and Collaboration".

[0349] For example, following product development work practices, "Product Development Manager" user B sets themselves as the creator of subtasks T4.2.8 "Software and Hardware Integration" and T4.2.9 "System Integration and Acceptance". In other words, they assign subtasks T4.2.8 and T4.2.9 to themselves.

[0350] 4) Set the current execution content [T4.1,b(1)] of the atomic subtask T4.1 "Overall Development Plan".

[0351] In this step, T4.1 and its execution content [T4.1,b(1)] are specifically described in Table 22 below: Table 22

[0352] Save all creation information generated by the aforementioned prior actions. For the case where user b is a human user, through clicking... Figure 36 The save button in the upper right corner triggers this action. For user b who is an AI (machine intelligence) user, this action is triggered via program commands.

[0353] User B confirms the creation information of each subtask generated by the aforementioned prior actions.

[0354] According to some embodiments, a creation information data block is generated and a creation information data packet is published. For details, please refer to the relevant patent applications filed by the applicant in the background section, which will not be repeated here.

[0355] According to some embodiments, a second process task state diagram.

[0356] When a new creative execution content [T4.1,b(1)] is added to Task_ID(n), a new second process task state diagram can be generated.

[0357] In some embodiments, in addition to using the corresponding data structure to operate the task state diagram in its runtime memory, the user equipment can also display the task state diagram in the user equipment's interactive interface so that human users can intuitively obtain relevant information.

[0358] After step S1 is completed, the second process task status diagram of the collaborative creation task Task_ID(928527) for "Automatic Bass Brushing Technique Toothbrush" is as follows: Figure 37 As shown.

[0359] Step S2: Creation information for framework-type subtask T4.2 "Development Division of Labor and Collaboration".

[0360] According to some embodiments, machine intelligence automatically generates creation information for T4.2 "Development Division of Labor and Collaboration".

[0361] After step S1 is completed, the T4.2 development collaboration changes from a non-creative state to a creative state. The following is step S2, which generates and publishes the execution content of the framework-type subtask T4.2 "Development Collaboration".

[0362] Step S2.1: According to the task template settings, T4.2 is automatically completed by machine intelligence. After the execution content [T4.1,b(1)] is published and T4.2 becomes a creative state, the task scheduling subsystem assigns the task of generating the framework subtask T4.2 execution content derived from the execution content [T4.1,b(1)] to the process management subsystem with the username "Machinery".

[0363] Step S2.2: The machine intelligence user "Machine Engineer" reads the framework subtask T4.2 "Development Division of Labor and Collaboration" and inputs the creation information derived from the execution content [T4.1,b(1)].

[0364] 1) The machine intelligence user "Machine Engineer" reads subtask T4.2 and issues a creation request to derive the execution content of T4.2 based on the execution content [T4.1,b(1)].

[0365] 2) The system pushes the subtask T4.2 to the user "mechanic" to create a content block object, which is derived from the execution content [T4.1,b(1)].

[0366] 3) The user "mechanic" inputs the subtask creation information (that is, the creation content information of the execution content [T4.2, mechanic (1)] of the framework subtask) into the creation content block object of subtask T4.2. Among them, according to the execution content [T4.1, b (1)], the number of development subtasks Y=9.

[0367] Table 23 below shows the data table format settings for the second-level subtask (T4.2 "Development Division of Labor and Collaboration") in the task state diagram, which is derived from the execution content [T4.1,b(1)]{[T4.1,b(1)]}.

[0368] Table 23

[0369]

[0370] The user "mechanic" triggers the submission of various sub-task creation information generated by the aforementioned prior actions through program instructions.

[0371] The user "mechanic" confirms the creation information of each subtask generated by the aforementioned prior actions through program instructions.

[0372] According to some embodiments, the creator machine tool receives the creation information of subtask T2.2, generates the creation information data block DB[T4.2, machine tool (1)]{[T4.1, b (1)]} corresponding to the creation information, and publishes the creation information data packet.

[0373] According to some embodiments, a second process task state diagram.

[0374] After adding the creative execution content [T4.2,Mechanical Industry (1)]{[T4.1,b(1)]} to Task_ID(928527), a new second-process task state diagram can be generated. See [T4.2,Mechanical Industry (1)]{[T4.1,b(1)]}. Figure 38 .Depend on Figure 38 As can be seen, the execution content [T4.2, mechanics(1)]{[T4.1, b(1)]} is not shown in the task status diagram. The number of sub-tasks at the next level of this execution content is determined to be Y=9, namely T4.2.1{[T4.1, b(1)]} User dental arch 3D digital model acquisition ~ T4.2.9{[T4.1, b(1)]} System integration and acceptance.

[0375] Figure 39 A block diagram of a computing device according to an exemplary embodiment of the present invention is shown.

[0376] like Figure 39 As shown, the computing device 30 includes a processor 12 and a memory 14. The computing device 30 may also include a bus 22, a network interface 16, and an I / O interface 18. The processor 12, memory 14, network interface 16, and I / O interface 18 can communicate with each other via the bus 22.

[0377] The processor 12 may include one or more general-purpose CPUs (Central Processing Units), microprocessors, or application-specific integrated circuits, etc., for executing relevant program instructions.

[0378] Memory 14 may include a machine system readable medium in the form of volatile memory, such as random access memory (RAM), read-only memory (ROM), and / or cache memory. Memory 14 is used to store one or more programs containing instructions, as well as data. Processor 12 may read the instructions stored in memory 14 to perform the methods described above according to embodiments of the present invention.

[0379] The computing device 30 can also communicate with one or more networks via the network interface 16. The network interface 16 can be a wireless network interface.

[0380] Bus 22 can include address bus, data bus, control bus, etc. Bus 22 provides a path for exchanging information between components.

[0381] It should be noted that, in specific implementations, the computing device 30 may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the device described above may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0382] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, as well as magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), network storage devices, cloud storage devices, or any type of medium or device suitable for storing instructions and / or data.

[0383] This invention also provides a computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods described in the above method embodiments.

[0384] Those skilled in the art will clearly understand that the technical solutions of the present invention can be implemented by means of software and / or hardware. In this specification, "unit" and "module" refer to software and / or hardware capable of independently performing or cooperating with other components to perform a specific function, wherein the hardware may be, for example, a field-programmable gate array (FPGA), an integrated circuit, etc.

[0385] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0386] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0387] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between devices or units may be electrical or other forms.

[0388] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0389] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0390] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device. Based on this understanding, the technical solution of the present invention, in essence, 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. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention.

[0391] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0392] Exemplary embodiments of the present invention have been specifically shown and described above. It should be understood that the present invention is not limited to the detailed structures, arrangements, or implementations described herein; rather, the present invention is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended provisions.

Claims

1. A method for processing subtasks in a collaborative community, characterized by, The method comprises: obtaining a first subtask in a first collaborative task, the first collaborative task comprising a plurality of subtasks, the plurality of subtasks comprising the first subtask, the first subtask being used to derive one or more groups of a plurality of subsequent subtasks with an undetermined number, the first collaborative task having a first task template associated therewith, the first task template comprising first task constraint information, the first task constraint information comprising correspondence information between the first subtask and the subsequent subtasks; providing the first subtask to a first task creator; obtaining first subtask creation information completed by the first task creator; submitting the first subtask creation information, wherein the first subtask creation information is used to derive one or more groups of the subsequent subtasks with a determined number according to the first task constraint information.

2. The method of claim 1, wherein, The first subtask creation information is also used to supplement subtask description information of any of the subsequent subtasks.

3. The method of claim 1, wherein, The first subtask creation information is also used to supplement an association relationship between the subsequent subtasks in any group of the subsequent subtasks.

4. The method of claim 1, wherein, The first subtask creation information comprises one or more first creation modules and quantity information of the one or more first creation modules, the quantity information being used to determine a number of the subsequent subtasks in any group of the subsequent subtasks according to the first task constraint information.

5. The method of claim 4, wherein, The one or more first creation modules have content information, and the content information is used to supplement the subtask description information of the subsequent subtasks.

6. The method of claim 4, wherein, When the first subtask creation information comprises a plurality of first creation modules, the first subtask creation information further comprises an association relationship between the first creation modules, and the association relationship is used to describe the association relationship between the subsequent subtasks in any group of the subsequent subtasks.

7. The method of claim 1, wherein, The first task constraint information comprises the following agreement: The number of the subsequent subtasks is determined by quantity information of a corresponding module included in the first subtask creation information; and / or The association relationship between the subsequent subtasks is determined by an association relationship between corresponding modules included in the first subtask creation information; and / or The subtask description information of the subsequent subtasks is supplemented according to content information of a corresponding module included in the first subtask creation information.

8. The method of claim 1, wherein, The plurality of subtasks further comprise a second subtask derived by the first subtask, and the second subtask has at least one group of the subsequent subtasks.

9. A method for processing subtasks in a collaborative community, characterized by, The method comprises: obtaining a third subtask in a first collaborative task, the first collaborative task comprising a plurality of subtasks, the plurality of subtasks comprising a first subtask, the first subtask being used to derive the third subtask with an undetermined number, the first collaborative task having a first task template associated therewith, the first task template comprising first task constraint information, the first task constraint information comprising correspondence information between the first subtask and the third subtask; providing the third subtask to a third task creator; obtaining third subtask creation information completed by the third task creator; submitting the third subtask creation information, The third subtask description information of the third subtask includes information corresponding to the corresponding content information in the first subtask creation information completed by the first subtask creator according to the first task constraint information.

10. The method of claim 9, wherein, The first subtask creation information includes a plurality of first creation modules. The quantity information of the plurality of first creation modules is used to determine the quantity of the third subtask according to the first task constraint information; and / or The content information of the plurality of first creation modules is used to supplement the subtask description information of the third subtask; and / or The association relationship between the plurality of first creation modules is used to describe the association relationship between the third subtasks.

11. The method of claim 9, wherein, The plurality of subtasks further include a second subtask derived from the first subtask, and the second subtask has the third subtask.

12. A method for processing subtasks in a collaborative community, characterized by, The method comprises: providing a first subtask in a first collaborative task to a first task creator, the first collaborative task including a plurality of subtasks, the plurality of subtasks including the first subtask, the first subtask being used to derive one or more groups of subsequent subtasks with an undetermined quantity, the first collaborative task having a first task template associated therewith, the first task template including first task constraint information, the first task constraint information including corresponding information between the first subtask and the subsequent subtasks; receiving first subtask creation information completed by the first task creator, the first subtask creation information including a first creation module, wherein the first subtask creation information includes the first creation module and quantity information of the first creation module; the quantity information is used to determine the quantity of the third subtask according to the first task constraint information; deriving one or more groups of the subsequent subtasks with a determined quantity according to the first task relationship constraint information and the first subtask creation information.

13. The method of claim 12, wherein: the first subtask creation information includes the first creation module and the quantity information of the first creation module; deriving one or more groups of the subsequent subtasks with a determined quantity according to the first task relationship constraint information and the first subtask creation information includes: determining the quantity of the subsequent subtasks in any group of subsequent subtasks according to the first task constraint information according to the quantity information.

14. The method of claim 12, wherein: the first creation module has content information; deriving one or more groups of the subsequent subtasks with a determined quantity according to the first task relationship constraint information and the first subtask creation information includes: supplementing the subtask description information of one or more groups of the subsequent subtasks with the content information.

15. The method of claim 12, wherein: when the first subtask creation information includes a plurality of first creation modules, the first subtask creation information further includes an association relationship between the plurality of first creation modules; Deriving one or more groups of a determined number of the subsequent sub-tasks according to the first task constraint information and the first sub-task creation information, including: describing the association relationship between the plurality of subsequent sub-tasks in any group of the subsequent sub-tasks by using the association relationship.

16. The method of claim 12, wherein, The first task constraint information includes the following agreement: The number of the subsequent sub-tasks is determined by the number information of the corresponding module included in the first sub-task creation information. The association relationship between the subsequent sub-tasks is determined by the association relationship between the corresponding modules included in the first sub-task creation information. The sub-task description information of the subsequent sub-tasks is supplemented according to the content information of the corresponding module included in the first sub-task creation information.

17. The method of claim 12, wherein, The plurality of sub-tasks further include a second sub-task derived by the first sub-task, and the second sub-task has at least one group of the subsequent sub-tasks in the one or more groups of the subsequent sub-tasks.

18. A computer program product, characterised in that, The computer program is executed by a processor to implement the method of any one of claims 1-12.

19. A computing device, comprising: including: a processor; and a memory storing a computer program, which, when executed by the processor, causes the processor to perform the method of any one of claims 1-12.

Images