Map data management method and apparatus

Abstract

The application discloses a map data management method and device, and relates to the technical field of computers. A specific implementation mode of the method comprises the following steps: acquiring a recommended route for a target route section generated in response to a user's route acquisition request; acquiring a target route selected by the user from the recommended routes; and respectively storing the target route and the recommended routes not selected by the user in association with the target route section. The implementation mode can guarantee the integrity of the relevant navigation data corresponding to the target route section by storing the recommended routes not selected by the user and the target route selected by the user in association with the target route section, thereby facilitating the user to view the real-time response result of the system to the user's route acquisition request; when the target route section comprises a plurality of sub-route sections, the relevant data of the sub-route sections in the target route section are stored in association, thereby facilitating the user to check and search the target route section and the routes of each sub-route section at one time, and facilitating rapidness.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a map data management method and apparatus. Background Technology

[0002] In existing technologies, when providing navigation services to users, multiple routes are typically generated for the user to choose from based on their route request. However, the system usually only saves the navigation route ultimately selected by the user. This makes it inconvenient for users to view the system's real-time response to their route request. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a map data management method and apparatus. By associating and storing recommended routes not selected by the user and target routes selected by the user with their corresponding target road segments, the integrity of the relevant navigation data corresponding to the target road segments can be guaranteed, making it convenient for users to view the real-time response results of the system to the user's route acquisition request. When the target road segment includes multiple sub-road segments, by associating and storing the relevant data of each sub-road segment in the target road segment, it is convenient to view and retrieve each sub-road segment included in the target road segment and the route of each sub-road segment at one time, which is convenient and fast.

[0004] To achieve the above objectives, according to one aspect of the present invention, a map data management method is provided, comprising:

[0005] Obtain a recommended route for a target road segment generated in response to a user's route request; the target road segment refers to the road segment from the user-specified starting point to the user-specified destination.

[0006] Obtain the target route selected by the user from each of the recommended routes;

[0007] The target route and the recommended route not selected by the user are associated and stored with the target road segment respectively.

[0008] Optionally, the target road segment includes multiple sub-road segments;

[0009] The process of associating and storing the target route and the recommended route not selected by the user with the target road segment includes: associating and storing the recommended sub-route not selected by the user and the target sub-route selected by the user with the sub-segment for each sub-segment, and then associating and storing each sub-segment.

[0010] Optionally, the recommended sub-routes not selected by the user and the target sub-routes selected by the user corresponding to each sub-route are associated and stored with the sub-route, including:

[0011] Set the same segment identifier for the sub-segment and the corresponding recommended sub-route that was not selected by the user and the target sub-route that was selected by the user, and then store them; or, store the sub-segment and the corresponding recommended sub-route that was not selected by the user and the target sub-route that was selected by the user in the same location.

[0012] Optionally, the method of associating and storing the recommended sub-routes that were not selected by the user and the target sub-routes that were selected by the user with each sub-route segment further includes setting a selection identifier for the target sub-route selected by the user corresponding to the sub-route segment.

[0013] Optionally, the various sub-road segments are stored in association, including:

[0014] Store the sub-segment information of each of the sub-segments in the same location; or, set the same navigation record identifier for the sub-segment information of each of the sub-segments and then store it; or, set a pointer to the next sub-segment for each of the sub-segments, and set the pointer of the last sub-segment in the target segment to the default value, and then store it.

[0015] Optionally, after associating and storing the target route and the recommended route not selected by the user with the target road segment, the method further includes: naming the associated stored data packets according to the road segment information of the target road segment.

[0016] Optionally, after associating and storing the target route and the recommended route not selected by the user with the target road segment, the method further includes: in response to the user's data editing request, deleting or modifying part or all of the associated stored data packet.

[0017] According to a second aspect of the present invention, a map data management device is provided, comprising:

[0018] The data acquisition module is used to: acquire recommended routes for target road segments generated in response to a user's route acquisition request, wherein the target road segment refers to the road segment from the starting point specified by the user to the destination specified by the user; and acquire the target route selected by the user from each of the recommended routes.

[0019] The associated storage module is used to associate and store the target route and the recommended route that was not selected by the user with the target road segment, respectively.

[0020] Optionally, the target road segment includes multiple sub-road segments;

[0021] The associated storage module associates and stores the target route and the recommended route not selected by the user with the target road segment, including: associating and storing the recommended sub-route not selected by the user and the target sub-route selected by the user with the sub-segment for each sub-segment, and then associating and storing each sub-segment.

[0022] Optionally, the associated storage module associates and stores the recommended sub-routes not selected by the user and the target sub-routes selected by the user with each sub-route, including:

[0023] Set the same segment identifier for the sub-segment and the corresponding recommended sub-route that was not selected by the user and the target sub-route that was selected by the user, and then store them; or, store the sub-segment and the corresponding recommended sub-route that was not selected by the user and the target sub-route that was selected by the user in the same location.

[0024] Optionally, the associated storage module associates and stores the recommended sub-routes that were not selected by the user and the target sub-routes that were selected by the user with each sub-route, and further includes setting a selection identifier for the target sub-route selected by the user corresponding to the sub-route.

[0025] Optionally, the associated storage module stores each of the sub-road segments in association, including:

[0026] Store the sub-segment information of each of the sub-segments in the same location; or, set the same navigation record identifier for the sub-segment information of each of the sub-segments and then store it; or, set a pointer to the next sub-segment for each of the sub-segments, and set the pointer of the last sub-segment in the target segment to the default value, and then store it.

[0027] Optionally, the associated storage module is further configured to: associate the target route and the recommended route not selected by the user with the target road segment respectively, and then name the associated storage data packets according to the road segment information of the target road segment.

[0028] Optionally, the associated storage module is further configured to: associate the target route and the recommended route not selected by the user with the target road segment respectively, and then, in response to the user's data editing request, delete or modify part or all of the associated storage data packet.

[0029] According to a third aspect of the present invention, an electronic device for map data management is provided, comprising:

[0030] One or more processors;

[0031] Storage device for storing one or more programs.

[0032] When the one or more programs are executed by the one or more processors, the one or more processors implement the method provided in the first aspect of the embodiments of the present invention.

[0033] According to a fourth aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, characterized in that the program, when executed by a processor, implements the method provided in the first aspect of the present invention.

[0034] One embodiment of the above invention has the following advantages or beneficial effects: by associating and storing the recommended routes not selected by the user and the target routes selected by the user with the corresponding target road segments, the integrity of the relevant navigation data corresponding to the target road segments can be guaranteed, making it convenient for users to view the real-time response results of the system to the user's route acquisition request; when the target road segment includes multiple sub-road segments, by associating and storing the relevant data of each sub-road segment in the target road segment, it is convenient to view and retrieve each sub-road segment included in the target road segment and the route of each sub-road segment at one time, which is convenient and fast.

[0035] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0036] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0037] Figure 1 This is a schematic diagram of the main process of the map data management method according to an embodiment of the present invention;

[0038] Figure 2 This is a schematic diagram of the main modules of the map data management device according to an embodiment of the present invention;

[0039] Figure 3 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0040] Figure 4 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

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

[0042] According to one aspect of the present invention, a map data management method is provided.

[0043] Figure 1 This is a schematic diagram of the main flow of the map data management method according to an embodiment of the present invention, as shown below. Figure 1 As shown, map data management methods include:

[0044] Step S101: Obtain the recommended route for the target road segment generated in response to the user's route acquisition request;

[0045] Step S102: Obtain the target route selected by the user from each of the recommended routes;

[0046] Step S103: Associate and store the target route and the recommended route that was not selected by the user with the target road segment respectively.

[0047] A target route segment refers to the route from a user-specified starting point to a user-specified destination. The user-specified starting and ending points can be obtained from the user's route retrieval request. When the user's route retrieval request does not include starting or ending point information, fuzzy matching can be used to determine the starting and ending points. For example, when a user intends to browse tourist routes in city Q, if the route retrieval request does not include starting and ending point information, the starting and ending points of the most popular tourist routes in city Q can be used as the user's intended search points when sending the route retrieval request, based on historical data. Alternatively, the starting and ending points of tourist routes promoted in city Q can be used as the user's intended search points when sending the route retrieval request, based on city Q's tourism promotion plan. For instance, if the starting point is A and the ending point is B, then the route segment from starting point A to ending point B is called the target route segment, denoted as the AB route segment.

[0048] When a journey from the starting point to the destination may pass through one or more intermediate points, any passable road segment formed between any two intermediate points, as well as between an intermediate point and the starting or ending point, is considered a sub-segment of the target road segment. A target road segment may include one or more sub-segments. If the journey from starting point A to ending point B passes through an intermediate point C, then the sub-segments of road segment AB include segments AC and CB. If the journey from starting point A to ending point B passes through two intermediate points C and D in sequence, then the sub-segments of road segment AB include segments AC, CD, and DB. Recommended routes are typically generated for each sub-segment, but may also include only one. When the target road segment includes only one sub-segment, recommended routes not selected by the user and the target route can be associated and stored with that sub-segment. For example, the target road segment is the road segment from the user's starting point A to the destination B, including a sub-segment AB. The recommended routes generated for road segment AB include Lab1, Lab2, and Lab3. If the user selects Lab2 as the final navigation route, then when storing navigation-related data, Lab1 and Lab3 are bound together with Lab2 to form a bound data package before storage. Alternatively, Lab1, Lab2, and Lab3 can be assigned the same road segment identifier "AB" and then stored in the system location or stored in different locations respectively. This embodiment can record the real-time status of the system's response to the user's route query request. When the user queries later, they can not only see the route they selected at that time, but also see other routes recommended by the system.

[0049] When a target road segment comprises multiple sub-segments, and the target road segment and recommended routes not selected by the user are associated with the target road segment for storage, each sub-segment and its corresponding route can be packaged and stored in the same location. For example, if the target road segment is a route from user's starting point A to destination B, including two sub-segments AC and CB, and the recommended routes generated for segment AC include Lac1, Lac2, and Lac3, and the user selects Lac2 as the navigation route for segment AC, and the recommended routes generated for segment CB include Lcb1, Lcb2, and Lcb3, and the user selects Lcb2 as the navigation route for segment CB, then when storing navigation-related data, Lac1, Lac2, and Lac3, as well as Lcb1, Lcb2, and Lcb3, are stored in the same location.

[0050] Optionally, when the target road segment includes multiple sub-segments, when storing the target road segment and the recommended routes not selected by the user as associated with the target road segment, the recommended sub-routes not selected by the user and the target sub-routes selected by the user corresponding to each sub-segment are stored as associated with the sub-segment, and then each sub-segment is stored as associated. For example, the target road segment is a road segment from user's starting point A to destination B, including two sub-segments AC and CB. Recommended routes generated for segment AC include Lac1, Lac2, and Lac3. The user selects Lac2 as the navigation route for segment AC. Recommended routes generated for segment CB include Lcb1, Lcb2, and Lcb3. The user selects Lcb2 as the navigation route for segment CB. Then, when storing navigation-related data, Lab1 and Lab3 are bound together with Lab2 to form a sub-data packet, and Lcb1 and Lcb3 are bound together with Lcb2 to form another sub-data packet. The two sub-data packets are then stored as associated. This embodiment enables layer-by-layer binding, with clear hierarchical structure, facilitating query and retrieval.

[0051] In some optional embodiments, the recommended sub-route not selected by the user and the target sub-route selected by the user corresponding to each sub-segment are associated and stored with the sub-segment, including: setting the same segment identifier for the sub-segment and the recommended sub-route not selected by the user and the target sub-route selected by the user corresponding to the sub-segment, and then storing them.

[0052] For example, the target road segment is the route from user's starting point A to destination B, including two sub-segments AC and CB. Recommended routes generated for segment AC include Lac1, Lac2, and Lac3. The user selects Lac2 as the navigation route for segment AC. Recommended routes generated for segment CB include Lcb1, Lcb2, and Lcb3. The user selects Lcb2 as the navigation route for segment CB. When storing navigation-related data, Lab1 and Lab3 are bound together with Lab2 to form a sub-data packet, and this sub-data packet is assigned the road segment identifier "AC". Lcb1 and Lcb3 are bound together with Lcb2 to form another sub-data packet, and this sub-data packet is assigned the road segment identifier "CB". Different routes within the same sub-data packet can be stored separately.

[0053] This embodiment reduces the requirements for storing each route by setting the same segment identifier for each route corresponding to the same sub-segment, making it easier to store them separately.

[0054] In some alternative embodiments, the sub-segment, along with the corresponding recommended sub-route that was not selected by the user and the target sub-route that was selected by the user, are stored in the same location.

[0055] For example, the target road segment is the road segment from the user's starting point A to the destination B, including two sub-road segments AC and CB. The recommended routes generated for road segment AC include Lac1, Lac2, and Lac3. The user selects Lac2 as the navigation route for road segment AC. The recommended routes generated for road segment CB include Lcb1, Lcb2, and Lcb3. The user selects Lcb2 as the navigation route for road segment CB. Then, when storing navigation-related data, Lab1 and Lab3 are bound together with Lab2 and stored in the same location (e.g., a folder named "AC"). Lcb1 and Lcb3 are also bound together with Lcb2 and stored in the same location (e.g., a folder named "CB").

[0056] This embodiment stores all routes corresponding to the same sub-segment in the same location, making it easy to view and retrieve data at once and improving data query speed.

[0057] Optionally, associating and storing the recommended sub-routes not selected by the user and the target sub-routes selected by the user with each sub-segment further includes: setting a selection identifier for the target sub-routes selected by the user corresponding to each sub-segment. The recommended route with the selection identifier is the target sub-routes selected by the user. By setting the selection identifier, it is easier to quickly determine the target route from among the recommended routes.

[0058] In this embodiment of the invention, when storing the various sub-road segments in association, the sub-road segment information of each sub-road segment can be stored in the same location for easy one-time viewing and retrieval. Alternatively, the same navigation record identifier can be set for the sub-road segment information of each sub-road segment. The navigation record identifier is generated based on the target road segment to which the sub-road segment belongs, representing that the sub-road segment is a component of the target road segment. The navigation record identifier can be a string including the start and end points of the target road segment, or it can be obtained by processing the string (such as hashing). Of course, a pointer to the next sub-road segment can also be set for each sub-road segment, and the pointer to the last sub-road segment in the target road segment can be set to a default value before storage.

[0059] In practical applications, after associating and storing the target road segment and the recommended routes not selected by the user with the target road segment, the associated stored data packets can be named according to the road segment information of the target road segment to distinguish each data packet and facilitate later retrieval. For example, the associated stored data can be named as a string including the start and end points of the target road segment, or as a hash value of the string including the start and end points of the target road segment. Users can also name the target route in other ways according to the actual situation, such as naming the tourist route in city Q as "City Q Tourist Route on XX Year XX Month XX Day".

[0060] Optionally, after associating and storing the target road segment and the recommended route not selected by the user with the target road segment, the system can also delete or modify part or all of the associated stored data packet in response to the user's data editing request. For example, the data within each overall data packet can be deleted or corrected to avoid interference from erroneous or useless data in subsequent route determination.

[0061] Users often need to navigate multiple times for a given route when using a navigation system. For example, a user traveling from point A to point B might pass through intermediate nodes C, D, and E. During the journey from C, D, and E to point B, the user searches for road segments AC, CD, DE, and EB. This route requires four navigation attempts. However, to recreate this route, four more searches are needed to find the original route. If the time interval is long, it becomes difficult to find the original route record, necessitating a route redefinition. This is especially tedious for travel routes, and redefining the route can easily lead to deviations from the original. For example, a user traveling from point A to point B might pass through intermediate nodes C, D, and E, searching for road segments AC, CD, DE, and EB. The navigation records selected by the user for each road segment are Lac0, Lcd0, Lde0, and Leb0. When the user travels from A to B again, because there are many intermediate nodes between A and B, and these intermediate nodes are usually interconnected (e.g., feasible routes between A and B include ACDEB, ACB, and ADEFB), it is difficult for the user to find the navigation route ACDEB that was searched previously. Furthermore, because each road segment may include multiple feasible routes (e.g., feasible routes for road segment AC may include Lac1, Lac2, and Lac3), it is difficult for the user to find a route similar to the original travel route Lac0, Lcd0, Lde0, and Leb0.

[0062] In this embodiment of the invention, when the target road segment includes multiple sub-road segments, the relevant data of each sub-road segment is associated and stored, for example, bound together to form a bound data package. The bound data package can be consulted, and the bound data package contains the navigation data required for that segment of the route. Thus, the integrity of the navigation data is guaranteed by binding, solving the problem of needing to consult or search multiple times for one end of the route. Moreover, the bound data package can be shared via the Internet to assist others in navigating multiple segments.

[0063] According to a second aspect of the present invention, an apparatus for implementing the above-described method is provided.

[0064] Figure 2 This is a schematic diagram of the main modules of the map data management device according to an embodiment of the present invention.

[0065] like Figure 2 As shown, the map data management device 200 includes:

[0066] Data acquisition module 201 is used to: acquire recommended routes for target road segments generated in response to a user's route acquisition request, wherein the target road segment refers to a road segment from the starting point specified by the user to the destination specified by the user; and acquire the target route selected by the user from each of the recommended routes.

[0067] The associated storage module 202 is used to associate and store the target route and the recommended route not selected by the user with the target road segment, respectively.

[0068] Optionally, the target road segment includes multiple sub-road segments;

[0069] The associated storage module associates and stores the target route and the recommended route not selected by the user with the target road segment, including: associating and storing the recommended sub-route not selected by the user and the target sub-route selected by the user with the sub-segment for each sub-segment, and then associating and storing each sub-segment.

[0070] Optionally, the associated storage module associates and stores the recommended sub-routes not selected by the user and the target sub-routes selected by the user with each sub-route, including:

[0071] Set the same segment identifier for the sub-segment and the corresponding recommended sub-route that was not selected by the user and the target sub-route that was selected by the user, and then store them; or, store the sub-segment and the corresponding recommended sub-route that was not selected by the user and the target sub-route that was selected by the user in the same location.

[0072] Optionally, the associated storage module associates and stores the recommended sub-routes that were not selected by the user and the target sub-routes that were selected by the user with each sub-route, and further includes setting a selection identifier for the target sub-route selected by the user corresponding to the sub-route.

[0073] Optionally, the associated storage module stores each of the sub-road segments in association, including:

[0074] Store the sub-segment information of each of the sub-segments in the same location; or, set the same navigation record identifier for the sub-segment information of each of the sub-segments and then store it; or, set a pointer to the next sub-segment for each of the sub-segments, and set the pointer of the last sub-segment in the target segment to the default value, and then store it.

[0075] Optionally, the associated storage module is further configured to: associate the target route and the recommended route not selected by the user with the target road segment respectively, and then name the associated storage data packets according to the road segment information of the target road segment.

[0076] Optionally, the associated storage module is further configured to: associate the target route and the recommended route not selected by the user with the target road segment respectively, and then, in response to the user's data editing request, delete or modify part or all of the associated storage data packet.

[0077] According to a third aspect of the present invention, an electronic device for map data management is provided, comprising:

[0078] One or more processors;

[0079] Storage device for storing one or more programs.

[0080] When the one or more programs are executed by the one or more processors, the one or more processors implement the method provided in the first aspect of the embodiments of the present invention.

[0081] According to a fourth aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, characterized in that the program, when executed by a processor, implements the method provided in the first aspect of the present invention.

[0082] Figure 3 An exemplary system architecture 300 is shown that can be applied to the map data management method or map data management device of the present invention.

[0083] like Figure 3As shown, system architecture 300 may include terminal devices 301, 302, and 303, a network 304, and a server 305. Network 304 serves as the medium for providing communication links between terminal devices 301, 302, and 303 and server 305. Network 304 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0084] Users can use terminal devices 301, 302, and 303 to interact with server 305 via network 304 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 301, 302, and 303, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0085] Terminal devices 301, 302, and 303 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0086] Server 305 can be a server that provides various services, such as a backend management server that supports shopping websites browsed by users using terminal devices 301, 302, and 303 (for example only). The backend management server can analyze and process data such as received product information query requests, and feed back the processing results (such as target push information and product information - for example only) to the terminal device.

[0087] It should be noted that the map data management method provided in this embodiment of the invention is generally executed by server 305, and correspondingly, the map data management device is generally set in server 305.

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

[0089] The following is for reference. Figure 4 It shows a schematic diagram of the structure of a computer system 400 suitable for implementing a terminal device of the present invention. Figure 4 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0090] like Figure 4As shown, the computer system 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 402 or programs loaded from storage section 408 into random access memory (RAM) 403. The RAM 403 also stores various programs and data required for the operation of the system 400. The CPU 401, ROM 402, and RAM 403 are interconnected via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0091] The following components are connected to I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 410 as needed so that computer programs read from it can be installed into storage section 408 as needed.

[0092] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by central processing unit (CPU) 401, it performs the functions defined above in the system of this invention.

[0093] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0094] 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 the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that 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 consecutively indicated 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 a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0095] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor. For example, a processor may include: a data acquisition module, configured to: acquire recommended routes for a target road segment generated in response to a user's route acquisition request, wherein the target road segment refers to a road segment from a user-specified starting point to a user-specified ending point; acquire the target route selected by the user from each of the recommended routes; and an association storage module, configured to: associate and store the target route and recommended routes not selected by the user with the target road segment, respectively. The names of these modules do not necessarily limit the module itself; for example, the association storage module may also be described as "a module for acquiring recommended routes for a target road segment generated in response to a user's route acquisition request."

[0096] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to include: acquiring recommended routes for a target road segment generated in response to a user's route acquisition request; acquiring a target route selected by the user from each of the recommended routes; and associating and storing recommended routes not selected by the user and the target route with the target road segment.

[0097] According to the technical solution of the present invention, by associating and storing the recommended routes not selected by the user and the target routes selected by the user with the corresponding target road segments, the integrity of the relevant navigation data corresponding to the target road segments can be guaranteed, making it convenient for users to view the real-time response results of the system to the user's route acquisition request; when the target road segment includes multiple sub-road segments, by associating and storing the relevant data of each sub-road segment in the target road segment, it is convenient to view and retrieve each sub-road segment included in the target road segment and the route of each sub-road segment at one time, which is convenient and fast.

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

Claims

1. A map data management method characterized by comprising: The method comprises the following steps: obtaining recommended routes for a target route segment generated in response to a user's route obtaining request; the target route segment refers to a route segment from a starting point specified by the user to a terminal point specified by the user, including a plurality of sub-route segments; when the user's route obtaining request does not carry starting point or terminal point information, and the user intends to browse a tourist route in a city, the starting point and the terminal point of the tourist route with the highest traffic are taken as the starting point and the terminal point that the user intends to search for when sending the route obtaining request according to historical data of tourists in the city, or the starting point and the terminal point of a tourist route that is highlighted in the city are taken as the starting point and the terminal point that the user intends to search for when sending the route obtaining request according to a tourist business promotion plan of the city; obtaining a target route selected by the user from the recommended routes; storing the target route and the recommended routes not selected by the user in association with the target route segment respectively, including: storing the target sub-route segment selected by the user and the recommended sub-route segments not selected by the user corresponding to each sub-route segment in association with the sub-route segment, and then storing each sub-route segment in association; storing each sub-route segment in association includes: binding each sub-route segment together to form a binding data packet, so as to be consulted according to the binding data packet; the method further comprises: sharing the binding data packet through the Internet to assist others in multi-segment navigation.

2. The method of claim 1, wherein, storing the target sub-route segment selected by the user and the recommended sub-route segments not selected by the user corresponding to each sub-route segment in association with the sub-route segment includes: setting the same route segment identifier for the sub-route segment and the recommended sub-route segments not selected by the user and the target sub-route segment selected by the user corresponding to the sub-route segment, and then storing; or storing the sub-route segment and the recommended sub-route segments not selected by the user and the target sub-route segment selected by the user corresponding to the sub-route segment to the same location.

3. The method of claim 2, wherein, storing the target sub-route segment selected by the user and the recommended sub-route segments not selected by the user corresponding to each sub-route segment in association with the sub-route segment further includes: setting a selection identifier for the target sub-route segment selected by the user corresponding to the sub-route segment.

4. The method of claim 1, wherein, storing each sub-route segment in association includes: storing the sub-route segment information of each sub-route segment to the same location; or setting the same navigation record identifier for the sub-route segment information of each sub-route segment, and then storing; or setting a pointer for each sub-route segment to point to the next sub-route segment of the sub-route segment, and setting the pointer of the last sub-route segment in the target route segment as a default value, and then storing.

5. The method according to any one of claims 1 to 4, characterized in that, after storing the target route and the recommended routes not selected by the user in association with the target route segment respectively, the method further comprises naming the data packet stored in association according to the route segment information of the target route segment.

6. The method of any one of claims 1-4, wherein, After the target route and the recommended routes not selected by the user are respectively stored in association with the target road segment, the method further comprises: in response to a data editing request of the user, deleting or modifying part or all of the data packets stored in association.

7. A map data management device characterized by comprising: The method comprises: a data acquisition module configured to acquire recommended routes from a target starting point to a target ending point for the target road segment generated in response to a route acquisition request of a user; acquiring a target route selected by the user from the recommended routes; the target road segment refers to a road segment from a starting point specified by the user to an ending point specified by the user, and includes a plurality of sub-road segments; when the route acquisition request of the user does not carry starting point or ending point information, and the user intends to browse a tourist route in a city, the starting point and the ending point of the tourist route with the highest traffic in the historical data of tourists in the city are taken as the starting point and the ending point that the user intends to search when sending the route acquisition request, or the starting point and the ending point of the tourist route that is the focus of promotion in the city according to the tourist business promotion plan of the city are taken as the starting point and the ending point that the user intends to search when sending the route acquisition request; an associated storage module configured to store the target route and the recommended routes not selected by the user in association with the target road segment, including: storing the recommended sub-road segments not selected by the user and the target sub-road segments selected by the user in association with each of the sub-road segments, and then storing the sub-road segments in association; the sub-road segments are stored in association, including: binding the sub-road segments together to form a bound data packet, so as to facilitate the bound data packet to be consulted; the device is further configured to share the bound data packet through the Internet to assist others to navigate multiple segments.

8. An electronic device of map data management, characterized by, The method comprises: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any one of claims 1-6.

9. A computer readable medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the method of any one of claims 1-6.

Images