WO2022249376A1

WO2022249376A1 - Schedule management device, system, method, and computer readable medium

Info

Publication number: WO2022249376A1
Application number: PCT/JP2021/020136
Authority: WO
Inventors: 哲也冬野
Original assignee: 日本電気株式会社
Priority date: 2021-05-27
Filing date: 2021-05-27
Publication date: 2022-12-01
Also published as: JPWO2022249376A1

Abstract

A schedule management device (1) comprises: a registration unit (11) that registers schedule information, including a scheduled stay time slot in which a prescribed user is planning to stay at a first location; an acquisition unit (12) that acquires current-stay information relating to a second location at which the user is currently staying; an estimation unit (13) that estimates an estimated arrival time at which the user will arrive at the first location on the basis of the schedule information and the current-stay information; and a notification unit (14) that, if the estimated arrival time satisfies a prescribed condition with respect to a start time of the scheduled stay time slot, notifies the user and/or an affiliated party of the first location of the estimated arrival time.

Description

Appointment management device, system, method and computer readable medium

The present invention relates to a schedule management device, system, method and program, and more particularly to a schedule management device, system, method and program for managing users' schedules.

　In some cases, it is possible to specify the delivery time zone in advance for the package to be delivered to the delivery company. Patent Literature 1 discloses a technology for managing a device that allows a user using a delivery service to collectively send a delivery request, an at-home notice that means a pickup request, and an out-of-office notice that means that the user is out of the office, to delivery workers of multiple delivery companies. is disclosed. Patent Literature 2 discloses a technology related to a delivery support system that notifies a delivery company whether or not a recipient at a delivery destination is at home.

JP 2018-190361 A JP 2017-111519 A

Here, the user, who is planning to stay at the destination (first point) during a predetermined time period, may not be able to arrive at the destination at another point (second point) where he or she has previously stayed due to various factors. may be delayed. In the example of home delivery, even if the expected time period for staying at home is decided, if the person spends more time outside than planned, the return home may be delayed. However, it is not always possible for the user to timely grasp the delay in the arrival schedule of the user, and in particular, it is not always possible to appropriately perform the procedure for changing the scheduled delivery time. In other words, when it is predicted that the estimated time of arrival at the first point will be changed according to the user's actual behavior, etc., a person related to the destination (for example, a delivery company) or the user himself/herself can There is a problem that it is difficult to grasp the scheduled time.

In view of the above-mentioned problems, the purpose of the present disclosure is to allow the user himself or the person concerned at the destination to appropriately grasp the change in the estimated arrival time to the destination according to the user's stay place and stay time other than the destination. It is an object of the present invention to provide a schedule management device, system, method and program for making it possible.

A schedule management device according to a first aspect of the present disclosure includes:
a registration means for registering schedule information including an expected stay time period in which a predetermined user plans to stay at a first point;
Acquisition means for acquiring staying information about a second point where the user is staying;
estimating means for estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the stay information;
notification means for notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
Prepare.

A schedule management system according to a second aspect of the present disclosure includes:
an authentication terminal installed at a second location;
a schedule management device;
The schedule management device
a registration means for registering schedule information including an expected stay time period in which a predetermined user plans to stay at a first point;
Acquisition means for acquiring, from the authentication terminal, staying information about the second point where the user is staying;
estimating means for estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the stay information;
notification means for notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
Prepare.

A schedule management method according to a third aspect of the present disclosure includes:
the computer
Registering schedule information including a scheduled stay time zone in which a predetermined user plans to stay at a first point;
Acquiring staying information about a second point where the user is staying;
estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the information during stay;
When the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time, the estimated arrival time is notified to at least one of the user and the person concerned at the first spot.

A schedule management program according to a fourth aspect of the present disclosure,
a registration process for registering schedule information including an expected stay time zone in which a predetermined user plans to stay at a first point;
Acquisition processing for acquiring staying information about a second point where the user is staying;
An estimation process for estimating an estimated arrival time at which the user will arrive at the first point based on the schedule information and the information during stay;
a notification process of notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
run on the computer.

According to the present disclosure, according to the user's place of stay and time of stay other than the destination, schedule management for enabling the user himself or the person concerned with the destination to appropriately grasp the change in the estimated time of arrival at the destination An apparatus, system, method and program can be provided.

1 is a block diagram showing the configuration of a schedule management device according to the first embodiment; FIG. 4 is a flow chart showing the flow of a schedule management method according to the first embodiment; FIG. 11 is a block diagram showing the overall configuration of a schedule management system according to a second embodiment; FIG. FIG. 9 is a block diagram showing the configuration of a user terminal according to the second embodiment; FIG. FIG. 9 is a block diagram showing the configuration of an authentication terminal according to the second embodiment; FIG. FIG. 11 is a block diagram showing the configuration of an authentication device according to the second embodiment; FIG. FIG. 12 is a block diagram showing the configuration of a schedule management device according to the second embodiment; FIG. 9 is a flowchart showing the flow of user information registration processing according to the second embodiment; 9 is a flow chart showing the flow of face information registration processing by the authentication device according to the second embodiment; FIG. 12 is a sequence diagram showing the flow of product order processing according to the second embodiment; 10 is a flowchart showing the flow of schedule registration processing according to the second embodiment; 9 is a flow chart showing the flow of face authentication processing by the authentication device according to the second embodiment; 10 is a flowchart showing the flow of scheduled time estimation processing according to the second embodiment; FIG. 11 is a sequence diagram showing the flow of schedule adjustment processing according to the second embodiment; FIG. 11 is an example of an examination request screen for an estimated delivery time displayed on the mobile terminal according to the second embodiment; FIG. FIG. 11 is a diagram showing an example of a notification screen (notification content display screen) of an estimated delivery time by the user terminal according to the second embodiment; FIG. 14 is a sequence diagram showing the flow of schedule adjustment processing according to a modification of the second embodiment; FIG. 11 is a diagram showing an example of a screen for accepting an estimated delivery time according to the second embodiment; FIG. 11 is a block diagram showing the overall configuration of a schedule management system according to a third embodiment; FIG. FIG. 11 is a block diagram showing the configuration of a schedule management device according to a third embodiment; FIG. FIG. 12 is a flow chart showing the flow of reservation registration processing according to the third embodiment; FIG. 14 is a flowchart showing the flow of scheduled time estimation processing according to the third embodiment; FIG. 13 is an example of a reservation date and time change approval request screen displayed on the store terminal according to the third embodiment; FIG. FIG. 12 is a diagram showing an example of a notification screen (notification content display screen) of a changed reservation date and time by the user terminal according to the third embodiment; FIG. 11 is a block diagram showing the overall configuration of a schedule management system according to a fourth embodiment; FIG. FIG. 13 is an example of a check-in alert screen displayed on the airport terminal according to the fourth embodiment; FIG.

Below, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same reference numerals are given to the same or corresponding elements, and redundant description will be omitted as necessary for clarity of description.

<Embodiment 1>
FIG. 1 is a block diagram showing the configuration of the schedule management device 1 according to the first embodiment. The schedule management device 1 estimates the estimated time of arrival at the first point in response to the fact that the user who is planning to stay at the first point during the scheduled time period stays at the second point, It is an information processing device for notification.

The schedule management device 1 includes a registration unit 11, an acquisition unit 12, an estimation unit 13, and a notification unit 14. The registration unit 11 registers schedule information including an expected stay time zone in which a predetermined user plans to stay at the first point. Acquisition unit 12 acquires staying information about a second point where the user is staying. Here, the staying information includes position information of the second point, time information when the user is staying at the second point, and the like. The location information of the second point is the location information of the authentication terminal installed at the second point, the location information of the portable terminal (user terminal) carried by the user, or the like. The time information is the time at which the user is authenticated by the authentication terminal installed at the second point, the acquisition time (current time) at which the acquisition unit 12 acquires the stay information, and the like. The estimation unit 13 estimates an estimated arrival time at which the user arrives at the first point based on the schedule information and the stay information. If the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period, the notification unit 14 notifies at least one of the user or the person concerned at the first point of the estimated arrival time. Specifically, the notification unit 14 transmits the estimated arrival time to the user terminal of the user or the terminal of the person concerned. Here, the relevant party is the delivery company if the first location is the delivery destination of the package. If the first location is a facility (hotel, restaurant, beauty salon, etc.) for which the user has made a reservation (specifying the scheduled stay time), the related party is the facility staff or the like. Further, the predetermined condition is, for example, that the estimated arrival time is before or after the start time of the scheduled stay period by a predetermined time.

FIG. 2 is a flow chart showing the flow of the schedule management method according to the first embodiment. The registration unit 11 registers the schedule information including the scheduled stay time zone in which the predetermined user plans to stay at the first point (S11). For example, the registration unit 11 receives schedule information from a user terminal operated by the user, and stores the received schedule information in a predetermined storage device. Here, the predetermined storage device may be one built into the schedule management device 1 or an external storage device connected to the schedule management device 1 .

Next, the acquisition unit 12 acquires staying information about the second point where the user is staying (S12). For example, the acquisition unit 12 acquires information during stay from the authentication terminal or user terminal installed at the second point while the user is staying at the second point. Then, the estimating unit 13 estimates the estimated arrival time at which the user arrives at the first point based on the schedule information registered in step S11 and the staying information acquired in step S12 (S13). After that, the schedule management device 1 determines whether or not the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay period (S14). When the predetermined condition is satisfied, the notification unit 14 notifies at least one of the user and the person concerned at the first point of the estimated arrival time (S15).

As described above, the schedule management apparatus 1 according to the present embodiment allows a user who is originally scheduled to stay at a first point to stay at a second point before arriving at the first point. It estimates the estimated time of arrival at a point. Then, when the estimated arrival time is different from the start time of the scheduled stay time period at the first spot by a predetermined time, the schedule management device 1 notifies the user and related persons of the estimated arrival time. Therefore, depending on the place and time of stay of the user at a place other than the destination (second point), the user himself/herself or a person concerned with the destination can appropriately change the estimated time of arrival at the destination (first point). can be grasped.

The schedule management device 1 includes a processor, memory, and storage device (not shown). Further, the storage device stores a computer program in which processing of the schedule management method according to the present embodiment is implemented. Then, the processor loads the computer program from the storage device into the memory and executes the computer program. Thereby, the processor realizes the functions of the registration unit 11 , the acquisition unit 12 , the estimation unit 13 and the notification unit 14 .

Alternatively, each component of the schedule management device 1 may be realized by dedicated hardware. Also, part or all of each component of each device may be implemented by general-purpose or dedicated circuitry, processors, etc., or combinations thereof. These may be composed of a single chip, or may be composed of multiple chips connected via a bus. A part or all of each component of each device may be implemented by a combination of the above-described circuits and the like and programs. As a processor, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field-Programmable Gate Array), a quantum processor (quantum computer control chip), or the like can be used.

Further, when part or all of each component of the schedule management device 1 is realized by a plurality of information processing devices, circuits, etc., the plurality of information processing devices, circuits, etc. may be centrally arranged, They may be distributed. For example, the information processing device, circuits, and the like may be implemented as a form in which each is connected via a communication network, such as a client-server system, a cloud computing system, or the like. Also, the functions of the schedule management device 1 may be provided in a SaaS (Software as a Service) format.

<Embodiment 2>
The second embodiment is a specific example of the first embodiment described above. FIG. 3 is a block diagram showing the overall configuration of the schedule management system 1000 according to the second embodiment. The schedule management system 1000 is an information system that manages a user's schedule and controls package delivery. For example, it is assumed that user U1 or U2 has purchased a product on electronic commerce server 400 and has performed a procedure to have package 401 (package) delivered to first location 501 (delivery destination) such as home. It is assumed that the users U1 and U2 are the same person or cohabitants at the first point 501 and who can receive the package 401 at the first point 501 . Also, if the first point 501 is a base of an organization, the users U1 and U2 should just belong to the organization and be able to receive the package 401 at the first point 501 .

The user U1 carries the user terminal 100-1, and the user U2 carries the user terminal 100-2. Here, it is assumed that the user terminals 100-1 and 100-2 have equivalent functions. In the following description, when there is no particular need to distinguish between the user terminals 100-1 and 100-2, they will be collectively referred to simply as "user terminal 100".

The user U1 or the like uses the user terminal 100 to register the scheduled stay time period at the first point 501 in the schedule management device 300 . In addition, it is assumed that the delivery company U3 is scheduled to deliver the package 401, which is the ordered product, to the first point 501 at the predetermined scheduled delivery time in response to the product ordered by the user U1 or the like. A delivery company U3 carries a mobile terminal 100-3. The delivery company U3 may load the package 401 onto a delivery vehicle (not shown) and drive the delivery vehicle to deliver the package 401 to the delivery destination.

Then, while the user U2 is staying at the second point 502, the authentication terminal 500 captures the face image of the user U2, and the schedule management device 300 controls the face authentication of the user U2. When the face authentication is successful, the schedule management device 300 determines the first location when the user U2 moves from the second location 502 to the first location 501 according to the location information of the authentication terminal 500, the authentication time, and the like. Estimate the estimated time of arrival at 501 . If the estimated arrival time is later than the start time of the scheduled stay time period at the first point 501 by a predetermined time or longer, the schedule management device 300 adjusts the estimated delivery time based on the estimated arrival time.

The schedule management system 1000 includes user terminals 100-1 and 100-2, an authentication device 200, a schedule management device 300, an electronic commerce server 400, an authentication terminal 500, and a mobile terminal 100-3. User terminals 100-1 and 100-2, authentication device 200, schedule management device 300, electronic commerce server 400, authentication terminal 500, and mobile terminal 100-3 are connected via network N so as to be able to communicate with each other. Here, the network N is a wired or wireless communication line or communication network, such as the Internet. The network N does not care about the type of communication protocol.

In the following description, face authentication, which is an example of biometric authentication, is used to verify the user's identity, and face feature information, which is an example of biometric information, is used to identify the user (personal identification information). However, biometric authentication and biometric information can be applied to other techniques that use captured images. For example, biometric information may be data (feature amounts) calculated from physical features unique to an individual, such as fingerprints, voiceprints, veins, retinas, irises, and palm patterns. Further, authentication for personal identification may be other than biometric authentication, and personal identification information may be other than biometric information. Examples of personal identification information include, but are not limited to, a user ID, a combination of an ID and a password, an electronic certificate, a two-dimensional code, and the like.

The user terminal 100 is an information terminal that is carried by each user and performs data transmission/reception with the schedule management apparatus 300 via the network N by wireless communication. The user terminal 100 is a mobile phone terminal, a smart phone, a tablet terminal, or the like.

FIG. 4 is a block diagram showing the configuration of the user terminal 100 according to the second embodiment. User terminal 100 includes camera 110 , storage unit 120 , memory 130 , communication unit 140 , input/output unit 150 and control unit 160 . The camera 110 is an imaging device that performs imaging under the control of the control unit 160 . The storage unit 120 is an example of a storage device such as flash memory. Storage unit 120 stores program 121 . The program 121 is a computer program in which processes including product order processing, user information registration processing, schedule registration processing, etc., which will be described later, are implemented. For example, program 121 includes a client application corresponding to schedule management device 300 .

The memory 130 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 160 operates. The communication unit 140 is a communication interface with the network N. FIG. The input/output unit 150 includes a display device (display unit) such as a screen and an input device. The input/output unit 150 is, for example, a touch panel. The control unit 160 is a processor that controls hardware of the user terminal 100 . The control unit 160 loads the program 121 from the storage unit 120 into the memory 130 and executes it. Thereby, the control unit 160 realizes the functions of the ordering unit 161 , the registration unit 162 and the display control unit 163 .

The ordering unit 161 accesses the electronic commerce server 400 via the network N and performs product ordering processing. Specifically, order unit 161 transmits a product order request to electronic commerce server 400 in accordance with a user's operation. The order request includes information on the product to be purchased, the delivery address of the product, payment information, and the like. The payment information may be credit card information, bank account information, or the like.

The registration unit 162 performs user information registration processing, schedule registration processing, and the like. Specifically, the registration unit 162 receives the user's face image and personal information input by the user. The registration unit 162 may accept a user's face image captured by the camera 110 . Also, the registration unit 162 may receive a face image from another mobile terminal or information processing device. The personal information is information including the user's name, address, telephone number, pre-hosting address, post-hosting address, payment information, and the like. Also, the registration unit 162 uses the terminal information of the user terminal 100 at the time of registration. The terminal information is information that becomes a notification destination when the user terminal 100 receives notification of information from the schedule management device 300 . The terminal information is, for example, a terminal ID, a client application login ID, an SNS (Social Network Service) account, an e-mail address, and the like. The registration unit 162 transmits a user registration request including the user's face image, personal information and terminal information to the schedule management apparatus 300 . Note that the face image is an example of personal identification information for registration. Therefore, the registration unit 162 may include the other personal identification information described above in the reservation registration request for registration instead of the face image.

In addition, the registration unit 162 accepts the planned stay place and planned stay time zone input by the user. The planned place of stay is location information such as the first point 501 and the second point 502 . For example, the location information of the first point 501 may be an address of a potential delivery point, such as the user's home, or GPS (Global Positioning System) information. The scheduled stay time zone is a set of start time and end time during which the user is scheduled to stay at the place of stay. The registration unit 162 transmits to the schedule management apparatus 300 a schedule registration request including the place of stay, the scheduled time period of stay, and the face image of the user. Note that the registration unit 162 may include the above-described other personal identification information in the planned registration request for authentication instead of the face image. Further, when receiving an approval operation for the scheduled delivery time from the user, the registration unit 162 transmits approval to the schedule management device 300 . Further, the registration unit 162 transmits the scheduled delivery time to the schedule management device 300 when receiving an operation to change the scheduled delivery time from the user. Further, the registration unit 162 sets the current time when the user arrived at the first point 501 as the arrival time, and sends a history registration request including the facial image, the arrival time, and the position information of the first point 501 to the schedule management apparatus 300 . Send to

The display control unit 163 controls the input/output unit 150 to display a product order screen, a user information registration screen, a schedule registration screen, etc. when accessing the electronic commerce server 400 . The display control unit 163 also controls the input/output unit 150 to display the estimated arrival time and the changed estimated delivery time received from the schedule management device 300 . The display control unit 163 also controls the input/output unit 150 to display the current estimated delivery time and estimated arrival time received from the schedule management device 300 .

If the authentication terminal 500 is not installed at the second location 502, the user terminal 100-2 may transmit an authentication request to the schedule management device 300. In that case, the authentication request may include the user's face image, terminal location information (GPS information, etc.) of the user terminal 100-2, and time information. Alternatively, the authentication request may include the above-described other personal identification information, the terminal ID of the user terminal 100-2, etc. instead of the user's face image. When the scheduled delivery time is adjusted in schedule management device 300 in response to the authentication request, display control unit 163 of user terminal 100-2 causes input/output unit 150 to display the estimated arrival time, the scheduled delivery time, and the like. may

Returning to FIG. 3, the description continues.
The authentication terminal 500 is an information processing device installed within a second location 502 . FIG. 5 is a block diagram showing the configuration of an authentication terminal 500 according to the second embodiment. Authentication terminal 500 includes camera 510 , storage unit 520 , memory 530 , communication unit 540 , input/output unit 550 and control unit 560 . Note that the authentication terminal 500 may further include a human sensor (not shown) that detects a moving object such as a person. The camera 510 is an imaging device that performs imaging under the control of the control unit 560 . The storage unit 520 is an example of a storage device such as flash memory. Storage unit 520 stores program 521 . The program 521 is a computer program in which processing including authentication request processing, which will be described later, is implemented. For example, program 521 includes a client application corresponding to schedule management device 300 .

The memory 530 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 560 operates. A communication unit 540 is a communication interface with the network N. FIG. The input/output unit 550 includes a display device (display unit) such as a screen and an input device. The input/output unit 550 is, for example, a touch panel. The control unit 560 is a processor that controls hardware of the authentication terminal 500 . The control unit 560 loads the program 521 from the storage unit 520 into the memory 530 and executes it. Thereby, the control unit 560 implements the functions of the acquisition unit 561 , the authentication request unit 562 and the display control unit 563 .

The acquisition unit 561 acquires the captured image captured by the camera 510 . Note that the acquisition unit 561 may acquire the captured image when a person is detected. The acquisition unit 561 may acquire the current time when the captured image is acquired as the time information. Acquisition unit 561 also acquires the location information of authentication terminal 500 . Note that the location information of the authentication terminal 500 may be stored in the storage unit 520 in advance.

The authentication requesting unit 562 extracts the face area of the person detected from the captured image acquired by the acquiring unit 561 as a face image, and transmits an authentication request including the face image, terminal position information and time information to the schedule management apparatus 300. do. Note that the authentication request may not include the time information. Note that the authentication requesting unit 562 may transmit a face authentication request including a face image to the authentication device 200 and receive a face authentication result from the authentication device 200 . Then, when the face authentication result indicates success, the authentication requesting unit 562 extracts the user ID included in the face authentication result, and sends the stay information including the user ID, terminal location information, and time information to the schedule management device 300. can be sent to

The display control unit 563 may cause the input/output unit 550 to display the authentication result corresponding to the authentication request from the authentication requesting unit 562 . For example, when the scheduled delivery time is adjusted in the schedule management device 300, the display control unit 563 may cause the input/output unit 550 to display the estimated arrival time, the scheduled delivery time, and the like.

Returning to FIG. 3, the description continues.
The authentication device 200 is an information processing device that manages facial feature information of a user and performs face authentication. In addition, in response to a face authentication request received from the outside, the authentication device 200 compares the face image or face feature information included in the request with the face feature information of each user, and requests the result of matching (authentication result). Reply to original.

FIG. 6 is a block diagram showing the configuration of the authentication device 200 according to the second embodiment. The authentication device 200 includes a face information DB (DataBase) 210 , a face detection section 220 , a feature point extraction section 230 , a registration section 240 and an authentication section 250 . The face information DB 210 associates and stores a user ID 211 and face feature information 212 of the user ID. The facial feature information 212 is a set of feature points extracted from the facial image. Note that the authentication device 200 may delete the facial feature information 212 in the facial feature DB 210 in response to a request from a user or the like corresponding to the facial feature information 212 . Alternatively, authentication device 200 may delete facial feature information 212 after a certain period of time has passed since registration.

The face detection unit 220 detects a face area included in a registered image for registering face information and outputs it to the feature point extraction unit 230 . The feature point extraction section 230 extracts feature points from the face area detected by the face detection section 220 and outputs facial feature information to the registration section 240 . Further, feature point extraction section 230 extracts feature points included in the facial image received from schedule management apparatus 300 or the like, and outputs facial feature information to authentication section 250 .

The registration unit 240 newly issues a user ID 211 when registering facial feature information. The registration unit 240 associates the issued user ID 211 with the facial feature information 212 extracted from the registered image and registers them in the facial information DB 210 . Authentication unit 250 performs face authentication using facial feature information 212 . Specifically, the authentication unit 250 collates the facial feature information extracted from the facial image with the facial feature information 212 in the facial information DB 210 . If the verification is successful, the authentication unit 250 identifies the user ID 211 associated with the verified facial feature information 212 . The authenticating unit 250 replies to the requester as a face authentication result indicating whether or not the facial feature information matches. Whether the facial feature information matches or not corresponds to the success or failure of the authentication. Note that matching of facial feature information (matching) means a case where the degree of matching is equal to or greater than a threshold. Also, the face authentication result shall include the specified user ID when the face authentication is successful.

Returning to FIG. 3, the description continues.
Electronic commerce server 400 is a server device that provides an electronic commerce site via network N. FIG. When the electronic commerce server 400 receives an order request for a product from the electronic commerce site, the electronic commerce server 400 performs payment processing for the product and generates product delivery information. Electronic commerce server 400 then transmits the generated delivery information to schedule management device 300 via network N. FIG.

The mobile terminal 100-3 is an information terminal (personnel terminal) that is carried by the delivery company U3 during the delivery business and that transmits and receives data to and from the schedule management device 300 via the network N by wireless communication. The mobile terminal 100-3 is a mobile phone terminal, a smart phone, a tablet terminal, or the like. Specifically, mobile terminal 100-3 receives the delivery instruction from schedule management device 300, identifies the product information, delivery destination, and scheduled delivery time included in the delivery instruction, and displays them on the screen. Further, mobile terminal 100-3 receives from schedule management device 300 the estimated arrival time of the user who is the recipient of the item (package 401) corresponding to the specific delivery ID at the delivery destination, and displays the estimated arrival time on the screen. indicate. Then, when receiving an operation to change the scheduled delivery time from the delivery company U3, the portable terminal 100-3 transmits the changed scheduled delivery time to the schedule management device 300. FIG. It should be noted that, when the mobile terminal 100-3 accepts a change in the scheduled delivery time of the product (package 401) corresponding to the specific delivery ID, it displays that fact on the screen. At this time, the portable terminal 100-3 accepts an approval operation for changing the scheduled delivery time from the delivery company U3, and returns the approval to the schedule management device 300. FIG. Here, the delivery company U3 determines a delivery route and delivers a plurality of packages to a plurality of delivery destinations in accordance with the respective scheduled delivery times. Therefore, the delivery company U3 can appropriately change the delivery route according to changes in the estimated time of arrival at the first location 501 and the estimated delivery time of the user U2 who is the recipient of the package 401 . Further, after the delivery company U3 finishes delivering the package 401 to the first point 501, the mobile terminal 100-3 transmits to the schedule management device 300 a registration request for the delivery completion time input from the delivery company U3. .

Returning to FIG. 3, the description continues.
The schedule management device 300 is an information processing device that performs user information registration processing, delivery control processing, schedule registration processing, scheduled time estimation processing, schedule adjustment processing, and the like. The schedule management device 300 is an example of the schedule management device 1 described above. The schedule management apparatus 300 may be made redundant by a plurality of servers, and each functional block may be realized by a plurality of computers.

FIG. 7 is a block diagram showing the configuration of the schedule management device 300 according to the second embodiment. The schedule management device 300 includes a storage section 310 , a memory 320 , a communication section 330 and a control section 340 . The storage unit 310 is an example of a storage device such as a hard disk or flash memory. Storage unit 310 stores program 311 , user information 312 , delivery information 313 , schedule information 314 and action history 315 . The program 311 is a computer program in which processing including user information registration processing, delivery control processing, schedule registration processing, scheduled time estimation processing, schedule adjustment processing, etc. according to the second embodiment is implemented.

The user information 312 is information in which a user ID 3121, personal information 3122, and terminal information 3123 are associated with each other. User ID 3121 is user identification information. The user ID 3121 is information identically or uniquely corresponding to the user ID 211 associated with the facial feature information 212 managed in the facial information DB 210 of the authentication device 200 . Therefore, it can be said that the user information 312 is information associated with the user identification information for registration via the user ID 3121 . Personal information 3122 is information including the user's name, address, telephone number, and the like. The terminal information 3123 is, as described above, information indicating the notification destination of the user terminal.

The delivery information 313 is information in which a delivery ID 3131, product information 3132, delivery destination 3133, estimated delivery time 3134, delivery company information 3135, and delivery completion time 3136 are associated with each other. Delivery ID3131 is the identification information of delivery information. The product information 3132 is information about products to be delivered. The delivery destination 3133 is information indicating the delivery destination of the product (package) to be delivered. The delivery destination 3133 is information including, for example, the address of the delivery destination, location information such as postal code and address, telephone number, and the like. The scheduled delivery time 3134 is the scheduled delivery time period of the product to be delivered (a set of the earliest and latest scheduled delivery times). The delivery company information 3135 is information about the delivery company. The delivery completion time 3136 is the time when the delivery was actually completed. Delivery completion time 3136 is information included in the registration request from portable terminal 100-3.

The schedule information 314 is information in which the user ID 3141, the location information 3142, and the scheduled stay time period 3143 are associated with each other. The user ID 3141 is information corresponding to the user ID 3121 described above. The location information 3142 is location information indicating the planned place of stay included in the above-described schedule registration request. The planned stay time zone 3143 is the planned stay time zone included in the above-described schedule registration request.

The action history 315 is information in which a user ID 3151, position information 3152, and time information 3153 are associated with each other. The user ID 3151 is information corresponding to the user ID 3121 described above. The location information 3152 is the location information included in the authentication request from the authentication terminal 500 and the location information of the user terminal 100 . The location information 3152 indicates a history of location information of locations where the user actually stayed. The time information 3153 is the time information included in the authentication request from the authentication terminal 500, the time when the authentication request is received, the time when the authentication is successful, or the like. Therefore, the action history 315 includes a history of user IDs of successfully authenticated users, authentication locations, and authentication dates and times. Also, the action history 315 includes a history of stay information for the user corresponding to the user ID 3151 . Also, the action history 315 includes a history of arrival times when the user corresponding to the user ID 3151 actually arrived at the first point.

The memory 320 is a volatile storage device such as RAM, and is a storage area for temporarily holding information when the control unit 340 operates. A communication unit 330 is a communication interface with the network N. FIG.

The control unit 340 is a processor that controls each component of the schedule management device 300, that is, a control device. The control unit 340 loads the program 311 from the storage unit 310 into the memory 320 and executes the program 311 . Thereby, the control unit 340 implements the functions of the registration unit 341 , the delivery control unit 342 , the acquisition unit 343 , the authentication control unit 344 , the identification unit 345 , the estimation unit 346 and the determination unit 347 .

The registration unit 341 is an example of the registration unit 11 described above. The registration unit 341 performs at least user information registration processing and schedule registration processing. The registration unit 341 registers the user information 312 based on the user registration request received from the user terminal 100 . Specifically, the registration unit 341 transmits a face information registration request to the authentication device 200 for the face image included in the user registration request, and acquires the user ID as a registration result. The registration unit 341 registers in the storage unit 310 the user information 312 in which the acquired user ID 3121 , the personal information 3122 included in the user registration request, and the terminal information 3123 are associated with each other.

Also, the registration unit 341 registers the schedule information 314 based on the schedule registration request received from the user terminal 100 . Specifically, the registration unit 341 stores the user ID 3141 when the face authentication controlled by the authentication control unit 344 in response to the schedule registration request is successful, the location information 3142 and the scheduled stay time period 3143 included in the schedule registration request. is registered in the storage unit 310 in the schedule information 314 associated with

Also, the registration unit 341 registers the action history 315 when the face authentication controlled by the authentication control unit 344 in response to the authentication request received from the authentication terminal 500 is successful. Specifically, the registration unit 341 registers in the storage unit 310 the action history 315 in which the user ID 3151 at the time of successful face authentication, the position information 3152 included in the authentication request, and the time information 3153 are associated with each other. Note that the registration unit 341 may use the time when the authentication request is received or the time when the authentication succeeds as the time information 3153 . Further, the registration unit 341 registers the action history 315 when the face authentication controlled by the authentication control unit 344 in response to the history registration request received from the user terminal 100 is successful. For example, the registration unit 341 registers the user ID 3151 when the face authentication is successful, the location information 3152 of the first point 501 included in the history registration request, and the actual arrival time at the first point 501 (time information 3153). is registered in the storage unit 310 as an action history 315 associated with .

The delivery control unit 342 is an example of the notification unit 14 described above. The delivery control unit 342 performs at least delivery control processing and schedule adjustment processing. Delivery control unit 342 registers delivery information 313 received from electronic commerce server 400 in storage unit 310 . The delivery control unit 342 identifies the mobile terminal 100-3 of the delivery company U3 based on the delivery destination 3133 and the delivery company information 3135 of the registered delivery information 313. FIG. Then, delivery control unit 342 transmits a delivery instruction including delivery ID 3131, product information 3132, delivery destination 3133, and scheduled delivery time 3134 of registered delivery information 313 to specified mobile terminal 100-3.

Further, when the estimated time of arrival of the user U2 at the first point 501 estimated by the estimation unit 346, which will be described later, is a predetermined time or more later than the start time of the scheduled stay time period, the delivery control unit 342 transports the package 401. The estimated arrival time is transmitted to the mobile terminal 100-3 of the delivery company U3. Then, when the estimated delivery time is changed in mobile terminal 100-3 according to the estimated arrival time, delivery control unit 342 receives the changed estimated delivery time from mobile terminal 100-3. At this time, the delivery control unit 342 specifies the delivery destination 3133 of the delivery ID to which the parcel 401 corresponds based on the delivery information 313, and includes the location information 3142 corresponding to the specified delivery destination from the schedule information 314. Identify information. Then, the delivery control unit 342 identifies, from the user information 312, the terminal information 3123 (user terminal 100) corresponding to the user ID 3141 (3121) of the identified schedule information. Then, the delivery control unit 342 transmits the estimated arrival time and the changed estimated delivery time to the specified user terminal 100 .

Alternatively, if the estimated arrival time is a predetermined time or more after the start time of the scheduled stay period, the delivery control unit 342 identifies the delivery destination 3133 of the delivery ID to which the parcel 401 corresponds, based on the delivery information 313 . Then, the delivery control unit 342 identifies schedule information including the position information 3142 corresponding to the identified delivery destination from the schedule information 314 . The delivery control unit 342 may specify the terminal information 3123 corresponding to the user ID 3141 (3121) of the specified schedule information from the user information 312 . The delivery control unit 342 then transmits the current estimated delivery time 3134 and estimated arrival time of the corresponding delivery ID to the specified user terminal 100 . After that, when the user wishes to change the estimated delivery time in the user terminal 100 according to the estimated arrival time, the delivery control unit 342 receives the requested change of the estimated delivery time from the user terminal 100 . At this time, delivery control unit 342 transmits the received scheduled delivery time to portable terminal 100-3. When the delivery control unit 342 receives the approval of the change of the estimated delivery time from the portable terminal 100-3, it transmits a change notification of the estimated delivery time to the user terminal 100. FIG. Note that, when the scheduled delivery time is adjusted (changed) by the schedule adjustment process described above, the delivery control unit 342 may transmit the estimated arrival time and the scheduled delivery time to the authentication terminal 500 that is the source of the authentication request.

The acquisition unit 343 is an example of the acquisition unit 12 described above. The acquisition unit 343 receives (acquires) an authentication request from the authentication terminal 500 . The authentication request includes the user's face image, the terminal location information of the authentication terminal 500, and the time information, as described above. That is, when the biometric authentication of the user U2 performed based on the photographed image of the user U2 at the second point 502 is successful, the acquisition unit 343 obtains the location information of the second point 502, the authentication time, and the user U2. is obtained as information during stay. Specifically, when authentication by the authentication control unit 344 in response to the received authentication request is successful, the acquisition unit 343 acquires the successfully authenticated user ID, terminal position information and time information included in the received authentication request. are acquired as information during their stay.

As described above, the authentication terminal 500 may directly request the authentication device 200 to perform face authentication. In that case, when the authentication terminal 500 installed at the second point 502 has successfully authenticated the user U2, the acquisition unit 343 obtains the location information of the second point 502, the authentication time, and the identification information of the user U2 (user ID ) may be acquired as information during stay. In other words, the acquisition unit 343 may acquire, from the authentication terminal 500, the successfully authenticated user ID, the terminal location information, and the time information as the stay information. Further, when the authentication terminal 500 is not installed at the second point 502, the user terminal 100-2 may send an authentication request to the schedule management device 300 or the authentication device 200 instead of the authentication terminal 500. good. In that case, the authentication request may include the user's face image, terminal location information (GPS information, etc.) of the user terminal 100-2, and time information. Alternatively, the authentication request may include the above-described other personal identification information, the terminal ID of the user terminal 100-2, etc. instead of the user's face image.

The authentication control unit 344 controls face authentication, which is an example of biometric authentication, as personal identification authentication. However, the authentication control unit 344 may control other biometric authentication or other personal identification authentication. The authentication control unit 344 controls face authentication for face images included in scheduled registration requests or authentication requests. In other words, the authentication control unit 344 controls authentication using personal identification information for registration and authentication. Specifically, authentication control unit 344 transmits a face authentication request including a face image to authentication device 200 and receives a face authentication result from authentication device 200 . Note that the authentication control unit 344 may detect the user's face area from the face image and include the image of the face area in the face authentication request. Alternatively, the authentication control unit 344 may extract facial feature information from the face area and include the facial feature information in the face authentication request.

The identifying unit 345 identifies the user ID included in the face authentication result when the face authentication result indicates success. The identifying unit 345 identifies the home address (location information) from the personal information 3122 associated with the identified user ID 3121 from the user information 312 . Note that home is an example of a delivery destination, and the specifying unit 345 specifies at least position information that can be a delivery destination. Further, the identifying unit 345 identifies, from the schedule information 314 , the scheduled stay time period 3143 associated with the identified user ID 3141 and the identified location information 3142 of the delivery destination. Further, the specifying unit 345 specifies, from the delivery information 313, the estimated delivery time 3134 associated with the delivery destination 3133 corresponding to the specified location information of the delivery destination.

The estimation unit 346 is an example of the estimation unit 13 described above. The estimation unit 346 estimates the estimated arrival time at which the user U2 arrives at the first point 501 based on the schedule information 314 and the information during stay. Specifically, the estimation unit 346 determines the first Estimates the estimated time of arrival at the point 501 of . That is, the estimation unit 346 estimates the estimated time of arrival at the first point 501 when the user U2 moves from the second point 502 to the first point 501 . Note that the estimating unit 346 may estimate the estimated arrival time by taking into consideration the means of transportation from the second point 502 to the first point 501 . For example, when the second point 502 is a bus stop, the estimating unit 346 calculates the estimated travel time by bus from the second point 502 to the nearest bus stop to the first point 501 and the time from the nearest bus stop to the first point. The estimated time of arrival is estimated by considering the estimated time of travel on foot to 501 . In addition, the estimation unit 346 may estimate the estimated arrival time by taking into account the user's stay information history. In addition, the estimation unit 346 may estimate the estimated arrival time by further considering the history of the user's arrival time at the first point 501 . In addition, the estimation unit 346 may estimate the estimated arrival time by further considering the history of the delivery completion time to the first location 501 of the user. For example, the estimating unit 346 calculates the estimated arrival time by taking into account the time information 3153 of the second point 502 and the first point 501, respectively, of the action history 315 regarding the user U2 whose face authentication has succeeded. presume. At this time, the estimating unit 346 may analyze the behavior history 315 regarding the user U2 whose face authentication has succeeded, and estimate the estimated arrival time from the analysis result of the behavior pattern of the user U2. In this way, the estimated arrival time can be estimated more accurately by using the past action results and arrival time results.

The determination unit 347 determines whether the face authentication result indicates success. Further, the determination unit 347 determines whether or not the estimated arrival time is later than the start time of the scheduled stay period by a predetermined time or longer. Here, the predetermined time is, for example, 15 minutes, but is not limited to this.

FIG. 8 is a flowchart showing the flow of user information registration processing according to the second embodiment. Here, it is assumed that user U1 registers user information, but user U2 also registers user information. First, the user terminal 100-1 receives the face image and personal information (address, etc.) of the user U1 input by the user U1, and acquires the terminal information of the user terminal 100-1 itself. Then, user terminal 100-1 transmits a user registration request including the face image, personal information, and terminal information of user U1 to schedule management apparatus 300 via network N. FIG. In response, the registration unit 341 of the schedule management device 300 receives the user registration request from the user terminal 100-1 via the network N (S301).

Next, the registration unit 341 acquires the face image of the user U1 from the received user registration request, and transmits the face information registration request including the face image to the authentication device 200 via the network N (S302). In response to this, the authentication device 200 performs face information registration processing.

FIG. 9 is a flow chart showing the flow of face information registration processing by the authentication device according to the second embodiment. First, the authentication device 200 receives a face information registration request (S201). For example, the authentication device 200 receives a face information registration request via the network N from the schedule management device 300 . Next, the face detection unit 220 detects a face area from the face image included in the face information registration request (S202). Then, the feature point extraction unit 230 extracts feature points (facial feature information) from the face area detected in step S202 (S203). Then, the registration unit 240 issues the user ID 211 (S204). Then, the registration unit 240 associates the extracted facial feature information 212 with the issued user ID 211 and registers them in the facial information DB 210 (S205). After that, the registration unit 240 returns the issued user ID 211 to the request source (for example, the schedule management device 300) (S206). Note that the authentication device 200 may perform face information registration processing in response to a face information registration request received from an arbitrary information registration terminal. For example, the information registration terminal is an information processing device such as a personal computer, a smart phone, or a tablet terminal. Also, the information registration terminal may be the user terminal 100 .

Return to Fig. 8 and continue the explanation. The registration unit 341 of the schedule management device 300 acquires the issued user ID from the authentication device 200 via the network N (S303). Then, the registration unit 341 registers the user information 312 associated with the user ID 3121 acquired in step S303, the personal information 3122 (address, etc.) included in the user registration request received in step S301, and the terminal information 3123 (S304). .

FIG. 10 is a sequence diagram showing the flow of product order processing according to the second embodiment. Here, it is assumed that user U1 purchases a product on the electronic commerce site of electronic commerce server 400 and the first point 501 is the delivery destination. Note that the user U2 may purchase the product on the electronic commerce site. It is also assumed that both users U1 and U2 can be recipients of packages at the first location 501. FIG.

First, the user terminal 100-1 accesses the e-commerce server 400 via the network N and displays the product purchase screen of the e-commerce site. The user terminal 100-1 accepts the product to be purchased, the delivery address, payment information, etc. input by the user U1. At this time, the user terminal 100-1 may accept designation of the scheduled delivery time (delivery time desired by the user) from the user U1. Then, the user terminal 100-1 transmits an order request including product information, delivery destination and payment information (and estimated delivery time) to the electronic commerce server 400 via the network N (S311). In response, the electronic commerce server 400 receives an order request for the product from the user terminal 100-1 via the network N, and uses the payment information included in the order request to perform payment processing for the product (S312). Then, the electronic commerce server 400 generates delivery information for the product for which payment has been completed (S313). Specifically, the electronic commerce server 400 issues a delivery ID. Then, the electronic commerce server 400 generates delivery information including at least the delivery ID, product information, and delivery destination. The electronic commercial transaction server 400 may determine the delivery company and the scheduled delivery time from the delivery destination. In that case, the electronic commerce server 400 further includes the estimated delivery time and the delivery company in the delivery information. Electronic commerce server 400 then transmits the generated delivery information to schedule management device 300 via network N (S314).

The delivery control unit 342 of the schedule management device 300 receives delivery information from the electronic commerce server 400 via the network N. Then, if necessary, the delivery control unit 342 determines the delivery company and scheduled delivery time from the delivery destination, and arranges delivery of the product. Then, the delivery control unit 342 registers the delivery information 313 including the determined delivery company and the scheduled delivery time in the received delivery information in the storage unit 310 (S315). After that, the delivery control unit 342 identifies the portable terminal 100-3 of the delivery company U3 corresponding to the delivery company information 3135 included in the delivery information 313. FIG. In addition, the delivery control unit 342 generates a delivery instruction including the delivery ID 3131, product information 3132, delivery destination 3133, and scheduled delivery time 3134 included in the delivery information 313. FIG. The delivery control unit 342 then transmits the generated delivery instruction to the mobile terminal 100-3 via the network N (S316). The portable terminal 100-3 prepares the package 401 according to the received delivery instruction, and delivers the package 401 to the first location 501, which is the delivery destination specified in the delivery instruction, at the specified scheduled delivery time. Prepare as follows.

FIG. 11 is a flowchart showing the flow of schedule registration processing according to the second embodiment. Here, it is assumed that the user U1 registers the schedule information regarding the scheduled stay time zone of the first spot 501, but the user U2 similarly registers the schedule information related to the scheduled stay time zone of the first spot 501. and Alternatively, the scheduled stay time zone of the first point 501 may include not only the user U1 but also the user U2's scheduled stay time zone.

First, the user terminal 100-1 accepts the first point 501 and the planned stay period of the user U1 at the first point 501 input by the user U1. Also, the user terminal 100-1 acquires the face image of the user U1. Then, the user terminal 100-1 transmits to the schedule management apparatus 300 via the network N a schedule registration request including the place of stay (first point 501), the scheduled time of stay, and the face image of the user U1. In response, the registration unit 341 of the schedule management device 300 receives the schedule registration request from the user terminal 100-1 via the network N (S321).

Then, the authentication control unit 344 transmits a face authentication request including the face image included in the scheduled registration request to the authentication device 200 via the network N (S322). In response to this, the authentication device 200 performs face authentication processing.

FIG. 12 is a flow chart showing the flow of face authentication processing by the authentication device according to the second embodiment. First, the authentication device 200 receives a face authentication request from the schedule management device 300 via the network N (S211). Note that the authentication device 200 may receive a face authentication request from the user terminal 100, the authentication terminal 500, or the like. Next, the authentication device 200 extracts facial feature information from the face image included in the face authentication request, similarly to steps S202 and S203 described above. Then, the authentication unit 250 of the authentication device 200 collates the facial feature information extracted from the face image included in the face authentication request with the facial feature information 212 of the face information DB 210 (S212), and calculates the matching degree. Then, the authentication unit 250 determines whether or not the degree of matching is equal to or greater than the threshold (S213). If the facial feature information matches, that is, if the degree of matching of the facial feature information is equal to or greater than the threshold, the authentication unit 250 identifies the user ID 211 associated with the facial feature information 212 (S214). Then, the authentication unit 250 returns the result of the face authentication including the result of the successful face authentication and the specified user ID 211 to the schedule management device 300 via the network N (S215). If the degree of matching is less than the threshold in step S213, the authentication unit 250 returns the result of face authentication including failure of the face authentication to the schedule management device 300 via the network N (S216).

Returning to FIG. 11, the description is continued.
The authentication control unit 344 of the schedule management device 300 receives the face authentication result from the authentication device 200 via the network N (S323). The determination unit 347 determines whether or not the face authentication result indicates success (S324). When the face authentication result indicates success, the specifying unit 345 specifies the user ID included in the face authentication result (S325). Then, the registration unit 341 registers, in the storage unit 310, the schedule information 314 in which the user ID 3141 at the time of successful face authentication is associated with the location information 3142 of the place of stay and the scheduled time of stay 3143 included in the schedule registration request. (S326). After that, the registration unit 341 replies to the user terminal 100-1 via the network N that the registration has been completed (S327).

It should be noted that if the face authentication result indicates failure in step S324, the registration unit 341 replies to the user terminal 100-1 via the network N to the effect that registration is not possible (S328). Note that the schedule registration request received in step S321 may include other personal identification information described above instead of the face image. In that case, instead of steps S322 to S324, the authentication control unit 344 performs authentication processing according to the identification information, and if the authentication succeeds, the identification unit 345 identifies the user ID.

FIG. 13 is a flowchart showing the flow of scheduled time estimation processing according to the second embodiment. As a premise, the personal information of the user U2 includes the home address (position information) of the first point 501, and the delivery company U3 delivers the package 401 to the first point 501 (the home of the user U2) for a predetermined delivery. Assume that delivery is scheduled at the scheduled time. Further, it is assumed that the scheduled stay time period at the first point 501 has been registered as the schedule information 314 of the user U2.

Then, it is assumed that the user U2 has visited the second point 502 while carrying the user terminal 100-2. Then, the authentication terminal 500 acquires the photographed image of the user U2 and extracts the face image from the photographed image. Authentication terminal 500 then transmits an authentication request including the extracted face image, terminal location information of authentication terminal 500 and current time information to schedule management apparatus 300 via network N. FIG. In response, the acquisition unit 343 of the schedule management device 300 receives the authentication request from the authentication terminal 500 via the network N (S331).

Then, the authentication control unit 344 transmits a face authentication request including the face image included in the authentication request to the authentication device 200 via the network N (S332). In response to this, the authentication device 200 performs face authentication processing in the same manner as in FIG. 12 described above. After that, the authentication control unit 344 receives the face authentication result from the authentication device 200 via the network N (S333). The determination unit 347 determines whether or not the face authentication result indicates success (S334). When the face authentication result indicates success, the specifying unit 345 specifies the user ID included in the face authentication result (S335). If the face authentication result indicates failure in step S334, the registration unit 341 returns the authentication failure to the authentication terminal 500 via the network N (S340). Note that when the user terminal 100-2 transmits the authentication request, the authentication request received in step S331 includes the above-described other identification information and the terminal ID of the user terminal 100-2 instead of the face image. Also good. In this case, the authentication request includes the terminal location information (GPS information, etc.) of the user terminal 100-2. Then, instead of steps S332 to S335, the authentication control unit 344 performs authentication processing according to the identification information or the like, and if the authentication succeeds, the specifying unit 345 specifies the user ID.

After step S335, the identifying unit 345 identifies the home position information of the user U2, the scheduled stay period, and the scheduled delivery time of the package 401 (S336). Specifically, the specifying unit 345 specifies the home address (location information) from the personal information 3122 associated with the specified user ID 3121 (user U2) from the user information 312 . Then, the specifying unit 345 specifies, from the schedule information 314, the scheduled stay time period 3143 associated with the specified user ID 3141 (user U2) and the specified delivery destination location information 3142 (home address). Further, the specifying unit 345 specifies, from the delivery information 313, the estimated delivery time 3134 associated with the delivery destination 3133 corresponding to the specified delivery destination location information (user U2's home).

Then, the estimation unit 346 estimates the estimated time of arrival at the delivery destination based on the current location of user U2 (S337). Specifically, the estimation unit 346 estimates the estimated time of arrival at the first point 501 when the user U2 moves from the second point 502 to the first point 501 . Note that the estimating unit 346 may estimate the estimated arrival time in consideration of the means of transportation of the user U2.

Then, the determination unit 347 determines whether or not the estimated arrival time is later than the start time of the scheduled stay period by a predetermined time or more (S338). If the estimated arrival time is less than the predetermined time after the start time (NO in S338), the process ends. For example, if the estimated arrival time is before the start time of the scheduled stay time zone or after about 10 minutes, there is a high probability that the user U2 will be able to return home and receive the package 401, so the scheduled delivery time is not changed. do not have.

On the other hand, if the estimated arrival time is later than the start time by a predetermined time or more (YES in S338), the delivery control unit 342 performs schedule adjustment processing (S339).

FIG. 14 is a sequence diagram showing the flow of schedule adjustment processing according to the second embodiment. First, if the estimated time of arrival is later than the start time of the scheduled stay period by a predetermined time or longer, the delivery control unit 342 identifies the mobile terminal 100-3 of the delivery company U3 (S341). Specifically, delivery control unit 342 identifies portable terminal 100-3 based on delivery company information 3135 of delivery information 313 with delivery destination 3133 being the home of user U2 whose face authentication has succeeded. In addition, the delivery control unit 342 also identifies the delivery ID of the delivery information 313 with the delivery destination 3133 being the home of the user U2 whose face authentication has succeeded.

Then, the delivery control unit 342 transmits the estimated arrival time and the delivery ID to the mobile terminal 100-3 via the network N (S342). It is assumed that the portable terminal 100-3 can acquire the delivery destination, the current scheduled delivery time, and the like using the received delivery ID as a clue. Alternatively, the delivery control unit 342 may specify record contents (product information, delivery destination, scheduled delivery time, etc.) of the delivery information corresponding to the specified delivery ID. In that case, the delivery control unit 342 transmits the estimated arrival time and the record contents of the specified delivery information to the mobile terminal 100-3. In response, the portable terminal 100-3 displays the delivery destination corresponding to the received delivery ID, the current scheduled delivery time, the estimated arrival time, etc. on the screen (S343). Then, the mobile terminal 100-3 receives from the delivery company U3, if necessary, a change in the estimated delivery time that takes into account the estimated arrival time (S344). Portable terminal 100-3 then transmits the changed scheduled delivery time to schedule management apparatus 300 via network N (S345).

In response, the delivery control unit 342 receives the changed scheduled delivery time from the mobile terminal 100-3 via the network N. Then, the delivery control unit 342 specifies the schedule information corresponding to the location information of the delivery destination of the corresponding delivery ID, and specifies the terminal information corresponding to the user ID of the specified schedule information (S346). Here, the delivery control unit 342 identifies the user terminal 100-2 of the user U2. The delivery control unit 342 then transmits the estimated arrival time and the changed estimated delivery time to the user terminal 100-2 via the network N (S347).

In response, the user terminal 100-2 receives the estimated arrival time and the changed estimated delivery time from the schedule management device 300 via the network N. Then, the user terminal 100-2 displays a notification content display screen including the received estimated arrival time and the changed estimated delivery time (S348).

For example, the delivery company U3 initially delivers the parcel 401 to the first point 501 at the scheduled delivery time of "15:00 to 18:00", and the estimated arrival time of the user U2 at the first point 501 is " 17:30". In this case, the mobile terminal 100-3 displays a screen requesting consideration of the estimated delivery time based on the received estimated arrival time and delivery ID in step S343. FIG. 15 is an example of the examination request screen 101 for the estimated delivery time displayed on the mobile terminal 100-3 according to the second embodiment. The estimated delivery time review request screen 101 includes an estimated delivery time display field 102 , an estimated arrival time display field 103 , an estimated delivery time change selection field 104 , a no change button 105 and a change button 106 . The estimated delivery time display field 102 is a display field for the current estimated delivery time corresponding to the delivery ID. Here, it is indicated that the initial scheduled delivery time for the delivery company U3 to deliver the package 401 to the first location 501 is "15:00 to 18:00". The estimated arrival time display field 103 is a display field for the estimated arrival time estimated by the schedule management device 300 . It indicates that the estimated time when the user U2 will return to the first point 501 is estimated to be "17:30". The change selection column 104 of the estimated delivery time is a column for receiving and displaying selection operation of the time after the change of the estimated delivery time by the delivery company U3. Here, it is shown that "18:00 to 20:00" has been selected by the delivery company U3 as the time after the change of the scheduled delivery time. The no change button 105 is a button for accepting approval of the current scheduled delivery time by the delivery company U3. When no change button 105 is pressed, portable terminal 100-3 indicates that the current scheduled delivery time will not be changed (approved), or changes the scheduled delivery time displayed in scheduled delivery time display field 102 to the scheduled delivery time. Send to the management device 300 . A change button 106 is a button for accepting a change in the estimated delivery time. When change button 106 is pressed, portable terminal 100 - 3 transmits the changed estimated delivery time displayed (selected) in change selection column 104 of estimated delivery time to schedule management device 300 . Here, it is assumed that the delivery company U3 selects the changed scheduled delivery time "18:00 to 20:00" for the portable terminal 100-3 and presses the change button . After that, the user terminal 100-2 receives notification of the estimated arrival time and the changed estimated delivery time via the schedule management device 300, and displays a notification content display screen.

FIG. 16 is a diagram showing an example of the estimated delivery time notification screen 111 (notification content display screen) by the user terminal 100-2 according to the second embodiment. The notification content display screen 111 includes an estimated arrival time display field 112 and an estimated delivery time display field 113 . The estimated arrival time display field 112 is the same as the estimated arrival time display field 103 described above. Here, it is shown that the estimated time at which user U2 will return to the first point 501 is estimated to be "17:30". The scheduled delivery time display column 113 is a column for displaying the time approved or changed by the delivery company U3 as the scheduled delivery time of the parcel 401 to the first location 501 . Here, it is shown that the scheduled delivery time of the package 401 has been changed to "18:00 to 20:00" by the delivery company U3. Thereby, the user U2 can grasp the change in the scheduled delivery time of the package 401 without changing the scheduled delivery time by himself/herself.

Note that the notification content display screen 111 in FIG. 16 may include an approval button. The approval button is a button for accepting that the user U2 approves the time displayed in the estimated delivery time display field 113 . Therefore, when the user U2 presses the approval button, the user terminal 100-2 transmits to the schedule management device 300 via the network N that the change in the scheduled delivery time has been approved by the user U2 who is the recipient. do. Upon receiving approval of the estimated delivery time from user terminal 100-2, schedule management device 300 notifies mobile terminal 100-3 of the estimated arrival time and the approved estimated delivery time.

As described above, the schedule management apparatus 300 according to the second embodiment can estimate the arrival time of the recipient at the delivery destination by using the information that the recipient of the package is staying at a location different from the delivery destination. It is possible to support the adjustment of the estimated delivery time considering the estimated time. Therefore, the delivery company U3 can reduce the probability of redelivery, and the user U2 can receive the parcel at an appropriate timing according to the actual behavior of the user U2.

In addition, in the schedule adjustment processing according to the second embodiment, the user who is the recipient of the package may confirm the estimated arrival time at the delivery destination in advance and change the estimated delivery time. FIG. 17 is a sequence diagram showing the flow of schedule adjustment processing according to the modification of the second embodiment. First, when the estimated time of arrival is after the start time of the scheduled stay period by a predetermined time or more, the delivery control unit 342 identifies the user terminal of the user U2 (S351). Specifically, the delivery control unit 342 identifies schedule information corresponding to the location information (home address) of the delivery destination of the corresponding delivery ID, and terminal information (user terminal) corresponding to the user ID of the identified schedule information. 100-2) may be specified. Then, the delivery control unit 342 transmits the current scheduled delivery time and estimated arrival time of the corresponding delivery ID to the user terminal 100-2 via the network N (S352).

In response, the user terminal 100-2 receives the current estimated delivery time and estimated arrival time from the schedule management device 300 via the network N. Then, the user terminal 100-2 displays a notification content display screen including the received current estimated delivery time and estimated arrival time (S353).

FIG. 18 is a diagram showing an example of the estimated delivery time review request screen 101a (notification content display screen) displayed on the user terminal 100-2 according to the second embodiment. The estimated delivery time consideration request screen 101a has the same configuration as that of FIG. 15 described above, so detailed description thereof will be omitted. However, since the estimated delivery time examination request screen 101a is displayed on the user terminal 100-2, it is operated by the user U2. Here, the scheduled delivery time display column 102 indicates that the initial scheduled delivery time for the delivery company U3 to deliver the package 401 to the first location 501 is "15:00 to 18:00". The estimated arrival time display column 103 indicates that the estimated time when the user U2 will return to the first point 501 is estimated to be "17:30". The change selection column 104 of the estimated delivery time is a column for receiving and displaying selection operation of the change time of the estimated delivery time desired by the user U2. Here, it is shown that the user U2 has selected "18:00 to 20:00" as the scheduled delivery time. The no change button 105 is a button for accepting user U2's approval of the current scheduled delivery time. When the no change button 105 is pressed, the user terminal 100-2 indicates that the current scheduled delivery time will not be changed (approved), or changes the scheduled delivery time displayed in the scheduled delivery time display field 102 to the scheduled delivery time. Send to the management device 300 . When the change button 106 is pressed, the user terminal 100 - 2 transmits the scheduled delivery time displayed (selected) in the change selection column 104 of the scheduled delivery time to the schedule management device 300 .

In FIG. 18, if the estimated delivery time is changed (because there is time to spare), a message may be displayed that recommends the user to purchase additional products that can be delivered. Specifically, if the estimated arrival time is later than the start time of the scheduled stay time zone by a predetermined time or more, the schedule management device 300 accepts an additional order at this time to accept the product ( Additional order candidate). For example, the schedule management device 300 changes the scheduled delivery time based on the purchase history of the user, the inventory status at the store, and the loading status of the delivery vehicle at the store. may be selected. At this time, the schedule management device 300 may inquire of the electronic commerce server 400 about additional order candidate products. Then, in step S352, the schedule management device 300 transmits additional order candidates to the user terminal 100-2 in addition to the current scheduled delivery time and estimated arrival time. The user terminal 100-2 displays the received message recommending the additional order candidate, an additional order button, and the like. The message that recommends the additional order candidate is, for example, "By changing the estimated delivery time to 18:00 to 20:00, you can additionally deliver (purchase) this product. How about that?" . Also, when the additional order button is pressed, user terminal 100-2 transmits an order request for additional order candidates to electronic commerce server 400. FIG. As a result, product order processing is performed for the additional order candidate product, and the delivery company U3 can load the product together with the package 401 onto the delivery vehicle and deliver the product at the changed scheduled delivery time.

Returning to Fig. 17, the explanation continues. The user terminal 100-2 accepts the change of the estimated delivery time by the user U2's selection operation (S354). When the user U2 presses the change button 106, the user terminal 100-2 transmits the changed scheduled delivery time to the schedule management apparatus 300 via the network N (S355).

In response, the delivery control unit 342 of the schedule management device 300 receives the changed scheduled delivery time from the user terminal 100-2. Then, the delivery control unit 342 identifies the portable terminal 100-3 of the delivery company U3, as in FIG. 14 described above (S341). In addition, the delivery control unit 342 also identifies the delivery ID of the delivery information 313 with the delivery destination 3133 being the home of the user U2 whose face authentication has succeeded. Then, the delivery control unit 342 transmits the received scheduled delivery time and specified delivery ID to the mobile terminal 100-3 via the network N (S356). In response, portable terminal 100-3 displays the delivery destination corresponding to the received delivery ID, the initial scheduled delivery time, the estimated arrival time, and the scheduled delivery time on the screen. Then, the mobile terminal 100-3 accepts an approval operation for the changed scheduled delivery time from the delivery company U3, and transmits the approval to the schedule management device 300 via the network N (S357). Note that the mobile terminal 100-3 accepts the changed estimated delivery time from the delivery company U3 as necessary, taking into consideration the estimated arrival time, and transmits the changed estimated delivery time via the network N to the schedule management device. 300. Alternatively, if there is no approval from the delivery company U3, the user U2 may change the scheduled delivery time again.

In response, the delivery control unit 342 receives approval of the scheduled delivery time from the mobile terminal 100-3 via the network N. Then, the delivery control unit 342 determines the approved scheduled delivery time as the revised scheduled delivery time. The delivery control unit 342 then transmits a change notification of the scheduled delivery time to the user terminal 100-2 via the network N (S358). In response, the user terminal 100-2 displays the notification content display screen including the received estimated arrival time and the changed estimated delivery time, as in FIG. 14 described above (S346).

<Embodiment 3>
Embodiment 3 is a modification of Embodiment 2 described above. In the third embodiment, the first point is the store, hotel, restaurant, etc. that the user has booked to visit. Then, when the estimated time of arrival at the first point differs from the reservation time by a certain range or more while the user is staying at the second point, the reception side of the first point is notified to that effect.

FIG. 19 is a block diagram showing the overall configuration of the schedule management system 1000a according to the third embodiment. In the schedule management system 1000a, the schedule management device 300a is changed from that of FIG. 3 described above, and the shop terminal 100-4 and the store clerk U4 are present in the first point 501a (restaurant). Note that other configurations of the schedule management system 1000a are the same as those in FIG. 3, so the differences will be mainly described below, and illustration and description of overlapping configurations will be omitted.

The store clerk U4 confirms and operates the display of the store terminal 100-4.
The store terminal 100-4 is an information terminal (personnel terminal) installed at the first point 501a and connected to the network N. FIG. The store terminal 100-4 is a mobile phone terminal, smart phone, tablet terminal, personal computer, or the like. The shop terminal 100-4 receives the estimated arrival time of the user who made the reservation to visit the store from the schedule management device 300a, and displays it on the screen. Then, the store terminal 100-4 accepts the approval by the store clerk U4 or the operation to the effect that the reservation time cannot be changed, and returns that effect to the schedule management device 300a. For example, when the estimated arrival time of the user who made a reservation to visit the store is earlier than the original reservation time, the store clerk U4 determines whether or not it is possible to bring forward the preparation of food. If it is determined that the reservation time can be brought forward and accepted, the store clerk U4 performs an approval operation on the store terminal 100-4. The same applies when the estimated arrival time of the user who has made a reservation to come to the store is later than the original reservation time. Note that the store terminal 100-4 registers the visit time in the schedule management device 300 according to the operation of the clerk U4 when the user who made the reservation comes to the store.

FIG. 20 is a block diagram showing the configuration of the schedule management device 300a according to the third embodiment. In the schedule management device 300a, the program 311a, the identification unit 345a, and the determination unit 347a are changed from those shown in FIG. It is what was done.

The program 311a is a computer program in which processes including the schedule adjustment process and the like according to the third embodiment are implemented in addition to the above-described user information registration process, schedule registration process, and scheduled time estimation process. Note that the program 311a may include the delivery control process described above.

The reservation information 316 is information for managing reservations to the first point 501a or the like. The reservation information 316 is information in which a reservation ID 3161, store information 3162, location information 3163, reservation date and time 3164, user ID 3165, and visit time 3166 are associated with each other. The reservation ID 3161 is reservation identification information. Store information 3162 is information about the store to be reserved. The location information 3163 is location information such as the address of the store to be reserved. For example, the location information 3163 is location information of the first point 501a. The reservation date and time 3164 is the date and time when the reservation was made. User ID 3165 is the identification information of the user who made the reservation. User ID 3165 is information corresponding to user ID 3121 described above. The visit time 3166 is the time when the user who made the reservation actually visited the store.

Here, the schedule information 314 according to the third embodiment includes the location information of the reserved store as the location information 3142 and the reservation time of the reserved store as the scheduled stay time zone 3143 . Specifically, the scheduled stay time zone 3143 is a set of the reservation start time (estimated arrival time) and the reservation end time of the first point 501 .

The reservation management unit 342a is an example of the notification unit 14 described above. The reservation management unit 342a performs at least reservation registration processing and schedule adjustment processing. The reservation management unit 342 a registers the reservation information 316 based on the reservation registration request received from the user terminal 100 . Specifically, the reservation management unit 342a issues a reservation ID and identifies the store information and reservation date and time included in the reservation registration request. In addition, the reservation management unit 342a identifies position information corresponding to the store information. Then, the reservation management unit 342a associates the user ID when the face authentication controlled by the authentication control unit 344 in response to the reservation registration request with the store information, the location information, the reservation date and time, and the reservation ID is associated with the reservation management unit 342a. Information 316 is registered in the storage unit 310 .

In addition, the reservation management unit 342a performs schedule adjustment processing with the user terminal 100 using the store terminal 100-4 of the reservation store as the related party terminal.

FIG. 21 is a flowchart showing the flow of reservation registration processing according to the third embodiment. Here, it is assumed that the user U1 registers the reservation for the restaurant at the first point 501a, but the user U2 may register the reservation for the restaurant at the first point 501a.

First, the user terminal 100-1 accepts store information, reservation date and time, and face image of the user U1 for which the user U1 makes a reservation. Send to schedule management device 300 . In response, the reservation management unit 342a of the schedule management device 300 receives the reservation registration request from the user terminal 100-1 via the network N (S411).

Then, the authentication control unit 344 transmits a face authentication request including the face image included in the reservation registration request to the authentication device 200 via the network N (S412). In response to this, the authentication device 200 performs face authentication processing in the same manner as in FIG. 12 described above. After that, the authentication control unit 344 receives the face authentication result from the authentication device 200 via the network N (S413). The determination unit 347a determines whether or not the face authentication result indicates success (S414). When the face authentication result indicates success, the specifying unit 345a specifies the user ID included in the face authentication result (S415). Then, the reservation management unit 342a extracts the store information and reservation date and time included in the reservation registration request. Then, if there is no problem with the store information and the reservation date and time, the reservation management unit 342a issues a reservation ID and specifies position information corresponding to the store information. Then, the reservation management unit 342a registers the schedule information 314 in which the issued reservation ID 3161, the store information 3162, the location information 3163, the reservation date and time 3164, and the specified user ID 3165 are associated with each other in the storage unit 310 (S416). After that, the reservation management unit 342a replies that the reservation is completed to the user terminal 100-1 via the network N (S417). If the face authentication result indicates failure in step S414, the reservation management unit 342a replies to the user terminal 100-1 via the network N to the effect that the reservation is not possible (S418).

FIG. 22 is a flowchart showing the flow of scheduled time estimation processing according to the third embodiment. It is assumed that the users U1 and U2 have already registered the schedule information with the reservation date and time of the restaurant at the first point 501a reserved by themselves as the planned stay time zone.

Therefore, for example, assume that the user U2 visits the second point 502 while carrying the user terminal 100-2. Then, the authentication terminal 500 acquires the photographed image of the user U2 and extracts the face image from the photographed image. Authentication terminal 500 then transmits an authentication request including the extracted face image, terminal location information of authentication terminal 500 and current time information to schedule management apparatus 300 via network N. FIG. In response, the acquisition unit 343 of the schedule management device 300 receives the authentication request from the authentication terminal 500 via the network N (S331). Thereafter, steps S332 to S335 and S340 are performed in the same manner as in FIG. 13 described above.

After step S335, the identifying unit 345a identifies the store location information 3163 and the reservation date and time 3164 associated with the identified user ID in the reservation information 316 (S336a). Then, the estimation unit 346 estimates the estimated time of arrival at the reserved shop based on the current position of the user U2 (S337a).

Then, the determination unit 347a determines whether or not the estimated arrival time is earlier than the start time of the scheduled stay period by a predetermined time or more (S338a). Here, the predetermined time may be 30 minutes, for example. If the estimated arrival time is less than the predetermined time before the start time (NO in S338a), the process ends. For example, if the estimated arrival time is within 30 minutes before the start time of the scheduled stay period, even if the user U2 arrives at the restaurant a little early, it is highly likely that the restaurant will be able to accommodate the reservation date and time. is not performed.

On the other hand, if the estimated arrival time is at least the predetermined time before the start time (YES in S338a), the reservation management unit 342a performs schedule adjustment processing (S339). First, the reservation management unit 342a identifies the store terminal 100-4 of the store clerk U4. Specifically, the reservation management unit 342a identifies, from the reservation information 316, the reservation ID including the user ID for which the face authentication was successful, the shop information, and the reservation date and time. Then, the reservation management unit 342a identifies the store terminal 100-4 corresponding to the identified store information. The reservation management unit 342a then transmits the estimated arrival time and the reservation ID via the network N to the shop terminal 100-4. In response, the store terminal 100-4 displays the reservation information corresponding to the received reservation ID, the original reservation date and time, and the estimated arrival time on the screen.

FIG. 23 is an example of a reservation date and time change approval request screen 101b displayed on the store terminal 100-4 according to the third embodiment. The reservation date and time change approval request screen 101b is obtained by applying the above-described scheduled delivery time review request screen 101 of FIG. 15 to the reservation date and time change approval request, and has the same basic configuration. Specifically, the reservation date/time change approval request screen 101b includes a reservation date/time display field 102b, an estimated arrival time display field 103b, a reservation date/time change selection field 104b, a change prohibition button 105b, and a change approval button 106b. The reservation date and time display field 102b is a display field for the original reservation date and time corresponding to the reservation ID. Here, it is shown that the user U2 has made a reservation at the first point 501a (restaurant) for "19:00 to 21:00". The estimated arrival time display field 103b is a display field for the estimated arrival time estimated by the schedule management device 300a. It indicates that the estimated time at which the user U2 will visit the first point 501a is estimated to be "18:00". The reservation date and time change selection column 104b is a column for receiving and displaying the selection operation of the time after the reservation date and time is changed by the store clerk U4. Here, it indicates that "18:00 to 20:00" has been selected by the clerk U4 as the time after the reservation date and time has been changed. The change-impossible button 105b is a button for accepting that the clerk U4 does not approve the change of the reserved date and time due to the preparation status of the store or the like. When the unchangeable button 105b is pressed, the store terminal 100-4 notifies the schedule management device 300a that the original reservation date and time will not be changed. The change approval button 106b is a button for accepting approval of the reservation date and time by the clerk U4. When the change approval button 106b is pressed, the store terminal 100-4 transmits the changed reservation date and time displayed (selected) in the reservation date and time change selection column 104b to the schedule management device 300a.

Here, the store terminal 100-4 determines whether the store can respond even if the estimated arrival time is earlier than the start time (reservation time) of the reservation date and time, or whether the store can respond even if it is later than the reservation time (or if the reservation is canceled). ) is accepted from the clerk (for the changed reservation date and time). Then, the store terminal 100-4 accepts approval of the changed reservation date and time from the store clerk U4 as necessary, taking into consideration the estimated arrival time, and manages the schedule via the network N for approval of the changed reservation date and time. Send to device 300 . For example, even if the user U2 comes to the store a little earlier than the reservation time, the store clerk U4 approves the changed reservation date and time if the store can handle it. Also, even if the user U2 arrives at the store somewhat later than the reservation time, there is no effect on subsequent customers who made the reservation, and if the store can handle it, the clerk U4 approves the changed reservation date and time. The schedule management device 300 notifies the user terminal 100-2 of the estimated arrival time and the changed reservation date and time in the same manner as in step S346 and subsequent steps of FIG. 14 described above.

FIG. 24 is a diagram showing an example of the changed reservation date and time notification screen 111b (notification content display screen) of the user terminal 100-2 according to the third embodiment. The notification content display screen 111b includes an estimated arrival time display field 112b and a reservation date and time display field 113b. The estimated arrival time display field 112b is the same as the estimated arrival time display field 103b described above. Here, it is shown that the estimated time when the user U2 will visit the first point 501a is estimated to be "18:00". The reservation date and time display column 113b is a column for displaying the changed reservation date and time approved by the store along with the estimated time of visit. Here, it indicates that the reservation date and time for user U2 has been changed to "18:00 to 20:00" by store clerk U4. Thereby, the user U2 can grasp the changed reservation date and time without changing the reservation date and time by himself/herself.

Note that the notification content display screen 111b in FIG. 24 may include an approval button. The approval button is a button for accepting that the user U2 approves the time displayed in the reservation date and time display field 113b. Therefore, when the user U2 presses the approval button, the user terminal 100-2 transmits, via the network N, to the schedule management device 300a that the change of the reservation date and time has been approved by the user U2 who made the reservation. . Then, when schedule management device 300a receives approval of the reservation date and time from user terminal 100-2, schedule management device 300a notifies store terminal 100-4 of the estimated arrival time and the approved reservation date and time.

As described above, in the third embodiment, the user who has made a reservation to the store (first point) or the like, according to the location of the place of stay (second point) before arriving at the store, the time of stay, etc., It notifies the store of the estimated arrival time. Therefore, the store side can confirm in advance the possibility that the visit time will be changed, and if it is possible to prepare for reception, approve the change of the reservation date and time, and prepare for reception. Also, the user who has made the reservation can grasp the approval of the changed reservation date and time without changing the reservation by himself/herself.

As in the second embodiment described above, the estimated arrival time may be notified to the user first, and the desired time to change the reservation date and time may be received and notified to the store. In other words, in the schedule adjustment processing according to the third embodiment, the user who made the reservation at the store or the like may confirm the estimated time of arrival at the store or the like in advance and change the reservation date and time. At that time, the processing may be performed in the sequence shown in FIG. 17 described above.

<Embodiment 4>
Embodiment 4 is a modification of Embodiment 2 or 3 described above. Embodiment 4 uses a user terminal instead of the authentication terminal installed at the second location. In other words, the location information that the user terminal 100 can receive is included in the staying information as the terminal location information at the second point.

FIG. 25 is a block diagram showing the overall configuration of the schedule management system 1000b according to the fourth embodiment. In the schedule management system 1000b, the schedule management device 300b is changed from that of FIG. 19 described above, and the airport terminal 100-5 and the airport staff member U5 are present in the first point 501b (airport). On the other hand, the schedule management system 1000b does not require an authentication terminal at the second location 502b (conference room).

For example, it is assumed that user U2 moves from the second point 502b to the first point 501b after the meeting and has booked an airline ticket for an aircraft departing from the first point 501b. Specifically, the schedule management device 300b stores the airport or airline information instead of the shop information as the reservation information, and the check-in deadline time at the first point 501b and the departure time of the aircraft as the reservation date and time. . Also, the visit time in the reservation information is the actual check-in time or the like. In addition, the schedule management device 300b stores the location information as the first point 501b and the start time of the scheduled stay time as the check-in deadline time as the schedule information.

It is assumed that user U2 is having a meeting in the meeting room at the second point 502b. Then, the user terminal 100-2 periodically acquires terminal location information using a GPS function or the like, and sends an authentication request including the face image of the user U2, terminal location information, and time information (for example, current time) to the schedule management device. 300b. That is, the acquisition unit 343 of the schedule management device 300b acquires the current location information, the acquisition time, and the face image of the user U2 acquired by the user terminal 100-2 at the second point as stay information.

Note that the user terminal 100-2 may photograph the face image of the user U2 at the second point 502b and include the photographed face image in the authentication request. In that case, when the biometric authentication of the user U2 is successfully performed based on the photographed image of the user U2 at the second point 502b, the acquisition unit 343 of the schedule management apparatus 300b obtains the location information of the second point 502b, It can be said that the authentication time and the user ID are acquired as information during stay. Alternatively, the user terminal 100-2 may include in the authentication request the other identification information described above or the terminal ID of the user terminal 100-2 instead of the face image.

The schedule management device 300b performs the above-described scheduled time estimation processing in response to the authentication request. For example, the schedule management device 300b estimates the estimated arrival time from the time information included in the authentication request, taking into consideration the means of transportation (taxi) from the second point 502b to the first point 501b and road congestion information. . Then, when the estimated arrival time is later than 5 minutes before the check-in deadline time, the schedule management device 300b performs the above-described schedule adjustment processing.

For example, the schedule management device 300b notifies the estimated arrival time and the like to the airport terminal 100-5. In response to this, the airport terminal 100-5 displays a check-in alert screen, which will be described later. As a result, the airport staff member U5 can know that the check-in of the user U2 is coming soon, and can suggest changing the time of the airline ticket. When the time change of the airline ticket is proposed, the airport terminal 100-5 notifies the user terminal 100-2 of the fact and the estimated time of arrival via the schedule management device 300b. In response to this, the user terminal 100-2 displays on the screen the contents of the airline ticket for which the time change is proposed (flight number, departure time, check-in time period, etc.), estimated arrival time, and the like. For example, the user terminal 100-2 may display a screen corresponding to FIG. 16 or FIG. 24 described above. The user terminal 100-2 may perform procedures such as changing the time of the airline ticket with the airport terminal 100-5 via the schedule management device 300b in accordance with the operation of the user U2. Alternatively, user terminal 100-2 may transmit to airport terminal 100-5 via schedule management device 300b, in response to an approval operation from user U2, that the time change of the airline ticket is approved.

FIG. 26 is an example of a check-in alert screen 101c displayed on the airport terminal 100-5 according to the fourth embodiment. The reservation date and time change approval request screen 101b is obtained by applying the above-described scheduled delivery time review request screen 101 of FIG. 15 to the reservation date and time change approval request, and has the same basic configuration. Specifically, the check-in alert screen 101c includes a check-in time zone display field 102c, an estimated arrival time display field 103c, a flight change selection field 104c, a no change button 105c, a proposal button 106c, and a check-in time after change. A band display field 107c is provided. The check-in time zone display field 102c is a display field for the initial check-in time zone corresponding to the reservation ID. Here, it indicates that the user U2 needs to check in at the first point 501b (airport) between "17:00 and 19:00". The estimated arrival time display field 103c is a display field for the estimated arrival time estimated by the schedule management device 300b. It indicates that the user U2 has arrived at the first point 501b and the estimated time of check-in is estimated to be "19:00". The flight change selection column 104c is a column for receiving and displaying a selection operation for changing the flight number (departure time) by the airport staff member U5. The changed check-in time zone display field 107c is a field for displaying the check-in time zone for the flight number selected in the flight change selection field 104c. Here, "hhh125 (departing at 20:00)" is selected as the flight after the change by the airport staff member U5, indicating that the check-in time period for this flight is "17:30 to 19:30". In other words, it indicates that the airport staff member U5 has selected a flight later than the current departure time (check-in deadline time) because there is a possibility that the user U2 will be late for the check-in deadline time. The no change button 105c is a button for accepting confirmation that the current check-in time zone and flight number will not be changed. When the no change button 105c is pressed, the airport terminal 100-5 indicates that the user U2 will arrive just before the check-in time limit for the flight number "hhh123 (departs at 19:30)" and boarding will be just before departure. , notify the boarding gate to that effect. The proposal button 106c is a button for accepting a proposal for changing the flight number (check-in time period) by the airport staff member U5. When the proposal button 106c is pressed, the airport terminal 100-5 displays (selects) the flight change selection field 104c and the changed check-in time zone display field 107c. The check-in time zone is transmitted to the schedule management device 300b.

Alternatively, if the estimated arrival time is later than 5 minutes before the check-in deadline time, the schedule management device 300b may notify the user terminal 100-2 of the estimated arrival time first. At this time, the user terminal 100-2 may display a screen similar to that of FIG. 26 described above. As a result, the user U2 can finish the meeting and head to the first point 501b, or can change the time of the airline ticket. In other words, in the schedule adjustment processing according to the fourth embodiment, the user who has reserved the airline ticket or the like may check the estimated arrival time at the airport or the like in advance and change the (time of) the airline ticket. At that time, the processing may be performed in the sequence shown in FIG. 17 described above.

In this way, the fourth embodiment can also achieve the same effects as those of the second or third embodiment.

<Other embodiments>
It should be noted that, if it is determined as YES in step S338 of FIG. 13 of the above-described second embodiment, the estimation unit 346 estimates a plan to change the scheduled delivery time based on the specified current scheduled delivery time and the estimated arrival time. You may For example, if the current scheduled delivery time is "15:00 to 18:00" and the estimated arrival time is "17:30", the estimation unit 346 proposes to change the scheduled delivery time to "18:00 to 18:00". 20:00" may be estimated. In this case, in the schedule adjustment process, the delivery control unit 342, in addition to the current scheduled delivery time and estimated arrival time, sends a delivery Submit a proposed time change. In response to this, for example, when displaying the screen of FIG. 15 in step S343 of FIG. may be displayed. Similarly, when displaying the screen of FIG. 18 in step S353 of FIG. 17, the user terminal 100-2 may display "18:00 to 20:00" by default in the change selection column 104 of the estimated delivery time. good. If the delivery company U3 or the user U2 selects or inputs the estimated delivery time to be changed from the unselected or uninputted delivery time, it can be said that the delivery company U3 and the user U2 have a heavy burden. Therefore, by displaying the changed delivery schedule time recommended by the schedule management apparatus 300 by default, it becomes easier for the user to select and input, and the change can be supported. For example, when the user or the like accepts the recommended changed estimated delivery time, the user or the like can change the estimated delivery time by simply pressing the change button 106 without operating the change selection field 104 .

Similarly, when performing the schedule adjustment process in Embodiment 3 described above, the estimation unit 346 may estimate a proposal for changing the reservation date and time based on the specified current reservation date and time and the estimated arrival time. For example, if the current reservation date and time is "19:00 to 21:00" and the estimated arrival time is "18:00", the estimation unit 346 proposes to change the reservation date and time to "18:00 to 20:00". 00”. In this case, in the schedule adjustment process, the reservation management unit 342a sends the current reservation date and time and the estimated arrival time to the store terminal 100-4 of the store clerk U4 or the user terminal 100-2 of the user U2, as well as the reservation date and time. Submit your proposed changes. In response to this, for example, when displaying the screen of FIG. 23, the store terminal 100-4 may display "18:00 to 20:00" by default in the reservation date and time change selection column 104b. Similarly, when the estimated arrival time and the like are transmitted to the user terminal 100-2 first, the user terminal 100-2 displays "18:00 to 20:00" by default in the reservation date and time change selection column 104b. good too.

Similarly, when performing the schedule adjustment process in the above-described fourth embodiment, the estimation unit 346 calculates the airline ticket ( departure times and check-in times) may be estimated. For example, if the current check-in time period is "17:00-19:00" and the estimated arrival time is "19:00", the estimation unit 346 determines that the check-in time period is "17:30-19:00". :30” may be presumed as a change proposal.

In the above-described second to fourth embodiments, when the estimated arrival time is likely to be late for the start time of the scheduled stay period or the reservation time, or when the estimated arrival time is too early, the schedule management device 300 or the like You may also recommend a means of transportation other than those currently used. For example, when the means of transportation usually used is a train or a bus, and the person is likely to be late, the schedule management device 300 or the like may suggest a taxi as the means of transportation. In addition, when a train or a bus is usually used as a means of transportation and the user arrives too early, the schedule management device 300 or the like may suggest walking as the means of transportation.

Although the schedule management device 300 and the authentication device 200 are described as separate information processing devices in the second to fourth embodiments described above, they may be the same. For example, the schedule management device 300 may register facial feature information in association with the user ID 3121 of the user information 312 . In that case, the control unit 340 may include the face detection unit 220, the feature point extraction unit 230, the registration unit 240, and the authentication unit 250 shown in FIG.

In the above examples, the program includes instructions (or software code) that, when read into a computer, cause the computer to perform one or more of the functions described in the embodiments. The program may be stored in a non-transitory computer-readable medium or tangible storage medium. By way of example, and not limitation, computer readable media or tangible storage media may include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drives (SSD) or other memory technology, CDs - ROM, digital versatile disc (DVD), Blu-ray disc or other optical disc storage, magnetic cassette, magnetic tape, magnetic disc storage or other magnetic storage device. The program may be transmitted on a transitory computer-readable medium or communication medium. By way of example, and not limitation, transitory computer readable media or communication media include electrical, optical, acoustic, or other forms of propagated signals.

It should be noted that the present disclosure is not limited to the above embodiments, and can be modified as appropriate without departing from the scope. In addition, the present disclosure may be implemented by appropriately combining each embodiment.

Some or all of the above embodiments may also be described in the following additional remarks, but are not limited to the following.
(Appendix A1)
a registration means for registering schedule information including an expected stay time period in which a predetermined user plans to stay at a first point;
Acquisition means for acquiring staying information about a second point where the user is staying;
estimating means for estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the stay information;
notification means for notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
A schedule management device comprising:
(Appendix A2)
The estimation means is
Based on the position information of the first point included in the schedule information and the position information and time information of the second point included in the information during stay, the user moves from the second point to the second point. The schedule management device according to appendix A1, which estimates the estimated arrival time to the first point when moving to one point.
(Appendix A3)
The estimation means is
The schedule management device according to appendix A1 or A2, wherein the estimated arrival time is estimated by further taking into consideration a means of transportation from the second point to the first point.
(Appendix A4)
The estimation means is
The schedule management device according to any one of appendices A1 to A3, wherein the estimated arrival time is estimated by further considering the history of the stay information of the user.
(Appendix A5)
The estimation means is
The schedule management device according to any one of appendices A1 to A4, wherein the estimated arrival time is estimated by further considering the history of arrival times of the user at the first point.
(Appendix A6)
The acquisition means is
When the user is successfully authenticated by the authentication terminal installed at the second point, the location information of the second point, the authentication time, and the user's identification information are acquired as the stay information. Appendixes A1 to A5 The schedule management device according to any one of 1.
(Appendix A7)
The acquisition means is
If the biometric authentication of the user based on the photographed image of the user at the second point is successful, the location information of the second point, the authentication time, and the identification information of the user are transmitted during the stay. Acquired as information The schedule management device according to any one of Appendices A1 to A6.
(Appendix A8)
The acquisition means is
The schedule management device according to any one of Appendices A1 to A5, wherein the current location information, the acquisition time, and the identification information of the user acquired by the user terminal of the user at the second point are acquired as the information during stay. .
(Appendix A9)
The notification means
notifying the user terminal of the user of the estimated arrival time;
The schedule management device according to any one of appendices A1 to A8, wherein, when approval of the estimated arrival time by the user is received from the user terminal, the related party terminal of the related person is notified of the estimated arrival time.
(Appendix A10)
The notification means
Notifying the related party terminal of the related party of the estimated arrival time,
The schedule management device according to any one of appendices A1 to A9, wherein, when approval of the estimated arrival time by the concerned party is received from the concerned party terminal, the estimated arrival time is notified to the user terminal of the user.
(Appendix A11)
the first point is a delivery destination of the product to be delivered to the user;
The concerned person is a person in charge of delivery of the product,
The notification means
The schedule according to any one of Appendices A1 to A10, in which the estimated arrival time is after a predetermined time or more from the start time of the scheduled stay time zone, notifying the related party terminal of the related party of the estimated arrival time management device.
(Appendix B1)
an authentication terminal installed at a second location;
a schedule management device;
The schedule management device
a registration means for registering schedule information including an expected stay time period in which a predetermined user plans to stay at a first point;
Acquisition means for acquiring, from the authentication terminal, staying information about the second point where the user is staying;
estimating means for estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the stay information;
notification means for notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
Appointment management system with
(Appendix B2)
The estimation means is
Based on the position information of the first point included in the schedule information and the position information and time information of the second point included in the information during stay, the user moves from the second point to the second point. The schedule management system according to appendix B1, wherein the estimated time of arrival at the first point is estimated when moving to one point.
(Appendix C1)
the computer
Registering schedule information including a scheduled stay time zone in which a predetermined user plans to stay at a first point;
Acquiring staying information about a second point where the user is staying;
estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the information during stay;
If the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period, notifying at least one of the user or the person concerned at the first point of the estimated arrival time;
Appointment management method.
(Appendix D1)
a registration process for registering schedule information including an expected stay time zone in which a predetermined user plans to stay at a first point;
Acquisition processing for acquiring staying information about a second point where the user is staying;
An estimation process for estimating an estimated arrival time at which the user will arrive at the first point based on the schedule information and the information during stay;
a notification process of notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
A non-transitory computer-readable medium storing a schedule management program that causes a computer to execute

Although the present invention has been described with reference to the embodiments (and examples), the present invention is not limited to the above-described embodiments (and examples). Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

1 schedule management device 11 registration unit 12 acquisition unit 13 estimation unit 14 notification unit 1000 schedule management system U1 user U2 user U3 delivery company U4 salesclerk U5 airport staff N network 100 user terminal 100-1 user terminal 100-2 user terminal 100-3 Portable terminal 100-4 Store terminal 100-5 Airport terminal 110 Camera 120 Storage unit 121 Program 130 Memory 140 Communication unit 150 Input/output unit 160 Control unit 161 Order unit 162 Registration unit 163 Display control unit 200 Authentication device 210 Face information DB
211 User ID
212 facial feature information 220 face detection unit 230 feature point extraction unit 240 registration unit 250 authentication unit 300 schedule management device 310 storage unit 311 program 312 user information 3121 user ID
3122 personal information 3123 terminal information 313 delivery information 3131 delivery ID
3132 Product information 3133 Delivery destination 3134 Scheduled delivery time 3135 Delivery company information 3136 Delivery completion time 314 Schedule information 3141 User ID
3142 Location information 3143 Scheduled stay time zone 315 Action history 3151 User ID
3152 position information 3153 time information 320 memory 330 communication unit 340 control unit 341 registration unit 342 delivery control unit 343 acquisition unit 344 authentication control unit 345 identification unit 346 estimation unit 347 determination unit 400 electronic commerce server 401 parcel 500 authentication terminal 510 camera 520 storage Section 521 Program 530 Memory 540 Communication Section 550 Input/Output Section 560 Control Section 561 Acquisition Section 562 Authentication Request Section 563 Display Control Section 501 First Location 502 Second Location 101 Estimated Delivery Time Examination Request Screen 101a Examination of Estimated Delivery Time Request screen 102 Estimated delivery time display field 103 Estimated arrival time display field 104 Estimated delivery time change selection field 105 No change button 106 Change button 111 Notification content display screen 112 Estimated arrival time display field 113 Estimated delivery time display field 1000a Schedule management system 501a First point 300a Schedule management device 311a Program 316 Schedule information 3161 Reservation ID
3162 store information 3163 location information 3164 reservation date and time 3165 user ID
3166 Arrival time 342a Reservation management unit 345a Identification unit 347a Judgment unit 101b Reservation date and time change approval request screen 102b Reservation date and time display field 103b Estimated arrival time display field 104b Change selection field for reservation date and time 105b Unchangeable button 106b Change approval button 111b Notification content Display screen 112b Estimated arrival time display field 113b Reservation date and time display field 1000b Schedule management system 501b First point 502b Second point 300b Schedule management device 101c Check-in alert screen 102c Check-in time zone display field 103c Estimated arrival time display field 104c Flight change selection field 105c No change button 106c Proposal button 107c Changed check-in time zone display field

Claims

a registration means for registering schedule information including an expected stay time period in which a predetermined user plans to stay at a first point;
Acquisition means for acquiring staying information about a second point where the user is staying;
estimating means for estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the stay information;
notification means for notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
A schedule management device comprising:
The estimation means is
Based on the position information of the first point included in the schedule information and the position information and time information of the second point included in the information during stay, the user moves from the second point to the second point. The schedule management device according to claim 1, which estimates the estimated time of arrival at the first point when moving to one point.
The estimation means is
The schedule management device according to claim 1 or 2, wherein the estimated arrival time is estimated by taking into consideration a means of transportation from the second point to the first point.
The estimation means is
4. The schedule management device according to any one of claims 1 to 3, wherein the estimated arrival time is estimated taking into consideration the history of the stay information of the user.
The estimation means is
5. The schedule management device according to any one of claims 1 to 4, wherein the estimated arrival time is estimated taking into account the history of arrival times of the user at the first point.
The acquisition means is
When the user is successfully authenticated by the authentication terminal installed at the second point, the location information of the second point, the authentication time and the identification information of the user are acquired as the staying information. 6. The schedule management device according to any one of 5.
The acquisition means is
If the biometric authentication of the user based on the photographed image of the user at the second point is successful, the location information of the second point, the authentication time, and the identification information of the user are transmitted during the stay. The schedule management device according to any one of claims 1 to 6, wherein the information is acquired as information.
The acquisition means is
6. The schedule management according to any one of claims 1 to 5, wherein current location information, acquisition time, and identification information of the user acquired by the user terminal of the user at the second point are acquired as the information during stay. Device.
The notification means
notifying the user terminal of the user of the estimated arrival time;
9. The schedule management device according to any one of claims 1 to 8, wherein, when approval of said estimated arrival time by said user is received from said user terminal, said related party terminal is notified of said estimated arrival time.
The notification means
Notifying the related party terminal of the related party of the estimated arrival time,
10. The schedule management device according to any one of claims 1 to 9, wherein, when approval of said estimated arrival time by said related person is received from said related party terminal, said estimated arrival time is notified to said user's user terminal.
the first point is a delivery destination of the product to be delivered to the user;
The concerned person is a person in charge of delivery of the product,
The notification means
11. The apparatus according to any one of claims 1 to 10, wherein when the estimated arrival time is after a predetermined time or more from the start time of the scheduled stay time, the estimated arrival time is notified to the related party terminal of the related party. Appointment management device.
an authentication terminal installed at a second location;
a schedule management device,
The schedule management device
a registration means for registering schedule information including an expected stay time period in which a predetermined user plans to stay at a first point;
Acquisition means for acquiring, from the authentication terminal, staying information about the second point where the user is staying;
estimating means for estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the stay information;
notification means for notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
Appointment management system with
The estimation means is
Based on the position information of the first point included in the schedule information and the position information and time information of the second point included in the information during stay, the user moves from the second point to the second point. 13. The schedule management system according to claim 12, wherein the estimated time of arrival at the first point is estimated when moving to one point.
the computer
Registering schedule information including a scheduled stay time zone in which a predetermined user plans to stay at a first point;
Acquiring staying information about a second point where the user is staying;
estimating an estimated arrival time at which the user arrives at the first point based on the schedule information and the information during stay;
If the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period, notifying at least one of the user or the person concerned at the first point of the estimated arrival time;
Appointment management method.
a registration process for registering schedule information including an expected stay time zone in which a predetermined user plans to stay at a first point;
Acquisition processing for acquiring staying information about a second point where the user is staying;
An estimation process for estimating an estimated arrival time at which the user will arrive at the first point based on the schedule information and the information during stay;
a notification process of notifying at least one of the user or a person concerned at the first location of the estimated arrival time when the estimated arrival time satisfies a predetermined condition with respect to the start time of the scheduled stay time period;
A non-transitory computer-readable medium storing a schedule management program that causes a computer to execute