Map data collection control method, device, equipment, medium and program product

Abstract

This application provides a map data acquisition control method, apparatus, device, medium, and program product. The method involves: acquiring a data acquisition task; selecting at least one object model corresponding to a data acquisition terminal from an object model library based on the task; using the object model to determine a common task instruction set for all data acquisition terminals based on the data acquisition task; and sending the instruction set to each data acquisition terminal, enabling each terminal to parse the task instruction set according to its stored object model, generate control instructions specific to the terminal, and acquire map data according to these instructions. By using the object model as a conversion medium for control instructions, the method eliminates the technical problem of differences in control methods between the task management end and different data acquisition terminals, building upon the original control programs of various acquisition devices.

Description

Technical Field

[0001] This application relates to the field of digital positioning technology, and in particular to a map data acquisition and control method, device, equipment, medium, and program product. Background Technology

[0002] With the continuous development of automotive technology, intelligent driving or autonomous driving is a recognized direction for automotive technology development. Both intelligent driving and autonomous driving rely on the pre-collection of rich and accurate map data, and require continuous updating and maintenance of this map data.

[0003] Currently, there are many ways to collect map data, such as using professional data collection vehicles and crowdsourcing. Ultimately, the map data collected through these different methods is aggregated to form a high-precision digital map. However, because the data collection equipment used in different methods inevitably differs, and the control methods for these devices also vary greatly, existing technologies require different task instructions to be issued for different data collection methods when each data collection task is published. This significantly increases the workload for task publishers.

[0004] Therefore, how to eliminate the differences in control methods between the task management terminal and various data acquisition terminals, simplify the release of data acquisition tasks, and retain the original control program of the acquisition device has become an urgent technical problem to be solved. Summary of the Invention

[0005] This application provides a map data acquisition control method, apparatus, device, medium, and program product to solve the technical problem of how to eliminate the differences in control methods between the task management terminal and various different data acquisition terminals, simplify the release of data acquisition tasks, and retain the original control program of the acquisition equipment.

[0006] Firstly, this application provides a map data acquisition control method, comprising:

[0007] Data acquisition tasks;

[0008] Based on the data acquisition task, at least one object model corresponding to the data acquisition terminal is selected from the object model library. The object model is a digital representation of the various attributes and functions of the data acquisition terminal.

[0009] Using the object model, a set of common task instructions for each data acquisition terminal is determined based on the data acquisition task;

[0010] The system sends task instruction sets to each data acquisition terminal, enabling each terminal to parse the task instruction sets based on its stored object model, generate control instructions specific to the data acquisition terminal, and collect map data according to the control instructions.

[0011] In one possible design, using an object model, a set of task instructions common to all data acquisition terminals is determined based on the data acquisition task, including:

[0012] Based on the data acquisition task, assign values ​​to the attribute parameters of the object model and the service parameters of the data acquisition service;

[0013] The set of task instructions applicable to each data acquisition terminal is determined based on the assigned attribute parameters and service parameters.

[0014] In one possible design, the attribute parameters include: basic information of the data acquisition task and various configuration parameters of the data acquisition terminal; the service parameters include: task triggering rules and data acquisition method.

[0015] Data acquisition tasks include:

[0016] Analyze the data acquisition task to determine basic information, task triggering rules, and data acquisition methods;

[0017] Based on the data acquisition task, assign values ​​to the attribute parameters of the object model and the service parameters of the data acquisition service, including:

[0018] Assign the values ​​of the first parameter corresponding to the basic information to the attribute parameters corresponding to each object model;

[0019] Assign the values ​​of the second parameters corresponding to the task triggering rules and data collection methods to the service parameters corresponding to each object model.

[0020] In one possible design, the data acquisition method includes: image acquisition, video acquisition, and structured data acquisition based on positioning data and / or motion data from the data acquisition terminal, performed at preset distance intervals or preset time intervals.

[0021] In one possible design, after parsing the data acquisition task, the following is also included:

[0022] Determine whether the data acquisition task includes acquisition rules and / or return rules;

[0023] If so, the parameter values ​​corresponding to the acquisition rules and / or feedback rules will be assigned to the corresponding attribute parameters in the object model.

[0024] In one possible design, based on the data acquisition task, values ​​are assigned to the attribute parameters of the object model and the service parameters of the data acquisition service, including:

[0025] Generate a digital twin of the object model based on the template file corresponding to the object model in the object model library;

[0026] Based on the parameter values ​​in the data acquisition task, assign corresponding values ​​to the attribute parameters and service parameters in the digital twin.

[0027] Secondly, this application provides a map data acquisition and control device, comprising:

[0028] The acquisition module is used to acquire data collection tasks;

[0029] The task parsing module is used to select at least one object model corresponding to the data acquisition terminal from the object model library according to the data acquisition task. The object model is a digital representation of the various attributes and functions of the data acquisition terminal.

[0030] The instruction processing module is used to determine a set of general task instructions for each data acquisition terminal based on the object model and the data acquisition task.

[0031] The sending module is used to send task instruction sets to each data acquisition terminal, so that each data acquisition terminal can parse the task instruction set according to its own stored object model, generate control instructions specific to the data acquisition terminal, and collect map data according to the control instructions.

[0032] In one possible design, the instruction processing module is used for:

[0033] Based on the data acquisition task, assign values ​​to the attribute parameters of the object model and the service parameters of the data acquisition service;

[0034] The task instruction set is determined based on the assigned attribute and service parameters.

[0035] In one possible design, the attribute parameters include: basic information of the data acquisition task and various configuration parameters of the data acquisition terminal; the service parameters include: task triggering rules and data acquisition method.

[0036] Correspondingly, the task parsing module is used for:

[0037] Analyze the data acquisition task to determine basic information, task triggering rules, and data acquisition methods;

[0038] Assign the values ​​of the first parameter corresponding to the basic information to the attribute parameters corresponding to each object model;

[0039] Assign the values ​​of the second parameters corresponding to the task triggering rules and data collection methods to the service parameters corresponding to each object model.

[0040] In one possible design, the data acquisition method includes: image acquisition, video acquisition, and structured data acquisition based on positioning data and / or motion data from the data acquisition terminal, performed at preset distance intervals or preset time intervals.

[0041] In one possible design, the task parsing module is also used to determine whether the data acquisition task includes acquisition rules and / or return rules.

[0042] If so, the instruction processing module is also used to assign the parameter values ​​corresponding to the acquisition rules and / or feedback rules to the corresponding attribute parameters in the object model.

[0043] In one possible design, the instruction processing module is used for:

[0044] Generate a digital twin of the object model based on the template file corresponding to the object model in the object model library;

[0045] Based on the parameter values ​​in the data acquisition task, assign corresponding values ​​to the attribute parameters and service parameters in the digital twin.

[0046] Thirdly, this application provides an electronic device, comprising:

[0047] Memory, used to store program instructions;

[0048] The processor is used to call and execute program instructions in the memory to perform any of the possible map data acquisition control methods provided in the first aspect.

[0049] Fourthly, this application provides a storage medium storing a computer program for executing any of the possible map data acquisition control methods provided in the first aspect.

[0050] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements any of the possible map data acquisition and control system methods provided in the first aspect.

[0051] This application provides a map data acquisition control method, apparatus, device, medium, and program product. The method involves: acquiring a data acquisition task; selecting at least one object model corresponding to a data acquisition terminal from an object model library based on the task; using the object model to determine a common task instruction set for all data acquisition terminals based on the data acquisition task; sending the instruction set to each data acquisition terminal, enabling each terminal to parse the task instruction set according to its stored object model, generate control instructions specific to the terminal, and acquire map data according to these instructions. By using the object model as a conversion medium for control instructions, the method eliminates the differences in control methods between the task management terminal and various data acquisition terminals, simplifies the issuance of data acquisition tasks, and achieves the technical effect of preserving the original control programs of various acquisition devices while unifying and simplifying the control methods of various acquisition devices. Attached Figure Description

[0052] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0053] Figure 1 A schematic diagram of the structure of a map data acquisition and control system in the prior art provided in this application;

[0054] Figure 2 A schematic diagram of an improved map data acquisition and control system provided in this application;

[0055] Figure 3 A flowchart illustrating a map data acquisition and control method provided in an embodiment of this application;

[0056] Figure 4 A flowchart illustrating another map data acquisition and control method provided for the implementation of this application;

[0057] Figure 5 This is a schematic diagram of the structure of a map data acquisition and control device provided in an embodiment of this application;

[0058] Figure 6 This is a schematic diagram of the structure of an electronic device provided in this application.

[0059] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort, including but not limited to combinations of multiple embodiments, are within the scope of protection of this application.

[0061] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0062] To facilitate understanding, the following is an explanation and introduction of the technical terms used in this application:

[0063] Object Model: An object model describes the capabilities and characteristics of a device. It consists of attributes, events, and services, encapsulating data and capabilities. It describes what the device is, what it can do, and what information it can provide. The object model also represents a reusable and replaceable component formed after decoupling a complex system. By defining the object model, it is clear that the device can report attribute and event information, and the server can issue commands to set attributes and invoke services.

[0064] Digital twin: A digital twin is used to store the online status of a device, the device's most recently reported device attribute values, and the configurations that the application server expects to send. Each device has one and only one digital twin. The device can obtain and set the digital twin to synchronize device attribute values. This synchronization can be done by the digital twin synchronizing with the device, or by the device synchronizing with the digital twin.

[0065] Data acquisition and control function object model abstraction: The acquisition task issuance is abstracted into an "acquisition task issuance" service, and the task triggering rules are abstracted into service parameters; the acquisition rules are abstracted into device attributes (such as longitude, latitude, etc.).

[0066] Data backhaul control function object model abstraction: Abstract the data backhaul control into device attributes (such as upload switch, cache days, etc.).

[0067] The following explains the reasons that triggered the inventors' inventive concept for this application:

[0068] Autonomous driving map data collection can be categorized into two types based on the collecting entity: map data collection by specialized collection vehicles and map data collection by crowdsourced vehicles. Specialized collection vehicles typically utilize specially modified or customized vehicles equipped with comprehensive professional data collection equipment to collect data on all roads in a single instance, organized by administrative region. However, due to limitations in cost and quantity, real-time map data collection and updates are not possible. In contrast, crowdsourced vehicle-based map data collection effectively complements specialized collection vehicles. It targets specific road segments and areas, collecting road data in a task-oriented manner, enabling real-time data collection and map updates.

[0069] Map data collection by crowdsourced vehicles can be divided into: self-organized crowdsourced map data collection and third-party crowdsourced map data collection.

[0070] Autonomous crowdsourced map data collection involves the data center purchasing ordinary vehicles and installing a certain number of data collection devices on them. However, these devices are not as comprehensive or complete as those in professional data collection vehicles. The data center then assigns dedicated personnel to perform the map collection. Autonomous crowdsourced map data collection is generally carried out according to specific task assignments, primarily to supplement data collection on road sections that third-party crowdsourced vehicles cannot complete, and to collect high-priority road section data.

[0071] Third-party crowdsourced map data collection typically involves installing data collection devices on third-party operated vehicles (such as taxis, ride-sharing services, and private cars from online rental platforms). While driving, the data is automatically collected when the vehicle passes through the designated data collection area (based on a pre-issued data collection task from the management system). Third-party crowdsourced map data collection vehicles rely entirely on the equipment in the driver's vehicle. The type, model, and supplier of the data collection equipment vary significantly depending on the vehicle model, but certain common characteristics exist.

[0072] Therefore, how to use a unified data acquisition task management system to collect and control data from various types, brands, and models of devices, that is, how to eliminate the differences in control methods between the task management end and various data acquisition ends, simplify the release of data acquisition tasks, and retain the original control programs of the acquisition devices, has become an urgent technical problem to be solved.

[0073] To solve the above-mentioned technical problems, the inventive concept of this application is as follows:

[0074] A cloud server is added between the task issuing end and the data acquisition terminal. Both the cloud server and the data acquisition terminal have corresponding object models. These object models eliminate the discrepancies between the control commands of the task issuing end and the control programs of the data acquisition terminal. This changes the traditional one-to-one task issuing mechanism (one control command corresponding to one data acquisition device) to a one-to-many mechanism (one unified control command corresponding to multiple different data acquisition devices), simplifying data acquisition and feedback control.

[0075] The following section details how this application enables the transmission of information through touch.

[0076] Figure 1 A schematic diagram of the structure of a map data acquisition and control system in the prior art provided in this application. (See diagram for example.) Figure 1 As shown, in the prior art, the map data acquisition and control system sends control commands corresponding to the type of data acquisition terminal 20 to each data acquisition terminal 20 via the task management terminal 10, such as... Figure 1 The control commands 1, 2, ..., n in the terminal control each data acquisition terminal to perform various types of map data acquisition tasks and receive data of various formats from different data acquisition terminals. After the task management terminal 10 corrects and integrates the data, the data format and type are uniformly processed and summarized to obtain a high-precision map.

[0077] Figure 2 A schematic diagram of an improved map data acquisition and control system provided in this application. Figure 2 As shown, the improved map data acquisition and control system adds a cloud server 30 between the task management terminal 10 and the data acquisition terminal 20. The cloud server 30 stores the object models corresponding to each data acquisition terminal 20: object model 31, object model 32, ..., object model 3n. Each data acquisition terminal 20 also stores its corresponding object model. Data center staff input the data acquisition task to be published into the task management terminal 10, which then publishes the task to the cloud server 30. The cloud server 30 parses the data acquisition task, calls one or more corresponding object models to generate a universal control instruction set applicable to all data acquisition terminals, and then sends it uniformly to each data acquisition terminal 20. Upon receiving the universal control instruction set, the data acquisition terminal 20 calls its own stored object model to convert the universal control instruction set into its own control instructions to complete the data acquisition task.

[0078] It should be noted that the object models in the data acquisition terminal 20 and the cloud server 30 need to be consistent. When the file corresponding to the object model is modified on either end, it will be synchronized with the other end immediately after the modification is completed to ensure the consistency of the object model between the two.

[0079] Figure 3 This is a flowchart illustrating a map data acquisition and control method provided in an embodiment of this application. Figure 3 As shown, the specific steps of this map data acquisition and control method include:

[0080] S301, Data Acquisition Task.

[0081] In this step, the task management terminal 10 generates one or more data acquisition tasks and publishes them to the cloud service terminal 30. Each data acquisition task includes five parts: a task description (basic information such as unified task identification code, task publisher, task priority, etc.), task triggering rules, data acquisition action type (data acquisition method such as single-frame image capture, multi-frame video capture, GPS positioning structured data acquisition, etc.), data acquisition rules, and data return rules. It is understandable that one or more of these five parts may be empty; for example, some data acquisition tasks may not have acquisition rules and data return rules set. Instead, a separate data acquisition task is published after a period of time, and acquisition rules or data return rules are set separately to avoid data congestion in the cloud or task management terminal caused by large-scale simultaneous data return.

[0082] S302. Based on the data acquisition task, select at least one object model corresponding to the data acquisition terminal from the object model library.

[0083] In this step, the object model is a digital representation of the various attributes and functions corresponding to the data acquisition terminal. The object model can include four parts: basic elements, attributes, services, and events.

[0084] The basic elements include: static information such as the object model's identification code, name, description, type, version, and tags.

[0085] Attributes: Used to describe the runtime state of the object model, and can consist of values ​​of different types, such as: string (character type), int (integer type), float (floating-point type), array (array type), struct (structure type), and comlink (sub-component type).

[0086] Service: Defines a list of methods supported by the object model. It describes multiple service capabilities or methods that can be accessed externally by the object model, and can set input parameters, output parameters, synchronous or asynchronous operation, etc.

[0087] Events: A list of events used to define the parameters of an object model. Events generally include notification information that needs to be perceived and processed externally, and may contain multiple output parameters. From its source, an event can be understood as something generated by one or more components and that has already occurred in the past.

[0088] Specifically, after receiving the data acquisition task through the data interface, the cloud server 30 parses the data acquisition task, extracts basic information, task triggering rules, and data acquisition methods, and then selects the corresponding object model from the object model library according to the data acquisition method.

[0089] S303. Using the object model, determine the set of task instructions that are common to each data acquisition terminal according to the data acquisition task.

[0090] In this step, the attribute parameters of the object model and the service parameters of the data acquisition service are assigned values ​​according to the data acquisition task; and the common task instruction set for each data acquisition terminal is determined based on the assigned attribute parameters and service parameters.

[0091] In this embodiment, the attribute parameters include: basic information of the data acquisition task and various configuration parameters of the data acquisition terminal, and the service parameters include: task triggering rules and data acquisition methods.

[0092] Specifically, based on the task triggering rules and data acquisition methods in the data acquisition task, values ​​are assigned to the parameters of the corresponding service in the object model, and then a corresponding task instruction set is generated through the instruction protocol. This task instruction set is a unified communication instruction that is consistent across various service terminals or various object models.

[0093] S304. Send task instruction sets to each data acquisition terminal.

[0094] In this step, the cloud server 30 packages and encapsulates the task instruction set and sends it to each data acquisition terminal via wireless transmission, such as 4G / 5G / Internet. It should be noted that the data acquisition terminals can be mounted on various types of vehicles, including: professional data acquisition vehicles, data center self-owned vehicles, and third-party operated vehicles. Optionally, the data acquisition terminals can also be mounted in fixed-location base stations.

[0095] After receiving the task instruction set, each data acquisition terminal parses the task instruction set according to its own stored object model, generates control instructions specific to the data acquisition terminal, and collects map data according to the control instructions.

[0096] For example, after receiving the task instruction set data from the object model module of the cloud server 30, the object model module in the data acquisition terminal 20 parses it into instructions corresponding to the respective data acquisition devices according to their object model definitions. It then sends the acquisition task instructions and acquisition control parameter setting instructions to the acquisition module, and sends the return control parameter setting instructions back to the return module. Upon receiving the acquisition task instructions, the acquisition module updates the acquisition task in the data acquisition terminal 20, including the acquisition task description (basic information), task triggering rules, and data acquisition actions (data acquisition method). Based on the task triggering rules, the data acquisition terminal 20 triggers the data acquisition task, executes data acquisition according to the acquisition control parameters, and sends the acquired data to the return module. The return module uploads the data to the cloud server 30 based on the data return control parameters. Finally, the cloud server 30 sends the data back to the task management terminal 10, completing the data acquisition process.

[0097] It should be noted that using object models can produce the following beneficial effects:

[0098] By abstracting and defining the object model of the acquisition devices, it can simultaneously support data acquisition and feedback control for acquisition devices of different brands, types, and models. Based on the object model, users do not need to worry about the differences between devices and can use a unified operation interface to manage, distribute, acquire, and control the data acquisition tasks. When adding acquisition devices of different types and models, the cloud server only needs to add the object model file of that device to realize data acquisition and feedback control for that acquisition device, greatly reducing development workload and deployment time.

[0099] This embodiment provides a map data acquisition and control system method. The method involves: acquiring a data acquisition task; selecting at least one object model corresponding to a data acquisition terminal from an object model library based on the task; the object model being a digital representation of the various attributes and functions of the data acquisition terminal; using the object model, determining a common task instruction set applicable to all data acquisition terminals based on the data acquisition task; and sending the instruction set to each data acquisition terminal, enabling each terminal to parse the task instruction set according to its stored object model, generate control instructions specific to the terminal, and acquire map data according to these instructions. By using the object model as a conversion medium for control instructions, the method eliminates the differences in control methods between the task management terminal and various data acquisition terminals, simplifies the issuance of data acquisition tasks, and achieves the technical effect of preserving the original control programs of various acquisition devices while unifying and simplifying the control methods of these devices.

[0100] Figure 4 A flowchart illustrating another map data acquisition and control method provided for the implementation of this application. (See attached diagram.) Figure 4As shown, the specific steps of this map data acquisition and control method include:

[0101] S401, Obtain data collection task.

[0102] In this step, each data acquisition task includes five parts: a task description (basic information such as task unified identification code, task publisher, task priority, etc.), task triggering rules, data acquisition action type (data acquisition method such as single-frame image capture, multi-frame video capture, GPS positioning structured data acquisition, etc.), data acquisition rules, and data feedback rules. It's understandable that one or more of these five parts may be empty; for example, some data acquisition tasks may not have acquisition rules and data feedback rules set. Instead, a separate data acquisition task is issued after a period of time, and acquisition rules or data feedback rules are set separately to avoid data congestion in the cloud or task management terminal caused by large-scale simultaneous data feedback.

[0103] In this embodiment, the task management terminal 10 generates one or more data acquisition tasks and sends them to the acquisition task distribution module of the cloud server terminal 30.

[0104] S402, Analyze the data acquisition task.

[0105] In this step, according to the preset communication protocol, the information contained in the data acquisition task is parsed, including: basic information, task triggering rules and data acquisition method.

[0106] Data acquisition methods include: image acquisition, video acquisition, and structured data acquisition based on positioning data and / or motion data from data acquisition terminals, performed at preset distance intervals or preset time intervals.

[0107] In this embodiment, the data acquisition task distribution module calls the data acquisition task distribution interface exposed by the shadow service of the cloud server 30 to decompose and parse the data acquisition task. It then sends the basic information, task triggering rules, and data acquisition method to the data acquisition control service of the cloud server 30.

[0108] S403. Based on the data acquisition task, select at least one object model corresponding to the data acquisition terminal from the object model library.

[0109] In this step, the object model is a digital representation of the various attributes and functions of the data acquisition terminal.

[0110] In this embodiment, based on the data acquisition method in the data acquisition task, the corresponding object model is selected from the object model library, and each object model corresponds to a type of data acquisition terminal device.

[0111] Specifically, the data acquisition control service automatically matches and maps the data acquisition task to the object model based on the action type, i.e., the data acquisition method, automatically selects the corresponding object model "data acquisition task issuance" service, and generates corresponding service parameters by generating the task description and task triggering rules, and generates the acquisition task issuance instruction.

[0112] S404. Determine whether the data acquisition task includes acquisition rules and / or return rules.

[0113] In this step, when parsing the data acquisition task in S402, if the information parsed includes acquisition rules and / or feedback rules, then step S405 is executed; otherwise, step S406 is executed.

[0114] Specifically, the cloud server 30's data collection task distribution module determines whether the data collection task includes collection rules and return rules. If so, it sends the collection rules and return rules to the attribute setting module.

[0115] S405. Assign the parameter values ​​corresponding to the acquisition rules and / or feedback rules to the corresponding attribute parameters in the object model.

[0116] S406. Assign the values ​​of the first parameters corresponding to the basic information to the attribute parameters corresponding to each object model.

[0117] S407. Assign the values ​​of the second parameters corresponding to the task triggering rules and data acquisition methods to the service parameters corresponding to each object model.

[0118] In steps S405 to S407, the specific assignment methods include:

[0119] Generate a digital twin of the object model based on the template file corresponding to the object model in the object model library;

[0120] Based on the parameter values ​​in the data acquisition task, assign corresponding values ​​to the attribute parameters and service parameters in the digital twin.

[0121] Specifically, in the attribute setting module, the data feedback rules are matched with the object model attributes, and the feedback rule values ​​from the data acquisition task are assigned to the feedback control attributes in the object model and sent to the digital twin. Upon receiving the feedback control attribute value settings, the digital twin updates the attribute values ​​in the digital twin module and generates data feedback control parameter setting instructions.

[0122] In the attribute setting module, data acquisition rules are matched with object model attributes, and the acquisition rule values ​​from the data acquisition task are assigned to the acquisition control attributes in the object model and sent to the digital twin. Upon receiving the acquisition control attribute value settings, the digital twin updates the corresponding attribute values ​​in the digital twin module and generates data acquisition control parameter setting instructions.

[0123] Then, the data acquisition task distribution module of cloud server 30 packages the data acquisition control parameter setting instructions, data return control parameter settings, and acquisition task distribution instructions into a single instruction set and sends it to the object model module of the cloud server. The object model module encapsulates the instruction set according to the object model protocol, preparing it for distribution.

[0124] S408: Send task instruction sets to each data acquisition terminal.

[0125] In this step, the cloud server 30 packages and encapsulates the task instruction set and sends it to each data acquisition terminal via wireless transmission, such as 4G / 5G / Internet. It should be noted that the data acquisition terminals can be mounted on various types of vehicles, including: professional data acquisition vehicles, data center self-owned vehicles, and third-party operated vehicles. Optionally, the data acquisition terminals can also be mounted in fixed-location base stations.

[0126] After receiving the task instruction set, each data acquisition terminal parses the task instruction set according to its own stored object model, generates control instructions specific to the data acquisition terminal, and collects map data according to the control instructions.

[0127] For example, after receiving the task instruction set data from the object model module of the cloud server 30, the object model module in the data acquisition terminal 20 parses it into instructions corresponding to the respective data acquisition devices according to their object model definitions. It then sends the acquisition task instructions and acquisition control parameter setting instructions to the acquisition module, and sends the return control parameter setting instructions back to the return module. Upon receiving the acquisition task instructions, the acquisition module updates the acquisition task in the data acquisition terminal 20, including the acquisition task description (basic information), task triggering rules, and data acquisition actions (data acquisition method). Based on the task triggering rules, the data acquisition terminal 20 triggers the data acquisition task, executes data acquisition according to the acquisition control parameters, and sends the acquired data to the return module. The return module uploads the data to the cloud server 30 based on the data return control parameters. Finally, the cloud server 30 sends the data back to the task management terminal 10, completing the data acquisition process.

[0128] It should be noted that using object models can produce the following beneficial effects:

[0129] By abstracting and defining the object model of the acquisition devices, it can simultaneously support data acquisition and feedback control for acquisition devices of different brands, types, and models. Based on the object model, users do not need to worry about the differences between devices and can use a unified operation interface to manage, distribute, acquire, and control the data acquisition tasks. When adding acquisition devices of different types and models, the cloud server only needs to add the object model file of that device to realize data acquisition and feedback control for that acquisition device, greatly reducing development workload and deployment time.

[0130] This embodiment provides a map data acquisition and control system method. The method involves: acquiring a data acquisition task; selecting at least one object model corresponding to a data acquisition terminal from an object model library based on the task; the object model being a digital representation of the various attributes and functions of the data acquisition terminal; using the object model, determining a common task instruction set applicable to all data acquisition terminals based on the data acquisition task; and sending the instruction set to each data acquisition terminal, enabling each terminal to parse the task instruction set according to its stored object model, generate control instructions specific to the terminal, and acquire map data according to these instructions. By using the object model as a conversion medium for control instructions, the method eliminates the differences in control methods between the task management terminal and various data acquisition terminals, simplifies the issuance of data acquisition tasks, and achieves the technical effect of preserving the original control programs of various acquisition devices while unifying and simplifying the control methods of these devices.

[0131] Figure 5 This is a schematic diagram of a map data acquisition and control device provided in an embodiment of this application. The map data acquisition and control device 500 can be implemented through software, hardware, or a combination of both.

[0132] like Figure 5 As shown, the map data acquisition and control device 500 includes:

[0133] Module 501 is used to acquire data collection tasks;

[0134] The task parsing module 502 is used to select at least one object model corresponding to the data acquisition terminal from the object model library according to the data acquisition task. The object model is a digital representation of the various attributes and functions of the data acquisition terminal.

[0135] The instruction processing module 503 is used to determine a set of general task instructions for each data acquisition terminal based on the data acquisition task using the object model.

[0136] The sending module 504 is used to send instruction sets to each data acquisition terminal, so that each data acquisition terminal can parse the task instruction set according to its own stored object model, generate control instructions specific to the data acquisition terminal, and collect map data according to the control instructions.

[0137] In one possible design, the instruction processing module 503 is used for:

[0138] Based on the data acquisition task, assign values ​​to the attribute parameters of the object model and the service parameters of the data acquisition service;

[0139] The task instruction set is determined based on the assigned attribute and service parameters.

[0140] In one possible design, the attribute parameters include: basic information of the data acquisition task and various configuration parameters of the data acquisition terminal; the service parameters include: task triggering rules and data acquisition method.

[0141] Correspondingly, task parsing module 502 is used for:

[0142] Analyze the data acquisition task to determine basic information, task triggering rules, and data acquisition methods;

[0143] Assign the values ​​of the first parameter corresponding to the basic information to the attribute parameters corresponding to each object model;

[0144] Assign the values ​​of the second parameters corresponding to the task triggering rules and data collection methods to the service parameters corresponding to each object model.

[0145] In one possible design, the data acquisition method includes: image acquisition, video acquisition, and structured data acquisition based on positioning data and / or motion data from the data acquisition terminal, performed at preset distance intervals or preset time intervals.

[0146] In one possible design, the task parsing module 502 is also used to determine whether the data acquisition task includes acquisition rules and / or return rules.

[0147] If so, the instruction processing module 503 is also used to assign the parameter values ​​corresponding to the acquisition rules and / or feedback rules to the corresponding attribute parameters in the object model.

[0148] In one possible design, the instruction processing module 503 is used for:

[0149] Generate a digital twin of the object model based on the template file corresponding to the object model in the object model library;

[0150] Based on the parameter values ​​in the data acquisition task, assign corresponding values ​​to the attribute parameters and service parameters in the digital twin.

[0151] It is worth noting that, Figure 5 The apparatus provided in the illustrated embodiments can execute the methods provided in any of the above method embodiments. Their specific implementation principles, technical features, explanations of technical terms, and technical effects are similar and will not be repeated here.

[0152] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 600 may include at least one processor 601 and a memory 602. Figure 6 The example shown is an electronic device using a processor.

[0153] The memory 602 is used to store programs. Specifically, the program may include program code, which includes computer operation instructions.

[0154] The memory 602 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0155] The processor 601 is used to execute computer execution instructions stored in the memory 602 to implement the methods described in the above embodiments.

[0156] The processor 601 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0157] Optionally, the memory 602 can be either standalone or integrated with the processor 601. When the memory 602 is a device independent of the processor 601, the electronic device 600 may further include:

[0158] Bus 603 is used to connect the processor 601 and the memory 602. The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not mean there is only one bus or one type of bus.

[0159] Optionally, in a specific implementation, if the memory 602 and the processor 601 are integrated on a single chip, the memory 602 and the processor 601 can communicate through an internal interface.

[0160] This application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a disk, or an optical disk. Specifically, the computer-readable storage medium stores program instructions, which are used in the methods described in the above-mentioned method embodiments.

[0161] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods described in the above-described method embodiments.

[0162] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

[0163] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A map data acquisition and control method, characterized in that, include: Data acquisition tasks; According to the data acquisition task, at least one object model corresponding to the data acquisition terminal is selected from the object model library. The object model is a digital representation of the various attributes and functions of the data acquisition terminal. According to the data acquisition task, the attribute parameters of the object model and the service parameters of the data acquisition service are assigned values; The set of common task instructions for each data acquisition terminal is determined based on the assigned attribute and service parameters. The attribute parameters include: basic information of the data acquisition task and various configuration parameters of the data acquisition terminal; the service parameters include: task triggering rules and data acquisition methods. Based on the task triggering rules and data acquisition methods in the data acquisition task, the parameters of the service corresponding to data acquisition are assigned in the object model, and the corresponding task instruction set is generated through the instruction protocol. The task instruction set is sent to each of the data acquisition terminals, so that each data acquisition terminal can parse the task instruction set according to the object model stored in its own memory, generate control instructions specific to the data acquisition terminal, and collect map data according to the control instructions.

2. The map data acquisition and control method according to claim 1, characterized in that, The data acquisition task includes: The data acquisition task is analyzed to determine the basic information, the task triggering rules, and the data acquisition method. The step of assigning values ​​to the attribute parameters of the object model and the service parameters of the data acquisition service according to the data acquisition task includes: Assign the values ​​of the first parameters corresponding to the basic information to the attribute parameters; Assign the values ​​of the second parameters corresponding to the task triggering rules and the data collection methods to the respective service parameters.

3. The map data acquisition and control method according to claim 2, characterized in that, The data acquisition methods include: image acquisition, video acquisition, and structured data acquisition based on positioning data and / or motion data from the data acquisition terminal, performed at preset distance intervals or preset time intervals.

4. The map data acquisition and control method according to claim 2, characterized in that, After parsing the data acquisition task, the following is also included: Determine whether the data acquisition task includes acquisition rules and / or return rules; If so, the parameter values ​​corresponding to the acquisition rule and / or the feedback rule are assigned to the corresponding attribute parameters in the object model.

5. The map data acquisition and control method according to claim 2, characterized in that, The step of assigning values ​​to the attribute parameters of the object model and the service parameters of the data acquisition service according to the data acquisition task includes: Generate a digital twin of the object model based on the template file corresponding to the object model in the object model library; Based on the parameter values ​​in the data acquisition task, assign corresponding values ​​to the attribute parameters and service parameters in the digital twin.

6. A map data acquisition and control device, characterized in that, include: The acquisition module is used to acquire data collection tasks; The task parsing module is used to select at least one object model corresponding to the data acquisition terminal from the object model library according to the data acquisition task. The object model is a digital representation of the various attributes and functions of the data acquisition terminal. The instruction processing module is used to assign values ​​to the attribute parameters of the object model and the service parameters of the data acquisition service according to the data acquisition task; and to determine the common task instruction set for each data acquisition terminal based on the assigned attribute parameters and service parameters. The attribute parameters include: basic information of the data acquisition task and various configuration parameters of the data acquisition terminal; the service parameters include: task triggering rules and data acquisition method; according to the task triggering rules and data acquisition method in the data acquisition task, the parameters of the service corresponding to data acquisition are assigned in the object model, and the corresponding task instruction set is generated through the instruction protocol; The sending module is used to send the task instruction set to each of the data acquisition terminals, so that each of the data acquisition terminals can parse the task instruction set according to the object model stored in its own memory, generate control instructions specific to the data acquisition terminal, and collect map data according to the control instructions.

7. An electronic device, characterized in that, include: processor; as well as, Memory for storing the computer program of the processor; The processor is configured to execute the map data acquisition control method according to any one of claims 1 to 5 by executing the computer program.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the map data acquisition and control method according to any one of claims 1 to 5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the map data acquisition and control method according to any one of claims 1 to 5.

Images