Method and apparatus for task processing, and device and storage medium

Abstract

On the basis of the embodiments of the present disclosure, provided are a method and apparatus for task processing, and a device and a storage medium. The method for task processing comprises: when a first task request or a first task processing result includes information of a first entity, a first processing unit storing attribute information of the first entity and a first entity identifier in an associating manner; the first processing unit replacing, with the first entity identifier, the information of the first entity that is included in the first task request or the first task processing result, such that the first task request or the first task processing result is transmitted to a second processing unit; the second processing unit acquiring at least part of the stored attribute information of the first entity on the basis of the first entity identifier in the first task request or the first task processing result; and the second processing unit executing, on the basis of the acquired at least part of the attribute information of the first entity, a task related to the first task request or the first task processing result.

Description

Method, apparatus, device and storage medium for task processing

[0001] This application claims priority to the Chinese invention patent application entitled “Method, apparatus, device and storage medium for task processing” and application number 202311111431.0, filed on August 30, 2023. The entire contents of that application are incorporated herein by reference. Technical Field

[0002] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for task processing. Background Art

[0003] In a task processing system, multiple distributed processing units collaborate to complete a specific task. Different processing units perform their respective functions at different nodes in the task. During task processing, different processing entities may need to operate and process the same entity. To help the processing units better understand the entity and successfully complete the task, they need to know certain attribute information about the entity.

[0004] Summary of the Invention

[0005] In a first aspect of the present disclosure, a method for task processing is provided, which is applied to a task processing system composed of multiple processing units. The method includes: when the first task request or the first task processing result contains information of the first entity, the first processing unit stores the attribute information of the first entity in association with the first entity identifier, and the first entity is mentioned for the first time within the scope of the first task subject of the task processing system; the first processing unit uses the first entity identifier to replace the information of the first entity contained in the first task request or the first task processing result, so that the first task request or the first task processing result is passed to the second processing unit; the second processing unit obtains at least a portion of the stored attribute information of the first entity based on the first entity identifier in the first task request or the first task processing result; and the second processing unit executes a task related to the first task request or the first task processing result based on at least a portion of the obtained attribute information of the first entity.

[0006] In a second aspect of the present disclosure, a task processing system is provided. The system includes: a first processing unit configured to: when a first task request or a first task processing result includes information about a first entity, store the attribute information of the first entity in association with a first entity identifier, and the first entity is mentioned for the first time within the scope of a first task subject of the task processing system; replace the information of the first entity included in the first task request or the first task processing result with the first entity identifier, so that the first task request or the first task processing result is passed to a second processing unit; a second processing unit configured to: based on the first entity identifier in the first task request or the first task processing result, obtain at least a portion of the stored attribute information of the first entity; and perform a task related to the first task request or the first task processing result according to at least a portion of the obtained attribute information of the first entity.

[0007] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.

[0008] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

[0009] It should be understood that the content described in this section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0011] FIG1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;

[0012] FIG2 is a schematic diagram showing a processing flow of a task processing system in processing tasks involving entities according to some embodiments of the present disclosure;

[0013] FIG3 shows a block diagram of an apparatus for task processing according to some embodiments of the present disclosure; and

[0014] FIG4 illustrates a block diagram of an electronic device in which one or more embodiments of the present disclosure can be implemented. DETAILED DESCRIPTION

[0015] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0016] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below.

[0017] Herein, unless explicitly stated otherwise, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.

[0018] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0019] It is understandable that before using the technical solutions disclosed in the various embodiments of the present disclosure, the type, scope of use, usage scenarios, etc. of the information involved in the present disclosure should be informed to relevant users and authorization should be obtained from relevant users in an appropriate manner in accordance with relevant laws and regulations. The relevant users may include any type of right holders, such as individuals, enterprises, and groups.

[0020] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly prompt the relevant user that the operation requested to be performed will require obtaining and using the information of the relevant user, so that the relevant user can independently choose whether to provide information to the software or hardware such as the electronic device, application, server or storage medium that executes the operation of the technical solution of the present disclosure based on the prompt message.

[0021] As an optional but non-limiting implementation, in response to receiving an active request from a relevant user, a prompt message may be sent to the relevant user in the form of a pop-up window, in which the prompt message may be presented in text form. Furthermore, the pop-up window may also include a selection control for the user to select "agree" or "disagree" to provide information to the electronic device.

[0022] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0023] As mentioned earlier, in order for processing units in a task processing system to better understand entities and thus better complete tasks, processing entities need to know certain attribute information about the entities. In a task processing system with distributed processing units, in order for the next processing unit to understand and operate on the entity, the entity's attribute information usually needs to be transferred between processing units, and different processing units may need to allocate their own storage space to cache attribute information.

[0024] This task processing process consumes a lot of communication and storage resources, which is not conducive to the effectiveness of task processing. Moreover, the previous processing unit may not fully understand whether the next processing unit needs to use entity attribute information in task execution and what specific entity attribute information is needed. Therefore, the previous processing unit often passes all the attribute information of the entity to the next processing unit. This will further cause greater resource consumption. On the other hand, if a processing unit needs to call an external processing unit, such as an external model, to assist in task processing, providing entity attribute information to the external processing unit will also involve information security issues.

[0025] In an embodiment of the present disclosure, an improved solution for task processing is provided. In this solution, in a task processing system comprising multiple processing units, if a task request or task processing result includes information about a first entity, and the first entity is mentioned for the first time within the scope of a first task in the task processing system, the processing unit stores the attribute information of the first entity in association with a first entity identifier, and replaces the first entity information contained in the task request or task processing result with the first entity identifier. When the task request or task processing result is passed to the next processing unit, the next processing unit retrieves at least a portion of the stored attribute information of the first entity based on the first entity identifier in the task request or task processing result, and executes the task associated with the task request or task processing result based on the at least a portion of the retrieved attribute information of the first entity. According to this solution, entity information is simplified to the form of an entity identifier between processing units, and the entity identifier is valid within the scope of a certain task. Thus, compared to directly transferring entity attribute information between processing units, identifying the entities involved in a task using entity identifiers can avoid excessive consumption of communication and storage resources during task processing, and different processing units can decide whether to read part or all of the attribute information of an entity based on their respective task processing requirements. In addition, when calling external processing units or models, the use of entity identifiers can also avoid information leakage and improve information security.

[0026] FIG1 shows a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. In the example environment 100, a task processing system 110 is configured to complete tasks in response to task requests. The task processing system 110 includes a plurality of processing units 112-1, 112-2, ... 112-N (collectively or individually referred to as processing units 112). Different processing units 112 can be configured with corresponding task processing functions. The task processing system 110 can execute corresponding tasks in response to user input from a user 120 or task requests from other sources.

[0027] In some embodiments, a processing unit 112 in the task processing system 110 may receive an initial task request. The processing unit 112 may execute the task associated with the task request and obtain the corresponding task processing result. The processing unit 112 may pass the task processing result to the next processing unit 112 for use in its own task processing, or may send a task request (which may be the original task request or a task request generated by the processing unit 112) to the next processing unit 112 to request the next processing unit 112 to process the corresponding task. In other words, each processing unit 112 may receive a task request from a user or other processing units, or a task processing result from another processing unit. Each processing unit 112 may pass the task request or task processing result to another processing unit. Multiple processing units 112 in the task processing system 110 work together to ultimately complete the task requested of the task processing system 110, such as a task request from a user 120.

[0028] In some application scenarios, the processing unit 112 in the task processing system 110 may include a digital assistant, which is configured to interact with the user 120 to receive user input and provide output feedback to the user. The digital assistant may support dialogue with the user 120 in natural language, determine the task processing requirements of the user 120 from the natural language input by the user, and call other processing units in the task processing system 110 to complete the task processing requirements of the user 120. In some embodiments, one or more other processing units 112 in the task processing system 110 may include plug-ins that can be called by the digital assistant, and each plug-in may be configured to perform a corresponding function. Examples of plug-ins may include, but are not limited to, search plug-ins, contact plug-ins, message plug-ins, document plug-ins, table plug-ins, mail plug-ins, calendar plug-ins, schedule plug-ins, task plug-ins, and the like. When completing a specific task requested by a user, one or more plug-ins may need to be called.

[0029] In some embodiments, each plug-in may correspond to one or more functional components in an application. A plug-in may be understood as a collection of functions, and a "tool" in a plug-in may be understood as a unit function or atomic function in the plug-in. With the help of multiple tools, a plug-in can ultimately be used to handle a class of tasks desired by the user. For example, a plug-in for processing documents may include: a document creation tool for creating new documents; a search tool for performing searches in documents; a formula generation tool for generating and inserting formulas in documents, and so on.

[0030] In some embodiments, the task processing system 110 is also connected to the target model 130 to complete the task with the help of the target model 130. In some embodiments, the task processing system 110 can use the target model 130 to understand user input to determine the user's task processing requirements, and to orchestrate and call processing units to complete the task processing requirements. In some embodiments, the target model 130 can be a model configured to perform other processing. The task processing system 110 (for example, one or more processing units 112 therein) can interact with the target model 130 to provide model input to the target model 130 and obtain corresponding model output from the target model 130. The target model 130 can run locally on the task processing system 110 or on a remote server. In some embodiments, the target model 130 can be a model with question-and-answer capabilities. Of course, the target model 130 can also be based on other appropriate models.

[0031] In some embodiments, the task processing system 110 can be partially or entirely deployed on a terminal device, and / or partially or entirely deployed on a service device. The terminal device can be, for example, any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. The service device can be, for example, any service device with computing capabilities, such as a mainframe, an edge computing node, a cloud service, etc.

[0032] In some embodiments, the modules included in the various processing units 112 in the task processing system 110 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more processing units 112 can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. For example, in some implementations, one or more processing units 112 can be implemented in the form of an application installed on a terminal device. In some implementations, in addition to or as an alternative to machine-executable instructions, the processing units 112 in the task processing system 110 can be at least partially implemented by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0033] It should be understood that the structure and function of each element in the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.

[0034] FIG2 illustrates a schematic diagram of a process flow 200 of task processing system 110 in processing tasks involving entities, according to some embodiments of the present disclosure. In the example of FIG2 , it is assumed that task processing system 110 triggers a task request based on user input 210 from user 120, and it is assumed that processing unit 112-1 of task processing system 110 receives user input 210. Based on user input 210, processing unit 112-1 may determine the user's task request.

[0035] When the task request or task processing result includes information about the first entity, the processing unit 112-1 stores the attribute information of the first entity in association with the first entity identifier. In some embodiments, the processing unit 112-1 may include a digital assistant that receives user input 210 and determines the task request from the user based on the user input 210.

[0036] In embodiments of the present disclosure, an entity refers to an operational object in the task processing system. In some embodiments, an entity may include at least one of the following: a document, audio, video, image, email, message, group, calendar, schedule, or task. The task processing system 110 can perform operations on these entities, such as processing documents, scheduling schedules, creating tasks, searching for content, and so on.

[0037] In an embodiment of the present disclosure, a simplified representation of entities is proposed, and entity identifiers are assigned to entities for use in task processing. For example, for a document entity, entity identifiers DOC_1, DOC_2, etc. may be assigned, and for a schedule entity, entity identifiers SCHEDULE_1, SCHEDULE_2, etc. may be assigned. In some embodiments, entity identifiers may also be assigned based on entity types. That is, for different entity types, the styles of entity identifiers may be different, for example, the entity identifier of a document entity includes "DOC", and the entity identifier of a schedule entity includes "SCHEDULE". In this way, at least the entity type can be identified from the entity identifier itself. Different entities under the same entity type can be further distinguished based on the entity identifier corresponding to the type, such as DOC_1, DOC_2, etc. as exemplified above.

[0038] Different entities often have different attribute information. For example, for a document entity, its attribute information may include the document title, document link (e.g., Uniform Resource Locator URL), document type, author information, document body, etc. For an email entity, its attribute information may include the email title, list of senders and receivers, receipt time, email link, email body, etc. For a message entity, its attribute information may include the message title, sending time, message body, etc. For a schedule entity, its attribute information may include the schedule time, participants, location, schedule content, etc. For each entity, the corresponding entity identifier and entity attribute may be stored in association. As shown in FIG2 , the entity identifier 222 of each entity is stored in the entity temporary storage 220 corresponding to its attribute information.

[0039] In some embodiments, attribute storage specifications corresponding to entity types can be configured. The attribute storage specifications define the attribute information types (also called attribute fields) that need to be stored under each entity type. Thus, when processing unit 112-1 wants to store attribute information of a first entity, it can obtain the attribute storage specifications corresponding to the entity type based on the entity type of the first entity, and store the attribute information of the first entity in association with the first entity identifier based on the attribute storage specifications. Table 1 below shows some entity types and their attribute storage specifications:

[0040] Table 1

[0041] In Table 1, "str" ​​indicates that the attribute information is a string type, "token" represents the unique identifier in the corresponding entity URL, "title" represents the corresponding entity title, "doc_type" represents the document type, "url" represents the corresponding entity URL, and "extra" represents additional information about the corresponding entity. It should be understood that Table 1 only provides some examples of entity types and attribute storage specifications. In specific implementations, different attribute storage specifications can be configured for more entity types or for different entity types as needed.

[0042] In some embodiments, the allocation of entity identifiers can be performed according to the task topic scope of the task processing system 110. In the task processing system 110, the task topic scope can be divided at any appropriate granularity. In some embodiments, a task topic scope can correspond to a task triggering of the task processing system 110 by the user 120. In some embodiments, if the user 120 interacts through the digital assistant in the task processing system 110, a task topic scope can correspond to a topic between the user 120 and the digital assistant. In the interaction with the digital assistant, a "topic" can be defined as corresponding to a specific context of the interaction between the user and the digital assistant. During the interaction process of each topic, the interaction information between the user and the digital assistant will be regarded as contextual information to assist the digital assistant in determining subsequent conversation messages. During the interaction process between the user and the digital assistant, the user can end the current topic and create a new topic as needed.

[0043] Upon receiving a task request or task processing result, each processing unit 112 in the task processing system 110 may determine the task subject scope corresponding to the task request or task processing result. For example, each task subject scope may be assigned a corresponding scope identifier, and the task request or task processing result within the task subject scope may include the scope identifier corresponding to the task subject scope. Thus, each processing unit 112 may determine the corresponding task subject scope using the scope identifier.

[0044] Specifically, if the processing unit 112-1 determines in the user input 210 that the first entity is mentioned for the first time within the task subject scope of the task processing system 110, then the processing unit 112-1 assigns a first entity identifier to the first entity and stores the attribute information of the first entity in association with the first entity identifier. In some embodiments, the processing unit 112 (e.g., the processing unit 112-1) may first load the entity identifiers stored within the task subject scope to determine whether the entity mentioned in the current task request or task processing result is mentioned for the first time within the task subject scope. The entity mentioned for the first time in the task request may be an existing entity that needs to be processed, and the entity mentioned for the first time in the task processing result may be an entity newly introduced or newly created after the task processing of the previous processing unit is completed.

[0045] In some embodiments, the first entity identifier of the first entity is stored within the corresponding task theme scope. In this way, the entity identifier of the same entity will not be reused between different task theme scopes. If the first entity is mentioned in another task theme scope, the entity identifier can be allocated again for use within the corresponding task theme scope.

[0046] In some embodiments, the processing unit 112-1 may store the attribute information of the first entity and the first entity identifier in association with each other in the entity temporary storage 220. In some embodiments, the entity temporary storage 220 may temporarily store the entity identifier and its attribute information required by the task processing system 110 at a certain granularity. The granularity may be the granularity of the task subject range, such as the topic granularity between the user and the digital assistant, or it may be a granularity smaller than the granularity of the task subject range, such as a round of conversation in the topic between the user and the digital assistant. In some embodiments, alternatively, the entity identifier 222 and its attribute information 224 stored in the entity temporary storage 220 may be stored in batches (e.g., at a specific granularity in the task subject range, such as the conversation granularity) in the entity persistent storage 230. It should be understood that the separate storage method of the entity temporary storage and entity persistent storage of the entity identifier and its attribute information shown in FIG2 is only an example. In actual applications, an appropriate storage system may be configured as needed, as long as it can achieve storage and reading according to the task subject range.

[0047] The above discussion is about the assignment of entity identifiers and the storage of entity attribute information for the entity mentioned for the first time within the task subject scope. The discussion is still based on the data flow sequence shown in Figure 2. For the first entity, after the first entity identifier is assigned, the processing unit 112-1 uses the first entity identifier to replace the information of the first entity contained in the task request or task processing result. The task request or task processing result here can be, for example, a task request or task processing result generated in response to user input 210. In Figure 2, it is assumed that the processing unit 112-1 passes the task request or task processing result replaced with the first entity identifier to the processing unit 112-2. The user inputs "Help me summarize this document {document title} {document link}". After the replacement of the entity identifier is performed, the user's actual input becomes "Help me summarize <<DOC_1> >".

[0048] Based on the first entity identifier in the task request or task processing result, processing unit 112-2 obtains at least a portion of the stored attribute information of the first entity. For example, processing unit 112-2 uses the first entity identifier to read at least a portion of the attribute information of the first entity from entity temporary storage 220. In other words, for a received task request or task processing result, the entity identifier contained therein can be simply used to obtain the attribute information corresponding to the entity. In this way, processing unit 112-2 can read the required attribute information from all stored entity information based on the needs of the task portion to be executed. Processing unit 112-2 executes the task related to the task request or task processing result based on at least a portion of the obtained attribute information of the first entity.

[0049] In some embodiments, if processing unit 112-2 modifies the first entity during the execution of a task, processing unit 112-2 may also update the attribute information of the first entity stored in entity temporary storage 220 and entity persistent storage 230. In this way, the first entity identifier of the first entity will be associated with the updated attribute information. Of course, if processing unit 112-2 modifies other existing entities besides the first entity during the execution of a task, the attribute information stored for the other existing entities may also be similarly updated.

[0050] In some embodiments, in addition to reading the attribute information of the entity, the processing unit 112 may also store the entities generated during the execution of the task (for example, the search plug-in searches for documents). In some embodiments, the processing unit 112-2 may determine that a new second entity is to be introduced during the execution of the task. The second entity may be an already created entity or an entity created by the processing unit 112-2 during the execution of the task, but the second entity is mentioned for the first time within the scope of the current task topic. Similar to the method described above for the first entity, a second entity identifier may also be assigned to the second entity, and the second entity identifier may be stored in the entity temporary storage 220 and the entity persistent storage 230 in association with the attribute information of the second entity.

[0051] In some embodiments, after executing a task related to a task request or task processing result from processing unit 112-1, processing unit 112-2 may continue to generate a new task request or task processing result to pass to the next processing unit, such as processing unit 112-3. If the task request or task processing result passed down also contains information about a first entity, processing unit 112-2 may also use the first entity identifier to replace the information about the first entity contained in the task request or task processing result. Similarly, if the task request or task processing result passed down also contains information about a second entity, processing unit 112-2 may also use the second entity identifier to replace the information about the second entity contained in the task request or task processing result, and so on.

[0052] At the processing unit 112-3, if the received task request or task processing result contains one or more entity identifiers, such as a first entity identifier and / or a second entity identifier, the processing unit 112-3 can use the entity identifiers to read at least a portion of the attribute information of the corresponding entity from the entity temporary storage 220 for executing the task related to the received task request or task processing result.

[0053] Similarly, if processing unit 112-3 modifies the attribute information of an existing entity, it may update the attribute information of the corresponding entity stored in entity temporary storage 220 and entity persistent storage 230. If a new entity, such as a third entity, is introduced at processing unit 112-3, processing unit 112-3 may also add the third entity identifier and attribute information of the third entity to entity temporary storage 220.

[0054] In some embodiments, the task processing system 110 is also connected to the target model 130. During task processing, the task processing system 110 requires the assistance of the target model 130, for example, by requesting the target model 130 to determine the user's task processing requirements from the user input 210 and orchestrate one or more processing units 112 to complete the task processing requirements (e.g., which processing units 112 should be called to perform a specific task processing). During interaction with the target model 130, one or more processing units 112 of the task processing system 110 also need to send task requests to the target model 130. In some embodiments, if the task request sent to the target model 130 contains information about a certain entity, the processing unit sending the task request also replaces the information about the first entity contained in the task request with the entity identifier of the entity. For example, if processing unit 112-1 calls the target model 130 to identify the task processing requirements of the user input 210 and to specifically execute the task processing requirements, processing unit 112-1 may replace the information about the first entity in the task request sent to the target model 130 with the first entity identifier. For other processing units 112 , in the interaction with the target model 130 , the entity identifier of the corresponding entity is similarly used to replace the entity information in the task request.

[0055] In some embodiments, unlike processing unit 112 in task processing system 110, target model 130 does not access stored entity attribute information when processing task requests. Thus, when processing a task, target model 130 only needs to focus on the specific entity it is operating on, without having to consider the specific entity attributes. For example, if a task request sent by task processing system 110 (e.g., processing unit 112-1) to target model 130 requests that target model 130 determine, from user input 210, the user's task processing requirements for a document, target model 130 may only need to focus on how to operate on the document to meet the user's task processing requirements, such as searching the document for passages containing a certain keyword. The model output returned by target model 130 may instruct processing unit 112-1 to call another processing unit (e.g., a document search plug-in) to search the document and inform processing unit 112-2 of the specific search keywords. During this process, target model 130 does not need to consider the specific attribute information of the document. Based on such model output, the processing unit 112 - 1 may request another processing unit (eg, a document search plug-in) in the task processing system 110 to perform a specific search task.

[0056] The above discussion discusses the task processing process for entities in task processing system 110. Although FIG2 illustrates the processing of processing units 112-1 through 112-3, depending on the specific task processing requirements, more or fewer processing units may be required to complete the entire task processing process. In the example of FIG2 , for a task processing process triggered by user input 210, task processing system 110 may provide output 212 to the user after completing the task processing. For example, output 212 may be presented to the user by a digital assistant in task processing system 110.

[0057] 3 shows a flow chart of a process 300 for task processing according to some embodiments of the present disclosure. The process 300 may be implemented at the task processing system 110. For ease of discussion, the process 300 will be described with reference to the environment 100 of FIG.

[0058] In box 310, when the first task request or the first task processing result includes information of the first entity, the first processing unit of the task processing system 110 stores the attribute information of the first entity in association with the first entity identifier, and the first entity is mentioned for the first time within the scope of the first task topic of the task processing system.

[0059] In block 320 , the first processing unit of the task processing system 110 replaces the first entity information contained in the first task request or the first task processing result with the first entity identifier, so that the first task request or the first task processing result is transferred to the second processing unit.

[0060] In block 330 , the second processing unit of the task processing system 110 obtains at least a portion of the stored attribute information of the first entity based on the first entity identifier in the first task request or the first task processing result.

[0061] In block 340 , the second processing unit of the task processing system 110 executes a task related to the first task request or the first task processing result according to at least a portion of the acquired attribute information of the first entity.

[0062] In some embodiments, when the first entity is modified during the execution of the task, the second processing unit of the task processing system 110 updates the attribute information of the first entity.

[0063] In some embodiments, the task processing system 110 is further connected to the target model. When the second task request sent by the task processing system 110 to the target model includes information about the first entity, the first entity identifier is used to replace the information about the first entity included in the second task request.

[0064] In some embodiments, the target model does not read the stored attribute information of the first entity when processing the second task request.

[0065] In some embodiments, storing the attribute information of the first entity and the first entity identifier in association with each other includes: obtaining the attribute storage specification corresponding to the entity type based on the entity type of the first entity; and storing the attribute information of the first entity and the first entity identifier in association with each other based on the attribute storage specification.

[0066] In some embodiments, the first entity identification of the first entity is stored within the scope of the first task subject matter.

[0067] In some embodiments, the first entity includes at least one of the following: a document, an audio, a video, an image, an email, a message, a calendar, a schedule, or a task.

[0068] FIG4 shows a block diagram of an electronic device 400 suitable for implementing embodiments of the present disclosure. It should be understood that the electronic device 400 shown in FIG4 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 400 shown in FIG4 can be used to implement part or all of the task processing system 110 of FIG1 .

[0069] As shown in FIG4 , electronic device 400 is in the form of a general-purpose computing device. Components of electronic device 400 may include, but are not limited to, one or more processors or processing units 410, memory 420, storage device 430, one or more communication units 440, one or more input devices 450, and one or more output devices 460. Processing unit 410 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 420. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to increase the parallel processing capabilities of electronic device 400.

[0070] The electronic device 400 typically includes a plurality of computer storage media. Such media can be any available media accessible to the electronic device 400, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 420 can be a volatile memory (e.g., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 430 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data and can be accessed within the electronic device 400.

[0071] The electronic device 400 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 4 , a disk drive for reading from or writing to a removable, non-volatile disk (e.g., a “floppy disk”) and an optical drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 420 may include a computer program product 425 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

[0072] The communication unit 440 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 400 can be implemented in a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device 400 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0073] Input device 450 may be one or more input devices, such as a mouse, keyboard, or trackball. Output device 460 may be one or more output devices, such as a display, a speaker, or a printer. Electronic device 400 may also communicate with one or more external devices (not shown) via communication unit 440 as needed, such as a storage device, a display device, or the like, with one or more devices that allow a user to interact with electronic device 400, or with any device that allows electronic device 400 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0074] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0075] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0076] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0077] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0078] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0079] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, not exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for task processing, applied to a task processing system composed of multiple processing units, the method comprising: When the first task request or the first task processing result includes information of the first entity, the first processing unit stores the attribute information of the first entity in association with the first entity identifier, and the first entity is mentioned for the first time within the scope of the first task subject of the task processing system; The first processing unit uses the first entity identifier to replace the information of the first entity contained in the first task request or the first task processing result, so that the first task request or the first task processing result is transmitted to the second processing unit; The second processing unit acquires at least a portion of the stored attribute information of the first entity based on the first entity identifier in the first task request or the first task processing result; as well as The second processing unit executes a task related to the first task request or the first task processing result according to at least a portion of the acquired attribute information of the first entity.

2. The method according to claim 1, further comprising: When the first entity is modified during the execution of the task, the second processing unit updates the attribute information of the first entity.

3. The method according to claim 1, wherein the task processing system is further connected to a target model, the method further comprising: When the second task request sent by the task processing system to the target model includes the information of the first entity, the information of the first entity included in the second task request is replaced by the first entity identifier. 4 . The method according to claim 3 , wherein the target model does not read the stored attribute information of the first entity in processing the second task request.

5. The method according to claim 1, wherein storing the attribute information of the first entity in association with the first entity identifier comprises: Based on the entity type of the first entity, obtaining a property storage specification corresponding to the entity type; as well as Based on the attribute storage specification, the attribute information of the first entity and the first entity identifier are stored in association with each other. The method of claim 1 , wherein the first entity identification of the first entity is stored within the scope of the first task subject matter.

7. The method according to claim 1, wherein the first entity comprises at least one of the following: a document, an audio, a video, an image, an email, a message, a calendar, a schedule, and a task.

8. A task processing system, comprising: The first processing unit is configured as follows: When the first task request or the first task processing result includes information of a first entity, storing the attribute information of the first entity in association with the first entity identifier, the first entity being mentioned for the first time within the scope of the first task subject of the task processing system; The first entity identifier is used to replace the first task request or the first task processing result. The information of the first entity contained in the processing unit enables the first task request or the first task processing result to be transmitted to the second processing unit; The second processing unit is configured as follows: Based on the first entity identifier in the first task request or the first task processing result, acquiring at least a portion of the stored attribute information of the first entity; as well as A task related to the first task request or the first task processing result is executed according to at least a portion of the acquired attribute information of the first entity. 9 . The system according to claim 8 , wherein the second processing unit is further configured to: update the attribute information of the first entity when the first entity is modified during the execution of the task.

10. The system according to claim 8, wherein the task processing system is also connected to a target model, wherein when the second task request sent by the task processing system to the target model contains information about the first entity, the first entity identifier is used to replace the information about the first entity contained in the second task request. 11 . The system according to claim 10 , wherein the target model does not use the first entity representation to read the stored attribute information of the first entity in processing the second task request.

12. The system according to claim 8, wherein the first processing unit is configured to: Based on the entity type of the first entity, obtaining a property storage specification corresponding to the entity type; and Based on the attribute storage specification, the attribute information of the first entity and the first entity identifier are stored in association with each other.

13. The system of claim 8, wherein the first entity identification of the first entity is stored within the scope of the first task subject matter.

14. The system according to claim 8, wherein the first entity comprises at least one of the following: a document, an audio, a video, an image, an email, a message, a calendar, a schedule, and a task.

15. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 7 when executed by the at least one processing unit.

16. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 7.

Images