WO2013127195A1 - 链式沟通协作方法、装置及*** - Google Patents
链式沟通协作方法、装置及*** Download PDFInfo
- Publication number
- WO2013127195A1 WO2013127195A1 PCT/CN2012/084523 CN2012084523W WO2013127195A1 WO 2013127195 A1 WO2013127195 A1 WO 2013127195A1 CN 2012084523 W CN2012084523 W CN 2012084523W WO 2013127195 A1 WO2013127195 A1 WO 2013127195A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- task
- client
- subtask
- feedback data
- sub
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
Definitions
- the invention relates to the technical field of computers, in particular to a chain communication and cooperation method, device and system.
- the current task management system generally creates a task, and the task-related personnel share the task, and most of them only process the first-level task.
- the original task is often forwarded to the next-level client, so that the related information before the task is forwarded cannot be recorded.
- the task record is not saved in the original task client, so that the personnel related to the task cannot obtain the progress, status or result of the subsequent task, and the association between the original task and the distributed task is not clear enough, resulting in the task. Management is not efficient.
- the main object of the present invention is to provide a chain communication and collaboration method, which realizes sharing and forwarding of task information through a server, so as to achieve the purpose of improving communication efficiency.
- the invention provides a chain communication cooperation method, and the method specifically comprises the steps of:
- the feedback data returned by the second task client is a task creation instruction, create a second subtask, and establish an association identifier to save an association relationship between the first subtask and the second subtask, and send the second sub Task to third task client;
- the result data is backgraded to the first task client step by step according to the association identifier.
- the first subtask includes at least task initiation client information, task client information, and specific content of the task.
- the second subtask is similar to the first subtask.
- the method further includes:
- the general data is sent to the corresponding task client.
- the task number is added while the task is created, and the task number is used as the association identifier.
- the information element of the first subtask is independent of each other when the second subtask is created.
- the method further comprises:
- the present invention also provides a chain communication cooperation device, and the device specifically includes:
- a first task creation module configured to receive a task creation instruction issued by the first task client, create a first sub-task according to the task creation instruction, and send the second sub-task to the second task client;
- a first identification module configured to receive feedback data returned by the second task client, and identify a type of the feedback data
- a second task creation module configured to: if the feedback data returned by the second task client is a task creation instruction, create a second sub-task, and establish an association identifier to save the association between the first sub-task and the second sub-task Relationship, sending the second subtask to the third task client;
- a second identification module configured to receive feedback data returned by the third task client, and identify a type of the feedback data
- the first sending module is configured to: when the feedback data returned by the third task client is the result data, return the result data to the first task client step by step according to the association identifier.
- the first subtask includes at least task initiation client information, task client information, and specific content of the task.
- the second subtask is similar to the first subtask.
- the device further includes a second sending module, configured to send the general data to the corresponding task client if the feedback data is general data.
- a second sending module configured to send the general data to the corresponding task client if the feedback data is general data.
- the first task creation module and the second task creation module are further configured to add a task number to the task while creating the task, and use the task number as an association identifier.
- the information element of the first subtask is independent of each other when the second subtask is created.
- the device further includes a query module, configured to receive a task query instruction sent by any task client, obtain a corresponding task progress by using the association identifier, and send the task task to the task client.
- a query module configured to receive a task query instruction sent by any task client, obtain a corresponding task progress by using the association identifier, and send the task task to the task client.
- the invention also proposes a chain communication and cooperation system,
- the device includes at least three clients and a chain communication cooperation device, where the chain communication cooperation device specifically includes:
- a first task creation module configured to receive a task creation instruction issued by the first task client, create a first sub-task according to the task creation instruction, and send the second sub-task to the second task client;
- a first identification module configured to receive feedback data returned by the second task client, and identify a type of the feedback data
- a second task creation module configured to: if the feedback data returned by the second task client is a task creation instruction, create a second sub-task, and establish an association identifier to save the association between the first sub-task and the second sub-task Relationship, sending the second subtask to the third task client;
- a second identification module configured to receive feedback data returned by the third task client, and identify a type of the feedback data
- the first sending module is configured to: when the feedback data returned by the third task client is the result data, return the result data to the first task client step by step according to the association identifier.
- the first subtask includes at least task initiation client information, task client information, and specific content of the task.
- the second subtask is similar to the first subtask.
- the device further includes a second sending module, configured to send the general data to the corresponding task client if the feedback data is general data.
- a second sending module configured to send the general data to the corresponding task client if the feedback data is general data.
- the first task creation module and the second task creation module are further configured to add a task number to the task while creating the task, and use the task number as an association identifier.
- the information element of the first subtask is independent of each other when the second subtask is created.
- the device further includes a query module, configured to receive a task query instruction sent by any task client, obtain a corresponding task progress by using the association identifier, and send the task task to the task client.
- a query module configured to receive a task query instruction sent by any task client, obtain a corresponding task progress by using the association identifier, and send the task task to the task client.
- the method of chain communication and cooperation provided by the invention adopts a new independent sub-task unit to deliver tasks hierarchically, retains the original tasks and records the relationship between different task units, so that the task progress is clear and the management efficiency is improved. .
- FIG. 1 is a flowchart of an embodiment of a chain communication cooperation method provided by the present invention.
- FIG. 2 is a flowchart of another embodiment of a chain communication cooperation method provided by the present invention.
- FIG. 3 is a schematic diagram of a module in an embodiment of a chain communication cooperation device according to the present invention.
- FIG. 4 is a schematic diagram of a module in another embodiment of a chain communication cooperation device according to the present invention.
- FIG. 5 is a schematic diagram of a module in another embodiment of a chain communication cooperation apparatus according to the present invention.
- FIG. 1 is a flowchart of a chain communication and cooperation method according to an embodiment of the present invention.
- the chain communication and collaboration method of the present invention can be applied to a task management system server to manage and record the dynamics of tasks in the system.
- the method includes the following steps:
- Step S110 Receive a task creation instruction issued by the first task client, create a first sub-task according to the task creation instruction, and send the task to the second task client.
- the first subtask includes task initiation client information, execution task client information, and specific content of the task, and is used to provide task requirement information to the task related parties.
- the task client information is executed as the second task client, and the server sends the created first sub-task to the second task client.
- Step S120 Receive feedback data returned by the second task client, and identify the type of the feedback data
- the type of feedback data may include task creation instructions, result data, and the like.
- Step S130 If the feedback data returned by the second task client is a task creation instruction, create a second subtask, and establish an association identifier to save the association relationship between the first subtask and the second subtask, and send the second subtask To the third task client;
- the second subtask is similar to the first subtask, and includes task initiation client information, execution task client information, and specific content of the task.
- the specific content of the task in the second subtask may be consistent with the specific content of the task in the first subtask, or may be inconsistent.
- an information unit independent of the first subtask is used, and an association identifier is established to save the association relationship between the first subtask and the second subtask.
- the association identifier can make the association relationship between the subtasks more clearly recorded, and the association identifier can facilitate the collection of the progress of the task completion.
- the execution task client information in the second subtask is the third task client.
- Step S140 Receive feedback data returned by the third task client, and identify the type of the feedback data.
- Step S150 If the feedback data returned by the third task client is the result data, the result data is returned to the first task client step by step according to the association identifier.
- the result data is sent to the first task client according to the association relationship between the second subtask and the first subtask.
- the third subtask is created, and the association identifier is established to save the association relationship between the third subtask and the second subtask, and the third subtask is sent to the corresponding Execute a task client, such as a fourth task client.
- a task client such as a fourth task client.
- all the task clients form a chain structure, and the server performs the task delivery or the return of the result data according to the feedback data of the task client.
- the tasks between the two task clients are independent, and all task progress is saved in the database through the associated identifier.
- the method of chain communication and cooperation provided by the invention adopts a new independent sub-task unit to deliver tasks hierarchically, retains the original tasks and records the relationship between different task units, so that the task progress is clear and the management efficiency is improved. .
- the feedback data received by the server may further include general data. If the feedback data is general data, the general data is sent to the corresponding task client, so as to facilitate Communication between users.
- the above general data includes information and target task client information.
- the server After the server receives the general data, it sends the information to the target task client.
- the task client of the chain structure formed according to the foregoing method embodiment if the received feedback data returned by the second task client is general data, and the target task client information is the first task client, The general data is sent to the first task client; if the received feedback data of the second task client is general data, and the target task client information is the third task client, the general data is sent to the third Task client.
- the server adds a task number while creating a task, and uses the task number as an association identifier. For example, the server creates the first subtask while creating the task number 1, creates the second subtask while creating the task number 2, creates the third subtask and creates the task number 3, and the task number is created in the order in which the tasks are created.
- an association identifier attribute is added for each task: the association identifier of the second subtask is linked to the task number 1, and the association identifier of the third subtask is linked to the task number 2.
- the method further includes a step S160: receiving a task query instruction sent by any client, and obtaining a corresponding task progress by using an association identifier, and Send it to any of these clients.
- the server queries the second sub-task to the first sub-task through the association identifier task number 2 of the second sub-task, and also queries the third sub-task to connect to Task number 2.
- the upper task of the second subtask is the first subtask
- the next subtask is the third subtask
- the obtained task progress is sent to the second task client.
- the present invention further provides a chain communication cooperation device.
- the device specifically includes: a first task creation module 210, a second identification module 220, a second task creation module 230, and a first Sending module 240, wherein:
- the first task creation module 210 is configured to receive a task creation instruction issued by the first task client, create a first sub-task according to the task creation instruction, and send the task to the second task client.
- the first subtask includes task initiation client information, execution task client information, and specific content of the task, and is used to provide task requirement information to the task related parties.
- the task client information is executed as the second task client, and the first task creation module 210 sends the created first sub-task to the second task client.
- the first identification module 220 is configured to receive feedback data returned by the second task client, and identify the type of the feedback data; the type of the feedback data may include a task creation instruction, result data, and the like.
- the second task creation module 230 is configured to: if the feedback data returned by the second task client is a task creation instruction, create a second sub-task, and establish an association identifier to save the association relationship between the first sub-task and the second sub-task Sending the second subtask to the third task client;
- the second subtask is similar to the first subtask, and includes task initiation client information, execution task client information, and specific content of the task.
- the specific content of the task in the second subtask may be consistent with the specific content of the task in the first subtask, or may be inconsistent.
- an information unit independent of the first subtask is used, and an association identifier is established to save the association relationship between the first subtask and the second subtask.
- the association identifier can make the association relationship between the subtasks more clearly recorded, and the association identifier can facilitate the collection of the progress of the task completion.
- the execution task client information in the second subtask is the third task client.
- the second identification module 240 is configured to receive feedback data returned by the third task client, and identify the type of the feedback data
- the first sending module 250 is configured to: when the feedback data returned by the third task client is the result data, return the result data to the first task client step by step according to the association identifier.
- the first sending module 250 sends the result data to the first task client according to the association relationship between the second subtask and the first subtask.
- the third subtask is created, and the association identifier is established to save the association relationship between the third subtask and the second subtask, and the third subtask is sent to the corresponding Execute a task client, such as a fourth task client.
- a task client such as a fourth task client.
- all the task clients form a chain structure, and the server performs the task delivery or the return of the result data according to the feedback data of the task client.
- the tasks between the two task clients are independent, and all task progress is saved in the database through the associated identifier.
- the device for chain communication and cooperation provided by the invention uses a new independent sub-task unit to deliver tasks hierarchically, retains the original task and records the relationship between different task units, so that the task progress is clear and the management efficiency is improved. .
- the device further includes a second sending module 260, configured to send the general data to the corresponding task client if the feedback data is general data, so as to facilitate communication between the users.
- a second sending module 260 configured to send the general data to the corresponding task client if the feedback data is general data, so as to facilitate communication between the users.
- the above general data includes information and target task client information.
- the second sending module 260 sends the information to the target task client.
- the task client of the chain structure formed according to the foregoing apparatus embodiment is that the feedback data returned by the second task client received by the second sending module 260 is general data, and the target task client information is the first task.
- the client sends the general data to the first task client; if the received feedback data of the second task client is general data, and the target task client information is the third task client, then the general The data is sent to the third task client.
- the first task creation module 210 and the second task creation module 230 add a task number while creating a task, and use the task number as an association identifier.
- the device creates the first subtask while creating the task number 1, creates the second subtask while creating the task number 2, creates the third subtask and creates the task number 3, and the task number is created according to the order in which the tasks are created.
- the apparatus provided by the present invention further includes a query module 270, configured to receive a task query instruction sent by any task client, and obtain a corresponding task by using an association identifier. Progress and send it to any of the task clients.
- the query module 270 queries the second sub-task to the first sub-task through the association identification task number 2 of the second sub-task, and also queries the third sub-task. Connect to task number 2.
- the upper task of the second subtask is the first subtask
- the next level task is the third subtask
- the query module 270 sends the obtained task progress to the second task client.
- the embodiment of the invention further provides a chain communication cooperation system, which system comprises at least three clients and a chain communication cooperation device.
- a chain communication cooperation system which system comprises at least three clients and a chain communication cooperation device.
- the embodiment of the task management system of the present invention can better record the task delivery path and the progress by providing the above-mentioned chain communication cooperation device, thereby facilitating the user to obtain the task progress information, thereby improving the management efficiency.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
本发明涉及一种链式沟通协作方法,该方法具体包括步骤:接收第一任务客户端发出的任务创建指令并创建第一子任务后,发送至第二任务客户端;接收第二任务客户端返回的反馈数据,并识别反馈数据的类型;若该反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存子任务之间的关联关系,发送第二子任务至第三任务客户端;接收第三任务客户端返回的反馈数据,并识别反馈数据的类型;若该反馈数据为结果数据时,则将其根据关联标识逐级回传至第一任务客户端。本发明提供的链式沟通协作的方法,采用新建独立子任务单元的方式将任务逐级下发,保留原始任务的同时记录不同任务单元之间的关联关系,使得任务进度明晰,提高了管理效率。
Description
技术领域
本发明涉及计算机技术领域,具体是一种链式沟通协作方法、装置及***。
背景技术
目前的任务管理***一般是创建一个任务,任务相关人员共享该任务,大多只是处理一级任务。当需要进行任务分发时,往往只是将原任务转发至下一级客户,这样任务转发之前的相关信息无法被记录。在原任务转发后,任务记录并不保存在原任务客户端,使得与此任务相关的人员无法获得任务后续的进展、状态或者结果,而且原始任务与分发后的任务之间的关联不够清晰,导致任务管理的效率不高。
发明内容
本发明的主要目的是提供一种链式沟通协作方法,通过服务器实现任务信息的共享以及转发,以实现提高沟通效率的目的。
本发明提出一种链式沟通协作方法,所述方法具体包括步骤:
接收第一任务客户端发出的任务创建指令,根据所述任务创建指令创建第一子任务并发送至第二任务客户端;
接收所述第二任务客户端返回的反馈数据,并识别所述反馈数据的类型;
若所述第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送所述第二子任务至第三任务客户端;
接收所述第三任务客户端返回的反馈数据,并识别所述反馈数据的类型;
若所述第三任务客户端返回的反馈数据为结果数据时,则将所述结果数据根据所述关联标识逐级回传至第一任务客户端。
优选地,所述第一子任务至少包括任务发起客户端信息、执行任务客户端信息和任务的具体内容。所述第二子任务与所述第一子任务相似。
优选地,所述接收第二任务客户端返回的反馈数据,并判断所述反馈数据的类型的步骤之后还包括:
若所述反馈数据为一般数据时,则将所述一般数据发送至相应的任务客户端。
优选地,在创建任务的同时添加任务编号,并将所述任务编号作为关联标识。
优选地,创建第二子任务时与第一子任务的信息单元相互独立。
优选地,在前述所有步骤之后,还包括:
接收任一任务客户端发送的任务查询指令,通过关联标识获取到对应的任务进度,并将其发送至所述任一任务客户端。
本发明还提出一种链式沟通协作装置,所述装置具体包括:
第一任务创建模块,用于接收第一任务客户端发出的任务创建指令,根据所述任务创建指令创建第一子任务并发送至第二任务客户端;
第一识别模块,用于接收所述第二任务客户端返回的反馈数据,并识别所述反馈数据的类型;
第二任务创建模块,用于若所述第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送所述第二子任务至第三任务客户端;
第二识别模块,用于接收所述第三任务客户端返回的反馈数据,并识别所述反馈数据的类型;
第一发送模块,用于若所述第三任务客户端返回的反馈数据为结果数据时,则将所述结果数据根据所述关联标识逐级回传至第一任务客户端。
优选地,所述第一子任务至少包括任务发起客户端信息、执行任务客户端信息和任务的具体内容。所述第二子任务与所述第一子任务相似。
优选地,所述装置还包括第二发送模块,用于若所述反馈数据为一般数据时,则将所述一般数据发送至相应的任务客户端。
优选地,所述第一任务创建模块以及所述第二任务创建模块还用于在创建任务的同时为任务添加任务编号,并将所述任务编号作为关联标识。
优选地,创建第二子任务时与第一子任务的信息单元相互独立。
优选地,所述装置还包括查询模块,用于接收任一任务客户端发送的任务查询指令,通过关联标识获取到对应的任务进度,并将其发送至所述任一任务客户端。
本发明还提出一种链式沟通协作***,
包括至少三个客户端以及链式沟通协作装置,其中链式沟通协作装置具体包括:
第一任务创建模块,用于接收第一任务客户端发出的任务创建指令,根据所述任务创建指令创建第一子任务并发送至第二任务客户端;
第一识别模块,用于接收所述第二任务客户端返回的反馈数据,并识别所述反馈数据的类型;
第二任务创建模块,用于若所述第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送所述第二子任务至第三任务客户端;
第二识别模块,用于接收所述第三任务客户端返回的反馈数据,并识别所述反馈数据的类型;
第一发送模块,用于若所述第三任务客户端返回的反馈数据为结果数据时,则将所述结果数据根据所述关联标识逐级回传至第一任务客户端。
优选地,所述第一子任务至少包括任务发起客户端信息、执行任务客户端信息和任务的具体内容。所述第二子任务与所述第一子任务相似。
优选地,所述装置还包括第二发送模块,用于若所述反馈数据为一般数据时,则将所述一般数据发送至相应的任务客户端。
优选地,所述第一任务创建模块以及所述第二任务创建模块还用于在创建任务的同时为任务添加任务编号,并将所述任务编号作为关联标识。
优选地,创建第二子任务时与第一子任务的信息单元相互独立。
优选地,所述装置还包括查询模块,用于接收任一任务客户端发送的任务查询指令,通过关联标识获取到对应的任务进度,并将其发送至所述任一任务客户端。
本发明提供的链式沟通协作的方法,采用新建独立子任务单元的方式将任务逐级下发,保留原始任务的同时记录不同任务单元之间的关联关系,使得任务进度明晰,提高了管理效率。
附图说明
图1为本发明提供的链式沟通协作方法一实施例中的流程图;
图2为本发明提供的链式沟通协作方法另一实施例中的流程图;
图3为本发明提供的链式沟通协作装置一实施例中的模块示意图;
图4为本发明提供的链式沟通协作装置另一实施例中的模块示意图;
图5为本发明提供的链式沟通协作装置另一实施例中的模块示意图。
本发明目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
具体实施方式
为了使本发明的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本发明进行进一步详细说明。应当理解,此处所描述的具体实施例仅仅用以解释本发明,并不用于限定本发明。
请参看图1,图1为本发明实施例中链式沟通协作方法的流程图。本发明中链式沟通协作方法可应用于任务管理***服务器中管理并记录***中任务的动态。如图1所述,该方法包括以下步骤:
步骤S110:接收第一任务客户端发出的任务创建指令,根据该任务创建指令创建第一子任务并发送至第二任务客户端;
该第一子任务包括任务发起客户端信息、执行任务客户端信息以及任务的具体内容等,用于向任务相关方提供任务需求信息。在本实施例中,执行任务客户端信息为第二任务客户端,服务器则将创建的第一子任务发送至第二任务客户端。
步骤S120:接收第二任务客户端返回的反馈数据,并识别该反馈数据的类型;
该反馈数据的类型可以包括任务创建指令、结果数据等等。
步骤S130:若第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送第二子任务至第三任务客户端;
该第二子任务与第一子任务相似,包括任务发起客户端信息、执行任务客户端信息以及任务的具体内容等。该第二子任务中任务的具体内容与第一子任务中任务的具体内容可以一致,也可以不一致。而且,创建第二子任务时,采用了相对第一子任务独立的信息单元,同时建立了关联标识以保存第一子任务与第二子任务的关联关系。关联标识可以使各子任务之间的关联关系能够更加清晰地被记录下来,而且通过关联标识可以便于收集任务完成的进度。在本实施例中,第二子任务中的执行任务客户端信息为第三任务客户端。
步骤S140:接收第三任务客户端返回的反馈数据,并识别该反馈数据的类型;
步骤S150:若第三任务客户端返回的反馈数据为结果数据,则将该结果数据根据关联标识逐级回传至第一任务客户端。
若第三任务客户端返回的反馈数据为结果数据,则根据第二子任务与第一子任务之间的关联关系,将结果数据发送至第一任务客户端。
若第三任务客户端返回的反馈数据为任务创建指令,则创建第三子任务,并建立关联标识以保存第三子任务与第二子任务之间的关联关系,发送第三子任务至相应的执行任务客户端,例如第四任务客户端。依次类推,所有的任务客户端形成了链式结构,服务器根据任务客户端的反馈数据,进行任务的下发或者结果数据的回传。另外,两任务客户端之间的任务是独立的,而且所有的任务进度都通过关联标识保存在数据库中。
本发明提供的链式沟通协作的方法,采用新建独立子任务单元的方式将任务逐级下发,保留原始任务的同时记录不同任务单元之间的关联关系,使得任务进度明晰,提高了管理效率。
在前述实施例的基础上,在另一实施例中,服务器接收到的反馈数据还可以包括一般数据,若反馈数据为一般数据时,则将该一般数据发送至相应的任务客户端,以便于用户之间的沟通。
上述一般数据包括信息及目标任务客户端信息。服务器接收到该一般数据后,则将信息发送至目标任务客户端。具体地,根据上述方法实施例形成的链式结构的任务客户端,若接收到的第二任务客户端返回的反馈数据为一般数据、且目标任务客户端信息为第一任务客户端,则将该一般数据发送至第一任务客户端;若接收到的第二任务客户端返回的反馈数据为一般数据、且目标任务客户端信息为第三任务客户端,则将该一般数据发送至第三任务客户端。
在前述实施例的基础上,本另一实施例中,服务器在创建任务的同时添加任务编号,并将该任务编号作为关联标识。例如,服务器创建第一子任务的同时创建任务编号1,创建第二子任务的同时创建任务编号2,创建第三任子务的同时创建任务编号3,任务编号按照创建任务的先后顺序创建,并同时为各任务添加关联标识属性:将第二子任务的关联标识链接至任务编号1,将第三子任务的关联标识链接至任务编号2。通过关联标识记录以链式结构存在的各任务,能够更好地收集到任务的进度。
参照图2,在前述实施例的基础上,本实施例中,在所有步骤之后,还包括步骤S160:接收任一客户端发送的任务查询指令,通过关联标识查获取到对应的任务进度,并将其发送至该任一客户端。例如,服务器接收到第二任务客户端发送的任务查询指令后,通过第二子任务的关联标识任务编号2查询到第二子任务链接至第一子任务,还查询到第三子任务连接至任务编号2。根据查询信息,第二子任务的上一级任务为第一子任务,下一级任务为第三子任务,将获取到的任务进度发送至第二任务客户端。
请参照图3,本发明还提出一种链式沟通协作装置,如图3所示,该装置具体包括:第一任务创建模块210、第二识别模块220、第二任务创建模块230以及第一发送模块240,其中:
第一任务创建模块210,用于接收第一任务客户端发出的任务创建指令,根据该任务创建指令创建第一子任务并发送至第二任务客户端。该第一子任务包括任务发起客户端信息、执行任务客户端信息以及任务的具体内容等,用于向任务相关方提供任务需求信息。在本实施例中,执行任务客户端信息为第二任务客户端,则第一任务创建模块210将创建的第一子任务发送至第二任务客户端。
第一识别模块220,用于接收第二任务客户端返回的反馈数据,并识别该反馈数据的类型;该反馈数据的类型可以包括任务创建指令、结果数据等等。
第二任务创建模块230,用于若第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送该第二子任务至第三任务客户端;
该第二子任务与第一子任务相似,包括任务发起客户端信息、执行任务客户端信息以及任务的具体内容等。该第二子任务中任务的具体内容与第一子任务中任务的具体内容可以一致,也可以不一致。而且,创建第二子任务时,采用了相对第一子任务独立的信息单元,同时建立了关联标识以保存第一子任务与第二子任务的关联关系。关联标识可以使各子任务之间的关联关系能够更加清晰地被记录下来,而且通过关联标识可以便于收集任务完成的进度。在本实施例中,第二子任务中的执行任务客户端信息为第三任务客户端。
第二识别模块240,用于接收第三任务客户端返回的反馈数据,并识别该反馈数据的类型;
第一发送模块250,用于若第三任务客户端返回的反馈数据为结果数据时,则将该结果数据根据关联标识逐级回传至第一任务客户端。
若第三任务客户端返回的反馈数据为结果数据,则根据第二子任务与第一子任务之间的关联关系,第一发送模块250将结果数据发送至第一任务客户端。
若第三任务客户端返回的反馈数据为任务创建指令,则创建第三子任务,并建立关联标识以保存第三子任务与第二子任务之间的关联关系,发送第三子任务至相应的执行任务客户端,例如第四任务客户端。依次类推,所有的任务客户端形成了链式结构,服务器根据任务客户端的反馈数据,进行任务的下发或者结果数据的回传。另外,两任务客户端之间的任务是独立的,而且所有的任务进度都通过关联标识保存在数据库中。
本发明提供的链式沟通协作的装置,采用新建独立子任务单元的方式将任务逐级下发,保留原始任务的同时记录不同任务单元之间的关联关系,使得任务进度明晰,提高了管理效率。
参照图4,所述装置还包括第二发送模块260,用于若反馈数据为一般数据时,则将该一般数据发送至相应的任务客户端,以便于用户之间的沟通。
上述一般数据包括信息及目标任务客户端信息。第二发送模块260接收到该一般数据后,则将信息发送至目标任务客户端。具体地,根据上述装置实施例形成的链式结构的任务客户端,若第二发送模块260接收到的第二任务客户端返回的反馈数据为一般数据、且目标任务客户端信息为第一任务客户端,则将该一般数据发送至第一任务客户端;若接收到的第二任务客户端返回的反馈数据为一般数据、且目标任务客户端信息为第三任务客户端,则将该一般数据发送至第三任务客户端。
在前述实施例的基础上,本另一实施例中,第一任务创建模块210以及第二任务创建模块230在创建任务的同时添加任务编号,并将该任务编号作为关联标识。例如,本装置创建第一子任务的同时创建任务编号1,创建第二子任务的同时创建任务编号2,创建第三任子务的同时创建任务编号3,任务编号按照创建任务的先后顺序创建,并同时为各任务添加关联标识属性:将第二子任务的关联标识链接至任务编号1,将第三子任务的关联标识链接至任务编号2。通过关联标识记录以链式结构存在的各任务,能够更好地收集到任务的进度。
参照图5,在前述实施例的基础上,本实施例中,本发明提出的装置还包括查询模块270,用于接收任一任务客户端发送的任务查询指令,通过关联标识获取到对应的任务进度,并将其发送至该任一任务客户端。例如,查询模块270接收到第二任务客户端发送的任务查询指令后,通过第二子任务的关联标识任务编号2查询到第二子任务链接至第一子任务,还查询到第三子任务连接至任务编号2。根据查询信息,第二子任务的上一级任务为第一子任务,下一级任务为第三子任务,查询模块270将获取到的任务进度发送至第二任务客户端。
本发明实施例还提出一种链式沟通协作***,该***包括至少三个客户端以及链式沟通协作装置。该链式沟通协作装置的实施方案请参照前述图3至图5所示实施例,在此不作详述。本发明任务管理***实施例由于设置有上述链式沟通协作装置,能够更好地记录任务下发路径以及进度,方便用户获取到任务进度信息,从而提升了管理效率。
以上仅为本发明的较佳实施例而已,并不用以限制本发明,凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等,均应包含在本发明的保护范围之内。
Claims (18)
- 一种链式沟通协作方法,其特征在于,所述方法具体包括步骤:接收第一任务客户端发出的任务创建指令,根据所述任务创建指令创建第一子任务并发送至第二任务客户端;接收所述第二任务客户端返回的反馈数据,并识别所述反馈数据的类型;若所述第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送所述第二子任务至第三任务客户端;接收所述第三任务客户端返回的反馈数据,并识别所述反馈数据的类型;若所述第三任务客户端返回的反馈数据为结果数据时,则将所述结果数据根据所述关联标识逐级回传至第一任务客户端。
- 根据权利要求1所述的方法,其特征在于,所述第一子任务至少包括任务发起客户端信息、执行任务客户端信息和任务的具体内容。所述第二子任务与所述第一子任务相似。
- 根据权利要求2所述的方法,其特征在于,所述接收第二任务客户端返回的反馈数据,并判断所述反馈数据的类型的步骤之后还包括:若所述反馈数据为一般数据时,则将所述一般数据发送至相应的任务客户端。
- 根据权利要求3所述的方法,其特征在于,在创建任务的同时添加任务编号,并将所述任务编号作为关联标识。
- 根据权利要求4所述的方法,其特征在于,创建第二子任务时与第一子任务的信息单元相互独立。
- 根据权利要求5所述的方法,其特征在于,在前述所有步骤之后,还包括:接收任一任务客户端发送的任务查询指令,通过关联标识获取到对应的任务进度,并将其发送至所述任一任务客户端。
- 一种链式沟通协作装置,其特征在于,所述装置具体包括:第一任务创建模块,用于接收第一任务客户端发出的任务创建指令,根据所述任务创建指令创建第一子任务并发送至第二任务客户端;第一识别模块,用于接收所述第二任务客户端返回的反馈数据,并识别所述反馈数据的类型;第二任务创建模块,用于若所述第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送所述第二子任务至第三任务客户端;第二识别模块,用于接收所述第三任务客户端返回的反馈数据,并识别所述反馈数据的类型;第一发送模块,用于若所述第三任务客户端返回的反馈数据为结果数据时,则将所述结果数据根据所述关联标识逐级回传至第一任务客户端。
- 根据权利要求7所述的装置,其特征在于,所述第一子任务至少包括任务发起客户端信息、执行任务客户端信息和任务的具体内容。所述第二子任务与所述第一子任务内容相似。
- 根据权利要求8所述的装置,其特征在于,所述装置还包括第二发送模块,用于若所述反馈数据为一般数据时,则将所述一般数据发送至相应的任务客户端。
- 根据权利要求9所述的装置,其特征在于,所述第一任务创建模块以及所述第二任务创建模块还用于在创建任务的同时为任务添加任务编号,并将所述任务编号作为关联标识。
- 根据权利要求10所述的装置,其特征在于,创建第二子任务时与第一子任务的信息单元相互独立。
- 根据权利要求11所述的装置,其特征在于,所述装置还包括查询模块,用于接收任一任务客户端发送的任务查询指令,通过关联标识获取到对应的任务进度,并将其发送至所述任一任务客户端。
- 一种链式沟通协作***,其特征在于,包括至少三个客户端以及链式沟通协作装置,其中链式沟通协作装置具体包括:第一任务创建模块,用于接收第一任务客户端发出的任务创建指令,根据所述任务创建指令创建第一子任务并发送至第二任务客户端;第一识别模块,用于接收所述第二任务客户端返回的反馈数据,并识别所述反馈数据的类型;第二任务创建模块,用于若所述第二任务客户端返回的反馈数据为任务创建指令时,则创建第二子任务,并建立关联标识以保存第一子任务与第二子任务的关联关系,发送所述第二子任务至第三任务客户端;第二识别模块,用于接收所述第三任务客户端返回的反馈数据,并识别所述反馈数据的类型;第一发送模块,用于若所述第三任务客户端返回的反馈数据为结果数据时,则将所述结果数据根据所述关联标识逐级回传至第一任务客户端。
- 根据权利要求13所述的***,其特征在于,所述第一子任务至少包括任务发起客户端信息、执行任务客户端信息和任务的具体内容。所述第二子任务与所述第一子任务内容相似。
- 根据权利要求14所述的***,其特征在于,所述装置还包括第二发送模块,用于若所述反馈数据为一般数据时,则将所述一般数据发送至相应的任务客户端。
- 根据权利要求15所述的***,其特征在于,所述第一任务创建模块以及所述第二任务创建模块还用于在创建任务的同时为任务添加任务编号,并将所述任务编号作为关联标识。
- 根据权利要求16所述的***,其特征在于,创建第二子任务时与第一子任务的信息单元相互独立。
- 根据权利要求17所述的***,其特征在于,所述装置还包括查询模块,用于接收任一任务客户端发送的任务查询指令,通过关联标识获取到对应的任务进度,并将其发送至所述任一任务客户端。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210047816.0A CN102629345B (zh) | 2012-02-28 | 2012-02-28 | 链式沟通协作方法、装置及*** |
CN201210047816.0 | 2012-02-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013127195A1 true WO2013127195A1 (zh) | 2013-09-06 |
Family
ID=46587603
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/084523 WO2013127195A1 (zh) | 2012-02-28 | 2012-11-13 | 链式沟通协作方法、装置及*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102629345B (zh) |
WO (1) | WO2013127195A1 (zh) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102629345B (zh) * | 2012-02-28 | 2016-06-08 | 深圳市汉普电子技术开发有限公司 | 链式沟通协作方法、装置及*** |
CN104318354A (zh) * | 2014-10-11 | 2015-01-28 | 北京网秦天下科技有限公司 | 任务信息处理方法和*** |
CN106921684A (zh) * | 2015-12-24 | 2017-07-04 | 北京奇虎科技有限公司 | 一种请求信息的处理方法和服务器 |
CN106485461B (zh) * | 2016-09-08 | 2020-02-04 | 东软集团股份有限公司 | 记录流程日志的方法和装置 |
CN108717438B (zh) * | 2018-05-16 | 2020-10-23 | 北京奇艺世纪科技有限公司 | 一种链式数据状态采集***及方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101604421A (zh) * | 2009-03-19 | 2009-12-16 | 深圳市青铜器软件***有限公司 | 一种基于网络的项目计划管理***及方法 |
CN102169562A (zh) * | 2011-04-14 | 2011-08-31 | 泛太领时科技(北京)有限公司 | 一种项目计划处理方法及*** |
CN102629345A (zh) * | 2012-02-28 | 2012-08-08 | 深圳市汉普电子技术开发有限公司 | 链式沟通协作方法、装置及*** |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS62242244A (ja) * | 1986-04-14 | 1987-10-22 | Nec Corp | コンピユ−タシステムにおけるタスク制御方式 |
CN102254246B (zh) * | 2011-06-17 | 2014-09-17 | 中国建设银行股份有限公司 | 一种工作流管理方法及其*** |
-
2012
- 2012-02-28 CN CN201210047816.0A patent/CN102629345B/zh not_active Expired - Fee Related
- 2012-11-13 WO PCT/CN2012/084523 patent/WO2013127195A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101604421A (zh) * | 2009-03-19 | 2009-12-16 | 深圳市青铜器软件***有限公司 | 一种基于网络的项目计划管理***及方法 |
CN102169562A (zh) * | 2011-04-14 | 2011-08-31 | 泛太领时科技(北京)有限公司 | 一种项目计划处理方法及*** |
CN102629345A (zh) * | 2012-02-28 | 2012-08-08 | 深圳市汉普电子技术开发有限公司 | 链式沟通协作方法、装置及*** |
Also Published As
Publication number | Publication date |
---|---|
CN102629345B (zh) | 2016-06-08 |
CN102629345A (zh) | 2012-08-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2013127195A1 (zh) | 链式沟通协作方法、装置及*** | |
WO2018161478A1 (zh) | 多区块链的分片处理方法、装置、服务器和存储介质 | |
WO2018014582A1 (zh) | 保单数据处理方法、装置、服务器和存储介质 | |
WO2018161479A1 (zh) | 区块链集群处理***、方法、计算机设备和存储介质 | |
WO2016190476A1 (ko) | 클라우드 서비스를 위한 암호화 키 관리 방법 및 그 장치 | |
WO2013117104A1 (zh) | Bt离线数据下载***及方法、计算机存储介质 | |
WO2014005501A1 (zh) | 用户账户保持登录态的方法、***及存储介质 | |
WO2017045395A1 (zh) | 一种虚拟sim卡实现方法及*** | |
WO2016033929A1 (zh) | 一种云数据备份及恢复方法 | |
WO2018036168A1 (zh) | 数据处理任务执行方法、装置、执行服务器和存储介质 | |
WO2017054619A1 (zh) | 一种基于地理位置信息的社群互联方法和*** | |
WO2019109957A1 (zh) | 基于esb的服务提供方法、装置、设备及可读存储介质 | |
WO2014094300A1 (zh) | 远程控制通讯终端工作的服务器和方法及通讯终端 | |
WO2016011826A1 (zh) | 云端虚拟服务器的调度方法及装置 | |
WO2018149083A1 (zh) | 业务数据流转方法、装置、存储介质和终端 | |
WO2020186773A1 (zh) | 调用请求监控方法、装置、设备及存储介质 | |
WO2014029111A1 (zh) | 一种用户行为处理***及方法 | |
WO2012050293A1 (en) | Method and apparatus for sharing contents using information of group change in content oriented network environment | |
WO2018233372A1 (zh) | 支持哈希调度策略的lvs调度方法、设备、装置及存储介质 | |
WO2014029354A1 (zh) | 图片上传方法和***、客户端 | |
WO2018035929A1 (zh) | 一种验证码的处理方法及装置 | |
WO2017152650A1 (zh) | 一种摄像机资源共享的方法和装置 | |
WO2017054446A1 (zh) | 网络通信方法、设备及网络附属存储设备 | |
WO2017173838A1 (zh) | 基于验证的消息显示方法及通信终端 | |
WO2016123898A1 (zh) | 一种短信管理方法及其移动终端 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12869981 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05/02/2015) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12869981 Country of ref document: EP Kind code of ref document: A1 |