A method, apparatus and storage medium for handling task requests and responses
By introducing preset task timing information into the diagnostic module of the CPAUTOSAR platform, the diagnostic tasks of the session layer, service scheduler, and service processing submodule are ensured to flow in sequence, which solves the problem of flow errors caused by unclear task allocation and realizes efficient management of task processing requests and effectiveness of diagnostic communication.
Patent Information
- Application Number
- CN202310222759.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-09
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-03-09
AI Technical Summary
In the existing technology, the task allocation of the session layer submodule, service scheduler submodule and service processing submodule in the diagnostic module of the CPAUTOSAR platform is unclear, which makes the task flow prone to errors and makes it impossible to effectively manage diagnostic communication.
A task processing request response method is provided, which executes multiple diagnostic tasks sequentially by pre-setting task timing information, including diagnostic tasks of the session layer submodule, service scheduler submodule and service processing submodule, to ensure that tasks flow in sequence, and realizes query and management of task processing requests by receiving, registering, executing and completing status flags.
This system enables multiple diagnostic tasks to flow sequentially, simplifies the communication process management of task processing requests, and improves the effectiveness and queryability of diagnostic communication.
Smart Images

Figure CN116360940B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle technology, and in particular to a task processing request and response method, apparatus and storage medium. Background Technology
[0002] The CPAUTOSAR platform's basic modules consist of fundamental functional modules such as System Services, Memory Services, and Communication Services. The diagnostic module is a crucial part of the System Services, and its two main functions are Diagnostic Event Manager (DEM) and Diagnostic Communication Manager (DCM). DCM is primarily responsible for diagnostic data flow control, diagnostic status control, data processing, and preparation.
[0003] The Diagnostic Communication Management (DCM) system primarily comprises three sub-modules: the Diagnostic Session layer (DSL), the Diagnostic Service Dispatcher (DSD), and the Diagnostic Service Processing (DSP). In existing technologies, the task allocation within and between these sub-modules is unclear, and task flow is prone to errors, hindering effective management of diagnostic communication. Summary of the Invention
[0004] This application provides a task processing request response method, apparatus, and storage medium, which not only enables multiple diagnostic tasks triggered in response to task processing requests to flow sequentially, but also facilitates the querying and management of the communication process of task processing requests.
[0005] On the one hand, this application provides a task processing request and response method, including:
[0006] Receive the task processing request for the target task sent by the requesting end;
[0007] Based on preset task timing information, multiple diagnostic tasks are executed sequentially in response to the task processing request to obtain processing response data; the preset task timing information indicates the flow sequence among the multiple diagnostic tasks triggered in response to the task processing request; the multiple diagnostic tasks include a first task set corresponding to the session layer submodule, a second task set corresponding to the service scheduler submodule, and a third task set corresponding to the service processing submodule, wherein the first task set, the second task set, and the third task set each include at least one of the diagnostic tasks;
[0008] The processing response data is sent to the requesting end.
[0009] Furthermore, the step of sequentially executing multiple diagnostic tasks in response to the task processing request based on preset task timing information includes:
[0010] In response to the completion of the previous diagnostic task corresponding to the target task, the current diagnostic task is triggered to register the task for the target task, so as to mark the current diagnostic task corresponding to the target task as registered.
[0011] In response to successful task registration, the task processing request is added to the task waiting queue of the current diagnostic task, and the current diagnostic task corresponding to the target task is marked as a task waiting state;
[0012] In response to the execution trigger of the task processing request, the task processing of the current diagnostic task corresponding to the target task is executed, and the current diagnostic task corresponding to the target task is marked as a task execution state;
[0013] In response to the completion of the processing of the current diagnostic task corresponding to the target task, the current diagnostic task corresponding to the target task is marked as having been completed.
[0014] Based on the preset task timing information, the next diagnostic task corresponding to the current diagnostic task is triggered to perform task registration processing for the target task.
[0015] Furthermore, the task processing request carries task request data;
[0016] Based on preset task timing information, multiple diagnostic tasks are executed sequentially in response to the task processing request to obtain processing response data, including:
[0017] In response to the task processing request, the session layer submodule obtains the resource status information corresponding to the diagnostic communication management module, performs attribute compliance detection based on the resource status information and the task request data, obtains the attribute compliance detection result, and sends it to the service scheduler submodule.
[0018] In response to the attribute compliance detection result, the service scheduler submodule obtains the operating environment data of the diagnostic communication management module, performs data compliance detection on the task request data based on the operating environment data, obtains the data compliance detection result, and sends it to the service processing submodule.
[0019] In response to the data compliance detection result, the service processing submodule performs task execution processing on the target task based on the task request data, obtains task response data, and sends it to the session layer submodule.
[0020] The session layer submodule encapsulates the task response data to obtain the processing response data.
[0021] Furthermore, the plurality of diagnostic tasks include cache diagnostic tasks, cache copying tasks, cache marking tasks, and attribute detection tasks;
[0022] The step of performing attribute compliance detection based on the resource status information and the task request data to obtain attribute compliance detection results includes:
[0023] The cache diagnostic task is executed based on the resource status information and the task request data to obtain the cache diagnostic results.
[0024] If the cache diagnostic result indicates that the resource status information meets the cache conditions corresponding to the task request data, the cache copying task is executed to store the task request data in the target cache area corresponding to the diagnostic communication management module;
[0025] The cache marking task is executed to mark the status of the target cache area corresponding to the task request data and generate a cache mark, which indicates the processing status of the target cache area.
[0026] The attribute detection task is executed on the task request data to obtain the attribute compliance detection result.
[0027] Furthermore, the multiple diagnostic tasks include initialization tasks and compliance testing tasks;
[0028] The data compliance check of the task request data based on the runtime environment data, to obtain the data compliance check result, includes:
[0029] Execute the initialization task to initialize the state of the task processing request for the service scheduler submodule;
[0030] The compliance detection task is executed based on the runtime environment data and the task request data to obtain the data compliance detection result.
[0031] Furthermore, the plurality of diagnostic tasks include target execution tasks and response suspension tasks;
[0032] The step of performing task execution processing on the target task based on the task request data to obtain task response data includes:
[0033] Based on the task request data, the target execution task is executed to process the target task and obtain the task response data;
[0034] During the processing of the target task, if the execution time of the target task exceeds the preset execution time, the response suspension task is executed to suspend the target task until the task response data is received.
[0035] Furthermore, the multiple diagnostic tasks include channel diagnostic tasks and data encapsulation tasks;
[0036] The session layer submodule encapsulates the task response data to obtain the processed response data, including:
[0037] Obtain the channel status information of the data transmission channel corresponding to the session layer submodule, perform the channel diagnostic task based on the channel status information, and obtain the channel diagnostic result;
[0038] If the channel diagnostic result indicates that the data transmission channel meets the data transmission conditions, the data encapsulation task is executed on the task response data to encapsulate the task response data and obtain the processed response data.
[0039] On the other hand, this application provides a task processing request and response apparatus, comprising:
[0040] Receiving module: Used to receive task processing requests for the target task sent by the requesting end;
[0041] Execution module: used to sequentially execute multiple diagnostic tasks in response to the task processing request based on preset task timing information, and obtain processing response data; the preset task timing information indicates the flow sequence among the multiple diagnostic tasks triggered in response to the task processing request; the multiple diagnostic tasks include a first task set corresponding to the session layer submodule, a second task set corresponding to the service scheduler submodule, and a third task set corresponding to the service processing submodule, wherein the first task set, the second task set, and the third task set each include at least one of the diagnostic tasks;
[0042] Sending module: Used to send the processing response data to the requesting end.
[0043] On the other hand, this application provides a computer-readable storage medium storing at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded by a processor and executed by the task processing request-response method described above.
[0044] On the other hand, this application provides an electronic device for implementing the above-described task processing request response method. The electronic device includes a processor and a memory. The memory stores at least one instruction or at least one program segment. The at least one instruction or the at least one program segment is loaded and executed by the processor to implement the task processing request response method as described above.
[0045] The task processing request and response method, apparatus, and storage medium provided in this application have the following beneficial effects:
[0046] The task processing request and response method of this application includes receiving a task processing request for a target task sent by a requesting end; executing multiple diagnostic tasks in response to the task processing request sequentially based on preset task timing information to obtain processing response data; the preset task timing information indicates the flow sequence between multiple diagnostic tasks triggered in response to the task processing request; the multiple diagnostic tasks include a first task set corresponding to the session layer submodule, a second task set corresponding to the service scheduler submodule, and a third task set corresponding to the service processing submodule, each of the first, second, and third task sets including at least one diagnostic task; and sending the processing response data to the requesting end; thus, not only can the multiple diagnostic tasks triggered in response to the task processing request flow sequentially, but it also facilitates the querying and management of the communication process of the task processing request. Attached Figure Description
[0047] To more clearly illustrate the technical solutions and advantages in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0048] Figure 1 This is a flowchart illustrating a task processing request and response method provided in an embodiment of this application;
[0049] Figure 2 This is a flowchart illustrating the sequential execution of multiple diagnostic tasks in response to a task processing request, as provided in an embodiment of this application.
[0050] Figure 3 A flowchart illustrating a method for obtaining processed response data, provided in an embodiment of this application;
[0051] Figure 4 This is a flowchart illustrating a process for obtaining attribute compliance detection results based on resource status information and task request data, as provided in an embodiment of this application.
[0052] Figure 5 This is a schematic diagram illustrating a process for obtaining data compliance detection results by performing task request data based on runtime environment data, as provided in an embodiment of this application.
[0053] Figure 6 This application provides a schematic diagram of a process for encapsulating task response data to obtain processed response data, as shown in the embodiments of this application.
[0054] Figure 7 A flowchart illustrating a task processing request and response method provided in an embodiment of this application;
[0055] Figure 8 This is a schematic diagram illustrating the diagnostic tasks corresponding to each submodule in a diagnostic communication management module provided in an embodiment of this application.
[0056] Figure 9 This application provides a schematic diagram of the flow timing between multiple diagnostic tasks in an embodiment.
[0057] Figure 10 This application provides a schematic diagram of the flow timing between multiple diagnostic tasks in an embodiment.
[0058] Figure 11 A schematic diagram of the structure of a task processing request and response device provided in an embodiment of this application;
[0059] Figure 12 This is a hardware structure block diagram of an electronic device for implementing a task processing request and response method, provided as an embodiment of this application. Detailed Implementation
[0060] To enable those skilled in the art to better understand the solutions of this application, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0061] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.
[0062] The task processing request and response method of this application can be applied to the automotive electronics CPAUTOSAR platform, enabling responses to diagnostic requests. Before introducing the method embodiments provided in this application, a brief introduction to relevant terms or nouns that may be involved in the method embodiments of this application will be given to facilitate understanding by those skilled in the art.
[0063] The CPAUTOSAR platform's basic modules consist of fundamental functional modules such as system services, storage management, and communication services. The diagnostic module is a crucial part of the system services, providing functions such as current system status, historical fault information from system self-tests, potential fault information, vehicle driving information, and Vehicle Identification Number (VIN) lookup. The diagnostic module plays an indispensable role in software and hardware development, manufacturing, and after-sales vehicle fault cause analysis.
[0064] The diagnostic module has two main functions: DEM (Diagnostic Equipment Model) and DCM (Diagnostic Management Model). DEM is primarily responsible for diagnostic services related to fault codes, such as fault identification, fault code storage, and fault code clearing. DCM is mainly responsible for diagnostic data flow control, diagnostic status control, data processing and preparation, including diagnostic sessions, secure access, and diagnostic service allocation.
[0065] The main functions of DCM (Diagnostic Compatibility) are integrated throughout the development, production, and after-sales processes of automobiles. For example, electromagnetic compatibility (EMC) and design verification (DV) during the development process can be achieved using diagnostic services. During the production process, functions such as software download and updates, end-of-line (EOL) testing of electronic control units (ECUs), automotive production line off-line testing, reading diagnostic trouble codes (DTCs) during the after-sales process, and control output debugging are also available.
[0066] DCM mainly consists of three sub-modules: the session layer sub-module, the service scheduler sub-module, and the service processing sub-module.
[0067] The session layer submodule ensures the data flow for diagnostic requests and responses, manages and ensures the timing of diagnostic protocols, and manages diagnostic states, especially diagnostic sessions and security. The session layer submodule primarily implements session processing, application-layer scheduled task processing, specific response behaviors, and authentication status handling for each diagnostic. Its main functions include processing diagnostic requests, processing diagnostic responses, managing security levels, handling session states, processing diagnostic protocols, handling communication modes, forwarding requests to the service scheduler submodule, maintaining online diagnostic functionality, and handling response requests from the service scheduler submodule.
[0068] The service scheduler submodule is used to process diagnostic data streams. Its main functions include receiving new diagnostic requests over the network and forwarding them to the data processor, as well as transmitting diagnostic responses over the network when triggered by the data processor (e.g., by the service processing submodule).
[0069] The specific processing content of the service scheduler submodule includes the following:
[0070] ① Check Diagnostic Service: Used to check the conditions for executing the diagnostic service, such as the current session mode, whether the diagnostic service is supported, and the security access level. If the conditions are not supported, it will reply with 0x7F and the specific NRC negative response code. If it passes, it will be processed by the upper-level service, which can also provide a negative response.
[0071] ② Summarize response data: Send the response data obtained from the judgment or the response data sent by the service processing submodule to the session layer submodule, which then sends the data outward.
[0072] The service processing submodule is used to process actual diagnostic requests. It is responsible for analyzing the received request messages, checking the message format and whether the subservice function is supported, obtaining data from the diagnostic event management, software components (SW-Cs) or other basic software (BSW) modules or executing the required function calls, and summarizing the response messages.
[0073] The service processing submodule can implement the Unified Diagnostic Services (UDS) functions specified in ISO 14229-1, such as restarting the Electronic Control Unit (ECU), clearing diagnostic information, reading and writing Data Identifiers (DIDs), secure access, communication control, and uploading and downloading data.
[0074] The following combination Figure 1 This application introduces a task processing request and response method provided in an embodiment of the present application. The task processing request and response method provided in this application is applied to the diagnostic communication management module of an in-vehicle terminal. The diagnostic communication management module includes a session layer submodule, a service scheduler submodule, and a service processing submodule.
[0075] Figure 1 This application provides a task processing request and response method, which includes:
[0076] S101. Receive the task processing request for the target task sent by the requesting end.
[0077] In this embodiment of the application, the requesting end can be a Protocol Data Unit Router (PduR) capable of sending a task processing request for a target task to the diagnostic communication management module, or it can be a vehicle diagnostic instrument.
[0078] In some embodiments, PduR responds to a task processing request for a target task sent by the vehicle diagnostic tool, and sends a task processing request for the target task to the diagnostic communication management module.
[0079] For example, the task processing request can be a diagnostic request; for example, the target task can be resetting the ECU, reading DTC information, reading memory by address, and secure access, etc.
[0080] S102. Based on preset task timing information, execute multiple diagnostic tasks in response to the task processing request in sequence to obtain processing response data; the preset task timing information indicates the flow sequence between multiple diagnostic tasks triggered in response to the task processing request; the multiple diagnostic tasks include a first task set corresponding to the session layer submodule, a second task set corresponding to the service scheduler submodule, and a third task set corresponding to the service processing submodule, and the first task set, the second task set, and the third task set each include at least one diagnostic task.
[0081] In some embodiments, the first task set, the second task set, and the third task set each include multiple diagnostic tasks; the multiple diagnostic tasks in the first task set are executed in the session layer submodule, the multiple diagnostic tasks in the second task set are executed in the service scheduler submodule, and the multiple diagnostic tasks in the third task set are executed in the service processing submodule. This achieves the itemization of diagnostic tasks in the session layer submodule, the service scheduler submodule, and the service processing submodule, respectively.
[0082] In some embodiments, preset task timing information can indicate the flow sequence between multiple diagnostic tasks, that is, the chronological order in which multiple diagnostic tasks are executed. These multiple diagnostic tasks are triggered in response to task processing requests, and include multiple diagnostic tasks corresponding to the session layer submodule, multiple diagnostic tasks corresponding to the service scheduler submodule, and multiple diagnostic tasks corresponding to the service processing submodule. This allows the multiple diagnostic tasks triggered in response to task processing requests to flow sequentially, facilitating the querying and management of the communication process for task processing requests.
[0083] In this embodiment of the application, please refer to Figure 2 S102 includes:
[0084] S201. In response to the completion of the previous diagnostic task corresponding to the target task, the task registration process for the current diagnostic task for the target task is triggered to mark the current diagnostic task corresponding to the target task as registered.
[0085] In some embodiments, based on preset task timing information, the previous diagnostic task corresponding to the current diagnostic task and the next diagnostic task corresponding to the current diagnostic task can be determined. If the previous diagnostic task is completed, the execution of the current diagnostic task is triggered; if the current diagnostic task is completed, the execution of the next diagnostic task is triggered. Thus, based on the preset task timing information, multiple diagnostic tasks corresponding to the task processing request are executed sequentially, thereby obtaining processing response data corresponding to the task processing request for the target task.
[0086] In some embodiments, after the previous diagnostic task is completed, a task registration process for the current diagnostic task targeting the target task is triggered based on preset task timing information to obtain the current diagnostic task; the correctness of the current diagnostic task registration is confirmed based on the preset task timing information; if the current diagnostic task is correctly registered, the current diagnostic task corresponding to the target task is marked as registered; if the current diagnostic task is incorrectly registered, the error is reported to the requesting end through DET (default error tracer).
[0087] Specifically, if the preset task timing information includes the current diagnostic task, the current diagnostic task is determined to be correctly registered; if the preset task timing information does not include the current diagnostic task, the current diagnostic task is determined to be incorrectly registered.
[0088] S202. In response to successful task registration, add the task processing request to the task waiting queue of the current diagnostic task, and mark the current diagnostic task corresponding to the target task as a task waiting state.
[0089] In some embodiments, when the same diagnostic task is registered for multiple task processing requests respectively, and the current diagnostic tasks corresponding to each of the multiple task processing requests are all marked as registered, the multiple task processing requests are added to the task waiting queue of the current diagnostic task respectively, and the current diagnostic tasks corresponding to each of the multiple task processing requests are all marked as task waiting.
[0090] For example, when a first task processing request for a first target task and a second task processing request for a second target task are concurrently issued on the same diagnostic instrument, task registration processing for the current diagnostic tasks for the first target task and the second target task is triggered respectively, resulting in the current diagnostic task corresponding to the first target task and the current diagnostic task corresponding to the second target task. When both the current diagnostic task corresponding to the first target task and the current diagnostic task corresponding to the second target task are marked as registered, the first task processing request and the second task processing request are added to the task waiting queue of the current diagnostic task, and both the current diagnostic task corresponding to the first target task and the current diagnostic task corresponding to the second target task are marked as task waiting.
[0091] Specifically, PduR can establish its own corresponding PduRID (Protocol Data Unit Routing Identifier) for each diagnostic instrument and each communication channel; based on PduRID, the diagnostic communication management module can distinguish and mark multiple task processing requests.
[0092] The task processing request and response method provided in this application embodiment is particularly suitable for situations where multiple task processing requests are concurrent, and enables the diagnostic communication management module to effectively manage diagnostic communication.
[0093] S203. In response to the execution trigger of the task processing request, execute the task processing of the current diagnostic task corresponding to the target task, and mark the current diagnostic task corresponding to the target task as a task execution status.
[0094] In some embodiments, the main function periodically scans the current diagnostic tasks corresponding to each target task. When the current diagnostic task corresponding to the target task is marked as a task waiting state, the function corresponding to the current diagnostic task is called to execute the current diagnostic task corresponding to the target task, and the current diagnostic task corresponding to the target task is marked as a task execution state.
[0095] Specifically, when the current diagnostic tasks corresponding to multiple target tasks are all marked as waiting, based on the timing information of task registration processing or the priority of task processing requests, the function corresponding to the current diagnostic task is called in sequence to execute the current diagnostic task corresponding to each target task.
[0096] S204. In response to the completion of the processing of the current diagnostic task corresponding to the target task, mark the current diagnostic task corresponding to the target task as the execution completion status.
[0097] In some embodiments, when the current diagnostic task corresponding to the target task is completed, the current diagnostic task corresponding to the target task is marked as completed.
[0098] S205. Based on the preset task timing information, trigger the task registration process of the next diagnostic task corresponding to the current diagnostic task for the target task.
[0099] In some embodiments, based on preset task timing information, the next diagnostic task corresponding to the current diagnostic task is triggered to register the target task, thereby marking the next diagnostic task corresponding to the target task as registered; in response to successful task registration, the task processing request is added to the task waiting queue of the next diagnostic task, and the next diagnostic task corresponding to the target task is marked as waiting; in response to the execution triggering of the task processing request, the task processing of the next diagnostic task corresponding to the target task is executed, and the next diagnostic task corresponding to the target task is marked as executing; in response to the completion of the processing of the next diagnostic task corresponding to the target task, the next diagnostic task corresponding to the target task is marked as completing; and based on preset task timing information, the next diagnostic task corresponding to the next diagnostic task is triggered to register the target task.
[0100] Understandably, based on preset task timing information, each diagnostic task is triggered sequentially, including task registration, registration status marking, task waiting status marking, task processing, task execution status marking, and execution completion status marking. This allows multiple diagnostic tasks triggered in response to task processing requests to flow sequentially, facilitating the querying and management of the communication process of task processing requests.
[0101] In this embodiment, the task processing request carries task request data; please refer to [link to relevant documentation]. Figure 3S102 includes:
[0102] S301. The session layer submodule responds to the task processing request, obtains the resource status information corresponding to the diagnostic communication management module, performs attribute compliance detection based on the resource status information and task request data, obtains the attribute compliance detection result, and sends it to the service scheduler submodule.
[0103] In this embodiment, multiple diagnostic tasks include a cache diagnostic task, a cache copying task, a cache marking task, and an attribute detection task. Please refer to [link to relevant documentation]. Figure 4 S301 includes:
[0104] S401. Execute a cache diagnostic task based on resource status information and task request data to obtain cache diagnostic results.
[0105] In some embodiments, the data length information of the task request data is determined based on the request packet header of the task request data; the current free cache space information corresponding to the diagnostic communication management module is determined based on the resource status information corresponding to the diagnostic communication management module; the data length information of the task request data is compared and processed with the current free cache space information corresponding to the diagnostic communication management module to obtain the cache diagnosis result.
[0106] S402. If the cache diagnostic result indicates that the resource status information meets the cache conditions corresponding to the task request data, execute the cache copy task to store the task request data in the target cache area corresponding to the diagnostic communication management module.
[0107] In some embodiments, when the cache diagnostic result indicates that the current free cache space corresponding to the diagnostic communication management module meets the cache conditions corresponding to the task request data, the request header of the task request data is stored in the target cache area corresponding to the diagnostic communication management module, and the data packet corresponding to the request header of the task request data is received. The received data packet and the request header of the task request data are then integrated to complete the copying of the task request data in the target cache area corresponding to the diagnostic communication management module.
[0108] Specifically, task request data can be obtained by receiving frames.
[0109] S403. Execute the cache marking task to mark the status of the target cache corresponding to the task request data and generate a cache mark. The cache mark indicates the processing status of the target cache.
[0110] In some embodiments, a cache marking task is performed to mark the status of the target cache corresponding to the task request data, generate a cache tag indicating the processing status of the target cache, and start timing the processing time of the task request. For example, the processing status of the target cache can be "processing".
[0111] S404. Perform an attribute detection task on the task request data to obtain the attribute compliance detection results.
[0112] In some embodiments, an attribute detection task is performed on the task request data to complete the attribute detection of the task request data. For example, the attribute detection includes request data type detection and request data source detection, thereby obtaining attribute compliance detection results.
[0113] For example, if the data type and source of the task request data meet the first preset condition, the attributes of the task request data are determined to be compliant; if the data type and / or source of the task request data do not meet the first preset condition, the attributes of the task request data are determined to be non-compliant.
[0114] In some embodiments, if the attribute compliance check result indicates that the attributes of the task request data are compliant, the attribute compliance check result is sent to the service scheduler submodule; if the attribute compliance check result indicates that the attributes of the task request data are non-compliant, an error is reported to the requesting end via DET.
[0115] S302. The service scheduler submodule responds to the attribute compliance detection result, obtains the operating environment data of the diagnostic communication management module, performs data compliance detection on the task request data based on the operating environment data, obtains the data compliance detection result, and sends it to the service processing submodule.
[0116] In this embodiment, multiple diagnostic tasks include initialization tasks and compliance detection tasks. Please refer to [link to relevant documentation]. Figure 5 S302 includes:
[0117] S501. Execute the initialization task to initialize the state of the service scheduler submodule for the task processing request.
[0118] In some embodiments, when the attribute compliance detection result indicates that the attributes of the task request data are compliant, the service scheduler submodule receives the attribute compliance detection result and obtains the runtime environment data of the diagnostic communication management module; at the same time, it performs state initialization for the task processing request for the service scheduler submodule.
[0119] S502. Perform compliance detection tasks based on runtime environment data and task request data to obtain data compliance detection results.
[0120] In some embodiments, compliance detection tasks are performed based on runtime environment data and task request data to complete compliance detection of the task request data. For example, compliance detection includes service type detection and request data length detection, thereby obtaining data compliance detection results.
[0121] Specifically, if the runtime environment data meets the service type and request data length processing conditions of the task request data in the current session mode, the task request data is deemed compliant; if the runtime environment data does not meet the service type and request data length processing conditions of the task request data in the current session mode, the task request data is deemed non-compliant.
[0122] In some embodiments, if the data compliance test result indicates that the data requested by the task is compliant, the data compliance test result is sent to the service processing submodule; if the data compliance test result indicates that the data requested by the task is non-compliant, an error is reported to the requesting end via DET.
[0123] S303. The service processing submodule responds to the data compliance detection result, performs task execution processing on the target task based on the task request data, obtains task response data, and sends it to the session layer submodule.
[0124] In this embodiment of the application, multiple diagnostic tasks include a target execution task and a response suspension task, and S303 includes:
[0125] Based on the task request data, the target task is executed to process the target task and obtain the task response data.
[0126] In some embodiments, when the data compliance detection result indicates that the data requested by the task is compliant, the service processing submodule receives the data compliance detection result and executes the target execution task corresponding to the task processing request to process the target task corresponding to the task processing request, thereby obtaining the task response data.
[0127] Specifically, task response data can be the result data of task processing for a target task; for example, the target task can be resetting the ECU, clearing diagnostic information, reading DTC information, reading memory by address, secure access, communication control, authentication, routing control, requesting download, requesting upload, requesting transfer exit, requesting file sending, and writing to memory by address, etc.
[0128] In this embodiment of the application, during the processing of the target task, if the execution time of the target task exceeds the preset execution time, the task is suspended in response to suspend the target task until the task response data is received.
[0129] In some embodiments, the preset execution duration can be the response cycle set by the diagnostic communication management module; specifically, the preset execution duration can be 2 seconds.
[0130] For example, if the target task is to read data from non-volatile memory, the corresponding calling component performs the corresponding data reading and returns a data waiting information; the service processing submodule responds to the data waiting information by suspending the task until it receives the task response data corresponding to the target task.
[0131] It is understandable that if the execution time for reading data from non-volatile memory exceeds the preset execution time, the execution will suspend the task to wait for the task response data.
[0132] S304. The session layer submodule encapsulates the task response data to obtain the processed response data.
[0133] In this embodiment, multiple diagnostic tasks include channel diagnostic tasks and data encapsulation tasks. Please refer to [link to relevant documentation]. Figure 6 S304 includes:
[0134] S601. Obtain the channel status information of the data transmission channel corresponding to the session layer submodule, perform channel diagnostic tasks based on the channel status information, and obtain the channel diagnostic results.
[0135] In some embodiments, when the session layer submodule receives task response data, it obtains the channel status information of the data transmission channel corresponding to the session layer submodule and performs a channel diagnostic task based on the channel status information; specifically, when the channel status information indicates that the data transmission channel is idle, it is determined that the data transmission channel meets the data transmission conditions corresponding to the processing response data; when the channel status information indicates that the data transmission channel is not idle, it is determined that the data transmission channel does not meet the data transmission conditions corresponding to the processing response data.
[0136] S602. If the channel diagnostic result indicates that the data transmission channel meets the data transmission conditions, perform a data encapsulation task on the task response data to encapsulate the task response data and obtain the processed response data.
[0137] In some embodiments, when the channel diagnostic results indicate that the data transmission channel meets the data transmission conditions, the task response data is encapsulated. Specifically, information such as the corresponding request header can be added to the task response data to obtain the processed response data.
[0138] In some embodiments, if the channel diagnostic result indicates that the data transmission channel does not meet the data transmission conditions, the channel status information is continuously acquired, and the encapsulation processing of the task response data is delayed until the channel diagnostic result indicates that the data transmission channel meets the data transmission conditions.
[0139] S103. Send the processing response data to the requesting end.
[0140] In some embodiments, the session layer submodule sends processing response data to PduR; in response to the processing response data sent by the session layer submodule, PduR sends processing response data to the vehicle diagnostic tool.
[0141] In this embodiment of the application, after S103, the task processing request response method further includes: post-processing of the task processing request by the session layer submodule, service scheduler submodule and service processing submodule in the diagnostic communication management module, respectively; for example, the post-processing of the task processing request in the session layer submodule includes channel status information update and resource status information update, etc.
[0142] The following describes the task processing request and response method provided in this application embodiment with reference to specific application scenarios. Please refer to [link to relevant documentation]. Figures 7-10 The task processing request and response method provided in this application embodiment is applied to the diagnostic communication management module, which includes a session layer submodule, a service scheduler submodule, and a service processing submodule. Figure 7 A flowchart illustrating a task processing request and response method provided in this application embodiment includes:
[0143] S11. Receive the task processing request for the target task sent by the requesting end.
[0144] S12. In response to the task processing request, obtain the resource status information corresponding to the diagnostic communication management module.
[0145] S13. Execute a cache diagnostic task based on resource status information and task request data to obtain cache diagnostic results.
[0146] S14. If the cache diagnostic result indicates that the resource status information meets the cache conditions corresponding to the task request data, execute the cache copy task to store the task request data in the target cache area corresponding to the diagnostic communication management module.
[0147] S15. Execute the cache marking task to mark the status of the target cache corresponding to the task request data and generate cache tags. The cache tags indicate the processing status of the target cache.
[0148] S16. Perform an attribute detection task on the task request data to obtain the attribute compliance detection results.
[0149] S17. In response to the attribute compliance check result, execute the initialization task to initialize the state of the service scheduler submodule for the task processing request.
[0150] S18. Obtain the operating environment data of the diagnostic communication management module, and perform compliance detection tasks based on the operating environment data and task request data to obtain data compliance detection results.
[0151] S19. In response to the data compliance detection results, based on the task request data, execute the target task to process the target task and obtain the task response data.
[0152] S110. Obtain the channel status information of the data transmission channel corresponding to the session layer submodule, perform channel diagnostic tasks based on the channel status information, and obtain the channel diagnostic results.
[0153] S111. If the channel diagnostic result indicates that the data transmission channel meets the data transmission conditions, perform a data encapsulation task on the task response data to encapsulate the task response data and obtain the processed response data.
[0154] S12. Send the processing response data to the requesting end.
[0155] Figure 8 Please refer to the schematic diagram of the diagnostic tasks corresponding to each submodule in the diagnostic communication management module provided in this application embodiment. Figure 8 For example, diagnostic tasks such as cache diagnostic tasks, cache copying tasks, cache marking tasks, attribute detection tasks, channel diagnostic tasks, and data encapsulation tasks are executed in the session layer submodule; diagnostic tasks such as initialization tasks and compliance detection tasks are executed in the service scheduler submodule; and diagnostic tasks such as target execution tasks and response suspension tasks are executed in the service processing submodule.
[0156] Figure 9 and Figure 10 A schematic diagram illustrating the flow and timing of multiple diagnostic tasks provided in this application embodiment includes:
[0157] S21. Cache diagnostic task.
[0158] S22. Cache copy task.
[0159] S23. Cache marking task.
[0160] S24. Attribute Detection Task.
[0161] S25. Initialize the task.
[0162] S26. Compliance testing tasks.
[0163] S27. Target execution task.
[0164] S28. Channel diagnostic task.
[0165] S29. Data encapsulation task.
[0166] The task processing request response method provided in this application embodiment not only enables multiple diagnostic tasks triggered in response to task processing requests to flow sequentially, but also facilitates the querying and management of the communication process of task processing requests, thereby achieving effective management of each diagnostic task and its status in the diagnostic communication management module.
[0167] This application also provides a task processing request and response device; please refer to [link to relevant documentation]. Figure 11 The task processing request response device provided in this application includes:
[0168] Receiving module 1110: Used to receive task processing requests for the target task sent by the requesting end.
[0169] Execution module 1120: is used to sequentially execute multiple diagnostic tasks in response to a task processing request based on preset task timing information to obtain processing response data; the preset task timing information indicates the flow sequence between multiple diagnostic tasks triggered in response to the task processing request; the multiple diagnostic tasks include a first task set corresponding to the session layer submodule, a second task set corresponding to the service scheduler submodule, and a third task set corresponding to the service processing submodule, and the first task set, the second task set, and the third task set each include at least one diagnostic task.
[0170] Sending module 1130: Used to send the processing response data to the requesting end.
[0171] In this embodiment of the application, the execution module 1120 includes:
[0172] First processing unit: In response to the completion of the previous diagnostic task corresponding to the target task, it triggers the task registration process of the current diagnostic task for the target task, so as to mark the current diagnostic task corresponding to the target task as registered.
[0173] The second processing unit is used to add the task processing request to the task waiting queue of the current diagnostic task in response to successful task registration, and to mark the current diagnostic task corresponding to the target task as a task waiting state.
[0174] The third processing unit is used to respond to the execution trigger of the task processing request, execute the task processing of the current diagnostic task corresponding to the target task, and mark the current diagnostic task corresponding to the target task as a task execution status.
[0175] The fourth processing unit is used to mark the current diagnostic task corresponding to the target task as completed in response to the completion of the current diagnostic task.
[0176] The fifth processing unit is used to trigger the next diagnostic task corresponding to the current diagnostic task to perform task registration processing for the target task based on preset task timing information.
[0177] In this embodiment of the application, the execution module 1120 includes:
[0178] The sixth processing unit is used by the session layer submodule to respond to task processing requests, obtain resource status information corresponding to the diagnostic communication management module, perform attribute compliance detection based on the resource status information and task request data, obtain the attribute compliance detection result, and send it to the service scheduler submodule.
[0179] The seventh processing unit is used by the service scheduler submodule to respond to the attribute compliance detection result, obtain the operating environment data of the diagnostic communication management module, perform data compliance detection on the task request data based on the operating environment data, obtain the data compliance detection result, and send it to the service processing submodule.
[0180] The eighth processing unit is used by the service processing submodule to respond to the data compliance detection results, perform task execution processing on the target task based on the task request data, obtain task response data, and send it to the session layer submodule.
[0181] The ninth processing unit is used by the session layer submodule to encapsulate and process the task response data to obtain the processed response data.
[0182] In this embodiment of the application, the sixth processing unit includes:
[0183] The first execution subunit is used to perform cache diagnostic tasks based on resource status information and task request data, and obtain cache diagnostic results.
[0184] The second execution subunit is used to execute a cache copying task if the cache diagnostic result indicates that the resource status information meets the cache conditions corresponding to the task request data, so as to store the task request data in the target cache area corresponding to the diagnostic communication management module.
[0185] The third execution subunit is used to execute the cache marking task to mark the status of the target cache corresponding to the task request data and generate cache marks. The cache marks indicate the processing status of the target cache.
[0186] The fourth execution subunit is used to perform attribute detection tasks on the task request data and obtain attribute compliance detection results.
[0187] In this embodiment of the application, the seventh processing unit includes:
[0188] The fifth execution subunit is used to perform initialization tasks to initialize the state of the service scheduler submodule in response to task processing requests.
[0189] The sixth execution subunit is used to perform compliance detection tasks based on runtime environment data and task request data, and obtain data compliance detection results.
[0190] In this embodiment of the application, the ninth processing unit includes:
[0191] The seventh execution subunit is used to obtain the channel status information of the data transmission channel corresponding to the session layer submodule, perform channel diagnostic tasks based on the channel status information, and obtain the channel diagnostic results.
[0192] The eighth execution subunit is used to perform a data encapsulation task on the task response data if the channel diagnostic result indicates that the data transmission channel meets the data transmission conditions, so as to encapsulate the task response data and obtain the processed response data.
[0193] The apparatus and method embodiments described above are based on the same application concept.
[0194] Please refer to Figure 12 This application provides an electronic device for implementing the task processing request response method described above. The electronic device includes a processor and a memory. The memory stores at least one instruction or at least one program segment. The at least one instruction or the at least one program segment is loaded and executed by the processor to implement the task processing request response method provided in the above method embodiments.
[0195] Memory can be used to store software programs and modules. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory. Memory can primarily include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for the functions, etc.; the data storage area can store data created based on the use of the device, etc. Furthermore, memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory can also include a memory controller to provide the processor with access to the memory.
[0196] The methods and embodiments provided in this application can be executed in mobile terminals, computer terminals, servers, or similar computing devices. That is, the aforementioned electronic devices may include mobile terminals, computer terminals, servers, or similar computing devices. The server may be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal may be a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, etc., but is not limited to these.
[0197] Figure 12 This is a hardware structure block diagram of an electronic device for implementing the above-described task processing request and response method, provided in an embodiment of this application. Figure 12 As shown, the electronic device 1200 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 1210 (CPUs 1210 may include, but are not limited to, microprocessors (MCUs) or programmable logic devices (FPGAs), a memory 1230 for storing data, and one or more storage media 1220 (e.g., one or more mass storage devices) for storing application programs 1223 or data 1222. The memory 1230 and storage media 1220 may be temporary or persistent storage. The program stored in the storage media 1220 may include one or more modules, each module including a series of instruction operations on the electronic device. Furthermore, the CPU 1210 may be configured to communicate with the storage media 1220 and execute the series of instruction operations in the storage media 1220 on the electronic device 1200. Electronic device 1200 may also include one or more power supplies 1260, one or more wired or wireless network interfaces 1250, one or more input / output interfaces 1240, and / or one or more operating systems 1221, such as Windows Server. TM MacOSX TM Unix TM Linux TM FreeBSD TM etc.
[0198] The processor 1210 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.
[0199] The input / output interface 1240 can be used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the electronic device 1200. In one example, the input / output interface 1240 includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the input / output interface 1240 may be a radio frequency (RF) module for wireless communication with the Internet.
[0200] The operating system 1221 may include system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, and driver layer, for implementing various basic business functions and handling hardware-based tasks.
[0201] Those skilled in the art will understand that Figure 12 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device 1200 may also include... Figure 12 The more or fewer components shown, or having the same Figure 12 The different configurations shown.
[0202] Embodiments of this application also provide a computer-readable storage medium, which can be disposed in an electronic device to store at least one instruction or at least one program related to implementing a task processing request response method in the method embodiment. The at least one instruction or the at least one program is loaded and executed by the processor to implement the task processing request response method provided in the above method embodiment.
[0203] Optionally, in this embodiment, the storage medium may be located at at least one of the multiple network servers in a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0204] Embodiments of this application also provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described above.
[0205] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, specific embodiments have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0206] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.
[0207] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.
[0208] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. A method for responding to a task processing request, applied to a diagnostic communication management module, the diagnostic communication management module comprising a session layer submodule, a service dispatcher submodule and a service processing submodule, characterized in that, The method includes: The receiving end sends a task processing request for a target task; the task processing request carries task request data. Based on preset task timing information, multiple diagnostic tasks are executed sequentially in response to the task processing request to obtain processing response data; the preset task timing information indicates the flow sequence among the multiple diagnostic tasks triggered in response to the task processing request; the multiple diagnostic tasks include a first task set corresponding to the session layer submodule, a second task set corresponding to the service scheduler submodule, and a third task set corresponding to the service processing submodule, wherein the first task set, the second task set, and the third task set each include at least one of the diagnostic tasks; Based on preset task timing information, multiple diagnostic tasks are executed sequentially in response to the task processing request to obtain processing response data, including: In response to the task processing request, the session layer submodule obtains the resource status information corresponding to the diagnostic communication management module, performs attribute compliance detection based on the resource status information and the task request data, obtains the attribute compliance detection result, and sends it to the service scheduler submodule. In response to the attribute compliance detection result, the service scheduler submodule obtains the operating environment data of the diagnostic communication management module, performs data compliance detection on the task request data based on the operating environment data, obtains the data compliance detection result, and sends it to the service processing submodule. In response to the data compliance detection result, the service processing submodule performs task execution processing on the target task based on the task request data, obtains task response data, and sends it to the session layer submodule. The session layer submodule encapsulates the task response data to obtain the processing response data; The processing response data is sent to the requesting end.
2. The task processing request response method according to claim 1, characterized by, The step of sequentially executing multiple diagnostic tasks in response to the task processing request based on preset task timing information includes: In response to the completion of the previous diagnostic task corresponding to the target task, the current diagnostic task is triggered to register the task for the target task, so as to mark the current diagnostic task corresponding to the target task as registered. In response to successful task registration, the task processing request is added to the task waiting queue of the current diagnostic task, and the current diagnostic task corresponding to the target task is marked as a task waiting state; In response to the execution trigger of the task processing request, the task processing of the current diagnostic task corresponding to the target task is executed, and the current diagnostic task corresponding to the target task is marked as a task execution state; In response to the completion of the processing of the current diagnostic task corresponding to the target task, the current diagnostic task corresponding to the target task is marked as having been completed. Based on the preset task timing information, the next diagnostic task corresponding to the current diagnostic task is triggered to perform task registration processing for the target task.
3. The task processing request and response method according to claim 1, characterized in that, The multiple diagnostic tasks include cache diagnostic tasks, cache copying tasks, cache marking tasks, and attribute detection tasks; The step of performing attribute compliance detection based on the resource status information and the task request data to obtain attribute compliance detection results includes: The cache diagnostic task is executed based on the resource status information and the task request data to obtain the cache diagnostic results. If the cache diagnostic result indicates that the resource status information meets the cache conditions corresponding to the task request data, the cache copying task is executed to store the task request data in the target cache area corresponding to the diagnostic communication management module; The cache marking task is executed to mark the status of the target cache area corresponding to the task request data and generate a cache mark, which indicates the processing status of the target cache area. The attribute detection task is executed on the task request data to obtain the attribute compliance detection result.
4. The task processing request and response method according to claim 1, characterized in that, The multiple diagnostic tasks include initialization tasks and compliance testing tasks; The data compliance check of the task request data based on the runtime environment data, to obtain the data compliance check result, includes: Execute the initialization task to initialize the state of the task processing request for the service scheduler submodule; The compliance detection task is executed based on the runtime environment data and the task request data to obtain the data compliance detection result.
5. The task processing request and response method according to claim 1, characterized in that, The multiple diagnostic tasks include target execution tasks and response suspension tasks; The step of performing task execution processing on the target task based on the task request data to obtain task response data includes: Based on the task request data, the target execution task is executed to process the target task and obtain the task response data; During the processing of the target task, if the execution time of the target task exceeds the preset execution time, the response suspension task is executed to suspend the target task until the task response data is received.
6. The task processing request and response method according to claim 1, characterized in that, The multiple diagnostic tasks include channel diagnostic tasks and data encapsulation tasks; The session layer submodule encapsulates the task response data to obtain the processed response data, including: Obtain the channel status information of the data transmission channel corresponding to the session layer submodule, perform the channel diagnostic task based on the channel status information, and obtain the channel diagnostic result; If the channel diagnostic result indicates that the data transmission channel meets the data transmission conditions, the data encapsulation task is executed on the task response data to encapsulate the task response data and obtain the processed response data.
7. A task processing request and response device, characterized in that, The device includes: Receiving module: used to receive task processing requests for a target task sent by the requesting end; the task processing request carries task request data; Execution module: used to sequentially execute multiple diagnostic tasks in response to the task processing request based on preset task timing information, and obtain processing response data; the preset task timing information indicates the flow sequence between the multiple diagnostic tasks triggered in response to the task processing request; the multiple diagnostic tasks include a first task set corresponding to the session layer submodule, a second task set corresponding to the service scheduler submodule, and a third task set corresponding to the service processing submodule, wherein the first task set, the second task set, and the third task set each include at least one of the diagnostic tasks; The execution module includes: The sixth processing unit is used by the session layer submodule to respond to the task processing request, obtain the resource status information corresponding to the diagnostic communication management module, perform attribute compliance detection based on the resource status information and the task request data, obtain the attribute compliance detection result, and send it to the service scheduler submodule. The seventh processing unit is used by the service scheduler submodule to respond to the attribute compliance detection result, obtain the operating environment data of the diagnostic communication management module, perform data compliance detection on the task request data based on the operating environment data, obtain the data compliance detection result, and send it to the service processing submodule. Eighth processing unit: In response to the data compliance detection result, the service processing submodule performs task execution processing on the target task based on the task request data to obtain task response data and sends it to the session layer submodule; Ninth processing unit: used by the session layer submodule to encapsulate the task response data to obtain the processing response data; Sending module: Used to send the processing response data to the requesting end.
8. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction or at least one program segment, which is loaded and executed by a processor according to any one of claims 1 to 7.
9. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the task processing request response method as described in any one of claims 1 to 7.
Citation Information
Patent Citations
Task engine execution method and device, equipment and medium
CN113672371A
