KR20210131538A - Delivery network system - Google Patents

Abstract

A delivery network system is disclosed. According to the present invention, the delivery network system includes a delivery app server, a first application, and a second application. The first application may be used by a user who uses the delivery, and the second application may be used by a mover who performs the delivery. The delivery app server can effectively execute delivery orders and execution by managing delivery schedules. Therefore, it is possible to update a schedule of the mover according to elapse of the schedule.

Description

DELIVERY NETWORK SYSTEM

The present invention relates to a delivery network system. In particular, the present invention is a delivery network system that provides a platform for connecting a user who requests delivery and a mover who performs delivery.

The delivery platform service can connect users and performers and earn brokerage fees. The method in which the delivery platform service connects the user and the performer may be a bidding method or an auction method.

For example, when a delivery user presents a delivery order, a method of negotiating with a number of preliminary performers presenting conditions may be applied to the delivery platform service. However, there is a fear that the management of the delivery practitioners will be poor.

In addition, when the delivery is performed using public transportation other than the existing truck or motorcycle, it may be necessary to manage the movement route of the delivery person in an integrated manner.

Patent Publication 10-2020-0000757

SUMMARY OF THE INVENTION The present invention aims to solve the above and other problems.

Another object of the present invention is to provide a delivery network system that inquires whether to perform delivery to a mover capable of performing the ordered delivery when a user places an order for delivery.

Another object of the present invention is to provide a delivery network system that selects one mover from among a plurality of movers that have accepted the execution of an ordered delivery.

Another object of the present invention is to provide a delivery network system for extracting an optimal route from a loading location to an unloading location of an ordered delivery item.

Another object of the present invention is to provide a delivery network system that sets both ends of a section in which public transportation means are interposed among the optimal routes as nodes of a schedule.

Another object of the present invention is to provide a delivery network system that integrates and manages the ordered delivery schedule with the mover's schedule for performing the ordered delivery.

Another object of the present invention is to provide a delivery network system that updates a mover's schedule according to the elapse of a schedule.

According to an aspect of the present invention to achieve the above or other object, a communication unit for transmitting and receiving a signal (signal) with a first application that provides a delivery consumption interface and a second application that provides a delivery execution interface; a database unit for storing data; and a processor for transmitting and receiving signals to and from the communication unit and the database unit, wherein the processor receives the delivery order request message from the first application through the communication unit, based on the mover data stored in the database unit. Extracting a mover capable of performing the ordered delivery, and if there is a mover capable of performing the ordered delivery, through the communication unit, to a second application of the mover capable of performing the ordered delivery, A delivery app that transmits a message whether to accept the execution of the ordered delivery, and selects a mover that performs the ordered delivery from among the accepted movers when there is an acceptance message returned from the mover that has received the delivery acceptance message A delivery app-server may be provided.

According to another (another) aspect of the present invention to achieve the above or other object, a communication unit for transmitting and receiving a signal (signal) with a second application that provides a discovery performance interface; a database unit for storing data; And a first communication unit for communicating with the delivery app server comprising a processor for transmitting and receiving a signal to and from the communication unit and the database unit; a touch screen displaying an image; and a first application providing a delivery consumption interface to the touch screen, wherein the delivery consumption interface includes: a delivery order button; Check delivery status button; In addition, a mobile terminal may be provided, including a touch screen indicating status information of a delivery in progress.

According to another (another) aspect of the present invention in order to achieve the above or other object, a communication unit for transmitting and receiving a signal (signal) with a first application that provides a delivery consumption interface; a database unit for storing data; And a second communication unit communicating with the delivery app server comprising a processor for transmitting and receiving a signal to and from the communication unit and the database unit; a touch screen displaying an image; and a second application that provides a delivery execution interface to the touch screen, wherein the delivery execution interface receives an inquiry message regarding delivery execution from the delivery app server through the second communication unit, A mobile terminal may be provided that displays a dump reception interface on the touch screen.

The effect of the excessive differential pressure relief system and method according to the present invention will be described as follows.

According to at least one of the embodiments of the present invention, when a user places an order for delivery, a mover capable of performing the ordered delivery may be inquired as to whether delivery is performed.

According to at least one of the embodiments of the present invention, one mover may be selected from among a plurality of movers that have accepted the execution of the ordered delivery.

According to at least one of the embodiments of the present invention, it is possible to extract an optimal route from a loading place of an ordered delivery item to an unloading place.

According to at least one of the embodiments of the present invention, both ends of a section in which public transportation means are interposed among the optimal routes may be set as nodes of the schedule.

According to at least one of the embodiments of the present invention, the schedule of the ordered delivery may be integrated and managed with the schedule of the mover performing the ordered delivery.

According to at least one of the embodiments of the present invention, the schedule of the mover may be updated according to the elapse of the schedule.

Further scope of applicability of the present invention will become apparent from the following detailed description. However, it should be understood that the detailed description and specific embodiments such as preferred embodiments of the present invention are given by way of illustration only, since various changes and modifications within the spirit and scope of the present invention may be clearly understood by those skilled in the art.

1 is a diagram illustrating a delivery network system 10 according to an embodiment of the present invention.
2 is a diagram illustrating a mobile terminal 100 according to an embodiment of the present invention.
3 is a diagram illustrating a state in which the first application 200 is displayed on a screen according to an embodiment of the present invention.
4 is a diagram illustrating a touch screen on which a delivery state information table is displayed.
5 is a diagram illustrating a screen in which the first application displays an interface related to the user's entire menu on the touch screen.
6 is a diagram illustrating an interface for confirming a delivery state.
7 to 9 are diagrams illustrating a delivery order interface 2100 according to an embodiment of the present invention.
10 is a diagram illustrating a delivery reception interface according to an embodiment of the present invention.
11 is a diagram illustrating a delivery reception interface in which a cost bid selection button is displayed according to a second application according to another embodiment of the present invention.
12 is a diagram illustrating an acceptance approval waiting state in a delivery reception interface according to an embodiment of the present invention.
13 is a diagram illustrating a state in which delivery acceptance is approved or rejected in the delivery reception interface according to an embodiment of the present invention.
14 is a diagram illustrating a state in which delivery is received or rejected in the delivery order interface 2100 according to an embodiment of the present invention.
15 is a diagram illustrating an initial screen of a mover app according to an embodiment of the present invention.
16 is a diagram illustrating a mover schedule confirmation interface indicating a first delivery.
17 is a diagram illustrating a mover schedule confirmation interface indicating a second delivery.
18 is a diagram illustrating a mover schedule confirmation interface indicating the entire delivery.
19 is a diagram illustrating a mover schedule management interface according to an embodiment of the present invention.
20 is a diagram illustrating a mover schedule management interface for managing the first delivery.
21 is a diagram illustrating a mover schedule management interface for reporting completion of delivery.
22 is a diagram illustrating a screen in which the second application displays an interface related to the full menu of the mover on the touch screen 110 .
23 is a diagram illustrating an app server 400 according to an embodiment of the present invention.
24 is a block diagram of individual delivery data 4100 according to an embodiment of the present invention.
25 is a block diagram of mover data 4200 according to an embodiment of the present invention.
26 is a diagram illustrating a data structure of a schedule according to an embodiment of the present invention.
27 is a block diagram of user data 4300 according to an embodiment of the present invention.
28 is a block diagram of environment data 4400 according to an embodiment of the present invention.
29 is a diagram illustrating a delivery order data form and a delivery cancellation data form according to an embodiment of the present invention.
30 is a diagram illustrating a delivery source data form DF200 according to an embodiment of the present invention.
31 is a diagram illustrating an individual delivery data form according to an embodiment of the present invention.
32 is a diagram illustrating an example of individual delivery data according to the individual delivery data form DF300 according to an embodiment of the present invention.
33 : is a figure which showed the integrated delivery data form DF400 and each segment.
34 is a view showing an example of the integrated delivery data form (DF400) according to an embodiment of the present invention.
Fig. 35 is a view showing an updated integrated delivery data form in which the individual delivery data form of Fig. 32 is added to the integrated delivery data form of Fig. 34;
FIG. 36 is a diagram illustrating a state in which serial numbers are newly assigned to each segment of the integrated delivery data form shown in FIG. 35 .
FIG. 37 is a diagram illustrating a unified delivery data form modified to enable connection between each segment of the unified delivery shown in FIG. 36 .
FIG. 38 is a diagram illustrating a unified delivery data form modified to enable connection between each segment of the unified delivery shown in FIG. 37 .
39 is a diagram illustrating a delivery manager 5000 according to an embodiment of the present invention.
40 is a diagram illustrating a list of movers capable of performing delivery according to an embodiment of the present invention.
41 is a diagram illustrating an acceptance/non-acceptance response message according to an embodiment of the present invention.
42 is a diagram illustrating a delivery execution acceptance mover list DF700 according to an embodiment of the present invention.
43 is a diagram illustrating a mover manager and a user manager according to an embodiment of the present invention.
44 is a flowchart illustrating a delivery processing method ( S10 ) according to an embodiment of the present invention.
45 is a flowchart illustrating a delivery order processing step (S3000) according to an embodiment of the present invention.
46 is a flowchart illustrating an order delivery capable mover extraction step (S3100) according to an embodiment of the present invention.
47 is a flowchart illustrating a determination step ( S3120 ) of whether order delivery of each mover can be performed according to an embodiment of the present invention.
48 is a flowchart illustrating a step (S3123) of merging individual delivery data forms into an integrated delivery data form according to an embodiment of the present invention.
49 is a flowchart illustrating the possibility of determining whether each segment of the integrated delivery data form is possible ( S3124 ) according to an embodiment of the present invention.
FIG. 50 is a diagram illustrating a state in which a touch input is applied to the second delivery progress confirmation button in the delivery status interface shown in FIG. 6 .

Hereinafter, the embodiments disclosed in the present specification will be described in detail with reference to the accompanying drawings, but the same or similar components are assigned the same reference numerals regardless of reference numerals, and overlapping descriptions thereof will be omitted. The suffixes "module" and "part" for the components used in the following description are given or mixed in consideration of only the ease of writing the specification, and do not have a meaning or role distinct from each other by themselves. In addition, in describing the embodiments disclosed in the present specification, if it is determined that detailed descriptions of related known technologies may obscure the gist of the embodiments disclosed in the present specification, the detailed description thereof will be omitted. In addition, the accompanying drawings are only for easy understanding of the embodiments disclosed in the present specification, and the technical spirit disclosed herein is not limited by the accompanying drawings, and all changes included in the spirit and scope of the present invention , should be understood to include equivalents or substitutes.

Terms including an ordinal number, such as first, second, etc., may be used to describe various elements, but the elements are not limited by the terms. The above terms are used only for the purpose of distinguishing one component from another.

When a component is referred to as being “connected” or “connected” to another component, it is understood that the other component may be directly connected or connected to the other component, but other components may exist in between. it should be On the other hand, when it is mentioned that a certain element is "directly connected" or "directly connected" to another element, it should be understood that the other element does not exist in the middle.

The singular expression includes the plural expression unless the context clearly dictates otherwise.

In the present application, terms such as "comprises" or "have" are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

1 is a diagram illustrating a delivery network system 10 according to an embodiment of the present invention. The delivery network system 10 may use the communication network 40 . The communication network 40 may include a wireless communication network or a wired communication network.

The delivery network system 10 may include a server 50 , a first terminal 60 , and a second terminal 70 . The first terminal 60 and the second terminal 70 may be implemented through the mobile terminal 100 . The mobile terminal 100 may execute an application. For example, the first terminal 60 may execute the first application 200 , and the second terminal 70 may execute the second application 300 . The mobile terminal 100 may be, for example, a smartphone. The first application 200 may be referred to as a “user app”. The second application 300 may be referred to as a “mover app”. A person who uses the first application 200 may be referred to as a “user”. A person who uses the second application 300 may be referred to as a “mover”.

The first terminal 60 and the second terminal 70 may be integrated into one terminal. For example, the first application 200 and the second application 300 may be installed and driven in the first terminal 60 . That is, a user can be a mover, and a mover can be a user.

The server 50 may transmit/receive signals to and from the first terminal 60 and the second terminal 70 . A signal transmitted and received by the server 50 may include information or data. The server 50 may process the signal. For example, the server 50 may process data or information according to an algorithm.

2 is a diagram illustrating a mobile terminal 100 according to an embodiment of the present invention. The mobile terminal 100 may include a home button 120 . When the home button 120 is pressed, an initial screen may be displayed on the mobile terminal 100 .

The mobile terminal 100 may include a touch screen 110 . The touch screen 110 may display an image or an image. The touch screen 110 may obtain a touch input. The icon 130 may be displayed on the touch screen 110 . The icon 130 may include, for example, a first icon 131 and a second icon 132 .

1 and 2 , the first icon 131 may be linked to the first application 200 , and the second icon 132 may be linked to the second application 300 . In FIG. 2 , the first icon 131 and the second icon 132 are displayed as being located at the same time in one mobile terminal 100 , but the present invention is not limited thereto.

For example, the first icon 131 may be displayed on the mobile terminal 100 of the user using the first application 200 and the second icon 132 may not be displayed. For example, the second icon 132 may be displayed on the mobile terminal 100 of the user using the second application 300 and the first icon 131 may not be displayed. The mobile terminal 100 on which the first application 200 is executed may include a “first communication unit” that communicates with an external device.

As shown in FIG. 2 , the user of the mobile terminal 100 may use both the first application 200 and the second application 300 . That is, the user group of the first application 200 and the user group of the second application 300 may overlap.

When the first icon 131 is touched, the first application 200 may be executed or may be in an on-ground state. When the second icon 132 is touched, the second application 300 may be executed or may be in an on-ground state. The first application 200 may be referred to as a “user delivery application”. The second application 300 may be referred to as a “mover delivery application”. “User” may mean a person who applies for and uses delivery. A “mover” may mean a person who performs delivery of loading, transporting, and unloading articles. A “user” may be referred to as a “consumer” consuming delivery.

3 is a diagram illustrating a state in which the first application 200 is displayed on a screen according to an embodiment of the present invention. In FIG. 3 , the user of the first application 200 may be in a state of logging in to the first application 200 .

Referring to FIG. 3 , the first application 200 may be displayed on the touch screen 110 of the mobile terminal 100 (refer to FIG. 2 ). The first application 200 may include a delivery order button 210 . Alternatively, the first application 200 may display the delivery order button 210 on the touch screen 110 . When the first application 200 obtains a touch input applied to the delivery order button 210 , the first application 200 may display an interface for the delivery order on the touch screen 110 .

The first application 200 may include a delivery status check button 220 . Alternatively, the first application 200 may display the delivery status check button 220 on the touch screen 110 . When the first application 200 obtains a touch input applied to the delivery status check button 220 , the first application 200 may display an interface for checking the delivery status on the touch screen 110 .

The first application 200 may include a user app menu group 230 . Alternatively, the first application 200 may display the user app menu group 230 on the touch screen 110 . The user app menu group 230 may include at least one user app menu.

The user app menu group 230 may include a user personal button 231 . The first application 200 may display the user personal button 231 on the touch screen 110 . When the first application 200 obtains a touch input applied to the user's personal button 231, the user's personal information (eg, residence address, a nearby subway station or bus stop, work address, An interface for managing a nearby subway station or bus stop, work time, work time, etc.) may be displayed on the touch screen 110 .

The user app menu group 230 may include a user setting button 232 . The first application 200 may display the user setting button 232 on the touch screen 110 . When the first application 200 obtains a touch input applied to the user setting button 232 , an interface related to the setting of the first application 200 may be displayed on the touch screen 110 . The setting of the first application 200 may be, for example, an alarm setting, a GPS setting, a retrieveable article setting, and the like.

The user app menu group 230 may include a delivery schedule button 233 . The first application 200 may display the delivery schedule button 233 on the touch screen 110 . When the first application 200 obtains a touch input applied to the delivery schedule button 233 , the first application 200 may display an interface indicating the delivery schedule requested by the user on the touch screen 110 .

The user app menu group 230 may include a user full menu button 234 . The first application 200 may display the user full menu button 234 on the touch screen 110 . When the first application 200 obtains a touch input applied to the user's full menu button 234 , the first application 200 may display a menu necessary for the user to use the first application 200 on the touch screen 110 .

The first application 200 may include a user screen 240 . Alternatively, the first application 200 may display the user screen 240 on the touch screen 110 . The user screen 240 may indicate the status of a delivery in progress. When the first application 200 obtains a touch input applied to the delivery schedule button 233 , the user screen 240 may be displayed on the touch screen 110 .

The user screen 240 may include a map 2410 (map). The map 2410 may include a location where the delivery is performed. For example, the map 2410 may include a place for loading an article, a place for moving, and a place for unloading the article.

In the map 2410, in the case of using a metro (metro, meaning subway or urban rail) station by moving from a loading place, a loading place, a metro station (loading station), a metro at a loading station A metro station (unloading station) to move along and get off, an unloading place, etc. may be displayed. Here, the metro may mean at least one of a subway, an urban railroad, a high-speed rail, a city bus, a wide-area bus, and an express bus.

The user screen 240 may include a mover current location indicator 2420 . The mover current position indicator 2420 may indicate the current position of a mover performing a specific delivery. The mover current position indicator 2420 may be displayed on the map 2410 . The user USR may touch the mover current position indicator 2420 . In FIG. 3 , the mover current location indicator 2420 is displayed in red color and may indicate a point on the map 2410 .

4 is a diagram illustrating a touch screen on which a delivery state information table is displayed.

Referring to FIG. 4 , when a user (USR, see FIG. 3 ) applies a touch input to the mover current position indicator 2420 , the first application 200 displays the delivery state information table 2430 on the touch screen 110 . can be displayed The delivery state information table 2430 may be displayed on the map 2410 . The delivery state information table 2430 may be displayed on the touch screen 110 adjacent to the mover current position indicator 2420 .

The delivery state information table 2430 may include information about the delivery state. The information on the delivery state may include, for example, information on whether the delivery is ready state, whether the article is loaded, whether the article is being loaded and moved, or whether the article is unloaded. The user can easily check the state information of the corresponding delivery through the delivery state information table 2430 .

The delivery state information table 2430 may include information about a mover that performs a corresponding delivery. The information about the mover may include, for example, information about the mover's contact information and rating. The contact information of the mover may be an encrypted number used in the corresponding delivery. The grade of the mover may be set based on credits generated in the process of performing delivery for a certain period of time. The mover's credit may be based on a user's evaluation.

The delivery state information table 2430 may include an unloading scheduled time. The scheduled unloading time may mean a scheduled time of unloading the article of the corresponding delivery.

5 is a diagram illustrating a screen in which the first application displays an interface related to the user's entire menu on the touch screen.

Referring to FIG. 5 , when the user applies a touch input to the user full menu button 234 , the first application 200 obtains the touch input and displays an interface 2340 related to the user full menu on the touch screen 110 . can do. The interface 2340 related to the user's entire menu may be referred to as "the user's entire menu interface".

The user full menu interface 2340 may include a user bulletin board button 2341 . The user bulletin board button 2341 may be displayed on the touch screen 110 . When the first application 200 obtains a touch input applied to the user bulletin board button 2341 , the first application 200 may display an interface related to the user bulletin board on the user overall menu interface 2340 . Data of the user bulletin board may be stored and managed in the user DB 412 (refer to FIG. 23 ).

The user bulletin board may form an online community of users using the delivery network system 10 (refer to FIGS. 1 and 2 ) according to an embodiment of the present invention. Users can establish a “friend relationship” through the user bulletin board. Users may jointly use delivery, for example. For example, a first user and a second user located in a short distance may apply for delivery by matching the loading location into one. In this case, the delivery cost may be lowered.

The user full menu interface 2340 may include a user rating confirmation button 2342 . The user rating confirmation button 2342 may be displayed on the touch screen 110 . When the first application 200 acquires a touch input applied to the user rating confirmation button 2342, the first application 200 may transmit a message requesting rating data of the corresponding user to the server 50 (refer to FIG. 1). The server 50 (refer to FIG. 1 ) may transmit the rating data (information) of the corresponding user to the first application 200 by processing the request message. The first application 200 may display rating information of the corresponding user (user) on the touch screen 110 . Accordingly, the user can easily check his/her rating. The user's rating may be calculated based on the credits the user receives from the mover while using the delivery network system 10 (refer to FIGS. 1 and 2 ) for a certain period of time.

The user full menu interface 2340 may include a user statistics view button 2343 . The user statistics view button 2343 may be displayed on the touch screen 110 . When the first application 200 obtains a touch input applied to the user statistics view button 2343, the first application 200 may transmit a message requesting statistical data of the corresponding user to the server 50 (refer to FIG. 1). The server 50 (refer to FIG. 1 ) may transmit the statistical data (information) of the corresponding user to the first application 200 by processing the request message. The first application 200 may display information about the history of the user (user) using the delivery network system 10 (refer to FIGS. 1 and 2 ) on the user overall menu interface 2340 .

The user full menu interface 2340 may include a user login/logout button 2344 . The user login/logout button 2344 may be displayed on the touch screen 110 . When the first application 200 obtains a touch input applied to the user login/logout button 2344 , the first application 200 may display an interface related to the user's login or logout on the user overall menu interface 2340 .

The user full menu interface 2340 may include a user notice button 2345 . The user notice button 2345 may be displayed on the touch screen 110 . When the first application 200 obtains a touch input applied to the user notice button 2345, the first application 200 may transmit a message requesting the user notice to the server 50 (refer to FIG. 1). The server 50 (refer to FIG. 1 ) may transmit the user announcement data (information) to the first application 200 by processing the request message. The first application 200 may display a user notice on the user overall menu interface 2340 . The user announcement may include information about the operation of the delivery network system 10 (refer to FIGS. 1 and 2 ).

6 is a diagram illustrating an interface for confirming a delivery state. The interface shown in FIG. 6 may be referred to as a delivery state interface 2200 .

Referring to FIG. 6 , when the first application 200 obtains a touch input applied to the delivery status check button 220 (see FIG. 3 ), the server 50 sends a message requesting the delivery status of the corresponding user. , see FIG. 1). The server 50 (refer to FIG. 1 ) may process the request message to transmit the delivery status of the corresponding user to the first application 200 . The first application 200 may display on the touch screen 110 a 'delivery status interface 2200' related to the delivery status of the corresponding user. For example, the corresponding user may be in a state in which the first delivery and the second delivery have been received.

A first delivery progress confirmation button 2210 may be displayed on the touch screen 110 . The first delivery progress confirmation button 2210 may display a brief state of the first delivery. For example, the first delivery progress confirmation button 2210 may indicate that the first delivery is in a loading state. When the first application 200 obtains a touch input applied to the first delivery progress confirmation button 2210 , the first application 200 may display an interface related to the progress state of the first delivery on the touch screen 110 .

A second delivery progress confirmation button 2220 may be displayed on the touch screen 110 . The second delivery progress confirmation button 2220 may display a brief state of the second delivery. For example, the second delivery progress confirmation button 2220 may indicate that the second delivery is in a preparing state. When obtaining a touch input applied to the second delivery progress confirmation button 2220 , the first application 200 may display an interface related to the progress state of the second delivery on the touch screen 110 .

The state interface 2200 of the delivery may receive an input related to a state change of the corresponding delivery. For example, the progress state of the second delivery may be a current preparing state, and an interface related to the progress state of the second delivery may receive an input regarding cancellation of the second delivery.

When there is only one delivery requested by the user, one delivery progress confirmation button may be displayed on the touch screen 110 . When there are multiple deliveries requested by the corresponding user, a progress confirmation button for each delivery may be displayed on the touch screen 110 .

7 to 9 are diagrams illustrating a delivery order interface 2100 according to an embodiment of the present invention.

Referring to FIG. 7 , when the first application 200 obtains a touch input applied to the delivery order button 210 (see FIG. 3 ), the delivery order interface 2100 is displayed on the touch screen 110 . can The first application 200 may provide a 'delivery consumption interface'. The delivery order interface 2100 may be one of the delivery consumption interfaces.

The delivery order interface 2100 may include a loading factor 2110 . The loading factor 2110 may relate to shipment of goods. The loading factor 2110 may include a loading time component 2111 and a loading location component 2112 . The loading time element 2111 may mean a scheduled time at which the article is loaded. The loading location element 2112 may mean a scheduled location where the article is to be loaded.

The delivery order interface 2100 may include an unloading factor 2120 . The unloading factor 2120 may relate to the unloading of articles. The unloading factor 2120 may include an unloading visual element 2121 and an unloading location element 2122 . The unloading time element 2121 may mean a scheduled time at which the article is unloaded. The unloading location element 2122 may mean a scheduled location where the article is to be unloaded.

The delivery order interface 2100 may include an item factor 2130 . The article factor 2130 may relate to information about the article. The article factor 2130 can include at least one of an article size element 2131 , an article weight element 2132 , and an article code element 2133 . The article size element 2131 may mean the size of an article to be retrieved. The article weight element 2132 may refer to the weight of the article. The article code element 2133 may mean a code related to the type of article. When the first application 200 obtains a touch input applied to the product code element 2133, a list related to the product code may be displayed on the touch screen 110 in a radio button manner. When the first application 200 obtains a touch input applied to one of the list related to the product code, the corresponding product code may be displayed on the touch screen 110 and designated as the product code element 2133 .

The product size photographing button 2131_1 may be displayed as being included in the delivery order interface 2100 . The first application 200 may execute a camera application upon acquiring a touch input applied to the article size photographing button 2131_1. When the camera application acquires an image of the corresponding article, the first application may calculate the size of the corresponding article.

The delivery order interface 2100 may include a mover selection element 2140 . 7 and 8 , when the first application 200 obtains a touch input applied to the mover selection element 2140 , an interface for selecting a mover according to the characteristics of the mover is displayed on the touch screen 110 . can be displayed For example, the first application 200 may display the non-selection element 2141 , the first class mover selection element 2142 , and the second class mover selection element 2143 on the touch screen 110 . When the first application 200 obtains a touch input applied to one of the non-selection element 2141 , the first class mover selection element 2142 , and the second class mover selection element 2143 , the selected element is selected as a mover element 2140 .

Referring to FIG. 9 , a screen in which the user writes or selects each item of the delivery order interface 2100 may be observed. For example, in the loading time element 2111 , “March 7, 2020 7:00 am” may be written. For example, in the loading place element 2112, "Seoul Nambu Art Museum" may be described. For example, in the unloading visual element 2121 , “March 7, 2020 6:00 PM” may be written. For example, "Seoul National University of Education" may be described in the unloading place element 2122 . For example, "30cm X 20cm X 10cm" may be written in the article size element 2131 . For example, the article weight element 2132 may read “1.5 kg”. For example, “C9” may be selected for article code element 2133 . For example, the unselected element 2141 may be selected for the mover selection element 2140 .

The delivery order interface 2100 may include a send delivery order button 2150 . When a touch is applied to the delivery order transmission button 2150, the first application 200 transmits the information described in each factor 2110, 2120, 2130, 2140 of the delivery order interface 2100 to the server 50, FIG. 1 see) can be transmitted.

10 is a diagram illustrating a delivery reception interface according to an embodiment of the present invention.

Referring to FIG. 10 , the second application 300 may display the delivery reception interface 3100 on the touch screen 110 . When the first application 200 (see FIGS. 7 to 9 ) executes a delivery order through the delivery order interface 2100 (see FIGS. 7 to 9 ), the server 50 (see FIG. 1 ) sends delivery order information can be obtained. The server 50 (refer to FIG. 1 ) may use the delivery order information to find a mover capable of performing the corresponding delivery. A mover capable of performing the corresponding delivery may be, for example, one person, or may be, for example, several people. The mobile terminal 100 on which the second application 300 is executed may include a second communication unit that communicates with an external device.

The server 50 (refer to FIG. 1 ) may transmit an inquiry message regarding whether to perform the corresponding discovery to a mover capable of performing the corresponding discovery. When the second application 300 obtains an inquiry message (or signal, or data, or information) about the execution of the delivery from the server 50 (see FIG. 1), the delivery reception interface ( 3100 may be displayed on the touch screen 110 . The touch screen 110 shown in FIG. 10 may be the touch screen 110 of the mobile terminal 100 (refer to FIG. 1 ) that has received an inquiry message regarding the delivery from the server 50 (refer to FIG. 1 ). The second application 300 may provide a 'delivery execution interface' to the touch screen 110 . The delivery reception interface 3100 may be one of delivery performance interfaces.

The delivery reception interface 3100 may include a map 3105 . Map 3105 may indicate loading and unloading locations of articles.

The delivery reception interface 3100 may include a loading visual element 3111 . The loading visual element 3111 of the delivery reception interface 3100 may correspond to the loading visual element 2111 (refer to FIGS. 7 to 9 ) of the delivery order interface 2100 (see FIGS. 7 to 9 ).

The delivery reception interface 3100 can include a loading location element 3112 . The loading place element 3112 of the delivery reception interface 3100 may correspond to the loading place element 2112 (see FIGS. 7-9 ) of the delivery order interface 2100 (see FIGS. 7-9 ). The loading location element 3112 may be displayed on the map 3105 to indicate the point where the article is loaded.

The delivery reception interface 3100 may include a loading station element 3113 . The location of the loading station element 3113 may mean a metro station that must travel from the location of the loading station element 3112 to arrive. The server 50 (see FIG. 1 ) may extract the loading station element 3113 from the loading location element 2112 (see FIGS. 7-9 ). The loading station element 3113 may be displayed in the map 3105 .

The delivery reception interface 3100 may include an unloading visual element 3121 . The unloading visual element 3121 of the delivery reception interface 3100 may correspond to the unloading visual element 2121 (refer to FIGS. 7 to 9 ) of the delivery order interface 2100 (see FIGS. 7 to 9 ). have.

The delivery reception interface 3100 may include an unload location element 3122 . The unloading place element 3122 of the delivery reception interface 3100 may correspond to the unloading place element 2122 (see FIGS. 7-9) of the delivery order interface 2100 (see FIGS. 7-9 ). have. The unloading location element 3112 may be displayed on the map 3105 to indicate the point where the article is unloaded.

The delivery reception interface 3100 may include an unloading station element 3123 . The unloading station element 3123 may refer to one of the metro stations adjacent from the unloading location element 3122 . The unloading station element 3123 may be a location prior to reaching the location of the unloading location element 3122 . The server 50 (see FIG. 1 ) may extract the unloading station element 3123 from the unloading location element 2122 (see FIGS. 7-9 ). Unloading station element 3113 may be displayed on map 3105 to point to one of the adjacent metro stations from unloading location element 3122 .

The loading station element 3113 and the unloading station element 3123 may be outputs derived from the loading location element 3112 and the unloading location element 3122 as inputs. The loading station element 3113 and the unloading station element 3123 may form an optimal path for movement from the loading site element 3112 to the unloading site element 3122 .

The delivery reception interface 3100 may include a delivery path 3107 . The delivery path 3107 may refer to a path through which articles are loaded, moved, and unloaded. The delivery route 3107 may be displayed on the map 3105 . For example, delivery path 3107 may include a path from a loading location element 3111 to a loading station element 3112 . For example, the delivery path 3107 may include a path from a loading station element 3112 to an unloading station element 3123 . For example, delivery path 3107 may include a path from an unloading station element 3123 to an unloading location element 3122 .

The delivery reception interface 3100 may include an article factor 3130 . The article factor 3130 of the delivery reception interface 3100 may correspond to the article factor 2130 (refer to FIGS. 7 to 9 ) of the delivery order interface 2100 (see FIGS. 7 to 9 ).

"Information about the delivery" includes a loading visual element 3111 , a loading place element 3112 , a loading station element 3113 , an unloading visual element 3121 , an unloading place element 3122 , and an unloading station element. It may mean at least one of 3123 and the article factor 3130 .

The delivery reception interface 3100 may include a reject button 3150 . When the second application 300 obtains a touch input applied to the reject button 3150, the message indicating that the delivery is rejected displayed on the delivery reception interface 3100 can be transmitted to the server 50 (refer to FIG. 1). have.

The delivery reception interface 3100 may include an accept button 3140 . When the second application 300 according to an embodiment of the present invention obtains a touch input applied to the accept button 3140 , the server 50 sends a message indicating that the delivery is performed displayed on the delivery reception interface 3100 . , see FIG. 1).

11 is a diagram illustrating a delivery reception interface in which a cost bid selection button is displayed according to a second application according to another embodiment of the present invention.

When the second application 300 according to another embodiment of the present invention obtains a touch input applied to the accept button 3140 (see FIG. 10 ), a fee bidding selection element 3160 is displayed on the touch screen 110 . can be displayed in The cost bid selection element 3160 may include a plurality of selection elements 3161 , 3162 , 3163 . For example, the cost bid selection element 3160 may include a no discount selection element 3161 , a 5 percent discount selection element 3162 , and a 10 percent discount selection element 3163 .

When the second application 300 obtains a touch input applied to any one of the plurality of selection elements 3161 , 3162 , and 3163 , the second application 300 may set information on the touched selection element as a cost bid selection element.

The delivery reception interface 3100 according to another embodiment of the present invention may include a transmit button 3165 . When the second application 300 acquires a touch input applied to the transmission button 3165, the cost bid selection element 3160 is set with a message indicating that the delivery is performed displayed on the delivery reception interface 3100. The information may be transmitted to the server 50 .

The server 50 (refer to FIG. 1 ) may classify the reception message of the corresponding delivery into each case of the plurality of selection elements 3161 , 3162 , and 3163 . For example, for the delivery, a group of movers set with a no-discount selection element 3161 , a group of movers with a 5-percent discount selection element 3162 set, and a group of movers with a 10-percent-discount selection element 3163 set. can be divided into The server 50 (refer to FIG. 1 ) may select a mover that preferentially performs a corresponding discovery for movers who have selected a high discount.

The server 50 (refer to FIG. 1 ) may calculate a basic cost based on a loading location and an unloading location of the corresponding delivery. For example, the greater the distance between the loading location element 3112 (see FIG. 10 ) and the unloading location element 3122 (see FIG. 10 ), the higher the base cost may be. For example, the greater the distance between the loading station element 3113 (see FIG. 10 ) and the unloading station element 3123 (see FIG. 10 ), the higher the base cost may be. For example, the higher the number of metro stations located on the path between the loading station element 3113 (see FIG. 10 ) and the unloading station element 3123 (see FIG. 10 ), the higher the base cost may be. For example, the greater the distance between the loading location element 3112 (see FIG. 10 ) and the loading station element 3113 (see FIG. 10 ), the higher the base cost may be. For example, the greater the distance between the unloading location element 3122 (see FIG. 10 ) and the unloading station element 3123, the higher the base cost may be.

12 is a diagram illustrating an acceptance approval waiting state in a delivery reception interface according to an embodiment of the present invention.

When a touch is applied to the accept button (3150, see FIG. 10) in the delivery reception interface (3100, see FIGS. 10 and 11) or a touch is applied to the transmit button (3165, see FIG. 11), the second application 300 may transmit a message for accepting the execution of the corresponding delivery to the server 50 (refer to FIG. 1 ).

Referring to FIG. 12 , the second application 300 may display a standby state until it receives an acceptance approval message or an acceptance rejection message from the server 50 (see FIG. 1 ). For example, the second application 300 may display on the touch screen 110 a guide phrase "A request for acceptance approval is being requested. Please wait for a moment."

13 is a diagram illustrating a state in which delivery acceptance is approved or rejected in the delivery reception interface according to an embodiment of the present invention. 13 (a) is a diagram illustrating a state in which acceptance is approved in the delivery reception interface 3100 . 13B is a diagram illustrating a state in which acceptance is rejected in the delivery reception interface 3100 .

Referring to FIG. 13 , an acceptance approval message is transmitted to the delivery reception interface 3100 of a mover selected as a mover to be performed of the corresponding delivery from among the movers who have accepted the execution of the delivery in the delivery reception interface 3100 , and the touch screen 110 , an acceptance rejection message may be transmitted to the delivery reception interface 3100 of a mover that is not selected as a mover to be performed of the corresponding delivery, and may be displayed on the touch screen 110 .

14 is a diagram illustrating a state in which delivery is received or rejected in the delivery order interface 2100 according to an embodiment of the present invention. 14 (a) is a diagram illustrating a state in which the delivery order is received in the delivery order interface 2100 . 14 (b) is a diagram illustrating a state in which the delivery order is not received in the delivery order interface 2100 .

Referring to FIG. 14 , an acceptance approval message is transmitted to a mover selected according to a certain principle among the movers who have accepted the corresponding delivery in the delivery reception interface 3100 (see FIGS. 10 to 12 ), and the delivery order interface ( A delivery reception message may be transmitted to 2100 , along with a discount condition of the selected mover, and displayed on the touch screen 110 . For example, a message “5% discount, delivery received” may be displayed on the touch screen 110 .

A predetermined principle for selecting a mover to perform the corresponding discovery may be, for example, selecting a mover that offers the most discount from among movers capable of performing the corresponding discovery.

A predetermined principle for selecting a mover to perform the corresponding discovery may be, for example, selecting a mover that first accepted the corresponding discovery from among movers capable of performing the corresponding discovery. The order of accepting the delivery may be the order in which the mover's acceptance message arrives at the server 50 (refer to FIG. 1 ).

If there is no mover that has accepted the execution of the delivery in the delivery reception interface 3100 (refer to FIGS. 10 to 12), or there is a mover that has accepted the execution of the delivery, but it is not possible, the server 50 (refer to FIG. 1) When it is determined, an order rejection message may be transmitted and displayed on the touch screen 110 . The order rejection message may be a message indicating that delivery is not received in the delivery order interface 2100 . For example, the message “No movers available” may be displayed on the touch screen 110 . The order rejection message may be referred to as a “delivery order rejection message”.

15 is a diagram illustrating an initial screen of a mover app according to an embodiment of the present invention. 15 may be a diagram illustrating the mover app home interface 3200 .

Referring to FIG. 15 , the mover app home interface 3200 may include a map 3105 . The map 3105 of the mover app home interface 3200 may correspond to the map 3105 (refer to FIG. 10 ) of the delivery reception interface 3105 (see FIG. 10 ).

The mover app home interface 3200 may include a status window 3210 . The status window 3210 may be displayed on the map 3105 . The second application 300 may display a place necessary for the mover to perform discovery on the map 3105 in the status window 3210 .

The mover app home interface 3200 may include a schedule window 3220 . The schedule window 3220 may display a schedule (or task) to be currently performed by the corresponding mover in the entire schedule. For example, the second application 300 may display a schedule to be currently performed and a schedule to be performed next in the schedule window 3220 . For example, a message “Move to Isu Station (Line 4) to board” may be displayed in the schedule window 3220 as a current schedule. For example, a message “moving/arriving to Sadang Station (Line 4)” may be displayed in the schedule window 3220 as the next schedule to be performed.

The contents displayed on the schedule window 3220 may be displayed on the status window 3210 . The current schedule displayed in the schedule window 3220 may be "Move to Isu Station (Line 4) and board". In the status window 3210 , the current location and Isu Station (Line 4) related to the current schedule displayed in the schedule window 3210 may be displayed. Alternatively, an arrow indicating movement from the current location to Isu Station (Line 4) related to the current schedule displayed in the schedule window 3220 may be displayed on the map 3105 in the status window 3210 . The next schedule to be performed displayed on the schedule window 3220 may be “Move/arrival to Sadang Station (Line 4)”. In the status window 3210, Isu Station (Line 4) and Sadang Station (Line 4) related to the next schedule to be performed displayed on the schedule window 3210 may be displayed. Alternatively, an arrow indicating movement from Isu Station (Line 4) to Sadang Station (Line 4) related to the next schedule displayed in the schedule window 3220 may be displayed on the map 3105 in the status window 3210 .

The mover app home interface 3200 may include a delivery view button 3230 . A plurality of delivery view buttons 3230 may be provided. When there are two deliveries to be performed by the mover, the view delivery button 3230 includes a first view delivery button 3231 , a second view delivery button 3232 , and a view full delivery button 3233 . may include.

When the second application 300 obtains a touch input applied to the delivery view button 3230, the second application 300 may display a corresponding delivery schedule on the mover schedule confirmation interface 3400 (refer to FIGS. 16 to 18). For example, when the second application 300 obtains a touch input applied to the first delivery view button 3231, the mover schedule confirmation interface 3400 (see FIGS. 16 to 18) displays the schedule can be displayed.

The mover app home interface 3200 may include a mover app menu group 330 . The mover app menu group 330 may include a mover personal button 331 . When the second application 300 obtains a touch input applied to the mover personal button 331, the mover's residence address, a metro station or bus station near the mover's residence, the mover's work address, or a metro station near the mover's work An interface for acquiring or displaying information such as a bus stop and a commuter's commuting time may be displayed on the touch screen 110 .

The mover app menu group 330 may include a mover setting button 332 . When the second application 300 obtains a touch input applied to the mover setting button 332, an alarm in the mobile terminal 100 (refer to FIG. 1) of the second application 300, and the current position of the mover An interface for setting the GPS, the type (or property) of an article that can be processed by the corresponding mover, etc. may be displayed on the touch screen 110 .

The mover app menu group 330 may include a mover schedule button 333 . When the second application 300 obtains a touch input applied to the mover schedule button 333, the "mover schedule management interface 3330 (refer to FIG. 19)" for managing the delivery of the mover is displayed on the touch screen. (110) can be indicated.

The mover app menu group 340 may include a mover full menu button 334 . When the second application 300 obtains a touch input applied to the mover full menu button 334 , the second application 300 may display an interface related to the mover full menu on the touch screen 110 .

16 is a diagram illustrating a mover schedule confirmation interface indicating a first delivery. Referring to FIG. 16 , when the second application 300 acquires a touch input applied to the first delivery view button 3231 (see FIG. 15 ), a mover schedule confirmation interface that displays information about the first delivery 3400 may be displayed on the touch screen 110 .

The mover schedule confirmation interface 3400 may include a status window 3210 and a schedule window 3220 . The status window 3210 and the schedule window 3220 of the mover schedule check interface 3400 are the status window 3210 (see FIG. 15) and the schedule window 3220, FIG. 15 of the mover app home interface (3200, see FIG. 15) refer to) may correspond to each. The schedule window 3220 of the mover schedule confirmation interface 3400 may display all remaining schedules among schedules of the corresponding delivery. In the status window 3210 , the schedule displayed in the schedule window 3220 may be diagrammed and displayed together with the map 3105 .

17 is a diagram illustrating a mover schedule confirmation interface indicating a second delivery. Referring to FIG. 17 , when the second application 300 acquires a touch input applied to the second delivery view button 3232 (see FIG. 15 ), a mover schedule confirmation interface that displays information about the second delivery 3400 may be displayed on the touch screen 110 .

18 is a diagram illustrating a mover schedule confirmation interface indicating the entire delivery. Referring to FIG. 18 , when the second application 300 obtains a touch input applied to the full delivery view button 3233 (refer to FIG. 15 ), a mover schedule confirmation interface 3400 that displays information about the entire delivery ) may be displayed on the touch screen 110 .

The full delivery may mean delivery in which the first delivery and the second delivery are integrated. For example, the entire delivery schedule of the corresponding mover may be a combination of the schedule of the first delivery and the schedule of the second delivery. The schedule of the first delivery and the schedule of the second delivery may be performed by the server 50 (refer to FIG. 1 ).

The first delivery schedule and the second delivery schedule may overlap. For example, the first delivery schedule and the second delivery schedule may share a section between Bangbae Station and Gyodae Station on Seoul Subway Line 2 . In this way, when the individual deliveries of the corresponding mover overlap each other, the delivery efficiency of the corresponding mover may be improved.

The public transportation means used by the mover in the present invention is not limited to the metro, and includes an express bus, a railway, an express rail, or KTX, or SRT, a city bus, a wide area bus, etc. It can be included in public transport. For example, it is said that a mover's personal schedule is to go on a business trip from Busan to Seoul by KTX, and a delivery order interface 2100 according to an embodiment of the present invention in order for a user to urgently deliver goods from near Busan station to near Seoul station. , see Figs. 7 to 9) using the delivery order can be set. In this situation, the mobile terminal 100 (refer to FIG. 1) of the mover may obtain information about the corresponding delivery share from the server 50 (refer to FIG. 1). When the mobile terminal 100 (refer to FIG. 1) of the mover obtains information about the corresponding delivery share from the server 50 (refer to FIG. 1), the second application 300 either accepts the delivery order or rejects it. A delivery reception interface 3100 (refer to FIGS. 10 and 11 ) regarding whether to do so may be displayed on the touch screen 110 . The mover's personal schedule may overlap significantly with the delivery schedule. Therefore, the mover can perform the delivery relatively easily if he adds an additional schedule to his personal schedule. That is, the mover can acquire the delivery cost by spending some time.

19 is a diagram illustrating a mover schedule management interface according to an embodiment of the present invention. Referring to FIG. 19 , when a touch input applied to the mover schedule button 333 is obtained, the second application 300 displays a “mover schedule management interface 3330” for managing the schedule of the mover on the touch screen 110 ) can be displayed.

The mover schedule management interface 3330 may include a delivery list 3331 . The delivery list 3331 may include buttons corresponding to the number of deliveries managed by the mover. For example, if the number of deliveries to be managed by the mover is two (which may be referred to as first and second deliveries, respectively), the delivery list 3331 may include two buttons. The two buttons may correspond to individual deliveries, respectively. The second application 300, for example, when acquiring a touch input applied to a button corresponding to the first delivery, displays the mover schedule management interface 3330 for managing the first delivery on the touch screen 110 . can be displayed

20 is a diagram illustrating a mover schedule management interface for managing the first delivery.

Referring to FIG. 20 , the mover schedule management interface 3330 may include a specific delivery status window 3332 . The delivery status window 3332 may display the status of the first delivery that is the delivery. For example, the state of the first delivery may be “unloaded”. That is, that the state of the first delivery is unloaded may be determined by the server 50 (refer to FIG. 1 ) by comparing the unloading time element 3122 (refer to FIG. 10 ) and the current time. The data determined by the server 50 (refer to FIG. 1 ) may be transmitted to the second application 300 .

The mover schedule management interface 3330 may include a report delivery completion button 3333 . The mover may be in a state in which an article of the first delivery, which is a corresponding delivery, is unloaded. The schedule of the first delivery may be terminated. A subsequent process may be that the mover reports the completion of the first delivery to the server 50 (refer to FIG. 1 ).

21 is a diagram illustrating a mover schedule management interface for reporting completion of delivery. Referring to FIG. 21 , when the second application 300 obtains a touch input applied to the delivery completion report button 3333 (see FIG. 20 ), touch the mover schedule management interface 3330 for the delivery completion report It can be displayed on the screen 110 .

The mover schedule management interface 3330 may include an authentication shot upload button 3334 . The mover may unload the goods of the first delivery, deliver it to the customer, and take an authentication shot. The corresponding authentication shot may be stored in the mobile terminal 100 of the mover (refer to FIG. 1 ). When the second application 300 obtains a touch input applied to the authentication shot upload button 3334, it works with the photo folder of the mobile terminal 100 of the mover (see FIG. 1) to provide an interface for selecting a photo. can

The mover schedule management interface 3330 may include an authentication shot taking button 3335 . The mover may unload the article of the first delivery and deliver it to the customer and activate the mover schedule management interface 3330 . The second application 300 may execute a camera application upon acquiring a touch input applied to the authentication shot taking button 3335 .

The mover schedule management interface 3330 may include a user rating button 3336 . The user can evaluate the mover that performed the discovery. Similarly, the mover can rate the users who use the delivery. For example, when a user contacts a mover and makes an unreasonable request while performing delivery, the mover's evaluation of the user may be relatively low.

The mover schedule management interface 3330 may include a delivery complete send button 3337 . When the second application 300 obtains a touch input applied to the delivery completion transmission button 3337, the server 50 (refer to FIG. 1) sends an authentication shot related to the completion of the delivery and evaluation information for the user. can be sent to

22 is a diagram illustrating a screen in which the second application displays an interface related to the full menu of the mover on the touch screen 110 .

Referring to FIG. 22 , when the mover applies a touch input to the mover full menu button 334, the second application 300 obtains the touch input and displays an interface related to the mover full menu on the touch screen 110. .

A mover bulletin board button 2341 may be displayed on the touch screen 110 . When the second application 300 obtains a touch input applied to the mover bulletin board button 3341 , the second application 300 may display an interface related to the mover bulletin board on the touch screen 110 . The mover bulletin board may form an online community of movers using the delivery network system 10 (refer to FIGS. 1 and 2 ) according to an embodiment of the present invention. Movers can make "friendships" through the mover bulletin board. The movers may jointly use a means of transportation, for example, in a section where the delivery schedules of each mover overlap. For example, the first mover and the second mover may jointly use personal mobility (or taxi) to move a section (eg, a section between Gangnam Station and Yeoksam Elementary School) in which the delivery schedule overlaps.

A mover rating confirmation button 3342 may be displayed on the touch screen 110 . When the second application 300 obtains a touch input applied to the mover rating confirmation button 3342 , the second application 300 may display rating information of the corresponding mover on the touch screen 110 . Accordingly, the mover can easily check his/her grade. The rank of the mover may be calculated based on credits received from the user while the mover uses the delivery network system 10 (refer to FIGS. 1 and 2 ) for a certain period of time.

A view mover statistics button 3343 may be displayed on the touch screen 110 . When the second application 300 acquires a touch input applied to the mover statistics view button 3343, the mover touches history information using the delivery network system 10 (refer to FIGS. 1 and 2). It can be displayed on the screen 110 .

A mover login/logout button 3344 may be displayed on the touch screen 110 . When the second application 300 obtains a touch input applied to the log-in/log-out button 3344 of the mover, the second application 300 may display an interface related to log-in or log-out of the corresponding mover on the touch screen 110 .

A mover announcement button 3345 may be displayed on the touch screen 110 . When the second application 300 obtains a touch input applied to the mover notice button 3345 , the second application 300 may display the mover notice on the touch screen 110 . The mover announcement may include information about the operation of the delivery network system 10 (refer to FIGS. 1 and 2 ).

23 is a diagram illustrating an app server 400 according to an embodiment of the present invention. Referring to FIG. 23 , the app server 400 may mean a server 50 (refer to FIG. 1 ). The app server 400 may include a database unit 410 . The database unit 4000 may store data. The app server 400 may be referred to as a 'delivery app server'.

The database unit 410 may include a delivery DB 411 . The delivery DB 411 may store data or information about each delivery. The database unit 410 may include a mover DB 412 . The mover DB 412 may store data or information related to each mover. The database unit 410 may include a user DB 413 . The user DB 413 may store data or information related to each user. The database unit 410 may include an environment DB 414 . The environment DB 414 may store information/data about a map or a means of transportation.

The app server 400 may include an input unit 430 . The input unit 430 may obtain an input. The input provided to the input unit 430 may include information about the operation and/or setting of the app server 400 .

The app server 400 may include a communication unit 440 . The communication unit 440 may be implemented by a wired and/or wireless communication method. The communication unit 440 may transmit/receive signals or data to and from an external device.

The app server 400 may include a processor 420 . The processor 420 may process or process data. The processor 420 may process data according to an algorithm. The processor 420 may be implemented as a CPU, a circuit board, a logic circuit, or the like. The processor 420 may refer to software running in a computing device.

The processor 420 may transmit/receive signals to and from the database unit 410 . For example, the processor 420 may transmit/receive a database signal SD to and from the database unit 410 . The database signal SD may be, for example, a query requested by the processor 420 from the database unit 410 . The database signal SD may include, for example, data extracted from the database unit 410 .

The processor 420 may transmit/receive signals to and from the input unit 430 . For example, the processor 420 may transmit/receive an input signal SI to and from the input unit 430 . The input signal SI may include, for example, input information obtained by the input unit 430 .

The processor 420 may transmit/receive signals to and from the communication unit 440 . For example, the processor 420 may transmit and receive a communication signal SC with the communication unit 440 . The communication signal SC is, for example, an app in a first application 200 (see FIGS. 1 to 22 ) or a second application 300 (see FIGS. 1 to 22 ) of the mobile terminal 100 (see FIG. 1 ). It may include a signal or data transmitted to the server 400 . The communication signal SC may include, for example, a signal or data to be transmitted from the app server 400 to the mobile terminal 100 (refer to FIG. 1 ).

The processor 420 may include a delivery manager 421 . The delivery manager 421 may create individual deliveries. The delivery manager 421 may search for a mover capable of performing the delivery with respect to the delivery order.

The processor 420 may include a mover manager 422 . The mover manager 422 may transmit/receive signals or information to/from the second application 300 (refer to FIGS. 1 to 22 ) of each mover. For example, the mover manager 422 may receive a signal or information from the second application 300 (refer to FIGS. 1 to 22 ) of the mover and process it. The mover manager 422 may generate or receive a communication signal SC.

The processor 420 may include a user manager 423 . The user manager 423 may transmit/receive signals or information to and from the first application 200 (refer to FIGS. 1 to 22 ) of each user. For example, the user manager 423 may receive a signal or information from the user's first application 200 (refer to FIGS. 1 to 22 ) and process it. The user manager 423 may generate or receive the communication signal SC.

24 is a block diagram of individual delivery data 4100 according to an embodiment of the present invention. 24 may mean a data structure of individual delivery. For example, the individual delivery data 4100 may mean data of individual delivery that is distinguished according to the ID of the delivery ID element 4111 . Individual delivery data 4100 may be stored in a delivery DB 411 (refer to FIG. 23 ).

Referring to FIG. 24 , individual delivery data 4100 may include a delivery head factor 4110 . The delivery head factor 4110 may include basic information of individual delivery data 4100 . The delivery head factor 4110 may include a delivery ID element 4111 . The delivery ID element 4111 may be an identifier of the corresponding delivery. The delivery head factor 4110 may include a user ID element 4112 . The user ID element 4112 may be an identifier of a user who has ordered delivery indicated by the delivery ID element 4111 . The mover ID element 4113 may be an identifier of a mover that performs delivery indicated by the delivery ID element 4111 .

Individual delivery data 4110 may include a loading factor 4120 . The loading factor 4120 may include a loading time component 4121 , a loading location component 4122 , and a loading station component 4123 . The loading time element 4121 , the loading location element 4122 , and the loading station element 4123 of the individual delivery data 4110 is the loading time element 3111 ( FIG. 10 ) of the delivery reception interface 3100 (see FIG. 10 ). 10), a loading place element 3112 (see FIG. 10), and a loading station element 3113 (see FIG. 10).

Individual delivery data 4110 may include an unloading factor 4130 . The unloading factor 4130 may include an unloading visual element 4131 , an unloading location element 4132 , and an unloading station element 4133 . The unloading visual element 4131 , the unloading location element 4132 , and the unloading station element 4133 of the individual delivery data 4110 are the unloading visual elements of the delivery reception interface 3100 (see FIG. 10 ). (3121, see FIG. 10), an unloading location element 3122 (refer to FIG. 10), and an unloading station element 3123 (refer to FIG. 10).

Individual delivery data 4100 may include an article factor 4140 . The article factor 4140 may include an article size element 4141 , an article weight element 4142 , and an article code element 4143 . The article factor 4140 of the individual delivery data 4100 may correspond to the article factor 3130 of the delivery reception interface 3100 (refer to FIG. 10 ).

Individual delivery data 4100 may include a delivery schedule factor 4150 . The delivery schedule factor 4150 may include a schedule segment group 4151 . The schedule segment group 4151 may include a plurality of schedule segments. A plurality of schedule segments can constitute a schedule of the delivery.

Individual delivery data 4100 may include a delivery management factor 4160 . The delivery management factor 4160 may include a delivery evaluation element 4161 . The delivery evaluation element 4161 may be set based on the evaluation of the mover and the evaluation of the user.

The delivery management factor 4160 may include a delivery cost factor 4162 . The delivery cost element 4162 may mean a cost paid by the user for performing the delivery. The delivery cost factor 4162 may be calculated by the server 50 (see FIG. 1 ) based on the loading factor 4120 , the unloading factor 4130 , and the article factor 4140 . The delivery cost component 4162 may be updated by applying the mover's discount rate to the estimated cost.

The delivery management factor 4160 may include a delivery status element 4163 . The delivery status element 4163 may include information about the status of the corresponding delivery. For example, the state of delivery may be divided into a ready state, a moving state to a loading place, a loading completion state, an unloading completion state, and a delivery evaluation completion state, and stored.

25 is a block diagram of mover data 4200 according to an embodiment of the present invention. 25 may mean a data structure of an individual mover. The mover data 4200 may be stored in the mover DB 412 (refer to FIG. 23 ).

Referring to FIG. 25 , mover data 4200 may include a mover personal factor 4210 . The mover personal factor 4210 may mean data related to personal information of a mover. For example, the mover personal factor 4210 may include a mover ID element 4211 . The mover ID element 4211 may correspond to the mover ID element 4113 (see FIG. 24 ) of individual delivery data 4100 (see FIG. 24 ). The mover ID element 4211 may be an ID of one mover.

The mover personal factor 4210 may include a mover rating factor 4212 . The mover rating factor may be calculated based on credits received from the user while the mover indicated by the mover ID element 4211 uses the delivery network system 10 (refer to FIGS. 1 and 2 ) for a certain period of time. The delivery cost factor 4162 (see FIG. 24 ) calculated by the processor 420 (refer to FIG. 23 ) may vary according to the mover rating factor 4212 . For example, the delivery cost element 4162 (refer to FIG. 24 ) may be higher as the 'grade of the mover' indicated by the mover rating element 4212 is excellent. When the 'grade of the mover' is relatively high, it may mean that the 'grade of the mover' is relatively good. In this case, the delivery cost element 4162 (refer to FIG. 24 ) may form a positive correlation with the 'mover rating' indicated by the mover rating element 4212 .

The mover personal factor 4210 may include a mover environment element 4213 . The mover environment element 4213 includes whether or not an alarm in the mobile terminal 100 (refer to FIG. 1) of the second application 300 (refer to FIG. 15) and/or a setting state, a setting state of GPS to determine the current location of the mover, It may include information about the type (or nature) of the article that the mover can handle.

The mover personal factor 4210 may include a mover delivery history 4214 . The mover delivery history 4214 may include history information in which the mover uses the delivery network system 10 (refer to FIGS. 1 and 2 ).

The mover data 4200 may include a delivery schedule factor 4220 . The delivery schedule factor 4220 may include a delivery list 4221 . The delivery list 4221 may include information on delivery to be performed by the corresponding mover. For example, the delivery list 4221 may include a delivery ID element 4111 (refer to FIG. 24 ) of delivery to be performed by the corresponding mover. Here, 'corresponding mover' may mean a mover indicated by the mover ID element 4211 .

The delivery schedule factor 4220 may include an individual delivery schedule group 4222 . The individual delivery schedule group 4222 may include a delivery schedule factor 4150 (refer to FIG. 24 ) of individual delivery data 4100 (refer to FIG. 24 ) of each individual delivery to be performed by the corresponding mover. For example, the individual delivery schedule group 4222 is a collection of delivery schedule factors 4150 (see FIG. 24 ) corresponding to each delivery ID element 4111 (see FIG. 24 ) of the delivery list 4221 . can do.

The delivery schedule factor 4220 may include an integrated schedule 4223 . The integrated schedule 4223 may mean a schedule in which individual deliveries to be performed by a corresponding mover are integrated into one. The delivery manager 5000 (refer to FIG. 23 ) may create an integrated schedule 4223 based on the individual delivery schedule group 4222 .

26 is a diagram illustrating a data structure of a schedule according to an embodiment of the present invention. Referring to FIG. 26A , a schedule ITIN100 may include a plurality of schedule segments ITIN1000. The schedule segment ITIN1000 may be referred to as a “segment”.

The segment ITIN1000 may be a node constituting the schedule ITIN100. Looking at the spatial concept, the connection of the place element ITIN1200 of the segment ITIN1000 may mean a path according to the schedule ITIN100.

The plurality of schedule segments ITIN1000 may be arranged in chronological order. That is, the plurality of schedule segments ITIN1000 may be arranged in time series. For example, two adjacent schedule segments ITIN1000 among the plurality of schedule segments ITIN1000 may have a temporal relationship with each other. For example, the second schedule segment ITIN1000-2 may be performed later than the first schedule segment ITIN1000-1.

Among the two adjacent schedule segments ITIN1000, the temporally earlier schedule segment ITIN1000 may be referred to as a 'pre-scheduled segment', and the temporally late schedule segment ITIN1000 may be referred to as a 'later schedule segment' or 'corresponding schedule segment'. can be called The line schedule segment may be referred to as a line segment. The later schedule segment may be referred to as a later segment.

For example, the k-th schedule segment ITIN1000-k may be a 'pre-scheduled segment' of the (k+1)-th schedule segment ITIN1000-(k+1). For example, the (k+1)th schedule segment ITIN1000-(k+1) may be a 'post schedule segment' of the kth schedule segment ITIN1000-k.

Referring to FIG. 26B , a schedule segment ITIN1000 may include a visual element ITIN1100. The time element ITIN1100 may mean a time at which the schedule segment ITIN1000 is performed.

The schedule segment ITIN1000 may include a venue element ITIN1200. The place element ITIN1200 may mean a place where the schedule segment ITIN1000 is performed.

The schedule segment ITIN1000 may include a required time element ITIN1300. The required time element ITIN1300 is a place element (ITIN1200, hereinafter) of the corresponding schedule segment ITIN1000 in a place element (ITIN1200, hereinafter may be referred to as a 'line place element') of the 'line schedule segment' of the corresponding schedule segment ITIN1000. It may mean the estimated time required to move to the 'corresponding place element').

For example, the required time element ITIN1300 of the second schedule segment ITIN1000-2 is the place element ITIN1200 of the first schedule segment ITIN1000-1 to the place element ITIN1000-2 of the second schedule segment ITIN1000-2. ITIN1200) can mean the estimated time it takes to travel.

In the case of the best segment (ITIN1000-1), the required time element (ITIN1300) may not be defined. That is, the required time element ITIN1300 of the first schedule segment ITIN1000-1 may be set to 'NULL'.

The processor 420 (refer to FIG. 23 ) may calculate the required time element ITIN1300 . The processor 420 (refer to FIG. 23 ) configures a place element (ITIN1200, corresponding place element) of the corresponding schedule segment ITIN1000-(k+1) and a place element (ITIN1200, line place element) of the line schedule segment ITIN1000-k. ), the required time element ITIN1300 of the corresponding schedule segment ITIN1000-(k+1) may be calculated. The processor 420 (refer to FIG. 23 ) may use the environment DB 414 (refer to FIG. 23 ) in calculating the required time element ITIN1300 .

The schedule segment ITIN1000 may include an action code element ITIN1400. The action element ITIN1400 may include an action to be performed by the corresponding mover in the corresponding schedule segment ITIN1000-(k+1).

The action code element ITIN1400 may basically mean 'arrive at the place element ITIN1200'. For example, the action code element ITIN1400 may result in a place element ITIN1200 originating from a loading place element 2112 (see Figures 7-9) of the delivery order interface 2100 (see Figures 7-9); It may be a “loading behavior code”. For example, the action code element ITIN1400 is the place element ITIN1200 resulting from the unloading place element 2122 (see Figs. 7-9) of the delivery order interface 2100 (see Figs. 7-9). , "unloading behavior code". For example, the action code element ITIN1400 may be a loading place element 2112 (see Figs. 7-9) or an unloading place element 2112 or an unloading place element of the delivery order interface 2100 (see Figs. 7-9) where the place element ITIN1200 is (2122, see Figs. 7-9), it may be "arrival behavior code".

The loading action code may mean loading a corresponding article upon arriving at the place element ITIN1200. The arrival behavior code may mean arriving at the place ITIN1200. The unloading action code may mean unloading an article upon arrival at the place element (ITIN12000).

The schedule segment ITIN1000 may include a delivery ID element ITIN1500. The delivery ID element ITIN1500 may mean an ID of a delivery to which the corresponding schedule segment ITIN1000-(k+1) belongs. The delivery ID element ITIN1500 may mean a delivery ID element 4111 of the delivery DB 411 (refer to FIG. 24 ).

27 is a block diagram of user data 4300 according to an embodiment of the present invention. The user data 4300 may be stored in the user DB 413 (refer to FIG. 23 ). The user data 4300 may include one user or information or data of a corresponding user.

Referring to FIG. 27 , user data 4300 may include a user personal factor 4310 . The user personal factor 4310 may include a user ID element 4311 . The user ID element 4311 may correspond to the user ID element 4112 (refer to FIG. 24 ) of the delivery DB 411 (see FIG. 24 ).

The user personal factor 4310 may include a user rating element 4312 . The user rating factor may be calculated based on the credit received from the mover while the user indicated by the user ID element 4311 uses the delivery network system 10 (refer to FIGS. 1 and 2 ) for a certain period of time. The delivery cost factor 4162 (see FIG. 24 ) calculated by the processor 420 (refer to FIG. 23 ) may vary according to the user rating factor 4312 . For example, the delivery cost element 4162 (refer to FIG. 24 ) may be lower as the 'user rating' indicated by the user rating element 4312 is superior. A relatively high 'user's grade' may mean that the 'user's grade' is relatively superior. In this case, the delivery cost element 4162 (refer to FIG. 24 ) may form a negative correlation with the 'user rating' indicated by the user rating element 4312 .

The user personal factor 4310 may include a user environment element 4313 . The user environment element 4313 may include the user's personal information (for example, residence address, a station or bus stop near the residence, work address, a subway station or bus stop near the work place, work time, work time, etc.), etc. It may contain information about

The user personal factor 4310 may include a user delivery history 4314 . The user discovery history 4314 may include history information that the corresponding user used the delivery network system 10 (refer to FIGS. 1 and 2 ).

28 is a block diagram of environment data 4400 according to an embodiment of the present invention. The environment data 4400 may be stored in the environment DB 414 (refer to FIG. 23 ). Referring to FIG. 28 , the environment DB 4400 may include a map factor 4410 . The map factor 4410 may include information about a map.

The map factor 4410 may include a base map element 4411 . The base map element 4411 may include information about geography, a road, an address and GPS at each point, and the like.

The map factor 4410 may include a metro line element 4412 . The metro line element 4412 may include information about a location of a metro station, a route of a metro, and the like. The metro may be understood as a concept including a railroad and an express rail, or KTX, or SRT.

The map factor 4410 may include a bus line element 4413 . The bus line element 4412 may include information regarding the location of a bus stop, a location of a bus terminal, a bus route, and the like. A bus may be understood as a concept including a city bus, a wide-area bus, and an express bus.

The environment DB 4400 may include a required time factor 4420 . The required time factor 4420 may store information about the estimated required time for each transportation means. The means of transportation may include at least one of a metro, a bus, and walking. In some cases, the means of movement may include personal mobility. Personal mobility may be, for example, an electric kickboard.

The time spent factor 4420 may include a metro time spent component 4421 . The metro travel time element 4421 may include information about an estimated travel time between two adjacent metro stations (or railway stations or high-speed rail stations). The metro required time element 4421 may separately store information about the estimated required time for each time zone. For example, the estimated time required from Gangnam Station on Seoul Subway Line 2 to Yeoksam Station may be relatively large during commuting time and relatively small during non-commuting time.

The metro required time element 4421 may be data corresponding to each section (with a direction) set in the metro line element 4411 . For example, the metro required time element 4421 may mean a set of data regarding an expected time used in 'each section set in the metro line element 4411'. 'Each section set in the metro line element 4411' may be a path from one station to an adjacent station in the metro line element 4411.

The duration factor 4420 may include a bus duration component 4422 . The bus travel time element 4422 may include information about the estimated travel time between two adjacent bus stops (or terminals). The bus required time element 4422 may separately store information about the expected required time for each time zone.

The bus required time element 4422 may be data corresponding to each section (with a direction) set in the bus line element 4412 . For example, the bus required time element 4422 may mean a set of data regarding an expected time used in 'each section set in the bus line element 4412 '. 'Each section set in the bus line element 4412' may be a path from one station to an adjacent station in the bus line element 4412.

The time taken factor 4420 can include a walk time factor 4423 . The walking time element 4423 may include information about the speed of a person moving on foot. The walking time element 4423 may vary depending on the person traveling on foot. A person moving on foot may be, for example, a mover. For example, the walking time component 4423 may vary according to the gender or age of the mover.

29 is a diagram illustrating a delivery order data form and a delivery cancellation data form according to an embodiment of the present invention.

Referring to (a) of Figure 29, the delivery order data form DF100 is obtained by the first application 200 (see Figures 7 to 9) from the delivery order interface 2100 (see Figures 7 to 9). It may be a data form that transmits one input to the server 50 (refer to FIG. 1). One data object according to the delivery order data form DF100 may correspond to one delivery order. The delivery order data form DF100 may be temporarily stored in a memory (not shown) of the app server 400 (refer to FIG. 23 ). The delivery order data form DF100 is a message transmitted by the first application 100 (see FIGS. 7 to 9 ) to the server 50 (see FIG. 1 ) and may be referred to as a “delivery order request message”.

The delivery order data form DF100 may include user ID data DF111. User ID data (DF111), the first application (200, see FIGS. 7 to 9) receives the input obtained from the delivery order interface (2100, see FIGS. 7 to 9) to the server (50, see FIG. 1) It may be data that is transmitted together when transmitting. The user ID data DF111 may be an ID of a user who has transmitted the delivery order request message.

The delivery order data form DF100 may include loading time data DF121 and loading location data DF122. The loading time data DF121 and the loading location data DF122 may be data based on the loading time element 2111 (refer to FIGS. 7 to 9 ) and the loading location element 2112 (refer to FIGS. 7 to 9 ), respectively.

The delivery order data form DF100 may include unloading time data DF131 and unloading location data DF132. The unloading time data DF131 and the unloading location data DF132 are data based on the unloading time element 2121 (refer to FIGS. 7 to 9) and the unloading location element 2122 (refer to FIGS. 7 to 9), respectively. can be

The delivery order data form DF100 may include article size data DF141, article weight data DF142, and article code data DF143. The article size data DF141, the article weight data DF142, and the article code data DF143 are, respectively, an article size element 2131 (see FIGS. 7 to 9 ) and an article weight element 2132 , see FIGS. 7 to 9 , respectively. ), and data based on the article code element 2133 (see FIGS. 7 to 9 ). The article data DF141, DF142, and DF143 may refer to at least one of article size data DF141, article weight data DF142, and article code data DF143.

The delivery order data form DF100 may include mover selection data DF151. The mover selection data DF151 may be data based on the mover selection element 2140 (refer to FIGS. 7 to 9 ).

Referring to FIG. 29B , the delivery cancellation data form DF190 may include cancellation flag data DF191. The cancellation flag data DF191 may include a flag related to "request cancellation of delivery". A flag of the cancellation flag data DF191 may be, for example, “1”.

The delivery cancellation data form DF190 may include delivery ID data DF192. The delivery ID data DF192 may include ID information of delivery to be canceled.

30 is a diagram illustrating a delivery source data form DF200 according to an embodiment of the present invention.

Referring to FIG. 30 , the delivery original data form DF200 may be a data form generated by the delivery manager 5000 (refer to FIG. 23 ) using the delivery order data form DF100 (refer to FIG. 29 ). One data object according to the delivery original data form DF200 may correspond to one data object according to the delivery order data form DF100 (refer to FIG. 29 ).

For example, the delivery manager 5000 (refer to FIG. 23) may generate the delivery original data form (DF200) by adding data related to the delivery ID to the delivery order data form (DF100, see FIG. 29). . The delivery original data form DF200 may include delivery ID data DF211. The delivery ID data DF211 may be an identifier of a corresponding delivery order. The delivery order raw data form DF200 may be temporarily stored in a memory (not shown) of the app server 400 (refer to FIG. 23 ).

The delivery raw data form (DF200) includes user ID data (DF212), loading time data (DF221), loading location data (DF222), unloading time data (DF231), unloading location data (DF232), and article size data. (DF241), article weight data (DF242), article code data (DF243), and mover selection data (DF251) may be included.

User ID data (DF212), loading time data (DF221), loading location data (DF222), unloading time data (DF231), unloading location data (DF232), article size data ( DF241), article weight data (DF242), article code data (DF243), and mover selection data (DF251) are user ID data (DF111, see FIG. 29) of the delivery order data form (DF100, see FIG. 29); Loading time data (DF121, see FIG. 29), loading location data (DF122, see FIG. 29), unloading time data (DF131, see FIG. 29), unloading location data (DF132, see FIG. 29), article size data ( DF141 (see FIG. 29), article weight data (DF142, see FIG. 29), article code data (DF143, see FIG. 29), and mover selection data (DF151, see FIG. 29), respectively.

31 is a diagram illustrating an individual delivery data form according to an embodiment of the present invention. One data object according to the individual delivery data form DF300 may correspond to one data object according to the original delivery data form DF200 (refer to FIG. 30 ). The individual delivery data form DF300 may be temporarily stored in a memory (not shown) of the app server 400 (refer to FIG. 23 ). The individual delivery data form DF300 may mean a data structure of "individual delivery data". The individual delivery data form DF300 may be data formed by processing the delivery order data form DF100 (refer to FIG. 29 ).

Referring to FIG. 31 , the delivery manager 5000 (refer to FIG. 23 ) is based on an individual delivery data form (DF300) based on a delivery source data form (DF200, see FIG. 30 ) and an environment DB 414 (see FIG. 23 ). ) can be created. The individual delivery data form DF300 may include a schedule and information on which job delivery is performed.

The data structure of the individual delivery data form DF300 may be the data structure of the schedule ITIN100 (refer to FIG. 26 ). For example, the individual delivery data form DF300 may include a plurality of segments DF310, DF320, DF330, and DF340.

A data structure of each of the plurality of segments DF310, DF320, DF330, and DF340 may be a data structure of a schedule segment ITIN1000 (refer to FIG. 26 ). For example, each of the plurality of segments DF310, DF320, DF330, DF340 includes a visual element DF311, DF321, DF331, DF341, a place element DF312, DF322, DF332, DF342, and a required time element DF313, DF323. , DF333, DF343), behavior code elements (DF314, DF324, DF334, DF344), and delivery ID elements (DF315, DF325, DF335, DF345).

The individual delivery data form DF300 may include a loading segment DF310 , a loading station segment DF320 , an unloading station segment DF330 , and an unloading segment DF340 .

The loading station segment DF320 may be a segment after the loading segment DF310. The loading station segment DF320 may be dependent on the loading segment DF310 . That is, the loading station segment DF320 may be determined according to the loading segment DF310 . For example, the loading station segment DF320 may need to be managed along with the loading segment DF310. The loading segment block DF301 may mean a loading segment DF310 and a loading station segment DF320. The loading segment DF310 may be a reference segment of the loading segment block DF301. For example, the time of the loading time element DF311 of the loading segment DF310 may be the reference time of the loading segment block DF301 .

The unloading station segment DF330 may be a pre-segment of the unloading segment DF340. The unloading station segment DF330 may be dependent on the unloading segment DF340 . That is, the unloading station segment DF330 may be determined according to the unloading segment DF340. For example, the unloading station segment DF330 may need to be managed together with the unloading segment DF340. The unloading segment block DF302 may mean an unloading segment DF340 and an unloading station segment DF330. The unloading segment DF340 may be a reference segment of the unloading segment block DF302. For example, the time of the unloading time element DF341 of the unloading segment DF340 may be the reference time of the unloading segment block DF302 .

The loading segment DF310 may include a loading time element DF311 , a loading place element DF312 , a time required element DF313 , an action code element DF314 , and a delivery ID element DF315 .

The loading time element DF311 may correspond to the loading time data DF221 (refer to FIG. 30 ) of the delivery raw data form DF200 (refer to FIG. 30 ). The loading visual element DF311 of the loading segment DF310 may correspond to the visual element ITIN1100 of the schedule segment ITIN1000 (refer to FIG. 26 ). That is, the visual element ITIN1100 of the loading segment DF310 may be the loading visual element DF311 .

The loading location element DF312 may correspond to the loading location data DF222 (refer to FIG. 30 ) of the delivery raw data form DF200 (refer to FIG. 30 ). The loading place element DF312 of the loading segment DF310 may correspond to the place element ITIN1200 of the schedule segment ITIN1000 (refer to FIG. 26 ). That is, the place element ITIN1200 of the loading segment DF310 may be the loading place element DF312.

The required time element DF313 of the loading segment DF310 may be in a null state.

The action code element DF314 may correspond to the action code element ITIN1400 of the schedule segment ITIN1000 (refer to FIG. 26 ). The behavior code element ITIN1400 of the loading segment DF310 may be set by the delivery manager 5000 (refer to FIG. 23 ). For example, in the process of forming the loading segment DF310 using the loading time data DF221 (refer to FIG. 30 ) and the loading location data DF222, the delivery manager 5000 (refer to FIG. 23 ) may perform an action code element. (DF314) can be set as "loading behavior code".

The delivery ID element DF315 of the loading segment DF310 may correspond to the delivery ID data DF211 of the delivery original data form DF200 (refer to FIG. 30 ). The delivery ID element ITIN1500 (refer to FIG. 26 ) of the loading segment DF310 may be a delivery ID element DF315.

A loading station segment (DF320) may include a loading station visual element (DF321), a loading station location element (DF322), a duration component (DF323), an action code element (DF324), and a delivery ID element (DF325). have.

Loading station location element DF322 is loaded location data (DF222, see FIG. 30) and unloading location data in the delivery raw data form (DF200, see FIG. 30) by the delivery manager 5000 (see FIG. 23). (DF232) and the environment DB (414, see FIG. 23) can be generated based on. For example, the delivery manager 5000 (see FIG. 23) may prepare the loading location data (DF222, see FIG. 30) and unloading location data (DF232) against the metro line element 4412 to the loading station location element (DF322). and unloading station location element DF332. The loading station placement element DF312 of the loading station segment DF320 may correspond to the placement element ITIN1200 of the schedule segment ITIN1000 (refer to FIG. 26 ). That is, the location element ITIN1200 of the loading station segment DF320 may be the loading station location element DF322 .

The duration component DF323 of the loading station segment DF320 is determined by the delivery manager 5000 (see FIG. 23), the loading location component DF312, the loading station location component DF322, and the environment DB 414 (see FIG. 23). can be calculated based on For example, the delivery manager 5000 (see FIG. 23 ) may calculate the distance traveled by comparing the distance between the loading location element DF312 and the loading station location element DF322 to the base map element 4411 , By dividing the calculated moving distance by the walking time factor 4423 (refer to FIG. 28 ), the required time component DF323 may be calculated.

The loading station visual element DF321 of the loading station segment DF320 may correspond to the visual element ITIN1100 of the schedule segment ITIN1000 (refer to FIG. 26 ). That is, the visual element ITIN1100 of the loading station segment DF320 may be the loading station visual element DF321.

Loading station segment DF320 may be executed after execution of loading segment DF310. The time of the loading station visual element DF321 may be the same as or later than the time of the loading time element DF311 . The loading station segment DF320 may be managed by being dependent on the loading segment DF310. For example, the delivery manager 5000 (refer to FIG. 23 ) sets the time of the loading station time element DF321 to the time of the loading time element DF311 plus a fine time (eg, 1 second or 0.1 second). can be set to

The action code element DF324 may correspond to the action code element ITIN1400 of the schedule segment ITIN1000 (refer to FIG. 26 ). The behavior code element ITIN1400 of the loading station segment DF320 may be set by the delivery manager 5000 (refer to FIG. 23 ). For example, the delivery manager 5000 (refer to FIG. 23) uses the loading location data DF222 and the environment DB 414 (refer to FIG. 28) to form the loading station segment DF320, the behavior code element (DF324) can be set as "Arrival behavior code".

The delivery ID element DF325 of the loading station segment DF320 may correspond to the delivery ID data DF211 of the delivery raw data form DF200 (refer to FIG. 30 ). The delivery ID element ITIN1500 (see FIG. 26 ) of the loading station segment DF320 may be a delivery ID element DF325.

The unloading station segment DF330 includes an unloading station visual element DF331, an unloading station location element DF332, a duration component DF333, a behavior code element DF334, and a delivery ID element DF335. may include

The unloading station location element DF332 may be derived by the delivery manager 5000 (see FIG. 23 ). The derivation process of the unloading station location element DF332 is as described above. The loading station location element DF332 and the unloading station location element DF332 may form an optimal path to travel from the location of the loading location data DF222 to the location of the unloading location data DF232 .

The loading station location element DF322 and the unloading station location element DF332 are selected from the section of the optimal route from the location of the loading location element DF312 to the location of the unloading location element DF342 in which public transport is involved. It can mean both ends (兩端). For example, the optimal path to travel from the location of the loading location element DF312 to the location of the unloading location element DF342 is to travel from the location of the loading location element DF312 to the location of the loading station location element DF322 a first route to, a second route from the location of the loading station location element DF322 to the location of the unloading station location element DF332, and from the unloading station location element DF332 to the unloading location element DF342 It may include a third path to move.

The unloading station place element DF332 of the unloading station segment DF330 may correspond to the place element ITIN1200 of the schedule segment ITIN1000 (refer to FIG. 26 ). That is, the location element ITIN1200 of the unloading station segment DF330 may be the unloading station location element DF332 .

The duration component DF333 of the unloading station segment DF330 is determined by the delivery manager 5000 (see FIG. 23 ), the loading station location element DF322 , the unloading station location element DF332 and the environment DB 414 ( FIG. 23 ). 23) can be calculated based on For example, the delivery manager 5000 (see FIG. 23 ) may run the section from the loading station location element DF322 to the unloading station location element DF332 against the metro time required component 4421 (see FIG. 28 ). Element DF333 can be calculated.

For example, if the station represented by the loading station location element DF322 is Sadang Station on Seoul Subway Line 2, and the station represented by the unloading station location element DF322 is Gyodae Station on Seoul Subway Line 2, the unloading station segment ( It can be seen how the required time component (DF333) of DF330) is calculated. The section may be from Sadang Station on Seoul Subway Line 2 to Gyodae Station on Seoul Subway Line 2. The corresponding required time compared to the corresponding section may be extracted from the metro required time element 4421 (refer to FIG. 28 ). The delivery manager (5000, see Fig. 23), from the metro required time element (4421, see Fig. 28), the time element from Sadang Station to Bangbae Station, the time element from Bangbae Station to Seocho Station, and the time element from Seocho Station to Gyodae Station. can be extracted. The required time may be calculated by adding up a time element from Sadang Station to Bangbae Station, a time element from Bangbae Station to Seocho Station, and a time element from Seocho Station to Gyodae Station. The delivery manager 5000 (refer to FIG. 23 ) may set the corresponding required time as the required time element DF333 of the unloading station segment DF330.

The unloading station visual element DF331 of the unloading station segment DF330 may correspond to the visual element ITIN1100 of the schedule segment ITIN1000 (refer to FIG. 26 ). That is, the visual element ITIN1100 of the unloading station segment DF330 may be the unloading station visual element DF331.

Since the unloading station segment DF330 is executed before the execution of the unloading segment DF340 , the time of the unloading station visual element DF331 may precede the time of the unloading visual element DF341 . The unloading station segment DF330 may be managed by being dependent on the unloading segment DF340. For example, the delivery manager 5000 (refer to FIG. 23) sets the time of the unloading station time element DF331 to the time of the unloading time data DF231 (refer to FIG. 30) for a fine time (for example, 1 second or 0.1 sec) can be set to the reduced time.

The action code element DF334 may correspond to the action code element ITIN1400 of the schedule segment ITIN1000 (refer to FIG. 26 ). The behavior code element ITIN1400 of the unloading station segment DF330 may be set by the delivery manager 5000 (refer to FIG. 23 ). For example, in the process of forming the unloading station segment DF330 using the unloading location data DF232 and the environment data 4400 (refer to FIG. 28), the delivery manager 5000 (refer to FIG. 23) acts Code element DF334 may be set to "Arrival behavior code".

The delivery ID element DF335 of the unloading station segment DF330 may correspond to the delivery ID data DF211 of the delivery original data form DF200 (refer to FIG. 30 ). A delivery ID element ITIN1500 (refer to FIG. 26 ) of the unloading station segment DF330 may be a delivery ID element DF335.

The unloading segment DF340 may include an unloading visual element DF341, an unloading location element DF342, a duration element DF343, an action code element DF344, and a delivery ID element DF345. have.

The unloading time element DF341 may correspond to the unloading time data DF231 (refer to FIG. 30 ) of the delivery raw data form DF200 (refer to FIG. 30 ). The unloading visual element DF341 of the unloading segment DF340 may correspond to the visual element ITIN1100 of the schedule segment ITIN1000 (refer to FIG. 26 ). That is, the visual element ITIN1100 of the unloading segment DF340 may be the unloading visual element DF341.

The unloading location element DF342 may correspond to the unloading location data DF232 (refer to FIG. 30 ) of the delivery raw data form DF200 (refer to FIG. 30 ). The unloading place element DF342 of the unloading segment DF340 may correspond to the place element ITIN1200 of the schedule segment ITIN1000 (refer to FIG. 26 ). The place element ITIN1200 of the unloading segment DF340 may be the unloading place element DF342 .

The required time element DF343 of the unloading segment DF340 is determined by the delivery manager 5000 (see Fig. 23), the unloading station place element DF332, the unloading place element DF342, and the environment DB 4, Fig. 23 ) can be calculated based on For example, the delivery manager 5000 (see FIG. 23 ) may calculate the moving distance by comparing the distance between the unloading station location element DF332 and the unloading location element DF342 to the base map element 4411 . and dividing the calculated moving distance by the required walking time element 4423 (refer to FIG. 28 ), it is possible to calculate the required time element DF343.

The action code element DF344 may correspond to the action code element ITIN1400 of the schedule segment ITIN1000 (refer to FIG. 26 ). The behavior code element ITIN1400 of the unloading segment DF340 may be set by the delivery manager 5000 (refer to FIG. 23 ). For example, the delivery manager 5000 (refer to FIG. 23) uses the unloading time data (DF231, see FIG. 30) and the unloading location data (DF232) to form the unloading segment DF340, The behavior code element DF314 may be set to “unloading behavior code”.

The delivery ID element DF345 of the unloading segment DF340 may correspond to the delivery ID data DF211 of the delivery original data form DF200 (refer to FIG. 30 ). The delivery ID element ITIN1500 (refer to FIG. 26 ) of the unloading segment DF340 may be a delivery ID element DF345.

The sum of the time components DF323 of the loading station segment DF320, the time components DF333 of the unloading station segment DF330, and the time components DF343 of the unloading segment DF340 are summed up It can be referred to as the "time required for delivery" of the delivery. Here, "corresponding delivery" may mean delivery according to delivery ID elements (DF315, DF325, DF335, DF345). The difference between the time of the unloading time element DF341 and the time of the loading time element DF311 may be referred to as "delivery elapsed time" of the corresponding delivery.

The delivery manager 5000 (refer to FIG. 23 ) may compare an elapsed delivery time and a required delivery time. If the delivery required time is less than or equal to the elapsed delivery time, the delivery manager 5000 (refer to FIG. 23 ) may determine that the delivery can be performed. If the delivery required time is greater than the elapsed delivery time, the delivery manager 5000 (refer to FIG. 23 ) may determine that the delivery cannot be performed.

32 is a diagram illustrating an example of individual delivery data according to the individual delivery data form DF300 according to an embodiment of the present invention. FIG. 32 may be described together with FIG. 31 .

31 and 32 , the structure of the individual delivery data DF300 may be the same as that of the schedule ITIN100 (refer to FIG. 26 ). The individual delivery data DF300 may include a loading segment block DF301 and an unloading segment block DF302. The loading segment block DF301 may include a loading segment DF310 and a loading station segment DF320. The unloading segment block DF302 may include an unloading station segment DF330 and an unloading segment DF340.

Looking at the loading segment DF310, the time of the loading visual element DF311 may be December 24, 2020, 8:00 AM. The place of the loading place element DF312 may be Seoul Bangil Elementary School. The time of the required time element DF313 may be NULL. The behavior code element DF314 may be “L”. “L” may mean loading an article upon arriving at the location of the loading location element DF312. The delivery ID element DF315 may be “DI-2”. “DI-2” may mean “a second separate delivery”.

Looking at loading station segment DF320, the time of loading station visual element DF321 may be December 24, 2020, 8:00 AM. That is, the time of the loading station time element DF321 may be set to be the same as the time of the loading time element DF311 . The location of the loading station location element DF322 may be Bangbae Station on Seoul Line 2. The time of the required time element DF323 is the time required to move from Seoul Bangil Elementary School to Bangbae Station, and may be set to 10 minutes. The action code element DF324 may be "A". "A" may mean arriving at the location of the loading station location element DF322. The delivery ID element DF325 may be “DI-2”.

Looking at the unloading station segment DF330, the time of the unloading station visual element DF331 may be December 24, 2020, 7:00 PM. That is, the time of the unloading station time element DF331 may be set to be the same as the time of the unloading time element DF341 . The location of the unloading station location element DF332 may be Gangnam Station on Seoul Line 2 . The time of the required time element DF333 is the time required to move from Bangbae Station to Gangnam Station, and may be set to 6 minutes. The action code element DF334 may be "A". "A" may mean arriving at the location of the unloading station location element DF332. The delivery ID element DF335 may be “DI-2”.

Looking at the unloading segment DF340, the time of the unloading visual element DF341 may be 7:00 pm on December 24, 2020. The location of the unloading location element DF342 may be Seoul Yeoksam Elementary School. The time of the required time element DF343 may be set to 10 minutes as the time required to move from Gangnam Station to Seoul Yeoksam Elementary School. The action code element DF344 may be “U”. “U” may mean unloading an article upon arrival at the location of the unloading location element DF342. The delivery ID element DF345 may be “DI-2”.

33 : is a figure which showed the integrated delivery data form DF400 and each segment. The integrated delivery data form DF400 may mean a data structure of "integrated delivery data" of one mover. “Integrated delivery data” of one mover may mean an integrated schedule 4223 (refer to FIG. 25 ) of one mover. Alternatively, the integrated delivery data form (DF400) is an integrated schedule (4223, see FIG. 25) of one mover stored in the mover DB (412, see FIG. 23) is extracted, and the memory of the app server (400, see FIG. 23) temporarily It may mean data loaded in (memory, not shown).

Referring to FIG. 33 , the integrated delivery data form DF400 may mean an entire schedule that one mover must perform. That is, each segment of the integrated delivery data form DF400 may mean a schedule performed by a work mover. The integrated delivery data form DF400 may be stored in the mover DB 4200 (refer to FIG. 23 ). For example, the unified delivery data form DF400 may be stored in the unified schedule 4223 (refer to FIG. 25 ) of the delivery schedule factor 4220 (refer to FIG. 25 ).

The unified delivery data form DF400 may include a mover ID element DF401. The ID of the mover ID element DF401 may mean the ID of a mover on which the corresponding integrated delivery data form DF400 is performed.

The structure of the integrated delivery data form DF400 may include the structure of the schedule (ITIN100, see FIG. 26 ). For example, the schedule (ITIN100, see FIG. 26) may be composed of a plurality of schedule segments (ITIN1000, see FIG. 26), and the integrated delivery data form DF400 may be composed of a plurality of segments (DF400-k). .

The plurality of segments DF400-k may be n. Here, n may be a natural number greater than 1. Here, k may be a natural number less than or equal to n. A second segment among the n segments DF400 - k may be a second segment DF400 - 2 . A first segment among the n segments DF400 - k may be a first segment DF400 - 1 . An n-th segment among the n segments DF400-k may be an n-th segment DF400-n. A k-th segment among the n segments DF400-k may be a k-th segment DF400-k.

The k-th segment DF400-k may include a k-th visual element DF400-k-1. The k-th visual element DF400-k-1 may correspond to the visual element ITIN1100 (refer to FIG. 26 ) of the schedule segment ITIN1000 (refer to FIG. 26 ).

The k-th segment DF400-k may include a k-th place element DF400-k-2. The k-th place element DF400-k-2 may correspond to a place element ITIN1200 (refer to FIG. 26 ) of the schedule segment ITIN1000 (refer to FIG. 26 ).

The k-th segment DF400-k may include a k-th required time element DF400-k-3. The k-th required time element DF400-k-3 may correspond to the required time element ITIN1300 (refer to FIG. 26 ) of the schedule segment ITIN1000 (refer to FIG. 26 ).

The k-th segment DF400-k may include a k-th behavior code element DF400-k-4. The kth action code element DF400-k-4 may correspond to the action code element ITIN1400 (refer to FIG. 26 ) of the schedule segment ITIN1000 (refer to FIG. 26 ).

The k-th segment DF400-k may include a k-th delivery ID element DF400-k-5. The k-th delivery ID element DF400-k-5 may correspond to the delivery ID element ITIN1500 (refer to FIG. 26 ) of the schedule segment ITIN1000 (refer to FIG. 26 ).

The plurality of segments DF400-k may be arranged in the integrated delivery data form DF400 in the order to be performed. For example, the k-th segment DF400-k may be performed before the (k+1)-th segment DF400-(k+1).

34 is a view showing an example of the integrated delivery data form (DF400) according to an embodiment of the present invention.

Referring to FIG. 34 , the mover ID element DF401 of the integrated delivery data form DF400 may be “MI-j”. In “MI-j”, “j” may mean a reference number of one mover. The source of the integrated delivery data form DF400 of FIG. 34 may be the integrated schedule 4223 of the mover having the ID "MI-j" (see FIG. 25) among the data stored in the mover DB 4200 (see FIG. 23). have. That is, in the integrated delivery data form (DF400), the integrated schedule (4223, see FIG. 25) of the mover having the "MI-j" ID is extracted and temporarily stored in the memory (memory, mido) of the app server 400 (see FIG. 23). time) may mean the data loaded in the

Looking at the first segment (DF400-1), the time of the visual element (ITIN1100) is December 24, 2020, 7:00 am, the place of the place element (ITIN1200) is the Seoul Nambu Museum of Art, and the time of the required time element (ITIN1300) is The time may be NULL, the code of the behavior code element ITIN1400 may be "L", and the ID of the delivery ID element ITIN1500 may be "DI-1". “DI-1” may be “first individual delivery”.

Looking at the second segment (DF400-2), the time of the visual element (ITIN1100) is December 24, 2020 at 7:05 am, the place of the place element (ITIN1200) is Sadang Station on Seoul Line 2, and the required time element (ITIN1300) ) is set to 5 minutes as the time required to move from Seoul Nambu Museum of Art to Sadang Station, the code of the action code element (ITIN1400) is "A", and the ID of the delivery ID element (ITIN1500) is "DI-1" "It could be

Looking at the third segment (DF400-3), the time of the visual element (ITIN1100) is 5:50 pm on December 24, 2020, the place of the place element (ITIN1200) is Seoul Subway Line 2 Gyodae Station, and the required time element (ITIN1300) ) is the time required to travel from Sadang Station to Gyodae Station and is set to 6 minutes, the code of the action code element (ITIN1400) is "A", and the ID of the delivery ID element (ITIN1500) is "DI-1". can

Looking at the fourth segment (DF400-4), the time of the visual element (ITIN1100) is December 24, 2020, 6 pm, the place of the place element (ITIN1200) is Seoul National University of Education, and the time of the required time element (ITIN1300) is The time is set to 10 minutes as the time required to travel from Gyodae Station to Seoul National University of Education, the code of the action code element (ITIN1400) is "U", and the ID of the delivery ID element (ITIN1500) is "DI-1". can

Fig. 35 is a view showing an updated integrated delivery data form in which the individual delivery data form of Fig. 32 is added to the integrated delivery data form of Fig. 34; FIG. 36 is a diagram illustrating a state in which serial numbers are newly assigned to each segment of the integrated delivery data form shown in FIG. 35 . FIG. 37 is a diagram illustrating a unified delivery data form modified to enable connection between each segment of the unified delivery shown in FIG. 36 . FIG. 38 is a diagram illustrating a unified delivery data form modified to enable connection between each segment of the unified delivery shown in FIG. 37 .

35 and 36 , the second individual delivery DI-2 may be merged into the integrated delivery data form DF400 configured of the first individual delivery DI-1. The visual element ITIN1100 of the loading segment block DF301 may be between the visual element ITIN1100 of the second segment DF400-2 and the visual element ITIN11000 of the third segment DF400-3. The loading segment block DF301 may be inserted between the second segment DF400-2 and the third segment DF400-3 based on ITIN1100. The unloading segment block DF302 is a visual element. Based on (ITIN1100), it may be inserted after the fourth segment (DF400-4).

The visual element ITIN1100 of the loading station segment DF320 of the inserted loading segment block DF301 may be modified. In FIG. 35 , the time of the visual element ITIN1100 of the loading station segment DF320 is 8:00 am, but in FIG. 36 , the time of the visual element ITIN1100 of the fourth segment DF400-4 is added by the time element ITIN1300 It can be amended to 8:10 a.m.

The visual element ITIN1100 of the unloading station segment DF330 of the inserted unloading segment block DF302 may be modified. In FIG. 35 , the time of the visual element ITIN1100 of the unloading station segment DF330 is 7:00 PM, but in FIG. 36 , the time of the visual element ITIN1100 of the seventh segment DF400-7 is the eighth segment DF400-8 ) may be modified to 6:50 PM by reducing the time of the required time element ITIN1300.

As the segments of the individual delivery data form (DF300) are inserted into the existing integrated delivery data form (DF400) in FIG. 35, it is confirmed in FIG. 36 that the number of each segment of the updated unified delivery data form (DF400) is modified can

For each of the modified numbered segments (DF400-1,2,3,4,5,6,7,8), it can be checked whether the schedule of the corresponding segment is connected in the schedule of the line segment.

When the action code element ITIN1400 of the corresponding segment and the action code element ITIN1400 of the line segment are both "A", it may be determined that the schedule of the corresponding segment is connected from the schedule of the line segment.

When the action code element ITIN1400 of the corresponding segment is "L" and the action code element ITIN1400 of the line segment is "U", it may be determined that the schedule of the corresponding segment is not connected from the schedule of the line segment. That is, when an article is unloaded from a line segment and another article is loaded from the segment, the process of moving from the place element ITIN1200 of the line segment to the place element ITIN1200 of the corresponding segment. It may be judged that public transport (eg the metro) should be intervened. In this case, a new segment may be inserted between the line segment and the corresponding segment. The inserted segment may be a segment related to the use of public transportation. That is, the behavior code element ITIN1400 of the inserted segment may be “A”.

In the new segment being inserted, the ID of the delivery ID element (ITIN1500) is the same as the ID of the corresponding segment, the behavior code element (ITIN1400) is "A", and the time of the visual element ITIN1100 is the visual element ( It can be set to the time of ITIN1100). There may be two new segments to be inserted. The two-segment placement element ITIN1200 to be inserted may form an optimal path for moving from the placement element ITIN1200 of the line segment to the placement element ITIN1200 of the corresponding segment. This process forms an optimal path for the delivery manager (5000, see FIG. 23) to move from the loading location data (DF222, see FIG. 30) to the location of the unloading location data (DF232, see FIG. 30). The process of deriving "loading station location element DF332 and unloading station location element DF332" may be the same.

When the behavior code element ITIN1400 of the corresponding segment is “L” and the behavior code element ITIN1400 of the line segment is “A”, a new segment may be inserted in some cases. For example, if the behavior code element (ITIN1400) of the corresponding segment is "L" and the behavior code element (ITIN1400) of the line segment is "A", the delivery manager 5000 (refer to FIG. 23 ) is the place element of the line segment. An optimal movement path can be derived from (ITIN1200) to the place element (ITIN1200) of the corresponding segment. The delivery manager 5000 (see FIG. 23 ) is configured to, if there is another station (or station) on the optimal path from the place element (ITIN1200) of the line segment to the place element (ITIN1200) of the segment, it assigns another station to the place element. (ITIN1200) can be inserted between the segment and the line segment.

For example, with respect to the third segment DF400-3, from Sadang Station of the second segment DF400-2, which is the line segment, to Seoul Bangil Elementary School of the third segment DF400-3, Seoul on the optimal path You can see that there is a Bangbae Station on Line 2.

When the behavior code element ITIN1400 of the corresponding segment is “A” and the behavior code element ITIN1400 of the line segment is “U”, a new segment may be inserted in some cases. For example, if the action code element (ITIN1400) of the corresponding segment is "A" and the action code element (ITIN1400) of the line segment is "U", the delivery manager 5000 (refer to FIG. 23 ) will set the location element of the line segment An optimal path can be derived from (ITIN1200) to the place element (ITIN1200) of the corresponding segment. The delivery manager 5000 (see FIG. 23 ) is configured to, if there is another station (or station) on the optimal path from the place element (ITIN1200) of the line segment to the place element (ITIN1200) of the segment, it assigns another station to the place element. (ITIN1200) can be inserted between the segment and the line segment.

For example, with respect to the seventh segment (DF400-7), from Seoul National University of Education in the sixth segment (DF400-6), which is the line segment, to Gangnam Station in the seventh segment (DF400-7), which is the corresponding segment, Seoul on the optimal path You can see that there is Gyodae Station on Line 2.

Referring to FIG. 37 , it can be confirmed that a new third segment DF400 - 3 is newly added. The third segment DF400-3 of FIG. 37 is inserted between the second segment DF400-2 (line segment) and the third segment DF400-3 (corresponding segment) of FIG. 36, and the second segment DF400 Since the schedule is executed immediately after the execution of -2), it is named “third segment DF400-3”, and the third to eighth segments of FIG. 36 may be corrected as fourth to ninth segments.

Referring to FIG. 38 , it can be confirmed that a new eighth segment DF400 - 8 is newly added. The eighth segment DF400-8 of FIG. 38 is inserted between the seventh segment DF400-7 (line segment) and the eighth segment DF400-8 (corresponding segment) of FIG. 37, and the seventh segment DF400 Since the schedule is executed immediately after the execution of -7), it is named “eighth segment DF400-8”, and the eighth to ninth segments of FIG. 37 may be corrected as ninth through tenth segments. Referring to , the place element (ITIN1200) of the corresponding segment (DF400-4) is Seoul Bangil Elementary School, the place element (ITIN1200) of the line segment (DF400-2) is Sadang Station, and the inserted segment (DF400- The location element ITIN1200 of 3) may form an optimal path moving from the location of the line segment DF400-2 to the location of the corresponding segment DF400-4. At least one of the concept of "shortest distance" and "minimum required time" may be applied to the "optimal path" in moving from the location of the line segment DF400-2 to the location of the corresponding segment DF400-4. have.

As the second individual delivery DI-2 is inserted into the integrated delivery data form DF400, the data of the inserted segment may need to be corrected.

For example, the required time element ITIN1400 of the fourth segment DF400-4 is the place element of the corresponding segment DF400-4 in Bangbae Station, which is the place element ITIN1200 of the added third segment DF400-3. (ITIN1200), which is the time required to travel to Seoul Bangil Elementary School, can be modified to 10 minutes.

For example, the required time element ITIN1400 of the ninth segment DF400-9 is a place element of the corresponding segment DF400-9 in the shift that is the place element ITIN1200 of the added eighth segment DF400-8. (ITIN1200) can be modified to 2 minutes, which is the time it takes to travel to Gangnam Station.

Each element ITIN1100, ITIN1200, ITIN1300, ITIN1400, and ITIN1500 of the newly added segments DF400-3 and DF400-8 may be set by the delivery manager 5000 (refer to FIG. 23 ).

The visual element (ITIN1100) and the delivery ID element (ITIN1500) of the added segment (DF400-3, DF400-8) are the visual element (ITIN1100) and the duration element (ITIN1100) of the segment (DF400-4, DF400-9) ITIN1300).

For example, the time element ITIN1100 of the third segment DF400-3 is the time element ITIN1100 of the fourth segment DF400-4 from 8:00 am to the time element ITIN1100 of the fourth segment DF400-4. (ITIN1300), which is 10 minutes earlier, may be 7:50 AM.

For example, the visual element ITIN1100 of the eighth segment DF400-8 takes the ninth segment DF400-9 at 6:50 PM, which is the visual element ITIN1100 of the ninth segment DF400-9. The time element ITIN1300 may be 6:48 PM, which is two minutes earlier.

The place element (ITIN1200) of the added segment (DF400-3, DF400-8) is the place element (ITIN1200) of the line segment (DF400-2, DF400-7) of the corresponding segment (DF400-4, DF400-9) It may be set to form an optimal path among paths moving to the place element ITIN1200.

Since the added segments DF400-3 and DF400-8 are necessary for optimal path formation, the behavior code element ITIN1400 of the added segments DF400-3 and DF400-8 may be set to "A".

The duration element (ITIN1300) of the added segment (DF400-3, DF400-8) is the segment (DF400-3, DF400-8) added from the place element (ITIN1200) of the line segment (DF400-2, DF400-7) ) can be set to the time required to travel to the place element (ITIN1200).

39 is a diagram illustrating a delivery manager 5000 according to an embodiment of the present invention. FIG. 39 may be described together with FIGS. 29 to 38 .

29 to 39 , the delivery manager 5000 may include an individual delivery processing unit 5100 . The individual delivery processing unit 5100 may form an individual delivery data form DF300 based on the original delivery data form DF200. For example, the individual delivery processing unit 5100 may form an individual delivery data form DF300 based on the delivery raw data form DF200 but using information of the environment data 4400 (see FIG. 28 ). have.

The individual delivery processing unit 5100 may include a station (stop) search module 5110 . The station (stop) search module 5110 may search for a station (or a bus stop, or a bus terminal, or an airport, or a seaport, or a railway station, or a high-speed rail station) closest to a place.

The station (stop) search module 5110 prepares, for example, the loading location data DF222 and the unloading location data DF232 against the map factor 4410 , the loading station location element DF322 and the unloading station A place (DF332) can be extracted. The loading station location element DF322 and the unloading station location DF332 may form an optimal path among the paths from the location of the loading location data DF222 to the location of the unloading location data DF232 .

Each delivery processing unit 5100 may include a visual difference calculation module 5120 . The time difference calculation module 5120 may calculate, for example, a difference between the time of the loading time data DF221 and the time of the unloading time data DF231 . The difference between the time of the loading time data DF221 and the time of the unloading time data DF231 can be referred to as "delivery elapsed time".

The individual delivery processing unit 5100 may include a required time calculation module 5130 . The required time calculation module 5130 may calculate a time required to move from a location in one segment to a location in an adjacent segment. The required time calculation module 5130 is configured to calculate, for example, the time required to move the location of one segment and the location of the adjacent segment from the location of one segment to the location of the adjacent segment in relation to the required time factor 4420 . can

For example, the time required calculating module 5130 calculates the time required to travel from the location of the loading location element DF312 to the location of the loading station location element DF322, and calculates the time required to travel from the location of the loading station segment DF320 to the location of the loading station segment DF320. DF323) can be set. For example, the required time calculation module 5130 calculates the time required to travel from the location of the loading station location element DF323 to the location of the unloading station location element DF332 to calculate the required time for the unloading station segment DF330. It can be set with a time element (DF333). For example, the required time calculation module 5130 calculates the time required to travel from the location of the unloading station location element DF332 to the location of the unloading location element DF342 to calculate the required time of the unloading segment DF340 It can be set by element (DF343).

The time of the required time element DF323 of the loading station segment DF320, the time of the required time element DF333 of the unloading station segment DF330, and the time of the required time element DF343 of the unloading segment DF340 The total time can be referred to as "delivery time required".

The individual delivery processing unit 5100 may include a delivery possibility check module 5140 . The delivery possibility check module 5140 may prepare the required delivery time with the elapsed delivery time. If the delivery required time is less than or equal to the delivery elapsed time, the delivery possibility check module 5140 may determine that the delivery can be performed. Here, the delivery may mean delivery identified by delivery ID data DF211. If the required delivery time is greater than the elapsed delivery time, the delivery possibility check module 5140 may determine that the delivery cannot be performed.

If the delivery possibility check module 5140 determines that the delivery cannot be performed, the individual delivery processing unit 5100 transmits a message regarding the inability to perform the delivery to the corresponding user and the database unit 4000 (FIG. 23) See), you can delete the data related to the delivery. Here, the user may mean a user identified by the user ID data DF212.

The individual delivery processing unit 5100 may form (or extract) the loading segment DF310 based on the delivery raw data form DF200. The individual delivery processing unit 5100 may set the time of the loading time data DF221 to the time of the loading time element DF311 . The individual delivery processing unit 5100 may set the location of the loading location data DF222 to the location of the loading location element DF312. The setting of the required time element DF313 of the loading segment DF310 is as described above. In the process of forming the loading segment DF310 based on the loading time data DF221 and the loading location data DF222, the individual delivery processing unit 5100 sets the behavior code element DF314 as "loading behavior code" or Can be set to "L". The loading behavior code indicates that the schedule to be performed in the corresponding segment (ITIN1000, see FIG. 26) is a visual element (ITIN1100, see FIG. 26) in the location element (ITIN1200, see FIG. 26) of the corresponding schedule segment (ITIN1000, see FIG. 26) Refer to) may mean loading the article at the time of The individual delivery processing unit 5100 may set the ID of the delivery ID data DF211 to the ID of the delivery ID element DF315.

The individual delivery processing unit 5100 may form (or extract) the loading station segment DF320 based on the delivery raw data form DF200. The loading station time element DF320 may be set based on the loading time data DF221 . For example, the time of the loading station time element DF320 may be substantially the same as the time of the loading time data DF221 . For example, the time of the loading station time element DF321 may be the same as the time of the loading time data DF221 . For another example, as described above, the time of the loading station time element DF321 may be set to a time when a fine time (or a minute time, differential time) has elapsed from the time of the loading time data DF221 . The location of the loading station location element DF322 may be set as described above. The individual delivery processing unit 5100 may set the behavior code element DF324 of the loading station segment DF320 to “arrival behavior code” or “A” in the process of forming the loading station segment DF320 . The arrival behavior code may mean that the schedule to be performed in the corresponding segment (ITIN1000, see FIG. 26) arrives at the location of the place element (ITIN1200, see FIG. 26) of the corresponding schedule segment (ITIN1000, see FIG. 26). . For example, if the behavior code element DF324 of the loading station segment DF320 is an arrival behavior code, it means that the schedule to be performed in the loading station segment DF320 must arrive at the place of the loading station venue element DF322. can mean

The individual delivery processing unit 5100 may form (or extract) the unloading station segment DF330 based on the delivery raw data form DF200. The unloading station time element DF330 may be set based on the unloading time data DF231. For example, the time of the unloading station time element DF331 may be substantially the same as the time of the unloading time data DF231 . For example, the time of the unloading station time element DF331 may be the same as the time of the unloading time data DF231 . For another example, as described above, the time of the unloading station time element DF331 may be set to a time earlier than the time of the unloading time data DF231 by a minute (or minute time, differential time). . The location of the unloading station location element DF332 may be set as described above. The required time element DF333 and the delivery ID element DF335 of the unloading station segment DF330 may be set as described above. The individual delivery processing unit 5100 may set the behavior code element DF334 of the unloading station segment DF330 to "arrival behavior code" in the process of forming the unloading station segment DF330. When the behavior code element DF334 of the unloading station segment DF330 is the arrival behavior code, it means that the schedule to be performed in the unloading station segment DF330 must arrive at the location of the unloading station venue element DF332. can do.

The individual delivery processing unit 5100 may form (or extract) the unloading segment DF340 based on the delivery raw data form DF200. The individual delivery processing unit 5100 may set the time of the unloading time data DF231 to the time of the unloading time element DF341 . The individual delivery processing unit 5100 may set the location of the unloading location data DF232 to the location of the unloading location element DF342 . The setting of the required time element DF343 of the unloading segment DF340 is the same as described above. In the process of forming the unloading segment DF340 based on the unloading time data DF231 and the unloading location data DF232, the individual delivery processing unit 5100 "unloads the behavior code element DF344" Behavior code" or "U". The unloading behavior code indicates that the schedule to be performed in the corresponding segment (ITIN1000, see FIG. 26) is a visual element (ITIN1100, see FIG. 26) in the place element (ITIN1200, see FIG. 26) of the corresponding schedule segment (ITIN1000, see FIG. 26) 26) may mean unloading the goods at the time of The individual delivery processing unit 5100 may set the ID of the delivery ID data DF211 to the ID of the delivery ID element DF345.

29 to 39 , the delivery manager 5000 may include an integrated delivery processing unit 5200 . The unified delivery processing unit 5200 may manage the unified delivery data form DF400. The integrated delivery processing unit 5200 may determine a mover capable of performing the individual delivery data form DF300. To this end, the integrated delivery processing unit 5200 checks whether the updated delivery data form (DF400) in which the individual delivery data form (DF300) is integrated into the unified delivery data form (DF400) of each mover can be executed. can judge

The integrated delivery processing unit 5200 may include a classification module 5210 . The classification module 5210 extracts the integrated schedule (4223, see FIG. 25) of one mover from the mover DB (412, see FIG. 23) and stores it in the memory (memory, not shown) of the app server 400 (see FIG. 23). You can set the uploaded data as an integrated delivery data form (DF400).

The classification module 5210 may integrate the individual delivery data form DF300 into the integrated delivery data form DF400 of the corresponding mover. For example, the classification module 5210 may insert the loading segment block DF301 and the unloading segment block DF302 into the integrated delivery data form DF400 of the corresponding mover. The classification module 5210 may sort each segment of the new unified delivery data form DF400 according to the visual element DF400-k-1. At this time, each segment of the inserted individual delivery data form DF300 is managed as a segment block. For example, the loading segment DF310 and the loading station segment DF320 are classified in the integrated delivery data form DF400 based on the time of the loading time element DF311, and the loading station segment DF320 is a loading segment. (DF310) may be disposed adjacent to immediately behind. For example, the unloading station segment DF330 and the unloading segment DF340 are classified in the integrated delivery data form DF400 based on the time of the unloading visual element DF341, but the unloading segment DF340 may be disposed immediately after and adjacent to the unloading station segment DF330.

The integrated delivery processing unit 5200 may include a visual difference calculation module 5220 . The time difference calculation module 5220 is configured to: the time of the visual element DF400-k-1 of one segment DF400-k or the corresponding segment, and the time of the line segment DF400-(k-1). The difference between the time of element DF400-(k-1)-1) can be calculated. The time of the visual element DF400-k-1 of one segment DF400-k and the time of the visual element DF400-(k-1)-1 of the line segment DF400-(k-1) The difference between , may be referred to as "elapsed time".

The integrated delivery processing unit 5200 may include a required time calculation module 5220 . The time required calculation module 5220 is configured to: the place element DF400-( The time required to move to the place of k-1)-2) is calculated with reference to the environment DB 414 (refer to FIG. 23), and the calculated required time is calculated as the required time element (DF400-k) of one segment (DF400-k). k-3) can be set.

The integrated delivery processing unit 5200 may include a mover likelihood check module 5240 . The mover possibility check module 5240 may determine whether the updated integrated delivery data form DF400 can be performed by the corresponding mover.

The mover possibility check module 5240 may compare the "elapsed time (or k-th elapsed time)" of the corresponding segment DF400-k with the time of the k-th required time element DF400-k-3. If the "elapsed time" of one segment DF400-k is greater than or equal to the time of the k-th required time element DF400-k-3, the mover possibility check module 5240 determines whether it is possible to perform the one segment DF400-k. segment can be considered.

If the "elapsed time" of one segment DF400-k is less than the time of the k-th required time element DF400-k-3, the mover possibility check module 5240 performs the segment DF400-k impossible to perform. can be judged as

The mover possibility check module 5240 may determine whether individual delivery can be performed by a corresponding mover while checking the performance possibility of each segment. When it is determined that one segment cannot be performed, the mover possibility check module 5240 may determine that individual discovery according to the individual delivery data form DF300 cannot be performed by the corresponding mover.

When it is determined that all segments can be performed, the mover possibility check module 5240 may determine that individual discovery according to the individual delivery data form DF300 can be performed by the corresponding mover. If it is determined that individual delivery according to the individual delivery data form DF300 can be performed by the corresponding mover, the mover possibility check module 5240 sets the ID of the corresponding mover to the delivery-performing mover list (DF500, FIG. 40 ) ) can be described.

If it is determined that individual delivery according to the individual delivery data form (DF300) cannot be performed by the corresponding mover, the mover possibility check module 5240 is the current integrated delivery data form (DF400) to the app server 400 23), it is possible to extract the integrated schedule (4223, see FIG. 25) of another mover and set it as the integrated delivery data form (DF400).

The integrated delivery processing unit 5200 may include a segment concatenation module 5250 . The segment connection module 5250 derives an optimal route of an adjacent segment, derives a route of public transportation on the derived optimal route, and uses both ends of the derived public transportation route as a place element (ITIN1200) A new segment can be inserted between a line segment and the corresponding segment. However, among both ends of the derived public transportation route, an end overlapping with the place element (ITIN1200) of the line segment or the place element (ITIN1200) of the next segment may be excluded.

When the action code element (ITIN1400) of the corresponding segment is "L" and the action code element (ITIN1400) of the line segment is "U", the segment connection module 5250 inserts a new segment between the line segment and the corresponding segment. can

The location of the location element ITIN1200 of the segment to be inserted may form an optimal movement path from the location of the location element ITIN1200 of the line segment to the location of the location element ITIN1200 of the corresponding segment. A function of the segment connection module 5250 may overlap with a function of the station search module 5110 . For example, the segment connection module 5250 may call and use the station search module 5110 as necessary.

The segment connection module 5250 is configured to, when the action code element (ITIN1400) of the corresponding segment is "L" and the action code element (ITIN1400) of the line segment is "A", or the action code element (ITIN1400) of the corresponding segment is " A" and the behavior code element (ITIN1400) of the line segment is "U", the segment connection module 5250 can derive the optimal path from the place element (ITIN1200) of the line segment to the place element (ITIN1200) of the corresponding segment. have. If there is another station (or station) in the derived optimal path, the segment connection module 5250 may insert a segment using the other station as the place element ITIN1200 between the corresponding segment and the line segment.

If it is determined that individual delivery according to the individual delivery data form (DF300) cannot be performed or can be performed by the corresponding mover, the mover possibility check module 5240, the current integrated delivery data form (DF400) ) can be deleted from the memory of the app server (400, see FIG. 23), and an integrated schedule (4223, see FIG. 25) of another mover can be extracted and set as the integrated delivery data form (DF400).

When a new unified delivery DF400 is established, the classification module 5210 may perform the process described above. This process may be performed for all mover ID elements 4211 (refer to FIG. 25) stored in the mover DB 412 (refer to FIG. 23).

The delivery manager 5000 may transmit an inquiry message regarding whether to perform the corresponding delivery to movers determined to be able to perform the corresponding delivery. For example, the delivery manager 5000 asks the movers of the first to n-th mover IDs (DF500-1 to n) listed in the list of movers capable of performing delivery (DF500, see FIG. 40 ) whether to accept the delivery execution. You can send inquiry messages about

The inquiry message regarding whether to accept the delivery execution may include data of an individual delivery data form (DF300, see FIG. 31 ) and data of a delivery original data form (DF200, see FIG. 30 ). For example, the inquiry message regarding whether to accept the delivery may include data of a loading segment (DF310), a loading station segment (DF320), an unloading station segment (DF330), and an unloading segment (DF340). have. For example, the inquiry message regarding whether the delivery is accepted or not may include data of product size data (DF241, see FIG. 30), product weight data (DF241, see FIG. 30), and product code data (DF243). can

When the second application 300 (see FIG. 10) obtains an inquiry message regarding whether to accept the delivery, the second application 300 (see FIG. 10) transmits the delivery reception interface 3100 (see FIG. 10) for the delivery. reference) may be displayed on the touch screen 110 (refer to FIG. 10 ). Information of an inquiry message regarding whether to accept the corresponding delivery may be displayed on the delivery reception interface 3100 (refer to FIG. 10 ) for the corresponding delivery.

The second application 300 (refer to FIG. 10) may obtain acceptance or discount information from the corresponding mover through the delivery reception interface 3100 (refer to FIG. 10). The second application 300 (refer to FIG. 10 ) may transmit whether the mover accepts the delivery and discount information to the server 400 (refer to FIG. 23 ). For example, the second application 300 (refer to FIG. 10) may transmit an acceptance or not response message (DF600, see FIG. 41) to the server 400 (refer to FIG. 23). The mover manager 7000 (refer to FIG. 23 ) may obtain an acceptance or not response message (DF600 (refer to FIG. 41 )) and deliver it to the delivery manager 5000 .

The delivery manager 5000, if the acceptance factor (DF600-2) of the acceptance response message (DF600, see FIG. 41) is "YES", the delivery execution acceptance of the mover ID of the mover ID element (DF600-1) It can be added to the mover list (DF700, see FIG. 42). The delivery manager 5000 may wait for a response from another mover when the acceptance factor DF600-2 of the acceptance response message DF600 (refer to FIG. 41 ) is “NO”.

The delivery manager 5000 may include an active mover selection unit 5300 . The active mover selection unit 5300 may select one mover from among the first to m-th movers DF700-1 to m of the delivery-performing acceptance mover list DF700 (refer to FIG. 42 ).

The active mover selection unit 5300, through the mover signal transmission unit 6200 (see FIG. 43), the first to mth movers (DF700-1 to m) of the delivery-performing acceptance mover list (DF700, see FIG. 42 ) An "acceptance approval message" may be transmitted to the movers selected from among them, and an "acceptance rejection message" may be transmitted to the remaining movers.

When the second application 300 (refer to FIG. 13 ) receives an “acceptance approval message”, it may display a state that acceptance is approved on the delivery reception interface 3100 (refer to FIG. 13 (a)). When the second application 300 (refer to FIG. 13 ) receives an "acceptance rejection message", it may display a state in which acceptance is rejected on the delivery reception interface 3100 (refer to FIG. 13 (b)).

The active mover selection unit 5300, when a mover is selected from the first to m-th movers DF700-1 to m of the delivery execution acceptance mover list DF700 (see FIG. 42), a user signal transmission unit 7200, 43), a "delivery reception completion message" may be transmitted to the corresponding user.

When the first application 200 (see Fig. 14 (a)) receives the "delivery reception completion message", the delivery order interface 2100 (see Fig. 14 (a)) accepts the order of the delivery. It can show the finished form. The "delivery reception completion message" may include discount information of the order delivery. The discount information of the order delivery may be discount information of a mover selected from among the first to mth performance acceptance movers (DF700-1 to m, see FIG. 42 ).

If there is no mover listed in the delivery execution acceptance mover list (DF700, see Fig. 42), the active mover selection unit 5300 sends a message to the user via the user signal transmission unit 7200 (refer to Fig. 43) "Delivery acceptance rejection" message" can be sent.

When the first application 200 (refer to FIG. 14 (b)) receives the "delivery acceptance rejection message", the delivery order interface 2100 (see FIG. 14 (b)) accepts the order of the delivery. may show rejection.

After receiving the delivery order data form DF100 from the first application 200 (refer to FIGS. 7 to 9), if a mover to perform the corresponding delivery (delivery performing mover) is determined or there is no mover to be performed, The corresponding delivery order performed by the corresponding user through the delivery order interface 2100 (refer to FIGS. 7 to 9 ) may be terminated.

After receiving the delivery order data form DF100 from the first application 200 (refer to FIGS. 7 to 9 ), when a mover to perform the corresponding delivery is determined, the delivery manager 5000 provides information about the delivery. Individual delivery data 4100 (see FIG. 24 ) may be generated and stored in the delivery DB 411 (see FIG. 23 ).

After receiving the delivery order data form DF100 from the first application 200 (refer to FIGS. 7 to 9 ), when a mover to perform a corresponding delivery is determined, the delivery manager 5000 may of the mover data 4200 (refer to FIG. 25) may be generated and stored in the mover DB 412 (refer to FIG. 23).

After receiving the delivery order data form DF100 from the first application 200 (refer to FIGS. 7 to 9 ), when a mover to perform the corresponding delivery is determined, the delivery manager 5000 provides the user data of the corresponding user. (4300, see FIG. 27) can be created and stored in the user DB (413, see FIG. 23).

After receiving the delivery order data form DF100 from the first application 200 (refer to FIGS. 7 to 9 ), when a mover to perform a corresponding delivery is determined, the delivery manager 5000 may By extracting the integrated schedule 4223 (see FIG. 25 ) of , the integrated delivery data form DF400 may be formed, and individual delivery data forms DF300 may be merged into the integrated delivery data form DF400. The delivery manager 5000 may update the combined schedule 4223 (refer to FIG. 25 ) of the corresponding delivery performing mover to the merged unified delivery data form DF400.

The delivery manager 5000 includes a mover ID of a delivery performing mover, a delivery order data form (DF100, see FIG. 29), a delivery source data form (DF200, see FIG. 30), an individual delivery data form (DF300, 31), and based on the discovery-performing mover list (DF700, see Fig. 42), mover data (4200, see Fig. 25) of the corresponding discovery-performing mover, and mover data (4200, 4200, of the corresponding retrieve-performing mover). 25) and user data 4300 (refer to FIG. 27) of the corresponding user may be generated.

The delivery manager 5000 includes a mover ID of a delivery performing mover, a delivery order data form (DF100, see FIG. 29), a delivery source data form (DF200, see FIG. 30), and an individual delivery data form (DF300). , based on Fig. 31), the delivery head factor (4110, see Fig. 24), the loading factor (4120, see Fig. 24) of the individual delivery data (4100, see Fig. 24), the unloading factor (4130, Fig. 24), an article factor 4140 (refer to FIG. 24), and a delivery schedule factor 4150 (refer to FIG. 24) may be set.

The delivery manager 5000 sets the discount information of the delivery mover included in the delivery acceptance mover list as the delivery cost element 4162 (see FIG. 24 ) of individual delivery data 4100 (see FIG. 24 ). can

When the delivery order performed by the user through the delivery order interface 2100 (see FIGS. 7 to 9) is terminated, the delivery manager 5000 displays the delivery order data form (DF100, see FIG. 29), Retrieve raw data form (DF200, see Fig. 30), individual delivery data form (DF300, see Fig. 31), unified delivery data form (DF400, see Fig. 33), list of movers capable of delivery (DF500, see Fig. 40) reference), the acceptance or not response message (DF600, see FIG. 41 ), and the delivery acceptance mover list (DF700, see FIG. 42 ) can be deleted.

Circumstances in which a delivery order is canceled may be considered. The integrated delivery processing unit 5200 provided with the delivery cancellation data form DF190 checks the flag related to the "cancellation request of delivery" of the cancellation flag data DF191, and the delivery of the delivery ID data DF192. You can proceed with the cancellation process for the Bury ID.

The integrated delivery processing unit 5200 is configured to include a delivery ID element 4111 of the delivery ID data DF192 and all the individual delivery data 4100 (see FIG. 24 ) among the individual delivery data 4100 (see FIG. 24 ). 24), individual delivery data 4100 (refer to FIG. 24 ) corresponding to the delivery ID data DF192 can be found.

The integrated delivery processing unit 5200 may extract the mover ID element 4113 (refer to FIG. 24 ) of the corresponding individual delivery data 4100 (refer to FIG. 24 ). The integrated delivery processing unit 5200 extracts the integrated schedule 4223 from the mover data 4200 (refer to FIG. 25 ) of the mover corresponding to the corresponding mover ID element 4113 (refer to FIG. 24 ) to extract the integrated delivery data form. (DF400) can be set.

The classification module 5210 may remove the delivery (delivery to be canceled) of the delivery ID data DF192 from the unified delivery data form DF400. For example, the delivery ID of the delivery ID data DF192 is “DI-2”, the unified delivery data form DF400 is shown in FIG. 38 , and the classification module 5210 is the unified delivery data form In (DF400), the segment related to "DI-2" can be deleted.

The required time calculation module 5230 may update the required time element ITIN1300 of each segment of the updated integrated delivery data form DF400. The segment connection module 5250 may update the unified delivery data form DF400 by checking the connection state of adjacent segments of the updated unified delivery data form DF400 .

When the deletion of the segment related to the corresponding delivery from the unified delivery data form DF400 is completed, the unified delivery processing unit 5200 converts the unified delivery schedule 4223 (refer to FIG. 25 ) of the corresponding mover to the updated unified delivery data form. (DF400) can be set. After the merged schedule (4223, see Fig. 25) of the mover is updated, the integrated delivery processing unit 5200, the individual delivery data (4100, see Figure 24), the delivery cancellation data form (DF190), and the integration The delivery data form (DF400) can be deleted.

40 is a diagram illustrating a list of movers capable of performing delivery according to an embodiment of the present invention. Referring to FIG. 40 , the delivery executable mover list DF500 includes a first executable mover DF500-1, a second executable mover DF500-2, and an n-th executable mover DF500-n. may include. n is a natural number and may mean the number of movers capable of performing the corresponding individual delivery. The corresponding individual delivery may mean, for example, individual delivery according to an individual delivery data form (DF300, see FIG. 31 ). Each of the executable movers DF500-1 to n may include ID information of the corresponding mover.

41 is a diagram illustrating an acceptance/non-acceptance response message according to an embodiment of the present invention. Referring to FIG. 41 , the acceptance or not response message DF600 may include a mover ID element DF600-1. The mover ID element DF600 - 1 may be the ID of the mover that has transmitted the acceptance or not response message DF600 .

The acceptance or not response message DF600 may include an acceptance or not element DF600 - 2 . The acceptance factor DF600-2 may be set to "NO" when a touch input is applied to the reject button 3150 (refer to FIG. 10 ) in the delivery reception interface 3100 (refer to FIG. 10 ).

Acceptance element (DF600-2) is, in the delivery reception interface (3100, see Fig. 10 or Fig. 11), a touch input is applied to the accept button (3140, see Fig. 10) and the send button (3165, see Fig. 11) When a touch input is applied, it may be set to "YES".

The acceptance or not response message DF600 may include a discount information element DF600-3. The discount information element DF600-3 may be set as the discount elements 3161, 3162, 3163 selected in the cost bidding 3160 (refer to FIG. 11) of the delivery reception interface 3100 (refer to FIG. 11).

42 is a diagram illustrating a delivery execution acceptance mover list DF700 according to an embodiment of the present invention. Referring to FIG. 42 , the delivery performance acceptance mover list DF700 may include first to mth execution acceptance movers DF700-1 to m. Each performance acceptance mover (DF700-1 to m) may include a mover ID. For example, the mover ID of the first performing acceptance mover (DF700-1) is "first mover ID", and when the acceptability element (DF600-2, see FIG. 41) is "YES", the mover ID element (DF600) -1) may be an ID.

Each performance acceptance mover DF700-1 to m may include discount information. For example, the discount information of the first performance acceptance mover DF700-1 may be “first discount information” and may be discount information of the discount information element DF600-3.

Each performance acceptance mover (DF700-1 to m) may include a mover grade. For example, the grade of the first performing acceptance mover DF700-1 is "first mover grade", and the mover grade of the mover personal factor 4210 (refer to FIG. 25 ) of the first performing acceptance mover DF700-1 It may be a class of element 4212 (see FIG. 25 ).

43 is a diagram illustrating a mover manager and a user manager according to an embodiment of the present invention. 43A is a diagram illustrating a mover manager. 43B is a diagram showing a user manager.

Referring to FIG. 43 , the user manager 7000 according to an embodiment of the present invention may include a user signal receiving unit 7100 . The user signal receiving unit 7100 may receive a signal (or data or information) from the user's first application 200 (refer to FIGS. 7 to 9 ).

For example, the user signal receiving unit 7100 may receive data obtained through the delivery order interface 2100 (see FIGS. 7 to 9 ) from the first application 200 (see FIGS. 7 to 9 ). have. For example, the user signal receiving unit 7100 may receive the delivery order data form DF100 (refer to FIG. 29 ) from the first application 200 (refer to FIGS. 7 to 9 ).

The user signal receiving unit 7100 receives a message (or signal or data) provided from the user's first application 200 (see FIGS. 5 and 7 to 9 ) in each unit of the processor 420 (see FIG. 23 ) (see FIG. 23 ). 23 or FIG. 39 or FIG. 43).

For example, if the message (or signal or data) provided from the user's first application 200 (refer to FIGS. 5 and 7 to 9 ) relates to the reception or cancellation of the delivery, the user signal reception unit 7100 ) may allocate the corresponding message to the delivery manager 5000 (refer to FIG. 39 ).

For example, if the message (or signal or data) provided from the user's first application (200, see FIGS. 5 and 7 to 9 ) relates to the user's related information or to check the delivery status (See FIG. 5 or FIG. 6 ), the user signal receiving unit 7100 may allocate the corresponding message to the user processing unit 7300 .

The user manager 7000 may include a user signal transmission unit 7200 . For example, the user signal transmission unit 7200 may transmit a message (or signal or data) to the first application 200 (refer to FIG. 14 ).

The user manager 7000 may include a user processing unit 7300 . The user processing unit 7300 may process the request message (or signal or data) provided from the first application 200 (see FIGS. 5 and 7 to 9 ) and transmit it to the corresponding user through the user transmission unit 7200 . have.

Referring to FIG. 43 , the mover manager 6000 according to an embodiment of the present invention may include a mover signal receiving unit 6100 . The mover signal receiving unit 6100 may receive a signal (or data or information) from the second application 300 of the mover (refer to FIGS. 10 to 13 and 15 to 22 ).

For example, the mover signal reception unit 6100 may receive data acquired through the delivery reception interface 2100 (see FIGS. 10 to 13 ) from the second application 300 (see FIGS. 10 to 13 ). have. For example, the mover signal reception unit 6100 may receive an acceptance or not response message (DF600 (refer to FIG. 41 )) from the second application 300 (refer to FIG. 10 or 11 ).

The mover signal receiving unit 6100 receives a message (or signal or data) received from the second application 300 of the mover (see FIGS. 10 to 13 and 15 to 22 ) to the processor 420 (refer to FIG. 23 ). may be assigned to each unit of (see FIG. 23 or 39 or 43 ).

For example, if the message (or signal or data) received from the mover's second application 300 (see FIGS. 10 to 13 and 15 to 22 ) relates to whether or not to accept delivery (see FIG. 10 or FIG. 10 ) 11), the mover signal receiving unit 6100 may allocate the corresponding message to the delivery manager 5000 (refer to FIG. 39 ).

For example, a message (or signal or data) provided from the second application 300 (see FIGS. 10 to 13 and 15 to 22 ) of the mover is related to the relevant information of the mover or indicates the status of delivery. If it is about confirming (see FIGS. 15-22 ), the mover signal receiving unit 6100 may assign the message to the mover processing unit 6300 .

The mover manager 6000 may include a mover signal transmission unit 6200 . For example, the mover signal transmission unit 6200 may transmit a message (or signal or data) to the second application 300 (refer to FIG. 13 ).

The mover manager 6000 may include a mover processing unit 6300 . The mover processing unit 6300 may process the request message (or signal or data) received from the second application 300 of the mover (refer to FIGS. 15 to 22 ) and transmit it to the corresponding user through the mover transmission unit 6200 . have.

44 is a flowchart illustrating a delivery processing method ( S10 ) according to an embodiment of the present invention. FIG. 44 may be described together with FIGS. 1 to 43 .

1 to 44 , the delivery processing method ( S10 ) according to an embodiment of the present invention may include a delivery processing request message reception step ( S1000 ). In this step ( S1000 ), the processor 420 may receive, for example, a processing message request regarding the order or cancellation of delivery from the first application 200 . For another example, in this Danye (S1000), the processor 420, a message about whether to accept the execution of the delivery from the second application 300 and / and a message about the management of the delivery (or data or signal) can be received.

The delivery processing method ( S10 ) according to an embodiment of the present invention may include a step ( S2000 ) of determining whether the received delivery processing request message is a delivery order request. In this step (S2000), the processor 420 may determine, for example, whether the received request message has a structure of the delivery order data form DF100.

The delivery processing method ( S10 ) according to an embodiment of the present invention may include processing the received delivery order ( S3000 ). If it is determined that the received request message has the structure of the delivery order data form DF100, the processor 420 may perform this step S3000. In this step (S3000), the processor 420 finds and matches a mover capable of performing the received delivery based on the received delivery order data form DF100, and performs matching with the mover's integrated schedule 4223 ) can be updated by adding the delivery of the delivery order data form (DF100).

The delivery processing method ( S10 ) according to an embodiment of the present invention may include a step ( S4000 ) of determining whether the received delivery processing request message is a delivery cancellation request. If it is determined that the received request message does not have a structure of the delivery order data form DF100, the processor may perform this step S4000. In this step (S4000), the processor 420 may determine, for example, whether the received request message has a structure of the delivery cancellation data form DF190.

The delivery processing method ( S10 ) according to an embodiment of the present invention may include processing the received delivery cancellation ( S5000 ). If it is determined that the received request message is the delivery cancellation data form DF190, the processor 420 may perform this step S5000. In this step ( S5000 ), the processor 420 may delete and update the schedule related to the delivery that is the target of cancellation from the integrated schedule 4223 of the mover that performs the delivery that is the target of cancellation.

The delivery processing method ( S10 ) according to an embodiment of the present invention may include a data update processing step ( S6000 ). If it is determined that the received request message is neither a delivery order request nor a cancellation request, the processor 420 may perform this step ( S6000 ).

For example, the received request message is an authentication shot regarding completion of the delivery transmitted by the second application 300 and evaluation information for the corresponding user, or evaluation of the corresponding mover transmitted by the first application 200 In the case of information, the processor 420 may perform this step (S6000). In this step ( S6000 ), the processor 420 may update data related to the received request message among data stored in the database unit 410 .

For example, the received request message may be a message requesting update of the integrated schedule 4223 transmitted by the second application 300 . In this case, the processor 420 may perform this step (S6000). This message may be a message that the second application 300 periodically transmits to the server 50 .

For example, when the integrated schedule 4223 of the one mover is the schedule shown in FIG. 38 , the schedule of the first segment DF400-1 and the second segment DF400-2 while the one mover performs the integrated schedule may be considered. The processor 420 compares the time element ITIN1100 of each segment with the time at which the update request message is received so that the current time is later than the time element ITIN1100 of the second segment DF400-2 and the third segment DF400 -3), it may be determined that scheduling of the first segment DF400-1 and the second segment DF400-2 is completed.

In this case, the processor 420 may delete the first segment DF400-1 and the second segment DF400-2 that are determined to have completed the schedule in step S6000.

The delivery processing method ( S10 ) according to an embodiment of the present invention may include a step ( S7000 ) of determining whether a reason for termination occurs. The processor 420 may perform this step S7000 when the delivery order processing step S3000 ends, the delivery cancellation processing step S5000 ends, or the data update processing step S6000 ends. In this step ( S7000 ), the processor 420 may terminate the delivery processing method ( S10 ) when it is determined that the reason for the termination of the delivery processing method ( S10 ) has occurred. In this step (S7000), if it is determined that the reason for the termination of the delivery processing method (S10) does not occur, the processor 420 may perform the delivery request message receiving step (S1000).

45 is a flowchart illustrating a delivery order processing step (S3000) according to an embodiment of the present invention. 45 may be described together with FIGS. 1 to 44 .

1 to 45 , the delivery order processing step ( S3000 ) according to an embodiment of the present invention may include a step ( S3100 ) of extracting a mover capable of performing order delivery. In this step (S3100), the processor 420 may prepare the order delivery and the integrated schedule 4223 of each mover. For example, in this step ( S3100 ), the processor 420 may determine whether the schedule of order delivery can be inserted into the integrated schedule 4223 of each mover.

The delivery order processing step ( S3000 ) according to an embodiment of the present invention may include a step ( S3200 ) of determining whether there is a mover capable of performing order delivery.

The delivery order processing step (S3000) according to an embodiment of the present invention may include transmitting an acceptance or not message to a mover capable of performing order delivery and receiving a reply message (S3300). If it is determined that there is a mover capable of performing order discovery, the processor 420 may perform this step ( S3300 ). In this step (S3300), the processor 420 may transmit a message whether to accept the order discovery to the second application 300 of the mover that can perform the order discovery.

The message returned from the mover may include information on whether to accept the order discovery, and may include information on a discount on a fee when the order discovery is performed.

The delivery order processing step ( S3000 ) according to an embodiment of the present invention may include a step ( S3400 ) of determining whether there is a mover that has accepted the order delivery execution. The processor 420 may perform this step (S3400).

The delivery order processing step ( S3000 ) according to an embodiment of the present invention may include a step ( S3500 ) of selecting a mover that performs order delivery. When it is determined that there is a mover that has accepted the order delivery (or corresponding delivery), the processor 420 may perform this step ( S3500 ). For example, the processor 420 may select one mover from among the mover(s) that have accepted the order delivery execution. The criterion for the processor 420 to select a mover to perform order discovery may be at least one of a first-come-first-served basis of a reply message, a cost discount rate of order discovery, and a grade of a mover that has accepted order discovery.

The delivery order processing step (S3000) according to an embodiment of the present invention may include updating the database unit 410 (S3600). In this step ( S3600 ), the processor 420 may update the mover data 4200 of a mover that performs order discovery. In this step (S3600), the processor 420 may update the individual delivery data 4100 of the order delivery.

The delivery order processing step ( S3000 ) according to an embodiment of the present invention may include a step ( S3700 ) of processing the inability to perform order delivery. The processor 420 may perform this step ( S3700 ) when it is determined that there is no mover capable of performing the order discovery or there is no mover that has accepted the execution of the order discovery. In this step ( S3700 ), the processor 420 may provide a message indicating that order delivery is impossible or rejected to the user.

46 is a flowchart illustrating an order delivery capable mover extraction step (S3100) according to an embodiment of the present invention. 46 may be described together with FIGS. 1 to 45 .

1 to 46 , the order delivery capable mover extraction step S3100 according to an embodiment of the present invention may include an initial setting step S3110 of the temporary variable j. The temporary variable (j, dummy variable) may be a variable for individually distinguishing a plurality of movers. For example, “j-th mover” may mean “j-th mover” when a plurality of movers are sequentially disposed. The plurality of movers may be “n”. The processor 420 may perform this step ( S3110 ).

The step of extracting the mover capable of performing order discovery according to an embodiment of the present invention ( S3100 ) may include the step of determining whether the j-th mover can perform order discovery ( S3120 ). The processor 420 may perform this step (S3120). This step ( S3120 ) may be referred to as a “determining whether the order delivery of each mover can be performed”.

According to an embodiment of the present invention, the step of extracting the mover capable of performing order delivery ( S3100 ) may include the step of writing the j-th mover in the list of movers capable of performing the delivery of an order ( S3130 ). When it is determined that the j-th mover can perform order delivery, the processor 420 may perform this step ( S3130 ). This step ( S3130 ) may be referred to as “a step of writing a corresponding mover in a list of movers capable of performing order delivery”.

The step of extracting a mover capable of performing order delivery according to an embodiment of the present invention (S3100) may include a step of changing an arbitrary variable (S3140). The processor 420 may perform this step ( S3140 ) after the j-th mover is listed in the order delivery capable mover list. Alternatively, if it is determined that the j-th mover cannot perform order delivery, the processor 420 may perform this step ( S3140 ) without writing in the list.

The step (S3100) of extracting an order delivery capable mover according to an embodiment of the present invention may include a step (S3150) of determining whether a reason for termination occurs. The processor 420 may perform this step ( S3150 ) after the step ( S3140 ) of changing the random variable. If it is determined that the reason for the termination has occurred, the processor 420 may terminate the order discovery execution possible mover extraction step ( S3100 ). When it is determined that the reason for termination has not occurred, the processor 420 may perform an operation S3120 of determining whether the j-th mover can perform order delivery. In this step (S3150), the "reason for termination" may be, for example, a case in which it is determined whether order delivery can be performed for all movers (S3120), and in this case, the random variable j is It may be "n+1".

47 is a flowchart illustrating a determination step ( S3120 ) of whether order delivery of each mover can be performed according to an embodiment of the present invention. 47 may be described together with FIGS. 1 to 46 .

1 to 47 , the step of determining whether order delivery of each mover can be performed according to an embodiment of the present invention (S3120) is a step of forming an individual delivery data form (DF300) of order delivery ( S3121) may be included. The processor 420 may perform this step ( S3121 ). For example, the individual delivery processing unit 5100 may perform this step ( S3121 ).

The step (S3120) of determining whether each mover can perform order delivery according to an embodiment of the present invention is a step (S3122) of extracting the combined schedule 4223 of the j-th mover to form an integrated delivery data form (DF400) (S3122). ) may be included. The integrated delivery processing unit 5200 may perform this step ( S3122 ). This step ( S3122 ) may be referred to as “a step of extracting the integrated schedule of each mover and forming an integrated delivery data form”. In this step (S3122), the integrated delivery data form DF400 may be the j-th mover's integrated schedule 4223.

The step (S3120) of determining whether the order delivery of each mover can be performed according to an embodiment of the present invention includes a step (S3123) of merging the individual delivery data form (DF300) into the integrated delivery data form (DF400) (S3123) can do. In this step ( S3123 ), the integrated delivery processing unit 5200 may merge (or insert) the individual delivery data forms DF300 into the combined delivery data forms DF400 of each mover.

This step S3123 can be particularly well explained through the embodiment shown in FIGS. 34 to 38 . In this step ( S3123 ), the unified delivery processing unit 5200 sorts the segments of the merged unified delivery data form DF400 into visual elements ITIN1100 , and between adjacent line segments and the corresponding segments. The optimal route of and each element (ITIN1100, ITIN1200, ITIN1300, ITIN1400, ITIN1500) of each segment can be modified.

The step (S3120) of determining whether each mover can perform order delivery according to an embodiment of the present invention may include a step (S3124) of determining whether each segment of the merged integrated delivery data form (DF400) is possible. can For example, the mover possibility check module 5240 may perform this step (S3124).

In this step (S3124), the mover possibility check module 5240 may compare the elapsed time and the required time of the corresponding segment. The elapsed time of the corresponding segment may mean a difference between the time of the visual element ITIN1100 of the corresponding segment and the time of the visual element ITIN1100 of the line segment. The required time of the corresponding segment may mean the time of the required time element ITIN1300 of the corresponding segment.

In this step (S3124), the mover possibility check module 5240 may determine the corresponding segment as an executable segment when the elapsed time of the corresponding segment is greater than or equal to the required time. In this step ( S3124 ), the mover possibility check module 5240 may determine the corresponding segment as an impossible segment when the elapsed time of the corresponding segment is less than the required time.

In this step (S3124), if the mover possibility check module 5240 determines that "the schedule of each segment of the merged integrated delivery data form (DF400) is possible", the processor 420 performs order delivery mover list A step (S3130) of describing the corresponding mover may be performed. In this step (S3124), if the mover possibility check module 5240 determines that "the schedule of each segment of the merged integrated delivery data form (DF400) is not possible", the processor 420 performs a random variable change step (S3140). ) can be done.

48 is a flowchart illustrating a step (S3123) of merging individual delivery data forms into an integrated delivery data form according to an embodiment of the present invention. FIG. 48 may be described together with FIGS. 1 to 47 .

1 to 48 , the step of merging the integrated delivery data form ( S3123 ) according to an embodiment of the present invention may include the step of classifying the segment ( S31231 ). In this step ( S31231 ), the unified delivery processing unit 5200 may classify segments of the merged unified delivery data form DF400 based on the visual element ITIN1100 .

The step of merging the integrated delivery data form ( S3123 ) according to an embodiment of the present invention may include a step of concatenating segments ( S31232 ). The segment connection module 5250, in this step (S31232), derives an optimal route between the place elements ITIN1200 of both adjacent segments, derives a route of public transportation on the derived optimal route, and derives A new segment with the place element (ITIN1200) at both ends of a public transportation route can be inserted between a line segment and the corresponding segment (between both adjacent segments). However, among both ends of the derived public transportation route, an end overlapping with the place element (ITIN1200) of the line segment or the place element (ITIN1200) of the next segment may be excluded.

The step (S3123) of merging the integrated delivery data form according to an embodiment of the present invention may include updating each segment (S31233). In this step (S31233), the integrated delivery processing unit 5200 may update or update each element (ITIN1100, ITIN1200, ITIN1300, ITIN1400, ITIN1500) of each segment.

49 is a flowchart illustrating the possibility of determining whether each segment of the integrated delivery data form is possible ( S3124 ) according to an embodiment of the present invention. 49 may be described in conjunction with FIGS. 1 to 48 .

1 to 49 , the determining whether each segment of the integrated delivery data form DF400 according to an embodiment of the present invention is possible (S3124) is a step of extracting the elapsed time of each segment (S31241) ) may be included. In this step ( S31241 ), the mover possibility check module 5240 may calculate and extract the difference between the time of the visual element ITIN1100 of the corresponding segment and the time of the visual element ITIN1100 of the line segment. Here, the corresponding segment may be referred to as an "inspection target segment" to be inspected, and the line segment may be referred to as a "line inspection target segment".

The step (S3124) of determining whether each segment of the integrated delivery data form (DF400) according to an embodiment of the present invention is possible may include a step (S31242) of determining the magnitude of the elapsed time and the required time of each segment. can The mover possibility check module 5240 may perform this step ( S31242 ). If the elapsed time in one segment is less than the required time, the random variable change step S3140 may be performed. If the elapsed time in each segment is equal to or longer than the required time, the step of writing the corresponding mover in the list of movers capable of performing order delivery ( S3130 ) may proceed.

FIG. 50 is a diagram illustrating a state in which a touch input is applied to the second delivery progress confirmation button in the delivery status interface shown in FIG. 6 .

Referring to FIG. 50 , when a touch is applied to the second delivery progress confirmation button 222 (see FIG. 6 ), the first application 200 provides an interface related to the second delivery progress status to the touch screen 110 . can do.

The second delivery progress information 2221 may be displayed on the touch screen 110 . The second delivery progress status information 2221 is a 'ready state' that is the current stage of the second delivery, information about loading and unloading of the second delivery, and information about the goods of the second delivery. can

A second delivery cancel button 2222 may be displayed on the touch screen 110 . When a touch is applied to the second delivery cancel button 2222, the first application 200 provides a message (or signal, or data) requesting cancellation of the second delivery to the app server 400 (see FIG. 23). can do.

When the app server 400 (refer to FIG. 23) receives a message requesting cancellation of the second delivery, the processor 420 (refer to FIG. 23) refers to the ID of the second delivery and an integrated schedule of the corresponding mover (4223, Figure 23). 25), the schedule related to the second delivery may be deleted.

1 to 50 , the delivery network system 10 according to the present invention may relate to a platform that connects a user who requests and uses delivery and a mover who performs delivery. In this platform 10 , the user may use the first application 200 to use the discovery, and the mover may perform the discovery using the second application 300 . The platform 10 connects a user and a mover, and the user may be a mover and the mover may be a user.

The platform 10 is premised on the use of public transportation. The public transportation may be at least one of a metro, a city bus, a light rail, a high-speed rail, a general rail, an express bus, and a wide-area bus.

A mover may be professionally delivered, or he may be using his commute to do a small amount of deliveries per day. For example, during work hours, goods may be loaded near home and goods may be unloaded near a work place (eg, a company). For example, during rush hour, you can load goods near your workplace and unload goods near your home. In such an example, the mover can effectively use time by making the time required for commuting to and from work overlap with the time required for delivery.

The platform 10 may search for a mover capable of performing the ordered delivery and inquire of the available mover whether to perform the ordered delivery. In this way, an accident in which the physically inoperable mover is responsible for order delivery can be prevented.

The schedule of the mover performing the delivery may be integratedly managed. The route according to the schedule of the mover may mean that the location of the location element ITIN1200 of each segment ITIN1000 is connected in time series. Here, the time series may be set based on the time element ITIN1100 of the segment ITIN1000. The segment ITIN1000 may be understood as a node. When a node is added to the schedule ITIN100, an optimal path may be re-established with respect to the added node. When a node is deleted from the schedule ITIN100, an optimal path may be re-established by the deleted node. In re-establishing an optimal path, when a new node is needed or an existing node needs to be omitted, a segment for the node may be added or omitted. The new node may be the end of the route of public transport on the updated optimal route.

It is apparent to those skilled in the art that the present invention may be embodied in other specific forms without departing from the spirit and essential characteristics of the present invention.

Any or other embodiments of the invention described above are not mutually exclusive or distinct. Certain or other embodiments of the present invention described above may be combined or combined in their respective configurations or functions.

The above detailed description should not be construed as restrictive in all respects and should be considered as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention.

10: delivery network system 50: server
60; first terminal 70: second terminal
100: mobile terminal 200: first application
300: second application 400: delivery app server

Claims (26)

a communication unit for transmitting and receiving signals to and from a first application providing a delivery consumption interface and a second application providing a delivery execution interface;
a database unit for storing data; and
A processor for transmitting and receiving signals to and from the communication unit and the database unit,
The processor is
Upon receiving the delivery order request message from the first application through the communication unit, extracting a mover capable of performing the ordered delivery based on the mover data stored in the database unit,
If there is a mover capable of performing the ordered delivery, sending a message whether to accept the execution of the ordered delivery to a second application of the mover capable of performing the ordered delivery through the communication unit,
If there is an acceptance message returned from the mover receiving the execution acceptance message, selecting a mover that performs the ordered delivery from among the accepted movers,
delivery app-server. According to claim 1,
The processor is
When receiving a delivery cancellation request message from the first application through the communication unit,
Extracting an integrated schedule of a mover performing the cancellation requested delivery from the mover data, deleting the schedule related to the cancellation requested delivery from the extracted integrated schedule, and storing the updated integrated schedule in the database unit ,
Delivery App Server. According to claim 1,
The processor is
If it is determined that there is no mover capable of performing the ordered delivery or there is no acceptance message received from the mover capable of performing the ordered delivery,
Transmitting, through the communication unit, an order rejection message indicating that the order of the delivery is rejected to the first application that has requested the delivery of the order,
Delivery App Server. According to claim 1,
The mover data is
Mover Personal Factor with respect to Il Mover's personal information; and
Containing a delivery schedule factor including information about the ID of the delivery to be performed by the work mover,
Delivery App Server. 5. The method of claim 4,
The mover personal factor is,
a mover ID element that is an ID of the one mover; and
comprising a mover rating element including information about the rating of the one mover,
Delivery App Server. 5. The method of claim 4,
The delivery schedule factor is,
a delivery list including information on delivery to be performed by the work mover; and
Including an integrated schedule in which the delivery to be performed by the work mover is an integrated schedule,
Delivery App Server. 7. The method of claim 6,
The integrated schedule is
comprising a plurality of segments arranged in time series,
One segment of the plurality of segments,
a visual element relating to the time at which the segment is performed;
a place element relating to a place where the segment is performed;
an action code element relating to an action to be performed by the work mover in the one segment; and
It relates to the ID of the delivery to which the segment belongs, including a delivery ID element,
Delivery App Server. 8. The method of claim 7,
The one segment is
a time required for moving from the location element of the line segment immediately preceding the one segment to the location element of the one segment;
If the one segment is the best segment, the duration element of the one segment is set to "NULL",
Delivery App Server. 9. The method of claim 8,
The delivery order request message is,
User ID data relating to the ID of the user who ordered the delivery through the first application;
loading time data, relating to a time at which the ordered item subject to delivery is loaded;
loading location data relating to the location where the article is loaded;
unloading time data relating to the time at which the article is unloaded;
unloading location data relating to the location where the article is unloaded; and
comprising article data relating to the article;
Delivery App Server. 10. The method of claim 9,
The processor is
Process the delivery order request message to form an individual delivery data form,
The individual delivery data form includes a loading segment, a loading station segment, an unloading station segment, and an unloading segment arranged in time series and having the same elements as the structure of the one segment,
Delivery App Server. 11. The method of claim 10,
The loading segment is formed based on the loading time data and the loading location data,
The unloading segment is formed based on the unloading time data and the unloading location data,
The processor is
Searching for an optimal route to move from the location of the loading location data to the location of the unloading location data, and setting the locations at both ends of the section where public transportation is involved among the optimal routes with the loading station location element, respectively set with the unloading station place element,
the loading station location element belongs to the loading station segment;
the unloading station location element belongs to the unloading station segment;
The optimal path is a path sequentially moving to the location of the loading location data, the loading station location element, the unloading station location element, and the location of the unloading location data.
Delivery App Server. 12. The method of claim 11,
The processor is
Extract the integrated schedule of the work mover and set it as an integrated delivery data form,
Merging the segment of the individual delivery data form and the segment of the integrated delivery data form to set the combined delivery data,
It is determined whether each segment of the merged unified delivery data form is executable, and if all segments of the merged unified delivery data form are executable, the one mover is used as a mover capable of performing the ordered delivery. classify, and if one or more of the segments of the merged unified delivery dataform are not performable, delete the unified delivery dataform and determine whether the ordered delivery can be performed for another mover to judge,
Delivery App Server. 13. The method of claim 12,
The processor is
In determining whether it is possible to perform an inspection target segment that is an inspection target among each segment of the merged integrated delivery data form,
setting the difference between the visual element of the segment to be inspected and the visual element of the segment to be inspected immediately preceding the segment to be inspected as the elapsed time;
setting the time required to move from the location element of the segment to be inspected immediately preceding the segment to be inspected to the place element of the segment to be inspected as the required time element of the segment to be inspected;
If the elapsed time for each segment of the merged integrated delivery data form is greater than or equal to the time of the required time element, classifying the work mover as a mover capable of performing the ordered delivery,
Delivery App Server. 13. The method of claim 12,
In the process of the processor merging the segment of the individual delivery data form and the segment of the unified delivery data form to set the unified delivery data form,
The processor is
Classifying each segment of the merged integrated delivery data form into a time series based on the visual element of each segment,
A new segment is inserted between the two segments by deriving an optimal route between the place elements of both adjacent segments and deriving a public transport route on the derived optimal route, and using both ends of the public transport route as a place element doing,
Delivery App Server. 15. The method of claim 14,
In the process of the processor merging the segment of the individual delivery data form and the segment of the unified delivery data form to set the unified delivery data form,
The processor is
Among the both ends of the derived public transportation route, a new segment having an end not overlapping with the place element of both segments as a place element is inserted into the both segments, and an end overlapping with the place element of both segments is selected Do not insert a new segment that is a place element,
Delivery App Server. 16. The method of claim 15,
The processor is
When receiving a message requesting update of the integrated schedule from the second application through the communication unit,
Comparing the time at which the message requesting the update of the integrated schedule is received and the time element of the segment of the integrated schedule, extracting the scheduled segment, and deleting the scheduled segment,
Delivery App Server. According to claim 1,
The delivery consumption interface,
a delivery order interface for composing the delivery order request message;
Delivery App Server. A communication unit for transmitting and receiving a signal (signal) and a second application that provides a delivery execution interface; a database unit for storing data; And a first communication unit for communicating with the delivery app server comprising a processor for transmitting and receiving a signal to and from the communication unit and the database unit;
a touch screen displaying an image; and
a first application that provides a delivery consumption interface to the touch screen;
The delivery consumption interface,
delivery order button;
Check delivery status button; and
Containing a touch screen indicating the status information of the delivery in progress,
mobile terminal. 19. The method of claim 18,
The first application is
When obtaining a touch input applied to the touch screen at the position of the delivery order button, displaying a delivery order interface related to an order of a new delivery on the touch screen,
mobile terminal. 20. The method of claim 19,
The delivery order interface,
a loading factor, relating to the input of the loading time and location of the article to be retrieved;
an unloading factor, relating to the input of time and place to the unloading of the article;
an article factor relating to the input of information about the article; and
For transmitting the information described in each factor to the delivery app server, including a delivery order transmission button,
mobile terminal. 21. The method of claim 20,
The delivery order interface,
comprising a mover selection element relating to the input of characteristics of the mover to perform the dereaver;
mobile terminal. 21. The method of claim 20,
The first application is
When a touch input applied to the touch screen is obtained at the position of the delivery order transmission button, the information described in each factor is transmitted to the delivery app server through the first communication unit,
mobile terminal. 23. The method of claim 22,
The first application is
When a delivery reception message is received from the delivery app server through the first communication unit when a mover to perform the delivery is selected, the delivery reception message is displayed on the touch screen,
When a delivery order rejection message is received from the delivery app server through the first communication unit when a mover to perform the delivery is not selected, the delivery order rejection message is displayed on the touch screen,
mobile terminal. a communication unit for transmitting and receiving a signal to and from a first application providing a delivery consumption interface; a database unit for storing data; And a second communication unit communicating with the delivery app server comprising a processor for transmitting and receiving a signal to and from the communication unit and the database unit;
a touch screen displaying an image; and
A second application that provides a delivery performance interface to the touch screen,
The delivery execution interface is,
When receiving an inquiry message about performing delivery from the delivery app server through the second communication unit, displaying a delivery reception interface on the touch screen,
mobile terminal. 25. The method of claim 24,
The delivery reception interface is,
a map on which the route of the delivery is displayed;
information about the delivery;
an accept button, relating to accepting the execution of the delivery; and
Regarding refusal to perform the delivery, including a reject button,
mobile terminal. 26. The method of claim 25,
The second application is
When a touch input applied to the touch screen is obtained at the position of the accept button, an acceptance message is transmitted to the delivery app server,
When a touch input applied to the touch screen is obtained at the position of the reject button, an acceptance message is transmitted to the delivery app server,
mobile terminal.

Images