Map task processing method and device, equipment, medium and program product

Abstract

The embodiment of the invention provides a map task processing method and device, equipment, a medium and a program product, and can relate to the field of maps, and the method comprises the following steps: creating task link configuration of a target map task; wherein the task link configuration comprises a production line code of a map production line to which the target map task belongs, and link codes and parameter configuration of each operation link of the target map task; when the target map task is created, reading task link configuration of the target map task; and after the target map task is created, if the historical task link flow chart comprises each operation link of the target map task, executing the target map task based on the historical task link flow chart and task link configuration of the target map task. When the historical task link flow chart comprises each operation link of the target map task, the historical task link flow chart does not need to be modified, and the historical task link flow chart is directly used, so that the execution efficiency of the map task can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of maps, and in particular to a map task processing method, apparatus, device, medium, and program product. Background Art

[0002] Map road operations typically involve one or more map production lines, such as those for intersection lane markings and ground object production. Each map production line can include one or more map tasks. For example, the intersection lane marking production line can include tasks such as drawing lane markings, drawing traffic lights, and drawing turn markers. Each map task can include one or more operational steps. For example, drawing lane markings at intersections involves pre-operation steps, in-operation steps, and post-quality inspection and submission steps.

[0003] Currently, when executing a map task, it can be executed based on the task process flow chart of the map task. For newly added map tasks or map tasks with changes in task process, it is necessary to modify the historical task process flow chart and execute the map task based on the modified historical task process flow chart. However, this task processing method has the problem of low map task execution efficiency. Summary of the Invention

[0004] The embodiments of the present application provide a map task processing method, apparatus, device, medium, and program product, thereby improving the efficiency of map task execution.

[0005] In the first aspect, an embodiment of the present application provides a map task processing method, including: creating a task link configuration for a target map task; wherein the task link configuration includes: the production line code of the map production line to which the target map task belongs, the link code of each operation link of the target map task, and the parameter configuration of each operation link; when creating the target map task, the task link configuration of the target map task is read; after the target map task is created, if the historical task link flowchart includes each operation link of the target map task, then the target map task is executed based on the historical task link flowchart and the task link configuration of the target map task.

[0006] In the second aspect, an embodiment of the present application provides a task processing device, including: a processing module, used to: create a task link configuration of a target map task; wherein the task link configuration includes: the production line code of the map production line to which the target map task belongs, the link code of each operation link of the target map task and the parameter configuration of each operation link; when creating the target map task, the task link configuration of the target map task is read; after the target map task is created, if the historical task link flowchart includes each operation link of the target map task, the target map task is executed based on the historical task link flowchart and the task link configuration of the target map task.

[0007] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and executing the method as in the first aspect or its various implementations.

[0008] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute the method in the first aspect or its various implementations.

[0009] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the method in the first aspect or its various implementations.

[0010] In a sixth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute the method in the first aspect or its various implementations.

[0011] Through the technical solution provided by this application, the embodiment of this application proposes a map task with newly added map tasks or changes in task links. When the historical task flowchart includes the various operation links of the map task, there is no need to modify the historical task flowchart. Instead, the task can be executed based on the task link configuration of the map task and the historical task flowchart, thereby improving the efficiency of map task execution. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0013] Figure 1 A schematic diagram of a system architecture involved in an embodiment of the present application;

[0014] Figure 2A flowchart of a map task processing method provided in an embodiment of the present application;

[0015] Figure 3 A partial schematic diagram of a task process flow chart provided in an embodiment of the present application;

[0016] Figure 4 It is a partial schematic diagram of a task link flow chart;

[0017] Figure 5 It is a partial schematic diagram of another task link flow chart;

[0018] Figure 6 A partial schematic diagram of another task link flow chart;

[0019] Figure 7 A data synchronization diagram provided in an embodiment of the present application;

[0020] Figure 8 A schematic diagram of hot and cold data separation provided in an embodiment of the present application;

[0021] Figure 9 A state transition diagram provided in an embodiment of the present application;

[0022] Figure 10 A data processing diagram provided in an embodiment of the present application;

[0023] Figure 11 A PMS operation flow chart provided in an embodiment of the present application;

[0024] Figure 12 A PMS architecture diagram provided in an embodiment of the present application;

[0025] Figure 13 A functional diagram of each service module provided in an embodiment of the present application;

[0026] Figure 14 A flowchart of a task processing process provided in an embodiment of the present application;

[0027] Figure 15 A schematic diagram of a task processing device 1500 provided in an embodiment of the present application;

[0028] Figure 16 It is a schematic block diagram of the server 1600 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0032] The embodiments of the present application may relate to the field of maps, but are not limited thereto.

[0033] Among them, the map field involves data collection, data preprocessing, map production, map output and map application.

[0034] Data collection methods include, but are not limited to, self-collection, device crowdsourcing, and manual crowdsourcing. Self-collection refers to the automated collection of data from various sources, such as websites, databases, and sensors, using specific tools or methods. Device crowdsourcing utilizes a large number of devices, such as smartphones and IoT devices, to collect data. Manual crowdsourcing utilizes a large number of human resources and intelligence to collect data.

[0035] Among them, data preprocessing may include: data denoising, data normalization, data cleaning, data dimensionality reduction, etc., but is not limited to these.

[0036] It should be understood that the map production process is a process of generating a map based on preprocessed data. The technical solution provided in the embodiment of the present application can be applied to the map production process. For example, the task provided in the embodiment of the present application can be the production task of a map of a certain road section.

[0037] Map applications may include, but are not limited to, navigation, basemap, and retrieval.

[0038] It should be understood that a base map generally refers to basic map data, which provides basic information such as geographic location, roads, buildings, and terrain. The base map is the foundational layer of a map service, and other layers (such as traffic flow and weather conditions) are usually overlaid on top of the base map.

[0039] It should be understood that in a map service, retrieval may include finding a place or route based on geographic location, name, or other attributes.

[0040] The following is an explanation of the relevant knowledge involved in this application:

[0041] 1. Map road operations usually refer to the work of collecting, editing, updating and maintaining road information on maps.

[0042] 2. Map production line: The road production line refers to the route taken during the map product production process. For example, in map road production, it can include: intersection lane line production line, ground target object production line, etc.

[0043] 3. Map tasks: A map production line can include one or more map tasks. For example, in a map road operation, a lane marking production line for an intersection may include tasks such as drawing lane markings at an intersection, drawing traffic lights at an intersection, and drawing turn markers at an intersection.

[0044] 4. The operation links of map tasks. A map task can include one or more operation links. For example, the lane line drawing at an intersection includes: pre-operation link, operation link and post-quality inspection submission link.

[0045] 5. Task process flow chart is a graphical representation used to intuitively describe the various work links and steps in the task execution process.

[0046] 6. The basic information table of map tasks is used to store the basic information of map tasks, such as task number, task link, task status, etc. The basic information table of map tasks can include: basic information table of collected data, basic information table of tasks, task link table, task status table, task attribute table, operation link attribute table, etc.

[0047] 7. Task master table, used to store the latest basic information of map tasks. The difference between it and the basic information table of map tasks is that the task master table only stores the latest basic information, while the basic information table can store the historical basic information and the latest basic information of map tasks. In other words, the information in the task master table belongs to the basic information table of map tasks.

[0048] 8. Task state machine, also known as finite-state machine (FSM) or finite-state automaton (FSA), is a mathematical computation model that represents a finite number of states and the transitions and actions between these states.

[0049] 9. Hot and cold data separation is a data processing strategy designed to reduce storage costs and improve data access efficiency. In this strategy, data is divided into hot and cold data. Hot data refers to frequently accessed and frequently modified data, while cold data refers to infrequently accessed and finalized data.

[0050] 10. Aspect-Oriented Programming (AOP) is a programming paradigm that allows developers to define cross-cutting concerns that span multiple modules, classes, or methods of an application. The main purpose of AOP is to separate the business logic of an application from cross-cutting concerns (such as logging, transaction management, security checks, etc.) to improve code maintainability and reusability.

[0051] 10. Aspects, which include pointcuts and advice. Advice defines the code to be executed at a pointcut. This code can be logic before or after a method is executed, or when an exception is thrown. Aspects allow developers to separate cross-cutting concerns such as logging, transaction management, and security checks from the main business logic, making the code clearer and more maintainable.

[0052] 11. A join point is a point in the application's execution where an aspect can be inserted. These points can be method calls, exception throws, or even field modifications. A join point is a virtual concept that represents a specific moment in the program's execution. In AOP, a join point is a potential location where an aspect's notifications can be applied.

[0053] 12. Pointcuts are a set of specific join points selected from all possible join points based on certain rules. These rules can be defined based on classes, methods, annotations, etc. The purpose of pointcuts is to precisely specify the join points at which advice should be applied. In other words, pointcuts define the specific join points at which advice should be woven.

[0054] The relationship between pointcuts and join points can be understood as follows: a join point is a set of all possible insertion points in a program's execution, while a pointcut is a specific set of insertion points selected from these. Pointcuts define rules to filter join points, ensuring that advice is applied at the right time.

[0055] 13. Advice defines the code to be executed when a pointcut is triggered. There are several types of advice, including before advice, after advice, after returning advice, after throwing advice, and around advice.

[0056] 14. Surround notification: The notification wraps the notified method and performs custom behaviors before and after the notified method is called.

[0057] 15. Batch processing is a computer data processing technology that allows users to organize a series of commands or programs into a batch file, and then automatically execute these commands or programs at one time without having to manually enter or run them each time.

[0058] 16. The mother database is the primary repository for map data, typically containing the most complete, accurate, and fundamental datasets. It serves as the starting point for map data production and is used to create and update other databases. Data in the mother database typically undergoes rigorous quality control and verification to ensure its accuracy and completeness. The mother database is typically not used directly for end-user map presentations, but rather serves as a data source for the production of other derived databases.

[0059] 17. Small libraries, also known as branch libraries, typically refer to a collection of map data for a specific region or range. This data is extracted from a larger data source (such as a parent library) as needed and appropriately processed and optimized. Small libraries are primarily used for map display and querying, as they contain detailed data for the area required by the user and are typically optimized to increase query and rendering speed. Small libraries have relatively small data volumes, are easy to manage and deploy, and are suitable for end users or applications.

[0060] 18. The differential database is a collection of map data that has changed compared to the main database. These changes may include newly added roads, buildings, terrain data, etc.

[0061] 19. Scattered distribution means that if two tasks have the same operation scope, there may be data conflicts. The service control task surfaces of these tasks need to be scattered (i.e., broken up or dispersed) to control their distribution order.

[0062] The following describes the technical problems, inventive concepts, and application scenarios to be solved by the embodiments of the present application:

[0063] As mentioned above, currently, when executing a map task, it can be executed based on the task process flow chart of the map task. For newly added map tasks or map tasks with changes in task process, it is necessary to modify the historical task process flow chart and execute the map task based on the modified historical task process flow chart. However, this task processing method has the problem of low map task execution efficiency.

[0064] In order to solve the above technical problems, the embodiment of the present application proposes that for newly added map tasks or map tasks with changes in task links, when the historical task flowchart includes the various operation links of the map task, there is no need to modify the historical task flowchart, but the task can be executed based on the task link configuration of the map task and the historical task flowchart, thereby improving the efficiency of map task execution.

[0065] In some implementations, the system architecture of the embodiment of the present application is as follows: Figure 1 shown.

[0066] Figure 1 This is a system architecture diagram involved in an embodiment of the present application, including a terminal device 110 and a server 120, wherein the terminal device 110 may be installed with an application (Application, APP) corresponding to the production management system, such as Wemap, and the server 120 is a background server corresponding to the production management system.

[0067] In some implementations, the terminal device 110 may be a desktop computer, a laptop computer, a tablet computer, a smart phone, a tablet computer, a smart watch, virtual reality (VR), augmented reality (AR), etc., but is not limited thereto.

[0068] The terminal device 110 and the server 120 may be connected directly or indirectly via wired or wireless communication, which is not limited in this application.

[0069] In some possible implementations, the server 120 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0070] It should be noted that Figure 1 This is only a schematic diagram of a system architecture provided by the embodiment of the present application. The system architecture involved in the embodiment of the present application is not limited to Figure 1 The system architecture shown, for example, the number of terminal devices 110 is not limited to Figure 1 One is shown, but there may be more than one.

[0071] The following is a detailed description of the embodiments of the present application:

[0072] Figure 2 This is a flowchart of a map task processing method provided in an embodiment of the present application. The method can be executed by a server, which can be a background server corresponding to a production management system, such as Figure 2 As shown, the method may include:

[0073] S210: Creating task link configuration for target map task;

[0074] In some implementations, the target map task may be a newly added task in the production management system or a task with a changed task link.

[0075] For example, a new task of drawing lane lines at intersections has been added to map road operations, and this map task can be used as a target map task.

[0076] For example, in map road operations, there was previously a task for drawing intersection channel lights. This map task included: pre-operation, during-operation, and after quality inspection submission. Among them, the pre-operation stage included three batch operations: batch z values, lane center lines, and batch guide strips. After the pre-operation stage of this map task was modified, it included two batch operations: batch z values ​​and lane center lines. Based on this, the task with the changed task stage can be used as the target map task.

[0077] In some possible implementations, the task link configuration includes, but is not limited to: the production line code of the production line to which the target map task belongs, the link code of each operation link of the target map task, and the parameter configuration of each operation link.

[0078] For example, the task step configuration for production line P_0719 includes: production line code production_line_code P_0719, pre-step code before_step, step parameter configurations 288 and 281, mid-step code middle_step, step parameter configurations 288 and 290, and post-quality inspection submission code after_step, step parameter configurations 281 and 290. 288 represents the batch operation: batch z values, 281 represents the batch operation: lane centerlines, and 290 represents the batch operation: batch guide strips. In other words, the task step configuration for production line P_0719 indicates batch z values ​​and lane centerlines in the pre-step, batch z values ​​and guide strips in the mid-step, and lane centerlines and guide strips in the post-quality inspection submission.

[0079] In some implementations, the task link configuration of the target map task can be stored in a link flow configuration table, but is not limited thereto.

[0080] For example, Table 1 is an exemplary link flow configuration table:

[0081] Table 1

[0082]

[0083] In some implementations, the server may receive a first creation instruction sent by a terminal device, and respond to the first creation instruction to create a task link configuration of the target map task.

[0084] In some implementations, the terminal device may obtain a first creation operation and generate a first creation instruction based on the first creation operation, wherein the first creation operation is used to create a task link configuration of the target map task.

[0085] It should be understood that the terminal device can be installed with applications (Application, APP) corresponding to the production management system, such as Wemap. WeMap is a map product system for the smart industry. The system consists of five major products, including data factory (Data), data management middle platform (Base), as well as intelligent analysis platform (AI), visualization platform (Vis), and industrial map service (Services).

[0086] S220: When creating a target map task, read the task link configuration of the target map task;

[0087] In some implementations, if the task link configuration of the target map task is stored in a link flow configuration table or any other location, the server can read the task link configuration of the target map task from the link flow configuration table or any other location.

[0088] It should be understood that, since the task link configuration of the target map task needs to be used when creating the target map task, the server can read the task link configuration of the target map task when creating the target map task.

[0089] S230: After the target map task is created, if the historical task link flowchart includes various operation links of the target map task, the target map task is executed based on the historical task link flowchart and the task link configuration of the target map task.

[0090] It should be understood that the historical mission link flowchart refers to the mission link flowchart used before the target map mission.

[0091] It should be understood that since similar map tasks may exist in different map production lines, the task link flowcharts corresponding to these similar map tasks are also similar, or for the same map task, the map tasks before and after modification are also similar, and the task link flowcharts corresponding to the two are also similar. And usually the task link flowchart is as comprehensive as possible. For example, the task link flowchart includes three batch operations in the pre-job link, the mid-job link, and the post-job link: batch z value, lane centerline, and batch guide strip. As for which batch operations are used in each link, it can be determined in combination with the task link configuration. Based on this, for the target map task, the server can first determine whether the historical task link flowchart includes all the operation links of the target map task. If the historical task link flowchart includes all the links of the target map task, then the target map task is executed based on the historical task link flowchart and the task link configuration of the target map task.

[0092] For example, Figure 3 A partial schematic diagram of a task link flow chart provided in an embodiment of the present application, such as Figure 3 As shown, there is a judgment operation before each batch processing operation in the pre-job stage, the job stage, and after the quality inspection submission.

[0093] Specifically, if before_step_288=1, then the batch z value operation of the pre-job link is executed; if before_step_288=0, then the batch z value operation of the pre-job link is not executed; if before_step_281=1, then the lane centerline batch processing operation of the pre-job link is executed; if before_step_281=0, then the lane centerline batch processing operation of the pre-job link is not executed; if before_step_290=1, then the batch guide belt operation of the pre-job link is executed; if before_step_290=0, then the batch guide belt operation of the pre-job link is not executed.

[0094] If middle_step_288=1, then the batch z value operation of the link in the job is executed; if middle_step_288=0, then the batch z value operation of the link in the job is not executed; if middle_step_281=1, then the lane centerline batch processing operation of the link in the job is executed; if middle_step_281=0, then the lane centerline batch processing operation of the link in the job is not executed; if middle_step_290=1, then the batch guide belt operation of the link in the job is executed; if middle_step_290=0, then the batch guide belt operation of the link in the job is not executed.

[0095] If after_step_288=1, then the batch z value operation of the link after quality inspection submission is executed; if after_step_288=0, then the batch z value operation of the link after quality inspection submission is not executed; if after_step_281=1, then the lane center line batch processing operation of the link after quality inspection submission is executed; if after_step_281=0, then the lane center line batch processing operation of the link after quality inspection submission is not executed; if after_step_290=1, then the batch guide belt operation of the link after quality inspection submission is executed; if after_step_290=0, then the batch guide belt operation of the link after quality inspection submission is not executed.

[0096] Assume that a new map task is added to the map production line P_0719. The task link configuration of this task is shown in Table 1. It is also assumed that the task link flowchart includes all the operation links of the task. Based on this, when executing the task based on the task link configuration and the task link flowchart, the batch z value and lane center line can be performed in the pre-operation stage, the batch z value and batch guide strip can be performed in the operation stage, and the lane center line and batch guide strip can be performed in the post-quality inspection stage.

[0097] It should be noted that in related technologies, when a new map task is added or a map task is modified, the historical task flow chart needs to be modified for the following reasons: Figure 4 This is a partial diagram of a task process flow chart. Before adding a map task of the map production line P_0719, the task process flow chart is as follows: Figure 4 As shown, a judgment operation is performed before each batch operation in the pre-operation phase, the operation phase, and the quality inspection submission phase. The judgment operation is as follows: for any batch operation in any operation phase, if the current production line code is in the list of production line codes for executing the batch operation, the batch operation is executed; if the current production line code is not in the list of production line codes for executing the batch operation, the batch operation is not executed.

[0098] Specifically, for the pre-operation link, the production line code list corresponding to the batch z value includes: {P_0711, P_0712, P_0713}, the production line code list corresponding to the lane center line includes: {P_0711, P_0712}, and the production line code list corresponding to the batch guide belt includes: {P_0711, P_0713}.

[0099] For the operation link, the production line code list corresponding to the batch z value includes: {P_0711, P_0712}, the production line code list corresponding to the lane center line includes: {P_0711, P_0712, P_0713}, and the production line code list corresponding to the batch guide belt includes: {P_0711, P_0713}.

[0100] For the post-quality inspection submission stage, the production line coding list corresponding to the batch z value includes: {P_0712, P_0713}, the production line coding list corresponding to the lane center line includes: {P_0711, P_0712, P_0713}, and the production line coding list corresponding to the batch guide belt includes: {P_0711, P_0713}.

[0101] Assume that a new map task for map production line P_0719 is added. For this map task, batch z value and lane centerline need to be processed before operation, batch z value and batch guide strip need to be processed during operation, and lane centerline and batch guide strip need to be processed after quality inspection submission. Based on this, the server needs to be modified. Figure 4 The corresponding task link flow chart, the partial schematic diagram of the modified task link flow chart is as follows Figure 5 As shown, Figure 5As shown, for the pre-operation link, the production line code list corresponding to the batch z value includes: {P_0711, P_0712, P_0713, P_0719}, the production line code list corresponding to the lane center line includes: {P_0711, P_0712, P_0719}, and the production line code list corresponding to the batch guide belt includes: {P_0711, P_0713}.

[0102] For the operation links, the production line code list corresponding to the batch z value includes: {P_0711, P_0712, P_0719}, the production line code list corresponding to the lane center line includes: {P_0711, P_0712, P_0713}, and the production line code list corresponding to the batch guide belt includes: {P_0711, P_0713, P_0719}.

[0103] For the post-quality inspection submission stage, the production line code list corresponding to the batch z value includes: {P_0712, P_0713}, the production line code list corresponding to the lane center line includes: {P_0711, P_0712, P_0713, P_0719}, and the production line code list corresponding to the batch guide belt includes: {P_0711, P_0713, P_0719}.

[0104] An embodiment of the present application provides a map task processing method, comprising: creating a task link configuration for a target map task; reading the task link configuration for the target map task when creating the target map task; and after the target map task is created, if a historical task link flowchart includes each operation link of the target map task, executing the target map task based on the historical task link flowchart and the task link configuration for the target map task. Because the historical task link flowchart does not need to be modified when it includes each operation link of the target map task, the historical task link flowchart can be directly used, thereby improving map task execution efficiency.

[0105] From another perspective, since the task execution code corresponds to the task link flowchart, if the server does not need to modify the historical task link flowchart, it does not need to modify the task execution code. Instead, it can directly use the historical task execution code, thereby improving the efficiency of map task execution.

[0106] It should be understood that the map task processing method provided in the embodiment of the present application supports map tasks with newly added map services and changes in task links, so as to realize the execution of such map tasks, or the link flow of such map tasks, without modifying the historical task link flowchart and task execution code.

[0107] In some possible implementations, after the target map task is created, if the historical task link flowchart does not include at least one operation link of the target map task, the server can update the historical task link flowchart; and execute the target map task based on the updated historical task link flowchart and the task link configuration of the target map task.

[0108] For example, suppose the partial diagram of the historical task process flow chart is as follows Figure 3 As shown in the figure, suppose a new map task of map production line P_0718 is added. The task link configuration of this map task is shown in Table 2:

[0109] Table 2

[0110]

[0111] Among them, 288 represents the batch operation: batch z value, 281 represents the batch operation: lane center line, 290 represents the batch operation: batch guide strip, and 280 represents the batch operation: batch traffic light.

[0112] As shown in Table 2, due to Figure 3 The partial diagram of the task flow chart does not include the batch signal light operation in the pre-operation phase of the map production line P_0718. Based on this, the server needs to be modified. Figure 3 The partial schematic diagram of the task link flow chart shown in FIG. 1 and the partial schematic diagram of the modified task link flow chart are as follows: Figure 6 As shown, Figure 6 and Figure 3 The difference is: Figure 6 Batch processing operations are added to each task link: batch signal light, where if before_step_280=1, the batch signal light operation of the pre-job link is executed; if before_step_280=0, the batch signal light operation of the pre-job link is not executed; if middle_step_280=1, the batch signal light operation of the mid-job link is executed; if middle_step_280=0, the batch signal light operation of the mid-job link is not executed; if after_step_280=1, the batch signal light operation of the post-quality inspection submission link is executed; if after_step_280=0, the batch signal light operation of the post-quality inspection submission link is not executed.

[0113] In an embodiment of the present application, if the historical task link flowchart does not include at least one operation link of the target map task, the server can update the historical task link flowchart; and execute the target map task based on the updated historical task link flowchart and the task link configuration of the target map task, wherein this embodiment is different from Figure 2The corresponding embodiments complement each other, that is, form a supplementary solution, thereby improving the reliability of map task execution.

[0114] In some possible implementations, the server may also synchronize the information in the basic information table of the target map task to the task master table of the target map task; and retrieve the target map task based on the task master table of the target map task.

[0115] In some implementations, the basic information table of the target map task may include, but is not limited to: a basic information table of collected data, a basic information table of tasks, a task link table, a task status table, a task attribute table, an operation link attribute table, and the like.

[0116] It should be understood that the collected data basic information table is used to store collected data.

[0117] For example, in map road operations, the basic information table of collected data (t_intelligence_basic) corresponding to a task may include, but is not limited to: the identification (Identity, ID) of the basic information table of collected data, the number of collected data (intelligence_number), the task number of the task (task_number), the priority of collected data (intelligence_priority), the production line code (prodution_line_code), the collection data code list (intelligence_code_list), the collection data code (intelligence_code), the data identification (data_id), the data source (data_source), the source of collected data (intelligence_from), province (province), city (city), province code (province_code), city code (city_code), the name of collected data (intelligence_name), extended field (payload), creation time (create_time), validity period (depth), type (type), and whether it is automated (is_auto).

[0118] Among them, the basic information table of collected data only supports insert and query operations, and does not support modification operations. For extended fields, since they store sparse information, they can be stored in JSONB format.

[0119] It should be understood that the task basic information table is used to store basic information of tasks.

[0120] For example, the task basic table (t_task_basic) may include, but is not limited to: the identifier (ID) of the task basic table, the task number (task_number) of the task, the task stage instance identifier (process_instance_id), the task type (type), the extended field (payload), the creation time (create_time), and whether it is automated (is_auto).

[0121] The task basic information table supports insert and query operations, but does not support modification operations.

[0122] It should be understood that the task link table is used to store data of each link of the task.

[0123] For example, the task link table (t_task_step) of a task includes, but is not limited to: the identifier (ID) of the task link table, the task link number (work_number), the task number (task_number) of the task, the task link type (type), the task link (step), the link execution identifier (step_execution ID), the link creation time (step_create_time), the link creator (step_create_by), the link version (step_version), the current status (current_status), and the creation time of the current status (current_status_create_time).

[0124] When the data in the task link table changes version, a new version number can be inserted, and the task status table trigger can be used to detect the insert operation in the task link table and write the current state of the inserted new version number into the task status table. For example, suppose the task link table stores a task step and its corresponding version: version 1.0. When the version of the task step in the task link table is upgraded to version 2.0, version 2.0 can be inserted into the task link table. At the same time, after detecting the insert operation in the task link table, the task status table trigger can write the current state into the task status table.

[0125] It should be understood that the task status table is used to store task status information.

[0126] For example, the task status table (t_task_status) may include, but is not limited to: the identifier (ID) of the task status table, the task link number (work_number), the status (status), the status creation time (status_create_time), the status creator (status_create_by), the status version (status_version), and the task number (task_number) of the task.

[0127] The trigger of the task status table can be used to detect the insertion operation of other basic information packages, and the current state of the inserted data is stored in the task status table. The task status table does not support active modification operations.

[0128] It should be understood that the task attribute table is used to store basic attribute information of the task.

[0129] For example, the task attribute table (t_task_attribute) of a task may include, but is not limited to: the identifier (ID) of the task attribute table, the task number (task_number) of the task, the task priority (task_priority), the green channel (green_channel), the return type (send_back_type), the return remark (send_back_memo), the version (version), the supplementary field (supplement), the automation success mark (success_log_mark), the automation failure mark (failed_log_mark), the automation unmarked (undo_log_mark), the outsourcer (edit_outsourcer), the status (statistical) outsourcer success mark (success_auto_mark), outsourcer failure mark (failed_auto_mark), outsourcer unmarked (undo_auto_mark), and the editing operator (edit_operator).

[0130] It should be understood that the operation link attribute table is used to store basic attribute information of the operation link of the task.

[0131] For example, the work link attribute table (t_work_attribute) of a task may include, but is not limited to: the identifier (ID) of the work link attribute table, the task link (i.e., work link) number (work_number), the operator (operator), the latest operator (last_operator), the outsourcer (outsourcer), the version (version), and the task number (task_number) of the task.

[0132] It should be understood that the task master table is used to store the latest basic information of the task.

[0133] For example, Figure 7 A data synchronization diagram provided in an embodiment of the present application is shown in FIG. Figure 7 As shown in the table, if the data in the basic information table of collected data is automated (is_auto) and the production line code (prodution_line_code) are updated, they will be synchronized to the task master table; if the ID (ID), task number (task_number), extended field (payload), task stage instance ID (process_instance_id), and task type (type) in the basic information table of task are updated, they will be synchronized to the task master table; if the task link number (work_number), task link type (type), task link (step), and execution ID (Execution ID) in the task link table are updated, they will be synchronized to the task master table. Any updates to the task master table include: ID), step creation time (step_create_time), step creator (step_create_by), and step version (step_version); updates to the status (status), status creator (status_create_by), and status version (status_version) in the task status table; updates to the task priority (task_priority) in the task attribute table; and updates to the operator (operator), latest operator (last_operator), and outsourcer (outsourcer) in the job step attribute table. Additionally, the task master table may include the creation time (create_time) and update time (update_time) of the task master table.

[0134] Among them, the task master table does not support active modification operations, and the insertion, update, and deletion of its internal information are completely dependent on the triggers of the basic information table.

[0135] In some implementations, the server may synchronize the information in the basic information table of the target map task to the task master table of the target map task in real time based on a trigger of the basic information table of the target map task.

[0136] For example, when a new production line code is inserted into the basic information table of collected data, when the trigger of the basic information table of collected data is triggered, the server can synchronize the production line code to the task master table of the target map task in real time. Specifically, the production line code stored in the task master table can be updated to the new production line code, or the server can delete the production line code stored in the task master table and insert the new production line code.

[0137] It's important to note that the information stored in the task master table is considered a basic information table. For example, a basic information table might store basic information about a task for up to a year, while the task master table might store basic information about the same task for up to a month. In other words, the amount of data in the task master table is kept relatively small, improving task retrieval efficiency.

[0138] In some implementations, the server may delete the information in the task master table after executing the target map task.

[0139] In some implementations, after the server deletes the information in the task master table, the server may receive a retrieval request for the target map task; and in response to the retrieval request, retrieve the target map task based on the basic information table of the target map task.

[0140] It should be understood that the basic information table of the target map task can store information for a longer time range, and when the information in the task master table is deleted, the server can retrieve the target map task based on the basic information table of the target map task.

[0141] In some implementations, the server may also migrate information in the basic information table of the target map task that is more than a preset time away from the current time to the data warehouse.

[0142] Among them, the information in the basic information table of the target map task that is more than a preset time away from the current time can be called cold data. This data can be backed up in the data warehouse. If the server receives a retrieval request for a historical task, it can first search for the historical task based on the basic information table of the target map task. If the retrieval fails, the server can search for the historical task in the data warehouse. Conversely, the information in the basic information table of the target map task that is less than a preset time away from the current time can be called hot data and does not need to be backed up in the data warehouse.

[0143] For example, Figure 8 A schematic diagram of hot and cold data separation provided in an embodiment of the present application is shown as follows: Figure 8As shown, the cloud database stores the basic information table and task master table for each task, among which the basic information table includes: data collection basic information table, task basic information table, task link table, task status table, task attribute table, operation link attribute table, etc. The information in these tables can be synchronized to the task master table. For hot data, it can continue to be stored in the basic information table, and for cold data, it can be backed up to the data warehouse.

[0144] In this embodiment of the present application, the server can also synchronize the information in the basic information table of the target map task with the task master table of the target map task. Based on the task master table of the target map task, the target map task is searched, so that the task master table always stores the latest data, thereby ensuring the accuracy of task retrieval. In addition, because the amount of data in the task master table is always kept within a relatively small range, the efficiency of task retrieval can be improved.

[0145] Furthermore, even if the information in the task master table is deleted, the server can still perform task retrieval in other basic tables or data warehouses, thereby ensuring the reliability of task retrieval.

[0146] In some implementations, the server may further create a task state machine for the target map task; and execute state transition of the target map task based on the task state machine for the target map task.

[0147] For example, Figure 9 A state transition diagram provided in an embodiment of the present application is shown as follows: Figure 9 As shown in the figure, the first step is to create a task link. At this time, the task enters the unassigned state, status = 0; when the operator receives the task, the task enters the assigned state, status = 1; when the operator starts the work, the task enters the working state, status = 2; when the operator does not work for a long time, the task enters the suspended state, status = 3; when the operator starts the work again, the task enters the working state again, status = 2; when the task is completed, the operator will submit the task, and the task enters the completed state, status = 4.

[0148] It should be understood that the task state machine defines transition information, which refers to relevant information describing transitions between states in the state machine. The transition information may include: a starting state, a target state, a state transition triggering event, and a transition action.

[0149] Among them, the source state is the starting state of the conversion, which indicates the state of the current object or system.

[0150] The target state is the target state of the conversion, indicating the state to which the current object or system will be converted.

[0151] The state transition trigger event (Trigger Event) is an event that triggers a state transition, which may be an external input event, an internal condition being met, or an event with other specific conditions.

[0152] Among them, the transition action is the action or logic executed when the state transition occurs, which is used to process the business logic during the state transition process.

[0153] For example, the conversion information can be as follows:

[0154] newTransitionInfo<>(TaskStatus.DOING,TaskStatus.DONE,BranchEvent.COMMIT,commit);

[0155] The transition information includes the starting state being DOING, indicating the ongoing state; the target state being DONE, indicating the completed state; the state transition triggering event being COMMIT, i.e., the commit event; and the transition action being commit, i.e., the commit action.

[0156] The transition information indicates that the task is in the in-progress state in the current job link. When a job link submission event occurs in the link, the task transitions from the in-progress state to the completed state in the current job link.

[0157] It should be understood that the implementation of state transitions by the task state machine in the present embodiment has the following advantages:

[0158] First, a clear description of the task flow: The task state machine provides a structured way to describe the task states and the transition rules between states. By defining different states and transition rules, the task execution flow can be clearly described, making the code easier to understand and maintain.

[0159] Second, flexible task flow control: The task state machine makes the task execution process more flexible. By defining different states and transition rules, the task execution process can be customized according to specific needs. The next action can be determined based on the current state and conditions of the task, achieving flexible task flow control.

[0160] Third, scalability and maintainability: Using a task state machine improves code scalability and maintainability. By defining different states and transition rules, new states and transitions can be easily added without significantly impacting existing code. This makes the task state machine an effective tool for handling complex tasks.

[0161] Fourth, error handling and fault tolerance: Task state machines provide robust error handling and fault tolerance mechanisms. By defining appropriate states and transition rules, exceptions during task execution can be captured and handled. Task state machines can help developers better handle errors and implement actions such as rollbacks and retries.

[0162] Fifth, visualization and debugging: The structured representation of the task state machine makes the task execution process easier to visualize and debug. Graphical tools or state diagrams can be used to display the task state machine, helping developers better understand and debug the task execution process.

[0163] In some implementations, when the target map task is converted to a completed state in the current operation link, the server can also transfer the target map task backward.

[0164] It should be understood that the so-called backward flow refers to the transfer of the target map task from the current operation link to the next operation link.

[0165] In some possible implementations, when the target map task enters the completion state, the server can publish a job submission event and detect the job submission event through an event trigger. Once the job submission event is detected, the server can call the completion function to complete the current job link of the target map task and transfer the target map task backward.

[0166] In some implementations, the completion function may be a complete function in weflow, but is not limited thereto.

[0167] In some implementations, the server may further determine tasks that are in a completed state and have not been forwarded; if the tasks that are in a completed state and have not been forwarded include a target map task, the target map task is forwarded backward.

[0168] In other words, this implementable method provides a fallback strategy for task transfer, that is, if the target map task is still in a completed state and there are no tasks transferred backward, the server can transfer the target map task backward again.

[0169] In some implementations, the server may call a completion function to forward the target map task.

[0170] In some implementations, the server can regularly scan all tasks to determine tasks that are in a completed state and have not been transferred backwards. For example, the server can scan all tasks once every morning at 10:00 to determine tasks that are in a completed state and have not been transferred backwards.

[0171] In some implementations, the server may scan all tasks under event triggering to determine tasks that are in a completed state and have not been forwarded. For example, after receiving a scan instruction, the server may scan all tasks to determine tasks that are in a completed state and have not been forwarded.

[0172] In the embodiment of the present application, the backward flow of the target map task can be guaranteed by the backup strategy of task flow, thereby ensuring the reliability of the backward flow.

[0173] In some implementations, the server may also perform log reporting of target map tasks based on the cut point and surround notifications.

[0174] In some implementations, the server may count the amount of information inserted into the basic information table of the target map task based on the cut point and the surrounding notification; and report the amount of information inserted into the basic information table of the target map task.

[0175] For example, the server inserts 100 pieces of information into the task basic information table of the target map task reported based on the tangent point and surround notification within 10 minutes.

[0176] The following uses the target map task basic information table as an example to illustrate log reporting based on tangent points and surround notifications:

[0177] 1. The server can define a log aspect class LogAspect. Aspect is a modular way of cross-cutting concerns. It can span multiple objects and methods and provide a mechanism for centrally handling cross-cutting concerns in the application.

[0178] 2. The server can define a pointcut, which is a notification that applies the aspect to a specified method. For example, if a join point matching the insertSelective() method in the TaskBasicEntityMapper interface is specified, that join point is used as the pointcut. The expression is as follows:

[0179] @Pointcut("execution(*com.tencent.pms.dao.mapper.TaskBasicEntityMapper.insertSelective(..))")

[0180] public void taskBasicInsertSelectivePointcut(){}

[0181] The meaning of this pointcut expression is to match the insertSelective() method in the TaskBasicEntityMapper interface under the com.tencent.pms.dao.mapper package with any return type, and the method parameters can be of any type and quantity.

[0182] 3. The server can define around advice, which can execute corresponding logic before and after the pointcut and control the execution of the pointcut.

[0183] @Around("taskBasicInsertSelectivePointcut()")

[0184] public Object taskBasicInsertAround(ProceedingJoinPoint point){}

[0185] The @Around annotation is applied to the pointcut named taskBasicInsertSelectivePointcut() . This means that the around advice will execute around the pointcut matched by taskBasicInsertSelectivePointcut() . In the around advice, you can execute logic before the pointcut, such as logging, specifically reporting the amount of inserted information. Then, you can execute the pointcut method by calling joinPoint.proceed() . Finally, you can execute logic after the pointcut returns normally or throws an exception, such as logging, specifically reporting the amount of inserted information.

[0186] It should be understood that the implementation of log reporting through point-cut and surround notification in the present embodiment has the following advantages:

[0187] First, business logic and cross-cutting concerns can be decoupled. The use of pointcuts and around advice can decouple cross-cutting concerns (such as logging, transaction management, etc.) from business logic.

[0188] Second, it enables code reuse and maintainability. Multiple methods or code blocks can share the same pointcut and around advice, avoiding the need to rewrite the same logic. This way, when a cross-cutting concern needs to be modified or extended, only the aspect logic needs to be modified, without modifying the business logic.

[0189] Third, using pointcuts and around advice allows for flexible control over the timing and execution logic of cross-cutting concerns. Based on specific needs, you can execute specific logic before or after method execution, or when an exception is thrown. This allows you to customize the behavior of cross-cutting concerns to suit different scenarios and requirements.

[0190] From a product perspective, the map task processing method provided in the embodiment of the present application can be applied to a production management system (PMS).

[0191] For example, Figure 10 A data processing diagram provided in an embodiment of the present application is as follows: Figure 10 As shown, in map road operations, the data processing process includes: data collection, data preprocessing, map production, map output and map application.

[0192] Among them, data collection methods may include: self-collection of data, equipment crowdsourcing and manual crowdsourcing, but are not limited to these.

[0193] Among them, PMS is responsible for map production. The front-end APP corresponding to the PMS system can be used to obtain user editing operations, generate editing instructions based on these editing operations, and send editing instructions to the back-end server corresponding to the PMS system to realize map production.

[0194] Furthermore, all output maps can be stored in the master database, while the latest version of the map can be stored in the product database. When performing navigation, base map or search applications, maps can be obtained from the master database or product database to implement corresponding map applications.

[0195] Figure 11 A PMS operation flow chart provided in the embodiment of this application is as follows: Figure 11 As shown in the figure, the PMS operation process is mainly divided into three stages, including: data preparation stage, data operation stage and data writing stage.

[0196] The data preparation stage includes: distributing data in a scattered manner, creating task surfaces, applying for small databases, and pulling small databases.

[0197] The data operation stage includes: internal production, product inspection, internal inspection, and quality inspection.

[0198] The data writing phase includes: applying for a differential database, loading the differential database, differential analysis of the database, and writing the differential results to the database.

[0199] Specifically, during the data preparation phase, PMS can distribute tasks with the same operating scope in a scattered manner to control the order in which these tasks are distributed. For the current task, first create the task surface, then apply for the small library, and pull the small library. During the data operation phase, PMS performs internal production for the created task surface, that is, map production. After production, product inspection can be performed, that is, automated map inspection. Furthermore, manual internal inspection and quality inspection (that is, external inspection) can be used. Finally, the inspected map is returned to the library and locked, that is, the inspected map is stored in the small library. Furthermore, PMS can apply for and load a differential small library, in which the data in the small library and the mother library for the same map area are differentially processed to obtain the differential result, and the differential result is written into the mother library. Finally, the small library is released to end.

[0200] Figure 12 A PMS architecture diagram is provided in the embodiment of the present application, such as Figure 12 As shown, the PMS system is divided into a client, access layer, detection layer, service layer, middleware, basic services, and continuous integration (CI) tools. It should be understood that the client can be a terminal device that includes a map editing app, which can be, but is not limited to, Wemap. The access layer, detection layer, service layer, middleware, basic services, and CI tools are located on the backend server corresponding to the PMS system.

[0201] Among them, the client can access various service modules in the PMS system through the access layer, such as Figure 12 As shown, the access layer may include: a routing proxy component, which can route requests received from the client to different service modules according to the configuration to achieve reverse proxy and load balancing. Among them, the routing proxy component also provides many security functions, such as access control, prevention of malicious requests, prevention of distributed denial of service (DDoS) attacks, etc.

[0202] The service layer deploys the core services of PMS, including eight microservices: service agent module, data collection service module, operation service module, configuration service module, inspection service module, small library service module, data access service module, and scattering service module.

[0203] Figure 13 The functional diagram of each service module provided in the embodiment of the present application is as follows: Figure 13 As shown in the figure, the functions of each service module are as follows:

[0204] Among them, the service proxy module is responsible for forwarding the request interface, forwarding Kafka messages, and providing adaptation of the external access interface.

[0205] The data collection service module is responsible for receiving upstream data, creating production management tasks, recording basic task information and starting task processes.

[0206] The job service module is responsible for task collection, allocation, suspension, submission, etc.

[0207] The configuration service module is responsible for providing dynamic configuration, production line management and management platform related configuration for each service.

[0208] The inspection service module is responsible for providing an inspection interface for post-job tasks.

[0209] The small library service module is responsible for upstream and downstream interactive services such as creating task pages, applying for small libraries, pulling small libraries, differentiating small libraries, and returning small libraries.

[0210] The data access service module is responsible for database access services.

[0211] The dispatching service module is responsible for controlling the dispatching of tasks, reducing task overlap, reducing conflicts in returning to the warehouse, and improving operational efficiency.

[0212] like Figure 12 As shown, the detection tools may include: detection and visualization tools, and instant messaging client detection tools.

[0213] The detection and visualization tool can detect various indicators and logs by configuring data sources, creating dashboards, and setting alarms, and can display and analyze data in an intuitive way. This tool can be the Grafana detection tool.

[0214] The IM client detection tool can integrate most middleware alerts from cloud components. When a middleware anomaly occurs, the alert information can be sent to the IM client, allowing developers to quickly respond to the issue. The IM client can be, but is not limited to, WeChat for Business, WeChat, QQ, etc.

[0215] like Figure 12 As shown, basic services may include: a process engine and a program service deployment container.

[0216] Among them, the process engine is responsible for the flow and scheduling of tasks. The process engine can be a process engine developed based on Flowable, which can be a Weflow engine.

[0217] like Figure 12 As shown, CI continuous integration tools may include: WorkBee and BlueShield.

[0218] Among them, WorkerBee is a git code management tool, and BlueShield is a pipeline deployment tool.

[0219] like Figure 12As shown, the middleware may include: distributed coordination service components, storage components, log management and analysis components, distributed message queue service components, cloud function components, log retrieval, analysis and visualization components, log collection components, etc.

[0220] The distributed coordination service component provides a highly available, high-performance distributed environment for coordinating and managing various tasks and configuration information in the distributed system. The distributed coordination service component may be Zookeeper, but is not limited thereto.

[0221] The storage component may include: a component for storing all information in the data production process, such as task information, configuration information, user information, etc., a component for storing files, a cache component for providing data cache, session storage, message queue, etc. The cache component may be Redis, but is not limited to this.

[0222] Log management and analysis components can help users collect, store, retrieve, and analyze large-scale log data to better understand and utilize the data.

[0223] The distributed message queue service component is a highly reliable and high-throughput distributed message queue service. It provides reliable message delivery and real-time data stream processing capabilities for upstream and downstream service communications.

[0224] Cloud Function components allow you to write and deploy code in the form of functions without having to worry about the underlying servers and infrastructure.

[0225] The log retrieval, analysis, and visualization component is responsible for log retrieval and data analysis and visualization.

[0226] The log collection component is responsible for log collection and is used in conjunction with a search engine, which may be ElasticSearch (ES).

[0227] Figure 14 A task processing process flow chart provided for an embodiment of the present application should be understood to be executed by the backend server corresponding to the PMS system. It should be noted that before executing the task processing process, R&D personnel can build the PMS infrastructure, including: first, building a CI tool for automated building, testing, and deploying code. Then, it is necessary to establish an access layer for processing user requests and routing. At the same time, it is also necessary to configure detection tools, various service modules, middleware, basic services, etc. in the service layer. The task processing process includes:

[0228] S1410: Obtain basic data and related configurations, and access upstream and downstream services;

[0229] In some implementations, the basic data may include, but is not limited to: project information, user information, etc., but is not limited thereto.

[0230] In some implementations, the relevant configurations may include, but are not limited to: creating tables such as projects, tasks, users, and permissions, as well as relationships and constraints between these configurations.

[0231] In some implementations, the upstream and downstream services are services that require the use of PMS to output data. For example, the upstream and downstream services may be small library tasks.

[0232] In some implementations, backend servers can define appropriate interfaces and protocols to enable upstream and downstream service access, ensuring accurate and consistent data delivery. This involves API design and data format specifications. Related configurations, such as authentication and authorization, and data synchronization, are also required to ensure secure and reliable communication between systems.

[0233] S1420: Obtain an initial task link flow chart, and perform process flow configuration on the task link flow chart to obtain a final task link flow chart;

[0234] In some implementations, the initial task link flow chart may be a user-drawn task link flow chart, which does not include any configurations, such as judgment conditions, etc. The process flow configuration is used to define and manage specific task link processes, such as adding judgment conditions, etc.

[0235] S1430: Create task;

[0236] S1440: According to the task link flow chart of the task, call the relevant interface to process the task, and / or receive the operation instructions performed by the operator according to the task link flow chart of the task to process the task.

[0237] In some implementations, tasks are processed by calling relevant interfaces, including data validation, conversion, calculation, and other operations. Through the flow of tasks and interface calls, data can be gradually processed and the final result generated. This ensures that tasks are carried out according to the predetermined process.

[0238] In some implementations, when an operator performs a task, the operations performed include: receiving a task, performing a task, submitting a task, etc. These operations may result in a change in the task status.

[0239] Operators can select a pending task from the task list. Once a task is accepted, its status changes from "Pending" to "Accepted," indicating that the task has been accepted and processing has begun. After accepting the task, operators will perform the work according to the task requirements. During the work process, operators can pause the work, etc. Upon completion, the operator submits their work results. The task status will be updated accordingly, and the task status will change to "Completed."

[0240] It should be noted that the backend server also performs tasks monitoring, querying, statistics, and archiving, enabling comprehensive task management and monitoring. The task monitoring function allows managers to monitor task status, progress, and execution in real time. This helps identify problems and take appropriate measures to ensure timely task completion. The task query function allows users to search and query tasks based on various conditions and criteria. The task statistics function provides task statistics and analysis, such as the number of tasks, completion rate, and delays.

[0241] It should be noted that the task link configuration of the target map creation task provided in the embodiment of the present application can be performed after the process flow configuration, or can be performed simultaneously with the process flow configuration, but is not limited to this.

[0242] In the embodiment of the present application, the task link configuration based on the historical task link flowchart and the target map task executes the target map task, which can be executed in S1440, but is not limited thereto.

[0243] In the embodiment of the present application, synchronizing the information in the basic information table of the target map task to the task master table of the target map task can be performed after S1430, but is not limited thereto.

[0244] The process of performing task state conversion based on the task state machine provided in the embodiment of the present application can be executed after S1430, but is not limited thereto.

[0245] The log reporting of the target map task based on the cut point and surrounding notification provided in the embodiment of the present application can be performed after S1430, but is not limited thereto.

[0246] The information in the task master table of the target map task provided in the embodiment of the present application can be deleted after the task is archived, but is not limited to this.

[0247] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, a variety of simple modifications can be made to the technical solution of the present application, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner unless there is any contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, and as long as they do not violate the ideas of the present application, they should also be regarded as the contents disclosed in the present application.

[0248] It should also be understood that in the various method embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0249] The above describes the method provided in the embodiment of the present application. The following describes the task processing device provided in the embodiment of the present application.

[0250] Figure 15 A schematic diagram of a map task processing device 1500 provided in an embodiment of the present application is shown as follows: Figure 15 As shown, the device 1500 includes: a processing module 1510, which is used to: create a task link configuration of the target map task; when creating the target map task, read the task link configuration of the target map task; wherein, the task link configuration includes: the production line code of the map production line to which the target map task belongs, the link code of each operation link of the target map task and the parameter configuration of each operation link; after the target map task is created, if the historical task link flowchart includes each operation link of the target map task, then the target map task is executed based on the historical task link flowchart and the task link configuration of the target map task.

[0251] In some implementations, the processing module 1510 is also used to: after creating the target map task, if the historical task link flowchart does not include at least one operation link of the target map task, update the historical task link flowchart; and execute the target map task based on the updated historical task link flowchart and the task link configuration of the target map task.

[0252] In some implementations, the processing module 1510 is further used to: synchronize the information in the basic information table of the target map task to the task master table of the target map task; and retrieve the target map task based on the task master table of the target map task.

[0253] In some implementations, the processing module 1510 is specifically configured to synchronize the information in the basic information table of the target map task to the task master table of the target map task in real time based on a trigger of the basic information table of the target map task.

[0254] In some implementations, the processing module 1510 is further configured to delete the information in the task master table after the target map task is executed.

[0255] In some implementations, the device 1500 also includes: a communication module 1520, which is used to receive a retrieval request for the target map task after the processing module 1510 deletes the information in the task master table; the processing module 1510 is also used to: in response to the retrieval request, retrieve the target map task based on the basic information table of the target map task.

[0256] In some implementations, the processing module 1510 is further configured to: migrate information in the basic information table of the target map task that is more than a preset time away from the current time to the data warehouse.

[0257] In some implementations, the processing module 1510 is further configured to: create a task state machine for the target map task; and execute state transition of the target map task based on the task state machine for the target map task.

[0258] In some implementations, the processing module 1510 is further configured to: when the target map task is converted to a completed state in the current operation link, transfer the target map task backward.

[0259] In some implementations, the processing module 1510 is further used to: determine tasks that are in a completed state and have not been transferred backward; if the tasks that are in a completed state and have not been transferred backward include a target map task, then transfer the target map task backward.

[0260] In some implementations, the processing module 1510 is specifically configured to periodically scan all tasks to determine tasks that are in a completed state and have not been forwarded.

[0261] In some implementations, the processing module 1510 is further configured to: perform log reporting of the target map task based on the cut point and the surround notification.

[0262] In some implementations, the processing module 1510 is specifically used to: count the amount of inserted information in the basic information table of the target map task based on the tangent point and the surrounding notification; and report the amount of inserted information in the basic information table of the target map task.

[0263] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Figure 15 The apparatus 1500 shown may perform Figure 2 The corresponding method embodiments, and the aforementioned and other operations and / or functions of each module in the apparatus 1500 are respectively to implement Figure 2 For the sake of brevity, the corresponding processes in each method are not repeated here.

[0264] The above describes the device 1500 of the embodiment of the present application from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps in the above method embodiment in conjunction with its hardware.

[0265] Figure 16 It is a schematic block diagram of the server 1600 provided in an embodiment of the present application.

[0266] Reference Figure 16 The server 1600 includes a processor 1610 , a memory 1620 , a network interface 1630 , an input / output interface 1640 , and a power supply component 1650 .

[0267] The processor 1610 may include, but is not limited to, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.

[0268] Memory 1620 includes, but is not limited to, volatile memory and / or nonvolatile memory. Nonvolatile memory may include ROM, PROM, EPROM, electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include RAM, which serves as an external cache. By way of example and not limitation, many forms of RAM are available, such as SRAM, DRAM, SDRAM, DDR SDRAM, ESDRAM, SLDRAM, and DR RAM.

[0269] The memory 1620 is used to store instructions, such as applications, that can be executed by the processor 1610. The applications stored in the memory 1032 may include one or more modules, each of which corresponds to a set of instructions.

[0270] The server 1600 may be configured with a wired or wireless network interface 1630 to enable the server 1600 to connect to a network.

[0271] The server 1600 may be configured with one or more input / output interfaces 1640 for connecting to other input devices, such as a keyboard, a mouse, and the like.

[0272] The power supply component 1650 can be logically connected to the processor 1610 through a power management system, so that the power management system can manage charging, discharging, power consumption and other functions.

[0273] It should be understood that the various components in the server are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0274] It should be understood that the server may execute Figure 2 The content and effects of the corresponding method embodiments will not be described in detail here.

[0275] The present application also provides a computer storage medium having a computer program stored thereon, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment. In other words, the present application also provides a computer program product containing instructions, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment.

[0276] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)).

[0277] Those skilled in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0278] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules is merely a logical function division. In actual implementation, there may be other division methods, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0279] Modules described as separate components may or may not be physically separate, and components displayed as modules may or may not be physical modules, i.e., they may be located in one place or distributed across multiple network elements. Some or all of the modules may be selected based on actual needs to achieve the purpose of the present embodiment. For example, the functional modules in the various embodiments of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into a single module.

[0280] The above content is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A map task processing method, characterized in that: include: Creating a task link configuration for a target map task; wherein the task link configuration includes: a production line code of the map production line to which the target map task belongs, link codes of each operation link of the target map task, and parameter configurations of each operation link; When creating the target map task, reading the task link configuration of the target map task; After the target map task is created, if the historical task link flowchart includes each operation link of the target map task, the target map task is executed based on the historical task link flowchart and the task link configuration of the target map task.

2. The method according to claim 1, characterized in that Also includes: After the target map task is created, if the historical task link flow chart does not include at least one operation link of the target map task, updating the historical task link flow chart; Based on the updated historical task link flow chart and the task link configuration of the target map task, the target map task is executed.

3. The method according to claim 1 or 2, characterized in that Also includes: Synchronize the information in the basic information table of the target map task to the task master table of the target map task; The target map task is retrieved based on the task master table of the target map task.

4. The method according to claim 3, characterized in that The step of synchronizing the information in the basic information table of the target map task to the task master table of the target map task includes: Based on the trigger of the basic information table of the target map task, the information in the basic information table of the target map task is synchronized in real time to the task master table of the target map task.

5. The method according to claim 3, characterized in that Also includes: After the target map task is executed, the information in the task master table is deleted.

6. The method according to claim 5, characterized in that After deleting the information in the task master table, the method further includes: receiving a search request for the target map task; In response to the retrieval request, the target map task is retrieved based on the basic information table of the target map task.

7. The method according to claim 3, characterized in that Also includes: The information in the basic information table of the target map task that is more than a preset time away from the current time is migrated to the data warehouse.

8. The method according to claim 1 or 2, characterized in that Also includes: Create a task state machine for the target map task; Based on the task state machine of the target map task, the state transition of the target map task is executed.

9. The method according to claim 8, characterized in that Also includes: When the target map task is converted to a completed state in the current operation link, the target map task is transferred backward.

10. The method according to claim 9, characterized in that Also includes: Identify tasks that are in a completed state and have not been transferred backwards; If it is in the completed state and the tasks that have not been transferred backward include the target map task, the target map task will be transferred backward.

11. The method according to claim 10, characterized in that The tasks that are determined to be completed and not transferred backward include: Scan all tasks regularly to determine which tasks are completed and have not been transferred backwards.

12. The method according to claim 1 or 2, characterized in that Also includes: The log of the target map task is reported based on the cut point and the surrounding notification.

13. The method according to claim 12, characterized in that The log reporting of the target map task based on the cut point and surround notification includes: Based on the tangent point and surrounding notifications, count the amount of inserted information in the basic information table of the target map task; Report the amount of information inserted into the basic information table of the target map task.

14. A map task processing device, characterized in that: include: Processing module for: Creating a task link configuration for a target map task; wherein the task link configuration includes: a production line code of the map production line to which the target map task belongs, link codes of each operation link of the target map task, and parameter configurations of each operation link; When creating the target map task, reading the task link configuration of the target map task; After the target map task is created, if the historical task link flowchart includes each operation link of the target map task, the target map task is executed based on the historical task link flowchart and the task link configuration of the target map task.

15. An electronic device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 13.

16. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 13.

17. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 13 is implemented.

Images