Method and system for address transmission between mobile devices and automatic navigation execution

Abstract

The present specification describes a method for address transmission and automatic navigation execution between mobile terminals, comprising: a step in which a server establishes a session between a main terminal and a receiving terminal; a step in which the main terminal accepts a first delivery order and obtains a first address included in the first delivery order; a step in which the main terminal generates a first payload based on a delivery platform identifier of the first delivery order and the first address; a step in which the main terminal transmits the first payload to the receiving terminal through the server; and a step in which the receiving terminal executes a first navigation application associated with the delivery platform identifier included in the first payload and automatically inputs the first address to automatically start route guidance.

Description

Technology Field

[0001] This specification relates to navigation execution technology, and more specifically, to a method and system for transmitting the destination address of a delivery order accepted at a main terminal to a receiving terminal via a server, and for automatically inputting the address at the receiving terminal to execute navigation guidance. Background Technology

[0003] Generally, delivery personnel frequently use navigation apps (e.g., Kakao Map, Tmap, Kakao Navi) to process delivery orders quickly. Traditionally, the primary method utilized was mirroring smartphone navigation screens via in-vehicle connectivity devices such as Android Auto or Apple CarPlay. However, this method had the inconvenience of requiring the vehicle's ignition to operate and preventing the smartphone from being used for other purposes while Bluetooth-based mirroring was in use.

[0004] In addition, the performance of in-vehicle devices is often inferior to that of standard smartphones, resulting in slow boot speeds when running navigation or playing multimedia. Consequently, users have experienced issues with overheating and battery drain. In particular, in situations where delivery personnel must process multiple orders within a limited time, these technical limitations have had a negative impact on work efficiency and safety.

[0005] Against this backdrop, some delivery workers utilized two or more smartphones simultaneously. That is, they accepted orders via a delivery app on a main device while running navigation on a separate device. However, even in this case, users had to manually enter the destination address into the receiving device, which posed a risk of safety accidents as they had to operate the screen while driving. Therefore, a technical means was required to automatically transmit the order address accepted on the main device to another device and to enable navigation on that device without separate operation. The problem to be solved

[0007] The purpose of this specification is to provide a system that transmits an order address accepted at a main terminal to a receiving terminal without separate operation and automatically executes navigation guidance at the receiving terminal.

[0008] In addition, the purpose of this specification is to propose a method for automatically synchronizing addresses between terminals through server-based linkage and enabling immediate navigation execution on the receiving terminal.

[0009] The technical problems that this specification aims to solve are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this specification belongs from the detailed description of the specification below. means of solving the problem

[0011] One aspect of the present specification may include a method for address transmission and automatic navigation execution between mobile terminals, comprising: a step in which a server establishes a session between a main terminal and a receiving terminal; a step in which the main terminal accepts a first delivery order and obtains a first address included in the first delivery order; a step in which the main terminal generates a first payload based on a delivery platform identifier of the first delivery order and the first address; a step in which the main terminal transmits the first payload to the receiving terminal through the server; and a step in which the receiving terminal executes a first navigation application associated with the delivery platform identifier included in the first payload and automatically inputs the first address to automatically start route guidance.

[0012] Additionally, the step of establishing the session may include: receiving unique user authentication information from the main terminal and the receiving terminal, respectively; managing a device list based on the unique user authentication information; and recording binding information between the main terminal and the receiving terminal.

[0013] Additionally, the step of obtaining the first address may include: a step of analyzing the UI structure of a navigation application displayed on the screen of the main terminal; and a step of extracting a text string corresponding to the first address based on a route card container, a search bar, or a destination badge.

[0014] Additionally, the first payload may include a user identifier (UID), transmitting terminal information, receiving terminal information, the delivery platform identifier, address text, timestamp, and hash value.

[0015] Additionally, the step of automatically starting the route guidance may include: the step of the receiving terminal automatically detecting and clicking a route finding button on the screen of the first navigation application using an accessibility service; and the step of automatically detecting and clicking a guidance start button on the screen of the first navigation application.

[0016] Additionally, the method further includes the steps of: the main terminal accepting a second delivery order and obtaining a second address included in the second delivery order; the main terminal generating a second payload based on the delivery platform identifier of the second delivery order and the second address; the main terminal transmitting the second payload to the receiving terminal through the server; and the receiving terminal executing a second navigation application associated with the delivery platform identifier of the second delivery order included in the second payload, and automatically starting route guidance by automatically entering the second address; wherein the first navigation application may be different from the second navigation application.

[0017] Another aspect of the present specification may include, in a system for address transmission and navigation automatic execution between mobile terminals, a main terminal that accepts a delivery order and obtains a destination address included in the delivery order, and generates and transmits a payload including a delivery platform identifier and the destination address; a server that establishes a session between the main terminal and a receiving terminal and transmits the payload to the receiving terminal; and the receiving terminal that receives the payload from the server, executes a navigation application associated with the delivery platform identifier included in the payload, and automatically initiates route guidance by automatically clicking a route finding button and a guidance start button using an accessibility service. Effects of the invention

[0019] According to an embodiment of the present specification, a system can be provided that transmits an order address accepted at a main terminal to a receiving terminal without separate operation and automatically executes navigation guidance at the receiving terminal.

[0020] In addition, according to an embodiment of the present specification, addresses between terminals can be automatically synchronized through server-based linkage, and navigation can be executed immediately on the receiving terminal.

[0021] The effects obtainable in this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which this specification belongs from the description below. Brief explanation of the drawing

[0023] FIG. 1 is a block diagram for illustrating an electronic device related to the present specification. FIG. 2 illustrates the operation of a system for address transmission between mobile terminals and automatic navigation execution according to one embodiment of the present specification. FIG. 3 illustrates a method for obtaining the address of a main terminal to which the present specification may be applied. FIG. 4 illustrates an automatic route guidance method for a receiving terminal to which the present specification may be applied. Specific details for implementing the invention

[0024] Hereinafter, embodiments disclosed in this specification will be described in detail with reference to the attached drawings. Identical or similar components regardless of drawing symbols will be assigned the same reference number, and redundant descriptions thereof will be omitted. The suffixes "module" and "part" used for components in the following description are assigned or used interchangeably solely for the ease of drafting the specification and do not inherently possess distinct meanings or roles. Furthermore, in describing the embodiments disclosed in this specification, if it is determined that a detailed description of related prior art could obscure the essence of the embodiments disclosed in this specification, such detailed description will be omitted. Additionally, the attached drawings are intended only to facilitate understanding of the embodiments disclosed in this specification; the technical concept disclosed in this specification is not limited by the attached drawings, and it should be understood that they include all modifications, equivalents, and substitutions that fall within the concept and technical scope of this specification.

[0025] Terms including ordinal numbers, such as first, second, etc., may be used to describe various components, but said components are not limited by said terms. These terms are used solely for the purpose of distinguishing one component from another.

[0026] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0027] A singular expression includes a plural expression unless the context clearly indicates otherwise.

[0028] In this application, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0029] FIG. 1 is a block diagram for illustrating an electronic device related to the present specification.

[0030] The above electronic device (100) may include a wireless communication unit (110), an input unit (120), a sensing unit (140), an output unit (150), an interface unit (160), a memory (170), a control unit (180), and a power supply unit (190), etc. Since the components illustrated in FIG. 1 are not essential for implementing the electronic device, the electronic device described herein may have more or fewer components than those listed above.

[0031] More specifically, among the above components, the wireless communication unit (110) may include one or more modules that enable wireless communication between the electronic device (100) and a wireless communication system, between the electronic device (100) and another electronic device (100), or between the electronic device (100) and an external server. Additionally, the wireless communication unit (110) may include one or more modules that connect the electronic device (100) to one or more networks.

[0032] This wireless communication unit (110) may include at least one of a broadcast receiving module (111), a mobile communication module (112), a wireless internet module (113), a short-range communication module (114), and a location information module (115).

[0033] The input unit (120) may include a camera (121) or video input unit for inputting a video signal, a microphone (122) or audio input unit for inputting an audio signal, and a user input unit (123, e.g., a touch key, a mechanical key, etc.) for receiving information from a user. Voice data or image data collected from the input unit (120) may be analyzed and processed into a control command by the user.

[0034] The sensing unit (140) may include one or more sensors for sensing at least one of information within the electronic device, information about the surrounding environment surrounding the electronic device, and user information. For example, the sensing unit (140) may include at least one of a proximity sensor (141), an illumination sensor (142), a touch sensor, an acceleration sensor, a magnetic sensor, a gravity sensor (G-sensor), a gyroscope sensor, a motion sensor, an RGB sensor, an infrared sensor (IR sensor: infrared sensor), a fingerprint sensor (finger scan sensor), an ultrasonic sensor, an optical sensor (e.g., see camera (121)), a microphone (see 122), a battery gauge, an environmental sensor (e.g., a barometer, a hygrometer, a thermometer, a radiation detection sensor, a heat detection sensor, a gas detection sensor, etc.), and a chemical sensor (e.g., an electronic nose, a healthcare sensor, a biometric sensor, etc.). Meanwhile, the electronic device disclosed in this specification can utilize information sensed by at least two of these sensors in combination.

[0035] The output unit (150) is intended to generate output related to sight, hearing, or touch, and may include at least one of a display unit (151), an acoustic output unit (152), a haptic module (153), and an optical output unit (154). The display unit (151) may form a layered structure with a touch sensor or be formed integrally to implement a touch screen. Such a touch screen functions as a user input unit (123) that provides an input interface between the electronic device (100) and the user, and at the same time can provide an output interface between the electronic device (100) and the user.

[0036] The interface section (160) serves as a passage for various types of external devices connected to the electronic device (100). This interface section (160) may include at least one of a wired / wireless headset port, an external charger port, a wired / wireless data port, a memory card port, a port for connecting a device equipped with an identification module, an audio I / O (Input / Output) port, a video I / O (Input / Output) port, and an earphone port. In response to an external device being connected to the interface section (160), the electronic device (100) can perform appropriate control related to the connected external device.

[0037] Additionally, the memory (170) stores data that supports various functions of the electronic device (100). The memory (170) can store a number of application programs (or applications) running on the electronic device (100), data for the operation of the electronic device (100), and commands. At least some of these application programs may be downloaded from an external server via wireless communication. Also, at least some of these application programs may exist on the electronic device (100) from the time of shipment for the basic functions of the electronic device (100) (e.g., phone incoming and outgoing functions, message receiving and outgoing functions). Meanwhile, the application programs may be stored in the memory (170), installed on the electronic device (100), and driven by the control unit (180) to perform the operation (or function) of the electronic device.

[0038] In addition to operations related to the application program, the control unit (180) typically controls the overall operation of the electronic device (100). The control unit (180) can provide or process appropriate information or functions to the user by processing signals, data, information, etc. that are input or output through the components described above, or by running an application program stored in memory (170).

[0039] Additionally, the control unit (180) can control at least some of the components examined together with FIG. 1 in order to run an application program stored in memory (170). Furthermore, the control unit (180) can operate at least two or more of the components included in the electronic device (100) in combination with each other to run the application program.

[0040] The power supply unit (190) receives external power and internal power under the control of the control unit (180) and supplies power to each component included in the electronic device (100). This power supply unit (190) includes a battery, and the battery may be a built-in battery or a replaceable battery.

[0041] At least some of the above components may operate in cooperation with each other to implement the operation, control, or control method of an electronic device according to various embodiments described below. Additionally, the operation, control, or control method of the electronic device may be implemented on the electronic device by running at least one application program stored in the memory (170).

[0042] In this specification, the electronic device (100) may be collectively referred to as a server, and the server may include a cloud server. Additionally, the terminal may include all or part of the configuration of the electronic device (100), and may include a tablet PC.

[0043] FIG. 2 illustrates the operation of a system for address transmission between mobile terminals and automatic navigation execution according to one embodiment of the present specification.

[0044] Referring to FIG. 2, the system (200) may include a main terminal, a server, and a receiving terminal.

[0045] Main terminal The main terminal is a transmitting terminal that accepts delivery orders and obtains destination addresses, and is responsible for uploading the received addresses to a server. The main terminal runs a delivery platform application such as Baedal Minjok or Coupang, and when an order acceptance event occurs, it can extract the pickup or destination address of the corresponding order.

[0046] serverIt is implemented in a cloud environment such as Google Cloud (Firebase) and is responsible for establishing a session between the main terminal and the receiving terminal, managing transmitted address data as a neutral payload, and delivering it to the receiving terminal in real time. It is also responsible for user authentication, device list management, and executing data log storage and deletion policies.

[0047] receiving terminal A terminal is a device that receives address data from a server and executes an appropriate navigation application based on a service identifier. For example, a Baemin call can execute Kakao Navi, and a Coupang call can execute Naver Navi. The receiving terminal can start route guidance without user intervention by automatically clicking the "Find Directions" and "Start Guidance" buttons using accessibility services in the executed navigation app.

[0048] The server establishes a session for the main terminal and the receiving terminal (S2010).

[0049] The server can establish a session between the main terminal and the receiving terminal. For example, each terminal provides unique user credentials, such as a Google UID, to the server, and the server can manage a list of devices based on this. Through this, it is possible to determine which terminal is the sender and which is the receiver.

[0050] In addition, the server records binding information between terminals to enable data transmission from the main terminal to a specific receiving terminal. For example, a user can select the sending device through the app UI, and the server can configure a routing table based on that selection information.

[0051] During the session establishment phase, session expiration times, device-specific data deletion cycles, and re-authentication procedures can be managed together to ensure data security and policy compliance. This prevents unnecessary data from being stored on the server for extended periods and enables secure data transmission.

[0052] When the main terminal accepts delivery call A, it obtains a first address based on delivery call A (S2020).

[0053] The main terminal may include one or more delivery platform applications. For example, when a user accepts a delivery call (Baemin application) through the main terminal, the main terminal extracts the pickup or destination address included in the order. At this time, the main terminal can obtain the address string through a text view on the screen or parent node traversal.

[0054] The extracted address can be structured with hash processing and timestamps to prevent duplication. This serves as foundational data to block the repeated execution of the same address.

[0055] The main terminal assigns a provider field (e.g., "BAEMIN") to the corresponding address, preparing to branch to allow the receiving terminal to execute navigation later.

[0056] The main terminal generates a first payload based on A delivery and the first address (S2030).

[0057] The main terminal generates a first payload including the acquired address and provider. For example, the payload may be configured in the form of {uid, sender, receiver, provider, address_text, ts, hash}.

[0058] This first payload is uploaded to a cloud server such as Firebase, and the server prepares to deliver it to the receiving terminal. The server stores the record in the user logs so that it can be utilized for auditing and retry logic. Additionally, when the payload is generated, the main terminal can block unauthorized data transmission by verifying that the user account and device information match.

[0059] The main terminal transmits the first payload to the receiving terminal via the server (S2040).

[0060] The main terminal uplinks the first payload via a server (e.g., Firebase). The server performs validation (e.g., UID / binding matching) and can store it as an address record along with user records. For example, the server can deliver it to the receiving terminal in real-time as an ADDRESS_NOTIFY event (push / listener). At this point, the format remains neutral, and no app-specific scheme / URI processing is performed.

[0061] Additionally, the server may log the delivery success / failure status and, in the event of failure, place it in a retry queue or return an error code. Long-term unreceived / expired records may be deleted according to policy.

[0062] The receiving terminal guides the user to a route through the first navigation based on the first payload (S2050).

[0063] The receiving terminal checks the provider in the payload and branches to the corresponding navigation execution mode. For example, if the provider is BAEMIN, it can branch to the Kakao (Map / Navi) execution mode. In this case, the receiving terminal can convert the address into a geo:0,0?q=<address> URI and pass it to the Kakao package.

[0064] In addition, the receiving terminal can automatically click the "Find Route" button of the first navigation and, subsequently, automatically click the "Start Guidance" button. For example, when the Kakao Navi screen comes to the foreground, the accessibility service is activated to detect and automatically click the "Find Route" button based on text / content description. The "Start Guidance" button that is subsequently displayed is also clicked in the same manner.

[0065] For example, the receiving terminal can perform a search loop up to 24 times at 1-second intervals to account for button delay / non-exposure. Additionally, if detection is not possible, coordinate clicks with resolution / DPI correction applied can be used as a limited auxiliary path (Priority: UI-based > Coordinate-based).

[0066] When the main terminal accepts the B delivery call, it obtains a second address based on the B delivery call (S2060).

[0067] For example, the main terminal can detect a Coupang call acceptance event and extract a second address from the screen. In this case, "COUPANG" can be set in the provider field to prepare for subsequent routing to Naver Navi.

[0068] The main terminal generates a second payload based on B delivery and the second address (S2070).

[0069] The main terminal can generate a second payload similar to the S2030 operation. However, the provider item may be changed to indicate the B delivery application. For example, the main terminal can generate a second payload of {uid, sender, receiver, provider=COUPANG, address_text, ts, hash}.

[0070] The main terminal transmits the second payload to the receiving terminal via the server (S2080).

[0071] The receiving terminal guides the user to a route through the second navigation based on the second payload (S2090).

[0072] For example, the receiving terminal can check provider=COUPANG and branch to the Naver Navi execution mode. At this time, the receiving terminal can convert the address into a Naver Navi-specific scheme / intent (e.g., naver-navi: / / route?destination=<binary data, 5 bytes>). After entering the navigation screen, the main terminal can detect and automatically click "Find Directions / Start Guidance" through accessibility services. This allows route guidance to start immediately without user intervention.

[0073] Additionally, the system (200) may further include a 'recent app return function'. This function allows the user to automatically return to the application they were previously using after navigation execution and / or address transmission is completed on the main terminal (or transmitting terminal).

[0074] For example, when the main terminal completes the address transmission, it calls the GLOBAL_ACTION_RECENTS action of the Android accessibility service to control the automatic switching to the app screen the user was using immediately before (e.g., Baedal Minjok, Coupang Eats, Yogiyo, etc.). Accordingly, the user can maintain a continuous workflow by having the control app (e.g., AutoNavi) temporarily displayed in the foreground and then returning to the original app immediately after the task is completed.

[0075] This feature enables users to continue their existing tasks in the delivery app without separate screen switching or manual operation, thereby achieving continuous workflow and UX automation effects that existing navigation automation systems could not provide.

[0076] In addition, in the system (200) according to the embodiment of the present specification, the main terminal and the receiving terminal are physically separated from each other and are separate devices, but according to another embodiment, both the main terminal function and the receiving terminal function can be performed within a single terminal.

[0077] In this case, the terminal independently obtains the order address and can automatically launch a navigation application within the same terminal to begin route guidance. This configuration enables automatic navigation execution without the need for separate communication between terminals, allowing for stable service provision even in areas with unstable communication environments.

[0078] FIG. 3 illustrates a method for obtaining the address of a main terminal to which the present specification may be applied.

[0079] Referring to FIG. 3, the main terminal can extract a destination address string from the screen depending on the type of navigation / map application executed immediately after accepting a call.

[0080] Referring to Fig. 3(a), some navigation applications may display destination information in the form of a route card (Container) on a bottom panel. In this case, the main terminal first identifies the parent container node of the route card and collects destination address tokens, such as road names, building names, and house numbers, from its child nodes. The collected text is combined while preserving its order, and unnecessary strings, such as advertising phrases or recommendation labels, are removed through regular expression-based filtering. Through this, a complete address string can be obtained even on a route card-based screen.

[0081] Referring to FIG. 3(b), the destination address may be directly displayed in the search bar or the top address bar. The main terminal reads the address string by searching the text view in the top search area. At this time, a regular expression-based address verification may be performed to determine whether it is a simple place name (e.g., "Seoul Station") or an actual road name / lot number-based address (e.g., "122-28, Bongnae-dong 2-ga, Jung-gu, Seoul"). The verified address undergoes normalization processes such as removing spaces and special characters and standardizing lot numbers / road names, and is subsequently inserted as a core field of the payload for server transmission.

[0082] Referring to Fig. 3(c), the destination address may be displayed centered around the arrival badge or summary panel. In this case, the main terminal first recognizes the "Arrival" label as an anchor node and searches for sibling containers adjacent to that label to obtain the destination address string. This method can operate reliably even if the UI structure changes or the resource ID is updated, and if necessary, detection is performed by combining the ContentDescription attribute or boundary information. As a result, reliable address extraction is possible even on a arrival badge-based screen.

[0083] Additionally, in some navigation applications (e.g., Tmap), destination addresses are displayed as multiple lines of text data rather than as UI nodes.

[0084] According to an embodiment of the present specification, in this case, the main terminal can parse the entire screen text into JSON format, extract the text corresponding to a predefined line index, and use it as a destination address.

[0085] This method can reliably recognize addresses even in environments where the UI layer is composed of a non-standard structure, and can obtain addresses through accurate row-based string extraction even when UI resource identifiers or node tree traversal are impossible.

[0086] Therefore, this technology can provide consistent address extraction performance in various navigation app environments, regardless of the screen rendering structure.

[0087] According to one embodiment of the present specification, the main terminal can analyze the entire screen text to separate it into multiple lines (T1, T2, ..., T_n) and calculate the probability that each line is a destination address in the form of a score.

[0088] For example, the score of each row T_i can be expressed by the following formula by combining the degree of match with the address format, the degree of match with map data or a place name dictionary, and the probability that the address appears on the screen.

[0089]

[0090] Here,

[0091] R_i: The degree to which the text in the corresponding row matches the address regular expression (road name, lot number, etc.),

[0092] G_i: The degree to which the row corresponds to an actual location or place name on the map,

[0093] Π_i: Represents the probability that an address will be displayed based on the position of the row or the UI structure.

[0094] α, β, and γ are weights used to adjust the importance of each element.

[0095] In this way, the main terminal calculates the above score for all rows and automatically determines the row with the highest score as the destination address. Therefore, even if the screen structure or the UI form of each app differs, addresses can be reliably identified through objective numerical calculations.

[0097] FIG. 4 illustrates an automatic route guidance method for a receiving terminal to which the present specification may be applied.

[0098] Referring to Fig. 4, the receiving terminal receives a payload containing a destination address from the server, automatically inputs the address into the navigation application, and automatically clicks a series of UI buttons to finally start route guidance.

[0099] First, when the navigation application pre-configured according to the delivery application is launched, the receiving terminal detects the route finding button (including the arrow icon) displayed on the screen. This button is identified by comprehensively analyzing text labels, ContentDescription attributes, resource identifiers, or the geometric boundaries (bounds) of the view, and is clicked immediately upon detection via the accessibility service's performAction(ACTION_CLICK) command. Through this process, the route finding step can be performed automatically without any separate user intervention.

[0100] Next, some navigation screens may display origin and destination selection items in the middle. The receiving terminal detects "Departure" and / or "Destination" text nodes in the corresponding UI layer and clicks the container node containing them to establish the correct route. If a UI loading delay or screen transition failure occurs, exception handling is performed by re-detecting the same items through an iterative navigation loop and, if necessary, clicking another candidate node (a sibling node with the same label).

[0101] Finally, when the guidance start button is displayed on the screen, the receiving terminal automatically detects it and clicks it to initiate the final route guidance. Similar to the previous steps, the guidance start button is detected via text, ContentDescription, resource ID, etc. If it is not displayed immediately due to asynchronous loading, for example, a navigation loop can be repeated up to 24 times at 1-second intervals. Since sufficient UI waiting time must be reflected during this process, appropriate waiting values ​​for each screen structure can be pre-set.

[0102] In addition, while coordinate-clicking can be utilized as an auxiliary method, simple coordinate input presents a problem in that errors occur depending on the device's resolution and DPI environment. Therefore, the receiving device uses a multi-criteria detection method based on accessibility services to ensure consistent operation regardless of resolution or model. Unlike methods that can be merely mimicked by coordinate-clicking, this provides the technical effect of enabling fully automated route guidance to be initiated consistently across all smartphone environments.

[0103] The foregoing specification may be implemented as computer-readable code on a medium on which a program is recorded. A computer-readable medium includes all types of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable media include Hard Disk Drives (HDDs), Solid State Disks (SSDs), Silicon Disk Drives (SDDs), ROMs, RAMs, CD-ROMs, magnetic tapes, floppy disks, optical data storage devices, etc., and also include implementations in the form of carrier waves (e.g., transmission over the Internet). Accordingly, the above detailed description should not be interpreted restrictively in all respects and should be considered exemplary. The scope of this specification should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of this specification are included within the scope of this specification.

[0104] Furthermore, although the above description has focused on the services and embodiments, this is merely illustrative and does not limit the scope of this specification. Those skilled in the art will understand that various modifications and applications not exemplified above are possible without departing from the essential characteristics of the services and embodiments. For example, each component specifically shown in the embodiments may be modified and implemented. Differences related to such modifications and applications should be interpreted as being included within the scope of this specification as defined in the appended claims.

Claims

Claim 1 A method for transmitting addresses between mobile terminals and automatically executing navigation comprises: a step in which a server establishes a session between a main terminal and a receiving terminal; a step in which the main terminal accepts a first delivery order and obtains a first address included in the first delivery order; a step in which the main terminal generates a first payload based on the delivery platform identifier of the first delivery order and the first address; a step in which the main terminal transmits the first payload to the receiving terminal through the server; and a step in which the receiving terminal executes a first navigation application associated with the delivery platform identifier included in the first payload and automatically inputs the first address to automatically start route guidance; wherein the step of automatically starting route guidance includes a step in which the receiving terminal automatically detects and clicks a route finding button on the screen of the first navigation application using an accessibility service. and the step of automatically detecting and clicking a guidance start button on the screen of the first navigation application; wherein the main terminal, when the transmission of the first payload is completed, calls the GLOBAL_ACTION_RECENTS operation of the Android accessibility service, and in accordance with the call of the GLOBAL_ACTION_RECENTS operation, controls the screen of the main terminal to automatically switch from the screen of the control application temporarily displayed for the generation or transmission of the first payload to the screen of the delivery platform application that the user was using immediately before accepting the first delivery order, and the step of obtaining the first address includes, when the destination address is displayed as multiple lines of text data rather than in the form of a UI node on the screen of the main terminal, the step of the main terminal parsing the entire screen text into JSON form; and the step of separating the parsed entire screen text into multiple lines (T_n).A method comprising: a step of calculating a score (S_i) indicating the probability that each of the plurality of rows is a destination address; and a step of determining the text of the row with the highest calculated score (S_i) as the first address; wherein the score (S_i) is calculated according to the following mathematical formula 1, [Mathematical Formula 1] S_i = αR_i + βG_i + γΠ_i where R_i is the degree to which the text of the i-th row (T_i) matches an address regular expression including a road name or lot number, G_i is the degree to which the text of the i-th row (T_i) matches map data or a place name dictionary, Π_i is the probability that a destination address is displayed based on the screen location or UI structure of the i-th row (T_i), and α, β, and γ are weights for adjusting the importance of R_i, G_i, and Π_i, respectively. Claim 2 A method according to claim 1, wherein the step of establishing the session comprises: receiving unique user authentication information from the main terminal and the receiving terminal, respectively; managing a device list based on the unique user authentication information; and recording binding information between the main terminal and the receiving terminal. Claim 3 A method according to claim 2, wherein the step of obtaining the first address comprises: a step of analyzing the UI structure of a navigation application displayed on the screen of the main terminal; and a step of extracting a text string corresponding to the first address based on a route card container, a search bar, or a destination badge. Claim 4 In paragraph 3, the method wherein the first payload comprises a user identifier (UID), transmitting terminal information, receiving terminal information, the delivery platform identifier, address text, timestamp, and hash value. Claim 5 delete Claim 6 The method according to claim 1 further comprises the steps of: the main terminal accepting a second delivery order and obtaining a second address included in the second delivery order; the main terminal generating a second payload based on the delivery platform identifier of the second delivery order and the second address; the main terminal transmitting the second payload to the receiving terminal through the server; and the receiving terminal executing a second navigation application associated with the delivery platform identifier of the second delivery order included in the second payload, and automatically starting route guidance by automatically inputting the second address; wherein the first navigation application is different from the second navigation application. Claim 7 delete

Images