Map production task processing method and apparatus, electronic device, and storage medium

Abstract

The present disclosure provides a task processing method and device, electronic equipment and storage medium, relates to the technical field of computers, in particular to the field of big data and high-precision maps. The specific implementation scheme is: in response to receiving service data, such as high-precision map data, determining a service routine for processing the service data; and generating a to-be-processed task according to preset public parameter information representing public attributes of the task and service parameter information corresponding to the service routine, the to-be-processed task being used for processing the service data by using the service routine.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to the fields of big data and high-precision maps. Specifically, it relates to a task processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the rapid development of computer and internet technologies, various map products have emerged, such as high-definition maps. High-definition maps, also known as high-precision maps, are used in the field of autonomous driving. They possess accurate vehicle location information and rich road element data, helping vehicles anticipate complex road conditions such as slope, curvature, and heading, thus better avoiding potential risks. The production of map data for these map products often relies on external services. Summary of the Invention

[0003] This disclosure provides a task processing method, apparatus, electronic device, and storage medium.

[0004] According to one aspect of this disclosure, a task processing method is provided, comprising: in response to receiving business data, determining a service routine for processing the business data; and generating a task to be processed based on preset public parameter information for characterizing common attributes of the task and service parameter information corresponding to the service routine, wherein the task to be processed is used to process the business data using the service routine.

[0005] According to another aspect of this disclosure, a task processing apparatus is provided, comprising: a determining module, configured to determine a service routine for processing the service data in response to receiving service data; and a generating module, configured to generate a task to be processed based on preset public parameter information for characterizing common attributes of a task and service parameter information corresponding to the service routine, wherein the task to be processed is used to process the service data using the service routine.

[0006] According to another aspect of this disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the task processing method as described above.

[0007] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause the computer to perform the task processing method as described above.

[0008] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the task processing method as described above.

[0009] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0011] Figure 1 This illustration schematically shows an exemplary system architecture to which task processing methods and apparatus can be applied according to embodiments of the present disclosure;

[0012] Figure 2 A flowchart illustrating a task processing method according to an embodiment of the present disclosure is shown schematically.

[0013] Figure 3 An overall flowchart of a task processing method according to an embodiment of the present disclosure is illustrated schematically;

[0014] Figure 4 A block diagram of a task processing apparatus according to embodiments of the present disclosure is schematically shown; and

[0015] Figure 5 A schematic block diagram of an example electronic device that can be used to implement embodiments of the present disclosure is shown. Detailed Implementation

[0016] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0017] In the technical solution disclosed herein, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information comply with the provisions of relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals.

[0018] The production process of high-definition maps often requires interaction with multiple external services. Different external services may have different interaction methods, such as asynchronous interaction methods like active invocation, passive access, and message queues, as well as synchronous interaction methods like synchronous waiting. Active invocation refers to proactively calling external services during the high-definition map production process. Passive access involves providing an access interface, allowing external services to access relevant data during high-definition map production. Message queues introduce middleware into the interaction between high-definition maps and external services, sending messages related to the pending high-definition map data to the middleware, which the external services then retrieve and process. Synchronous waiting requires waiting for the previous task to complete before proceeding to the next. To ensure the normal and orderly operation of the high-definition map production process, the high-definition map production management platform needs to adapt to the different interaction methods of external services. Furthermore, for reuse purposes, a unified access layer can be provided for various external services.

[0019] By treating this service and external services as equivalent, a unified access layer based on HTTP (Hypertext Transfer Protocol) can be provided. This access layer can abstract a task bus implemented by queues, i.e., a task distribution interface. This task bus is responsible for transmitting all interaction messages between this service and external services. By distributing interaction messages to different services according to their type, task scheduling between services is accomplished. Interaction messages sent by each service to the task bus use JSON format, which can abstract unified task header information. Detailed task information can be defined according to the service type.

[0020] In realizing the concept disclosed herein, the inventors discovered that the task bus requires additional configuration. This additional bus distribution strategy tightly couples the access layer with the business logic, and also requires the bus developers to understand the business logic of all services and the calling relationships between various interaction messages. Furthermore, text-based interaction messages implemented using JSON format have a low data compression ratio and low serialization efficiency.

[0021] Another unified access layer based on HTTP can provide a unified interface for different services. The interface parameters can include the union of service parameters from different services. High-precision map platforms can distinguish different services by their service addresses, and each service can obtain the necessary parameters according to its own requirements.

[0022] In the process of realizing the concept disclosed herein, the inventors discovered that a unified interface that includes all parameters required by all services would result in parameter redundancy and strong coupling between business fields of various services.

[0023] This disclosure provides a task processing method, apparatus, electronic device, and storage medium. The task processing method includes: in response to receiving business data, determining a service routine for processing the business data; and generating a task to be processed based on preset public parameter information characterizing common attributes of the task and service parameter information corresponding to the service routine. The task to be processed is used to process the business data using the service routine.

[0024] Figure 1 An exemplary system architecture for applying task processing methods and apparatus according to embodiments of this disclosure is illustrated.

[0025] It is important to note that Figure 1 The examples shown are merely examples of system architectures that can be applied to the embodiments of this disclosure, to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments, or scenarios. For example, in another embodiment, an exemplary system architecture to which the task processing method and apparatus can be applied may include a terminal device, but the terminal device can implement the task processing method and apparatus provided by the embodiments of this disclosure without interacting with the server.

[0026] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, and 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the terminal devices 101, 102, and 103 and the server 105. The network 104 may include various connection types, such as wired and / or wireless communication links, etc.

[0027] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as knowledge reading applications, web browser applications, search applications, instant messaging tools, email clients, and / or social platform software, etc. (for example only).

[0028] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0029] Server 105 can be a server providing various services, such as a backend management server supporting the content browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process received user requests and other data, and feed back the processing results (such as web pages, information, or data obtained or generated based on user requests) to the terminal devices. The server can be a cloud server, also known as a cloud computing server or cloud host, a host product within the cloud computing service system, addressing the shortcomings of traditional physical hosts and VPS (Virtual Private Server, or simply "VPS") in terms of management difficulty and weak business scalability. The server can also be a server for a distributed system or a server integrated with blockchain technology.

[0030] It should be noted that the task processing method provided in the embodiments of this disclosure can generally be executed by terminal devices 101, 102, or 103. Accordingly, the task processing device provided in the embodiments of this disclosure can also be disposed in terminal devices 101, 102, or 103.

[0031] Alternatively, the task processing method provided in this embodiment can generally be executed by server 105. Correspondingly, the task processing apparatus provided in this embodiment can generally be located in server 105. The task processing method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the task processing apparatus provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0032] For example, when task processing is required, terminal devices 101, 102, 103, or server 105 can acquire business data. In response to receiving the business data, they determine a service routine for processing it and generate a task to be processed based on preset public parameter information characterizing the task's public attributes and the service parameter information corresponding to the service routine. The task to be processed is used to process the business data using the service routine. Alternatively, a server or server cluster capable of communicating with terminal devices 101, 102, 103, and / or server 105 can generate a task to be processed in response to receiving business data.

[0033] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0034] Figure 2 A flowchart illustrating a task processing method according to an embodiment of the present disclosure is shown schematically.

[0035] like Figure 2 As shown, the method includes operations S210 to S220.

[0036] In operation S210, in response to receiving business data, a service routine for processing the business data is determined.

[0037] In operation S220, a task to be processed is generated based on the preset public parameter information used to characterize the public attributes of the task and the service parameter information corresponding to the service routine. The task to be processed is used to process business data using the service routine.

[0038] According to embodiments of this disclosure, business data may include data related to high-precision map services, such as lane lines, road boundaries, road signs, and driving routes. Service routines for processing business data may include service routines of external services that exist independently of the high-precision map production management platform. These external services can be used to facilitate data processing on the high-precision map production management platform. Service routines may include at least one of preprocessing service routines, quality inspection service routines, differential processing service routines, and batch processing service routines, and are not limited thereto.

[0039] It should be noted that business data can also include data related to business in other application scenarios, and this is not limited here.

[0040] According to embodiments of this disclosure, the common attributes of a task may include at least one of the following: task ID (identifier), task execution status, task type, task start time, and task end time. Preset common parameters may include at least one of the following: parameters related to the task identifier, parameters related to the task execution status, parameters related to the task type, parameters related to the task start time, and parameters related to the task end time. Service parameters may include parameters corresponding to the business data required in the service routine.

[0041] For example, when the service routine is a preprocessing service routine, the service parameters may include at least one of the following: a data source address and a data upload address. When the service routine is a quality inspection service routine, the service parameters may include at least one of the following: a data source address and an address related to a pre-defined quality inspection method for various types of data. When the service routine is a differential service routine, the service parameters may include at least one of the following: parameters representing the data content corresponding to different versions of the same data, and parameters representing the data content corresponding to the same data before and after processing. When the service routine is a batch processing service routine, the service parameters may include at least one of the following: a data source and a batch processing unit data volume.

[0042] According to embodiments of this disclosure, the tasks to be processed may include tasks determined based on preset public parameters and their corresponding data, tasks determined based on service parameters and their corresponding data, and tasks determined based on preset public parameters, service parameters, and their corresponding data. The high-precision map production management platform may have a preset workflow, which can control the platform to automatically trigger corresponding tasks for data processing when it receives relevant data, and can automatically trigger the execution of the next task after the previous task is completed.

[0043] For example, when the platform receives newly collected map data, it can determine that the service used to process this newly collected map data is a preprocessing service. Then, a preprocessing task can be generated based on preset public parameter information and service parameter information corresponding to the preprocessing service. The preprocessing task can include public attribute information of the task, such as task ID, task execution status, task type, etc., and can also include data information that the task needs to process, so as to realize the processing of map data using the preprocessing service.

[0044] Through the above embodiments of this disclosure, the public information of different tasks can be represented by preset public parameter information, and the unique information related to each service can be represented by service parameter information. Based on this parameter construction method, different services can maintain a parameter structure according to the parameters required by each service, which can effectively decouple the business fields between different services and effectively alleviate the redundancy of parameter settings.

[0045] The following describes specific embodiments. Figure 2 The method shown will be further explained.

[0046] According to embodiments of this disclosure, generating a task to be processed based on preset public parameter information characterizing the public attributes of a task and service parameter information corresponding to a service routine may include: determining public attribute data characterizing the public attributes of the task to be processed based on the preset public parameter information; determining service data corresponding to business data based on the service parameter information; and generating the task to be processed based on the public attribute data and the service data.

[0047] According to embodiments of this disclosure, for example, the service routine is a preprocessing service. Records for preprocessing tasks corresponding to the preprocessing service can be generated based on preset public parameter information, including task ID, task execution status, and task type, to obtain public attribute data characterizing the public attributes of the preprocessing task. In this record, the task ID can represent unique identification information used to determine the preprocessing task. The task execution status can characterize the real-time status changes of the preprocessing task during processing, such as "created but not started," "processing," "processing successful," or "processing failed." The task type can be a preprocessing task. Furthermore, based on service parameter information corresponding to the preprocessing service and combined with business data, the pending data to be processed in the preprocessing task, i.e., the aforementioned service data, can be determined, characterizing the business data corresponding to the service parameter information. This facilitates the generation of a preprocessing task including record information and pending data based on the public attribute data and service data of the preprocessing task.

[0048] Through the embodiments of this disclosure, tasks to be processed can be generated based on public attribute data determined by preset public parameter information and service data determined by service parameter information. On the one hand, the integrity of task data can be maintained; on the other hand, business fields between different services can be effectively decoupled, and parameter setting redundancy can be reduced.

[0049] According to embodiments of this disclosure, after generating a task to be processed, the task processing method may further include: invoking a service routine in response to detecting the task to be processed; and using the service routine to process service data to process the task to be processed.

[0050] According to embodiments of this disclosure, pending tasks, including recorded information and data to be processed, can be stored in a preset database. By polling the tasks in the database, when a pending task is detected, an appropriate interaction method can be selected to allow an external service to obtain and process the relevant data of the pending task.

[0051] According to embodiments of this disclosure, since the interaction method may include active invocation, passive access, message queue, synchronous waiting, etc., the method of invoking a service routine in response to detecting a pending task may include: if it is determined that the interaction method between the detected pending task and the external service is active invocation, the service routine of the external service may be actively invoked upon detection of the pending task to process the pending task. If it is determined that the interaction method between the detected pending task and the external service is passive access, the external service routine may actively invoke and process the relevant data in the pending task upon detection. If it is determined that the interaction method between the detected pending task and the external service is message queue, the data related to the pending task may be stored in the message queue for the service routine of the external service to retrieve and process. If it is determined that the interaction method between the detected pending task and the external service is synchronous waiting, the status of other tasks in the database may be detected. If it is determined that other tasks are not yet completed, a waiting process may be initiated until all other tasks are completed, and then the service routine of the external service may be used to process the pending task.

[0052] According to embodiments of this disclosure, when there are many tasks to be processed stored in the database, the number of external services can be expanded to enable rapid processing of the tasks to be processed.

[0053] Through the embodiments described above, asynchronous processing of task generation and task execution can be achieved. Furthermore, the task processing based on this method exhibits good service scalability.

[0054] According to embodiments of this disclosure, before processing the service data using a service routine, the task processing method may further include: converting the service data into binary format data; and transmitting the binary format data to the service routine.

[0055] According to embodiments of this disclosure, the service routine can be an external service routine that exists independently of the high-precision map production management platform. The relevant data of the task to be processed can be stored in the internal database of the high-precision map production management platform. When using an external service to process the task to be processed, the relevant data of the task to be processed can be sent to the service routine of the external service in binary format.

[0056] According to embodiments of this disclosure, inter-service interaction can be achieved using brpc and Protobuffer. brpc is an RPC (Remote Procedure Call) framework based on the protobuf interface, and Protobuffer is an independent data exchange format. brpc uses Protobuffer's serialization method to convert the data to be processed stored in the database into binary format for transmission. The binary format data to be processed can be more compact.

[0057] By converting service data into binary format through the above embodiments of this disclosure, message serialization efficiency can be improved, thereby effectively improving task processing efficiency.

[0058] According to embodiments of this disclosure, in the process of processing a task to be processed using a service routine, the task processing method may further include: updating public attribute data in response to processing the task to be processed.

[0059] According to embodiments of this disclosure, for example, the task to be processed is a preprocessing task, and the public attribute data may include information such as the task ID, task execution status, task type, task start time, and task end time of the preprocessing task. When a preprocessing task is generated and data related to the preprocessing task is stored in a preset database, the status in the public attribute data can be "Created but not started," indicating that the preprocessing task has not yet processed the data to be processed. If it is determined that a service routine can process the task to be processed, the status in the public attribute data can be automatically updated to "Processing," in which case the preprocessing task can obtain and process the data to be processed. After the service routine completes processing the task to be processed, the status in the public attribute data can be automatically updated to "Processing successful." If the processing of the task to be processed using the service routine fails, the status in the public attribute data can be automatically updated to "Processing failed," in which case the preprocessing task can be automatically re-executed.

[0060] The above embodiments of this disclosure can record the processing status of tasks in real time, which is beneficial to the normal execution of various pending tasks.

[0061] According to embodiments of this disclosure, the service routine may include at least one of the following: a preprocessing service routine, a quality inspection service routine, a differential service routine, and a batch processing service routine, and may be wired to the ratio.

[0062] According to embodiments of this disclosure, corresponding parameter structures can be pre-configured for various service routines that need to interact in various business scenarios, so as to realize the interaction between various service routines and business data.

[0063] It should be noted that parameter structures for different service configurations can be uniformly stored in a preset database, and can also be stored in the same preset database as preset common parameter information.

[0064] Through the above embodiments of this disclosure, interaction between various service routines and business data in various scenarios can be realized. The implemented task processing method is compatible with various service types and can be easily extended to new service routines.

[0065] According to embodiments of this disclosure, the common attributes of a task may include at least one of the following: task identifier, task execution status, task type, task start time, and task end time, and may be wired thereto.

[0066] Through the above embodiments of this disclosure, the processing details of tasks can be recorded in real time, which is beneficial to the normal execution of various pending tasks.

[0067] Figure 3 An overall block diagram of a task processing method according to an embodiment of the present disclosure is shown schematically.

[0068] like Figure 3 As shown, the upstream service module 310 can include various business modules, such as modules related to the high-precision map generation and management platform. The access layer interface module 320 can encapsulate predefined parameter structures for the business data processed by each service, such as Server_task_info_1, Server_task_info_2, etc., as well as predefined parameter structures for public attributes representing different tasks that are unrelated to business in the task scheduling framework, such as Task_info, etc. The database module 330 can store relevant data for tasks to be processed, such as service data that the task to be processed needs to process, and public attribute data of the task to be processed. The interaction module 340 can provide multiple interaction methods, such as active invocation, passive access, message queues, synchronous waiting, etc., to facilitate interaction between the service routines 351, 352, 353, etc. of external services 350 and the database module 330, enabling the processing of tasks to be processed using service routines 351, 352, 353, etc.

[0069] According to embodiments of this disclosure, the format of the parameter structure and the information of each parameter can be pre-defined according to the actual business scenario, and different parameter information with different formats and fields can be defined for different services. The parameter structure can abstract the interaction of tasks into a unified format. For example, when facing various tasks such as push (submit a task), pull (retrieve a task from the queue), trigger (trigger a task through an interface), update (update the task status), and kill (terminate a task), these various tasks can be unified into processing service data and updating public attribute data.

[0070] For example, in response to upstream service module 310 receiving business data, the service routine used to process the business data can be identified as a quality inspection service routine, and the parameter structure corresponding to the quality inspection service routine is, for example, Server_task_info_2. Common attribute data, such as task ID, task type (quality inspection), task status ("created but not started"), task start time (empty), and task end time (empty), can be populated into the predefined parameter information in Task_info. Furthermore, based on the business data and the predefined parameter information in Server_task_info_2, the service data to be processed by the task can be obtained. The populated service data and common attribute data can be saved to database module 330 to generate a quality inspection task. Downstream quality inspection services (such as service routine 352) can detect and obtain the quality inspection task, for example, through a pull method, and process the quality inspection task. Accordingly, when processing a direct task, the execution status of the quality inspection task stored in database 330 can be updated to "processing" based on the task ID of the quality inspection task. By updating the task execution status, it is possible to refuse other services from processing the task if other services also obtain the quality inspection task.

[0071] It should be noted that when using the quality inspection service routine to process quality inspection tasks, since single-machine processing is slow, the task may be broken down into many smaller tasks internally. Each task can have its own state. If a smaller task fails, its internal retry mechanism can be executed. The corresponding state in the database will only be updated when all smaller tasks have been processed.

[0072] According to embodiments of this disclosure, Task_info can be considered equivalent to the header information of a task to be processed. When processing a task, this part can be parsed first to obtain information such as task ID, task execution status, and task type. This means that the task processing flow can be achieved by parsing only the process attribute data. The parameters defined in the corresponding Server_task_info can be parsed only when dealing with a specific service to determine and obtain the service data that the task to be processed needs.

[0073] Through the above embodiments of this disclosure, a framework that supports access services for multiple types of tasks can be implemented, enabling interaction between various service routines and business data in various scenarios. The implemented task processing method is compatible with various service types and is easy to extend.

[0074] Figure 4 A block diagram of a task processing apparatus according to an embodiment of the present disclosure is shown schematically.

[0075] like Figure 4 As shown, the task processing device 400 may include a determining module 410 and a generating module 420.

[0076] The determination module 410 is used to determine the service routine for processing the business data in response to receiving the business data.

[0077] The generation module 420 is used to generate a task to be processed based on the preset public parameter information used to characterize the public attributes of the task and the service parameter information corresponding to the service routine. The task to be processed is used to process business data using the service routine.

[0078] According to embodiments of this disclosure, the generation module includes a first determining unit, a second determining unit, and a generation unit.

[0079] The first determining unit is used to determine the common attribute data used to characterize the common attributes of the task to be processed, based on the preset common parameter information.

[0080] The second determining unit is used to determine the service data corresponding to the business data based on the service parameter information.

[0081] The generation unit is used to generate tasks to be processed based on public attribute data and service data.

[0082] According to embodiments of this disclosure, the task to be processed includes service data corresponding to business data. The task processing apparatus further includes a calling module and a processing module.

[0083] The calling module is used to invoke service routines in response to the detection of pending tasks.

[0084] The processing module is used to process service data using service routines in order to process the tasks to be processed.

[0085] According to embodiments of this disclosure, the task processing apparatus further includes a conversion module and a transmission module before the processing module.

[0086] The conversion module is used to convert service data into binary format data.

[0087] The transmission module is used to transmit binary format data to the service routine.

[0088] According to embodiments of this disclosure, the task to be processed includes public attribute data. The task processing apparatus also includes an update module.

[0089] The update module is used to update public attribute data in response to the processing of tasks to be processed.

[0090] According to embodiments of this disclosure, the service routine includes at least one of the following: a preprocessing service routine, a quality inspection service routine, a differential service routine, and a batch processing service routine.

[0091] According to embodiments of this disclosure, the common attributes of a task include at least one of the following: task identifier, task execution status, task type, task start time, and task end time.

[0092] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0093] According to an embodiment of the present disclosure, an electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the task processing method described above.

[0094] According to embodiments of the present disclosure, a non-transitory computer-readable storage medium stores computer instructions, wherein the computer instructions are used to cause a computer to perform the task processing method described above.

[0095] According to an embodiment of this disclosure, a computer program product includes a computer program that, when executed by a processor, implements the task processing method described above.

[0096] Figure 5 A schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0097] like Figure 5As shown, device 500 includes a computing unit 501, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 502 or a computer program loaded from storage unit 508 into random access memory (RAM) 503. RAM 503 may also store various programs and data required for the operation of device 500. The computing unit 501, ROM 502, and RAM 503 are interconnected via bus 504. Input / output (I / O) interface 505 is also connected to bus 504.

[0098] Multiple components in device 500 are connected to I / O interface 505, including: input unit 506, such as keyboard, mouse, etc.; output unit 507, such as various types of monitors, speakers, etc.; storage unit 508, such as disk, optical disk, etc.; and communication unit 509, such as network card, modem, wireless transceiver, etc. Communication unit 509 allows device 500 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0099] The computing unit 501 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as task processing methods. For example, in some embodiments, the task processing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by the computing unit 501, one or more steps of the task processing method described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform task processing methods by any other suitable means (e.g., by means of firmware).

[0100] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0101] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0102] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0103] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0104] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0105] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, distributed system servers, or servers incorporating blockchain technology.

[0106] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0107] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A task processing method, comprising: In response to receiving service data, determine a service routine for processing the service data; as well as Based on preset public parameter information used to characterize the common attributes of the task and service parameter information corresponding to the service routine, a task to be processed is generated, wherein the task to be processed is used to process the business data using the service routine; the preset public parameter information is used to characterize the common information between different tasks; the service parameter information is used to characterize the service-related specific information. The step of generating a task to be processed based on preset public parameter information used to characterize the public attributes of the task and service parameter information corresponding to the service routine includes: determining public attribute data used to characterize the public attributes of the task to be processed based on the preset public parameter information; determining service data corresponding to the business data based on the service parameter information; and generating the task to be processed based on the public attribute data and the service data.

2. The method according to claim 1, wherein, The task to be processed includes service data corresponding to the business data, and the method further includes: In response to detecting the pending task, the service routine is invoked; and The service routine is used to process the service data in order to process the task to be processed.

3. The method of claim 2, further comprising, before processing the service data using the service routine: Convert the service data into binary format data; and The binary format data is transmitted to the service routine.

4. The method according to any one of claims 1 to 3, wherein, The task to be processed includes public attribute data, and the method further includes: In response to processing the task to be processed, the public attribute data is updated.

5. The method according to any one of claims 1 to 4, wherein, The service routine includes at least one of the following: Preprocessing service routines, quality inspection service routines, differential service routines, and batch processing service routines.

6. The method according to any one of claims 1 to 5, wherein, The task public attributes include at least one of the following: Task identifier, task execution status, task type, task start time, and task end time.

7. A task processing apparatus, comprising: A determination module is configured to determine a service routine for processing the received service data in response to receiving the service data. as well as The generation module is used to generate a task to be processed based on preset public parameter information used to characterize the common attributes of the task and service parameter information corresponding to the service routine. The task to be processed is used to process the business data using the service routine. The preset public parameter information is used to characterize the common information between different tasks. The service parameter information is used to characterize the service-related specific information. The generation module includes: The first determining unit is used to determine, based on the preset common parameter information, common attribute data used to characterize the common attributes of the task to be processed. The second determining unit is configured to determine, based on the service parameter information, the service data corresponding to the business data; and The generation unit is used to generate the task to be processed based on the public attribute data and the service data.

8. The apparatus according to claim 7, wherein, The task to be processed includes service data corresponding to the business data, and the device further includes: The calling module is used to invoke the service routine in response to detecting the pending task; and The processing module is used to process the service data using the service routine in order to process the task to be processed.

9. The apparatus of claim 8, wherein, prior to the processing module, the apparatus further comprises: A conversion module is used to convert the service data into binary format data; and A transmission module is used to transmit the binary format data to the service routine.

10. The apparatus according to any one of claims 7 to 9, wherein, The task to be processed includes public attribute data, and the device further includes: An update module is used to update the public attribute data in response to processing the task to be processed.

11. The apparatus according to any one of claims 7 to 10, wherein, The service routine includes at least one of the following: Preprocessing service routines, quality inspection service routines, differential service routines, and batch processing service routines.

12. The apparatus according to any one of claims 7 to 11, wherein, The task public attributes include at least one of the following: Task identifier, task execution status, task type, task start time, and task end time.

13. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.

14. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-6.

15. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-6.

Images