JP2003085382A - System, server, method and user information distribution device for adjusting timing of providing service - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a service timing adjustment system for timely providing a service to a user. SOLUTION: When the user passes a ticket barrier 71 of a station, a record of passing is sent from a passage information distribution device 70 and stored in a notification service server 40, and a record of the user reaching home is stored in the notification service server 40 also. When an order for a service is sent by using a user terminal 20, it reaches a delivery service server 60 of a delivery company via the notification service sever 40. Thereafter, when the user passes the ticket barrier 71 of the station, the time the user reaches home is calculated on the basis of the records stored by the notification service server 40, and timing of the service can be adjusted.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a service providing system and the like which acquires user information via a network and adjusts the timing of providing a service to the user.

[0002]

2. Description of the Related Art Conventionally, in providing various services to users, efficient service providing methods have been studied. For example, when a service person provides a service such as delivery, repair, and sales, the service person who is closest to the user heads for the service to shorten the waiting time until the user receives the service. ing. As a specific method, the service person in charge informs the service provider of his / her location information. Based on this, the service providing company checks the position of the service person and the position of the user and gives an instruction to provide the service to the service person closest to the user.

The problem here is the position of the user who receives the service. In many cases, the user who has applied for the service needs to be present at the service providing place at the service providing place. Therefore, the user has to apply for the service in consideration of his own convenience and the time when the service person arrives. After applying for the service, the user has to act with the scheduled service provision time in mind, which is very inconvenient because the user is restricted in the action.

Therefore, the service providing time is flexibly set according to the user's request.
As a specific example, in the meal delivery service, the user informs the service providing company of the time when he / she wants to have a meal, and receives the meal delivery at that time.

[0005]

However, when a meal is to be delivered, preparations such as dishes are required. Therefore, it is necessary to apply for the service in advance, for example, 30 minutes before the scheduled service provision time. . In this case, for example, even if the user applies for the service to deliver the meal immediately after returning home, the service is actually available only 30 minutes after the application. Although it is possible to apply for the return time in advance, it is difficult to apply for the service from the train, etc. on the way home, and the user has to pay attention to the time when applying for the service. It is very troublesome. Furthermore, if you forget to apply for the service, you will miss the service. On the other hand, it is possible to apply for delivery at night in the morning of that day, but since it becomes necessary to specify the time of delivery, the time for returning home is also limited. Furthermore, if the scheduled return time changes after applying for the service, it is necessary to notify the service provider of the change in the delivery time, which is also time-consuming. Under such a background, when a user is provided with a service, there is a demand for a method of providing the service in a timely and efficient manner without being bound by the delivery time of the user.

The present invention has been made based on the above technical problems, and a main object of the present invention is to provide a service system capable of servicing a user at an optimum timing.

[0007]

Based on the above object, the timing adjusting system of the present invention is a timing adjusting system for adjusting the timing of providing a predetermined service to a user, and the user can set a predetermined position information. Recording means for recording a tracking record including user position recognition means for recognizing arrival at the providing point, time data recognized by the user position recognizing means, position data for the position information providing point, and user identification data And an application acceptance means for accepting a service application by a user who receives a prescribed service at a prescribed service providing point, the application is accepted by the application acceptance means, and the user has reached the position information providing point by the user position recognizing means. Is recognized, the past tracking record recorded in the recording means is deleted. By calculating the time required for the service provision point from the positional information providing site you are, it is characterized in that a obtaining means for obtaining the timing for providing services for a user.

As described above, when the user reaches the position information providing point, it is possible to predict that the user will reach the service providing point by the tracking record, so that the service can be provided to the user in a timely manner. In addition,
The recognition of the user and the acceptance of the service provision application can be performed through the network or directly. As a specific method for acquiring the service timing, the acquisition unit calculates the timing by calculating the required time from the position information providing point to the service providing point using the past tracking record recorded in the recording unit. Can be obtained.

The user position and time data recognized by the user position recognizing means is, for example, push type data sent from the position information providing point when the user passes through the fixed position information providing point. Or
The user position and time data may be pull-type data transmitted from the mobile communication terminal by requesting the mobile communication terminal owned by the user.

The present invention can also be regarded as a service providing system. This service providing system provides a passage information distribution device that delivers position information of a user via a network, and a timing of acquiring a user's position information from the passage information distribution device via a network and providing a predetermined service to the user. And a timing adjustment server for adjusting, wherein the passage information distribution device recognizes that the user has reached the position providing point, and sends the point arrival recognition information of the user generated by the recognition to the timing adjustment server. Then, the timing adjustment server recognizes the order of the predetermined service from the user, receives the point arrival recognition information transmitted from the passage information distribution device, and the estimated arrival time at which the user arrives at the service provision point from the point arrival recognition information. Calculate and obtain the timing to provide the service from the scheduled arrival time. It is an butterfly.

In this case, the service providing system further includes a service providing server of a service provider that provides the service, and the service providing server causes the timing adjustment server to receive the order of the predetermined service from the user and notify the timing. The timing adjustment server may send the timing to the provider server in response to the notification request from the service providing server.

The present invention can also be regarded as a timing adjustment server. This timing adjustment server
Predetermined point data indicating a predetermined position providing point by the storage means, and service providing point data indicating a point providing a predetermined service to the user, for adjusting timing for providing a predetermined service to the user. Data on the time required from the position providing point to the service providing point and a user record containing the same are accumulated, the order recognition means recognizes the order of a predetermined service by the user, and the passage information acceptance means recognizes the order, and then the specific position. In the user record extracted by the arrival time calculation means, the user passage information is received, the user record whose position providing point is within a predetermined range from the specific position is extracted from the user records accumulated by the accumulation means by the extraction means. Based on the estimated time of arrival of the user at the service provision point based on It is characterized in that to indicate the timing to provide a service based on the expected arrival time by the stage.

Here, the user record can be calculated from a tracking record generated when the user reaches the position providing point fixedly installed. The user record can also be calculated from a tracking record obtained by requesting the mobile communication terminal owned by the user. The timing adjustment server may include a user permission information storage unit that records a position acquisition method permitted by the user to acquire the position information of the user. In addition, when the order recognition unit recognizes an order sent from the user terminal of the user, a relay processing unit that relays and connects the user terminal to a service providing server that provides a predetermined service may be further provided. .

Further, the timing adjustment server of the present invention is
In order to adjust the timing for providing a predetermined service to the user, the acquisition unit acquires a tracking record indicating the position of the user and the time when the user was at that position, and the storage unit acquires the tracking record. Is recorded in the tracking record storage unit and a new new tracking record is acquired for the user, it is determined by the tracking record determination means whether or not the past tracking records acquired in the past stored in the tracking record storage unit are stored. Then, based on the past tracking record and the new tracking record, the required time calculation means calculates the required time from the data acquisition point of the past tracking record to the data acquisition point of the new tracking record, and the required time determination means calculates it. The required time is appropriate as the data used to calculate the timing of providing a predetermined service. Determining whether or not such,
When it is determined that the required time is appropriate data, the required time is recorded as the accumulated record in the accumulated record accumulating section by the recording means, and when the user requests the provision of the predetermined service by the timing calculating means, the tracking record newly acquired. And the accumulated record, the timing is calculated.

The present invention can also be regarded as a user information distribution device. This user information distribution device recognizes and records the position of the user in order to adjust the timing for providing the predetermined service to the user, and whether or not the user is registered as a person who receives the predetermined service. The storage unit that has registered the user registration information indicating that, the recognition unit that recognizes the presence of the user at the predetermined position providing point, the determination processing unit that determines whether or not the user is registered in the storage unit, and the user When it is determined that the user is registered, the time recording unit that records the time when the user existed, and the position time data output unit that outputs the existence time together with the data indicating the position providing point to the outside via the network were provided. It is characterized by. In this case, when it is determined that the user recognized by the recognition unit is not registered as a user, it is possible to prohibit recording the time when the user is recognized in the time recording unit.

Further, the present invention can be understood as a timing adjusting method. This timing adjusting method is a method of adjusting the timing for providing a predetermined service to a user via a network, and a step of recognizing that the user has reached a position information providing point and a user providing the position information. Acquiring a tracking record including time data indicating the time when the point of arrival is recognized, position data indicating the position of the position information providing point, and user identification data of the user; and a predetermined service at a predetermined service providing point. The step of accepting the service application by the user who receives the information and the recognition that the user has reached the location information providing point calculates the time required from the location information providing point to the service providing point based on the tracking record acquired in the past. To acquire the timing to provide the service to the user. Tsu and up, and is characterized in that it has a.

Further, the timing adjusting method of the present invention is a method for the service provider to adjust the timing of providing a predetermined service to the user, and accepts registration and identification of the user who receives the predetermined service. The step of accumulating data about the user including data and position data in the database, and calculating the time required from the position providing point that detects the user's position to the service providing point where the user provides a predetermined service A step of accumulating in a database, a step of receiving from the service providing system a timing notification request for notifying the service providing system of the service provider of the timing of providing the service, and a step of recognizing that the user is located at the position providing point, For users located at the location providing point The user arrives at the service providing point from the step of determining whether there is a timing notification request and the position recognition time and the required time when the user recognizes that the user is located at the position providing point when it is determined that there is a timing notification request. And a step of calculating a planned required time until it is performed.

In this case, the step of determining whether or not the desired notification setting time designated by the timing notification request is less than or equal to the planned required time, and the service provision if the notification desired setting time is determined to be less than or equal to the planned required time. Informing the system that it is time to do so.

Further, in this case, the step of calculating and accumulating the required time accumulates a plurality of tracking records obtained by tracking the behavior of the user, and from the tracking records,
The step of calculating the average required time from the position providing point to the service providing point and calculating the planned required time includes the estimated arrival time at which the user arrives at the service providing point when the user reaches the position providing point. The timing for providing a predetermined service to the user can be set according to the calculated estimated arrival time.

[0020]

BEST MODE FOR CARRYING OUT THE INVENTION The present invention will be described below in detail based on the embodiments shown in the accompanying drawings. FIG. 1 is a diagram illustrating a delivery service system 10 according to the present embodiment. In the delivery service system (system for adjusting the timing of providing a service) 10 shown in FIG. 1, a user terminal 20 used when a user places an order for a delivery service, and portable communication for transmitting user's position information. Used by a terminal (hereinafter referred to as a mobile terminal) 30, a notification service server (timing adjustment server) 40 for calculating an appropriate time for providing a delivery service to a user and notifying the delivery service provider, A delivery service server 60 and a passage information delivery device 70 that delivers the user's position information to the notification service server 40 are provided, and are connected via a network such as the Internet. The user terminal 20 and the mobile terminal 3
0, notification service server 40, delivery service server 6
0, the connection to the network in each of the passage information distribution devices 70 may be either wired or wireless. Further, the user terminal 20 and the mobile terminal 30 may be one terminal.

FIG. 2 is a diagram showing the configuration of the user terminal 20 shown in FIG. The user terminal 20 is a terminal used by a user who receives the delivery service, for example, P
C (Personal Computer). The user terminal 20 registers user information in the order / order processing unit 21 that orders a delivery service and the notification service server 40 as a function realized by a calculation unit such as a CPU through a predetermined program such as a browser. The registration processing unit 22 is provided. Further, the user terminal 20 includes an input unit 23 that receives an input from the user, a display unit 24 that displays output data, and a communication unit 25 that transmits / receives data to / from the outside via a network.

FIG. 3 is a diagram showing the configuration of the mobile terminal 30 shown in FIG. The mobile terminal 30 sends the location information of the user to the GPS (Gl
This is a terminal such as a mobile phone having a function of notifying by obal Positioning Systems). The mobile terminal 30 detects a position data request receiving unit 31 that receives a position data request from the notification service server 40, a radio wave receiving unit 32 that receives a radio wave from a satellite, and detects the current position of the mobile terminal 30 from the received radio wave. A position detection unit 33 and a position data transmission unit 34 that sends the detected position data to the notification service server 40 are provided. If the mobile terminal 30 and the user terminal 20 have both functions as described above, they may be realized as one device.

FIG. 4 is a diagram showing the configuration of the notification service server 40 shown in FIG. Notification service server 40
Is a server that functions to notify the delivery service provider of the service timing, and includes a user registration information processing unit 41 that registers user information and a user position information processing unit (position information processing) that processes user position information. Part) 42
And an order relay unit (application recognition unit) 43 for relaying and transmitting the order of the delivery service ordered by the user to the delivery service provider, and a notification request processing unit for processing a user position notification request from the delivery service provider (timing Calculation unit) 44
And, and the respective functions are realized by an arithmetic unit such as a CPU based on a predetermined program. Further, the notification service server 40 includes a user database (hereinafter, database is abbreviated as DB) 50, a position information provider DB 54,
The delivery service provider information DB 55 and the notification request DB 56 are provided. The user DB 50 includes a user registration information storage unit (user permission information storage unit) 51, a user position information storage unit 52, and a user security information storage unit 53.

FIG. 5 is a diagram showing the configuration of the delivery service server 60 shown in FIG. Delivery service server 60
Is a terminal, for example, a computer device used by a delivery service provider who provides a delivery service to a user. The delivery service server 60 executes C based on a predetermined program.
As a function implemented by a computing unit such as a PU, a relay connection request processing unit 61 that processes a relay connection request from the notification service server 40, an order acceptance unit 62 that receives an order for a delivery service, and a notification service server 40 are provided. Notification request processing unit 63 for making a user position notification request and a notification processing unit 64 for processing a notification sent from the notification service server 40.
And are equipped with. Furthermore, the delivery service server 60
Input unit 65 that receives input from the delivery service company
An output unit 66 that outputs data using a display unit, a voice unit, and the like, a communication unit 67 that transmits and receives data via a network, and a service DB 68 that registers available services.

FIG. 6 is a passage information distribution device 7 shown in FIG.
It is a figure showing the composition of 0. The passage information distribution device 70 is
In the present invention, as shown in FIG. 1, it is connected to a ticket gate (recognition unit) 71 of a station and receives a user information registration unit 72 for registering user information and information that a person has passed through the ticket gate 71. Passage information receiving unit (recognition unit) 73, a user determination unit (determination processing unit) 74 that determines whether the person who passed is a user, and a passage information registration unit (existence time recording unit) 75 that registers the passage information of the user. A passage information distribution unit (position time data output unit) 76 that distributes the passage information of the registered user to the notification service server 40, a communication processing unit 77 that transmits and receives data via the network,
Is equipped with.

FIG. 7 is a diagram for explaining an example of a service received by the user in the delivery service system 10 shown in FIG. As shown in FIG. 7, for example, the user 2 who has registered as a member in the delivery service system 10 uses the user terminal 20 at an appropriate time (for example, 13:10) and returns to the “chicken” for “dinner” on the day after returning home. To order. Then, the order is sent to the delivery service server 60 of the delivery service provider via the notification service server 40. The delivery service server 60, which has received the order, requests the notification service server 40 to notify the user position. In response to this, the notification service server 40 extracts the position and time data of the user 2 acquired from the passage information distribution device 70 or the like.
For example, in FIG. 7, this data is data indicating that the position of the user is abc station and the time is 18:30 when the user 2 passes through the ticket gate 71 of the abc station. In addition, the notification service server 40 similarly acquires the data indicating the position of the user 2 transmitted from the mobile terminal 30 owned by the user 2.

The notification service server 40 acquires the timing for providing the service from the data of the user 2 thus acquired. Then, when the timing for providing the service comes, a notification to that effect is sent to the delivery service server 60, and the delivery service provider provides the user 2 with the delivery service. As a result, User 2 returns home (for example, 18:50).
Immediately after (for example, 18:55) you will receive dinner delivery. As described above, in the delivery service system 10, the user 2 can receive the delivery service at the timing when the user 2 returns home even if the user 2 does not specify the time. Hereinafter, a specific process for realizing such a delivery service system 10 will be described.

First, the main terms used here will be explained. -Destination point means a service providing point where the user 2 receives a delivery service. In the case of providing the delivery service shown in FIG. 7, the destination is the home of the user 2. -Position providing point This is the position at which the user 2 is recognized to exist. In the case of providing the delivery service shown in FIG. 7, the abc station is the location providing point. Further, when the data when the user 2 arrives at the home is recorded as the tracking record, the home is the position providing point. If the position information is transmitted from the mobile terminal 30 owned by the user 2, the mobile terminal 3
0 is the point of user 2 recognized. Tracking record This is data indicating the position and time of the user 2 acquired at the position providing point. For example, in the case of the delivery service provision shown in FIG. 7, the data means that the user 2 was at abc station as a location providing point at 18:30 (hereinafter referred to as location providing time). The storage record includes position data indicating the position providing point, position data of the destination point, and time data indicating the time required to reach from the position providing point to the destination point. The accumulated record is referred to when calculating the timing of providing a service from the tracking record, and can be calculated from a plurality of tracking records. For example, in the case of providing the delivery service shown in FIG. 7, it is data indicating that it takes 20 minutes from the location providing point abc station to the destination point home.

FIG. 8 is a diagram for explaining the processing flow of the user terminal 20. First, the user terminal 20 includes the communication unit 25.
Then, it connects to the notification service server 40 via the network and makes a logon request to the notification service server 40 (step S201). Then, it is determined whether or not the user can log on to the notification service server 40 (step S203). If the user 2 cannot log on, it is determined whether the user 2 is already registered as a member who can receive the service of the delivery service system 10 (step S204). If it is determined that the user is not registered, the notification service server 40 A member registration request is made to (step S206).

FIG. 9A shows data recorded in the user registration information storage unit 51 of the notification service server 40 by the user 2's member registration. In the member registration in step S206, the personal information of the user 2 as shown in FIG.
That is, the name, address, telephone number, etc. of the notification service server 4
Register to 0. In addition, the data indicating the location such as address is ID
9 is recorded in the user registration information accumulating section 51 as the point information to which the is added. Further, the tracking record of the user 2 can be acquired by various methods. Therefore, the user 2 registers the reference permission data as shown in FIG. 9C in the notification service server 40 as a concrete acquisition means of the tracking record. For example, user 2 is ab
Although the station c is used, as shown in FIG. 9C, the user 2 has registered that the acquisition of the tracking record is permitted at the station abc as the position providing point. Further, the user 2 permits acquisition of the tracking record by the xy mobile phone company of the mobile terminal 30 owned by the user 2.

In addition, as information to be registered in the notification service server 40 by the user 2 in step S206, auxiliary records as shown in FIG. 10 are also registered. The auxiliary record is an approximate time that the user 2 knows from the position providing point of the tracking record to the destination point where the user 2 receives the service. In general, the user 2 often knows the time it takes to reach his / her home from the abc station that he / she normally uses, and registers that time as auxiliary data. Note that the registration of this auxiliary record is optional, but for example, when the user 2 receives the delivery service immediately after the member registration, it is necessary for the notification service server 40 to adjust the delivery service providing time (timing). It is preferable to register the auxiliary record in advance because the trace record that is No. does not exist and the accumulated record cannot be used. However, the auxiliary record may be calculated by the notification service server 40 from the distance between the destination point and the position providing point, the walking speed of a normal person, and the like.

Next, the user terminal 20 makes a step S203.
When the user logs on in the process of (1), the registered user 2's user registration information sent from the notification service server 40 is received, and the user registration information is displayed on the display unit 24 of the user terminal 20 (step S207). On the other hand, the user 2 looks at the displayed user registration information and confirms whether there is any change or whether there is information to be newly registered, and if there is information to be changed or newly registered, the user terminal It is input through the input unit 23 of 20. In response to this, the user terminal 20 determines whether or not new information to be registered has been input (step S209), and if there is input, the registration processing unit 22 notifies the notification service server 4
0 is requested to register new information (step S21)
0).

When it is determined in step S209 that there is no new information, it is determined whether there is an order for the delivery service (step S211). When it is determined that there is no order by the instruction of the user 2, the notification service server 40
Is requested to log off (step S223), and this processing ends. On the other hand, if it is determined in step S211 that there is an order, the order placement processing unit 21 makes an order request to the notification service server 40 (step S213). Then, the list of delivery service providers sent from the notification service server 40 is received (step S215), and a request for selecting the delivery service provider selected by the user 2 from the list is made (step S21).
7). Further, the list of delivery services that can be provided by the selected delivery service provider is received (step S21).
9). Then, the delivery service selected by the user 2 is selected from the list, and the user 2 further specifies the service content such as the timing at which the user wants to receive the service, and based on this, the user terminal 20 sends the service content data ( Step S221).

FIG. 11 is a diagram showing data of service contents sent from the user terminal 20 and registered in the order receiving unit 62 of the delivery service server 60 in step S221. As shown in FIG. 11, the service content data includes the user ID, the service content desired by the user 2, and the data of the timing when the user wants to receive the service. Here, regarding the timing at which the user 2 wants to receive the service, the user 2 does not need to set the direct time in detail. For example, even if the user 2 wants to receive a delivery service after returning home, it is difficult to assure the concrete return time from various factors that occur after the order is placed. Therefore, in the present embodiment, the user 2 sets the service timing immediately after the event of the user 2 “going home” as shown in FIG. 11, and does not set the direct time as shown in hours and minutes. I haven't. As described above, in the delivery service system 10, the user 2 wants to receive the service at “after returning home” or “at home 15”.
It can be set in relation to the action (event) of the user 2, such as “after minutes”.

Then, when the specification of the service contents in step S221 is completed, the user terminal 20 requests the notification service server 40 to log off (step S2).
23), the process ends. The user 2 who has performed the user registration and the order for the delivery service using the user terminal 20 as described above performs the service at an appropriate time by the processing performed by the notification service server 40, the passage information distribution device 70, and the delivery service server 60. Can be provided.

Next, a specific method of acquiring the user's tracking record will be described. FIG. 12 is a diagram illustrating a flow of acquisition of a tracking record in the passage information distribution device 70.
The passing information distribution device 70 first detects the notification service server 40.
The information of the user registered as a member of the delivery service system 10 is received via the communication processing unit 77 (step S701). The received user information is registered in the user information registration unit 72 in the passage information distribution device 70 (step S703). The passage information distribution device 70
Is notified by the notification service server 40 when the user information is registered in step S206 or step S210 shown in FIG. 8 or at every predetermined time based on the information shown in FIG. 9C in the notification service server 40. The user ID to be received is received.

The passage information distribution device 70 is connected to the ticket gate 71 of the abc station as shown in FIG. 1, and recognizes a person who has passed through the ticket gate 71 detected by the ticket gate 71 (step S705). ). As a specific recognition method at this time, data such as a user ID unique to the person passing through is included in a commuter pass or the like, and the ticket gate 71 detects the user ID for recognition. Done. Next, the user determination unit 74 determines whether or not the passing person is registered as a member in the user information registration unit 72 (step S707). If it is determined that the passing person is not registered as a member, this processing ends. If it is determined that the person who has passed through is the user 2 who is registered as a member, the user 2
The passage information of is registered in the passage information registration unit 75 (step S709). The registered passage information is passed to the passage information distribution unit 7
6 is delivered to the notification service server 40 (step S711).

As described above, the tracking record of the user 2 who is a registered member is acquired at the abc station, which is the position providing point, and is sent to the notification service server 40. In this way, since it is determined whether the person who has passed through the ticket gate 71 is a registered member and the tracking record is acquired only when the member is a member, it is not necessary to collect the data of those who do not wish to acquire the tracking record or non-members. Therefore, it is preferable in consideration of privacy. Further, it is efficient because unnecessary data is not delivered to the notification service server 40. The type of tracking record that is automatically provided due to the behavior of the user 2 passing through the fixed location providing point in this way is called "push type" data. In addition, as a push type tracking record,
The home of the user 2, which is the destination, can also be set as the position providing point. In this case, User 2 arrives at home,
When the home security system recognizes that the user has arrived at the home by opening the entrance key or the like, the tracking record is sent to the notification service server 40.

The method of acquiring the tracking record of the user 2 is not limited to the method described with reference to FIG. For example, the tracking record can be acquired using the mobile terminal 30 owned by the user 2. First, the mobile terminal 30 uses the position data request acceptance unit 31 to notify the notification service server 4
The position data request of user 2 is accepted from 0. In response to this, the mobile terminal 30 receives the radio wave from the satellite in the radio wave reception unit 32, and detects the position of the user 2 in the position detection unit 33. Then, the obtained position of the user 2 is transmitted from the position data transmitting unit 34 to the notification service server 40 via the network. In this way, by using the mobile terminal 30, the position providing point is not fixed, and the tracking record of the user 2 can be obtained anywhere within the range where the radio waves reach. The method of acquiring position data in the mobile terminal 30 is not limited to GPS, and a method of detecting the position of the mobile phone based on the connection strength of the radio waves of the mobile phone or the like can also be used. In this way, the position providing point is not fixed, and the type of the tracking record obtained by the request from the notification service server 40 is called “pull type” data.

FIG. 13 is a diagram for explaining the flow of processing when registering a tracking record in the notification service server 40. First, the notification service server 40 acquires new tracking records in the user position information processing unit 42 (step S405). The new tracking record to retrieve may be either push type or pull type.
Here, when acquiring the tracking record of the user 2, the notification service server 40 uses the reference permission data as shown in FIG. 9C in the user information of the user registration information storage unit 51 of the user 2 and the position information provider DB 54. The location information provider data recorded in FIG. 14 is referred to. When the pull-type information provider is registered for the user 2, the time for inquiring the mobile terminal 30 about the position of the user 2 is set, and the user position is set for the mobile terminal 30 at each set time. The tracking record is obtained by inquiring.

Then, the notification service server 40 registers the acquired new tracking record in the user position information storage unit 52 (step S407). FIG. 15A shows an example of a specific tracking record registered. The tracking record registered in this manner includes the member ID for identifying which user 2 the information is, and the data of the position providing point and the position providing time. When the notification service server 40 acquires a new tracking record, the notification service server 40 performs a registration process in step S407 and a process of notifying the delivery service provider of the tracking record. The latter process of notifying the delivery service provider of the tracking record will be described later.

When the new tracking record is registered, the notification service server 40 refers to the user position information storage unit 52,
It is determined whether there is a tracking record acquired in the past (step S409). When it is determined that the past tracking records are not stored in the user position information storage unit 52, this process ends. When it is determined that there is a past tracking record, it is determined whether the position providing time of the past tracking record is within a predetermined time from the current time (step S411). If it is determined that it is not within the predetermined time, that is, the predetermined time has elapsed after the acquisition, the past tracking record is deleted (step S412).

The predetermined time in step S411 can be set arbitrarily, but for example, it can be set so that a tracking record that has passed three hours or more after the tracking record is acquired is deleted. If the time elapsed from the position providing time of the tracking record to the present time is too long, the tracking record cannot be used to calculate the accumulated record described later. As a specific example,
Even if the accumulated record is calculated from the traced record acquired at the abc station when user 2 goes to work in the morning and the new traced record when user 2 returns home, the time required for the accumulated record Is too long and the data may change significantly depending on the day, so that the accumulated record cannot be directly used in the delivery service system 10. Further, if unnecessary tracking records are recorded, the amount of data of the accumulated tracking records will increase infinitely, so it is preferable to delete the unnecessary tracking records. Note that such unnecessary tracking record deletion is not limited to when a new tracking record is received, and may be periodically performed by the notification service server 40 at predetermined time intervals.

If it is determined in step S411 that the position providing time of the past tracking record is within the predetermined time, the new tracking record registered in step S407 is compared with the past tracking record. Then, the time taken for the user 2 to reach the position providing point of the new tracking record from the position providing point of the past tracking record is calculated (step S413). Here, for example, if the past tracking record is a tracking record acquired at the abc station and the new tracking record is a tracking record acquired when the user 2 arrives at his / her home, it is possible to reach the home from the abc station. The required time is calculated.

Next, the notification service server 40 determines whether or not the accumulated record has already been recorded in the user position information accumulating section 52 for the user 2 (step S4).
15). Here, the accumulated record is, as shown in FIG. 15B, data including a destination point, a position providing point of the tracking record used to calculate the accumulated record, and a required time. When the notification service server 40 determines that the accumulated record has not been registered in the user position information accumulation unit 52, the value calculated in step S413 is a limit calculated from the distance between the position providing point and the destination point. It is checked whether it is within the range of values (step S416). If the required time is too long compared to the distance, for example, when you visit a store near your home during work, you accidentally pass a point near the destination but not toward the destination. It is assumed that the value is calculated in such a case. If the value calculated in this way is used, the correct required time will not be calculated. Therefore, it is desirable to set a limit value and determine whether the required time is less than or equal to the limit value. Here, although the limit value can be set arbitrarily, for example, it can be set to 30 minutes per kilometer according to the distance. Step S413
When it is determined that the value calculated in step S4 is within the range of the limit value, a new accumulated record is registered (step S41).
8). If it is determined that the value is not within the range of the limit value, this processing ends.

On the other hand, when it is determined that there is a storage record already registered in the user position information storage unit 52, the notification service server 40 determines whether the required time calculated in step S413 is less than or equal to the threshold value (step S).
417). In addition, if the required time is too long than the accumulated record that has already been registered, the user 2 does not normally perform the action between the position providing point and the destination point (e.g., returning home or shopping on a different route). You may have visited the store to do so). Therefore, considering the required time when such an unusual action is taken, the correct required time cannot be calculated. Therefore, it is necessary to set a threshold value and determine whether the required time is less than or equal to the threshold value. Although the threshold value can be set arbitrarily, for example, with respect to the required time of the accumulated record already registered in the user position information accumulating section 52, ± 1 km per 1 km depending on the distance.
It can be set to 5 minutes.

When the notification service server 40 determines in step S417 that the required time is longer than the threshold value, the process returns to step S409, other registered past tracking data is extracted, and the same process as above is started. On the other hand, when it is determined that the required time is less than or equal to the threshold value, the accumulated record recorded in the user position information accumulating unit 52 is updated (step S419), and this processing ends. The update can be processed by, for example, taking an average value from the accumulated records accumulated in the past and the accumulated record this time. As described above, the user position information storage unit 52
The accumulated record recorded in is always updated with a new tracking record, and the update is processed without adopting a tracking record different from a normal tracking record. It can be calculated.

FIG. 16 is a diagram for explaining the flow of processing of the delivery service ordered by the user 2 in the notification service server 40. First, the notification service server 40
The user registration information processing unit 41 receives the logon request sent from the user terminal 20 (step S43).
1). The notification service server 40 authenticates the user 2 who logs on by referring to the user registration information storage unit 51 of the user DB 50 in the user registration information processing unit 41.
When the user 2 is not a registered member, the registration request of the user 2 is received, and then the logon request is received.

Next, the notification service server 40 issues a security token to the user terminal 20 of the logged-on user 2 by referring to the user security information storage unit 53 (step S433). By using the security token in this manner, it is possible to prevent the information of the user 2 from being leaked to others. The data of the security token in the user security information storage unit 53 is shown in FIG.
It is issued for each user 2 as shown in, and prevents the user information from leaking to the outside. Subsequently, the notification service server 40 sends the registration information of the user 2 stored in the user registration information storage unit 51 to the user terminal 20 (step S435). The response from the user terminal 20 is received, and it is determined whether or not the user registration information is updated (step S437). If it is determined that there is an update, the data is updated (step S438).

When the notification service server 40 determines in step S437 that the user registration information has not been updated, it determines whether there is an order for delivery service from the user 2 (step S439). If it is determined that there is no order, this process ends. When it is determined that an order has been placed, a list of delivery service providers capable of providing the service to the user 2 among the delivery service providers registered in the delivery service provider information DB 55 is sent to the user terminal 20 (step S441). ). Delivery service provider information DB
18, the location, the type of service that can be delivered, and the data of the deliverable range are registered for each delivery service provider as shown in FIG. 18, and the URL of the connection destination of the delivery service provider and the order are accepted. UR of order destination
L is registered. Here, U of the communication destination and the ordering destination
Although the RLs are different, the same URL may be used.

The notification service server 40 includes the order relay unit 4
3, the user 2's selection request for the delivery service provider is accepted (step S443). Then, the notification service server 40 sends the security token to the selected delivery service provider (step S4).
45). Then, the order relay unit 43 issues an order relay connection request for relaying the order to the delivery service server 60 of the delivery service company (step S44).
7). Then, the connection acceptance sent from the delivery service server 60 in response to the sent order relay connection request is accepted (step S449). When the order relay connection is performed in this way, the user terminal 20 can make a specific order for the delivery service to the delivery service server 60.

Next, the notification service server 40 accepts the logoff request sent from the user terminal 20, disconnects the connection with the user terminal 20, and ends the order relay connection (step S451). And the notification service server 4
0 accepts the notification request sent from the delivery service server 60 in the notification request processing unit 44 (step S4).
53), and further inspects the security token sent from the delivery service server 60 (step S45).
5).

Thereafter, the notification service server 40 issues a notification request ID to the received notification request, and notifies the delivery service server 60 that the notification request has been received (step S457). Further notification service server 4
0 registers the notification request in the notification request DB 56 (step S459), and ends this processing. Here, the notification request data registered in the notification request DB 56 is the member ID of the user 2 who placed the order, the delivery service provider ID that provides the service, and the position where the service is provided, as shown in FIG. It includes data of the point ID and a notification set time indicating how many minutes before the user 2 is scheduled to reach the destination point for providing the service, the delivery service server 60 is notified. The notification service server 40, which has registered the notification request as described above, performs the notification process upon receiving the new tracking record. Next, the notification processing by the notification service server 40 will be described.

FIG. 20 is a diagram for explaining the flow of notification processing in the notification service server 40. First, the notification service server 40 uses the passage information distribution device 70 and the mobile terminal 3
A new tracking record is obtained from 0 (step S471).
Then, the notification service server 40 determines whether or not there is a notification request for the user 2 of the tracking record.
The determination is made by referring to 56 (step S473). If it is determined that there is no notification request, this process ends. When it is determined that there is a notification request, the notification request data is read from the notification request DB 56 (step S475). Since the destination point is indicated by the ID in the read notification request data as shown in FIG. 19, the specific destination point is referred to by referring to the point information shown in FIG. 9B recorded in the user DB 50. Read the latitude and longitude of.

Next, the notification service server 40 judges whether or not the accumulated record including the data of the destination is registered in the user position information accumulating section 52 (step S4).
77). When it is determined that there is no accumulated record, it is determined whether an auxiliary record is registered in the user position information accumulating unit 52 (step S478). When it is determined that the auxiliary record is not registered in the user position information storage unit 52, the process returns to step S473 again, and the process of determining whether or not there is another notification request is performed. For example, when the user 2 orders multiple delivery services,
Since there is a possibility that a notification request different from the notification request to be processed this time is registered for the user 2, this processing is continued until there is no notification request.

The notification service server 40 executes the step S4.
If it is determined in 77 that there is an accumulated record, or if it is determined in step S478 that there is an auxiliary record, the accumulated record or auxiliary record is read (step S479). Then, it is determined whether or not the data indicating the position providing point of the read accumulated record or auxiliary record is the “point fixed type” calculated from the push type tracking record (step S48).
1).

If it is determined in step S481 that the location is fixed, the notification service server 40 determines whether the location providing point of the accumulated record or the auxiliary record matches the location providing point of the new tracking record (step S483). ). If it is determined that they do not match, the process of step S477 is performed again in order to check whether or not there is any other accumulated record or auxiliary record registered.

A case will be described in which it is determined in step S481 that the record is not the fixed point type, that is, the accumulated record or the auxiliary record of the "non fixed point type" calculated from the pull type tracking record. In this case, the notification service server 40 determines whether the position providing point of the accumulated record or the auxiliary record is within the predetermined range from the position providing point of the new tracking record (step S482). When it is determined that the position is not within the predetermined range, it is further determined whether the position providing point of the new tracking record is closer to the destination than the position providing point of the accumulated record or the auxiliary record (step S484). When it is determined that the destination is not close to the destination, the process returns to step S475 to search for another notification request record and continue the processing.

Next, in the following cases, the notification service server 40 determines whether the time required for the user 2 indicated by the accumulated record or the auxiliary record to reach the destination is within the range of the notification setting time of the position request data. It is determined (step S485). When the position providing point of the accumulated record or the auxiliary record matches the position providing point of the new tracking record in step S483. In step S482, the position providing point of the accumulated record or the auxiliary record is predetermined from the position providing point of the new tracking record. If it is determined that the position is within the range-In step S484, it is determined that the position providing point of the new tracking record is closer to the destination than the position providing point of the accumulated record or the auxiliary record (in this case, according to the distance). You can also dynamically correct the set time by

When the notification service server 40 determines in step S485 that the required time is not within the range of the notification set time, the process returns to step S477, and the process for determining whether there is another suitable accumulated record or auxiliary record is continued. To do. On the other hand, when it is determined that the required time is within the notification set time range, the delivery service server 60 of the delivery service provider is notified (step S48).
7). Then, the notification request for which the notification is completed to the delivery service server 60 is deleted from the notification request DB 56 (step S489). Then, it is determined whether or not there is another notification request for the user 2 in the notification request DB 56 of the notification service server 40. (Step S49
1) If it is determined that there is another notification request, the process returns to step S475, and the notification request is similarly processed. On the other hand, when it is determined that there is no notification request in the notification request DB 56, this processing ends.

Thus, when the notification service server 40 receives the new tracking record, it registers the tracking record shown in FIG. 13 and performs the notification processing shown in FIG. Therefore, the notification service server 40 can notify the delivery service server 60 of the delivery service provider that the user 2 has arrived at the predetermined position efficiently and with good timing. As a result, the delivery service provider can start preparation for providing the service to the user 2 upon receiving the notification, and can provide the delivery service to the user 2 in a timely manner.

FIG. 21 is a diagram for explaining the flow of processing in the delivery service server 60. First, the delivery service server 60 of the delivery service provider receives the relay connection request from the notification service server 40 in the relay connection request processing unit 61 (step S601). Upon receiving the relay connection request, the notification service server 40 permits the user terminal 20 to connect to a website on the Internet (order destination URL shown in FIG. 18) that provides an interface through which services can be ordered. And user 2
The service contents that can be provided by the delivery service provider are extracted from the service DB 68 and sent to the user terminal 20 (step S603). On the other hand, the service request transmitted from the user terminal 20 for the service selected by the user 2 is accepted (step S605), and the relay connection is terminated.

Subsequently, the delivery service server 60 considers the selected service type, the destination point where the user 2 wants to receive the desired service, and the timing of the service desired by the user 2, and gives a notification. The notification request processing unit 63 calculates the set time (step S607).
For example, the delivery service server 60 calculates backward from the timing the time taken from the start of preparation for providing the service to the provision of the service so that the user 2 can provide the service at the desired service timing. Notification set time can be set.

The delivery service server 60 causes the notification request processing unit 63 to send the calculated notification set time together with the notification request to the notification service server 40 to make a registration request (step S609). Correspondingly, the notification request ID sent from the notification service server 40 is received (step S611), the processing for order acceptance is ended, and the notification service server 40 waits for a notification.

The delivery service server 60 includes the notification processing unit 6
4, the notification sent from the notification service server 40 is confirmed by confirming the notification request ID (step S6).
13). Then, the delivery service server 60 outputs the output section 66.
At, an instruction to start the service providing process for the user 2 is output (step S615), and the delivery service provider starts the service providing process accordingly.
As described above, the processing of the delivery service server 60 ends.

As described above, in the delivery service system 10 according to the present embodiment, the user 2 uses the ticket gate 7 at the abc station.
The service can be provided at a good timing by using the event of the user 2 passing 1 as a trigger. Specifically, user 2 is the location providing point ab
It is possible to accumulate the data of the time required to reach the home from the c station, and based on the accumulated data, it is possible to predict the return time of the user 2 based on the event of the user and provide the service. Therefore, when the user 2 places an order for providing the service, it is not necessary to set the providing time in detail and specifically, and since the order is placed, the time of the user 2 is not restricted after the order is placed. It is very convenient for user 2. Moreover, since the probability that the user 2 who is the service providing destination will not be present at the service providing place at the time of providing the service is low, the delivery service provider can efficiently provide the service.

In the above embodiment, the notification service server 40 and the delivery service server 60 are separately configured, and the notification service agent and the delivery service agent manage the processing by each server. 40 and the delivery service server 60 may be configured by one server. In that case, the notification service provider and the delivery service provider may be the same or different providers. Also, the notification service server 40, the delivery service server 60, the passage information distribution device 70.
Are each made up of one machine,
It may be composed of a plurality of servers with distributed functions. Furthermore, the user terminal 20 is the delivery service server 6
Instead of connecting to 0, the notification service server 40 may be configured to accept orders on behalf of and forward them to the delivery service server 60.

Further, in the above-mentioned embodiment, the position information providing point from which the push type tracking record can be obtained is set to the abc station used by the user 2 or the user's home. May be For example,
It can be set to the gate of the company where the user 2 works, or if the user 2 always shop at the same store. The user 2 can leave a record of the tracking record by using a card (a time card, a shopping card, etc.) in which the ID of the user 2 is registered at each position information providing point. Further, in the above-described embodiment, the service providing point is set to the home, but the user 2 can set an arbitrary place as the service providing point as a place other than this. In that case, the timing of the service can be acquired by processing the tracking record or the storage record having the position data close to the newly set service providing point.

In addition, although the service provided in the above embodiment is a delivery service, the type of service that can be provided in the delivery service system 10 is not limited to this. For example, it is possible to provide services such as starting adjustment of the air conditioning and heating the bath before the user 2 returns home in consideration of the user 2's return home time. Other than this, the configurations described in the above embodiments can be selected or changed to other configurations without departing from the gist of the present invention.

[0070]

As described above, according to the present invention, it is possible to provide a service in a timely manner even if the user does not specify a specific time for providing the service.

[Brief description of drawings]

FIG. 1 is a diagram illustrating a delivery service system according to the present embodiment.

FIG. 2 is a diagram showing a configuration of a user terminal shown in FIG.

FIG. 3 is a diagram showing a configuration of the mobile terminal shown in FIG.

4 is a diagram showing a configuration of a notification service server shown in FIG.

5 is a diagram showing a configuration of a delivery service server shown in FIG.

FIG. 6 is a diagram showing a configuration of the passage information distribution device shown in FIG. 1.

FIG. 7 is a diagram illustrating an example of a service received by a user in the delivery service system.

FIG. 8 is a diagram illustrating a processing flow of a user terminal.

FIG. 9 is a diagram illustrating user information recorded in a user registration information storage unit, in which (a) is user information data;
(b) is a diagram showing location information data, and (c) is a diagram showing reference permission information data.

FIG. 10 is a diagram illustrating an auxiliary record recorded in a user position information storage unit.

FIG. 11 is a diagram illustrating data of service contents ordered by a user.

FIG. 12 is a diagram illustrating a flow of acquisition of a tracking record in the passage information distribution device.

FIG. 13 is a diagram illustrating a flow of processing when a tracking record is registered in a notification service server.

FIG. 14 is a diagram illustrating position information provider data recorded in a position information provider DB.

15A and 15B are diagrams illustrating data recorded in a user position information storage unit, in which FIG. 15A is a diagram showing a tracking record and FIG. 15B is a diagram showing a storage record.

FIG. 16 is a diagram illustrating a processing flow of a delivery service ordered by a user in the notification service server.

FIG. 17 is a diagram illustrating data of a security token recorded in a user security information storage unit.

FIG. 18 is a diagram illustrating data of a delivery service agent recorded in a delivery service agent information DB.

FIG. 19 is a diagram illustrating position request data recorded in a notification request DB.

FIG. 20 is a diagram illustrating a flow of notification processing in the notification service server.

FIG. 21 is a diagram illustrating a processing flow in the delivery service server.

[Explanation of symbols]

10 ... Delivery service system, 20 ... User terminal, 21
... order / order processing unit, 22 ... registration processing unit, 30 ... mobile terminal, 31 ... position data request receiving unit, 33 ... position detecting unit,
34 ... Position data transmission unit, 40 ... Notification service server (timing adjustment server), 41 ... User registration information processing unit, 42 ... User position information processing unit (position information processing unit),
43 ... Order relay section (application recognition section), 44 ... Notification request processing section (timing calculation section), 50 ... User DB, 51 ... User registration information storage section (user permission information storage section), 52 ...
User position information storage unit, 54 ... Position information provider DB, 5
5 ... Delivery service provider information DB, 60 ... Delivery service server, 61 ... Relay connection request processing unit, 62 ... Order receiving unit,
63 ... Notification request processing unit, 64 ... Notification processing unit, 70 ... Passage information distribution device, 71 ... Ticket gate (recognition unit), 72 ... User information registration unit, 73 ... Passage information receiving unit (recognition unit), 74 ...
User determination unit (determination processing unit), 75 ... Passing information registration unit (presence time recording unit), 76 ... Passing information distribution unit (position time data output unit)

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Akira Daimon             1623 1423 Shimotsuruma, Yamato-shi, Kanagawa Japan             BM Co., Ltd. Daiwa Office (72) Inventor Satoko Tonegawa             1623 1423 Shimotsuruma, Yamato-shi, Kanagawa Japan             BM Co., Ltd. Daiwa Office

Claims (17)

[Claims] 1. A timing adjustment system for adjusting the timing of providing a predetermined service to a user, the user position recognizing unit recognizing that the user has reached a predetermined position information providing point, and the user position. Recording means for recording a tracking record including time data recognized by the recognition means, position data of the position information providing point, and identification data of the user, and a user who receives the predetermined service at a predetermined service providing point When the application is accepted by the application acceptance means for accepting an application for the service by the user and the user position recognition means recognizes that the user has reached the position information providing point, Using the past tracking records recorded in the recording means, the position information By calculating the time required from the point to the service provision point, timing adjustment system characterized by comprising an acquisition unit configured to acquire the timing of providing services for a user. 2. The time data and the position data are push type data transmitted from the position information providing point when the user passes through the fixed position information providing point. 1. The timing adjustment system described in 1. 3. The time data and the position data are pull-type data transmitted from the mobile communication terminal when the user position recognition means requests the mobile communication terminal owned by the user. The timing adjustment system according to claim 1, characterized in that 4. A passage information distribution device for distributing position information of a user via a network and a position information of the user from the passage information distribution device via the network to provide a predetermined service to the user. And a timing adjustment server that adjusts the timing to perform, wherein the passage information distribution device recognizes that the user has reached a position information providing point, and the user's point arrival recognition information generated by the recognition. To the timing adjustment server, the timing adjustment server recognizes the order of the predetermined service from the user, receives the point arrival recognition information sent from the passage information distribution device, and receives the point arrival recognition. Calculated from the information to calculate the estimated time at which the user will arrive at the service providing point Service providing system, characterized in that to get the timing to provide a service from the serial scheduled arrival time. 5. The timing adjustment server further includes a service providing server of a service provider that provides a service, wherein the service providing server receives an order of the predetermined service by the user and notifies the timing of the service. 5. The service providing system according to claim 4, wherein the timing adjustment server sends the timing to the service providing server in response to the notification request from the service providing server. 6. A timing adjustment server that adjusts the timing for providing a predetermined service to a user, the predetermined point data indicating a predetermined position providing point, and a point providing the predetermined service to the user. Accumulation means for accumulating a user record containing service providing point data, required time data from the position providing point to the service providing point, order recognition means for recognizing an order of the predetermined service by the user, After recognizing the order by the order recognizing means, a passage information receiving means for receiving passage information of the user at a specific position, and among the user records accumulated by the accumulating means,
Extracting means for extracting a user record in which the position providing point is within a predetermined range from the specific position; and arrival time calculating means for calculating an estimated arrival time of the user at the service providing point based on the extracted user record. And a service providing instruction means for instructing a timing of providing the service based on the calculated estimated arrival time. 7. The timing adjustment server according to claim 6, wherein the user record is calculated from a tracking record generated when the user reaches a fixedly provided position providing point. 8. The timing adjustment server according to claim 6, wherein the user record is calculated from a tracking record obtained by requesting a mobile communication terminal owned by the user. 9. The user permission information storage unit for recording the position acquisition method permitted by the user to acquire the position information of the user.
The described timing adjustment server. 10. A relay process for relaying and connecting the user terminal to a service providing server that provides the predetermined service when the order recognition unit recognizes the order sent from the user terminal of the user. 7. The timing adjustment server according to claim 6, further comprising means. 11. A timing adjustment server that adjusts the timing for providing a predetermined service to a user, the position of the user, and the time when the user was at the position,
An acquisition unit that acquires a tracking record that indicates the tracking record, a storage unit that records the tracking record in a tracking record storage unit, and a new tracking record that is acquired for the user. Tracking record determining means for determining whether or not the acquired past tracking records are accumulated, based on the past tracking records and the new tracking records,
A required time calculating means for calculating a required time from the data acquisition point of the past tracking record to the data acquisition point of the new tracking record; and the calculated required time for calculating timing for providing the predetermined service. Required time determining means for determining whether or not the required time is appropriate data, and a record for recording the required time as an accumulated record in the accumulated record accumulating unit when it is determined that the required time is appropriate data. Means, when the user applies for the provision of the predetermined service,
A tracking record to be newly acquired, the accumulated record,
And a service timing calculation means for calculating the timing from the timing adjustment server. 12. A user information distribution device which recognizes and records the position of a user in order to adjust the timing for providing the predetermined service to the user, and is registered as a person who receives the predetermined service. A storage unit that has registered user registration information indicating whether the user is present, a recognition unit that recognizes the presence of the user at a predetermined position providing point, and a determination that determines whether the user is user-registered in the storage unit. When the processing unit determines that the user is registered as a user, the time recording unit that records the time when the user existed, and outputs the time together with the data indicating the location providing point to the outside through the network. A user information distribution device, comprising: a position / time data output unit. 13. The recording device according to claim 12, wherein when the user recognized by the recognition unit is determined not to be registered as a user, the time when the user is recognized is prohibited from being recorded in the time recording unit. User information distribution device. 14. A timing adjusting method for adjusting a timing for providing a predetermined service to a user via a network, the method comprising: recognizing that the user has reached a position information providing point; A step of obtaining a tracking record including time data indicating a time at which the position information providing point is recognized, position data indicating a position of the position information providing point, and user identification data of the user; A step of receiving an application for the service by a user who receives the predetermined service at a predetermined service providing point, and recognizing that the user has reached the position information providing point, based on the tracking record acquired in the past, Calculate the time required from the location information providing point to the service providing point Timing adjusting method characterized by comprising the steps of: obtaining a timing that provides a service to the user by. 15. A method for a service provider to adjust the timing of providing a predetermined service to a user, the registration of a user who receives the predetermined service being accepted,
Accumulating data relating to the user including identification data and position data in a database, and from the position providing point for detecting the position of the user until the user reaches the service providing point for providing the predetermined service Calculating a required time and accumulating it in the database; receiving a timing notification request from the service providing system for notifying the service providing system of the service providing timing; and the user providing the position providing point. Recognizing that the user is located at the position providing point, determining whether there is the timing notification request for the user located at the position providing point, and determining that there is the timing notification request, the user is the position Be located at the service point From the recognized position recognition time and the required time and the timing adjustment method characterized by a step of the user to calculate the expected time required to arrive at the service provision point. 16. A step of determining whether a desired notification setting time designated by the timing notification request is less than or equal to the planned required time, and a step of determining that the desired notification setting time is less than or equal to the planned required time. 16. The timing adjusting method according to claim 15, further comprising the step of notifying the service providing system that the timing has come. 17. The step of calculating and accumulating the required time accumulates a plurality of tracking records obtained by tracking the behavior of the user, and from the tracking records,
The step of calculating the average required time from the position providing point to the service providing point, and calculating the planned required time is such that when the user reaches the position providing point, the user arrives at the service providing point. The timing adjustment method according to claim 15, wherein a scheduled time is calculated from the average required time, and a timing for providing the predetermined service to the user is set according to the calculated estimated time of arrival.