SERVER DEVICE, DELIVERY STATUS DISPLAY SYSTEM, DELIVERY STATUS RESPONSE METHOD, AND RECORDING MEDIUM

An acquirer acquires a current location from a deliverer terminal being used by a deliverer. A calculator calculates, based on the acquired current location and delivery route information including a delivery destination where the deliverer stops for a delivery, an estimated time of delivery at which the deliverer is expected to be able to make a delivery to the user. A generator generates, in response to the inquiry information received by the receiver, response information including the estimated time of delivery. A transmitter transmits the generated response information to the user terminal. Then, the generator generates, based on the delivery route information, the response information further including the current location only when there is no other delivery destination between the current location and a delivery to the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of Japanese Patent Application No. 2023-132680, filed on Aug. 16, 2023, the entire disclosure of which is incorporated by reference herein.

FIELD OF THE INVENTION

The present disclosure relates to a server device, a delivery status display system, a delivery status response method, and a recording medium.

BACKGROUND OF THE INVENTION

In recent years, e-commerce has become widespread, and many deliveries of purchased items have been made accordingly. For example, an item purchased online by a user through a so-called “online grocer” is delivered to a user's home by a dedicated or affiliated delivery company. Note that, if a user is not at home at a time of delivery, the delivery is not completed, resulting in a re-delivery. Thus, for example, a delivery notification service that notifies a user of the delivery by an e-mail or the like on the day before or on the day of the delivery to encourage the user to be at home has also become widespread. Nevertheless, when the delivery is not a timed delivery, the delivery notification service only notifies a date of delivery, and thus, a user has to remain at home on the date of delivery and wait all day (until the delivery is made). Further, even when the delivery is a timed delivery, there is a range of several hours for a specified time period, and thus, a user still has to remain at home in the specified time period and wait for a long time.

Thus, a system that allows a user to inquire about a time of delivery (time of arrival of a package) has also been developed recently. For example, Unexamined Japanese Patent Application Publication No. 2002-284353 discloses an invention of a delivery time inquiry system (parcel delivery time inquiry system) capable of responding to an inquiry from a user about a time of arrival of a package.

In the invention described in Unexamined Japanese Patent Application Publication No. 2002-284353, a user can inquire a current location of a package (current location of a transportation vehicle) and a time of delivery (scheduled time of delivery) by inputting information relating to the package on an inquiry screen (parcel delivery time inquiry screen as illustrated inFIG.4).

Incidentally, when an actual delivery is made, not only a delivery addressed to a user making an inquiry but also a delivery addressed to another user is also made. For example, a deliverer (delivery company) makes deliveries along a delivery route including a plurality of delivery destinations where he/she stops for a delivery.

Further, as in the above-described invention described in Unexamined Japanese Patent Application Publication No. 2002-284353, when a user inquires a time of delivery or the like, the inquiry is expected to be repeated a plurality of times, not just once.

However, in the invention described in Unexamined Japanese Patent Application Publication No. 2002-284353, there is a risk that a user can estimate a delivery addressed to another user by repeating the inquiry a plurality of times.

In other words, in the invention described in Unexamined Japanese Patent Application Publication No. 2002-284353, since not only a time of delivery but also a current location of a package can be inquired without limitation, there is a problem that a user can estimate another user's home where a delivery may have been made from a trajectory (as an example, a travel route and a stop for a predetermined period of time or more) of current locations acquired by repeating the inquiry.

Due to such a circumstance, there has been a need for a technique that can present a delivery status to a user intelligibly while protecting privacy.

SUMMARY OF THE INVENTION

The present disclosure has been made in view of the above-described circumstance, and an objective of the present disclosure is to provide a server device, a delivery status display system, a delivery status response method, and a recording medium that can present a delivery status to a user intelligibly while protecting privacy.

A server device according to a first point of view of the present disclosure includes:an acquirer acquiring a current location from a deliverer terminal being used by a deliverer who delivers an item to a user;a calculator calculating, based on the current location acquired by the acquirer and delivery route information including a delivery destination where the deliverer stops for a delivery, an estimated time of delivery at which the deliverer is expected to be able to make a delivery to the user;a receiver receiving inquiry information transmitted from a user terminal being used by the user;a generator generating, in response to the inquiry information received by the receiver, response information including the estimated time of delivery calculated by the calculator; anda transmitter transmitting the response information generated by the generator to the user terminal,wherein the generator generates, based on the delivery route information, the response information further including the current location only when there is no other delivery destination between the current location and a delivery to the user.

Further, in the server device according to the above-described point of view, the generator may generate the response information including a map image on which a mark indicating the current location is superimposed and a message indicating the estimated time of delivery or time remaining until the estimated time of delivery only when there is no other delivery destination between the current location and a delivery to the user.

Further, the server device according to the above-described point of view may further include:an updater controlling the acquirer and the calculator to update the current location and the estimated time of delivery at each predetermined time interval; anda notifier notifying the user terminal of advance notice information that a delivery is about to be made soon when time remaining until the estimated time of delivery goes below a predetermined threshold value.

A delivery status display system according to a second point of view of the present disclosure is a delivery status display system in which a deliverer terminal being used by a deliverer who delivers an item to a user, a user terminal being used by a user, and a server device are communicably connected, whereinthe user terminal includes:a terminal transmitter transmitting inquiry information to the server device;a terminal receiver receiving response information rent from the server device; anda display displaying the response information received by the terminal receiver,the server device includes:an acquirer acquiring a current location from the deliverer terminal;a calculator calculating, based on the current location acquired by the acquirer and delivery route information including a delivery destination where the deliverer stops for a delivery, an estimated time of delivery at which the deliverer is expected to be able to make a delivery to the user;a receiver receiving the inquiry information transmitted from the user terminal;a generator generating, in response to the inquiry information received by the receiver, the response information including the estimated time of delivery calculated by the calculator; anda transmitter transmitting the response information generated by the generator to the user terminal, andthe generator generates, based on the delivery route information, the response information further including the current location only when there is no other delivery destination between the current location and a delivery to the user.

A delivery status response method according to a third point of view of the present disclosure is a delivery status response method executed by a server device, and includes:acquiring a current location from a deliverer terminal being used by a deliverer who delivers an item to a user;calculating, based on the acquired current location and delivery route information including a delivery destination where the deliverer stops for a delivery, an estimated time of delivery at which the deliverer is expected to be able to make a delivery to the user;receiving inquiry information transmitted from a user terminal being used by the user;generating, in response to the received inquiry information, response information including the calculated estimated time of delivery; andtransmitting the generated response information to the user terminal,wherein the generating includes generating, based on the delivery route information, the response information further including the current location only when there is no other delivery destination between the current location and a delivery to the user.

An information recording medium according to a fourth point of view of the present disclosure is a non-transitory computer-readable recording medium recording a program, the program causing a computer to execute processing comprising:acquiring a current location from a deliverer terminal being used by a deliverer who delivers an item to a user;calculating, based on the acquired current location and delivery route information including a delivery destination where the deliverer stops for a delivery, an estimated time of delivery at which the deliverer is expected to be able to make a delivery to the user;receiving inquiry information transmitted from a user terminal being used by the user;generating, in response to the received inquiry information, response information including the calculated estimated time of delivery; andtransmitting the generated response information to the user terminal,wherein the generating includes generating, based on the delivery route information, the response information further including the current location only when there is no other delivery destination between the current location and a delivery to the user.

The above-described information recording medium is a non-transitory recording medium, and can be distributed and sold independently of a computer. Herein, the non-transitory recording medium refers to a tangible recording medium. The non-transitory recording medium is, for example, a compact disc, a flexible disk, a hard disk, a magneto-optical disk, a digital video disc, a magnetic tape, a semiconductor memory, or the like. Further, a transitory recording medium indicates a transmission medium (propagation signal) per se. The transitory recording medium is, for example, an electrical signal, an optical signal, an electromagnetic wave, or the like. Note that, a temporary storage area is an area for temporarily storing data or a program, and is, for example, a volatile memory such as a random access memory (RAM).

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the present disclosure are described below. In the embodiments of the present disclosure, description is given using an example of a so-called “online grocer” that accepts an order for an item (product) via a network and delivers the item to a neighborhood user. However, the embodiments of the present disclosure are not limited to such a case of delivering an item purchased at an online grocer, but are similarly applicable to a case of delivering an item purchased through various types of e-commerce transactions.

In other words, the embodiments below are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Therefore, a person skilled in the art can adopt the embodiments in which each or all of the elements thereof are substituted by equivalents thereto, but the embodiments are also included in the scope of the present disclosure.

As illustrated inFIG.1, a delivery status display system100according to Embodiment 1 of the present disclosure includes a server device200controlling the entire delivery status display system100, a user terminal300being used by a user, a deliverer terminal400being used by a deliverer, and an internet900through which the server device200, the user terminal300, and the deliverer terminal400are connected to one another. Note that, it is assumed that the multiple user terminals300are present according to users who use the system, although simplified in the drawing. Further, it is assumed that the multiple deliverer terminals400are also present according to deliverers who deliver an item.

The server device200is, for example, a computer or the like for a server, and presents a delivery status of an item purchased by a user at an online grocer on the user terminal300of the user.

The user terminal300is, for example, a smartphone, a tablet, a personal computer, or the like being used by a user who uses an online grocer, and performs necessary communication with the server device200.

For example, the user terminal300transmits inquiry information to the server device200for inquiring about a delivery status of an item purchased by a user. Then, the user terminal300receives response information sent from the server device200, and displays the response information on a screen. Note that, a detail of the response information is described later.

The deliverer terminal400is, for example, a smartphone, a tablet, or the like being used by a deliverer who delivers an item purchased by a user to a user's home, and performs necessary communication with the server device200.

For example, the deliverer terminal400includes a GPS signal receiver capable of receiving a GPS signal sent from a plurality of global positioning system (GPS) satellites, and transmits a current location (location information) of the deliverer terminal400to the server device200in response to a request from the server device200.

Note that, instead of using such a GPS signal, the deliverer terminal400may use, for example, radio wave strength (receiving strength or the like) from a plurality of base stations to position a current location of the deliverer terminal400, and may transmit the current location to the server device200in response to a request from the server device200.

(Summary Configuration of Information Processing Device)

A typical information processing device500achieving the server device200, the user terminal300, and the like according to the embodiment of the present disclosure is described.

As illustrated inFIG.2, the information processing device500includes a central processing unit (CPU)501, a read only memory (ROM)502, a random access memory (RAM)503, a network interface card (NIC)504, an image processor505, a voice processor506, an auxiliary storage507, an interface508, an operation unit509, a display unit510, and a positioning unit511.

The CPU501controls an operation of the entire information processing device500, is connected to each of the components, and exchanges a control signal or data therewith.

The ROM502records an initial program loader (IPL) that is executed immediately after power-on, and, when the initial program loader is executed, a program stored in the auxiliary storage507is read into the RAM503and execution of the program by the CPU501is started.

The RAM503is for temporarily storing data or a program, and holds a program or data read out from the auxiliary storage507, as well as other data or the like necessary for communication.

The NIC504is for connecting the information processing device500to a computer communication network such as the internet, and includes one conforming to the 10BASE-T/100BASE-T standard for use in configuring a local area network (LAN), an analog modem for connecting to the internet by using a telephone line, an integrated services digital network (ISDN) modem, an asymmetric digital subscriber line (ADSL) modem, a cable modem for connecting to the internet by using a cable television line, and the like.

The image processor505processes, by using an image arithmetic processor (not illustrated) included in the CPU501or the image processor505, image data read out from the auxiliary storage507or the like, and thereafter records the processed image data in a frame memory (not illustrated) included in the image processor505. Image information recorded in the frame memory is converted into a video signal at predetermined synchronization timing, and the video signal is output to outside via the interface508or the like. Note that, when the information processing device500internally includes a display device (the display unit510), the image processor505outputs the converted video signal to the display device. In other words, under control of the CPU501, the image processor505generates an image needed in the progress of processing performed by the information processing device500, and displays the image on the internal or external display device.

The voice processor506converts music data or voice data read out from the auxiliary storage507or the like into a voice signal, and outputs the voice signal to outside via the interface508or the like. Note that, when the information processing device500internally includes a speaker, the voice processor506outputs the converted voice signal to the speaker. In other words, under control of the CPU501, the voice processor506generates a musical sound or a voice to be generated in the progress of processing performed by the information processing device500, and outputs the musical sound or the like from the internal or external speaker.

The auxiliary storage507is a hard disk, a solid state drive (SSD), or the like, and stores various types of programs or various types of data needed for controlling an operation of the entire information processing device500. For example, the auxiliary storage507stores a program for achieving the server device200, the user terminal300, and the like according to the embodiment. Then, by control of the CPU501, the auxiliary storage507reads out the stored program or data as appropriate, and temporarily stores the program or data in the RAM503or the like.

The interface508conforms to, for example, a standard such as an HDMI (registered trademark), a universal serial bus (USB), an inter-integrated circuit (I2C), or the like, and, for example, the operation unit509, the display unit510, and the positioning unit511are connected thereto. Note that, the interface508may transmit and receive necessary information to and from external equipment connected thereto besides the above.

The operation unit509accepts an operation input of a worker or the like who uses the information processing device500.

The display unit510draws an image according to image data output by the image processor505, and presents the image to a worker or the like who uses the information processing device500.

The positioning unit511receives, for example, a GPS signal sent from a plurality of GPS satellites, and positions a current location of the information processing device500at each predetermined timing.

Note that, instead of using such a GPS signal, the positioning unit511may use radio wave strength (receiving strength or the like) from a plurality of base stations to position a current location of the information processing device500.

Besides the above, the information processing device500may include a drive unit for a digital versatile disc (DVD)-ROM or the like, instead of the auxiliary storage507. In this case, the information processing device500reads out a program or data from the DVD-ROM or the like loaded into the drive unit, and operates similarly to the above.

Hereinafter, a functional configuration or the like of the server device200achieved by the above-described information processing device500is described with reference toFIGS.3to6. When the information processing device500is powered on and is enabled to communicate with, for example, the user terminal300and the deliverer terminal400, a program causing the information processing device500to function as the server device200according to Embodiment 1 is executed, and the server device200according to Embodiment 1 is achieved.

(Functional Configuration of Server Device200)

FIG.3is a block diagram illustrating one example of a functional configuration of the server device200according to Embodiment 1. As illustrated, the server device200includes a receiver210, a transmitter220, a storage230, and a controller240.

The receiver210receives various pieces of information sent from the user terminal300or the deliverer terminal400via the internet900.

For example, the receiver210is controlled by the controller240(more specifically, an acquirer241to be described later), and receives a current location from the deliverer terminal400.

Further, the receiver210receives inquiry information about a delivery status from the user terminal300of a user being a delivery destination of an item.

Note that, the above-described NIC504may function as the receiver210as the above.

The transmitter220transmits, for example, various pieces of information addressed to the user terminal300or the like via the internet900.

For example, the transmitter220is controlled by the controller240(more specifically, a notifier244to be described later), and gives, by means of push notification, advance notice information to the user terminal300of a user having an upcoming delivery.

Further, the transmitter220is controlled by the controller240(more specifically, a generator245to be described later), and transmits response information to be described later to the user terminal300.

Note that, the above-described NIC504may function as the transmitter220as the above.

The storage230stores various pieces of information necessary for various types of processing in the server device200. For example, the storage230stores delivery route information231and update rule information232.

Specifically, the storage230stores, as one example, the delivery route information231as illustrated inFIG.4.

Note that, the delivery route information231illustrated inFIG.4is an intelligible schematic representation of a delivery route RT and delivery destinations CS (user's homes) on the route, and, in practice, it is assumed that, for example, information on nodes and links defining the delivery route RT, location information of each of the delivery destinations CS, and the like are defined. Further, it is assumed that, for example, user information, item information, and delivery management information are associated with each of the delivery destinations CS.

The user information includes, for example, a user's name, specific information of the user terminal300used in push notification, a building classification (a house, an apartment complex, or the like) of a user's home, and the like.

Further, the item information includes, for example, an invoice number (slip number) and description of an item to be delivered.

Then, the delivery management information includes, for example, management information (as one example, delivery in progress, delivery completed, missed delivery, or the like) about delivery of an item.

Further, the storage230stores, as one example, the update rule information232as illustrated inFIG.5.

As illustrated inFIG.5, the update rule information232includes, as one example, a remaining time232aand an update interval232b.

The remaining time232ais information that defines ranges of time remaining until an estimated time of delivery calculated by the controller240(more specifically, a calculator242to be described later), and is associated with the update interval232b.

Further, the update interval232bdefines an interval (update timing) at which a current location of the deliverer terminal400and an estimated time of delivery to each of the delivery destinations CS are updated by the controller240(more specifically, an updater243to be described later).

Besides the above, the storage230stores a current location of the deliverer terminal400acquired by the controller240(more specifically, an acquirer241to be described later) and an estimated time of delivery to each of the delivery destinations CS (user's homes) calculated by the controller240(more specifically, the calculator242to be described later).

Further, the storage230also stores information associating a user (the user terminal300) with a deliverer (the deliverer terminal400) and various types of images or text data constituting response information to be described later.

Note that, the above-described auxiliary storage507or the like may function as the storage230as the above.

Returning toFIG.3, the controller240controls the entire server device200. The controller240includes, for example, the acquirer241, the calculator242, the updater243, the notifier244, and the generator245.

The acquirer241acquires a current location from the deliverer terminal400being used by a deliverer who delivers an item to a user.

For example, the acquirer241acquires a current location of the deliverer terminal400by requesting, through control of the transmitter220, the deliverer terminal400to transmit a current location, and receiving, by the receiver210, the current location sent in response thereto from the deliverer terminal400. Note that, timing at which the acquirer241acquires a current location from the deliverer terminal400is controlled by the updater243to be described later.

The calculator242calculates, based on the above-described current location acquired by the acquirer241and the above-described delivery route information231as illustrated inFIG.4, an estimated time of delivery at which a deliverer is expected to be able to make a delivery to a user's home.

In other words, the calculator242calculates an estimated time of delivery to each of the delivery destinations CS (user's homes). Note that, it is assumed that each time delivery by a deliverer proceeds and there arise a delivery destination CS where a delivery has been completed and a delivery destination CS where a user has been absent, the calculator242excludes the delivery destinations CS and calculates an estimated time of delivery for a remaining delivery destination CS.

Further, the calculator242may calculate an estimated time of delivery by specifying, based on the delivery route information231, the number of other delivery destinations between the current location and a user's home or a building classification as for the other delivery destinations and the user's home, and further adding time required according to the specified number of the other delivery destinations or the building classification.

Further, timing at which the calculator242calculates an estimated time of delivery to each of the delivery destinations CS is controlled by the updater243to be described later.

The updater243controls the above-described acquirer241and the above-described calculator242to update a current location and an estimated time of delivery at each predetermined time interval.

For example, among the delivery destinations CS for which the calculator242has calculated an estimated time of delivery, the updater243determines to which of the remaining time232ain the update rule information232illustrated inFIG.5, time remaining until the estimated time of delivery to a next delivery destination CS belongs, and sets the update interval232bassociated therewith as next update timing.

In other words, the updater243changes a time interval according to length of time remaining until an estimated time of delivery, and updates a current location and the estimated time of delivery.

The notifier244notifies the user terminal300of advance notice information that a delivery is about to be made soon when time remaining until the estimated time of delivery calculated by the calculator242described above goes below a predetermined threshold value.

For example, when, among the delivery destinations CS for which the calculator242has calculated an estimated time of delivery, there is any delivery destination CS at which time remaining until the estimated time of delivery goes below a threshold value (as one example, thirty minutes), the notifier244gives, by means of push notification, advance notice information to the user terminal300being used by a user at the delivery destination CS.

Note that, it is assumed that the notifier244excludes the delivery destination CS (the user terminal300) to which advance notice information has been already given, and gives advance notice information only for the delivery destination CS (the user terminal300) at which time remaining goes below a threshold value for the first time.

The generator245generates, in response to inquiry information received by the above-described receiver210from the user terminal300, response information including a current location of the deliverer terminal400and an estimated time of delivery. Then, the generator245controls the above-described transmitter220to transmit the generated response information to the inquiring user terminal300.

For example, the generator245generates response information RS1as illustrated inFIG.6A. The response information RS1includes a message MS1, a map image MP1, and a reload symbol RL.

The message MS1includes, for example, a text indicating an estimated time of delivery and time remaining until the estimated time of delivery. Note that, the message MS1may include any one of an estimated time of delivery and remaining time.

Further, the map image MP1includes a marker MK1indicating a current location of the deliverer terminal400and an icon IC indicating a location of a user's home, the marker MK1and the icon IC being superimposed on a map. Note that, the generator245may change a form (for example, size, color, or the like) of the marker MK1according to length of time remaining until the estimated time of delivery. For example, in a case ofFIG.6A, since time remaining until the estimated time of delivery is long, the generator245generates the light-colored marker MK1larger than standard, and superimposes the marker MK1on the map.

Further, the reload symbol RL is a symbol for reloading the response information RS1. In other words, when the response information RS1is sent to the user terminal300and displayed, and the reload symbol RL is operated (touched or the like) by a user, inquiry information is transmitted to the server device200.

Note that, even when the reload symbol RL as the above is operated on the user terminal300, the generator245generates the response information RS1, based on the current location and the estimated time of delivery acquired and calculated at most recent update timing, since the acquirer241and the calculator242are controlled by the updater243, as described above. In other words, the generator245generates the response information RS1in which only the remaining time in the message MS1is changed (when more than 1 minute of time has elapsed).

Furthermore, when the message MS1includes only the estimated time of delivery (that is, when including no remaining time), the generator245may save the generated response information RS1once in the storage230, and may read out the saved response information RS1and transmit the response information RS1as is to the user terminal300until update timing of the updater243arrives.

Further, as delivery by a deliverer proceeds and the current location of the deliverer terminal400approaches the user's home (the icon IC), the generator245generates, for example, response information RS2as illustrated inFIG.6B. The response information RS2includes a message MS2, a map image MP2, and a reload symbol RL.

The message MS2includes, similarly, an estimated time of delivery and time remaining until the estimated time of delivery. Note that, the message MS2may include any one of an estimated time of delivery and remaining time.

Further, the map image MP2includes a marker MK2indicating a current location of the deliverer terminal400and an icon IC indicating a location of a user's home, the marker MK2and the icon IC being superimposed on a map. Note that, the generator245may change a form of the marker MK2according to length of time remaining until the estimated time of delivery. For example, in a case ofFIG.6B, since time remaining until the estimated time of delivery is short, the generator245generates the dark-colored marker MK2as large as standard (smaller than the above-described marker MK1), and superimposes the marker MK2on the map.

Then, the reload symbol RL is, similarly, a symbol for reloading the response information RS2.

Note that, the above-described CPU501, the image processor505, or the like may function as the controller240configured as the above.

Next, a functional configuration or the like of the user terminal300achieved by the above-described information processing device500is described with reference toFIGS.7and8A-8B. When the information processing device500is powered on and is enabled to communicate with, for example, the server device200, a program causing the information processing device500to function as the user terminal300according to Embodiment 1 is executed, and the user terminal300according to Embodiment 1 is achieved.

(Functional Configuration of User Terminal300)

FIG.7is a block diagram illustrating one example of a functional configuration of the user terminal300according to Embodiment 1. As illustrated, the user terminal300includes a communicator310, an operator320, a storage330, a display340, and a controller350.

The communicator310receives various types of information sent from the server device200, and transmits various types of information to the server device200.

For example, the communicator310receives advance notice information sent from the server device200by means of push notification and response information sent from the server device200. Further, the communicator310transmits, for example, inquiry information or the like to the server device200in response to an operation of a user.

Note that, the above-described NIC504may function as the communicator310as the above.

The operator320is, for example, a touch panel (touch screen) or the like, and accepts various types of operations performed by a user.

For example, the operator320accepts an operation to a push notification (advance notice information) displayed on the display340or an operation to response information (a reload symbol or the like) displayed on the display340.

Note that, the above-described operation unit509may function as the operator320as the above.

The storage330stores various pieces of information necessary for various types of processing in the user terminal300. For example, the storage330stores user information about a user who uses the user terminal300.

Note that, the above-described auxiliary storage507or the like may function as the storage330as the above.

The display340displays various pieces of information for a user.

For example, the display340displays advance notice information NT sent from the server device200by means of push notification, as illustrated inFIG.8A. Note that, when the advance notice information NT is operated by a user, inquiry information is sent to the server device200. Then, the display340displays response information RS sent in response thereto from the server device200, as illustrated inFIG.8B.

The response information RS includes a message MS, a map image MP, and a reload symbol RL, as described above. The response information RS as the above can be displayed on the display340also by, for example, a user inputting, on a predetermined inquiry screen, an invoice number (slip number) or the like of a purchased item, other than by a user operating the advance notice information NT as illustrated inFIG.8A.

Further, when the reload symbol RL included in the response information RS is operated by a user, inquiry information is sent to the server device200. Then, the display340displays the response information RS sent in response thereto from the server device200.

Note that, the above-described display unit510may function as the display340as the above.

Returning toFIG.7, the controller350controls the entire user terminal300.

For example, when the communicator310receives a push notification from the server device200, the controller350displays the above-described advance notice information NT as illustrated inFIG.8Aon the display340. Further, when the advance notice information NT as illustrated inFIG.8Ais operated by a user, the controller350controls the communicator310to transmit inquiry information to the server device200, and displays the response information RS sent in response thereto from the server device200on the display340, as illustrated inFIG.8B.

Furthermore, when the reload symbol RL included in the response information RS as illustrated inFIG.8Bis operated by a user, the controller350displays the response information RS sent in response thereto from the server device200on the display340.

Note that, the above-described CPU501, the image processor505, or the like may function as the controller350as the above.

Further, the deliverer terminal400is also achieved similarly by the information processing device500, but description therefor is omitted.

(Operation of Server Device200and User Terminal300)

Hereinafter, an operation of the server device200and the user terminal300according to Embodiment 1 is described with reference toFIG.9.FIG.9is a flowchart illustrating a flow of delivery status response processing executed by the server device200and delivery status inquiry processing executed by the user terminal300.

Note that, the delivery status response processing is started, for example, in response to delivery start by a deliverer who uses the deliverer terminal400. Further, the delivery status inquiry processing is started, for example, in response to a push notification from the server device200.

First, the server device200acquires a current location from the deliverer terminal400(Step S11).

In other words, the controller240(the acquirer241) acquires a current location from the deliverer terminal400being used by a deliverer who makes a delivery to each of the delivery destinations CS.

The server device200calculates an estimated time of delivery to each of the delivery destinations CS (Step S12).

In other words, the controller240(the calculator242) calculates an estimated time of delivery to each of the delivery destinations CS, based on the current location of the deliverer terminal400acquired in Step S11described above and the delivery route information231as illustrated inFIG.4.

The server device200determines whether remaining time is less than a threshold value (Step S13).

In other words, the controller240(the notifier244) determines whether, among the delivery destinations CS for which the estimated time of delivery has been calculated in Step S12described above, there is any delivery destination at which time remaining until the estimated time of delivery goes below a threshold value (as one example, thirty minutes). Note that, it is assumed that the controller240excludes a delivery destination CS to which advance notice information has been already given, and determines whether there is any delivery destination CS at which remaining time goes below a threshold value for the first time.

When determining that remaining time is not less than a threshold value (Step S13; No), the server device200proceeds with the processing to Step S15to be described later.

Meanwhile, when determining that remaining time is less than a threshold value (Step S13; Yes), the server device200gives a push notification of advance notice information (Step S14).

In other words, the controller240(the notifier244) controls the transmitter220to transmit, by means of push notification, advance notice information to the user terminal300of interest.

The user terminal300to which a push notification has been sent displays the received push notification (Step S31).

In other words, the controller350displays, for example, the advance notice information NT as illustrated inFIG.8Aon the display340.

The user terminal300determines whether any operation to the push notification has been performed (Step S32).

When determining that no operation to the push notification has been performed (Step S32; No), the user terminal300returns the processing to Step S31described above.

Returning to the server device200—side flowchart, the server device200sets update timing (Step S15).

In other words, the controller240(the updater243) refers to the update rule information232as illustrated inFIG.5, and sets an update interval according to time remaining until the estimated time of delivery to a next delivery destination CS.

The server device200determines whether the update timing set in Step S15described above has arrived (Step S16).

When determining that the update timing has arrived (Step S16; Yes), the server device200returns the processing to Step S11described above.

Meanwhile, when determining that the update timing has not arrived (Step S16; No), the server device200determines whether inquiry information has been received (Step S17).

In other words, the controller240determines whether inquiry information sent from the user terminal300has been received.

When determining that inquiry information has not been received (Step S17; No), the server device200returns the processing to Step S16described above.

Returning to the user terminal300—side flowchart, when determining that an operation to the push notification has been performed in Step S32described above (Step S32; Yes), the user terminal300transmits inquiry information to the server device200(Step S33).

Returning to the server device200—side flowchart, when determining that inquiry information has been received in Step S17described above (Step S17; Yes), the server device200generates response information (Step S18).

In other words, the controller240(the generator245) generates, for example, the response information RS1or RS2as illustrated inFIG.6A or6B.

The server device200transmits the response information to the user terminal300(Step S19).

In other words, the controller240(the generator245) transmits the response information generated in Step S18described above to the inquiring user terminal300.

Returning to the user terminal300—side flowchart, the user terminal300displays the received response information (Step S34).

In other words, the controller350displays, for example, the response information RS as illustrated inFIG.8Bon the display340.

The user terminal300determines whether any reload operation has been performed (Step S35).

In other words, the controller350determines whether the reload symbol RL in the response information RS as illustrated inFIG.8Bhas been operated by a user.

When determining that a reload operation has been performed (Step S35; Yes), the user terminal300returns the processing to Step S33described above.

Meanwhile, when determining that no reload operation has been performed (Step S35; No), the user terminal300determines whether a delivery to a user's home has been completed (Step S36).

For example, when delivery completion information for informing completion of a delivery is sent from the server device200and the delivery completion information is received by the communicator310, the controller350determines that a delivery to a user's home has been completed.

When determining that a delivery to a user's home has not been completed (Step S36; No), the user terminal300returns the processing to Step S35described above.

Meanwhile, when determining that a delivery to a user's home has been completed (Step S36; Yes), the user terminal300ends the delivery status inquiry processing.

Returning to the server device200—side flowchart, the server device200determines whether all of deliveries have been finished (Step S20).

In other words, the controller240determines whether all of deliveries to the delivery destinations CS assigned to the deliverer have been finished. Note that, even when the user is not at home at a time of delivery, the delivery to the delivery destination CS is determined as finished.

When determining that not all of deliveries have been finished (Step S20; No), the server device200returns the processing to Step S16described above.

Meanwhile, when determining that all of deliveries have been finished (Step S20; Yes), the server device200ends the delivery status response processing.

Through the delivery status response processing and the delivery status inquiry processing illustrated inFIG.9as the above, timing of acquiring a current location from the deliverer terminal400and timing of calculating an estimated time of delivery to each delivery destination are controlled on the server device200side. This can prevent increase in load (communication load or processing load) on the server device200, even when inquiry information is sent frequently from the user terminal300to the server device200.

As a result, a delivery status can be presented to a user intelligibly while preventing increase in load.

In Embodiment 1 described above, a case in which update timing (timing of acquiring a current location from the deliverer terminal400and timing of calculating an estimated time of delivery to each delivery destination) is controlled on the server device200side has been described. However, the update timing may be controlled on the user terminal300side.

Hereinafter, a delivery status display system100according to Embodiment 2 of the present disclosure in which update timing is controlled on a user terminal300side is described. Note that, an overall configuration of the delivery status display system100according to Embodiment 2 is the same asFIG.1.

(Functional Configuration of Server Device200)

FIG.10is a block diagram illustrating one example of a functional configuration of a server device200according to Embodiment 2. As illustrated, the server device200includes a receiver210, a transmitter220, a storage250, and a controller260.

Note that, the receiver210and the transmitter220have the same configuration as the server device200inFIG.3described above.

The storage250stores various pieces of information necessary for various types of processing in the server device200. For example, the storage230stores delivery route information231.

In other words, the storage250has the configuration of the storage230in the server device200inFIG.3from which the update rule information232is deleted.

Note that, the delivery route information231is the same as the content described with reference toFIG.4described above.

The controller260controls the entire server device200. The controller260includes, for example, an acquirer241, a calculator242, a notifier244, and a generator245.

In other words, the controller260has the configuration of the controller240in the server device200inFIG.3from which the updater243is deleted.

The acquirer241, the calculator242, the notifier244, and the generator245are the same as the configuration of the controller240in the server device200inFIG.3. Nevertheless, the acquirer241, the calculator242, and the generator245are slightly different from the server device200inFIG.3.

The acquirer241acquires a current location from a deliverer terminal400in response to inquiry information received by the receiver210.

When a current location is acquired by the acquirer241, the calculator242calculates, based on the acquired current location and the delivery route information231stored in the storage250, an estimated time of delivery at which a deliverer is expected to be able to make a delivery to a user's home.

When an estimated time of delivery is calculated by the calculator242, the generator245generates response information including the current location and the estimated time of delivery.

For example, the generator245generates response information RS3as illustrated inFIG.11A. The response information RS3includes a message MS1, a map image MP1, and an auto mark AM.

The message MS1and the map image MP1are the same as the response information RS1inFIG.6Adescribed above.

Further, the auto mark AM is a mark indicating automatic update. In other words, the response information RS3includes the auto mark AM instead of the reload symbol RL in the response information RS1inFIG.6A.

Further, as delivery by a deliverer proceeds and the current location of the deliverer terminal400approaches the user's home (an icon IC), the generator245generates, for example, response information RS4as illustrated inFIG.11B. The response information RS4includes a message MS2, a map image MP2, and an auto mark AM.

The message MS2and the map image MP2are the same as the response information RS2inFIG.6Bdescribed above.

Further, the auto mark AM is a mark indicating automatic update. In other words, the response information RS4includes the auto mark AM instead of the reload symbol RL in the response information RS2inFIG.6B.

(Functional Configuration of User Terminal300)

FIG.12is a block diagram illustrating one example of a functional configuration of a user terminal300according to Embodiment 2. As illustrated, the user terminal300includes a communicator310, an operator320, a storage360, a display340, and a controller370.

Note that, the communicator310, the operator320, and the display340have the same configuration as the user terminal300inFIG.7described above.

Nevertheless, the display340displays the response information RS3or RS4generated by the generator245in the server device200and sent therefrom, as illustrated inFIG.13A or13B.

Returning toFIG.12, the storage360stores various pieces of information necessary for various types of processing in the user terminal300. For example, the storage360stores update rule information232.

In other words, the storage360stores the update rule information232as illustrated inFIG.5described above.

The controller370controls the entire user terminal300. The controller370includes, for example, a transmission controller371.

The transmission controller371causes inquiry information to be transmitted at each predetermined time interval.

For example, the transmission controller371determines to which of a remaining time232ain the update rule information232, remaining time in the message (the message MS1, MS2, or the like) included in the response information (the response information RS3, RS4, or the like illustrated inFIGS.13A-13B) sent from the server device200belongs, and sets an update interval232bassociated therewith as next transmission timing of inquiry information.

In other words, the transmission controller371changes a time interval according to length of time remaining until the estimated time of delivery included in the response information, and causes inquiry information to be transmitted to the server device200.

(Operation of Server Device200and User Terminal300)

Hereinafter, an operation of the server device200and the user terminal300according to Embodiment 2 is described with reference toFIG.14.FIG.14is a flowchart illustrating a flow of delivery status response processing executed by the server device200and delivery status inquiry processing executed by the user terminal300.

Note that, the delivery status response processing is started, for example, in response to delivery start by a deliverer who uses the deliverer terminal400. Further, the delivery status inquiry processing is started, for example, in response to a push notification from the server device200, but processing about the push notification is omitted (the same applies to the delivery status response processing).

First, the server device200determines whether any inquiry information sent from the user terminal300has been received (Step S41).

When determining that no inquiry information has been received (Step S41; No), the server device200continues to wait for reception of inquiry information.

Moving to the user terminal300—side flowchart, the user terminal300transmits inquiry information to the server device200(Step S51).

For example, the controller370transmits inquiry information to the server device200only at the first time advance notice information sent by means of push notification from the server device200is operated by a user.

Returning to the server device200—side flowchart, when determining that inquiry information has been received in Step S41described above (Step S41; Yes), the server device200acquires a current location from the deliverer terminal400(Step S42).

In other words, the controller260(the acquirer241) acquires a current location from the deliverer terminal400being used by a deliverer.

The server device200calculates an estimated time of delivery to each of delivery destinations CS (Step S43).

In other words, the controller260(the calculator242) calculates an estimated time of delivery to each of the delivery destinations CS, based on the current location of the deliverer terminal400acquired in Step S42described above and the delivery route information231.

Note that, the controller260may calculate only an estimated time of delivery to the delivery destination CS of the user terminal300having sent inquiry information.

The server device200generates response information (Step S44).

In other words, the controller260(the generator245) generates, for example, the response information RS3or RS4as illustrated inFIG.11A or11B.

The server device200transmits the response information to the user terminal300(Step S45).

In other words, the controller260(the generator245) transmits the response information generated in Step S44described above to the inquiring user terminal300.

Returning to the user terminal300—side flowchart, the user terminal300displays the received response information (Step S52).

In other words, the controller370displays, for example, the response information RS (RS3or RS4) as illustrated inFIG.13A or13Bon the display340.

The user terminal300sets transmission timing of inquiry information (Step S53).

In other words, the controller370(the transmission controller371) determines to which of the remaining time232ain the update rule information232, remaining time in the message (the message MS1, MS2, or the like) included in the response information (the response information RS3, RS4, or the like illustrated inFIGS.13A-13B) belongs, and sets the update interval232bassociated therewith as next transmission timing of inquiry information.

The user terminal300determines whether the transmission timing set in Step S53described above has arrived (Step S54).

When determining that the transmission timing has arrived (Step S54; Yes), the user terminal300returns the processing to Step S51described above.

Meanwhile, when determining that the transmission timing has not arrived (Step S54; No), the user terminal300determines whether a delivery to a user's home has been completed (Step S55).

For example, when delivery completion information for informing completion of a delivery is sent from the server device200and the delivery completion information is received by the communicator310, the controller370determines that a delivery to a user's home has been completed.

When determining that a delivery to a user's home has not been completed (Step S55; No), the user terminal300returns the processing to Step S54described above.

Meanwhile, when determining that a delivery to a user's home has been completed (Step S55; Yes), the user terminal300ends the delivery status inquiry processing.

Returning to the server device200—side flowchart, the server device200determines whether all of deliveries have been finished (Step S46).

In other words, the controller260determines whether all of deliveries to the delivery destinations CS assigned to the deliverer have been finished. Note that, even when the user is not at home at a time of delivery, the delivery to the delivery destination CS is determined as finished.

When determining that not all of deliveries have been finished (Step S46; No), the server device200returns the processing to Step S41described above.

Meanwhile, when determining that all of deliveries have been finished (Step S46; Yes), the server device200ends the delivery status response processing.

In the delivery status response processing and the delivery status inquiry processing illustrated inFIG.14as the above, update timing (timing of acquiring a current location from the deliverer terminal400and timing of calculating an estimated time of delivery to each delivery destination) is controlled on the user terminal300side. At that time, automatic update is performed by the user terminal300side at appropriate intervals, which can prevent increase in load (communication load or processing load) on the server device200.

As a result, a delivery status can be presented to a user intelligibly while preventing increase in load.

In Embodiment 1 or 2 described above, a case in which the controller240or260(the generator245) in the server device200unconditionally generates response information including a map image has been described. However, from a point of view of protecting privacy of other users, response information including a map image may be generated only when there is no other delivery destination between a current location of the deliverer terminal400and a user's home.

Hereinafter, a delivery status display system100according to Embodiment 3 of the present disclosure in which privacy-protected response information is generated is described. Note that, an overall configuration of the delivery status display system100according to Embodiment 3 is the same asFIG.1.

Further, in the delivery status display system100according to Embodiment 3, a case in which update timing (timing of acquiring a current location from a deliverer terminal400and timing of calculating an estimated time of delivery to each delivery destination) is controlled on a server device200side is described, similarly to Embodiment 1. However, the delivery status display system100according to Embodiment 3 is also applicable to a case in which update timing is controlled on a user terminal300side, similarly to Embodiment 2.

(Functional Configuration of Server Device200)

FIG.15is a block diagram illustrating one example of a functional configuration of a server device200according to Embodiment 3. As illustrated, the server device200includes a receiver210, a transmitter220, a storage230, and a controller270.

Note that, the receiver210, the transmitter220, and the storage230have the same configuration as the server device200inFIG.3described above.

The controller270controls the entire server device200. The controller270includes, for example, an acquirer241, a calculator242, an updater243, a notifier244, and a generator271.

In other words, the controller270includes the generator271instead of the generator245in the controller240illustrated inFIG.3.

The acquirer241, the calculator242, the updater243, and the notifier244are the same as the configuration of the controller240in the server device200inFIG.3.

The generator271generates, in response to inquiry information received by the receiver210from a user terminal300, response information including at least an estimated time of delivery. Then, the generator271controls the transmitter220to transmit the generated response information to the inquiring user terminal300.

For example, the generator271generates response information RS5as illustrated inFIG.16Awhen there is another delivery destination between a current location of the deliverer terminal400and a user's home. The response information RS5includes a message MS1and a reload symbol RL. In other words, the generator271generates the response information RS5excluding a map image when there is another delivery destination between a current location of the deliverer terminal400and a user's home.

Meanwhile, the generator271generates, for example, response information RS6as illustrated inFIG.16Bwhen there is no other delivery destination between a current location of the deliverer terminal400and a user's home. The response information RS6includes a message MS2, a map image MP2, and a reload symbol RL.

In other words, the generator271generates response information including a map image only when there is no other delivery destination between a current location of the deliverer terminal400and a user's home.

Note that, a functional configuration of the user terminal300is the same asFIG.7, and thus, description therefor is omitted.

(Operation of Server Device200)

Hereinafter, an operation of the server device200according to Embodiment 3 is described with reference toFIG.17.FIG.17is a flowchart illustrating a flow of delivery status response processing executed by the server device200and delivery status inquiry processing executed by the user terminal300. Note that, an operation on the user terminal300side is the same as the delivery status inquiry processing inFIG.9, and thus, description therefor is omitted.

Further, in the delivery status response processing inFIG.17, processing same as the delivery status response processing inFIG.9is assigned with the same reference sign. Hereinafter, the same processing is described simply.

First, the server device200acquires a current location from the deliverer terminal400(Step S11), and calculates an estimated time of delivery to each of delivery destinations CS (Step S12).

The server device200determines whether remaining time is less than a threshold value (Step S13), and, when determining that remaining time is not less than a threshold value (Step S13; No), the server device200proceeds with the processing to Step S15to be described later.

Meanwhile, when determining that remaining time is less than a threshold value (Step S13; Yes), the server device200gives a push notification of advance notice information (Step S14).

The server device200sets update timing (Step S15), and determines whether the update timing has arrived (Step S16).

When determining that the update timing has arrived (Step S16; Yes), the server device200returns the processing to Step S11described above.

Meanwhile, when determining that the update timing has not arrived (Step S16; No), the server device200determines whether inquiry information has been received (Step S17), and, when determining that inquiry information has not been received (Step S17; No), the server device200returns the processing to Step S16described above.

Meanwhile, when determining that inquiry information has been received (Step S17; Yes), the server device200generates response information according to presence of another delivery destination (Step S61).

In other words, the controller270(generator271) generates, for example, the response information RS5as illustrated inFIG.16Awhen there is another delivery destination between a current location of the deliverer terminal400and a user's home. The response information RS5includes a message MS1and a reload symbol RL. In other words, the controller270generates the response information RS5excluding a map image when there is another delivery destination between a current location of the deliverer terminal400and a user's home.

Meanwhile, the controller270generates, for example, the response information RS6as illustrated inFIG.16Bwhen there is no other delivery destination between a current location of the deliverer terminal400and a user's home. The response information RS6includes a message MS2, a map image MP2, and a reload symbol RL.

In other words, the controller270generates response information including a map image only when there is no other delivery destination between a current location of the deliverer terminal400and a user's home.

The server device200transmits the response information to the user terminal300(Step S19).

In other words, the controller270(the generator271) transmits the response information generated in Step S61described above to the inquiring user terminal300.

The server device200determines whether all of deliveries have been finished (Step S20), and, when determining that not all of deliveries have been finished (Step S20; No), the server device200returns the processing to Step S16described above.

Meanwhile, when determining that all of deliveries have been finished (Step S20; Yes), the server device200ends the delivery status response processing.

Through the delivery status response processing illustrated inFIG.17as the above, response information including a map image is generated only when there is no other delivery destination between a current location of the deliverer terminal400and a user's home. This can prevent estimation of a delivery addressed to another user from a map image.

As a result, a delivery status can be presented to a user intelligibly while protecting privacy.

Other Embodiments

In Embodiments 1 to 3 described above, a case in which an estimated time of delivery to each of the delivery destinations CS is calculated, by the calculator24in the server device200, based on a current location of the deliverer terminal400and the delivery route information231as illustrated inFIG.4has been described. However, an estimated time of delivery may be calculated by adding another piece of information.

For example, each time the acquirer241acquires a current location from the deliverer terminal400, travel history information associated with a time of acquisition is stored in the storage230or250. Note that, as the travel history information, only a history of current locations within a most recent fixed period of time may be stored.

Then, the calculator242calculates an estimated time of delivery to each of the delivery destinations CS, based on the current location of the deliverer terminal400, the delivery route information231as illustrated inFIG.4, and the travel history information stored in the storage230or250.

At that time, the calculator242may calculate an estimated time of delivery to each of the delivery destinations CS by considering a decaying average (an average with less weight given to a more previously acquired value) of current locations in the travel history information.

Besides the above, the calculator242may calculate an estimated time of delivery to each of the delivery destinations CS by also considering externally acquired traffic jam information.

As described above, the present disclosure can provide a server device, a delivery status display system, a delivery status response method, and a recording medium that can present a delivery status to a user intelligibly while protecting privacy.