Method and system for issuing task in cooperative community and computing equipment

Abstract

The invention provides a method and a system for issuing tasks in a collaborative community and computing equipment, users of the collaborative community have user label information, and the method comprises the following steps: determining a first collaborative template for completing a first task; determining task setting information according to the first cooperation template; according to the task setting information, task planning information of the first task is generated, the first task corresponds to the first cooperation template, and the first task comprises at least one subtask; issuing the first task according to the task planning information, including: determining a task scheduling scheme for the first task according to the task planning information and the user tag information, the task scheduling scheme being used for setting a user executing the subtask; according to the task scheduling scheme, the corresponding subtasks are sent to corresponding users set by the task scheduling scheme in a pushing mode and / or a dispatching mode. By means of the method, a more friendly interaction mode can be provided.

Description

Technical Field

[0001] The present invention relates to the field of digital information technology, and in particular to a method and system for publishing tasks in a collaborative community and a computing device. Background Art

[0002] Existing technologies still have shortcomings in natural language understanding and processing, making it difficult to accurately capture the nuances and underlying meaning of user questions, thus affecting the accuracy of template matching. Traditional template libraries are typically static and infrequently updated, making it difficult to promptly reflect emerging question types or changing user needs. When faced with rapidly changing needs or emergencies, existing systems may be unable to respond quickly due to lagging template adjustments.

[0003] Fixed templates fail to capture all possible user needs, leaving some users' specific needs unmet or forcing them to use less-suitable templates. Furthermore, most systems fail to fully consider users' individual needs and preferences, often offering one-size-fits-all solutions that don't adapt well to the specific circumstances of different users. Requiring users to provide detailed information or select a template can impose additional cognitive load, especially if they're unfamiliar with the required content.

[0004] Therefore, a technical solution is needed to provide a more friendly interactive method and provide users with better services. Summary of the Invention

[0005] This invention aims to provide a method, system, and computing device for posting tasks in a collaborative community. These methods offer a user-friendly interactive experience, allowing users to focus on asking questions without worrying about selecting or filling out templates. This not only lowers the operational barrier for users but also improves overall efficiency and service quality.

[0006] According to one aspect of the present invention, a method for publishing a task in a collaborative community is provided, wherein users of the collaborative community have user tag information, the method comprising:

[0007] determining a first collaboration template for completing a first task;

[0008] Determining task setting information according to the first collaboration template;

[0009] generating task planning information for the first task according to the task setting information, wherein the first task corresponds to the first collaboration template and includes at least one subtask;

[0010] Publishing the first task according to the task planning information includes:

[0011] Determine a task scheduling scheme for the first task based on the task planning information and the user tag information, wherein the task scheduling scheme is used to set a user who executes a subtask;

[0012] According to the task scheduling scheme, the corresponding subtask is sent to the corresponding user set by the task scheduling scheme through a push mode and / or a dispatch mode.

[0013] According to some embodiments, determining a first collaboration template for completing a first task includes:

[0014] Obtain the first task intention description from the task publisher;

[0015] Automatically matching in a collaborative template library according to the first task intention description;

[0016] If a collaboration template is matched from the collaboration template library, the collaboration template determined according to the matching result is used as the first collaboration template;

[0017] If no collaboration template is matched from the collaboration template library, a collaboration template matching the first task intention description is asynchronously generated as the first collaboration template.

[0018] According to some embodiments, automatically matching in a collaboration template library according to the first task intent description includes:

[0019] The first task intention description is matched with the collaboration template description information in the collaboration template library, and the collaboration template that meets the matching requirements is provided to the task publisher.

[0020] According to some embodiments, the asynchronously generating a collaboration template that matches the first task intention description as the first collaboration template includes:

[0021] A collaboration template generation requirement corresponding to the first task intention description is published in the collaboration community, thereby obtaining a collaboration template corresponding to the first task intention description as the first collaboration template.

[0022] According to some embodiments, the first collaboration template includes a task setting object;

[0023] Determining task setting information according to the first collaboration template includes:

[0024] Acquire task setting information corresponding to the task setting object included in the first collaboration template.

[0025] According to some embodiments, generating task planning information for the first task based on the task setting information includes:

[0026] Assigning a task number to the first task;

[0027] The task planning information is generated according to the first collaboration template and the task setting information corresponding to the first collaboration template.

[0028] According to some embodiments, issuing the first task according to the task planning information further includes:

[0029] Generate a corresponding task data packet according to the task planning information.

[0030] According to some embodiments, each subtask of the at least one subtask is in a non-authorable state or an authorable state;

[0031] The task planning information of the first task includes subtask related information of each subtask;

[0032] Determining a task scheduling scheme for the first task according to the task planning information and the user tag information includes:

[0033] The subtask related information of each subtask in the authorable state is matched with the user tag information, and the user who executes the corresponding subtask is set according to the matching result.

[0034] According to some embodiments, the subtask related information includes a subtask process interaction tag;

[0035] The pushing method and / or the dispatching method is determined according to the subtask process interaction tag.

[0036] According to some embodiments, the collaborative community includes a plurality of communities;

[0037] The subtask related information includes a subtask community range tag, and the user tag information includes a user community tag;

[0038] Matching the subtask related information of each subtask in the authorable state with the user tag information, including: matching each subtask community range tag with the user community tag respectively.

[0039] According to some embodiments, in the assignment method, the user set to perform the corresponding subtask receives the assigned corresponding subtask and performs the corresponding subtask according to a predetermined rule;

[0040] In the push mode, the user who is set to perform the corresponding subtask receives the pushed corresponding subtask and determines whether to perform the corresponding subtask.

[0041] According to some embodiments, the first collaboration template is added to the collaboration template library.

[0042] According to another aspect of the present invention, a system for publishing tasks in a collaborative community is provided, comprising:

[0043] An acquisition module is used to obtain the first task intention description of the task publisher;

[0044] A template determining module, determining a first collaboration template for completing a first task;

[0045] a setting module, determining task setting information according to the first collaboration template determined by the template determination module;

[0046] a planning module, configured to generate task planning information for a first task based on the task setting information provided by the setting module;

[0047] A publishing module, configured to publish a first task according to the task planning information generated by the planning module;

[0048] Wherein, the publishing module includes:

[0049] A scheduling submodule, combining the task planning information and the user tag information to determine a task scheduling solution for the first task;

[0050] The sending submodule sends the subtasks to the corresponding users set in the task scheduling scheme through a push method and / or a dispatch method according to the task scheduling scheme.

[0051] According to some embodiments, the template determination module includes:

[0052] The acquisition submodule is used to obtain the first task intention description of the task publisher;

[0053] a matching submodule, which automatically matches a first collaboration template in a collaboration template library according to the first task intention description obtained by the acquisition submodule;

[0054] A generation submodule asynchronously generates a collaboration template that matches the first task intention description as the first collaboration template.

[0055] According to another aspect of the present invention, there is provided a computing device comprising:

[0056] processor; and

[0057] A memory storing a computer program, which, when executed by the processor, causes the processor to perform any of the above methods.

[0058] According to an embodiment of the present invention, after determining the first collaborative template for completing the first task, the system can automatically handle subsequent processes such as determining task planning information and determining task scheduling plans to ensure that the requirements of the task are correctly understood and processed in a structured manner, which helps to improve the consistency and efficiency of task execution, reduce the occurrence of misunderstandings and errors, and lower the user's usage threshold. Based on the task setting information, the task planning information of the first task is generated, the overall task is decomposed into multiple subtasks, and a detailed execution plan is formulated for each subtask, which helps to optimize resource allocation and improve task execution efficiency. Generating task planning information based on task setting information and intelligently allocating subtasks based on user tag information can organize resources more efficiently and reduce human intervention. Sending subtasks to corresponding users by push and / or dispatch not only ensures the flexibility of task allocation, but also selects the most appropriate communication channel according to actual conditions to improve response speed.

[0059] According to some embodiments, by automatically matching the most suitable collaborative template from the collaborative template library or asynchronously generating a new template, the time cost of manually selecting or creating templates is reduced, the speed of task publishing is improved, and even in the absence of ready-made templates, a matching new template can be asynchronously generated, and the new template can be added to the collaborative template library, so that the method can flexibly respond to various different task requirements and increase the adaptability and scalability of the system.

[0060] According to some embodiments, by automatically finding the most suitable first collaboration template from the collaboration template library or asynchronously generating a collaboration template that matches the first task intent description as the first collaboration template, the time and workload of manually selecting templates are reduced. According to some embodiments, the system can generate detailed task planning information and intelligently assign subtasks based on user tag information, thereby improving the efficiency and accuracy of task management. Not only does it significantly improve the efficiency and accuracy of task publishing, it also improves the user experience in an intelligent way, enhances the flexibility and adaptability of the system, and is conducive to building an efficient and collaborative knowledge sharing and task execution environment.

[0061] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments.

[0063] Figure 1 A flowchart of a method for publishing a task in a collaborative community according to an example embodiment is shown.

[0064] Figure 2A schematic diagram of an overall technical architecture of a collaborative community according to an example embodiment is shown.

[0065] Figure 3 A schematic diagram illustrating an overall business process of a collaborative community according to an example embodiment is shown.

[0066] Figure 4 A diagram illustrating a composition of a task scheduling solution according to an example embodiment is shown.

[0067] Figure 5 A schematic diagram illustrating a system issuing tasks according to an example embodiment.

[0068] Figure 6 A flowchart illustrating authoring of a push-type subtask according to an example embodiment is shown.

[0069] Figure 7 A flowchart illustrating authoring of dispatched subtasks according to an example embodiment is shown.

[0070] Figure 8 A block diagram showing system components for publishing tasks in a collaborative community according to an example embodiment is shown.

[0071] Figure 9 A state diagram of a task initiated through a collaborative community according to some embodiments is shown.

[0072] Figure 10 A state diagram of a task initiated through a collaborative community according to some embodiments is shown.

[0073] Figure 11 A state diagram of an initial task initiated by a collaborative community according to some other embodiments is shown.

[0074] Figure 12 A state diagram of a setting task initiated by a collaborative community according to some other embodiments is shown.

[0075] Figure 13 It is shown that a first task state diagram is generated by a current collaborative task initiated by a collaborative community according to some other embodiments.

[0076] Figure 14 A block diagram of a computing device is shown according to an exemplary embodiment. DETAILED DESCRIPTION

[0077] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art. Like reference numerals in the drawings represent like or similar parts, and thus repeated description thereof will be omitted.

[0078] In addition, the described features, structures or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present invention. However, it will be appreciated by those skilled in the art that the technical solutions of the present invention can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring various aspects of the present invention.

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

[0080] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0081] 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. Thus, the first component discussed below could be referred to as the second component without departing from the teachings of the present inventive concept. As used herein, the term "and / or" includes any one and all combinations of one or more of the associated listed items.

[0082] 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, stored data, displayed data, etc.) involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

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

[0084] A narrow computing network refers to the computing resources that form the computing power supply network. From this perspective, key innovations in the AI industry to date, from OpenAI to DeepSeek, including joint optimization of pre-training and inference, have focused solely on the computing power supply side, falling within the narrow computing power network.

[0085] When we examine computing networks through the lens of the intelligent era, focusing solely on the supply side of computing power won't yield the optimal solution. Expanding our perspective to include the demand side of computing power within the computing network requires joint optimization of the computing network's interconnected two sides: demand and supply. Including terminal devices and edge devices within the computing network requires joint optimization of intelligent resources across the three-layer "end-edge-cloud" network.

[0086] If human intelligence is also considered a form of intelligent resource and included in the scope of the computing power network, then it is necessary to jointly optimize the intelligent resources that collaborate across the two domains of "human intelligence and machine intelligence." In other words, through "interpersonal collaboration, human-machine collaboration, and inter-machine collaboration," the human-machine environment intelligent system covering the human intelligence domain and the machine intelligence domain must be jointly optimized. In this invention, users in the collaborative community include both human users and machine intelligence users. Both types of users are intelligent resources in the generalized computing power network. This invention uses the terms intelligent resources and users concurrently, and the two are equivalent.

[0087] As technology develops and application scenarios continue to expand, the concept of the generalized computing network will evolve, continuing to lead the way in digital transformation. The intelligent portal is the operating platform for the generalized computing network, providing portal-style services for the era of collective intelligence through the construction and operation of collaborative communities.

[0088] In summary, the generalized computing power network refers to the generalized intelligent system in the intelligent era, including the two-side linkage formed by the "computing power demand side-computing power supply side", the three-layer networking formed by the intelligent resources deployed in the "cloud-edge-end", and the human-machine-environment collaboration formed by "machine intelligence-human intelligence".

[0089] While existing technologies offer some support for solving user questions and posting tasks, they still face numerous challenges and limitations. Existing technologies still have shortcomings in natural language understanding and processing, making it difficult to accurately capture the nuances and underlying meanings of user questions, thus impacting the accuracy of template matching. The question templates provided by current systems are often fixed and fail to cover all possible user needs. This results in some users' specific needs not being met, or having to resort to using less-than-suitable templates.

[0090] To this end, this paper proposes a method for publishing tasks in collaborative communities. This method incorporates advanced technologies to gradually overcome drawbacks such as a lack of flexibility, providing users with superior services. By building and operating collaborative communities, users are provided with a comprehensive service system, encompassing the entire business process from user registration to task participation, to the display and evaluation of results. Throughout this process, the platform prioritizes user experience and continuously optimizes each step to meet user needs and expectations.

[0091] Before describing the embodiments of the present application, some terms or concepts involved in the embodiments of the present application are explained.

[0092] Atomization refers to the gradual decomposition of large tasks during the collaborative process, ultimately decomposing them into a series of interrelated atomic subtasks with minimized mutual information.

[0093] Structuring means that during the collaborative process of tasks, the relationship between subtasks is gradually established through hierarchical planning, step decomposition, module bifurcation, and loop iteration, including nesting, looping, series connection, and parallel connection, thus forming a structured and dynamically evolving task status diagram.

[0094] Socialization refers to providing structured community services for collaborative tasks based on task status diagrams, including intelligent dispatching / intelligent push / autonomous order grabbing services with atomic subtasks as the smallest granularity and for generalized computing power networks, as well as process management, results assembly, recording rights and accounting, in-scene communication, scenario-based digital twins and VR / AR / XR, scenario-based AI intelligent agents, and scenario-based platform assistance.

[0095] Exemplary embodiments of the present invention are described below with reference to the accompanying drawings.

[0096] Figure 1 A flowchart of a method for publishing a task in a collaborative community according to an example embodiment is shown.

[0097] In S103 , a first collaboration template for completing the first task is determined.

[0098] According to some embodiments, the task publisher may directly select a collaboration template for the task from the collaboration template library as the first collaboration template.

[0099] A collaborative template is an object with attached markup, data, text, or multimedia content, along with template description information. In the present invention, templates serve multiple purposes. For example, they describe the file format and default content of an entire document. Collaborative templates can be generated or expressed using XML files or other software with content management and interaction capabilities, though this invention is not limiting.

[0100] A template can use a topology composed of several information objects to define the document's information framework. These information objects include task information objects and content information objects. This information framework can be specifically represented as a topology composed of several information objects. This topology can be described by a data structure that uniquely defines the relationships between these information objects. For example, one information object can correspond to multiple file blocks. File blocks specify the location of the information object's content within the document. File blocks are one of the components of an XML document.

[0101] According to some embodiments, a first task intent description may be obtained from a task issuer. Then, based on the task requirement information input by the user, the task intent processing module of the task setting subsystem may perform task intent analysis. According to some embodiments, task intent processing may be performed by an AI agent specialized in task intent analysis.

[0102] According to some embodiments, the first task intention description is matched with the collaboration template description information in the collaboration template library, and the collaboration template that meets the matching requirements is provided to the task publisher.

[0103] Based on the task intent's content and the collaborative template descriptions in the collaborative template library, the collaborative template processing module performs information matching. It then determines the collaborative template with the highest matching score as the collaborative template corresponding to the task intent. Alternatively, the collaborative template processing module pushes several highly matching collaborative templates to the task initiator, who then selects one of these templates as the corresponding collaborative template.

[0104] According to some embodiments, a collaboration template that meets the requirements for matching the task intent refers to a collaboration template in which the matching degree between the collaboration template description information and the content information of the task intent is not lower than the matching degree threshold set by the task setting subsystem, or not lower than the matching degree threshold required by the task type of the task corresponding to the task intent.

[0105] The information matching metric calculation method can use a keyword matching method, such as statistical keyword overlap or keyword weighted matching, or a semantic distance-based matching method. Alternatively, a semantic understanding-based method, such as using the pre-trained language model BERT or matching based on semantic role labeling, can be used. This invention is not limited to this.

[0106] A collaboration template is used to describe a task's collaborative plan, which can be embodied, for example, as an initial task state diagram. The task's collaborative plan includes at least one subtask. A subtask includes subtask-related information, including subtask label information. The subtask-related information also includes subtask description information. According to some embodiments, at least some of the subtask-related information is organized in the form of prompts tailored to the reasoning model, making it usable by human users or intelligent agents.

[0107] According to some embodiments, the collaboration community includes multiple communities, and the subtask tag information includes a subtask community scope tag.

[0108] According to some embodiments, the subtask tag information may further include other tag information content, such as a subtask service quality requirement tag, which is used to describe the service quality requirement of the subtask, such as the time delay characteristics of the delivery of the result, the quality level of the result, etc.

[0109] According to some embodiments, the subtask tag information may also include other tag information content, such as the computing power attribute requirement tag of the subtask, which is used to describe the computing power attribute requirement of the subtask. For example: human expert type, offline operation type, computing intensive (CPU + low latency cache), natural language processing intensive (LPU, such as AI reasoning tasks, legal analysis), memory intensive (such as data analysis, in-memory database, gene sequencing, etc.), I / O throughput sensitive (such as patent search, database transaction processing, log analysis), network intensive (such as autonomous driving, edge computing, video conferencing), real-time sensitive (robot motion planning, medical equipment, autonomous driving), energy efficiency priority (low power computing, such as IoT devices), parallel computing / graphics processing (GPU + high-bandwidth video memory), distributed computing (such as big data processing, federated learning), etc.

[0110] According to some embodiments, subtask tag information may also include other tag information content, such as a subtask expert attribute requirement tag, which is used to describe the professional attribute requirements of the subtask. Examples include: patent search, legal analysis, financial analysis, market analysis, gene sequencing, robot motion planning, Wensheng video, Wensheng source code, Traditional Chinese Medicine diagnosis, agricultural data analysis, mathematical reasoning, physics, chemistry, current affairs news, sports and health, etc.

[0111] According to some embodiments, the subtask tag information may further include other tag information content, for example, a geographic location requirement tag of the subtask, which is used to describe the geographic location requirements of the subtask for the creator.

[0112] According to some embodiments, the subtask label information may also include other label information content, such as the qualification requirement label of the subtask, which is used to describe the qualification requirements of the subtask for the creator, such as a practicing physician certificate, a practicing assistant physician certificate, a practicing pharmacist registration certificate, a health manager professional skill level certificate, an environmental assessment engineer qualification certificate, a lawyer's license, a teacher's qualification certificate, etc.

[0113] The present invention does not limit the content of more subtask tag information, and the collaboration template can add, delete and set the tag information of the subtask as needed.

[0114] According to some embodiments, the collaboration template includes user location information, which can be used to support communication within a task scenario, task scheduling, etc., and to statically or dynamically set corresponding users.

[0115] According to some embodiments, the subtask related information may further include a subtask process interaction tag, which is used to describe the process interaction type of the subtask, including a push type or a dispatch type.

[0116] According to some embodiments, matching can be automatically performed in the collaboration template library based on the first task intent description. If a collaboration template is matched from the collaboration template library, the collaboration template determined based on the matching result will be used as the first collaboration template; if no collaboration template is matched from the collaboration template library, a collaboration template that matches the first task intent description will be asynchronously generated as the first collaboration template.

[0117] According to some embodiments, if no matching collaboration template is found in the collaboration template library, a collaboration template matching the first task intent description is asynchronously generated as the first collaboration template. For example, a collaboration template generation request corresponding to the first task intent description is published to the collaboration community, thereby obtaining the collaboration template corresponding to the first task intent description as the first collaboration template.

[0118] According to some embodiments, an intelligent agent can also be used to generate a corresponding collaboration template based on the first task intent description as a first collaboration template. For example, the intelligent agent calls a large language model, and the large language model generates a first task expansion description based on the first task intent description. The first task expansion description includes the steps and methods for completing the task. Based on the first task expansion description, the intelligent agent calls a pre-trained neural network model capable of generating collaboration templates. The pre-trained neural network model is pre-trained using existing tasks and corresponding collaboration templates as training materials. According to some embodiments, the intelligent agent also searches for network resources and inputs the network resource search results into the large language model.

[0119] Add the first collaboration template to the collaboration template library. If the first collaboration template does not already exist in the collaboration template library, add the first task intent description and the corresponding first collaboration template to the collaboration template library. As the collaboration template library expands, the collaboration template library can be used to iteratively upgrade the first pre-trained neural network model.

[0120] The present invention does not impose any particular limitation on the method for determining the template, and other methods may also be used to determine the collaboration template.

[0121] In S105 , task setting information is determined according to the first collaboration template.

[0122] According to an example embodiment, the first collaboration template includes a task setting object, and task setting information is determined based on the first collaboration template; determining the task setting information includes acquiring task setting information corresponding to the task setting object included in the first collaboration template.

[0123] According to some embodiments, based on the first collaboration template, the task setting information includes the following:

[0124] Task setting information content 1: the community scope of the task release, for example, specified by the community scope tag.

[0125] Task setting information content 2: the collaboration template used in the task.

[0126] Task setting information content 3: Task setting information corresponding to the collaboration template.

[0127] In S107 , task planning information of a first task is generated according to the task setting information, where the first task corresponds to the first collaboration template and includes at least one subtask.

[0128] According to an example embodiment, a task number may be assigned to the first task first, but the present invention is not limited thereto.

[0129] According to some embodiments, the task planning information is generated based on the first collaboration template and the task setting information corresponding to the first collaboration template.

[0130] In S109 , the first task is published according to the task planning information.

[0131] According to some embodiments, a corresponding task data packet is generated based on the task planning information. The entire task is first packaged. The packaged task data packet can be used for task scheduling and publishing. As described below, the push or dispatch action of the subtask is determined based on the task scheduling strategy, such as the interaction tag of the subtask process.

[0132] According to some embodiments, a task scheduling scheme for the first task may be determined based on the task planning information and the user tag information, and the task scheduling scheme is used to set a user who executes the subtask.

[0133] According to some embodiments, each subtask of the at least one subtask is in a non-authorable state or an authorable state.

[0134] According to some embodiments, the task planning information of the first task may include subtask related information of each subtask.

[0135] According to some embodiments, the subtask-related information of each subtask in the authorable state can be matched with the user tag information, and the user who executes the corresponding subtask is set according to the matching result. According to some embodiments, the task planning information of the first task includes the subtask-related information of the subtask.

[0136] The collaborative community includes multiple communities, the subtask-related information includes a subtask community-wide tag, and the user tag information includes a user community tag. The subtask-related information of each subtask in an authorable state is matched with the user tag information, including matching each subtask community-wide tag with the user community tag. The subtask community-wide tag can be inherited from the community-wide tag of the community where the task is published, or can be specified separately.

[0137] The users of the collaborative community include various user types, such as: human expert users, machine intelligence community users, machine intelligence calling users, and platform support users.

[0138] The user type label of an intelligent resource is used to describe the user type to which the intelligent resource belongs.

[0139] When a user joins a community, it is necessary to establish community user identity information and assign a user type tag to the intelligent resource. According to some embodiments, the user tag information may also include other tag information content, such as the service quality tag of the intelligent resource. The collaborative community has a task scheduling subsystem that can match the appropriate intelligent resources for the subtasks and push or dispatch them based on the service quality tag of the intelligent resource, the current load of the intelligent resource, and the quality of service (QoS) requirements of the subtask to improve the service quality and user experience. The service quality tag of the intelligent resource is used to describe the service quality characteristics of the intelligent resource. For example, the time delay characteristics of the delivery of the results, the quality level of the results, etc.

[0140] When an intelligent resource joins a collaborative community, its QoS tag can be assigned an initial value or temporarily unassigned. As the intelligent resource becomes active in the collaborative community, the system can assign and gradually adjust the QoS tag based on its performance.

[0141] According to some embodiments, user tag information may also include other tag information, such as the computing power attribute tag of an intelligent resource. The collaborative community has a task scheduling subsystem that can match the computing power attribute requirements of subtasks with the computing power attributes of intelligent resources, push or dispatch appropriate intelligent resources to subtasks, thereby enhancing system efficiency and improving the quality of results.

[0142] The computing power attribute tag of an intelligent resource is used to describe the computing power attributes of the intelligent resource. Examples include: human expert type, offline operation type, compute-intensive (CPU + low-latency cache), natural language processing-intensive (LPU, such as AI reasoning tasks and legal analysis), memory-intensive (such as data analysis, in-memory databases, gene sequencing, etc.), I / O throughput-sensitive (such as patent search, database transaction processing, log analysis), network-intensive (such as autonomous driving, edge computing, video conferencing), real-time-sensitive (robotic motion planning, medical equipment, autonomous driving), energy efficiency-first (low-power computing, such as IoT devices), parallel computing / graphics processing (GPU + high-bandwidth video memory), distributed computing (such as big data processing and federated learning), and so on.

[0143] When an intelligent resource joins a collaborative community, its computing power attribute tag may be assigned an initial value or temporarily unassigned. As the intelligent resource becomes active in the collaborative community, the system can gradually adjust the information in the computing power attribute tag based on its actual performance in the collaborative community.

[0144] According to some embodiments, user tag information may also include other tag information, such as the expert attribute tag of an intelligent resource. The collaborative community has a task scheduling subsystem that can match appropriate intelligent resources to subtasks based on their professional attributes and the expert attributes of intelligent resources, thereby enhancing system efficiency and improving the quality of results.

[0145] The expert attribute tag of an intelligent resource is used to describe the professional attributes of the intelligent resource. Examples include patent search, legal analysis, financial analysis, market analysis, gene sequencing, robot motion planning, Wensheng video, Wensheng source code, Traditional Chinese Medicine diagnosis, agricultural data analysis, mathematical reasoning, physics, chemistry, current affairs news, sports and health, etc.

[0146] When an intelligent resource joins a collaborative community, its expert attribute tag is assigned an initial value. As the intelligent resource becomes active in the collaborative community, the system can gradually adjust the information in the expert attribute tag based on the actual performance of the intelligent resource in the collaborative community.

[0147] According to some embodiments, user tag information may also include other tag information content, such as the location status tag (dynamic tag) of the smart resource. The location status tag of the smart resource is used to describe the location status of the smart resource. The collaborative community has a task scheduling subsystem that can match appropriate smart resources to subtasks based on their location requirements.

[0148] According to some embodiments, user tag information may also include other tag information content, such as the qualification tag of the intelligent resource. The qualification tag of the intelligent resource is used to describe the qualifications of the intelligent resource. For example: practicing physician certificate, practicing assistant physician certificate, practicing pharmacist registration certificate, health management professional skill level certificate, environmental assessment engineer qualification certificate, lawyer's license, teacher qualification certificate, etc. The collaborative community has a task scheduling subsystem that can match the appropriate intelligent resource for each subtask based on its qualification requirements.

[0149] The present invention does not limit the content of more tags, and the system can add, delete and set tags of smart resources as needed.

[0150] According to some embodiments, after the task scheduling scheme is determined, the subtasks may be sent to corresponding users set by the task scheduling scheme by pushing and / or dispatching according to the task scheduling scheme.

[0151] According to some embodiments, the corresponding subtask may be sent to the corresponding user set by the task scheduling scheme via a push method and / or a dispatch method, and the push method and / or the dispatch method may be determined according to the subtask process interaction tag.

[0152] According to some embodiments, in the assignment method, after receiving the assigned corresponding subtask, the user who is set to perform the corresponding subtask performs the corresponding subtask according to a predetermined rule.

[0153] According to some embodiments, in the push mode, the user set to perform the corresponding subtask determines whether to perform the corresponding subtask after receiving the pushed corresponding subtask.

[0154] Generate a task scheduling plan, including subtask push and subtask dispatch. For the composition of the task scheduling plan, see Figure 4The collaborative community has a task scheduling subsystem, which aims to achieve joint optimization of the generalized computing power network, including the two-side linkage formed by "intelligent demand side-intelligent supply side", the three-layer networking formed by intelligent resources deployed in "cloud-edge-end", and the two-domain collaboration formed by "machine intelligence-human intelligence".

[0155] According to some embodiments, users corresponding to subtask user locations can be set to generate a task scheduling plan. When a task is first released, none of the subtasks in the first task state diagram have new execution content. After the task is released, as long as a subtask has new execution content, the first task state diagram will evolve into the second task state diagram.

[0156] The system sets the creation status based on the series (derivation-dependency) relationship between subtasks. In the first task state diagram, the creation status of subtask nodes that do not depend on other subtasks is a creation state; those subtask nodes that depend on other subtasks are in a non-creation state. In the second task state diagram, when all the other atomic subtasks that a subtask depends on have execution content; and all the other framework subtasks that the subtask depends on have atomic lower-level subtasks, and the atomic lower-level subtasks also have execution content, the creation status of the subtask node is a creation state; those subtask nodes that do not meet the above conditions are in a non-creation state.

[0157] For subtasks in the first task status diagram and the second task status diagram that are in the authorable state, the task scheduling subsystem matches the subtask related information of the subtask with the intelligent resource information in the collaborative community, and according to the matching result, sets the user corresponding to the user site owned by the subtask node to generate a task scheduling plan.

[0158] The subtask-related information of the subtask includes subtask prior information, subtask description information, and subtask tag information. In the first task status diagram, for subtasks in the authorable state, its subtask prior information includes task setting information. In the second task status diagram, for subtasks in the authorable state, its subtask prior information includes task setting information, and may also include subtask description information, subtask tag information, and subtask execution content information of each previous subtask on which the subtask directly or indirectly depends.

[0159] The intelligent resource information in the collaborative community may be intelligent resource tag information, and the user site possessed by the subtask node may be a push-type user site or a dispatch-type user site according to the subtask process interaction tag possessed by the subtask node. For push-type user sites, the task scheduling subsystem usually sets several users with the highest matching degree between the subtask related information and the intelligent resource information for the user site, such as setting the top five users with the highest matching degree. The users corresponding to the push-type user sites are usually human expert users or machine intelligent community users. For dispatch-type user sites, the task scheduling subsystem usually sets the user site with the user with the highest matching degree between the subtask related information and the intelligent resource information. The users corresponding to the dispatch-type user sites are usually machine intelligent calling users. In addition, for tasks carried out within the internal community, the users corresponding to the dispatch-type user sites may also be human expert users.

[0160] For subtask push tasks, when the subtask's creation status is ready, the task scheduling subsystem pushes the subtask to the users corresponding to the subtask's user location according to the task scheduling plan. If the user corresponding to the subtask's user location is a human expert, the system may also attach the subtask's execution content generated by the machine intelligence-invoked user as reference execution content when pushing the subtask. This reference execution content can be reviewed and further processed by human expert users, including but not limited to identifying and removing illusions, creating new content, and streamlining and improving content.

[0161] When the creation status of the subtask is the createable status, according to the task scheduling scheme, for the dispatchable subtask, the task scheduling subsystem dispatches the subtask to the user corresponding to the user site of the subtask.

[0162] If the user site associated with a subtask is a human expert, the system may also attach the execution content generated by the machine intelligence-invoked user as reference execution content when assigning the subtask. The reference execution content is provided for review and further processing by the human expert, including but not limited to identifying and removing illusions, creating new content, and streamlining and improving it.

[0163] Figure 2 A schematic diagram of an overall technical architecture of a collaborative community according to an example embodiment is shown.

[0164] See also Figure 2The collaborative community is task-centric and can adopt cloud architecture (including IaaS / PaaS / DaaS / SaaS), RAG (Retrieval-Augmented Generation), API / Web API (Application Programming Interface), MCP (Model Context Protocl) and other architectures and interface technologies to collaborate with each other and carry out the construction and operation of a three-in-one collaborative community of task aggregation, capability training and sharing, and task completion.

[0165] According to the classification and function of collaborative communities, they can be divided into public communities, alliance communities and internal communities. When users join a collaborative community, they can be automatically included in the public community, or they can be set not to be included in the public community but to be included in one or several alliance communities or internal communities.

[0166] Public communities are open to all users. Data published in public collaborative communities, including tasks, subtask execution content, task-generated information snapshots, and corresponding digital works, is publicly available to every user in the collaborative community. This means that every user in the collaborative community can browse or search for data published in the public collaborative community.

[0167] Alliance communities collaborate to call upon alliance applications, alliance data, and alliance computing power. Data published in an alliance community can only be browsed or searched by users within the alliance community, and users outside the alliance community cannot access it.

[0168] Internal communities collaborate to utilize internal applications, internal data, and internal computing power. Data published in an internal community can only be browsed or searched by users within that community, and users outside of that community cannot access it.

[0169] When a coalition community or internal community is established, platform support users are set up for the coalition community or internal community. The community tags owned by these platform support users include the coalition community or internal community.

[0170] According to some embodiments, the collaborative community also includes a portal application platform (SaaS), a portal resource base (DaaS), a portal capability base (PaaS), and a portal infrastructure (IaaS). The public internet is coordinated with the portal application platform, portal resource base, portal capability base, and portal infrastructure. The public internet includes public applications, public data, and public computing power. The public internet connects various public applications and resources, such as search engines, social media, and online shopping software, and supports the execution of various computing tasks based on the public computing resources provided by the public computing power.

[0171] The portal application platform (SaaS) includes ecological applications, flagship applications, and platform user terminals. The portal resource base (DaaS) includes a computing power aggregation platform, a talent aggregation platform, and a collaboration solution aggregation platform (collaboration template library), providing users with a wealth of resources and services.

[0172] The portal capability base (PaaS) includes task planning, which helps users plan and manage tasks to ensure the effective execution of tasks; intelligent push, which recommends relevant resources and tasks based on user needs and behaviors; process management, which manages and monitors the task execution process to ensure the smoothness and efficiency of the process; results assembly, which integrates and displays the results of task execution for users to view and share; in-scene communication, which provides instant messaging and collaboration tools to facilitate users to communicate and exchange during task execution; rights and account sharing, which handles user rights management and profit distribution to ensure fairness, transparency and platform support.

[0173] The portal infrastructure (IaaS) includes a unified trust system for blockchain-based service networks (such as the BSN consortium chain), a file storage system, a database system, and a computing power service system. The BSN consortium chain unified trust system, based on blockchain technology, ensures data security and credibility. The file storage system provides file storage and management services, supporting large-capacity and high-reliability file storage. The database system is used to store and manage various data, supporting efficient query and analysis. The computing power service system provides powerful computing capabilities to support various complex computing tasks.

[0174] This embodiment demonstrates that the intelligent portal, as a comprehensive collaborative community, provides users with a comprehensive, efficient, and secure service platform through a multi-level and multi-dimensional technical architecture.

[0175] Figure 3 A schematic diagram illustrating an overall business process of a collaborative community according to an example embodiment is shown.

[0176] According to some embodiments, when users join a collaborative community, the collaborative community system includes a user service subsystem responsible for user registration, login, user identity information management, and user smart tag management. Collaborative community users can have various identity types, such as human expert users, machine intelligence community users, machine intelligence call users, and platform support users.

[0177] According to some embodiments, users establish communities. The collaborative community has a community service subsystem. In addition to public communities, the collaborative community also supports users to establish their own communities through the community service subsystem, such as alliance communities and internal communities.

[0178] According to some embodiments, users initiate tasks. The collaborative community has a task management subsystem. This subsystem provides users with two interfaces for initiating tasks: a human-computer interaction interface and an API. Human expert users and machine intelligence community users have the authority to initiate tasks, while machine intelligence call users do not.

[0179] The user who initiates the task initiates the task in a professional or free style through the human-computer interface or program interface, and can specify the scope of the community in which the task is published. The scope of the community in which the task is published is the scope of the creative activities of the task. For example: the user who initiates the task can choose to publish the task in a public collaborative community or select one or several communities from the community list to publish the task. Alternatively, the user who initiates the task creates a new community to publish the task within the scope of this community. The user submits a request to initiate the task, and after the task is set, the task management subsystem receives the request to initiate the task submitted by the user, calls the code generation module, and pre-assigns a globally unique task number Task_ID to the request to initiate the task. The user who initiates the task obtains the task number, wherein: the task management subsystem receives the request to initiate the task submitted by the user, and after the task is set, calls the code generation module, and pre-assigns a globally unique task number Task_ID to the request to initiate the task and the user who initiates the task obtains the task number. The action can also be placed at a later time, and the globally unique task number will be assigned when the user publishes the task.

[0180] According to some embodiments, task setting is performed. The collaborative community has a task management subsystem, a community service subsystem, a collaborative template library, and a task setting subsystem. The task setting subsystem includes information exchange functions, demand analysis functions, and demand completion functions.

[0181] The collaborative community provides two ways for users to enter task requirements through the task setting subsystem: professional and free. After initiating a task, a user enters the task requirements. Based on the user's input, the task setting subsystem generates task setting information. The task setting subsystem feeds this generated task setting information back to the user for confirmation. If the user confirms, the task setting subsystem generates a confirmation version of the task setting information. The task requirements entered by the user (including the interaction process) and the task setting information generated by the task setting subsystem are submitted to the task management subsystem and archived in the user's task log.

[0182] The user enters task requirement information in a professional manner. Users who enter task requirement information in a professional manner can typically be industry-specific human experts or industry-specific machine intelligence community users. The user who initiates the task browses or accesses a collaboration template library through a human-computer interface or program interface and specifies the collaboration template to be used for the task. According to some embodiments, based on the user-specified collaboration template, the task setting information processing module of the task setting subsystem requires the user to enter task setting information according to the requirements of the task setting object of the collaboration template.

[0183] As a user enters task setting information, the task setting information processing module of the task setting subsystem verifies the user's input based on the task setting object obtained from the collaboration template. During the verification process, if any questions require supplementation or clarification, the task setting information processing module invokes the interaction module to send a message to the user to initiate interaction. Through this interaction, the task setting information processing module completes the task setting information until it determines that the user's input is valid and complete.

[0184] The user inputs the task requirement information in a free style. The user who inputs the task requirement information in a free style can generally be a mass human expert user or an embodied intelligent machine intelligence community user.

[0185] The user who initiates the task inputs the task requirement information in a free style through a human-computer interface or a program interface, including the following actions:

[0186] 1) Freely input other task requirement information.

[0187] 2) Based on the task requirement information, the Task Intent Analysis module of the Task Setting subsystem performs a task intent analysis. If any questions require supplementation or clarification during the task intent analysis process, the module calls the Interaction Module to send a message to the user to initiate interaction. Through this interaction, the module completes the task requirements until the user's task intent is clearly understood.

[0188] According to some embodiments, the task intent analysis module can be constructed using a custom NLP model (such as BERT) combined with a keyword extraction tool, or it can be constructed based on an open source model using intent analysis corpus pre-training, which is not limited by the present invention.

[0189] 3) According to the task intent, the collaboration template processing module of the task setting subsystem determines a collaboration template corresponding to the task intent.

[0190] The main contents of the collaboration template include the initial task state diagram, which includes a collaboration template node (root node), a task node (task setting object node, used to set task setting information), a subtask node, and a platform support node (optional).

[0191] Among them, in the initial task state diagram, the task node can be represented by the task setting object node. The platform support node may include an arbitrator node, a quality manager node, and a professional committee node. The initial task state diagram also includes the association relationship of the subtask nodes. The association relationship may include nesting (ownership-attribution), series connection (derivation-dependency), parallel bifurcation, and loop iteration. Subtasks may include framework subtasks and atomic subtasks. In the process of collaboration, framework subtasks gradually establish the mutual association relationship between subtasks through hierarchical planning, step decomposition, module bifurcation, and loop iteration, including nesting, looping, series connection, and parallel connection, thereby forming a structured and dynamically evolving task hierarchical planning. Atomic refers to the gradual decomposition of large tasks in the process of collaboration, and eventually decomposed into a series of atomic subtasks that are interrelated and minimize mutual information.

[0192] Collaboration template nodes contain collaboration template description information, and each subtask node contains subtask description information. In the initial task state diagram, task nodes, collaboration template nodes, subtask nodes, and platform support nodes can each have multiple tags. Within the task template, the task template can pre-assign initial values to certain of these tags. After task configuration, the task planning subsystem can pre-assign default values to these tags based on the task configuration information, user preferences, and other information.

[0193] The users corresponding to the user sites owned by nodes are dynamically assigned in real time. In the initial task state diagram, task nodes, collaboration template nodes, subtask nodes, and platform support nodes can all have user sites to support communication and task scheduling within the task scenario. Only the user sites owned by collaboration template nodes have corresponding specific users, typically the user who published the collaboration template, i.e., the collaboration template publisher. Other nodes, including task nodes and subtask nodes, have empty user sites, meaning that their user sites do not yet correspond to specific users.

[0194] There are two types of user locations for subtasks: push-type user locations and assigned user locations. For users corresponding to push-type user locations, after receiving a task, they can independently decide whether to participate in the creation of the task. If the user does not want to participate, they can ignore the pushed task information. If the user does want to participate, they can independently take the order and participate in the creation process of the pushed task. Typically, users corresponding to push-type user locations are human experts or machine intelligence community users.

[0195] For users associated with assigned user sites, upon receiving task information, they will follow the agreed-upon procedures to create the subtasks specified in the task information. Typically, users associated with assigned user sites are machine intelligence-invoked subtasks. Alternatively, for tasks conducted within the community, assigned user sites can also be human expert users.

[0196] The type of user site owned by a subtask node is determined by the subtask process interaction tag owned by the subtask node. If the subtask process interaction tag owned by the subtask node is set to Push, the user site owned by the subtask node is a Push-type user site. If the subtask process interaction tag owned by the subtask node is set to Dispatch, the user site owned by the subtask node is a Dispatch-type user site.

[0197] The creation state of a subtask node. In the initial task state diagram, each subtask node has a creation state to support process management. The creation state includes a creation state and a non-creation state. The system sets the creation state based on the series (derivation-dependency relationship) between subtasks. Specifically, in the initial task state diagram, the task setting object node is in the creation state, and the other subtasks are in the non-creation state.

[0198] 4) Based on the task setting object obtained from the collaboration template, the task setting information processing module of the task setting subsystem extracts the task setting information from the task requirement information input by the user. During the task setting information extraction process, if any questions require supplementation or clarification, the task setting information processing module calls the interaction module to send a message to the user to initiate interaction. Through interaction, the task setting information processing module completes the task setting information until the complete task setting information is extracted.

[0199] According to some embodiments, the process of determining the collaboration template is that the user inputs task requirement information in a free style, and based on the task intent, the collaboration template processing module of the task setting subsystem determines the collaboration template corresponding to the task intent. For example, the collaboration template processing module determines the collaboration template corresponding to the task intent by matching and retrieving the collaboration template library.

[0200] Specifically, the collaborative template processing module performs information matching based on the task intent content information and the collaborative template description information in the collaborative template library. The collaborative template processing module determines the collaborative template with the highest matching degree as the collaborative template corresponding to the task intent; or the collaborative template processing module pushes several collaborative templates with the highest matching degree to the user who initiated the task, and the user selects one of the collaborative templates as the collaborative template corresponding to the task intent.

[0201] If the collaboration template processing module fails to retrieve a collaboration template that satisfies the task intent, the collaboration template processing module searches for network resources related to the task intent and invokes a machine intelligence-invoking user to generate a collaboration template corresponding to the task intent. If the machine intelligence-invoking user successfully generates a collaboration template corresponding to the task intent, the collaboration template processing module determines the collaboration template as the collaboration template corresponding to the task intent.

[0202] The machine intelligence calling user is a machine intelligence system with the ability to generate collaborative templates. Specifically, the machine intelligence calling user can be a generative pre-trained large model, using the collaborative templates in the collaborative template library and their corresponding task intentions and related resources as training materials for pre-training.

[0203] A collaboration template that meets the requirements for matching the task intent means that the matching degree between the collaboration template description information of the collaboration template and the content information of the task intent is not lower than the matching degree threshold set by the task setting subsystem, or not lower than the matching degree threshold required by the task type of the task corresponding to the task intent.

[0204] The information matching metric calculation method can be based on keyword matching, such as statistical keyword overlap or weighted keyword matching; or it can be based on semantic understanding, such as using the pre-trained language model BERT or matching based on semantic role labeling. This invention is not limited to this.

[0205] If the machine intelligence calling user fails to generate a collaborative template corresponding to the task intent, the emergency fallback is to conventional intelligent processing. The task setting subsystem calls the machine intelligence calling user, submits the task intent to the machine intelligence calling user, and generates a machine intelligence processing result corresponding to the task intent. The task setting subsystem calls the interaction module to output information to the user who initiated the task. The output information includes two parts. The first part informs the user who initiated the task: Regarding the task initiated by the user, the system currently does not have a corresponding collaborative template and is temporarily unable to carry out expert-level collaborative creation. The conventional processing result obtained by the system calling the machine intelligence calling user is first provided for reference. At the same time, the machine intelligence processing result corresponding to the task intent generated by the machine intelligence calling user is attached. The second part informs the user who initiated the task: the collaborative template creation requirements required for the task initiated by the user are published in the collaborative template creation area. When the collaborative template required for the task is completed, the collaborative creation process of the task can be continued.

[0206] New templates are added to support the expansion of the collaborative template library and the evolution of system capabilities. The collaborative template processing module publishes the collaborative template generation requirements corresponding to the task intent to the collaborative template creation area of the collaborative community. Users in the collaborative community can browse these collaborative template generation requirements in the collaborative template creation area. At the same time, the collaborative community will match the collaborative template requirement information with the user information of the collaborative community users and push the collaborative template generation requirements to the collaborative community users with the highest matching scores.

[0207] Based on the collaboration template generation requirements, users in the collaboration community generate corresponding collaboration templates and submit them for review. Once approved by the platform, the user publishes the collaboration template, uploads it to the blockchain, and obtains the NFT (Non-Fungible Token) corresponding to the collaboration template. The collaboration template processing module identifies the collaboration template published by the user as the collaboration template corresponding to the task intent.

[0208] The generative pre-trained large model with collaborative template generation capabilities is iteratively enhanced. The collaborative template processing module incorporates the collaborative templates published by the user into the collaborative community's collaborative template library. As the collaborative template library continues to expand, the generative pre-trained large model with collaborative template generation capabilities continuously enhances its collaborative template generation capabilities through iterative training.

[0209] According to some embodiments, task resetting may also be required.

[0210] The task setting subsystem feeds the generated task setting information back to the user for confirmation. If the user confirms, the task setting subsystem generates a confirmation version of the task setting information. If the user does not confirm, they can continue to enter new task requirements. Based on the new task requirements, the system modifies the previously generated task setting information and generates new task setting information.

[0211] The task requirements (which may include an interactive process) input by the user and the task setting information confirmation version generated by the task setting subsystem are submitted to the task management subsystem and archived in the user's task log.

[0212] According to some embodiments, the collaborative community system includes a task planning subsystem responsible for generating a task planning solution. The task planning subsystem receives a confirmation version of task setting information and generates a default task planning solution corresponding to the confirmation version of task setting information. The task planning subsystem then provides feedback to the user regarding the default task planning solution.

[0213] The main contents of the default task planning scheme include setting a task status diagram, which includes a collaboration template node, a task node (task setting information node), a subtask node, and a platform support node (optional).

[0214] In the task setting state diagram, the task node can be represented by a task setting information node. In the task setting state diagram, the task planning subsystem can pre-set default values for the values in the subtask tags based on the task setting information, user preferences, and other information.

[0215] The users corresponding to the user sites owned by a node are dynamically assigned in real time. In the task setting state diagram, the user sites owned by a task node typically correspond to the user who initiated the task. The user who initiated the task is typically the one who entered the task setting information for that task. In the task setting state diagram, the user sites owned by each subtask node and platform support node are empty, meaning that the user sites of these nodes do not yet correspond to specific users.

[0216] The creative status of the subtask node. In the task status diagram, the creative status of the subtask nodes that do not depend on other subtasks is the creative status; the creative status of the subtask nodes that depend on other subtasks is the non-creative status.

[0217] According to some embodiments, the user can adjust the task label. The task planning subsystem also provides the task initiating user with the function of adjusting the task label assignment in the task planning solution.

[0218] After the default task planning solution is generated, each subtask in the default task state diagram included in the default task planning solution has several (at least one) tags. These tags have default values. These default values are pre-estimated and generated by the task planning subsystem based on task setting information for the task, user data such as user preferences, and task big data.

[0219] Before publishing a task, the user initiating the task can adjust the tags as needed through the human-computer interface or program interface. After the tags are adjusted, the task published by the user includes the adjusted task plan. The system executes the task using the adjusted task plan. The user initiating the task can also publish the task directly using the default tag values without making any adjustments. In this case, the published task uses the default task plan, or the adjusted task plan is equivalent to the default task plan.

[0220] According to some embodiments, task replanning is performed. The system provides the user with a default task planning solution. If the user does not confirm the solution, the user can enter new task requirements. The new task requirements trigger the task setting subsystem to perform task replanning and generate a new task setting information confirmation version. Based on the new task setting information confirmation version, the task planning subsystem generates a new default task planning solution.

[0221] According to some embodiments, after a task plan is generated, the user initiating the task can submit and publish the task. The task is published within the community scope specified by the task community scope label. For example, if the task community scope label is a public collaborative community, the task is published in the public collaborative community. If the task community scope label is a certain alliance community or internal community, the task is published in the alliance community or internal community.

[0222] Figure 5 A schematic diagram illustrating a system issuing tasks according to an example embodiment.

[0223] See also Figure 5 ,According to an example embodiment, the task publishing method is as follows.

[0224] In S501, task requirement information, task setting information, and task planning information are received, and a task data block DB {Task_ID(N)} corresponding to the collaborative creation task Task_ID(N) is generated. This includes:

[0225] Task requirement information (including the first task intention description, optional), task adjustment information (including task adjustment information confirmation version), task planning information (including task planning adjustment plan).

[0226] The globally unique task identifier Task_ID(N) is a globally unique task identifier generated by the system for the current task, which may be a character string or a binary code string.

[0227] The identity information of the task issuer includes the user ID and / or public key of user A.

[0228] The data block identifier of this task is DB[Task_ID(N)].

[0229] In S503, the server or user device generates a digital fingerprint of the task data block based on the task data block, which can be a digital fingerprint generated by the user using a private key to digitally sign the task data block.

[0230] In S505 , the server or user device stores the task data block and generates an access address of the task data block (such as a URL or other addressing address, which may be one access address or a list of several access addresses).

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

[0232] In S509 , the server or user equipment publishes the task data packet.

[0233] Publishing a task data package includes the right to be recorded on the chain, and also includes enabling relevant users with access rights in the collaborative creation and collaboration community to access or be pushed to the task data package.

[0234] According to some embodiments, a method for publishing a task data packet is that a user terminal or server may publish the task data packet to a suitable blockchain for recording, and obtain a blockchain access address as an index for the task data packet. Specifically, the following steps may be included:

[0235] (1) Select a suitable blockchain. Other public chains, consortium chains, or private chains can be selected, and this invention does not limit this.

[0236] (2) Developing a task data package and publishing a smart contract on the blockchain and deploying it on the blockchain.

[0237] (3) The task publisher initiates a task data packet publishing transaction, calls the task data packet publishing smart contract on the blockchain, publishes the task data packet to the blockchain, and obtains the corresponding blockchain access address as the task data packet index.

[0238] According to some embodiments, another way to publish a task data package is that the user terminal or server can upload the task data package DP[Task_ID(N)] to a task library. Through the task library, users of the collaborative creation and collaboration community can browse the task according to their permissions and needs.

[0239] According to some embodiments, another way to publish a task data package is to assign or push the task to appropriate collaborative creation community users. Specifically, the following steps may be included:

[0240] (1) The user device or server submits the task data packet DP[Task_ID(N)] to the task scheduling subsystem.

[0241] (2) The task scheduling subsystem generates a task scheduling plan for the current collaborative task corresponding to the task data packet DP[Task_ID(N)], matches the subtask related information of each subtask in the authorable state with the user tag information of each user in the community scope of the task release, and sets the corresponding user corresponding to the user position of the corresponding subtask according to the matching result.

[0242] (3) According to the task scheduling plan, the task scheduling subsystem sends the task data packet DP[Task_ID(N)] and the identifier of the corresponding subtask to the corresponding users within the "community scope of task release" by dispatching or pushing the task data packet DP[Task_ID(N)].

[0243] In this embodiment, to protect the privacy of the task publisher, the community tag of the intelligent resource not only records the current community to which the intelligent resource belongs, but also includes the role of the intelligent resource in the community to which it belongs. The role of the intelligent resource in the community to which it belongs includes creative role, demand-oriented role, and support-oriented role.

[0244] Before the task scheduling plan is generated, the task status diagram in the task data packet is the set task status diagram.

[0245] After the task scheduling scheme is generated, the task scheduling subsystem generates a first task state diagram for the current collaborative task corresponding to the task data packet.

[0246] For the current collaborative task corresponding to the task data packet, the task scheduling work carried out by the task scheduling subsystem includes:

[0247] Add several platform support nodes to the task state diagram of the current collaborative task corresponding to the task data packet, such as arbitration committee members, quality management personnel, and professional committee members. Each platform support node has node description information. (Platform support nodes can also be added to the task state diagram during the task setting stage, which is not limited in the present invention.)

[0248] For the platform support nodes, the "task information of the current collaborative task" and platform support node description information are matched with the "intelligent resource information of relevant platform support users in the collaborative community." Based on the information matching results, users corresponding to the user locations owned by the platform support nodes are assigned.

[0249] For subtask nodes in the authorable state in the set task state diagram included in the current collaborative task corresponding to the task data packet, the "subtask-related information of the subtask node" is matched with the "relevant intelligent resource information in the collaborative community." Based on the information matching result, the user corresponding to the "user location owned by the subtask node" is set.

[0250] The relevant concepts included in the above work content are explained as follows:

[0251] The task information of the current collaborative task includes: task setting information, task planning information (including collaborative template information, task setting information, task status diagram, label information, etc.), and task publisher identity information.

[0252] The intelligent resource information of the relevant platform supporting users in the collaborative community includes: the intelligent resource tag information of each supporting functional user within the "community scope of task release" in the task setting information of the current collaborative task.

[0253] The subtask related information of the subtask node includes subtask prior information, subtask description information, and subtask tag information. In the task setting state diagram, for subtasks in the authorable state, their subtask prior information includes task setting information.

[0254] The relevant intelligent resource information in the collaborative community includes: intelligent resource tag information of each creative functional user within the “community scope of task release” in the task setting information of the current collaborative task.

[0255] According to some embodiments, the task scheduling subsystem publishes the task data package to the alliance community specified by the task community scope tag included in the current collaborative task, allowing creative functional users within the alliance community to access the task data package. Furthermore, the task scheduling subsystem schedules the current collaborative task corresponding to the task data package according to the task scheduling scheme, including pushing and assigning subtasks.

[0256] The above three methods of publishing task data packets can be used simultaneously or in combination, and the present invention does not impose any special restrictions on this.

[0257] For push-type subtasks, the user whose user location corresponds to the task being pushed can independently decide whether to participate in the creation of the pushed task. If the user does not want to participate, they can ignore the pushed task information. If the user does want to participate, they can independently take the order and participate in the creation process of the pushed task. The users corresponding to the user locations of push-type subtasks are human expert users and machine intelligence community users.

[0258] For dispatched subtasks, upon receiving the task information, the user corresponding to the assigned user site will proceed with the creation of the subtask specified in the task information according to the agreed-upon procedures. The user corresponding to the assigned user site is typically a machine intelligence user. Alternatively, for tasks conducted within the internal community, the user corresponding to the assigned user site can also be a human expert user.

[0259] Figure 6 A flowchart illustrating authoring of a push-type subtask according to an example embodiment is shown.

[0260] See also Figure 6 ,The steps for creating push-type subtasks are described as follows.

[0261] In S601 , user a selects subtask T and inputs creation information of subtask T.

[0262] After a human expert user or machine intelligence user selects a pushed subtask, or selects a subtask that can be created through the public collaborative community task hall / community task list, they issue a creation request. The system pushes the creation content block object of the subtask to the user.

[0263] The user enters the subtask creation information in the content block object. The user submits and confirms the creation information. For human expert users, this action is triggered by clicking a confirmation button on the content block object page. For machine intelligence users, this action is triggered by program instructions.

[0264] In S603, the system receives the creation information submitted by user a and generates a creation information data block DB{Task_ID(N).[T,a(1)]} corresponding to the creation information, including:

[0265] Creative content information, wherein the creative content information includes creative information submitted by the user.

[0266] Task ID, Task_ID(N).

[0267] Creator identity information, including the user's user ID and / or user public key.

[0268] This creation information data block is identified by DB{Task_ID(N).[T,a(1)]}.

[0269] In S605, the server or user device generates a digital fingerprint of the creative information data block based on the creative information data block, which can be a digital fingerprint generated by the user using a private key to digitally sign the creative information data block.

[0270] In S607, the server or user device stores the creation information data block and generates an access address for the creation information data block.

[0271] In S609, the server or user device generates a creation information data packet DP{Task_ID(N).[T,a(1)]}, which includes the following contents: creation information data block access address, creator identity information (such as user public key), and creation information data block digital fingerprint.

[0272] In S611, the server or user device publishes the creation information data package. Publishing the creation information data package includes recording rights on the chain and allowing relevant users with access rights in the collaborative creation collaboration community to access or be pushed to the creation information data package.

[0273] According to some embodiments, an operation for publishing a creative information data package is that a user terminal or server may publish the creative information data package to a suitable blockchain for recording, and obtain a blockchain access address as an index for the creative information data package. Specifically, the following steps may be included:

[0274] (1) Select a suitable blockchain. For example, select the BSN consortium chain. Of course, other public chains, consortium chains, or private chains can also be selected, and this invention does not limit this.

[0275] (2) Developing and creating information data packets on the blockchain and publishing smart contracts, and deploying them on the blockchain.

[0276] (3) The creator initiates a creative information data package publishing transaction, calls the creative information data package publishing smart contract on the blockchain, publishes the creative information data package on the blockchain, and obtains the corresponding blockchain access address as the creative information data package index.

[0277] According to some embodiments, another operation for publishing a creative information data packet is that a user terminal or server may upload the creative information data packet DP{Task_ID(N).[T,a(1)]} to a task library. If the execution content corresponding to the creative information data packet is the first execution content of the task, the first task state diagram of the task evolves to the second task state diagram. Through the task library, users of the collaborative creative community can browse the creative information of the task Task_ID(N) according to their permissions and needs.

[0278] Figure 7 A flowchart illustrating authoring of dispatched subtasks according to an example embodiment is shown.

[0279] See also Figure 7 ,The steps for creating a dispatched subtask are described as follows.

[0280] In S701, user b receives task information and generates creation information of subtask T.

[0281] User b receives task information including a subtask T assigned to the user. After receiving the assigned subtask T, user b executes the subtask according to predetermined rules, generates creation information for the subtask T, and submits and confirms the creation information.

[0282] At S703, the system receives the creation information submitted by user b and generates a creation information data block DB{Task_ID(N).[T,b(1)]} corresponding to the creation information, including:

[0283] Creative content information, wherein the creative content information includes creative information submitted by the user.

[0284] Task ID, Task_ID(N).

[0285] Creator identity information, including the user's user ID and / or user public key.

[0286] This creation information data block is identified by DB{Task_ID(N).[T,b(1)]}.

[0287] In S705, the server or user device generates a digital fingerprint of the creation information data block according to the creation information data block.

[0288] Specifically, it can be a digital fingerprint generated by the user using a private key to digitally sign the creation information data block.

[0289] In S707, the server or user device stores the creation information data block and generates an access address for the creation information data block.

[0290] At S709 , the server or user device generates a creation information data packet DP{Task_ID(N).[T,b(1)]}.

[0291] Specifically, it includes the following contents: access address of the creation information data block, creator identity information (such as user public key), and digital fingerprint of the creation information data block.

[0292] At S711, the server or user device publishes the creation information data packet.

[0293] Publishing a creative information data package includes the right to be recorded on the chain, and also includes enabling relevant users with access rights in the collaborative creation community to access or be pushed to the creative information data package. The operation of publishing a creative information data package is as follows:

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

[0295] (1) Select a suitable blockchain. For example, select the BSN consortium chain. Of course, other public chains, consortium chains, or private chains can also be selected, and this invention does not limit this.

[0296] (2) Developing and creating information data packets on the blockchain and publishing smart contracts, and deploying them on the blockchain.

[0297] (3) The creator initiates a creative information data package publishing transaction, calls the creative information data package publishing smart contract on the blockchain, publishes the creative information data package on the blockchain, and obtains the corresponding blockchain access address as the creative information data package index.

[0298] Alternatively, the user terminal or server can upload the creation information data packet DP{Task_ID(N).[T,b(1)]} to the task library. If the execution content corresponding to the creation information data packet is the first execution content of the task, the first task state diagram of the task evolves to the second task state diagram. Through the task library, users of the collaborative creation community can browse the creation information of the task Task_ID(N) according to their permissions and needs.

[0299] Figure 8 A block diagram showing system components for publishing tasks in a collaborative community according to an example embodiment is shown.

[0300] See also Figure 8 The system for publishing tasks in a collaborative community includes a template determination module 801 , a setting module 803 , a planning module 805 and a publishing module 807 .

[0301] According to an example embodiment, the template determination module 801 determines a first collaboration template for completing a first task. The setting module 803 determines task setting information based on the first collaboration template determined by the template determination module 801. The planning module 805 generates task planning information for the first task based on the task setting information provided by the setting module 803. The publishing module 807 publishes the first task based on the task planning information generated by the planning module 805.

[0302] According to some embodiments, the template determination module may include an acquisition submodule, a matching submodule, and a generation submodule. The acquisition submodule is used to acquire a first task intent description from a task publisher; the matching submodule automatically matches a first collaboration template in a collaboration template library based on the first task intent description obtained by the acquisition submodule; and the generation submodule asynchronously generates a collaboration template that matches the first task intent description as the first collaboration template.

[0303] According to some embodiments, the publishing module 807 may include a scheduling submodule and a sending submodule. The scheduling submodule determines a task scheduling scheme for the first task in combination with task planning information and user tag information. The sending submodule sends the subtask to the corresponding user set by the task scheduling scheme through push and / or dispatch according to the task scheduling scheme.

[0304] The system for publishing tasks in the collaborative community in this embodiment processes the raised questions. The process of publishing tasks in the collaborative community is similar to the above method and will not be described in detail.

[0305] The method of the present invention is further verified below with reference to the examples.

[0306] Example 1

[0307] The method of issuing tasks in this patent collaboration community is evaluated using the problem of "preventing avian influenza".

[0308] The user initiates a task and enters the task requirements in a free style. The user selects the community of this patent and enters the task requirements.

[0309] For example: User A selects the alliance community "Nanhai City Poultry Association" and enters the information: Evaluate patents to prevent avian influenza.

[0310] Based on the task requirement information input by user A, the task intent processing module of the task setting subsystem performs task intent analysis. The task intent processing module is an AI agent that specializes in analyzing task intent.

[0311] For example:

[0312] The result of task intent analysis is: User A needs to conduct a patent evaluation on the patent "Prevention of Avian Flu".

[0313] The task intent processing module searched for "patents for preventing avian influenza" and found 2,826 related patents.

[0314] The task intention processing module reasons about the patent evaluation task and believes that the patent evaluation task may include two intentions: the patent scope of the patent evaluation and the purpose of the patent evaluation.

[0315] The patent scope of patent evaluation tasks includes: patent evaluation of specific patent cases and patent evaluation in a certain field.

[0316] The purposes of patent evaluation tasks include: patent infringement risk assessment, patent value assessment, and patent rights stability assessment.

[0317] To this end, the task intention processing module determines that the patent scope and purpose of user A's patent evaluation need to be further clarified.

[0318] The system outputs interactive information, and the task intention processing module of the task setting subsystem calls the interactive module to output information based on the analysis results.

[0319] For example:

[0320] System output: Hello user, 2,826 patents related to "avian influenza prevention" have been retrieved. Further determination of the patent scope and intended use for the patent evaluation is required. Regarding patent scope, are you evaluating a patent case related to avian influenza prevention, or are you evaluating patents related to "avian influenza prevention"? Regarding intended use, are you evaluating the risk of infringement, the value of the patent, or the stability of the patent?

[0321] The user enters new task requirements.

[0322] For example:

[0323] User A inputs the information: I want to make a value assessment on the patent for “Preventing Avian Influenza in Chicken Flocks”.

[0324] The task intent has been clarified, and the task intent is analyzed. Based on the new task requirement information input by user A, the task intent processing module of the task setting subsystem conducts task intent analysis again.

[0325] For example, the system outputs information: The analysis results show that the user's task intention is clear: the user wants to make a value assessment of the patent "Preventing Avian Influenza in Chickens".

[0326] Determine the collaboration template. According to the task intent, the collaboration template processing module of the task setting subsystem determines the collaboration template corresponding to the task intent and determines the "patent value assessment collaboration template."

[0327] Among them, the collaboration template processing module is an AI agent that determines the collaboration template based on the task intention.

[0328] The collaboration template is characterized by:

[0329] The collaboration template includes template description information, task setting objects, and subtasks;

[0330] The template description information is used to describe the collaboration template;

[0331] The task setting object is used by the task publisher to input task setting information;

[0332] The subtasks include subtask description information, and there are dependencies between the subtasks;

[0333] The subtask is used to provide the creator with input of creation information according to the subtask description information;

[0334] The dependencies between the subtasks are used to set the creation status of the subtasks; and / or

[0335] The collaboration template also includes a creative content block of a digital work and a first content generation method;

[0336] The creative content blocks of the digital work include content block objects, content block presentation attributes, and content block relationship attributes;

[0337] The content block object is used to input the content of the work;

[0338] The content block presentation attribute is used to describe the presentation form of the work content of the content block object in the digital work;

[0339] The content block relationship attribute is used to describe the relationship between the content block and other content blocks in the digital work;

[0340] The first content generation method is used to describe a method for generating the creative content block from the execution content of the subtask;

[0341] The collaborative creation task further includes task setting information, and the task setting information is provided to the creator so that the creator can input creation information according to the task setting information and the subtask description information.

[0342] To determine whether the task setting information is complete, the task setting subsystem includes a task setting information processing module. The task setting information processing module is an AI agent that determines the task setting information based on the collaboration template and the task requirement information input by the user.

[0343] For example:

[0344] According to the task setting object included in the "Patent Value Assessment Report Collaboration Template", the task setting information processing module obtains task setting information from the task requirement information input by the user.

[0345] Specifically, the task objective for the "Patent Value Assessment Report Collaboration Template" requires obtaining a patent application number, patent publication number, or patent grant number that effectively corresponds to a specific patent. However, the task intent processing module searches for "patents for preventing avian influenza in chickens" and finds 1,868 related patents. The task setting information processing module fails to obtain the required information from the task requirement information entered by User A. Therefore, the task setting information processing module reports that the required task setting information for the current task is incomplete.

[0346] The system outputs interactive information, and the task setting information processing module of the task setting subsystem calls the interactive module to output information based on the analysis results.

[0347] For example:

[0348] System output: Hello user! There are 1,868 patents related to "avian influenza prevention in chickens." Please provide the application number, publication number, or authorization number of the patent to be evaluated to determine which one you want to evaluate.

[0349] The user inputs new task requirement information, such as the user input information: application number 100012345678.9.

[0350] The mission intent has been clarified, analyze the mission intent.

[0351] Based on the new task requirement information input by user A and combined with the previous conversation history, the task intention processing module of the task setting subsystem conducts task intention analysis again.

[0352] For example: After search and analysis, the patent name of patent application number 100012345678.9 is "A chicken flock management method and system for preventing avian influenza."

[0353] At this point, the user's task intention has been clarified, which is to evaluate the value of the patent application number "100012345678.9". Figure 1 To.

[0354] Determine the collaboration template. According to the task intent, the collaboration template processing module of the task setting subsystem determines the collaboration template corresponding to the task intent, determines the "patent value assessment collaboration template", and determines whether the task setting information is complete.

[0355] According to an example embodiment, the user's task intention of "making a value assessment on the patent with patent application number "100012345678.9"" is matched with the collaboration template description information in the collaboration template library, and the collaboration template that meets the matching requirements, for example, the patent value assessment collaboration template, is provided to the task publisher.

[0356] Based on the task setting object obtained from the "Patent Value Assessment Report Collaboration Template" and the task requirement information obtained from the user, the task setting information processing module of the task setting subsystem conducts analysis to determine whether the task setting information required for the current task is complete.

[0357] Analysis shows that the task requirement information entered by the user is patent application number 100012345678.9, and the patent name corresponding to this patent application number is "A chicken flock management method and system for preventing avian influenza." The technical field of this patent is the prevention of avian influenza in chicken flocks, which is consistent with the user's intention. Figure 1 To.

[0358] The task setting information processing module gives an analysis conclusion: the task setting information required for the current task is complete.

[0359] Generate task setting information. The task setting subsystem generates task setting information.

[0360] For example:

[0361] The community scope of the task release: Alliance community "Nanhai City Poultry Association".

[0362] Collaboration template: Collaboration template α (1588), patent value assessment report collaboration template.

[0363] Task setting information: Patent application number "100012345678.9".

[0364] User confirmation of task setting information (optional)

[0365] Push the generated task setting information to the user and ask the user to confirm.

[0366] User confirmation.

[0367] Generate a default version of mission planning information.

[0368] Based on the above task setting information, a default version of the task planning information is generated. The default version of the task planning information includes the task number (such as 10068) pre-assigned by the task management subsystem to the currently initiated task, as well as the task state diagram and node description information.

[0369] The default scheme for task planning includes but is not limited to the default set task state diagram.

[0370] The default task state diagram includes task nodes, collaboration template nodes, subtask nodes, and platform support nodes (optional).

[0371] Among them, the task node can be represented by the task setting information node. The platform support node can include the arbitrator node, the quality manager node, and the professional committee node.

[0372] The task state diagram also includes the relationship between subtask nodes. The relationship may include nesting (ownership-attribution), series connection (derivation-dependency), parallel forking, and loop iteration. Subtasks may include framework subtasks and atomic subtasks. The task state diagram of the task currently initiated by user A can be found in Figure 9 and Figure 10 .

[0373] For machine intelligence users, the task status diagram is obtained by reading the data structure, as shown in Table 1 below. This table is only an example and will be revised later to achieve the correspondence between the subtask table and the task status diagram.

[0374] Table 1

[0375] Subtask ID Subtask description information Subtask dependencies Subtask(1) Keywords and search strategies No dependencies on other subtasks Subtask(2) Related comparative literature Dependency Subtask(1) Subtask(3) Technology Value Assessment Dependency Subtask(2) Subtask(4) Legal Value Assessment Dependency Subtask(2) Subtask(5) Market value assessment No dependencies on other subtasks Subtask(9) Evaluation Conclusion Depends on Subtask(3), Subtask(4), Subtask(5)

[0376] Node description information: Task nodes have task description information, collaboration template nodes have collaboration template description information, and each subtask node has subtask description information. The subtask name is also part of the subtask description information.

[0377] The task tags (default values) that a node possesses. In the task state diagram, task nodes, collaboration template nodes, subtask nodes, and platform support nodes can each possess several tags. Based on task configuration information, user preferences, and other information, the task planning subsystem can pre-assign default values to the tags.

[0378] The user sites owned by the nodes (dynamically allocated in real time). In the set task status diagram, task nodes, collaboration template nodes, subtask nodes, and platform support nodes can all have user sites to support communication and task scheduling within the task scenario.

[0379] The user site of a task node is usually the user who initiated the task. The user who initiated the task is usually the person who inputs the task setting information. The user site of a collaboration template node is usually the user who published the collaboration template, i.e., the collaboration template publisher.

[0380] The user sites of each subtask node and platform support node are empty, that is, the user sites of these nodes do not yet correspond to specific users.

[0381] There are two types of user sites for subtasks: push-type user sites and dispatch-type user sites.

[0382] For users corresponding to push-type user sites, after receiving a task, they can independently decide whether to participate in the creation of the task. If the user does not want to participate, they can ignore the pushed task information. If the user does want to participate, they can independently take the order and participate in the creation process of the pushed task. Typically, users corresponding to push-type user sites are human expert users and machine intelligence community users.

[0383] For users assigned to assigned user sites, upon receiving task information, they will follow the agreed-upon procedures to create the subtasks specified in the task information. Typically, users assigned to assigned user sites are machine intelligence users. Alternatively, for tasks performed within the community, assigned user sites can also be human expert users.

[0384] In the task state diagram above, the subtasks for machine intelligence community users at the user site include: 1.2 Related Patents and Literature, and T4 Legal Subtasks. The subtasks for machine intelligence callers at the user site include: T6 Evaluation Conclusion. The subtasks for human expert users at the user site include: all other subtasks in addition to the above subtasks.

[0385] The creation status of the subtask node. In the set task state diagram, each subtask node has a creation status to support process management. The creation status includes a creation state and a non-creation state. The system sets the creation status based on the series connection (derivation-dependency relationship) between subtasks. Specifically, in the first task state diagram, those subtask nodes that do not depend on other subtasks have a creation state of creation state; those subtask nodes that depend on other subtasks have a non-creation state.

[0386] The user confirms the task planning information, and the generated default version of the task planning information is pushed to the user for confirmation.

[0387] The user adjusts the task plan information. After receiving the default version of the task plan information, the user only adjusts the task process interaction label, changing the default value of "Release and Done" to "Release and Participate", while other aspects remain unchanged. The user then confirms the submission.

[0388] Generate a confirmation version of the task planning information. Based on the task planning information submitted by the user, the task planning subsystem generates a confirmation version of the task planning information.

[0389] Release the task. After the task planning information confirmation version is generated, the user releases the task.

[0390] Example 2

[0391] The method of publishing tasks in this patent collaboration community is evaluated using the question "How can patients with hypoglycemia lose weight?"

[0392] Users input task requirements in a free style. The intelligent resource tags of a certain mass human expert user E include: alliance community "health management expert service" and demand-based functions.

[0393] User E selects the alliance community "Health Management Expert Service" to initiate a task.

[0394] The user inputs the task requirements in a free style. User E inputs the task requirement information "low blood sugar patients lose weight".

[0395] Determine whether the task intent is clear and find that the task intent needs further clarification.

[0396] According to the task requirement information input by user E, the task intention processing module of the task setting subsystem performs task intention analysis.

[0397] Task intent analysis results: User E inputs "Lose weight for hypoglycemia patients". This task may include two intentions: obtaining popular science knowledge and general suggestions on "How to lose weight for hypoglycemia patients" and formulating a health management plan for "Lose weight for hypoglycemia patients" for specific patients.

[0398] To this end, the task intention processing module determines that further clarification is needed. Regarding "low blood sugar patients lose weight", what does user E want to do?

[0399] The system outputs interactive information, and the task intention processing module of the task setting subsystem calls the interactive module to output information based on the analysis results.

[0400] For example:

[0401] System output: Hello user, regarding the "weight loss for hypoglycemic patients" task, the purpose needs to be further determined. For example, is it to obtain scientific knowledge and general advice on "weight loss for hypoglycemic patients," to develop a health management plan for "weight loss for hypoglycemic patients" for specific patients, or is there another purpose?

[0402] The user enters new task requirement information. The user enters new task requirement.

[0403] For example:

[0404] User E inputs information: I am a hypoglycemic patient and I would like you to develop a weight loss plan for me.

[0405] The mission intent has been clarified, analyze the mission intent.

[0406] According to the new task requirement information input by user E, the task intention processing module of the task setting subsystem conducts task intention analysis again.

[0407] For example:

[0408] System output information: The analysis results show that the user's task intention is clear: the user is a hypoglycemic patient and needs to develop a health management plan for weight loss.

[0409] Determine the collaboration template: Based on the task intent, the collaboration template processing module of the task setting subsystem determines the collaboration template corresponding to the task intent, but the determination action fails.

[0410] For example, according to the task intent, the collaboration template processing module fails to retrieve a collaboration template that meets the requirements of the task intent by searching the collaboration template library.

[0411] Afterwards, the collaborative template processing module generates a “weight loss health management plan for hypoglycemia patients” corresponding to the task intention by searching network resources and calling the machine intelligence calling user MG. The machine intelligence calling user MG returns a result of generation failure.

[0412] Fall back to traditional mode, fall back to conventional intelligent processing in an emergency, and call machine intelligence calling users.

[0413] After receiving the generation failure result from the machine intelligence calling user MG, the task setting subsystem calls the machine intelligence calling user DS and submits the task intent determined in the above steps to the user DS. The machine intelligence calling user DS generates a processing result corresponding to the task intent.

[0414] The system outputs interactive information, and the task intention processing module of the task setting subsystem calls the interactive module to output information based on the above results.

[0415] For example:

[0416] System output: Hello user, regarding your requested task of developing a "weight loss health management plan for hypoglycemia patients," we apologize that we currently do not have the required collaboration template and are unable to conduct expert-level collaborative creation. The following is general scientific knowledge and advice on "how to lose weight and related health management plans for hypoglycemia patients" generated by a machine intelligence-based user DS after searching online resources. For your reference, we wish you good health!

[0417] Regarding the request for a collaborative template for a weight loss health management program for hypoglycemic patients, we will publish it in the collaborative template creation area. Once the collaborative template is completed, we will continue to advance this task you initiated. Thank you for your understanding and support!

[0418] Publish to the collaborative template creation area to support the iterative evolution of collaborative template generation capabilities and publish template creation requirements.

[0419] After receiving a generation failure response from the machine intelligence calling user MG, the collaboration template processing module of the task setting subsystem posts a collaboration template generation request for the task "Weight Loss Health Management Program for Hypoglycemia Patients" corresponding to the task intent to the collaboration template creation area of the collaboration community. Users in the collaboration community can browse the collaboration template generation request in the collaboration template creation area.

[0420] At the same time, the collaboration community will also match the demand information of the collaboration template with the user information of the collaboration community users, and push the generation demand of the collaboration template to several collaboration community users with the highest matching degree.

[0421] The collaborative community user L generates the collaborative template α (16598) in the collaborative template creation area. After receiving the collaborative template generation requirement pushed by the system, the collaborative community user L generates the collaborative template (globally unique collaborative template number 16598) and submits it for review.

[0422] After approval by the relevant platform support user of the collaborative community system, user L publishes the collaborative template (collaboration template number 16588), for example, and records it on the chain. According to some embodiments, the collaborative template processing module of the task setting subsystem incorporates the collaborative template 16598 into the collaborative template library of the collaborative community.

[0423] The collaborative template developer L inputs the creation information of the collaborative template α(m), including: template description information, the initial task state diagram of the collaborative creation task (subtask system), the content block clustering system, reference creation information, and task setting objects.

[0424] The collaboration template is characterized by:

[0425] The collaboration template includes template description information, task setting objects, and subtasks;

[0426] The template description information is used to describe the collaboration template;

[0427] The task setting object is used by the task publisher to input task setting information;

[0428] The subtasks include subtask description information, and there are dependencies between the subtasks;

[0429] The subtask is used to provide the creator with input of creation information according to the subtask description information;

[0430] The dependencies between the subtasks are used to set the creation status of the subtasks; and / or

[0431] The collaboration template also includes a creative content block of a digital work and a first content generation method;

[0432] The creative content blocks of the digital work include content block objects, content block presentation attributes, and content block relationship attributes;

[0433] The content block object is used to input the content of the work;

[0434] The content block presentation attribute is used to describe the presentation form of the work content of the content block object in the digital work;

[0435] The content block relationship attribute is used to describe the relationship between the content block and other content blocks in the digital work;

[0436] The first content generation method is used to describe a method for generating the creative content block from the execution content of the subtask;

[0437] The collaborative creation task further includes task setting information, and the task setting information is provided to the creator so that the creator can input creation information according to the task setting information and the subtask description information.

[0438] After receiving the collaborative template generation request from the system, collaborative community user L initiates the collaborative template creation process. The collaborative template management subsystem pre-assigns a globally unique collaborative template number, 16598, to the collaborative template α(m) that may be generated by the collaborative template creation process. This collaborative template can be uniquely identified by the code α(16598).

[0439] The collaboration template description information is provided. The collaboration template 16598 includes the template description information: a collaboration template for the task of formulating a "weight loss health management plan for hypoglycemic patients", which customizes a personalized weight loss health management plan for hypoglycemic patients based on the patient's health status and dynamic data.

[0440] Generate the initial task state diagram. The initial task state diagram included in the collaboration template α (16598) can be found in Figure 11 Corresponding to the initial task state diagram, the subtask related information included in the collaboration template α (16598) is as follows in Table 2:

[0441] Table 2

[0442]

[0443]

[0444] The content block clustering system corresponds to the initial task state diagram and the digital work to be delivered in this task, "Weight Loss Health Management Plan for Hypoglycemic Patients". The content block clustering system included in the collaboration template α (16598) is as follows.

[0445] The overall content block clustering composition method is based on the requirement of assembling the creative content of each subtask into a digital work according to the collaborative creation task. The overall content block clustering composition method formulated by template developer L for the "Weight Loss Health Management Program for Hypoglycemic Patients" is shown in Table 3 below:

[0446] Table 3

[0447]

[0448]

[0449] The initial composition of the “scheme header” of the first-level content block cluster BC(1) is BC(1,L). The initial composition of the “scheme header” of the classic content block cluster BlockCluster(1) is BlockCluster(1,L) as shown in Table 4:

[0450] Table 4

[0451]

[0452] The initial composition of the first-level content block cluster BC(T1) "Basic Health Assessment" is BC(T1,L). The initial composition of the direct fixed-length frame-type content block cluster BC(T1) "Basic Health Assessment" is shown in Table 5:

[0453] Table 5

[0454]

[0455]

[0456] The initial composition of the first-level content block cluster BC(T2) "dynamic data monitoring" is BC(T2,L). The initial composition of the classic content block cluster BC(T2) "dynamic data monitoring" is shown in Table 6:

[0457] Table 6

[0458]

[0459]

[0460] The initial composition of the first-level content block cluster BC(T3) "Emergency Card" is BC(T3,L), and the initial composition of the classic content block cluster BC(T3) "Emergency Card" is BC(T2,L) as shown in Table 7:

[0461] Table 7

[0462]

[0463] The initial composition of the first-level content block cluster BC(T4) "Educational Resources" is BC(T4,L), and the initial composition of the classic content block cluster BlockCluster (T3) "First Aid Cards" is BC(T3,L) as shown in Table 8:

[0464] Table 8

[0465]

[0466] The initial composition of the first-level content block cluster BC(T5) "Dietary Management" is BC(T5,L), and the initial composition of the indirect fixed-length frame-type content block cluster BC(T5) "Dietary Management" is BC(T5,L) as shown in Table 9:

[0467] Table 9

[0468]

[0469]

[0470] The initial composition method of the first-level content block clusters BC(T6) to BC(T9) is similar to the initial composition method BC(T5, L) of BC(T5), and will not be repeated here.

[0471] A label system is established, corresponding to the initial task state diagram in the collaboration template. The label system and its initial assignment included in the collaboration template α (16598) are as follows.

[0472] Task Reward Label: In the initial task status diagram, a task is attached with a Task Reward Label. The Task Reward Label includes the "Task Reward Currency" and "Task Reward Amount" fields. The default value of the Task Reward Amount field is RMB 3,000.

[0473] Node Reward Label: In the initial task state diagram, each node is assigned a node reward label. The node reward label includes fields such as "node owner," "node reward distribution ratio," "node reward currency," and "node reward amount."

[0474] The initial assignment of node reward labels in this embodiment is shown in Table 10:

[0475] Table 10

[0476]

[0477]

[0478] Task process interaction label. In the initial task state diagram, the task setting object node is attached with the task process interaction label. The label is initially assigned the value of "release and forget".

[0479] Subtask node process interaction label, in the initial task state diagram, each subtask has a subtask process interaction label. The initial assignment of the subtask node process interaction label of this embodiment is as follows in Table 11:

[0480] Table 11

[0481]

[0482] Task community scope label, in the initial task state diagram, the task and each subtask have a community scope label. The initial assignment of the task community label in this embodiment is shown in Table 12 below:

[0483] Table 12

[0484]

[0485]

[0486] Task service quality label, in the initial task state diagram, the task and each subtask have a service quality label. The initial assignment of the task service quality label of this embodiment is as shown in Table 13:

[0487] Table 13

[0488]

[0489] Subtask power attribute tag, in the initial task state diagram, each subtask has a power attribute tag. The initial assignment of the subtask power attribute tag in this embodiment is as shown in Table 14:

[0490] Table 14

[0491]

[0492]

[0493] Subtask professional attribute label, in the initial task state diagram, each subtask has a professional attribute label. The initial assignment of the subtask professional attribute label of this embodiment is as follows in Table 15:

[0494] Table 15

[0495]

[0496] Subtask geographic location tag: In the initial task state diagram, each subtask has a geographic location tag. In this embodiment, the collaboration template assigns an initial value of "no requirement" to the subtask geographic location tag.

[0497] Subtask creator qualification tag, in the initial task state diagram, each subtask has a creator qualification tag. The initial assignment of the subtask creator qualification tag in this embodiment is shown in Table 16:

[0498] Table 16

[0499]

[0500]

[0501] The node creation state corresponds to the task node and each subtask node in the initial task state diagram in the collaboration template. The node creation state and its initial assignment included in the collaboration template α (16598) are shown in Table 17 below.

[0502] Table 17

[0503]

[0504] The initial user locations correspond to the nodes in the initial task state diagram in the collaboration template. The user locations and their initial values included in the collaboration template α (16598) are shown in Table 18:

[0505] Table 18

[0506]

[0507]

[0508] The task setting object, the task setting object TaskSet in the collaboration template, is used to provide task setting information to the task publisher.

[0509] An example of the task setting object TaskSet of the collaboration template α (16598) is as follows:

[0510] TaskSet object information object 1: Health management app. This includes the health management app's connection status to the collaborative community described in this solution. Subsequent operations on the task set object are performed through the health management app.

[0511] Information object 2 of the task setting object TaskSet: Personal information, including name, mobile phone number, gender, date of birth, blood type, emergency contact name and mobile phone number.

[0512] Information object 3 of the TaskSet object: Physical examination report. This includes basic physical indicators, metabolic indicators, complication screening results, and pancreatic function assessment.

[0513] Information object 4 of the task setting object TaskSet: Continuous blood glucose meter. This includes the connection status of the continuous blood glucose meter to the health management app.

[0514] Information object 5 of the task setting object TaskSet: smart health bracelet. This includes the connection status of the health bracelet to the health management app.

[0515] Determine a collaboration template, and determine a collaboration template for a weight loss health management program for hypoglycemic patients. The collaboration template processing module of the task setting subsystem determines the collaboration template corresponding to the task intention.

[0516] The task setting information processing module of the task setting subsystem performs analysis based on the task setting object obtained from the collaboration template and the user input information obtained from the user, and determines that the task setting information required for the current task is incomplete.

[0517] The system outputs interactive information, and the task setting information processing module of the task setting subsystem calls the interactive module to output information based on the analysis results.

[0518] For example:

[0519] System output: Hello, User E! We have generated the required collaboration template for the "Low-Weight Health Management Plan for Hypoglycemic Patients" task you requested. Next, please provide the task setup information. The content of this task setup information is determined by the task setup object, including the aforementioned information objects within the task setup object TaskSet.

[0520] The user enters new task requirement information. User E submits the task setting information based on the requirements of the task setting object, with the assistance and guidance of the task setting subsystem, including:

[0521] Information Object 1: Connecting the Health Management App to the Collaborative Community. This includes: Following the prompts in the Task Setting Object, the user downloads, installs, registers, and logs in to the Health Management App, connecting to the Collaborative Community described in this solution. If the user has already installed the Health Management App and is already connected to the Collaborative Community, no additional downloads are required. The Task Setting Object in the Collaborative Community App prompts the user, and subsequent operations after entering task setting information will be executed through the Health Management App.

[0522] Information Object 2: Through the health management app, the user fills in personal information according to the prompts of the task setting object, including: name E, mobile phone number 1XXXXXXXXXX, gender F, birth date May 1950, blood type O, permanent address Haidian District, Beijing, emergency contact H and mobile phone number 1YYYYYYYYYY.

[0523] Information Object 3: Through the health management app, user E goes to the corresponding medical institution for a physical examination according to the prompts of the task setting object. After the physical examination is completed, the electronic version of the physical examination report is input into the health management app for data archiving. This includes: basic physical indicators, metabolic-related indicators, complication screening, and pancreatic function assessment. The method for inputting the electronic version of the physical examination report into the health management app can be to take a photo of the physical examination report and upload it to user E's health management app, or the health management app of user E can retrieve it from the physical examination report database of the corresponding medical institution through the network data interface. The specific input method used is not limited by the present invention.

[0524] Information Object 4: Dynamic Blood Glucose. User E, through the health management app, follows the instructions for the task setting object and places an order for the corresponding dynamic blood glucose meter. After the dynamic blood glucose meter arrives, the user wears it, turns it on, and logs online, connecting it to the health management app.

[0525] Information Object 5: Smart Health Bracelet. User E, through the health management app, follows the instructions for the task setting object and places an order for the corresponding smart health bracelet. After the smart health bracelet arrives, the user puts it on, turns it on, goes online, and connects it to User E's health management app.

[0526] To determine whether the task setting information is complete, the task setting information processing module of the task setting subsystem performs analysis based on the task setting object obtained from the "Weight Loss Health Management Program for Hypoglycemic Patients" and the task requirement information obtained from the user to determine whether the task setting information required for the current task is complete.

[0527] The analysis shows that the task requirement information entered by user E includes all the required items in the task setting object. The task setting information required for the current task is complete.

[0528] Generate task setting information. The task setting subsystem generates task setting information.

[0529] For example:

[0530] Community scope for task release: Alliance community "Health Management Expert Service".

[0531] Collaboration template: Collaboration template α (16598), collaboration template for weight loss health management program for hypoglycemic patients.

[0532] Task setting information: relevant content submitted by user E in the task setting object.

[0533] Generate a default version of the task planning information based on the above task setting information.

[0534] Compared with the collaboration template, the default version of mission planning information includes the following new content:

[0535] The default version of the task planning information includes the task number (such as 90068) pre-assigned by the task management subsystem to the currently initiated task, and the task is recorded as Task_ID (90068).

[0536] In the content clustering system included in the collaboration template, the setting objects of each setting content block have setting information. For example, the setting content block SCBlock (100) of the patient name has setting information "E". For details, please refer to: "Minimum Deficit and Health Management Program Collaboration Template Initial Work.doc" and "Minimum Deficit and Health Management Program Task Setting Work.doc".

[0537] The initial task status diagram in the collaboration template is updated to the set task status diagram.

[0538] In the Task Setting Status diagram, the authoring status of several task and subtask nodes has been updated. This includes: the Task Setting Object node has been changed to the Task Setting Information node, and its authoring status will change to "Unauthorizable" after the task plan information is confirmed. Subtasks that do not depend on other subtasks can now be in the "Authorizable" state.

[0539] In this example, T1 is a fixed-length framework-type subtask that already has a second-level subtask and does not require additional creation. Therefore, T1 is not authorable. However, nodes T2, T3, T4, and T1.1 through T1.4 are authorable.

[0540] According to the present invention, the label system in the task status diagram can be changed according to the task setting information.

[0541] In this embodiment, according to the task setting information input by user E, user E was born in May 1950 and is 75 years old.

[0542] According to the rules set in the collaboration template, for users aged 75 and over, the creators of subtasks T5 to T9 must be in the same city as the patient. To this end, the task planning subsystem needs to adjust the initial assignment of the subtask geolocation tags for these subtasks from "No requirement" to "Beijing," the same city as user E's location. The adjusted subtask geolocation tag assignments are shown in Table 19.1:

[0543] Table 19.1

[0544]

[0545] Task community scope tags. In the initial task state diagram, the task and most subtasks have community scope tags that have not yet been assigned values. Based on the "Community scope of task release" in the task setting information, the alliance community "Health Management Expert Service" is determined. The task community scope tag settings and assignments in this embodiment are as shown in Table 19.2:

[0546] Table 19.2

[0547]

[0548]

[0549] In this example, assuming that the content of the tag system other than the subtask location tag and the subtask community scope tag remains unchanged, set the task state diagram and the initial task state Figure 1 To.

[0550] The user confirms the task planning information, and the generated default version of the task planning information is pushed to the user for confirmation.

[0551] The user adjusts the task planning information. After receiving the default version of the task planning information, the user directly confirms and submits it without making any adjustments.

[0552] Generate a confirmation version of the task planning information. Based on the task planning information submitted by the user, the task planning subsystem generates a confirmation version of the task planning information.

[0553] In this embodiment, after receiving the default version of the task planning information, the user does not make any adjustments and directly confirms the submission.

[0554] Generate a task number. The task planning information confirmation version includes the system-wide unique task number Task_ID (90068) generated by the task management subsystem for the current task.

[0555] Confirm the adopted collaboration template. The task planning information confirmation version includes the collaboration template α (16598) adopted by the current task.

[0556] Task setting information, which includes relevant content submitted by user E in the task setting object.

[0557] Setting the task state diagram: After user E enters the task setting information and before the task is released, the task state diagram at this time is called the setting task state diagram. Figure 12 .

[0558] Compared with the initial task state diagram in the collaboration template, in the set task state diagram in the task data package,

[0559] The subtask related information remains unchanged.

[0560] The overall content block clustering composition remains unchanged.

[0561] The "scheme header" of the first-level content block cluster BC(1) changes from the initial composition mode BC(1,L) to the set composition mode BC[(1,L),E), and the other first-level content block clusters remain unchanged.

[0562] According to the present invention, the tag system in the task state diagram can be changed according to the task setting information. However, this embodiment assumes that the tag system content other than the subtask geographic location tag remains unchanged. Figure 1 The present invention supports whether the tag system is changed according to the task setting information and does not limit this.

[0563] The node creation status corresponds to the task node and each subtask node in the task status diagram. The node creation status and setting assignment of task Task_ID (90068) are as shown in Table 20:

[0564] Table 20

[0565]

[0566] Set the user location, corresponding to each node in the task state diagram. The user location and its setting assignment of task Task_ID (90068) are shown in Table 21 below:

[0567] Table 21

[0568]

[0569] Release the task. After the task planning information confirmation version is generated, the user can release the task.

[0570] When a task is released, the system records the task release event on the chain, specifically including the following steps:

[0571] R1: The task release subsystem receives task requirement information (which may include the first task intention description and dialogue process), task setting information (including the task setting information confirmation version), and task planning information (including the task planning confirmation version), and generates a system-wide unique task number Task_ID (90068) for this task, and generates a task data block DB {Task_ID (90068)} corresponding to the task Task_ID (90068).

[0572] The content of the task data block DB{Task_ID(90068)} includes:

[0573] Task requirement information (optional), task setting information, task planning information (including the community scope of task release, collaboration template information, task setting information, task status diagram and the node description information it contains, content block clustering system, label information, user location information, node creation status, etc.).

[0574] Globally unique task identifier Task_ID (90068).

[0575] The identity information of the task issuer includes the user ID and / or public key of user E.

[0576] The data block identifier of this task is DB[Task_ID(90068)].

[0577] R2: User E uses the private key to digitally sign the task data block and generate a digital fingerprint of the task data block.

[0578] R3: User E stores the task data block and generates an access address for the task data block.

[0579] R4: User E generates a task data packet DP[Task_ID(90068)], which includes the following contents: task data block access address, task data block digital fingerprint, and task publisher user E's identity information (user E's public key).

[0580] R5: User E publishes the task data packet DP [Task_ID(90068)]. The specific method includes the following:

[0581] User E publishes the task data package to the consortium blockchain BSN for recording, and obtains the blockchain access address as the index of the task data package. Specifically, the following steps may be involved:

[0582] (1) The collaborative community selects the consortium chain BSN.

[0583] (2) The collaborative community develops a task data package on BSN and publishes a smart contract, which is deployed on the blockchain.

[0584] (3) User E calls the task data package to publish the smart contract.

[0585] DP[Task_ID(90068)] is published to BSN, and the corresponding BSN blockchain access address is obtained as the task data packet index.

[0586] Alternatively, user E uploads the task data packet DP[Task_ID(90068)] to the task library.

[0587] Alternatively, the system sends the task to appropriate collaborative community users through assignment or push. Specific steps may include:

[0588] The user device E submits the task data packet DP[Task_ID(90068)] to the task scheduling subsystem.

[0589] The task scheduling subsystem generates a task scheduling plan for the current collaborative task corresponding to the task data package DP[Task_ID(90068)], matches the subtask related information of each subtask in the authorable state with the user tag information of each user in the alliance community "Health Management Expert Service", and sets the corresponding user corresponding to the user position of the corresponding subtask according to the matching result.

[0590] According to the task scheduling plan, the task scheduling subsystem sends the task data packet DP[Task_ID(90068)] and the identifier of the corresponding subtask to the corresponding user in the alliance community "Health Management Expert Service" by dispatching or pushing it.

[0591] In this embodiment, for the current collaborative task [Task_ID(90068)] corresponding to the task data packet DP[Task_ID(90068)], the task scheduling work performed by the task scheduling subsystem corresponds to the work content of the above step "generating a task scheduling plan" and includes:

[0592] Relative to Figure 12 The setting task status diagram of the current task Task_ID (90068) is shown. Figure 13 Three new platform support nodes have been added: Arbitrator, Quality Manager, and Professional Committee Member. Each platform support node has a node description. For example, the description for the Arbitrator node reads: "The Arbitrator's responsibility is to arbitrate and mediate disputes arising during the collaboration process."

[0593] For the three platform support nodes above, the task setting information of Task_ID (90068) and the node description information of each platform support node are matched with the intelligent resource tag information of each support-type functional user within the "Health Management Expert Service" alliance community. Based on the information matching results, the support-type functional user with the highest matching degree is set as the user corresponding to the user position owned by the corresponding platform support node. The user corresponding to the user position of the arbitration committee node is Lao Wu. The user corresponding to the user position of the quality manager node is Lao Zhao. The user corresponding to the user position of the professional committee node is Lao Ren.

[0594] In the set task state diagram for the current task Task_ID (90068), the subtask nodes in the authorable state include T1.1 to T1.4, T2, T3, and T4. According to the subtask process interaction tags, T1.1 to T1.4, T2, and T3 are dispatched subtasks, and T4 is a push subtask.

[0595] For assigned subtasks, the task setting information, subtask description information, and subtask tag information of each subtask node are matched with the intelligent resource tag information of each creative functional user within the "Health Management Expert Service" alliance community. Based on the information matching results, the creative functional user with the highest matching degree is set as the user corresponding to the user site owned by the corresponding subtask node. The user sites corresponding to subtask nodes T1.1 to T1.4 and T2 are all machine intelligence call-type users within the "Health Management Expert Service" alliance community, "Health Management APP," referred to as "Jian A." The user site corresponding to subtask T3 is the offline operation user "Xiao Zhu" within the "Health Management Expert Service" alliance community. Xiao Zhu is a human expert user and serves as the interface for the Red Cross Society to connect with the "Health Management Expert Service" alliance community's first aid card production business.

[0596] For push-type subtasks, the task setting information, subtask description information, and subtask tag information of the subtask node are matched with the intelligent resource tag information of each creative functional user within the "Health Management Expert Service" alliance community. Based on the information matching results, the top three creative functional users with the highest matching degree are assigned to the user location of the corresponding subtask node. The user location corresponding to the T4 subtask node is the human expert users "Geng, Wei, and Jin" within the "Health Management Expert Service" alliance community.

[0597] Forming a first task state diagram, according to the above task scheduling scheme, the task scheduling subsystem generates a first task state diagram for the current collaborative task corresponding to the task data packet, such as Figure 13 shown.

[0598] Compared with the set task status diagram in the task data packet, in the first task status diagram generated by the task scheduling subsystem, the subtask related information remains unchanged, the overall content block clustering composition method remains unchanged, the content block clustering at all levels remains unchanged, the label system remains unchanged, and the node creation status remains unchanged.

[0599] Compared with the setting task state diagram, the first task state diagram has the following changes:

[0600] Add three platform support nodes: arbitration committee member, quality management staff member, and professional committee member. Each platform support node has node description information.

[0601] The user sites owned by the above three platform support nodes are set with corresponding users.

[0602] The user site of the subtask node in the authorable state has the corresponding user set.

[0603] The user position of the first task state diagram is referred to as the "first state user position". The corresponding user situation of the user position setting of each node in the first task state diagram of task Task_ID (90068) is as follows in Table 22:

[0604] Table 22

[0605]

[0606] In this embodiment, for the current collaborative task [Task_ID(90068)] corresponding to the task data packet DP[Task_ID(90068)], the task scheduling work performed by the task scheduling subsystem corresponds to the work content of the above step "sending subtasks according to the task scheduling plan" and includes:

[0607] Platform support node push: In the current collaborative task, there are three platform support nodes. The task scheduling subsystem pushes the current collaborative task and arbitration committee node to Mr. Wu, the current collaborative task and quality manager node to Mr. Zhao, and the current collaborative task and professional committee node to Mr. Ren. Pushing platform support nodes means pushing the task data packet DP[Task_ID(90068)] and the corresponding platform support node identifier.

[0608] Subtask assignment: For subtask nodes in the current collaborative task that are in the authorable state, T1.1 through T1.4, T2, and T3 are dispatchable subtasks based on the subtask process interaction tags. The task scheduling subsystem dispatches the current collaborative task and subtask nodes T1.1 through T1.4, and T2 to the machine intelligence caller user Jian A of the "Health Management Expert Service" alliance community, and dispatches the current collaborative task and subtask node T3 to the human expert user Xiao Zhu. For dispatchable subtasks, upon receiving the task information, the user corresponding to the user site will proceed with the creation of the subtask specified in the task information according to the agreed-upon procedure.

[0609] Subtask push: In the subtask node of the current collaborative task that is in a createable state, T4 is a push-type subtask, based on the subtask process interaction tag. The task scheduling subsystem pushes the current collaborative task and the T4 subtask node to three human expert users: Geng, Wei, and Jin. For push-type subtasks, the user corresponding to the user site receives the pushed subtask and can independently decide whether to participate in the creation of the pushed subtask. If the user does not want to participate, they can ignore the pushed task information. If the user does want to participate, they can independently grab the order and participate in the creation process of the pushed task.

[0610] In the above assigned or pushed subtask sending operation, sending the subtask means sending the task data packet DP[Task_ID(90068)] and the corresponding subtask identifier.

[0611] The task scheduling subsystem publishes the task data package to the alliance community "Health Management Expert Service" specified by the task community scope tag included in the current collaborative task, allowing creative functional users within the "Health Management Expert Service" alliance community to access the task data package. Furthermore, the task scheduling subsystem schedules the current collaborative task corresponding to the task data package according to the task scheduling plan, including pushing and assigning subtasks.

[0612] This example embodiment illustrates the situation where if there is no corresponding template for the question, it is necessary to fall back to the existing technology and publish it to the collaborative template creation collaborative community. The method of publishing tasks through the collaborative community of this patent can also give a satisfactory answer to the question.

[0613] According to some embodiments, a large model is trained specifically for finding, making, and generating templates. On the other hand, it should be noted that even without such a large model, it will not affect our current patent applications and product releases.

[0614] Carry out subtask creation. For assigned subtasks, after the user corresponding to the user site receives the task information, he / she will carry out the creation activity of the subtask specified in the task information according to the agreed procedure.

[0615] For push-type subtasks, the user whose user location receives the pushed subtask can decide whether to participate in the creation of the pushed subtask. If the user does not want to participate, they can ignore the pushed task information. If the user does want to participate, they can independently take the order and participate in the creation process of the pushed task.

[0616] Assignment-type subtasks, taking T1.1 "Basic Physical Indicators" as an example, T1.1 "Basic Physical Indicators" is an atomic subtask; content block clustering corresponding subtasks; belonging to T1, depending on task setting information, deriving T5 to T9.

[0617] The subtask label values for T1.1 "Basic Physical Indicators" are as follows:

[0618] Node reward label, 0 yuan.

[0619] Subtask node process interaction label, dispatch type.

[0620] The value of the subtask node process interaction label is dispatch type.

[0621] The steps for creating a distributed subtask are as follows:

[0622] Step U1: User "Jian A" receives task information and generates creation information for subtasks.

[0623] User "Jian A" receives task information, which includes subtasks assigned to the user.

[0624] User "Jian A" generates the creation information of the subtask.

[0625] Submit and confirm the creation information.

[0626] Step U2: The system receives the creative information submitted by the user "Jian A" and generates a creative information data block DB [T1.1, Jian A (1)] corresponding to the creative information, including:

[0627] 1) Creative content information, including the creative information submitted by the user.

[0628] 2) Task ID, Task_ID(n).

[0629] 3) Creator identity information, including the user's user ID and / or user public key.

[0630] 4) This creation information data block identifies DB[T1.1, key A(1)].

[0631] Step U3: The user uses the private key to digitally sign the finalized information snapshot data block to generate a digital fingerprint of the data block. (This step is optional for machine intelligence call users)

[0632] Step U4: The server stores the creation information data block and generates an access address for the creation information data block.

[0633] Step U5: User "Jian A" generates a creation information data packet DP[Task_ID(90068).T1.1, Jian A(1)], which includes the following contents: creation information data block access address, creation information data block digital fingerprint, and creation information publisher identity information (user "Jian A" public key).

[0634] Step U6: The user device or server publishes the creation information data package, making it accessible to relevant users in the collaborative community. If the execution content corresponding to the creation information data package is the first execution content of the task, the first task state diagram of the task evolves to the second task state diagram. Furthermore, the system can also push the data package to appropriate collaborative community users (referring to the community that published the task).

[0635] Figure 14 A block diagram of a computing device is shown according to an exemplary embodiment.

[0636] like Figure 14 As shown, computing device 30 includes processor 12 and memory 14. Computing device 30 may also include bus 22, network interface 16, and I / O interface 18. Processor 12, memory 14, network interface 16, and I / O interface 18 may communicate with each other via bus 22.

[0637] According to some embodiments, the processor 12 is responsible for receiving and processing input from the task publisher, obtaining the first task intent description, and can receive user input through the I / O interface 18, and then pass these inputs to the processor 12. The memory 14 is used to temporarily store the received first task intent description for subsequent processing. The processor 12 may include one or more general-purpose CPUs (Central Processing Units, processors), microprocessors, or application-specific integrated circuits, etc., for executing relevant program instructions. According to some embodiments, the computing device 30 may also include a high-performance display adapter (GPU) 20 for accelerating the processor 12.

[0638] The memory 14 stores a collaboration template library, which contains various predefined collaboration templates. The processor 12 automatically matches the collaboration template library in the memory 14 according to the first task intention description. The processor 12 executes the corresponding algorithm to find the most matching collaboration template and determines the first collaboration template according to the first task intention description.

[0639] Based on the first collaboration template, processor 12 further refines and determines task setting information. After determining the task setting information, processor 12 generates task planning information for the first task based on the task setting information. This involves breaking down the overall task into several subtasks and specifying the specific content, execution order, and interdependencies of each subtask. Memory 14 is used to store the task setting information and the generated task planning information for subsequent use.

[0640] To publish the first task, the network interface 16 publishes the task planning information to the collaborative community, and the processor 12 sends the task planning information to the collaborative community server or other related systems through the network interface 16. The task scheduling scheme for the first task is determined based on the task planning information and the user tag information, and the task scheduling scheme is used to set the user who performs the subtask; according to the task scheduling scheme, the corresponding subtask is sent to the corresponding user set by the task scheduling scheme by pushing and / or dispatching. If the I / O interface 18 needs to locally display or notify the user of the status of the task release, a display or other output device can be connected through the I / O interface 18. The computing device 30 can also communicate with one or more networks through the network interface 16. The network interface 16 can be a wireless network interface.

[0641] Bus 22 serves as a critical communication bridge throughout the entire process, ensuring efficient data and instruction exchange between processor 12, memory 14, network interface 16, and I / O interface 18, ensuring the smooth operation of the entire task issuance process. Bus 22 can include an address bus, a data bus, a control bus, and so on. Bus 22 provides a pathway for information exchange between various components.

[0642] It should be noted that, in the specific implementation process, the computing device 30 may also include other components necessary for normal operation. In addition, those skilled in the art will understand that the above-mentioned device may also only include components necessary to implement the embodiments of this specification, and does not necessarily include all components shown in the figure.

[0643] 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 method. The computer-readable storage medium may include, but is not limited to, any type of disk, including a floppy disk, an optical disk, a DVD, a CD-ROM, a microdrive and a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory device, a magnetic or optical card, a nanosystem (including a molecular memory IC), a network storage device, a cloud storage device, or any type of medium or device suitable for storing instructions and / or data.

[0644] An embodiment of the present invention further provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute part or all of the steps of any method described in the above method embodiments.

[0645] Those skilled in the art will readily appreciate that the technical solutions of the present invention can be implemented using software and / or hardware. "Unit" and "module" in this specification refer to software and / or hardware that can independently perform specific functions or work in conjunction with other components. Examples of hardware include field programmable gate arrays and integrated circuits.

[0646] It should be noted that for the aforementioned method embodiments, for simplicity of description, they are all expressed as a series of action combinations. However, those skilled in the art should be aware that the present invention is not limited by the order of the actions described, because according to the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0647] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0648] In the several embodiments provided herein, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is merely a logical functional division. In actual implementation, other division methods may be used. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. In addition, the coupling or direct coupling or communication connection shown or discussed may be through some service interface. The indirect coupling or communication connection of devices or units may be electrical or other forms.

[0649] Units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0650] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0651] 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 memory. Based on this understanding, the technical solution of the present invention, 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 a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the method of the present invention.

[0652] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0653] The exemplary embodiments of the present invention are specifically shown and described above. It should be understood that the present invention is not limited to the detailed structure, configuration or implementation described herein; on the contrary, the present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended clauses.

Claims

1. A method for publishing tasks in a collaborative community, characterized in that: The users of the collaborative community have user tag information, and the method includes: determining a first collaboration template for completing a first task; Determining task setting information according to the first collaboration template; generating task planning information for the first task according to the task setting information, wherein the first task corresponds to the first collaboration template and includes at least one subtask; Publishing the first task according to the task planning information includes: Determine a task scheduling scheme for the first task based on the task planning information and the user tag information, wherein the task scheduling scheme is used to set a user who executes a subtask; According to the task scheduling scheme, the corresponding subtask is sent to the corresponding user set by the task scheduling scheme through a push mode and / or a dispatch mode.

2. The method according to claim 1, characterized in that A first collaboration template for completing a first task is determined, including: Obtain the first task intention description from the task publisher; Automatically matching in a collaborative template library according to the first task intention description; If a collaboration template is matched from the collaboration template library, the collaboration template determined according to the matching result is used as the first collaboration template; If no collaboration template is matched from the collaboration template library, a collaboration template matching the first task intention description is asynchronously generated as the first collaboration template.

3. The method according to claim 2, characterized in that Automatically matching in the collaboration template library according to the first task intent description includes: The first task intention description is matched with the collaboration template description information in the collaboration template library, and the collaboration template that meets the matching requirements is provided to the task publisher.

4. The method according to claim 2, characterized in that The asynchronously generating a collaboration template that matches the first task intention description as the first collaboration template includes: A collaboration template generation requirement corresponding to the first task intention description is published in the collaboration community, thereby obtaining a collaboration template corresponding to the first task intention description as the first collaboration template.

5. The method according to claim 1, wherein The first collaboration template includes a task setting object; Determining task setting information according to the first collaboration template includes: Acquire task setting information corresponding to the task setting object included in the first collaboration template.

6. The method according to claim 5, characterized in that Generating task planning information for the first task based on the task setting information includes: Assigning a task number to the first task; The task planning information is generated according to the first collaboration template and the task setting information corresponding to the first collaboration template.

7. The method according to claim 1, characterized in that Publishing the first task according to the task planning information also includes: Generate a corresponding task data packet according to the task planning information.

8. The method according to claim 1, characterized in that Each of the at least one subtask is in a non-authorable state or an authorable state; The task planning information of the first task includes subtask related information of each subtask; Determining a task scheduling scheme for the first task according to the task planning information and the user tag information includes: The subtask related information of each subtask in the authorable state is matched with the user tag information, and the user who executes the corresponding subtask is set according to the matching result.

9. The method according to claim 8, characterized in that The subtask related information includes a subtask process interaction tag; The pushing method and / or the dispatching method is determined according to the subtask process interaction tag.

10. The method according to claim 8, characterized in that The collaborative community includes multiple communities; The subtask related information includes a subtask community range tag, and the user tag information includes a user community tag; Matching the subtask related information of each subtask in the authorable state with the user tag information, including: matching each subtask community range tag with the user community tag respectively.

11. The method according to claim 1, wherein In the assignment method, the user who is set to perform the corresponding subtask receives the assigned corresponding subtask and performs the corresponding subtask according to a predetermined rule; In the push mode, the user who is set to perform the corresponding subtask receives the pushed corresponding subtask and determines whether to perform the corresponding subtask.

12. The method according to claim 4, characterized in that Also includes: Add the first collaboration template to the collaboration template library.

13. A system for publishing tasks in a collaborative community, characterized in that: The system comprises: A template determining module, determining a first collaboration template for completing a first task; a setting module, determining task setting information according to the first collaboration template determined by the template determination module; a planning module, configured to generate task planning information for a first task based on the task setting information provided by the setting module; a publishing module, configured to publish the first task according to the task planning information generated by the planning module; Wherein, the publishing module includes: A scheduling submodule, combining the task planning information and the user tag information to determine a task scheduling solution for the first task; The sending submodule sends the subtasks to the corresponding users set in the task scheduling scheme through a push method and / or a dispatch method according to the task scheduling scheme.

14. The system according to claim 13, wherein: The template determination module includes: The acquisition submodule is used to obtain the first task intention description of the task publisher; a matching submodule, which automatically matches a first collaboration template in a collaboration template library according to the first task intention description obtained by the acquisition submodule; A generation submodule asynchronously generates a collaboration template that matches the first task intention description as the first collaboration template.

15. A computing device, characterized in that include: processor; as well as A memory storing a computer program, which, when executed by the processor, causes the processor to perform the method according to any one of claims 1 to 12.

Images