Method and apparatus for sharing map update data

Abstract

The present disclosure relates to a method and apparatus for sharing a map correction history.SOLUTION: A method according to an embodiment of the present disclosure includes receiving, from a first user terminal, a first correction history generated based on an initial map and a first correction map obtained by correcting the initial map, and receiving, from a second user terminal, a second correction history generated based on the initial map and a second correction map obtained by correcting the initial map. The second correction history may be transmitted to the first user terminal, the first correction history may be transmitted to the second user terminal, and the second correction history may be reflected in the second correction map displayed on the first user terminal in real time and the first correction history may be reflected in the second correction map displayed on the second user terminal in real time according to a result of the transmission.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present disclosure provides a method and apparatus for sharing map correction data. [Background technology]

[0002] In recent years, there has been an increase in tasks that require generating map data for use in navigation devices or continuously modifying previously generated map data. When modifying previously generated map data, there is a possibility that the map modification history made by each user may be lost due to multiple users modifying the map data.

[0003] Therefore, when multiple users simultaneously modify map data, a technology is needed that allows map modification histories made by other users to be reflected in real time. Summary of the Invention [Problem to be solved by the invention]

[0004] The present invention provides a method and apparatus for sharing map correction data. The problems to be solved by the present invention are not limited to those described above, and other problems and advantages of the present invention not mentioned can be understood from the following description and will be more clearly understood from the embodiments of the present invention. Furthermore, it will be understood that the problems to be solved and advantages of the present invention can be achieved by the means set forth in the claims and combinations thereof. [Means for solving the problem]

[0005] As a technical means for achieving the above-mentioned technical problem, a first aspect of the present disclosure provides a method for sharing a map correction history, the method including the steps of receiving from a first user terminal a first correction history generated based on an initial map and a first corrected map obtained by correcting the initial map, receiving from a second user terminal a second correction history generated based on the initial map and a second corrected map obtained by correcting the initial map, transmitting the second correction history to the first user terminal and transmitting the first correction history to the second user terminal, and reflecting the second correction history in real time in the first corrected map displayed on the first user terminal and the second corrected map displayed on the second user terminal based on the transmission result.

[0006] In addition, the second revision history may be reflected in real time on the first revised map displayed on the first user terminal to generate a first final map, and the first revision history may be reflected in real time on the second revised map displayed on the second user terminal to generate a second final map, and the first final map displayed on the first user terminal and the second final map displayed on the second user terminal may be synchronized in real time.

[0007] The sending step may also include converting the first revision history and the second revision history into a first key value and a second key value, respectively, corresponding to a specific string, and sending the first key value to the second user terminal and sending the second key value to the first user terminal.

[0008] The sending step may also include the step of sending the first key value to the second user terminal via a first intermediary server that communicates with the second user terminal.

[0009] Furthermore, the sending step may include a step of sending the first key value to the first user terminal via a first intermediary server that communicates with the first user terminal, and a step of sending the first key value to the second user terminal via a second intermediary server that receives the first key value from the first user terminal.

[0010] The sending step may also include a step of comparing the data size of the first revision history with a predetermined data size, and a step of sending the first key value to the second user terminal if the data size of the first revision history is larger than the predetermined data size based on the comparison result.

[0011] The transmitting step may also include a step of grouping a plurality of user terminals including the first user terminal into either a first user terminal group or a second user terminal group, and a step of determining whether to transmit the first key value to the second user terminal depending on whether the second user terminal is included in the first user terminal group or the second user terminal group.

[0012] The transmitting step may also include a step of grouping the initial map into either a first map group or a second map group depending on the type of the initial map, and a step of determining whether to transmit the first key value to the second user terminal depending on whether the initial map is included in the first map group or the second map group.

[0013] The sending step may also include a step of grouping a plurality of intermediary servers including the first intermediary server into either a first intermediary server group or a second intermediary server group, and a step of determining whether to send the first key value to the second user terminal via the first intermediary server depending on whether the first intermediary server is included in either the first intermediary server group or the second intermediary server group. [Effects of the Invention]

[0014] According to the above-described means for solving the problems of the present disclosure, the revision histories made by each user of a plurality of user terminals can be shared in real time, thereby preventing the possibility of losing the revision histories made by each user.

[0015] According to the means for solving the problems of the present disclosure described above, users of multiple user terminals can modify map data in real time, thereby improving business efficiency. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram illustrating a system for sharing map correction history according to one embodiment. [Figure 2] FIG. 2 is an exemplary diagram illustrating a method for sharing map correction history according to one embodiment. [Figure 3] FIG. 3 is an exemplary diagram illustrating a method for sharing map correction history according to one embodiment. [Figure 4] FIG. 4 is an exemplary diagram illustrating a method for sharing map revision histories according to the size of data containing the map revision histories, according to one embodiment. [Figure 5] FIG. 5 is a diagram illustrating an exemplary method for sharing a map correction history according to a group to which a first user terminal belongs, according to an embodiment. [Figure 6]FIG. 6 is an exemplary diagram illustrating how a map revision history is shared according to the group to which the original map belongs, according to one embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a method for sharing map correction history according to a group to which an intermediary server belongs, according to one embodiment. [Figure 8] FIG. 8 is a flowchart of a method for sharing map correction history according to one embodiment. [Figure 9] FIG. 9 is a block diagram of a key-value generation server according to one embodiment. BEST MODE FOR CARRYING OUT THE INVENTION

[0017] The present disclosure relates to a method and apparatus for sharing a map correction history. A method according to an embodiment of the present disclosure includes receiving, from a first user terminal, an initial map and a first correction history generated based on a first corrected map obtained by correcting the initial map, receiving, from a second user terminal, a second correction history generated based on the initial map and a second corrected map obtained by correcting the initial map, transmitting the second correction history to the first user terminal, transmitting the first correction history to the second user terminal, and, based on the results of the transmission, reflecting the second correction history in real time on the first corrected map displayed on the first user terminal and reflecting the first correction history in real time on the second corrected map displayed on the second user terminal. DETAILED DESCRIPTION OF THE INVENTION

[0018] The advantages and features of the present invention, as well as methods for achieving them, will become more apparent from the detailed description of the embodiments accompanied by the accompanying drawings. However, the present invention is not limited to the embodiments presented below, and may be embodied in different forms, and should be understood to encompass all modifications, equivalents, and alternatives within the spirit and technical scope of the present invention. The embodiments presented below are provided to fully disclose the present invention and fully convey the scope of the invention to those skilled in the art to which the present invention pertains. In describing the present invention, if it is determined that a detailed description of related publicly disclosed technology may obscure the gist of the present invention, such a detailed description will be omitted.

[0019] The terms used in this application are merely used to describe specific embodiments and are not intended to limit the present invention. The singular expressions include the plural expressions unless the context clearly dictates otherwise. In this application, terms such as "comprise" or "have" are intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described herein, and are understood not to preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0020] Some embodiments of the present disclosure may be represented by functional blocks and various processing steps. Some or all of these functional blocks may be implemented in various hardware and / or software configurations that perform specific functions. For example, the functional blocks of the present disclosure may be implemented by one or more microprocessors or by circuit configurations for a given function. For example, the functional blocks of the present disclosure may be implemented in various programming or scripting languages. The functional blocks may be implemented by algorithms executed by one or more processors. The present disclosure may employ conventional techniques for electronic configuration, signal processing, and / or data processing. Terms such as "mechanism," "element," "means," and "configuration" may be used broadly and are not limited to mechanical or physical configurations.

[0021] Furthermore, the connecting lines or members between components shown in the figures are merely exemplary functional and / or physical or circuit connections, and in an actual device the connections between components may be represented by various alternative or additional functional, physical, or circuit connections.

[0022] FIG. 1 is a diagram illustrating a system for sharing map correction history according to one embodiment.

[0023] The system 100 for sharing a map revision history according to one embodiment may include a key-value generation server 1000, at least one user terminal 2000, and an intermediary server 3000. Meanwhile, only components related to one embodiment are shown in the system 100 for sharing a map revision history illustrated in Fig. 1. Therefore, it will be obvious to those skilled in the art that the system 100 for sharing a map revision history may further include other general-purpose components in addition to the components illustrated in Fig. 1.

[0024] In the present invention, the revision history refers to changes applied during the map editing process via a user terminal. The revision history may represent the difference between the initial map and an intermediate edited map, the difference between the initial map and a final edited map, the difference between the first intermediate edited map and a second intermediate edited map, or the difference between the intermediate edited map and a final edited map.

[0025] The revision history of the present invention includes all changes that can be made in map editing work, such as the display or non-display of the component hierarchy, polygons, objects, icons, text, etc. in the map, as well as their color, opacity, size, and rotation.

[0026] The system 100 for sharing map revision history can correspond to a system in which the key value generation server 1000 shares the revision history generated when the first user of the first user terminal 2001 revised the initial map with at least one user terminal, such as the second user terminal 2002, via the intermediary server 3000.

[0027] According to one embodiment, the user terminal 2000 can receive an initial map from the key-value generation server 1000, and can receive a map correction input from the user to generate a corrected map. The user terminal 2000 can generate a correction history based on the initial map and the corrected map.

[0028] According to one embodiment, the key value generation server 1000 can convert the revision history received from the user terminal 2000 into a key value. The key value may correspond to a value that is converted, implied, or compressed by encoding the revision history according to a determined rule or method. For example, the key value may correspond to a specific string that is a set of a series of consecutive characters. The key value generation server 1000 can transmit the generated key value to the intermediation server 3000. Meanwhile, the key value generation server 1000 may correspond to a database that stores the revision history and the original map received from the user terminal 2000 or the intermediation server 3000.

[0029] According to one embodiment, the intermediary server 3000 can transmit the key value distributed from the key value generation server 1000 to at least one user terminal 2000 that communicates with the intermediary server 3000. For example, the intermediary server 3000 can distribute the revision history generated by the first user terminal 2001 to other user terminals connected to the intermediary server 3000, and share the revision history in real time.

[0030] When users of multiple user terminals simultaneously modify the initial map, different modified maps may be generated for each user, which may result in the loss of the modification history generated from each of the multiple user terminals. Therefore, as described above, the modification history generated from each of the multiple user terminals can be shared with each other in real time, thereby preventing the possibility of the modification history being lost.

[0031] According to one embodiment, the key value generation server 1000 can receive from the first user terminal 2001 a first revision history generated based on an initial map and a first revised map obtained by revising the initial map, and can receive from the second user terminal 2002 a second revision history generated based on the initial map and a second revised map obtained by revising the initial map. In addition, the key value generation server 1000 can transmit the second revision history to the first user terminal 2001 and the first revision history to the second user terminal 2002 via the intermediary server 3000. This allows the key value generation server 1000 to reflect the second revision history in real time in the first revised map displayed on the first user terminal 2001 and reflect the first revision history in real time in the second revised map displayed on the second user terminal 2002.

[0032] Finally, the second revision history may be reflected in real time on the first revised map displayed on the first user terminal 2001 to generate a first final map, and the first revision history may be reflected in real time on the second revised map displayed on the second user terminal 2002 to generate a second final map. At this time, the first final map displayed on the first user terminal 2001 and the second final map displayed on the second user terminal 2002 may be synchronized in real time.

[0033] The key-value generation server 1000, at least one user terminal 2000, and intermediary server 3000 can communicate with each other using a network. For example, the network may be a local area network (LAN), a wide area network (WAN), a value-added network (VAN), a mobile radio communication network, a satellite communication network, or any combination thereof. This network is a comprehensive data communication network that enables smooth communication between the network components shown in FIG. 1 and may include wired internet, wireless internet, and mobile wireless communication networks. Wireless communication may include, but is not limited to, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, ZigBee, Wi-Fi Direct (WFD), ultra wideband (UWB), infrared data association (IrDA), and near field communication (NFC).

[0034] For example, the user terminal 2000 may be, but is not limited to, a smartphone, a tablet PC, a PC, a smart TV, a mobile phone, a PDA (personal digital assistant), a laptop, a media player, a microserver, a GPS (global positioning system) device, an e-reader, a terminal for digital broadcasting, a navigation system, a kiosk, an MP3 player, a digital camera, a home appliance, a device equipped with a camera, and other mobile or non-mobile computing devices.

[0035] Meanwhile, each of the key-value generation server 1000 and the intermediation server 3000 can be implemented as a computer device or multiple computer devices that communicate via a network to provide instructions, code, files, content, services, and the like.

[0036] FIG. 2 is an exemplary diagram illustrating a method for sharing map correction history according to one embodiment.

[0037] According to one embodiment, the key value generation server 1000 can receive from a first user terminal an initial map and a revision history generated based on a revised map obtained by revising the initial map. The key value generation server 1000 can convert the generated revision history into a key value and transmit the key value to a first intermediary server that communicates with a second user terminal. Finally, the key value generation server 1000 can transmit the key value to the second user terminal via the first intermediary server.

[0038] Referring to FIG. 2, a first user terminal 2001 and a second user terminal 2002 may receive an initial map from the key-value generation server 1000. For example, a first user of the first user terminal 2001 may receive the initial map and generate an updated map by updating the initial map. The first user terminal 2001 may generate an update history based on the initial map and the updated map. For example, the first user terminal 2001 may generate an update history from the initial map and the updated map using a difference algorithm. The update history may be generated in various ways. For example, it may be generated in input units for a user's map update unit or in preset time units. The update history may be stored and transmitted in different input units.

[0039] The first user terminal 2001 can transmit the revision history to the first relay server 3001. Furthermore, the first relay server 3001 can transmit the revision history to the key value generation server 1000.

[0040] The key value generation server 1000 can convert the revision history received from the first intermediary server 3001 into a key value corresponding to a specific character string, and can transmit the key value to the second intermediary server 3002. Here, the key value can mean the revision history revised via the first user terminal that has been converted, implied, or compressed according to a predetermined rule or method. Meanwhile, in FIG. 2, the key value generation server 1000 is shown transmitting the key value only to the second intermediary server 3002, but is not limited thereto, and the key value can be transmitted to a plurality of other intermediary servers in addition to the second intermediary server 3002.

[0041] The second intermediation server 3002 can transmit the key value received from the key value generation server 1000 to the second user terminal 2002 that communicates with the second intermediation server 3002. Meanwhile, in FIG. 2, the key value generation server 1000 is shown transmitting the key value only to the second user terminal 2002, but this is not limited thereto, and the key value can be transmitted to a plurality of user terminals that communicate with the second intermediation server 3002. This allows the second user terminal 2002 to share the revision history generated by the first user terminal 2001 in real time.

[0042] Meanwhile, the second user terminal 2002 may generate a second revision history based on the initial map and a second revision map obtained by revising the initial map. In this case, the first revision history generated by the first user terminal 2001 can be reflected in the second revision map displayed on the second user terminal 2002 in real time. Finally, a second final map can be generated by reflecting the first revision history in the second revision map in real time. Similarly, the first user terminal 2001 can share the second revision history generated by the second user terminal 2002, and can reflect the second revision history generated by the second user terminal 2002 in the first revision map displayed on the first user terminal 2001 in real time. Finally, a first final map can be generated by reflecting the second revision history in the first revision map in real time.

[0043] FIG. 3 is an exemplary diagram illustrating a method for sharing map correction history according to one embodiment.

[0044] According to one embodiment, the key value generation server 1000 can receive from a first user terminal an initial map and a revision history generated based on a revised map obtained by revising the initial map. The key value generation server 1000 can convert the generated revision history into a key value and transmit the key value to the first user terminal via a first intermediary server that communicates with the first user terminal. Finally, the key value generation server can transmit the key value to a second user terminal via a second intermediary server that received the key value from the first user terminal.

[0045] 3, the first user terminal 2001 and the second user terminal 2002 can receive an initial map from the key-value generation server 1000. For example, the first user of the first user terminal 2001 can receive the initial map and generate a revised map by modifying the initial map. The first user terminal 2001 can generate a revision history based on the initial map and the revised map. For example, the first user terminal 2001 can generate a revision history from the initial map and the revised map using a difference algorithm.

[0046] The first user terminal 2001 can transmit the revision history to the first relay server 3001. Furthermore, the first relay server 3001 can transmit the revision history to the key value generation server 1000.

[0047] The key value generation server 1000 can convert the revision history received from the first intermediary server 3001 into a key value corresponding to a specific character string, and can transmit the key value to the first intermediary server 3001 that communicates with the first user terminal. For example, the first intermediary server can correspond to an HTTP server, and the key value generation server 1000 can transmit the key value to the first intermediary server in the form of an HTTP response.

[0048] First intermediary server 3001 can transmit the key value received from key value generation server 1000 to first user terminal 2001, which communicates with first intermediary server 3001. First user terminal 2001 can transmit the key value received from first intermediary server 3001 to second intermediary server 3002. Meanwhile, first intermediary server 3001 and second intermediary server 3002 may each be configured to be included in a single server, or may each correspond to separate servers.

[0049] The second intermediary server 3002 can transmit the key value received from the key value generation server 1000 to the second user terminal 2002 that communicates with the second intermediary server 3002. For example, the second intermediary server 3002 may correspond to a streaming server. Meanwhile, in FIG. 2, the key value generation server 1000 is shown transmitting the key value only to the second user terminal 2002, but is not limited to this and can transmit the key value to multiple user terminals that communicate with the second intermediary server 3002. This allows the second user terminal 2002 to share the modification history generated by the first user terminal.

[0050] Meanwhile, the second user terminal 2002 may generate a second revision history based on the initial map and a second revision map obtained by revising the initial map. In this case, the first revision history generated by the first user terminal 2001 can be reflected in the second revision map displayed on the second user terminal 2002 in real time. Finally, a second final map can be generated by reflecting the first revision history in the second revision map in real time. Similarly, the first user terminal 2001 can share the second revision history generated by the second user terminal 2002, and can reflect the second revision history generated by the second user terminal 2002 in the first revision map displayed on the first user terminal 2001 in real time. Finally, a first final map can be generated by reflecting the second revision history in the first revision map in real time.

[0051] FIG. 4 is an exemplary diagram illustrating a method for sharing map revision histories according to the size of data containing the map revision histories, according to one embodiment.

[0052] According to one embodiment, the key-value generation server 1000 can determine whether to convert the revision history into a key-value and transmit it, depending on the data size including the revision history. The embodiment in Fig. 4 can be applied to each of the above-mentioned embodiments in Figs. 1 to 3.

[0053] Referring to FIG. 4, the revision history can be generated from the first user terminal, and the key-value generation server 1000 that receives the revision history can compare the size of the revision history with a preset data size.

[0054] When the size of the revision history is equal to or larger than a preset data size, the key value generation server 1000 can operate to convert the revision history and transmit the generated key value to the second user terminal 2002. When the size of the revision history is smaller than a preset data size, the key value generation server 1000 can operate to transmit the revision history as is to the second user terminal 2002 without converting it into a key value.

[0055] FIG. 5 is a diagram illustrating an exemplary method for sharing a map correction history according to a group to which a first user terminal belongs, according to an embodiment.

[0056] According to one embodiment, the key-value generation server 1000 can transmit a key-value to a second user terminal depending on whether the first user terminal is included in the first user terminal group or the second user terminal group. The embodiment of Fig. 5 can be applied to each of the above-mentioned embodiments of Figs. 1 to 3.

[0057] Referring to FIG. 5, the revision history may be generated from a first user terminal 2001 .

[0058] First, the key value generation server 1000 can group a plurality of user terminals including the first user terminal 2001 into either a first user terminal group or a second user terminal group. In addition, the key value generation server 1000 can determine whether the first user terminal 2001 is included in either the first user terminal group or the second user terminal group.

[0059] When the first user terminal 2001 is included in the first user terminal group, the key value generation server 1000 can operate to transmit the key value generated by converting the revision history to the second user terminal 2002. On the other hand, when the first user terminal 2001 is included in the second user terminal group, the key value generation server 1000 can operate to confirm whether the key value generated by converting the revision history is approved and then transmit the key value to the second user terminal 2002. For example, when the first user terminal 2001 is included in the second user terminal group, the key value can be transmitted to the second user terminal 2002 after first receiving approval for the key value transmission from a third user terminal having approval authority.

[0060] FIG. 6 is an exemplary diagram illustrating how a map revision history is shared according to the group to which the original map belongs, according to one embodiment.

[0061] According to one embodiment, the key-value generation server 1000 can transmit a key-value to the second user terminal depending on which of the first map group and the second map group the initial map is included in. The embodiment in Fig. 6 can be applied to each of the above-mentioned embodiments in Figs. 1 to 3.

[0062] 6, the key value generation server 1000 can group the initial map into either a first map group or a second map group depending on the type or data size of the initial map. The key value generation server 1000 can also determine whether the initial map is included in either the first map group or the second map group.

[0063] When the first map is included in the first map group, the key value generation server 1000 can operate to transmit the key value generated by converting the revision history to the second user terminal 2002. On the other hand, when the first map is included in the second map group, the key value generation server 1000 can operate to confirm whether or not to approve the key value generated by converting the revision history, and then transmit the key value to the second user terminal 2002. For example, when the first map is included in the second map group, the key value can be transmitted to the second user terminal 2002 after first receiving approval for the key value transmission from a third user terminal having approval authority.

[0064] On the other hand, the revision history or the key value generated by converting the revision history can include information that can identify the type of the original map, and the key value generation server 1000 can determine whether to send the key value to the second user terminal 2002 based on the information that can identify the type of the original map.

[0065] FIG. 7 is a diagram illustrating an example of a method for sharing map correction history according to a group to which an intermediary server belongs, according to one embodiment.

[0066] According to one embodiment, when the key value generation server 1000 transmits the key value obtained by converting the revision history to the relay server, the key value can be transmitted to the second user terminal via the relay server depending on whether the relay server is included in the first relay server group or the second relay server group. The embodiment of Fig. 7 can be applied to each of the above-mentioned embodiments of Figs. 1 to 3.

[0067] 7, the key value generation server 1000 can group a plurality of relay servers into either a first relay server group or a second relay server group. The key value generation server 1000 can also determine whether the relay server to which the key value converted from the modification history is to be sent is included in either the first relay server group or the second relay server group.

[0068] When the intermediary server is included in the first intermediary server group, the key value generation server 1000 can operate so that the key value generated by converting the revision history is sent to the intermediary server communicating with the second user terminal 2002. On the other hand, when the intermediary server is included in the second intermediary server group, the key value generation server 1000 can operate so that the key value generated by converting the revision history is not sent to the intermediary server communicating with the second user terminal 2002.

[0069] For example, the intermediary server can be classified into a first intermediary server group or a second intermediary server group depending on whether all user terminals communicating with the intermediary server have the authority to receive the key value. If all user terminals communicating with the intermediary server have the authority to receive the key value, the intermediary server may be included in the first intermediary server group, and if at least one user terminal communicating with the intermediary server does not have the authority to receive the key value, the intermediary server may be included in the second intermediary server group.

[0070] For example, if the intermediary server is included in the second intermediary server group, the key value can be transmitted to the intermediary server after first receiving approval for the key value transmission from a third user terminal having approval authority.

[0071] FIG. 8 is a flowchart of a method for sharing map correction history according to one embodiment.

[0072] Referring to FIG. 8, in step 810, the key value generation server 1000 may receive from the first user terminal a first modification history generated based on the initial map and a first modified map that modifies the initial map.

[0073] In step 820, the key-value generation server 1000 can receive, from the second user terminal, a second revision history generated based on the initial map and a second revised map that has revised the initial map.

[0074] In step 830, the key-value generation server 1000 can transmit the second modification history to the first user terminal and the first modification history to the second user terminal.

[0075] According to one embodiment, the key value generation server 1000 can convert the first revision history and the second revision history into a first key value and a second key value corresponding to a specific string, respectively, and send the first key value to the second user terminal and send the second key value to the first user terminal.

[0076] According to one embodiment, the key value generation server 1000 can transmit the first key value to the second user terminal via a first intermediary server that communicates with the second user terminal.

[0077] According to one embodiment, the key value generation server 1000 can transmit a first key value to a first user terminal via a first intermediary server that communicates with the first user terminal, and can transmit the first key value to a second user terminal via a second intermediary server that has received the first key value from the first user terminal.

[0078] According to one embodiment, the key value generation server 1000 compares the data size of the first revision history with a preset data size, and if the data size of the first revision history is greater than the preset data size based on the comparison result, the key value generation server 1000 can send the first key value to the second user terminal.

[0079] According to one embodiment, the key value generation server 1000 groups a plurality of user terminals, including a first user terminal, into either a first user terminal group or a second user terminal group, and can determine whether to send the first key value to the second user terminal depending on whether the second user terminal is included in either the first user terminal group or the second user terminal group.

[0080] According to one embodiment, the key value generation server 1000 groups the initial map into either a first map group or a second map group depending on the type of the initial map, and can determine whether to send the first key value to the second user terminal depending on whether the initial map is included in the first map group or the second map group.

[0081] According to one embodiment, the key value generation server 1000 groups multiple intermediary servers, including the first intermediary server, into either a first intermediary server group or a second intermediary server group, and can determine whether to send the first key value to the second user terminal via the first intermediary server depending on whether the intermediary server is included in the first intermediary server group or the second intermediary server group.

[0082] In step 840, the key value generation server 1000 can, based on the transmission result, reflect the second revision history in real time on the first revised map displayed on the first user terminal, and can reflect the first revision history in real time on the second revised map displayed on the second user terminal.

[0083] According to an embodiment, the second revision history may be reflected in real time on the first revised map displayed on the first user terminal to generate a first final map, and the first revision history may be reflected in real time on the second revised map displayed on the second user terminal to generate a second final map. Also, the first final map displayed on the first user terminal and the second final map displayed on the second user terminal may be synchronized in real time.

[0084] FIG. 9 is a block diagram of a key-value generation server according to one embodiment.

[0085] 9, a key-value generation server 900 can include a communication unit 910, a processor 920, and a DB 930. Only components relevant to the embodiment are shown in the key-value generation server 900 in Fig. 9. Therefore, it can be understood by those skilled in the art that the key-value generation server 900 can further include other general-purpose components in addition to the components shown in Fig. 9.

[0086] The communication unit 910 may include one or more components that enable wired / wireless communication with an external server or device. For example, the communication unit 910 may include at least one of a short-range communication unit (not shown), a mobile communication unit (not shown), and a broadcast receiving unit (not shown).

[0087] The DB 930 is hardware that stores various data processed within the key-value generation server 900, and can store programs for processing and controlling the processor 920. The DB 930 can store payment information, user information, etc.

[0088] DB930 may include random access memory (RAM), such as dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM, Blu-ray or other optical disk storage, hard disk drive (HDD), solid state drive (SSD), or flash memory.

[0089] The processor 920 controls the overall operation of the key-value generation server 900. For example, the processor 920 can generally control the input unit (not shown), the display (not shown), the communication unit 910, the DB 930, etc. by executing a program stored in the DB 930. The processor 920 can control the operation of the lane determination device 900 by executing a program stored in the DB 930.

[0090] The processor 920 can control at least a part of the operations of the key-value generation server described above with reference to FIGS.

[0091] The processor 920 may be implemented using at least one of application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, and electrical units for performing other functions.

[0092] Embodiments of the present invention may be implemented in the form of a computer program executable on a computer via various components, and such a computer program may be recorded on a computer-readable medium, including magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, etc.

[0093] On the other hand, the computer programs may be those specially designed and constructed for the purposes of the present invention, or they may be those well known and available to those skilled in the computer software art. Examples of computer programs include not only machine code, such as produced by a compiler, but also high-level language code that can be executed by a computer using an interpreter, etc.

[0094] According to one embodiment, methods according to various embodiments of the present disclosure may be provided in a computer program product. The computer program product may be traded as a commodity between a seller and a buyer. The computer program product may be distributed in the form of a device-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)) or distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store server, or an intermediary server.

[0095] Unless explicitly stated or stated to the contrary, steps constituting a method according to the present invention may be performed in any suitable order. The order in which the steps are described is not necessarily intended to limit the present invention. The use of all examples or exemplary terms (e.g., etc.) in the present invention is merely for the purpose of explaining the present invention in detail, and the scope of the present invention is not limited by such examples or exemplary terms unless otherwise limited by the claims. Furthermore, those skilled in the art will recognize that various modifications, combinations, and variations can be made according to design conditions and factors within the scope of the appended claims or their equivalents.

[0096] Therefore, the spirit of the present invention should not be limited to the above-described embodiments, and all scopes equivalent to or modified equivalently from the scope of the claims, as well as the scope of the claims described below, can be said to belong to the spirit of the present invention.

Claims

1. In the method for sharing map correction history, receiving, from a first user terminal, an initial map and a first revision history generated based on a first revised map that has revised the initial map; receiving, from a second user terminal, a second revision history generated based on the initial map and a second revised map that has revised the initial map; transmitting the second revision history to the first user terminal and the first revision history to the second user terminal; and reflecting the second revision history in real time on the first revision map displayed on the first user terminal based on the transmission result, and reflecting the first revision history in real time on the second revision map displayed on the second user terminal.

2. The second revision history is reflected in real time on the first revised map displayed on the first user terminal, thereby generating a first final map; The first revision history is reflected in real time on the second revised map displayed on the second user terminal, thereby generating a second final map; The method of claim 1 , wherein the first final map displayed on the first user terminal and the second final map displayed on the second user terminal are synchronized in real time.

3. The transmitting step includes: converting the first revision history and the second revision history into a first key value and a second key value corresponding to a specific character string, respectively; transmitting the first key-value to the second user terminal and transmitting the second key-value to the first user terminal.

4. The transmitting step includes: The method of claim 3 , further comprising: transmitting the first key-value to the second user terminal via a first intermediary server that communicates with the second user terminal.

5. The transmitting step includes: transmitting the first key-value to the first user terminal via a first intermediary server that communicates with the first user terminal; The method of claim 3 , further comprising: transmitting the first key value to the second user terminal via a second intermediary server that has received the first key value from the first user terminal.

6. The transmitting step includes: comparing the data size of the first revision history with a preset data size; The method of claim 3, further comprising: if, based on the comparison result, the data size of the first revision history is greater than the preset data size, sending the first key value to the second user terminal.

7. The transmitting step includes: grouping a plurality of user terminals including the first user terminal into one of a first user terminal group and a second user terminal group; The method of claim 3, further comprising: determining whether to send the first key value to the second user terminal depending on whether the second user terminal is included in either the first user terminal group or the second user terminal group.

8. The transmitting step includes: grouping the initial maps into either a first map group or a second map group according to the type of the initial maps; The method of claim 3, further comprising: determining whether to send the first key value to the second user terminal depending on whether the first map is included in the first map group or the second map group.

9. The transmitting step includes: A step of grouping a plurality of intermediation servers including the first intermediation server into either a first intermediation server group or a second intermediation server group; The method of claim 4, further comprising a step of determining whether to send the first key value to the second user terminal via the first intermediary server depending on whether the first intermediary server is included in either the first intermediary server group or the second intermediary server group.

10. In a device for sharing map correction history, a memory for storing at least one program; at least one processor that shares the revision history by executing the at least one program; The at least one processor receiving, from a first user terminal, an initial map and a first revision history generated based on a first revised map obtained by revising the initial map; receiving, from a second user terminal, a second revision history generated based on the initial map and a second revised map obtained by revising the initial map; Sending the second revision history to the first user terminal and sending the first revision history to the second user terminal; and a device that, based on the transmission result, reflects the second revision history in real time on the first revision map displayed on the first user terminal, and reflects the first revision history in real time on the second revision map displayed on the second user terminal.

Images