Method and apparatus for data management

Abstract

According to embodiments of the present disclosure, methods and apparatuses for data management are provided. The method includes presenting a data management interface, the data management interface including a map component; in response to receiving a fence creation request, determining a plurality of area units corresponding to a fence to be created; configuring, via a configuration window corresponding to the fence, a parking attribute of the plurality of area units; and rendering a set of elements corresponding to the fence in the map component, wherein a style of the set of elements is determined based on the parking attribute. In this way, embodiments of the present disclosure can improve the accuracy of autonomous vehicle parking behavior by utilizing area units to manage parking areas.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to methods, apparatus, devices, computer-readable storage media, and computer program products for data management. Background Technology

[0002] With the rapid development of computer processing power, research on autonomous vehicles has received widespread attention. Autonomous vehicle systems can be divided into perception systems and decision-making systems. Localization is the core of the perception system, and the quality of vehicle localization directly affects subsequent planning and control. The decision-making system is responsible for planning a drivable route after acquiring localization and other perception information.

[0003] Regarding location tracking, autonomous vehicles can determine road segment information, such as parking availability. Furthermore, they can plan their subsequent driving routes based on this parking availability information. Therefore, a more convenient management method is needed for parking availability information to ensure autonomous vehicles park in suitable locations. Summary of the Invention

[0004] In a first aspect of this disclosure, a method for data management is provided. The method includes: presenting a data management interface, the data management interface including a map component; in response to receiving a fence creation request, determining multiple area units corresponding to the fence to be created; configuring docking attributes of the multiple area units via a configuration window corresponding to the fence; and drawing a set of elements corresponding to the fence in the map component, wherein the style of the set of elements is determined based on the docking attributes.

[0005] In a second aspect of this disclosure, an apparatus for data management is provided. The apparatus includes: a management interface presentation module configured to present a data management interface, the data management interface including a map component; a region unit determination module configured to determine multiple region units corresponding to a fence to be created in response to receiving a fence creation request; a docking attribute configuration module configured to configure docking attributes of the multiple region units via a configuration window corresponding to the fence; and an element drawing module configured to draw a set of elements corresponding to the fence in the map component, wherein the style of the set of elements is determined based on the docking attributes.

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

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program that can be executed by a processor to implement the method of the first aspect.

[0008] In a fifth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions that, when executed by a processor, implement the method of the first aspect.

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

[0010] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0011] Figure 1 A schematic diagram of an example environment in which embodiments of the present disclosure can be implemented is shown;

[0012] Figures 2A to 2E A schematic diagram of an example interface for data management according to some embodiments of the present disclosure is shown;

[0013] Figure 2F A schematic diagram of an example architecture for docking attribute inheritance between map versions is shown, according to some embodiments of the present disclosure;

[0014] Figures 3A to 3B A schematic diagram of an example interface for data management according to other embodiments of the present disclosure is shown;

[0015] Figures 4A to 4C A schematic diagram of an example interface for data management according to further embodiments of the present disclosure is shown;

[0016] Figure 5 A schematic diagram of an example process for data management according to some embodiments of the present disclosure is shown;

[0017] Figure 6 A schematic structural block diagram of an example apparatus for data management according to certain embodiments of the present disclosure is shown; and

[0018] Figure 7 A block diagram of an apparatus capable of implementing several embodiments of the present disclosure is shown. Detailed Implementation

[0019] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0020] It should be noted that the headings of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and embodiments of any type may be included under any section / subsection. Furthermore, embodiments described in any section / subsection may be combined in any way with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0021] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0022] The embodiments of this disclosure may involve user data, data acquisition, and / or use. All of these aspects comply with applicable laws, regulations, and relevant provisions. In the embodiments of this disclosure, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, in implementing the embodiments of this disclosure, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained in accordance with relevant laws and regulations through appropriate means. The specific methods of notification and / or authorization may vary depending on the actual situation and application scenario, and the scope of this disclosure is not limited in this respect.

[0023] In this specification and the embodiments, any processing of personal information will be carried out only under the premise of legality (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information other than that necessary for basic functions will not affect the user's use of basic functions.

[0024] As briefly mentioned earlier, autonomous vehicles can determine road information, such as information on available parking spots, based on their location. Furthermore, the operation of autonomous vehicles also depends on information about available parking spots.

[0025] In view of this, embodiments of the present disclosure propose an improved solution for data management. According to various embodiments of the present disclosure, a data management interface is presented, including a map component. If a fence creation request is received, multiple area units corresponding to the fence to be created are determined. Accordingly, the docking attributes of the multiple area units are configured via a configuration window corresponding to the fence. Then, a set of elements corresponding to the fence is drawn in the map component. The style of the set of elements is determined based on the docking attributes.

[0026] In this way, the embodiments of this disclosure can improve the accuracy of autonomous vehicle parking behavior by using regional units to manage parking areas.

[0027] Example Environment

[0028] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. In this example environment 100, an application 120 is installed on a terminal device 110. A user 140 can interact with the application 120 via the terminal device 110 and / or an attached device of the terminal device 110.

[0029] Environment 100 may also include multiple autonomous vehicles, i.e., vehicles with autonomous driving capabilities (or driverless capabilities), also known as driverless cars, autonomous vehicles, etc. Application 120 may be a management application (e.g., an application for operators of autonomous vehicles to manage parking areas of multiple autonomous vehicles), a content acquisition application, or any other suitable application.

[0030] In some scenarios, user 140 (e.g., an operations staff member) can manage map-related data based on terminal device 110 to support the operation of each of multiple autonomous vehicles. Such map-related data may include, for example, information on available road segments that the autonomous vehicles can access through map data.

[0031] exist Figure 1 In environment 100, if application 120 is active, terminal device 110 can display page 150 of application 120. Page 150 may include various types of pages provided by application 120, such as data presentation pages, data configuration pages, publishing pages, personal homepages, etc. Application 120 may also have a publishing function, allowing user 140 to publish configured regional units.

[0032] In some embodiments, terminal device 110 communicates with server 130 to provide services to application 120. Terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, terminal device 110 can also support any type of user-facing interface (such as "wearable" circuitry). Server 130 can be various types of computing systems / servers capable of providing computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, etc.

[0033] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0034] The data management scheme of this disclosure will be described below with reference to the accompanying drawings. It should be understood that the pages shown in the drawings are merely examples, and various page designs are possible in practice. The various graphic elements on the page may have different arrangements and different visual representations, one or more elements may be omitted or replaced, and one or more other elements may also be present. The embodiments of this disclosure are not limited in this respect. Furthermore, in the following description, exemplary embodiments will be primarily described with respect to terminal device 110. It should be understood that the actions described with respect to terminal device 110 can be performed by application 120 on terminal device 110, or can be performed by application 120 in conjunction with its server (e.g., server 130).

[0035] The following will be referenced Figures 2A to 2E ,and Figures 3A to 3B This disclosure describes a data management scheme. Figures 2A to 2E Schematic diagrams of example interfaces 200A to 200E for data management according to some embodiments of the present disclosure are shown. Figures 3A to 3B Schematic diagrams of example interfaces 300A to 300B for data management according to other embodiments of the present disclosure are shown.

[0036] In embodiments of this disclosure, terminal device 110 presents a data management interface, which includes a map component. For example... Figure 2AThe example interface 200A shown shows that the terminal device 110 manages the parking areas for multiple autonomous vehicles based on user 140's triggering, and can present a data management interface 200A for multiple autonomous vehicles. The data management interface 200A may include a map component 216.

[0037] In embodiments of this disclosure, if terminal device 110 receives a fence creation request, it determines multiple area units corresponding to the fence to be created. In some examples, based on a data management interface, user 140 can choose to send the fence creation request via multiple unit identifiers. In other examples, based on a data management interface, user 140 can also choose to send the fence creation request via selecting a target range.

[0038] The following is for reference first. Figures 2A to 2B The example interfaces 200A to 200B shown illustrate how user 140 sends a fence creation request via multiple unit identifiers.

[0039] In some embodiments, terminal device 110 acquires multiple cell identifiers input by a user. Then, terminal device 110 determines multiple region units (also referred to as cells) corresponding to the multiple cell identifiers. Figures 2A to 2B In the example interfaces 200A to 200B shown, if the terminal device 110 receives a trigger from the user 140 on the "Batch Add" control 217, it can present the add interface 200B for receiving multiple unit identifiers input by the user 140.

[0040] User 140 can enter multiple unit identifiers in input box 221, such as unit identifier 223, unit identifier 224, etc. Based on the multiple unit identifiers entered by user 140, terminal device 110 can determine the multiple area units corresponding to the multiple unit identifiers.

[0041] The following is for reference only. Figure 3A and Figure 2B The example interfaces 300A and 200B shown illustrate that user 140 can also choose to send a fence creation request by selecting the target range.

[0042] In some embodiments, the terminal device 110 may receive a selection of a target range via a map component. Subsequently, the terminal device 110 determines a plurality of area units corresponding to the target range based on the user's selection of the target range.

[0043] like Figure 3A and Figure 2BAs shown in example interfaces 300A and 200B, if terminal device 110 receives a trigger operation from user 140 on target range 311 in map component 216, it can present interface 200B for batch adding multiple area units. It can be understood that in the scenario where terminal device 110 receives a trigger operation from user 140 on target range 311, terminal device 110 can automatically fill in multiple unit identifiers corresponding to target range 311, thereby determining the multiple area units corresponding to target range 311. In some examples, each area unit in the multiple area units has a unit identifier.

[0044] In this scenario, terminal device 110 can automatically fill one or more unit identifiers corresponding to the target range 311 into input box 221 in interface 200B. In some examples, user 140 can also select certain unit identifiers (e.g., unit identifier 223, unit identifier 224) from the multiple unit identifiers presented in input box 221 to configure the docking attributes of certain area units corresponding to certain unit identifiers.

[0045] In embodiments of this disclosure, the terminal device 110 configures the docking attributes of multiple area units via a configuration window corresponding to the fence. For example... Figure 2A As shown, after receiving a fence creation request sent by user 140 via multiple unit identifiers, terminal device 110 can display the configuration window 212 corresponding to the fence. Figure 3A In the example interface 300A shown, after receiving a fence creation request from user 140 via selection of a target area, terminal device 110 can display the configuration window 312 corresponding to that fence. In some examples, Figures 2B to 2E For the purpose of description, the following text will refer to some sample interfaces of the configuration window. Figures 2B to 2E This describes how terminal device 110 configures the docking attributes of multiple area units via a configuration window. However, this is merely an example and is not intended to limit the scope of the invention.

[0046] In some examples, terminal device 110 can configure the parking attributes of multiple area units via configuration information entered by user 140 in a configuration window. In some embodiments, the parking attributes of multiple area units can indicate whether parking is permitted for the multiple area units. It is understood that the parking attributes of multiple area units can indicate objective parking attributes. That is, objective parking attributes can indicate whether an area unit can park, for example, whether parking is prohibited or permitted.

[0047] like Figures 2B to 2CIn the example interfaces 200B to 200C shown, if terminal device 110 receives a request from user 140 to select "Objective Dockability 226" as the type of the fence to be created in the configuration window, then the dockability attribute of the fence will be configured as "Objective Dockability 226". Further, if user 140 selects a no-parking type 231 included in "Objective Dockability 226" based on the configuration window, then parking is not allowed in the multiple area units corresponding to the fence to be created. If user 140 selects a parking-allowed type included in "Objective Dockability 226" based on the configuration window, then parking is allowed in the multiple area units corresponding to the fence to be created.

[0048] In some embodiments, the parking attributes of multiple area units can also indicate the permitted parking duration for the multiple area units. It is understood that the parking attributes of multiple area units can indicate objective parking attributes. That is, objective parking attributes can indicate parking time restrictions for area units. For example, temporary parking (e.g., parking within 2 hours) or long-term parking (e.g., parking within two days). In some embodiments, user 140 can input the duration for which the autonomous vehicle can park in the areas corresponding to the multiple area units in the parking time input box 232 of the configuration window.

[0049] In some examples, if user 140 selects a temporary parking type included in objective dockability 226 based on the configuration window, then multiple area units corresponding to the fence to be created allow temporary parking. In other examples, if user 140 selects a long-term parking type included in objective dockability 226 based on the configuration window, then multiple area units corresponding to the fence to be created allow long-term parking.

[0050] In some examples, if terminal device 110 determines that area unit B exists simultaneously in multiple lists, it may display a prompt window. This prompt window includes a notification to user 140 that the docking attributes of area unit B have been configured and whether to replace them. If terminal device 110 receives confirmation from user 140, it removes area unit B from the existing lists and adds the new, effective docking attributes for area unit B.

[0051] In some embodiments, for certain area units among multiple area units corresponding to the fence to be created, user 140 can simultaneously configure the subjective exit / objective docking of those certain units. For example... Figure 2E As shown, if the terminal device 110 determines that AA area unit 251 and BB area unit 252 in the multiple areas corresponding to the fence to be created both belong to subjective admission, it can present the configuration window 200E.

[0052] In some embodiments, the terminal device 110 may also determine the time-sharing information of multiple area units via a configuration window. In some embodiments, the time-sharing information may indicate whether multiple area units are allowed to be exposed as unmanned sites within a specified time period. It is understood that the terminal device 110 may determine whether multiple area units can be selected as unmanned sites via a configuration window.

[0053] like Figure 2D In the example interface 200D shown, if the terminal device 110 receives a request from user 140 to select subjective accessibility 241 as the type of the fence to be created in the configuration window, it can configure the docking attribute of the fence to subjective accessibility 241. Further, if user 140 selects the optional types 242 included in subjective accessibility 241 in the configuration window, the multiple area units corresponding to the fence to be created can be selected as unmanned sites to be exposed. If user 140 selects the unselectable types included in subjective accessibility 241 in the configuration window, the multiple area units corresponding to the fence to be created cannot be selected as unmanned sites to be exposed.

[0054] In some embodiments, the time-sharing information can also indicate whether parking is permitted for multiple area units within a specified time period. It is understood that the terminal device 110 can determine whether parking is permitted for multiple area units via a configuration window. Figure 2D In the example interface 200D shown, if user 140 is subject to the non-parking type 245 included in the subjective admission 241 of the configuration window, then parking is not allowed in the multiple area units corresponding to the fence to be created.

[0055] In some embodiments, the terminal device 110 can also determine the inheritance type of multiple area units via a configuration window. In some embodiments, the inheritance type can indicate whether the docking type of multiple area units is inherited by the next map version. In some examples, such as Figure 2C In the example interface 200C shown, if user 140 selects not to inherit type 234 in the configuration window, the docking types of multiple areas corresponding to the fence to be created will not be inherited in the next map version.

[0056] In some examples, if user 140 selects the inheritance type in the configuration window, the docking types of multiple areas corresponding to the fence to be created will inherit the docking attributes of multiple areas in the current version in the next map version.

[0057] In some embodiments, during the generation of the next map version, if the terminal device 110 determines that a first docking attribute of a first area unit among a plurality of area units needs to be inherited, it can determine that a second area unit overlaps with the first area unit. Accordingly, the terminal device 110 determines a second docking attribute of the second area unit based on the first docking attribute of the first area unit. Figure 2F A schematic diagram of an example architecture 200F for docking attribute inheritance between map versions is shown, according to some embodiments of the present disclosure.

[0058] Reference Figure 2F In the example architecture 200F shown, during the generation of the initial second version 262, if the XX docking attribute of the C area unit among the multiple area units corresponding to the first version 261 needs to be inherited, then the D area unit overlapping with the C area unit in the initial second version 262 can be determined. Furthermore, the XXX docking attribute of the D area unit will inherit the XX docking attribute of the C area unit.

[0059] like Figure 2F As shown, user 140 can also edit the initial second version 262, which inherits certain area units from the first version 261, to generate a second version 263. Subsequently, during the generation of the third version 264, if it is determined that a certain docking attribute of the CC area unit among the multiple area units corresponding to the second version 263 needs to be inherited, the terminal device 110 can determine the DD area unit overlapping with the CC area unit in the third version 264. Furthermore, the docking attribute of the DD area unit will inherit a certain docking attribute of the C area unit.

[0060] In some embodiments, the inheritance type implementation strategy for multiple regional units can be that the prohibited parking data is greater than the unselectable data, and the unselectable data is greater than the selectable data. It is understood that this applies to a scenario where the previous map version, configured as an inheritance type, has its docking attribute configured as unselectable (i.e., it is not allowed to be exposed as an unmanned station within a specified time period). If the terminal device 110 determines that the prohibited parking type is selected in the currently created map version, it can override the unselectable type of the previous map version. That is, the docking attribute of the currently created version is the prohibited parking type.

[0061] In some embodiments, the parking attributes of multiple area units can also indicate whether getting on and off the vehicle is convenient. For example, if an area unit is an entrance / exit, a sidewalk, etc., the parking attribute of that area unit can be set to a convenient type. If an area unit is a green belt, a secondary road with a main road, etc., the parking attribute of that area unit can be set to an inconvenient type.

[0062] In some embodiments, user 140 can also batch edit multiple region units based on the data management interface. For example... Figure 2AAs shown, if the terminal device 110 receives a click from the user 140 on the batch editing control 210, it can display an editing panel for editing one or more area units selected by the user 140. Thus, the terminal device 110 can update the map data based on the user 140's editing operation on one or more area units.

[0063] The following description, with reference to the accompanying drawings, describes how, after configuring the docking attributes of multiple area units, the elements corresponding to the fences are drawn in the map component.

[0064] In this embodiment, the terminal device 110 draws a set of elements corresponding to the fence in the map component. In some embodiments, the style of the set of elements is determined based on the docking attribute. Figure 2A As shown, for scenarios where the docking attribute is "No-Dock", a group of elements can be presented with a first visual style. For example, a group of elements can be presented with a first color (e.g., red) or a first fill style 213.

[0065] For scenarios where the parking attribute is long-term parking, a group of elements can be presented using a second visual style. For example, a group of elements can be presented using a second color (e.g., blue) or a second fill style 214. For scenarios where the parking attribute is temporary parking, a group of elements can be presented using a third visual style. For example, a group of elements can be presented using a third color (e.g., yellow) or a third fill style 215. It is understood that the first visual style, second visual style, third visual style, etc., described above are merely exemplary, and this disclosure does not limit them.

[0066] In some embodiments, a set of elements may indicate the first element of the fence's extent. Figure 3A In the example interface 300A shown, if the terminal device 110 determines that the docking attributes of multiple area units corresponding to the target range 311 have been configured as long-term docking type, it can draw the element 313 corresponding to the target range 311 in the map component 216 with visual style 314.

[0067] In some embodiments, a set of elements may further include multiple second elements corresponding to multiple region units. For example... Figure 2A In the example interface 200A shown, if the terminal device 110 determines that the docking attribute of area unit A among multiple area units has been configured as long-term docking type, the element 219 corresponding to area unit A can be drawn in the map component 216 with visual style 214.

[0068] If terminal device 110 determines that the docking attribute of area unit B among multiple area units has been configured as a no-parking type, it can draw the element 218 corresponding to area unit B in map component 216 using visual style 213. If terminal device 110 determines that the docking attribute of area unit C among multiple area units has been configured as a temporary parking type, it can draw the element 211 corresponding to area unit C in map component 216 using visual style 215.

[0069] In some embodiments, terminal device 110 can create map data based on the parking attributes of multiple area units. Then, terminal device 110 provides the map data to the autonomous vehicle to trigger the autonomous vehicle to determine a parking location based on the parking attributes of the multiple area units. In some examples, after terminal device 110 creates or updates map data based on the parking attributes of multiple area units configured by user 140, the autonomous vehicle can determine a suitable parking location based on the map data.

[0070] In some embodiments, terminal device 110 may also support user 140 in filtering active area units as needed. For example... Figure 3B In the example interface 300B shown, if the terminal device 110 receives a trigger operation (e.g., a click operation) from the user 140 on the filter control 321, the filter panel 320 is displayed. The filter panel 320 may include the editing type 323 (e.g., optionality / docking), docking type 324, reason for activation 325, inheritance 326, effective design domain 327, and other filter conditions.

[0071] Terminal device 110 can determine one or more area cells that meet the filter criteria selected by user 140 in filter panel 320. Correspondingly, terminal device 110 can also display the number 322 corresponding to the filter results in the associated area of ​​filter control 321. In some examples, after determining one or more area cells that meet the filter criteria, terminal device 110 will simultaneously display map data and the data corresponding to the one or more area cells.

[0072] The following text continues for further reference. Figures 4A to 4C This disclosure describes a data management scheme. Figures 4A to 4C Schematic diagrams of example interfaces 400A to 400C for data management according to further embodiments of the present disclosure are shown.

[0073] In some embodiments, such as Figure 4AIn the example interface 400A shown, if the terminal device 110 receives a click from user 140 on the export control 411, it can export a table file corresponding to the map data created by user 140. The table file can include information such as city, region, map, region unit, and attributes. In some examples, the terminal device 110 can export the table file at the region unit granularity for each piece of data.

[0074] like Figures 4B to 4C In the example interfaces 400B to 400C shown, if the terminal device 110 detects that the user 140 clicks on the control 421 for viewing details of a certain data item, it can display a details page 400C for that data item. In some embodiments, the details page 400C may include basic information 431 corresponding to the data item, such as information related to the city, region, map version, and regional unit version. The details page 400C may also include real-time information 432 corresponding to the data item.

[0075] In summary, the embodiments of this disclosure can improve the accuracy of autonomous vehicle parking behavior by utilizing area units to manage parking areas.

[0076] Example process

[0077] Figure 5 A flowchart of an example process 500 for data management according to some embodiments of the present disclosure is shown. Process 500 can be implemented at terminal device 110. References are made below. Figure 1 Describe the process 500.

[0078] like Figure 5 As shown in box 510, terminal device 110 presents a data management interface, which includes a map component.

[0079] In box 520, terminal device 110, in response to receiving a fence creation request, identifies multiple area units corresponding to the fence to be created.

[0080] In frame 530, terminal device 110 configures the docking attributes of multiple area units via the configuration window corresponding to the fence.

[0081] In box 540, terminal device 110 draws a set of elements corresponding to the fence in the map component, the style of which is determined based on the docking attribute.

[0082] In some embodiments, the parking attribute indicates at least one of the following: whether parking is permitted in the plurality of area units; and the duration for which parking is permitted in the plurality of area units.

[0083] In some embodiments, process 500 further includes: determining time-sharing information for a plurality of area units via a configuration window, wherein the time-sharing information indicates whether the plurality of area units are permitted to be exposed as unmanned sites within a specified time period; and / or whether the plurality of area units are permitted to park within a specified time period.

[0084] In some embodiments, in response to receiving a fence creation request, determining a plurality of area units corresponding to the fence to be created includes: obtaining a plurality of unit identifiers input by a user; and determining a plurality of area units corresponding to the plurality of unit identifiers.

[0085] In some embodiments, in response to receiving a fence creation request, determining multiple area units corresponding to the fence to be created includes: receiving a selection of a target range via a map component; and determining multiple area units corresponding to the target range.

[0086] In some embodiments, a set of elements includes: a first element indicating the extent of the fence; and / or a plurality of second elements corresponding to a plurality of area units.

[0087] In some embodiments, process 500 further includes: determining, via a configuration window, an inheritance type for a plurality of area units, the inheritance type indicating whether the docking attributes of the plurality of area units are inherited by the next map version; during the generation of the next map version, in response to the requirement that a first docking attribute of a first area unit among the plurality of area units needs to be inherited, determining that a second area unit overlaps with the first area unit; and determining a second docking attribute of the second area unit based on the first docking attribute of the first area unit.

[0088] In some embodiments, process 500 further includes: creating map data based on the parking attributes of multiple area units; and providing the map data to the autonomous vehicle to trigger the autonomous vehicle to determine a parking location based on the parking attributes of the multiple area units.

[0089] Example devices and equipment

[0090] Figure 6 A schematic structural block diagram of a data management apparatus 600 according to certain embodiments of the present disclosure is shown. The apparatus 600 may be implemented as or included in a terminal device 110. The various modules / components in the apparatus 600 may be implemented by hardware, software, firmware, or any combination thereof.

[0091] As shown in the figure, device 600 includes a management interface presentation module 610, configured to present a data management interface, which includes a map component. Device 600 also includes a region unit determination module 620, configured to determine multiple region units corresponding to the fence to be created in response to receiving a fence creation request. Device 600 further includes a docking attribute configuration module 630, configured to configure the docking attributes of the multiple region units via a configuration window corresponding to the fence. Device 600 also includes an element drawing module 640, configured to draw a set of elements corresponding to the fence in the map component, wherein the style of the set of elements is determined based on the docking attributes.

[0092] In some embodiments, the parking attribute indicates at least one of the following: whether parking is permitted in the plurality of area units; and the duration for which parking is permitted in the plurality of area units.

[0093] In some embodiments, the device 600 further includes a time-sharing information configuration module, configured to determine time-sharing information of multiple area units via a configuration window, wherein the time-sharing information indicates whether the multiple area units are allowed to be exposed as unmanned sites within a specified time period; and / or whether the multiple area units are allowed to park within a specified time period.

[0094] In some embodiments, the region unit determination module 620 is further configured to acquire a plurality of unit identifiers input by a user; and to determine a plurality of region units corresponding to the plurality of unit identifiers.

[0095] In some embodiments, the region unit determination module 620 is further configured to receive a selection of a target range via a map component; and to determine a plurality of region units corresponding to the target range.

[0096] In some embodiments, a set of elements includes: a first element indicating the extent of the fence; and / or a plurality of second elements corresponding to a plurality of area units.

[0097] In some embodiments, the apparatus 600 further includes an inheritance type determination module configured to determine, via a configuration window, an inheritance type indicating whether the docking attributes of the multiple area units are inherited by the next map version; during the generation of the next map version, in response to the requirement that a first docking attribute of a first area unit among the multiple area units needs to be inherited, determine that a second area unit overlaps with the first area unit; and based on the first docking attribute of the first area unit, determine a second docking attribute of the second area unit.

[0098] In some embodiments, the apparatus 600 further includes a parking location determination module configured to create map data based on parking attributes of multiple area units; and to provide the map data to the autonomous vehicle to trigger the autonomous vehicle to determine a parking location based on the parking attributes of multiple area units.

[0099] Figure 7 A block diagram is shown illustrating a computing device 700 in which one or more embodiments of the present disclosure may be implemented. It should be understood that... Figure 7 The computing device 700 shown is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. Figure 7 The computing device 700 shown can be used to implement Figure 1 Terminal equipment 110.

[0100] like Figure 7 As shown, computing device 700 is in the form of a general-purpose computing device. Components of computing device 700 may include, but are not limited to, one or more processors or processing units 710, memory 720, storage devices 730, one or more communication units 740, one or more input devices 750, and one or more output devices 760. Processing unit 710 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 720. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of computing device 700.

[0101] Computing device 700 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to computing device 700, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 720 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 730 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data (e.g., training data for training) and can be accessed within computing device 700.

[0102] The computing device 700 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 7 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 720 may include computer program product 725 having one or more program modules configured to perform various methods or actions of various embodiments of this disclosure.

[0103] The communication unit 740 enables communication with other computing devices via a communication medium. Additionally, the components of the computing device 700 can function as a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the computing device 700 can operate in a networked environment using logical connections to one or more other servers, networked personal computers (PCs), or another network node.

[0104] Input device 750 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 760 can be one or more output devices, such as a monitor, speaker, printer, etc. Computing device 700 can also communicate as needed with one or more external devices (not shown) via communication unit 740. These external devices, such as storage devices, display devices, etc., can communicate with one or more devices that enable user interaction with computing device 700, or with any device (e.g., network card, modem, etc.) that enables computing device 700 to communicate with one or more other computing devices. Such communication can be performed via input / output (I / O) interface (not shown).

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

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

[0107] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

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

[0109] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0110] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A data management method, comprising: A data management interface is presented, which includes a map component; In response to receiving a fence creation request, identify multiple area units corresponding to the fence to be created; Configure the docking attributes of the multiple area units via the configuration window corresponding to the fence; as well as In the map component, a set of elements corresponding to the fence are drawn, wherein the style of the set of elements is determined based on the docking attribute.

2. The method of claim 1, wherein the docking attribute indicates at least one of the following: Whether parking is permitted in the multiple area units; and / or The permitted parking duration for the multiple area units.

3. The method according to claim 1, further comprising: The time-sharing information of the multiple regional units is determined via the configuration window. The time-sharing information indicates: Whether the multiple regional units are allowed to be exposed as unmanned sites within a specified time period; and / or Whether parking is permitted in the multiple area units within a specified time period.

4. The method of claim 1, wherein in response to receiving a fence creation request, determining the plurality of area units corresponding to the fence to be created includes: Retrieve multiple unit identifiers input by the user; as well as Determine the plurality of region units corresponding to the plurality of unit identifiers.

5. The method of claim 1, wherein determining the plurality of area units corresponding to the fence to be created in response to receiving a fence creation request comprises: The selection of the target range is received via the map component; as well as Determine the plurality of regional units corresponding to the target range.

6. The method of claim 1, wherein the set of elements comprises: The first element indicating the extent of the fence; and / or Multiple second elements corresponding to the multiple region units.

7. The method according to claim 1, further comprising: The inheritance type of the plurality of regional units is determined via the configuration window, and the inheritance type indicates whether the docking attribute of the plurality of regional units is inherited by the next map version; During the generation of the next map version, in response to the need to inherit the first docking attribute of the first area unit among the plurality of area units, it is determined that the second area unit overlaps with the first area unit. as well as Based on the first docking attribute of the first area unit, the second docking attribute of the second area unit is determined.

8. The method according to claim 1, further comprising: Map data is created based on the docking attributes of the multiple regional units; as well as The map data is provided to the autonomous vehicle to trigger the autonomous vehicle to determine the parking location based on the parking attributes of the multiple regional units.

9. An apparatus for data management, comprising: The management interface presentation module is configured to present a data management interface, which includes a map component. The area unit determination module is configured to determine multiple area units corresponding to the fence to be created in response to receiving a fence creation request; The docking attribute configuration module is configured to configure the docking attributes of the multiple area units via the configuration window corresponding to the fence; as well as An element drawing module is configured to draw a set of elements corresponding to the fence in the map component, wherein the style of the set of elements is determined based on the docking attribute.

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

11. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 8.

12. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 8.

Images