Mobile sales support device and program thereof

Abstract

To enable not only residents who use a designated sales place but also residents who have difficulty in going to the sales place to use mobile sales.SOLUTION: A mobile sales support device includes route specification means, arrival time prediction means, stop-by determination means, and route determination means. The route specification means specifies a route from a departure point of the mobile stall to a sales point where the mobile sale by the mobile stall is performed via a stop-by place of the mobile sale designated by the user. The arrival time prediction means predicts an arrival time at which the mobile shop that has departed from the departure point at a predetermined departure time arrives at the sales point through the route. The stop-by determination means determines whether or not stop-by to the stop-by place is permitted by comparing the arrival time predicted by the arrival time prediction means with the sales start time at the sales point. The route determination means determines a travel route of the mobile shop vehicle based on a determination result by the stop-by determination means.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a mobile sales support device and a program therefor. [Background technology]

[0002] One form of product sales is mobile sales. Mobile sales involve traveling around the area in a vehicle loaded with food, daily necessities, and other products, parking the vehicle in a suitable location and selling the products. Generally, the location and date and time of the sale are notified to local residents, and residents can purchase the products by going to the designated location on the notified date and time.

[0003] Mobile vendors like this are extremely useful in areas experiencing depopulation and few retail stores. However, it is anticipated that there will be some residents who would like to use mobile vendors, such as the elderly and people with disabilities, who find it difficult to get to the sales location and are therefore unable to do so. Therefore, it is conceivable that mobile vendors could stop by a location of the resident's choice to sell their products, so that residents who have difficulty getting to the sales location can still use the service. However, if the mobile vendors are delayed in arriving at the original sales location because they stop at a location other than the designated sales location, this could result in residents using the mobile vendors having to wait at that location, raising concerns that the mobile vendors would no longer be viable. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-028348 Summary of the Invention [Problem to be solved by the invention]

[0005] The problem that the embodiments of the present invention aim to solve is to provide a mobile sales support device and its program that enables mobile sales to be used not only by residents who use designated sales locations, but also by residents who have difficulty traveling to sales locations. [Means for solving the problem]

[0006] In one embodiment, the mobile sales support device includes a route identification means, an arrival time prediction means, a stop-by determination means, and a route determination means. The route identification means identifies a route from the departure point of the mobile sales vehicle to a sales point where the mobile sales vehicle will conduct mobile sales, via mobile sales stop-by locations specified by the user. The arrival time prediction means predicts the arrival time at which the mobile sales vehicle, having departed from the departure point at a specified departure time, will arrive at the sales point along the route. The stop-by determination means determines whether to allow a stop at the stop-by location by comparing the arrival time predicted by the arrival time prediction means with the sales start time at the sales point. The route determination means determines the driving route of the mobile sales vehicle based on the determination result by the stop-by determination means. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a schematic diagram for explaining an outline of a mobile sales system according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing the system configuration of the mobile sales support system. [Figure 3] FIG. 3 is a block diagram showing the main circuit configuration of the in-vehicle terminal. [Figure 4] FIG. 4 is a block diagram showing the main circuit configuration of the user terminal. [Figure 5] FIG. 5 is a block diagram showing the main circuit configuration of the mobile sales support server. [Figure 6] FIG. 6 is a schematic diagram showing the main data structure of the point-of-sale database. [Figure 7] FIG. 7 is a schematic diagram showing the main data structure of the required time database. [Figure 8]FIG. 8 is a schematic diagram showing the main data structure of the mobile sales database. [Figure 9] FIG. 9 is a schematic diagram showing the main data structure of the product database. [Figure 10] FIG. 10 is a schematic diagram showing the data structure of the date route table. [Figure 11] FIG. 11 is a schematic diagram showing the data structure of the reserved item table. [Figure 12] FIG. 12 is a block diagram showing the main functional configuration that the processor of the mobile sales support server provides to the user terminal. [Figure 13] FIG. 13 is a sequence diagram of main data signals exchanged between the mobile sales support server and the user terminal. [Figure 14] FIG. 14 is a block diagram showing the main functional configuration that the processor of the mobile sales support server 10 provides to the vehicle-mounted terminal. [Figure 15] FIG. 15 is a sequence diagram of main data signals exchanged between the mobile sales support server and the vehicle-mounted terminal. [Figure 16] FIG. 16 is a flowchart showing the procedure of information processing executed by the processor of the user terminal in accordance with the mobile sales application. [Figure 17] FIG. 17 is a flowchart showing the procedure of information processing executed by the processor of the mobile sales support server in accordance with the first mobile sales support program. [Figure 18] FIG. 18 is a flowchart showing a specific procedure of the stop-by determination process in FIG. [Figure 19] FIG. 19 is a flowchart showing a specific procedure for the route creation process in FIG. [Figure 20] FIG. 20 is a diagram showing an example of data in a date-based route table. [Figure 21] FIG. 21 is a diagram showing an example of data in a date-based route table. [Figure 22] FIG. 22 is a diagram showing an example of data in a date-based route table. [Figure 23]FIG. 23 is a flowchart showing the procedure of information processing executed by the processor of the vehicle-mounted terminal according to the main program. [Figure 24] FIG. 24 is a flowchart showing the procedure of information processing executed by the processor of the vehicle-mounted terminal in accordance with the main program. [Figure 25] FIG. 25 is a flowchart showing the procedure of information processing executed by the processor of the mobile sales support server in accordance with the second mobile sales support program. [Figure 26] FIG. 26 is a flowchart showing the procedure of information processing executed by the processor of the mobile sales support server in accordance with the second mobile sales support program. [Figure 27] FIG. 27 is a flowchart showing the procedure of information processing executed by the processor of the mobile sales support server in accordance with the second mobile sales support program. [Figure 28] FIG. 28 is an example of a display image showing a driving route. [Figure 29] FIG. 29 is an example of a display image showing a driving route. [Figure 30] FIG. 30 is an example of an image displaying a list of reserved items. DETAILED DESCRIPTION OF THE INVENTION

[0008] Below, we will explain, with reference to the drawings, an embodiment of a mobile sales support device and its program that makes mobile sales available not only to residents who use designated sales locations, but also to residents who have difficulty traveling to sales locations.

[0009] [Outline of the mobile sales system] FIG. 1 is a schematic diagram for explaining an overview of a mobile sales system according to one embodiment. In this embodiment, a mobile sales operation starts and ends at a garage S, and travels around the area in a mobile sales vehicle 1 loaded with products such as food and daily necessities. The mobile sales vehicle 1 stops sequentially at four predetermined sales locations A, B, C, and D to sell products. The arrival and departure times of the mobile sales vehicle 1 for each of the sales locations A to D are determined for each day of the week, and the mobile sales operation is carried out by traveling around the area according to this schedule.

[0010] On the other hand, this embodiment configures a mobile sales support system 100 so that even residents who have difficulty traveling to sales locations A to D, such as the elderly or people with disabilities, can use mobile sales. The mobile sales support system 100 includes a mobile sales support server 10, which is one aspect of a mobile sales support device, an on-board terminal 20 mounted on a mobile sales vehicle 1, and a user terminal 30 used by a resident 2 who has difficulty traveling to sales locations A to D. In the following, a resident 2 who uses the user terminal 30 will be referred to as a user 2, and will be distinguished from a resident who travels to sales locations A to D and uses mobile sales.

[0011] 2 is a block diagram showing the system configuration of the mobile sales support system 100. The mobile sales support system 100 connects the mobile sales support server 10 to a communication network 41. The mobile sales support system 100 then enables the in-vehicle terminal 20 and the user terminal 30 to be connected to this communication network 41 using wireless communication. By connecting to the communication network 41, the in-vehicle terminal 20 and the user terminal 30 can receive services related to mobile sales from the mobile sales support server 10. The communication network 41 is, for example, the Internet, which allows mobile data communication, and the mobile sales support server 10 provides services related to mobile sales to the in-vehicle terminal 20 and the user terminal 30 in a cloud computing environment.

[0012] The mobile sales support server 10 cooperates with a map information server 50. The mobile sales support server 10 and the map information server 50 are connected by an inter-server network 42. The mobile sales support server 10 and the map information server 50 may also be connected via a communication network 41.

[0013] The map information server 50 uses an electronic map to identify the driving route of the mobile sales vehicle 1 from the departure point to the destination. The map information server 50 then provides the mobile sales support server 10 with map information showing the route and the average travel time required for the mobile sales vehicle 1 to travel that route. It is preferable that the map information server 50 be able to provide the driving route and travel time of the mobile sales vehicle 1 taking into consideration road conditions, traffic conditions, etc.

[0014] The mobile sales support server 10 provides a service that enables even residents who have difficulty traveling to sales locations A to D to use the mobile sales service, based on the travel route and travel time of the mobile sales vehicle 1 provided by the map information server 50.

[0015] [In-vehicle terminal configuration explanation] 3 is a block diagram showing the main circuit configuration of the in-vehicle terminal 20. The in-vehicle terminal 20 includes a processor 21, a main memory 22, an auxiliary storage device 23, a wireless unit 24, a GPS receiver 25, a scanner 26, a display 27, a printer 28, and a system transmission path 29. The system transmission path 29 includes an address bus, a data bus, a control signal line, etc. The system transmission path 29 connects the processor 21 to each of the other components directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0016] The in-vehicle terminal 20 constitutes a computer by connecting a processor 21, a main memory 22, and an auxiliary storage device 23 via a system transmission path 29. The in-vehicle terminal 20 also connects a wireless unit 24, a GPS receiver 25, a scanner 26, a display 27, and a printer 28 to the computer via the system transmission path 29.

[0017] The processor 21 corresponds to the central part of the computer. The processor 21 controls each part to realize various functions of the in-vehicle terminal 20 in accordance with an operating system or an application program. The processor 21 is, for example, a CPU (Central Processing Unit).

[0018] The main memory 22 corresponds to the main storage portion of the computer. The main memory 22 includes a nonvolatile memory area and a volatile memory area. The main memory 22 stores an operating system or application programs in the nonvolatile memory area. The main memory 22 may store data required for the processor 21 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is rewritten by the processor 21 as appropriate. The nonvolatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

[0019] The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 23. The auxiliary storage device 23 stores data used by the processor 21 when performing various processes, data created by the processes in the processor 21, etc. The auxiliary storage device 23 may also store the application programs described above.

[0020] The wireless unit 24 performs wireless communication according to a wireless communication protocol with an access point provided in the communication network 41. This wireless communication enables the in-vehicle terminal 20 to send and receive data signals to and from the mobile sales support server 10 even when the in-vehicle terminal 20 is moving or stopped within the area where the mobile sales is conducted.

[0021] The GPS receiver 25 performs positioning to identify its own position by receiving GPS signals output from GPS satellites. The in-vehicle terminal 20 acquires the current position of the mobile sales vehicle 1 through positioning by the GPS receiver 25.

[0022] The scanner 26 is a device for reading barcodes attached to products. The in-vehicle terminal 20 can identify the products purchased by the shopper based on the barcodes read by the scanner 26. Note that a camera may be provided instead of the scanner 26, and the products may be identified based on images of the products captured by the camera.

[0023] The display 27 is a device for displaying various images. The in-vehicle terminal 20 displays images based on data received from the mobile sales support server 10 on the display 27. Note that a touch panel may be used instead of the display 27.

[0024] The printer 28 is a device for printing data on a predetermined paper such as receipt paper, etc. The vehicle-mounted terminal 20 can operate the printer 28 to issue a receipt to the shopper.

[0025] The on-board terminal 20 may be linked to a car navigation system installed in the mobile sales vehicle 1. In this case, the GPS receiver of the car navigation system may be used, and the GPS receiver 25 may be omitted from the on-board terminal 20.

[0026] [User terminal configuration explanation] 4 is a block diagram showing the main circuit configuration of the user terminal 30. The user terminal 30 includes a processor 31, an internal memory 32, an external memory 33, a wireless unit 34, a GPS receiver 35, a touch panel 36, and a system transmission path 37. The system transmission path 37 includes an address bus, a data bus, a control signal line, etc. The system transmission path 37 connects the processor 31 to each of the other components directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0027] The user terminal 30 constitutes a computer by connecting a processor 31, an internal memory 32, and an external memory 33 via a system transmission path 37. The user terminal 30 also connects a wireless unit 34, a GPS receiver 35, and a touch panel 36 to the computer via the system transmission path 37.

[0028] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the user terminal 30 in accordance with an operating system or application programs. The processor 31 is, for example, a CPU.

[0029] The internal memory 32 corresponds to the main memory of the computer. The internal memory 32 includes a non-volatile memory area and a volatile memory area. The internal memory 32 stores an operating system or application programs in the non-volatile memory area. The internal memory 32 stores data required for the processor 31 to execute processes for controlling each part in the volatile memory area. The internal memory 32 also uses the volatile memory area as a work area where data can be rewritten by the processor 31 as appropriate. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0030] The external memory 33 corresponds to the auxiliary storage portion of the computer. For example, an SD memory card, a USB memory, etc. can be the external memory 33. The external memory 33 stores data used by the processor 31 when performing various processes, or data created by the processes in the processor 31. The external memory 33 may also store the application programs.

[0031] The wireless unit 34 performs wireless communication in accordance with a wireless communication protocol with an access point provided in the communication network 41. This wireless communication enables the user terminal 30 to send and receive data signals to and from the mobile sales support server 10.

[0032] The GPS receiver 35 performs positioning to identify its own location by receiving GPS signals output from GPS satellites. The user terminal 30 acquires the current location of the user terminal 30, that is, the current location of the user 2 using the user terminal 30, through positioning by the GPS receiver 35.

[0033] The touch panel 36 includes a display as a display device and a touch sensor as an input device. The user terminal 30 displays information to be displayed to the user 2 on the display, and detects input from the user 2 regarding the information based on the touch position detected by the touch sensor.

[0034] The user terminal 30 configured as described above can be, for example, a general-purpose electronic device such as a smartphone, tablet terminal, or personal computer. The user 2 installs application software specifically for mobile sales in the internal memory 32 or external memory 33 of the user terminal 30 in advance. Hereinafter, this application software will be referred to as a mobile sales app. By installing the mobile sales app on an electronic device such as a smartphone, tablet terminal, or personal computer, the user 2 can use the electronic device as the user terminal 30.

[0035] [Mobile sales support server configuration explanation] 5 is a block diagram showing the main circuit configuration of the mobile sales support server 10. The mobile sales support server 10 comprises a processor 11, a main memory 12, an auxiliary storage device 13, a clock 14, a network interface 15, an inter-server interface 16, and a system transmission path 17. The system transmission path 17 includes an address bus, a data bus, and a control signal line. The system transmission path 17 connects the processor 11 to each of the other components directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0036] The mobile sales support server 10 constitutes a computer by connecting a processor 11, a main memory 12, and an auxiliary storage device 13 via a system transmission path 17. The mobile sales support server 10 then connects a clock 14, a network interface 15, and an inter-server interface 16 to the computer via the system transmission path 17.

[0037] The processor 11 corresponds to the central part of the computer. The processor 11 controls each part to realize various functions of the mobile sales support server 10 in accordance with an operating system or an application program. The processor 11 is, for example, a CPU. The processor 11 may be, for example, an MPU (Micro Processing Unit), an SoC (System on a Chip), a DSP (Digital Signal Processor), a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field-Programmable Gate Array). Alternatively, the processor 11 may be a combination of two or more of these.

[0038] The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The main memory 12 stores an operating system or application programs in the nonvolatile memory area. The main memory 12 may store data required for the processor 11 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 12 uses the volatile memory area as a work area where data is rewritten by the processor 11 as appropriate. The nonvolatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0039] The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, HDD, or SSD can be the auxiliary storage device 13. The auxiliary storage device 13 stores data used by the processor 11 when performing various processes, data created by the processes in the processor 11, etc. The auxiliary storage device 13 may also store the application programs described above.

[0040] The clock 14 keeps track of the date and time. The mobile sales support server 10 acquires the date and time kept by the clock 14 as the current date and time.

[0041] The network interface 15 is a communication interface connected to the communication network 41. The mobile sales support server 10 can perform data communication with the vehicle-mounted terminal 20 and the user terminal 30 via the network interface 15.

[0042] The inter-server interface 16 is a communication interface connected to the inter-server network 42. The mobile sales support server 10 can perform data communication with the map information server 50 via the inter-server interface 16.

[0043] The mobile sales support server 10 configured as above uses part of the storage area of ​​the auxiliary storage device 13 as an area for a sales location database 131, a required time database 132, a mobile sales database 133, and a product database 134. The mobile sales support server 10 also uses part of the storage area of ​​the auxiliary storage device 13 as an area for a date-based route table 135 and a reserved product table 136. Note that the areas for the date-based route table 135 and the reserved product table 136 may use part of the volatile memory area in the main memory 12.

[0044] FIG. 6 is a schematic diagram showing the main data structure of the sales location database 131. The sales location database 131 is a data collection that stores data such as location names, latitudes, longitudes, and sales times in association with location IDs. The location ID is identification information set for each location to identify the garage S and each of the sales locations A to D shown in FIG. 1. In this embodiment, the location ID of the garage S is set to "000," the location ID of the sales location A is set to "001," the location ID of the sales location B is set to "002," the location ID of the sales location C is set to "003," and the location ID of the sales location D is set to "004."

[0045] The location name is an identification name of a location identified by the corresponding location ID. In this embodiment, the location name of garage S is "S", the location name of sales location A is "A", the location name of sales location B is "B", the location name of sales location C is "C", and the location name of sales location D is "D".

[0046] The latitude and longitude are the latitude and longitude of the center point of the location identified by the corresponding location ID. In Figure 6, "zz°N" indicates north latitude and "zz°E" indicates east longitude.

[0047] The sales time is the time during which the vehicle is parked at a location identified by the corresponding location ID and sells products. In this embodiment, since no products are sold at garage S, the sales time for garage S is 0 minutes. On the other hand, since products are sold at each of sales locations A, B, C, and D, an arbitrary sales time is set for each. The sales time is set appropriately for each sales location based on, for example, the number of shoppers, customer demographics, etc. The sales time may be uniform for each sales location A, B, C, and D. Alternatively, the sales time may be set for each day of the week. In this embodiment, regardless of the day of the week, the sales time for sales location A is 30 minutes, the sales time for sales location B is 20 minutes, the sales time for sales location C is 30 minutes, and the sales time for sales location D is 40 minutes.

[0048] FIG. 7 is a schematic diagram showing the main data structure of the required time database 132. The required time database 132 is a data collection that stores required times in association with departure points and arrival points. The departure point and arrival point are the garage S or each of the sales locations A to D. In other words, if the garage S is the departure point, the arrival point can be sales location A, sales location B, sales location C, or sales location D. If sales location A is the departure point, the arrival point can be the garage S, sales location B, sales location C, or sales location D. If sales location B is the departure point, the arrival point can be the garage S, sales location A, sales location C, or sales location D. The same applies to the other sales locations C and D. The required time is the average driving time required for the mobile sales vehicle 1 to arrive at the arrival point after departing from the departure point. The required time may be set for each day of the week. The required time is always provided with the latest time from the map information server 50 and is updated each time. In this embodiment, the unit of the required time is "minutes."

[0049] 8 is a schematic diagram showing the main data structure of the mobile sales database 133. The mobile sales database 133 is a data collection that stores data on departure times and basic routes for each day of the week. The departure time is the time when the mobile sales vehicle 1 departs from the garage S. In this embodiment, the mobile sales vehicle 1 departs from the garage S at 9:30 every Monday and Saturday, at 12:00 every Wednesday and Friday, and is closed on Tuesdays, Thursdays, and Sundays.

[0050] The basic route indicates the route that the mobile sales vehicle 1 will travel. In this embodiment, the basic route starts from garage S every Monday and Friday, visiting sales locations A, B, C, and D in that order, before returning to garage S. The basic route starts from garage S every Wednesday and Saturday, visiting sales locations D, C, B, and A in that order, before returning to garage S. Note that the basic route does not necessarily have to visit all sales locations A to D. For example, the basic route may omit some sales locations depending on the day of the week.

[0051] FIG. 9 is a schematic diagram showing the main data structure of the product database 134. The product database 134 is a data collection that stores data on the product code, product name, price, and stock quantity for each product loaded on the mobile sales vehicle 1. The product code is a unique code set to identify each product item. The product name and price are the item name and price of the product identified by the corresponding product code. The stock quantity is the number of products loaded that are identified by the corresponding product code. The product database 134 is updated as appropriate by the manager running the mobile sales so that the latest data is stored every time the products loaded on the mobile sales vehicle 1 are changed.

[0052] 10 is a schematic diagram showing the data structure of the date-based route table 135. The date-based route table 135 is a data table organized by date in the format year, month, and day (YYYYMMDD). The date-based route table 135 has a column for record number (No.), a column for location name, a column for latitude and longitude, a column for arrival time, and a column for departure time.

[0053] The record number is a series of numbers starting from "0." The location name and latitude / longitude are the name of the location where mobile sales van 1 will stop and the latitude and longitude of the center point of that location. The arrival time is the scheduled time when mobile sales van 1 is scheduled to arrive at that location, and the departure time is the scheduled time when mobile sales van 1 is scheduled to depart from that location. Below, the record number, location name, latitude / longitude, arrival time, and departure time written in each column of the same line will be referred to as a route record.

[0054] The route record with record number "0" includes the location that is the starting point of the mobile sales, that is, the location name and latitude / longitude of garage S, and the departure time. This route record does not include the arrival time. The route record with record number "1" includes the location name and latitude / longitude of the sales location that mobile sales vehicle 1 will first stop at along the basic route after departing garage S, as well as the arrival and departure times. Similarly, the route records with record numbers "2," "3," and "4" include the location name and latitude / longitude of the sales locations that mobile sales vehicle 1 will stop at sequentially along the basic route, as well as the arrival and departure times. The route record with record number "5" includes the location that is the ending point of the mobile sales, that is, the location name and latitude / longitude of garage S, and the arrival time. This route record does not include the departure time.

[0055] The arrival time is calculated based on the required travel time set in the required travel time database 132 and a predetermined stop-over grace period. The stop-over grace period is a time allowance added to the required travel time to allow the mobile sales vehicle 1 to stop over at locations other than the sales location. For example, if the required travel time from the departure point to the arrival point is 20 minutes and the stop-over grace period is 15 minutes, the arrival time will be 35 minutes after the departure time of the previous route record. On the other hand, the departure time is calculated based on the sales time set in the sales location database 131. In other words, the departure time will be the time when the sales time has elapsed from the arrival time.

[0056] Such a date-specific route table 135 is created, for example, by the day before the mobile sales is conducted, and stored in the auxiliary storage device 13 or the main memory 12. Then, it is deleted the day after the mobile sales is conducted.

[0057] 10 shows the date-specific route table 135 corresponding to the data for Monday in the mobile sales database 133 in FIG. 8, i.e., when the departure time is set to "09:30" and the basic route is set to "S → A → B → C → D → S." The sales location database 131 stores the data shown in FIG. 6. The required time database 132 has the following set: the required time from garage S to sales location A is set to 30 minutes, the required time from sales location A to sales location B is set to 20 minutes, the required time from sales location B to sales location C is set to 35 minutes, the required time from sales location C to sales location D is set to 40 minutes, and the required time from sales location D to garage S is set to 30 minutes.

[0058] Therefore, the departure time of the route record with record number "0" is "09:30". The arrival time of the route record with record number "1" is "10:15", which is the time 30 minutes required and 15 minutes allowed for stopping after the departure time of "09:30" from garage S, and the departure time is "10:45", which is the time 30 minutes allowed for sales after the arrival time of "10:15". The arrival time of the route record with record number "2" is "11:20", which is the time 20 minutes required and 15 minutes allowed for stopping after the departure time of "10:45" from sales location A, and the departure time is "11:40", which is the time 20 minutes allowed for sales after the arrival time of "11:20". The arrival time of the route record with record number "3" is "12:30", which is the time 35 minutes required and 15 minutes allowed for stopping after the departure time of "11:40" from sales location B, and the departure time is "13:00", which is the time 30 minutes allowed for sales after the arrival time of "12:30". The arrival time of the route record with record number "4" is "13:55", which is the time 40 minutes required and 15 minutes allowed for stopping after the departure time of "13:00" from sales location C, and the departure time is "14:35", which is the time 40 minutes allowed for sales after the arrival time of "13:55". The arrival time of the route record with record number "5" is "15:20", which is the time 30 minutes required and 15 minutes allowed for stopping after the departure time of "14:35" from sales location D.

[0059] 11 is a schematic diagram showing the data structure of the reserved item table 136. The reserved item table 136 has a column for the planned purchase date, a column for the location name, a column for the product code, a column for the product name, and a column for the number of items on hold.

[0060] The planned purchase date is the date on which user 2 of user terminal 30 requests to use the mobile sales service at a location other than sales locations A to D. The location name is a name that identifies a location other than sales locations A to D. Hereinafter, locations other than sales locations A to D will be referred to as stop-off locations Po. The location name of stop-off location Po is arbitrary. For example, it can be a name that can be used to identify the garage or sales locations A, B, C, D, such as stop-off locations Pa, Pb, Pc, etc. The location name of the location specified by user 2 as stop-off location Po is entered in the corresponding column of the reserved product table 136.

[0061] The product code, product name, and reservation quantity are data related to the products that user 2 plans to purchase using the mobile sales. In other words, the product code, product name, and reservation quantity of the products that user 2 plans to purchase using the mobile sales at the stopover location Po specified by the location name on the planned purchase date are stored in the reserved product table 136. Incidentally, in the mobile sales, products that user 2 has requested as products that they plan to purchase are reserved in advance. For this reason, in this embodiment, the number of products that the user plans to purchase is expressed as the reservation quantity.

[0062] Hereinafter, the planned purchase date, location name, product code, product name, and reservation quantity written in each column of the same row will be referred to as a reservation record. Reservation records are created through data communication with the user terminal 30 and saved in the reserved product table 136. Reservation records whose planned purchase date has passed are automatically deleted from the reserved product table 136.

[0063] [First function description of the mobile sales support server] Fig. 12 is a block diagram showing the main functional configuration that the processor 11 of the mobile sales support server 10 has with respect to the user terminal 30. Fig. 13 is a sequence diagram of main data signals exchanged between the mobile sales support server 10 and the user terminal 30. Below, the functions that the processor 11 of the mobile sales support server 10 has with respect to the user terminal 30 will be explained using Figs. 12 and 13. Hereinafter, this function will be referred to as the first function.

[0064] As shown in Figure 12, the processor 11 has, as its first function for the user terminal 30, functions of a product notification means 61, a stopover location acquisition means 62, a route identification means 63, an arrival time prediction means 64, a stopover determination means 65, a route determination means 66, a product reservation means 67, an inventory update means 68, and a result notification means 69.

[0065] The product notification means 61 is a function that notifies the user 2 of a list of products loaded on the mobile sales vehicle 1. A user who wishes to stop by the mobile sales vehicle 1 starts the mobile sales app installed on the user terminal 30 and then performs a start input operation on the user terminal 30. In response to this operation, a product list request event is sent from the user terminal 30 to the mobile sales support server 10, as shown in FIG.

[0066] In response to the product list request event, the available product notification means 61 creates a product list based on data in the product database 134. The product list is data that lists the product codes, product names, prices, etc. of products with a stock quantity of "1" or more. The available product notification means 61 notifies the user terminal 30 that sent the product list request event of the product list. Specifically, as shown in FIG. 13 , the available product notification means 61 sends a product list response event including the product list to the user terminal 30 that sent the product list request event. The product list is displayed on the touch panel 36 of the user terminal 30 that received the product list response event.

[0067] The stop-off place acquisition means 62 is a function that acquires the stop-off place Po of the mobile sales van 1 designated by the user 2 of the user terminal 30 based on information from the user terminal 30. After the user 2 confirms that the product list displayed on the touch panel 36 of the user terminal 30 includes the product they wish to purchase, the user 2 operates the touch panel 36 to specify the stop-off place Po, the desired stop date, and the product they plan to purchase. The stop-off place Po is preferably near the home of the user 2. If the user 2 is operating the user terminal 30 at home, the user 2 may specify the current location of the user terminal 30, identified by the GPS receiver 35, as the stop-off place Po. Alternatively, the user 2 may display an electronic map on the touch panel 36 and specify the stop-off place Po on that map.

[0068] The user 2, having specified the stop-off location Po, the desired stop-off date, and the product to be purchased, performs a stop-off application operation on the user terminal 30. In response to this operation, a stop-off request event is transmitted from the user terminal 30 to the mobile sales support server 10, as shown in FIG. 13. The stop-off request event includes information on the latitude and longitude of the stop-off location Po specified by the user 2, information on the desired stop-off date, and information on the product to be purchased. The stop-off location acquisition means 62 acquires the latitude and longitude information of the stop-off location Po from the stop-off request event.

[0069] It should be noted that the stop request event does not necessarily have to include information on the latitude and longitude of the stop place Po. The stop request event may include the address of the stop place Po. If the address is included, the stop place acquisition means 62 acquires information on the latitude and longitude of the address from the map information server 50.

[0070] The route identification means 63 is a function that identifies a route from the departure point of the mobile sales vehicle 1 to the sales point where the mobile sales is performed by the mobile sales vehicle 1, via the stop-off place Po specified by the user 2. For example, if the basic route is "S → A → B → C → D → S," and the stop-off place acquired by the stop-off place acquisition means 62 is between the garage S and the sales point A, the route identification means 63 identifies a route from the garage S, which is the departure point, to the sales point A, via the stop-off place Po. Similarly, when the stop-off place is between the sales point A and the sales point B, the route identification means 63 identifies a route from the sales point A, which is the departure point, to the sales point B, via the stop-off place Po. Even when the stop-off place is between the sales point B and the sales point C, or between the sales point C and the sales point D, the route identification means 63 identifies a route from the sales point, which is the departure point, to the sales point, via the stop-off place Po. When the stop-off place is between the sales place D and the garage S, the route specifying means 63 also specifies a route from the sales place D, which is the starting point, to the garage S via the stop-off place Po.

[0071] Specifically, the route identification means 63 first identifies the departure point and the point of sale by referring to the date-specific route table 135 for the desired stop date. That is, the route identification means 63 compares the latitude and longitude of each place name described in each route record of the date-specific route table 135 with the latitude and longitude of the stop location Po to identify the place name closest to the stop location Po. Hereinafter, the identified place name will be referred to as a specific place name X, and a place name other than the specific place name X will be referred to as another place name Y.

[0072] The route identification means 63 determines whether the stop place Po is located upstream or downstream of the specific place name X on the basic route in the vehicle's traveling direction. That is, if the stop place Po exists on the route from a location where the mobile sales vehicle 1 stops before the specific place name X, i.e., from either the garage S or another sales location with a different place name Y, to the specific place name X, the route identification means 63 determines that the stop place Po is located upstream of the specific place name X on the basic route in the vehicle's traveling direction. Conversely, if the stop place Po exists on the route from the specific place name X to a location where the mobile sales vehicle 1 stops after the specific place name X, i.e., from either the other place name Y or the garage S, the route identification means 63 determines that the stop place Po is located downstream of the specific place name X on the basic route.

[0073] If the stop-off place Po is located upstream of the basic route, the route identification means 63 determines the garage S or another place named Y where the mobile sales vehicle 1 stops before the place named specific place X as the departure point Pf, and the place named specific place X as the sales point Pr. If it is determined that the stop-off place Po is located downstream of the basic route, the route identification means 63 determines the place named specific place X as the departure point Pf, and the sales place or garage S of another place named Y where the mobile sales vehicle 1 stops after the place named specific place X as the sales point Pr.

[0074] Having determined the departure point Pf and the sales point Pr, the route identification means 63 provides the map information server 50 with information on the latitude and longitude of the departure point and sales point, and information on the latitude and longitude of the stop-off place Po, and acquires map information indicating the optimal route from the departure point Pf to the sales point via the stop-off place Po. This map information includes the required time Tfo from the departure point Pf to the stop-off place Po, and the required time Tor from the stop-off place Po to the sales point Pr.

[0075] The arrival time prediction means 64 has a function of predicting the arrival time at which the mobile sales van 1, which departs from the departure point Pf at a predetermined departure time, will arrive at the sales point Pr along the route identified by the route identification means 63. Hereinafter, the predicted arrival time will be referred to as the predicted arrival time. The arrival time prediction means 64 calculates the predicted arrival time by referring to the date-specific route table 135 for the desired stop date and further using map information obtained from the map information server 50. That is, the arrival time prediction means 64 obtains the departure time of the departure point Pf, which is upstream of the stop location Po, from the date-specific route table 135. Then, the arrival time prediction means 64 calculates the predicted arrival time as the time elapsed from the departure time by the required time Tfo from the departure point Pf to the stop location Po, which are included in the map information, and the required time Tor from the stop location Po to the sales point Pr, plus the predetermined stop sales time Tn. That is, the arrival time prediction means 64 calculates the predicted arrival time by adding the required time Tfo, the required time Tor, and the drop-off sales time Tn to the departure time. The drop-off sales time Tn is any amount of time that is necessary and sufficient for the user 2 to purchase products at the drop-off location Po. Since the user 2 specifies the products they wish to purchase in advance, a drop-off sales time Tn of about 5 minutes, for example, is appropriate.

[0076] The stop determination means 65 is a function that determines whether or not to permit a stop at the stop location Po by comparing the predicted arrival time at the sales location predicted by the arrival time prediction means 64 with the sales start time at that sales location. The sales start time is the arrival time at the sales location described in the date-specific route table 135. The stop determination means 65 determines that a stop at the stop location Po is permitted if the predicted arrival time is in time for the sales start time. On the other hand, the stop determination means 65 determines that a stop at the stop location Po is not permitted if the predicted arrival time is not in time for the sales start time.

[0077] Here, the case where the predicted arrival time is in time for the start of sales means that the predicted arrival time is earlier than the start of sales or the same as the start of sales. However, in this regard, even if the predicted arrival time is a few minutes later than the start of sales, for example, 2 to 3 minutes, it is considered that the waiting time for residents using the sales location is extremely short, is within the range of acceptable delay, and will not interfere with the mobile sales, so it may also be considered that the predicted arrival time is in time for the start of sales.

[0078] In addition, when a stopover place Po is added on the route from the last sales location on the basic route back to the garage S, the stopover determination means 65 determines that a stopover at the stopover place Po is not permitted in principle if the estimated arrival time at the sales location estimated by the arrival time prediction means 64 is not in time for the arrival time at the garage S. However, in this regard, since the mobile sales can be established even if the arrival time at the garage S is delayed, it may be determined that a stopover at the stopover place Po is permitted regardless of the estimated arrival time.

[0079] The route determination means 66 has a function of determining the driving route of the mobile sales vehicle 1 based on the determination result by the stop determination means 65. That is, if the stop determination means 65 permits a stop at the stop place Po, the route determination means 66 determines a route that passes through the stop place Po as the driving route. Then, the route determination means 66 updates the date-specific route table 135 for the desired stop date with data of a route that passes through the stop place Po. That is, a route record including the place name, latitude, longitude, arrival time, and departure time of the stop place Po is added to the date-specific route table 135. The arrival time is the time when the required time Mfo for the mobile sales vehicle 1 to arrive at the stop place Po has elapsed from the departure time of the departure point that is upstream of the stop place Po. The departure time is the time when the stop sales time Tn has elapsed from the arrival time.

[0080] On the other hand, if a stop at the stop place Po is not permitted, the route determination means 66 determines a route that does not pass through the stop place Po as the travel route. In other words, the route determination means 66 does not update the date-specific route table 135.

[0081] The product reservation means 67 is a function that adds information about the desired product specified by the user 2 when the stop is permitted by the stop determination means 65 to the reserved product table 136. That is, the product reservation means 67 adds a reservation record to the reserved product table 136, the reservation record including the planned purchase date which is the desired stop date, the location name which identifies the stop location Po, the product code of the desired product, the product name, and the reservation quantity.

[0082] The inventory update means 68 is a function that, when a stop is permitted by the stop determination means 65, subtracts the number of items on hold from the stock number of the desired product stored in the product database 134. When a stop is permitted, the desired product specified by user 2 is set aside separately and is not included in the inventory. For this reason, the inventory update means 68 subtracts the number of items on hold from the stock number of the desired product in advance.

[0083] The result notifying means 69 is a function that notifies the user terminal 30 of the determination result made by the stop-by determination means 65. As shown in FIG. 13 , when the stop-by determination means 65 determines that a stop is permitted, the result notifying means 69 transmits a stop-by permitted event to the user terminal 30. The stop-by permitted event includes information such as the date and time of arrival at the stop-by location Po and the products to be purchased. In the user terminal 30 that has received the stop-by permitted event, the date and time of arrival at the stop-by location Po and the information about the products to be purchased are displayed on the touch panel 36. Therefore, the user 2 of the user terminal 30 can know that the application to stop by has been permitted. The user 2 can use the mobile sales service by going to the specified stop-by location Po by the arrival time on the specified desired stop-by date.

[0084] On the other hand, if the stop-in determination means 65 determines that the stop-in is not permitted, the result notification means 69 transmits a stop-in denial event to the user terminal 30. In the user terminal 30 that receives the stop-in denial event, a message indicating that the stop-in is not permitted is displayed on the touch panel 36. Therefore, the user 2 of the user terminal 30 can know that the stop-in is not permitted on the specified desired stop-in date.

[0085] Incidentally, in this embodiment, the route from the basic route is reversed depending on the day of the week, and the departure time from the garage S is changed. Therefore, depending on the desired date of the stop, the required time Txp from the departure point to the stop location Po, or the required time Tpy from the stop location Po to the arrival point, may be shortened due to road conditions or traffic conditions on that day. Therefore, user 2 who was not permitted to stop can change the desired date of the stop and apply for a stop again. By doing so, there is a possibility that the stop will be permitted and the mobile sales will be able to use the mobile sales.

[0086] The first function described above in detail enables the mobile sales support server 10 to accept a request from the user 2 using the user terminal 30 to use the mobile sales service at a location other than the designated sales location, a so-called stop-by request. Upon accepting the stop-by request, the mobile sales support server 10 checks whether stopping at the stop-by location Po designated by the user 2 will cause a delay in arrival at the designated sales locations A to D. If there will be no delay in arrival at the sales locations A to D, the mobile sales support server 10 permits the user to stop at the stop-by location Po. On the other hand, if there will be a delay in arrival at the sales locations A to D, the mobile sales support server 10 does not permit the user to stop at the stop-by location Po.

[0087] If a stop is permitted, the mobile sales support server 10 determines a driving route that includes the stop location Po. Then, the mobile sales support server 10 adds a route record that describes the location name, latitude and longitude, arrival time, and departure time of the stop location Po to the date-specific route table 135, which has the desired stop date as the date, between the route record of the sales location located upstream in the route travel direction from the stop location and the route record of the sales location located downstream. In addition, the mobile sales support server 10 adds a reservation record that describes the planned purchase date, location name, product code, product name, and reservation quantity to the reservation product table 136 in order to reserve separately the product that the user 2 wishes to purchase.

[0088] In this way, the mobile sales support server 10 can determine a driving route that will not delay the arrival time at the predetermined sales locations A to D, even if the mobile sales vehicle 1 passes through the stop-off location Po. In addition, the mobile sales support server 10 can keep a list of products that users 2 using the mobile sales service at the stop-off location Po wish to purchase.

[0089] [Second function explanation of the mobile sales support server] Fig. 14 is a block diagram showing the main functional configuration that the processor 11 of the mobile sales support server 10 has with respect to the on-board terminal 20. Fig. 15 is a sequence diagram of main data signals exchanged between the mobile sales support server 10 and the on-board terminal 20. Below, the functions that the processor 11 of the mobile sales support server 10 has with respect to the on-board terminal 20 will be explained using Figs. 14 and 15. Hereinafter, this function will be referred to as the second function.

[0090] As shown in Figure 14, the processor 11 has, as second functions for the in-vehicle terminal 20, functions such as a driving route acquisition means 71, a driving route notification means 72, a vehicle position acquisition means 73, a stopping point notification means 74, a stopping point determination means 75, a reserved product notification means 76, a product registration processing means 77, and an inventory update means 78.

[0091] The driving route acquisition means 71 is a function that acquires the driving route of the mobile sales vehicle 1 by referring to the date-specific route table 135. As shown in Fig. 15, the in-vehicle terminal 20 transmits a driving route request event, for example, in response to a start input operation by a salesperson getting into the mobile sales vehicle 1. Upon receiving this driving route request event, the driving route acquisition means 71 acquires the data from the date-specific route table 135 for the current day as the driving route. Specifically, the driving route acquisition means 71 acquires a driving route that starts from the location specified by the location name in the route record with record number "0," passes through the locations specified by the location names in the route records with record numbers "1" and higher, and ends at the location specified by the location name in the route record with the largest record number.

[0092] The driving route notification means 72 is a function that notifies the in-vehicle terminal 20 of the driving route acquired by the driving route acquisition means 71. Specifically, as shown in Fig. 15 , the driving route notification means 72 transmits a driving route response event including data of the driving route to the in-vehicle terminal 20 that is the sender of the driving route request event. In the in-vehicle terminal 20 that receives the driving route response event, the driving route is displayed on the display 27.

[0093] If the stop-off determination means 65 in the first function permits a stop at the stop-off place Po, a route record for the stop-off place Po is added to the date-specific route table 135. In this case, the travel route acquisition means 71 acquires a travel route that travels around the area with the stop-off place Po as a stop-off point. Therefore, the display 27 of the in-vehicle terminal 20 displays a travel route that includes the stop-off place Po as a stop-off point in addition to the predetermined sales locations A to D.

[0094] The vehicle position acquisition means 73 is a function that acquires the position of the mobile sales vehicle 1 by communicating with the on-board terminal 20 mounted on the mobile sales vehicle 1. As shown in FIG. 15, when the on-board terminal 20 detects that the vehicle has started moving, it outputs a departure notification event to the mobile sales support server 10. In response to this departure notification event, the mobile sales support server 10 detects the position information of the mobile sales vehicle 1 identified by the GPS receiver 25. Using this position information, the vehicle position acquisition means 73 acquires the latitude and longitude of the point from which the mobile sales vehicle 1 started.

[0095] The stop point notification means 74 is a function that notifies the in-vehicle terminal 20 of the next stop point of the mobile sales vehicle 1 based on the travel route determined by the route determination means 66 of the first function and the position of the mobile sales vehicle 1 acquired by the vehicle position acquisition means 73. That is, the stop point notification means 74 determines which latitude and longitude of the departure point of the mobile sales vehicle 1 acquired by the vehicle position acquisition means 73 are closest to which latitude and longitude of a location in the date-specific route table 135 for the current day. For example, if the latitude and longitude of the departure point are close to the latitude and longitude of garage S in the date-specific route table 135, the stop point notification means 74 determines that the departure point of the mobile sales vehicle 1 is the garage. The stop point notification means 74 determines the next stop point after garage S on the travel route, for example, sales location A, as the stop point. Similarly, if the latitude and longitude of the departure point are close to the latitude and longitude of sales location A in the date route table 135, the stop point notification means 74 determines that the departure point of the mobile sales vehicle 1 is sales location A. The stop point notification means 74 determines the next stop on the travel route after sales location A, for example, sales location B, as the stop point. Here, if a travel route has been determined that stops at stop point Po on the way from sales location A to sales location B, the stop point notification means 74 determines stop point Po as the stop point.

[0096] After determining the stop point, the stop point notification means 74 outputs a stop point notification event to the in-vehicle terminal 20, notifying the location determined as the stop point, as shown in Fig. 15. As a result, information indicating the next stop point is displayed on the display 27 of the in-vehicle terminal 20. Therefore, the salesperson of the mobile sales van 1 can simply drive toward the next stop point. If the in-vehicle terminal 20 is linked to a car navigation system, the car navigation system may provide guidance on the driving route with the stop point as the destination.

[0097] The stopping position determination means 75 has a function of determining the position where the mobile sales vehicle 1 is stopped. As shown in FIG. 15 , when the in-vehicle terminal 20 detects that the vehicle has stopped, it outputs a stopping notification event to the mobile sales support server 10. In response to this stopping notification event, the mobile sales support server 10 detects the position information of the mobile sales vehicle 1 identified by the GPS receiver 25. The stopping position determination means 75 uses this position information to obtain the latitude and longitude of the point where the mobile sales vehicle 1 is stopped. Then, based on the latitude and longitude, the stopping position determination means 75 determines whether the point where the mobile sales vehicle 1 is stopped is a sales location A, B, C, or D on the driving route, a stop-off location Po, or a garage S.

[0098] For example, if the latitude and longitude of the point where the mobile sales vehicle 1 stopped are close to those of sales location A, the stopping position determination means 75 identifies the stopping position of the mobile sales vehicle 1 as sales location A. For example, if the latitude and longitude of the point where the mobile sales vehicle 1 stopped are close to those of stop-off location Po, the stopping position determination means 75 identifies the stopping position of the mobile sales vehicle 1 as stop-off location Po. The same applies to other sales locations B, C, D, or garage S. On the other hand, if the latitude and longitude of the point where the mobile sales vehicle 1 stopped are far from the latitude and longitude of any of sales locations A, B, C, D, or stop-off location Po, or garage S, it is considered that the mobile sales vehicle stopped for reasons other than the purpose of mobile sales. In this case, the stopping position determination means 75 does not identify the stopping position.

[0099] The reserved item notification means 76 has a function of notifying the on-board terminal 20 of a list of reserved items for the user 2 who specified the stop location Po when the mobile sales van 1 stops at the stop location Po. That is, when the stop location determination means 75 identifies the stop location Po as the stop location of the mobile sales van 1, the reserved item notification means 76 operates. That is, the reserved item notification means 76 searches the reserved item table 136 and extracts reservation records with the location name of the stop location Po from among the reservation records for which the purchase date is the current day. The reserved item notification means 76 then creates a reserved item list that lists the product codes, product names, and reservation quantities of the extracted reservation records, and notifies the on-board terminal 20 of the list. Specifically, the reserved item notification means 76 transmits a reserved item notification event including the reserved item list to the on-board terminal 20, as shown in FIG. 15 . Upon receiving the reserved item notification event, the on-board terminal 20 displays the reserved item list on the display 27. Therefore, the salesperson can prepare the reserved item displayed in the reserved item list and sell it to the user 2 who is waiting at the stopover point Po.

[0100] The product registration processing means 77 has a function of registering sales data of products whose product codes have been read by the scanner 26 of the in-vehicle terminal 20. When the mobile sales vehicle 1 stops at the stop-off place Po or any of the sales locations A, B, C, or D, the mobile sales operation begins. That is, the salesperson uses the scanner 26 to scan the barcodes attached to the products to be purchased by the users 2 waiting at the stop-off place Po or the shoppers waiting at any of the sales locations A, B, C, or D.

[0101] When the barcode is scanned by the scanner 26, a product registration request event is sent from the vehicle-mounted terminal 20 to the mobile sales support server 10, as shown in Figure 15. The product registration request event includes the product code read from the barcode, etc. The product registration processing means 77 obtains the price of the product identified by the product code from the product database 134, and registers the product sales data in the sales file in the main memory 12 based on that price. The product sales data is data including the product code, product name, number of items sold, sales amount, etc. The number of items sold is usually "1". The sales amount is the price multiplied by the number of items sold.

[0102] The inventory update means 78 has a function of subtracting the number of items purchased by the shopper from the inventory quantity of each item stored in the item database 134. However, for items registered in the reserved item table 136, the inventory quantity has already been subtracted. Therefore, the inventory update means 78 checks whether the item registered by the item registration processing means 77 is an item on reservation. Then, when sales data of an item other than an item on reservation is registered, the inventory update means 78 subtracts the number of items purchased by the shopper from the inventory quantity of that item stored in the item database 134.

[0103] By the second function described above in detail, the mobile sales support server 10 notifies the on-board terminal 20 of the mobile sales vehicle 1 that is about to start mobile sales of the day's driving route. Upon receiving this notification, the on-board terminal 20 displays the day's driving route on its display 27. Therefore, the salesperson getting into the mobile sales vehicle 1 can see the day's driving route from the screen of the display 27.

[0104] When the mobile sales vehicle 1 starts moving, the mobile sales support server 10 notifies the mobile sales vehicle 1 of the next stopping point. The stopping point may be one of the predetermined sales locations A to D, or it may be a stop-off location Po designated by the user 2. The stopping point is displayed on the display 27 of the in-vehicle terminal 20. Therefore, the salesperson simply drives the mobile sales vehicle 1 along the driving route toward the stopping point.

[0105] When the mobile sales vehicle 1 stops, the mobile sales support server 10 determines whether it has stopped at one of the sales locations A to D or at the stop-off location Po. If it has stopped at the stop-off location Po, the mobile sales support server 10 notifies the on-board terminal 20 of a list of reserved items corresponding to that stop-off location Po. Upon receiving this notification, the on-board terminal 20 displays the on-hold item list on the display 27. The on-hold item list is a list of items that user 2, who has specified the stop-off location Po, wishes to purchase. Therefore, the salesperson simply retrieves the items that have been reserved in advance for user 2 and sells them to the user. However, this does not prevent user 2 from purchasing items other than the items that he or she wishes to purchase.

[0106] [Explanation of information processing on the mobile sales support server] The first function described above is realized by the processor 11 of the mobile sales support server 10 executing information processing in accordance with a first mobile sales support program. The second function is realized by the processor 11 executing information processing in accordance with a second mobile sales support program. Next, the information processing executed by the processor 11 of the mobile sales support server 10 will be described.

[0107] Incidentally, the first mobile sales support program and the second mobile sales support program are both types of application programs stored in the main memory 12 or the auxiliary storage device 13. There are no particular limitations on the method for installing the first mobile sales support program and the second mobile sales support program into the main memory 12 or the auxiliary storage device 13. The first mobile sales support program and the second mobile sales support program can be recorded on a removable recording medium, or can be distributed by communication via a network and installed into the main memory 12 or the auxiliary storage device 13. The recording medium can be in any form, such as a CD-ROM or memory card, as long as it can store a program and is readable by the device.

[0108] [Information processing explanation for the first function] Fig. 16 is a flowchart showing the procedure of information processing executed by the processor 31 of the user terminal 30 in accordance with the mobile sales app. Figs. 17 to 19 are flowcharts showing the procedure of information processing executed by the processor 11 of the mobile sales support server 10 in accordance with the first mobile sales support program. The information processing related to the first function will be explained below with reference to Figs. 16 to 19.

[0109] As shown in Fig. 16, the processor 31 of the user terminal 30 on which the mobile sales app has been launched waits for a start input in ACT101. When the start input is detected by a touch operation on the touch panel 36 by the user 2, the processor 31 proceeds to ACT102. In ACT102, the processor 31 controls the output of a product list request event. By this control, a product list request event signal is wirelessly transmitted via the wireless unit 34. This signal is received at an access point of the communication network 41 and transmitted to the mobile sales support server 10 via the communication network 41.

[0110] 17, the processor 11 of the mobile sales support server 10 waits for a product list request event in ACT201. When a product list request event signal is received via the network interface 15, the processor 11 proceeds to ACT202. In ACT202, the processor 11 creates a product list based on the data in the product database 134. That is, the processor 11 obtains the product code, product name, price, etc. of products whose inventory quantity is "1" or more from the product database 134, and creates a product list.

[0111] After creating the product list, processor 11 proceeds to ACT 203. In ACT 203, processor 11 controls the output of a product list response event. This control causes a product list response event signal including the product list to be transmitted from network interface 15 to user terminal 30, the sender of the product list request event. The product list response event signal is wirelessly transmitted from a predetermined access point via communication network 41, and is received by user terminal 30, the sender of the product list request event.

[0112] After controlling the output of the product list request event in ACT102 of Fig. 16, the processor 31 of the user terminal 30 proceeds to ACT103. In ACT103, the processor 31 waits for a product list response event. In this waiting state, if the product list response event is not received even after a predetermined time has elapsed since the processor 31 controlled the output of the product list request event, it is highly likely that a communication error has occurred. The processor 31 terminates the information processing procedure shown in the flowchart of Fig. 16 as an error.

[0113] In the standby state of ACT103, if the processor 31 receives a product list response event signal via the wireless unit 34 within a predetermined time, the processor 31 proceeds to ACT104. In ACT104, the processor 31 displays the product list included in the product list response event on the touch panel 36. Therefore, the user 2 can check the products loaded on the mobile sales vehicle 1 based on the information in the product list.

[0114] After displaying the product list on the touch panel 36, the processor 31 proceeds to ACT 105. In ACT 105, the processor 31 checks whether or not a stop-by request has been issued by the user 2 through a touch operation on the touch panel 36. For example, the touch panel 36 displays, along with the product list, button images of a first button to be entered when making a stop-by request and a second button to be entered when not making a stop-by request. User 2 who wishes to make a stop-by request because the product they wish to purchase is listed on the product list touches the first button. User 2 who does not wish to make a stop-by request because the product they wish to purchase is not listed on the product list touches the second button.

[0115] In ACT105, the processor 31 waits for the first button or the second button to be pressed. If the second button is pressed, the processor 31 proceeds to ACT106. In ACT106, the processor 31 controls the output of an end notification event. By this control, a signal of the end notification event is wirelessly transmitted via the wireless unit 34. This signal is received at an access point of the communication network 41 and transmitted to the mobile sales support server 10 via the communication network 41. After controlling the output of the end notification event, the processor 31 ends the information processing of the procedure shown in the flowchart of FIG. 16.

[0116] On the other hand, if the first button is pressed, the processor 31 proceeds to ACT 107. The processor 31 acquires the product intended for purchase in ACT 107. That is, the processor 31 acquires the product selected by the user's touch operation from the product list as the product intended for purchase. At this time, the desired purchase quantity for the product intended for purchase can be input, and user 2 who wishes to purchase two or more of the same product also inputs the desired purchase quantity. If the desired purchase quantity is input, the processor 31 acquires that number as the desired purchase quantity of the product intended for purchase. If the desired purchase quantity is not input, the processor 31 acquires "1" as the desired purchase quantity of the product intended for purchase.

[0117] After acquiring the product to be purchased, the processor 31 proceeds to ACT108. In ACT108, the processor 31 determines a stop-off place Po. For example, the processor 31 displays a selection screen on the touch panel 36, which allows the user 2 to select whether to set the current location as the stop-off place Po or to specify the stop-off place Po on a map. When the user 2 selects, by a touch operation, to set the current location as the stop-off place Po, the processor 31 determines the current location of the user terminal 30 identified by the GPS receiver 35 as the stop-off place Po. On the other hand, when the user selects, by a touch operation, to specify the stop-off place Po on a map, the processor 31 displays an electronic map on the touch panel 36. Then, the processor 31 determines the point indicated by the touch operation of the user 2 as the stop-off place Po.

[0118] After determining the stop-off location, the processor 31 proceeds to ACT 109. In ACT 109, the processor 31 acquires the desired stop-off date. The processor 31 displays an image of a calendar on the touch panel 36, for example. The processor 31 then acquires the date indicated on the calendar by the touch operation of the user 2 as the desired stop-off date. Note that the method by which the user 2 specifies the desired stop-off date is not limited to the method using a calendar. For example, the desired stop-off date may be entered manually.

[0119] Therefore, after acquiring the product to be purchased, determining the stop-off location Po, and acquiring the desired stop-off date, the processor 31 proceeds to ACT 110. In ACT 110, the processor 31 controls the output of a stop-off request event. This control causes a stop-off request event signal to be wirelessly transmitted via the wireless unit 34. This signal is received at an access point of the communication network 41 and transmitted to the mobile sales support server 10 via the communication network 41. The stop-off request event includes information about the product to be purchased, information about the stop-off location Po, and information about the desired stop-off date. Note that the procedure for accepting the product to be purchased, the stop-off location Po, and the desired stop-off date in the user terminal 30 is not limited to the procedure shown in the flowchart of FIG. 16 . For example, the stop-off location Po may be accepted first, followed by the input of the desired stop-off date, and finally the information about the product to be purchased. Alternatively, the input of the desired stop-off date may be accepted first, followed by the information about the product to be purchased, and finally the stop-off location Po.

[0120] The processor 11 of the mobile sales support server 10, which controlled the transmission of the product list response event in ACT 203 of Fig. 17, proceeds to ACT 204. The processor 11 waits to receive a stop-by request event in ACT 204. In this waiting state, if a signal of an end notification event is received instead of a stop-by request event, the processor 11 ends the information processing of the procedure shown in the flowchart of Fig. 17.

[0121] In the standby state of ACT204, when a signal of a stop-off request event is received via the network interface 15, the processor 11 proceeds to ACT205. The processor 11 executes a stop-off determination process in ACT205. The stop-off determination process is a process for determining whether or not it is possible to stop at the stop-off location Po specified by the user 2. The stop-off determination process will be described in detail later.

[0122] After executing the stop-off determination process, the processor 11 proceeds to ACT206. In ACT206, the processor 11 checks whether the stop-off is permitted. If the stop-off is not permitted, the processor 11 proceeds to ACT207. In ACT207, the processor 11 controls the output of a stop-off not permitted event. By this control, a signal of the stop-off not permitted event is transmitted from the network interface 15 to the user terminal 30 that is the sender of the stop-off request event. The signal of the stop-off not permitted event is wirelessly transmitted from a predetermined access point via the communication network 41 and received by the user terminal 30 that is the sender of the stop-off request event. After controlling the output of the stop-off not permitted event, the processor 11 ends the information processing of the procedure shown in the flowchart of FIG. 17.

[0123] If the stop is permitted in ACT206, the processor 11 proceeds to ACT208. In ACT208, the processor 11 controls the output of a stop-permitted event. By this control, a signal of the stop-permitted event is transmitted from the network interface 15 to the user terminal 30 that is the sender of the stop-request event. The signal of the stop-permitted event is wirelessly transmitted from a predetermined access point via the communication network 41, and is received by the user terminal 30 that is the sender of the stop-request event. The stop-permitted event includes the date and time of arrival at the stop-permitted location Po, etc.

[0124] After controlling the output of the stop-by allowed event, the processor 11 proceeds to ACT 209. In ACT 209, the processor 11 acquires information about the product desired to be purchased from the stop-by request event. The information about the product desired to be purchased includes, for example, the product code, product name, and reservation quantity. After acquiring the information about the product desired to be purchased, the processor 11 proceeds to ACT 210. In ACT 210, the processor 11 adds a reservation record including the product code, product name, and reservation quantity of the product desired to be purchased to the reserved product table 136. In ACT 211, the processor 11 also subtracts the reservation quantity from the inventory quantity of the product desired to be purchased stored in the product database 134. With this, the processor 11 ends the information processing of the procedure shown in the flowchart of FIG. 17.

[0125] 16, the processor 31 of the user terminal 30 that controlled the output of the stop-in request event proceeds to ACT 111. In ACT 111, the processor 31 waits to receive a stop-in permitted event. In this waiting state, if a stop-in prohibited event is received via the wireless unit 34, the processor 31 proceeds to ACT 112. In ACT 112, the processor 31 displays information on the touch panel 36 indicating that the stop-in is not permitted.

[0126] On the other hand, if a stop-permitted event is received via the wireless unit 34, the processor 31 proceeds to ACT 113. In ACT 113, the processor 31 displays information indicating that the stop is permitted on the touch panel 36. For example, the date and time of arrival at the stop-permit location Po is displayed on the touch panel 36.

[0127] After completing the processing in ACT112 or ACT113, the processor 31 ends the information processing of the procedure shown in the flowchart of FIG.

[0128] FIG. 18 is a flow chart showing specific steps of the stop-by determination process. When the processor 11 enters the stop-by determination process in ACT205 of FIG. 17, the processor 11 proceeds to ACT221 of FIG. 18. In ACT221, the processor 11 acquires the desired stop-by date from the stop-by request event. In ACT222, the processor 11 checks whether the desired stop-by date is a mobile sales day. That is, the processor 11 detects the day of the week of the desired stop-by date and searches the mobile sales database 133 for that day of the week. As a result, if a departure time has been set for the day of the week of the desired stop-by date, the processor 11 determines that the desired stop-by date is a mobile sales day. If a departure time has not been set for the day of the week of the desired stop-by date, the processor 11 determines that the desired stop-by date is not a mobile sales day. If the desired stop-by date is not a mobile sales day, the processor 11 proceeds to ACT233. The processing of ACT233 will be described later.

[0129] On the other hand, if the desired stop-by date is a mobile sales day, the processor 11 proceeds to ACT 223. In ACT 223, the processor 11 checks whether or not a date-specific route table 135 for the desired stop-by date has already been created. If a date-specific route table 135 for the desired stop-by date has already been created, the processor 11 proceeds to ACT 224. In ACT 224, the processor 11 obtains the date-specific route table 135 for the desired stop-by date from the auxiliary storage device 13 or the main memory 12.

[0130] On the other hand, if the date-specific route table 135 for the desired stop date has not yet been created, the processor 11 proceeds to ACT 225. The processor 11 executes a route creation process in ACT 225. The route creation process is a process for creating the date-specific route table 135 for the desired stop date.

[0131] Figure 19 is a flow chart showing specific steps of the route creation process. When the processor 11 enters the route creation process in ACT 225 in Figure 18, it proceeds to ACT 241 in Figure 19. In ACT 241, the processor 11 acquires the day of the week on which the customer wishes to stop by. Next, in ACT 242, the processor 11 searches the mobile sales database 133 to acquire the departure time and basic route set for the day of the week on which the customer wishes to stop by. In the following explanation, for convenience, the basic route set for the day of the week on which the customer wishes to stop by is assumed to be "S → A → B → C → D → S."

[0132] The processor 11 acquires the number N of sales locations set in the basic route as ACT 243. That is, when the basic route is "S → A → B → C → D → S", sales location A, sales location B, sales location C, and sales location D are set, so the processor 11 acquires "4" as the number N of sales locations.

[0133] After completing the processing of ACT241 to ACT243, the processor 11 proceeds to ACT244. In ACT244, the processor 11 resets the counter n to "0". Then, in ACT245, the processor 11 creates a route record with the value of the counter n as the record number. The location name of the route record with record number "0" is the location that is the starting point of the basic route, that is, the location name "S" of the garage S. The latitude and longitude of the route record are the latitude and longitude of the garage S. Incidentally, the location name "S" and the latitude and longitude of the garage S are set in the sales location database 131. The departure time of the route record is the departure time obtained from the mobile sales database 133. Note that the route record with record number "0" does not include an arrival time.

[0134] After creating the route record with record number "0", the processor 11 proceeds to ACT 246. In ACT 246, the processor 11 counts up the counter n by "1". Then, in ACT 247, the processor 11 checks whether the counter n has exceeded the number N of sales locations.

[0135] At this point, counter n does not exceed the number of sales locations N. Therefore, processor 11 proceeds to ACT 248. Processor 11 acquires the nth sales location on the basic route in ACT 248. That is, since counter n is "1", processor 11 acquires sales location A, which stops next to garage S, as the first sales location.

[0136] After acquiring the n-th sales location, the processor 11 proceeds to ACT 249. In ACT 249, the processor 11 searches the required time database 132 to acquire the average required time for the mobile sales vehicle 1 to travel the route from the location specified by the location name of the route record with record number "n-1" to the n-th sales location. In other words, the processor 11 acquires the required time for the route from the garage S to the sales location A from the required time database 132.

[0137] After acquiring the required time for the route from garage S to sales location A, processor 11 proceeds to ACT250. In ACT250, processor 11 calculates the arrival time and departure time for the nth location. The arrival time is the time when the required time acquired in ACT249 and the specified stop grace time have elapsed from the departure time of the route record with record number "n-1". The departure time is the time when the sales time of the nth sales location set in sales location database 131 has elapsed from the arrival time.

[0138] After calculating the arrival time and departure time for the nth location, the processor 11 proceeds to ACT251. In ACT251, the processor 11 creates a route record with the value of counter n as the record number. That is, it creates a route record with record number "1". The location name of the route record is the location name of the nth sales location, that is, sales location A. The latitude and longitude of the route record are the latitude and longitude of sales location A. Incidentally, the location name "A" and the latitude and longitude of sales location A are set in the sales location database 131. The arrival time and departure time of the route record are the arrival time and departure time calculated in ACT250.

[0139] After creating the route record with record number "n", the processor 11 returns to ACT246. In ACT246, the processor 11 counts up the counter n by "1". If the counter n does not exceed the number N of points of sale, the processor 11 executes the processes of ACT247 to ACT251 in the same manner as described above.

[0140] Thus, processor 11 acquires sales location B, which stops next after sales location A, as the second sales location. Processor 11 then searches travel time database 132 to acquire the average travel time required for mobile sales vehicle 1 to travel the route from sales location A to sales location B. Processor 11 then calculates the arrival time and departure time for sales location B based on the travel time, the specified stop-over grace period, and the sales time of sales location B. Processor 11 then creates a route record for sales location B with record number "2."

[0141] Thereafter, the processor 11 repeatedly executes the processes of ACT246 to ACT251 until the counter n exceeds the number of points of sale N. As a result, the processor 11 creates a route record for point of sale C as a route record with record number "3", and creates a route record for point of sale D as a route record with record number "4".

[0142] In ACT247, when the counter n exceeds the number N of sales locations, the processor 11 proceeds to ACT252. In ACT252, the processor 11 searches the travel time database 132 to obtain the average travel time required for the mobile sales van 1 to travel the route from the sales location of the route record with record number "n-1" to the nth location. The nth location is the garage S. That is, the processor 11 obtains the travel time for the route from the sales location D to the garage S from the travel time database 132.

[0143] The processor 11 calculates the arrival time at the nth location in ACT 253. The arrival time is the time when the required time acquired in ACT 252 and the predetermined stop grace time have elapsed since the departure time of the route record with record number "n-1".

[0144] After calculating the arrival time at the nth location, the processor 11 proceeds to ACT254. In ACT254, the processor 11 creates a route record with the value of counter n as the record number. That is, it creates a route record with record number "5". The location name of the route record is the location name of the nth sales location, that is, garage S. The latitude and longitude of the route record are the latitude and longitude of garage S. The arrival time of the route record is the arrival time calculated in ACT253. Note that the route record, that is, the route record with record number "5", does not include a departure time.

[0145] After creating the route record with record number "5", the processor 11 proceeds to ACT255. In ACT255, the processor 11 saves the date-specific route table 135 in which the desired stop date is used as the date. That is, the processor 11 creates the date-specific route table 135 in which the route record with record number "0" created in the processing of ACT245, the route records with record numbers "1" to "4" created in the processing of ACT251, and the route record with record number "5" created in the processing of ACT254 are written in ascending order of record number, and saves this in the auxiliary storage device 13 or the main memory 12. With this, the processor 11 ends the route creation processing.

[0146] Returning to the description of FIG. After obtaining the created route table by date 135 for the desired stop date in ACT 224, or creating the route table by date 135 for the desired stop date in ACT 225, the processor 11 proceeds to ACT 226. In ACT 226, the processor 11 detects the latitude and longitude of the stop location Po from the information of the stop location Po included in the stop request event.

[0147] Next, the processor 11 compares the latitude and longitude of the garage S or sales locations A to D described in the date-specific route table 135 for the desired stop date as ACT227 with the latitude and longitude of the stop location Po, and determines the starting point Pf, which is upstream of the driving route that passes through the stop location Po, and the sales point Pr, which is downstream of the driving route that passes through the stop location Po.

[0148] Having determined the departure point Pf and the sales point Pr, the processor 11 proceeds to ACT228. In ACT228, the processor 11 cooperates with the map information server 50 to obtain the required time Tfo from the departure point Pf to the stop-off point Po and the required time Tor from the stop-off point Po to the sales point Pr. In ACT229, the processor 11 also refers to the date-specific route table 135 to obtain the departure time Tf from the departure point Pf. Similarly, in ACT230, the processor 11 refers to the date-specific route table 135 to obtain the arrival time Tt at the sales point Pr.

[0149] The processor 11 calculates the predicted arrival time Tx at the sales point Pr in ACT 231. That is, the processor 11 calculates the predicted arrival time Tx as the time when the required time Tfo, the required time Tor, and the stop-and-sell time Tn have elapsed since the departure time Tf from the departure point Pf.

[0150] In ACT232, the processor 11 compares the predicted arrival time Tx with the arrival time Tt at the sales point Pr. Here, if the predicted arrival time Tx is later than the arrival time Tt, the processor 11 proceeds to ACT233. In this way, the processor 11 proceeds to ACT233 if the desired stop-in date is not a mobile sales day (NO in ACT222) or if the predicted arrival time Tx is later than the arrival time Tt. In ACT233, the processor 11 determines that a stop-in at the stop-in location Po is permitted.

[0151] In ACT232, if the predicted arrival time Tx is before the arrival time Tt or if the predicted arrival time Tx is the same as the arrival time Tt, the processor 11 proceeds to ACT234. In ACT234, the processor 11 determines that a stop at the stop place Po is permitted. Then, in ACT235, the processor 11 updates the data in the date-specific route table 135 to data of a driving route that passes through the stop place Po. That is, a route record including the place name, latitude, longitude, arrival time, and departure time of the stop place Po is added to the date-specific route table 135. With the above, the processor 11 ends the stop-by determination process.

[0152] Here, the processor 11 of the mobile sales support server 10 realizes the function of the handled product notification means 61 by processing ACT201 to ACT203 in Figure 17. The processor 11 realizes the function of the stop-off location acquisition means 62 by processing ACT226 in Figure 18. The processor 11 realizes the function of the route identification means 63 by processing ACT227 and ACT228 in Figure 18. The processor 11 realizes the function of the arrival time prediction means 64 by processing ACT229 to ACT231 in Figure 18. The processor 11 realizes the function of the stop-off determination means 65 by processing ACT232 to ACT234 in Figure 18. The processor 11 realizes the function of the route determination means 66 by processing ACT235 in Figure 18. The processor 11 realizes the function of the product reservation means 67 by processing ACT209 and ACT210 in Figure 17. The processor 11 realizes the function of the inventory update means 68 by the processing of ACT211 in Fig. 17. The processor 11 realizes the function of the result notification means 69 by the processing of ACT206 to ACT208 in Fig. 17.

[0153] Figure 20 is an example of a date-specific route table 135-1 updated by the route determination means 66 when a stop is permitted for a stop request event in which the date in the date-specific route table 135 shown in Figure 10 is set as the desired stop date and a stop location Pa is specified as a location on the route from sales location C to sales location D.

[0154] For such a stop-by request event, the mobile sales support server 10, in cooperation with the map information server 50, calculates the required time Tfo from sales location C to stop-by location Pa and the required time Tor from stop-by location Pa to sales location D. Here, it is assumed that the required time Tfo is 15 minutes and the required time Tor is 30 minutes. In this case, since the departure time from sales location C is 13:00, the predicted arrival time at sales location D is 13:50, which is 50 minutes after adding the required time Tfo (15 minutes), the required time Tor (30 minutes), and the stop-by sales time Tn (5 minutes). Therefore, the predicted arrival time at sales location D, 13:50, is before the arrival time at sales location D, 15:55, so a stop at stop-by location Pa is permitted. As a result, a route record with record number "4" describing the location name of stopover point Pa, its latitude and longitude, arrival time, and departure time is added after the route record with record number "3" in the date-specific route table 135. In addition, the route records with record numbers "4" and "5" are updated to route records with record numbers "5" and "6", respectively.

[0155] Figure 21 is an example of a date-specific route table 135-2 updated by the route determination means 66 when a stop is permitted for a stop request event in which the date in the date-specific route table 135-1 shown in Figure 20 is set as the desired stop date and a stop location Pb is specified as a location on the route from sales location B to sales location C.

[0156] For such a stop-by request event, the mobile sales support server 10, in cooperation with the map information server 50, calculates the required time Tfo from sales location B to stop-by location Pb and the required time Tor from stop-by location Pb to sales location C. Here, assume that the required time Tfo is 20 minutes and the required time Tor is 25 minutes. In this case, since the departure time from sales location B is 11:40, the predicted arrival time at sales location C is 12:30, which is 50 minutes after adding the required time Tfo (20 minutes), the required time Tor (25 minutes), and the stop-by sales time Tn (5 minutes). Therefore, the predicted arrival time at sales location C, 12:30, is equal to the arrival time at sales location C, 12:30, so a stop at stop-by location Pb is permitted. As a result, a route record with record number "3" describing the place name, latitude, longitude, arrival time, and departure time of stop-off place Pb is added after the route record with record number "2" in the date-specific route table 135. In addition, the route records with record numbers "3" to "6" are updated to route records with record numbers "4" to "7", respectively.

[0157] For example, if the required time Tor from stopover point Pb to sales location C is 30 minutes, the predicted arrival time is 12:35. In other words, since this will be 5 minutes later than the arrival time at sales location C of 12:30, a stopover at stopover point Pb is not permitted. If a stopover is not permitted, the date-specific route table 135-1 is not updated.

[0158] In this regard, if it is considered that a delay of about 5 minutes in arrival time at the sales location will not hinder the mobile sales, the mobile sales person may be permitted to stop at the stop-off location Pb, and the date-specific route table 135-1 may be updated.

[0159] 22 shows a date-specific route table 135-3 after a stop is permitted for a stop request event in which the desired stop date is the date in the date-specific route table 135-1 shown in FIG. 20, and a new stop location Pc is specified along the route from sales location C, where a stop at stop location Pa has already been permitted, to sales location D. Note that this shows a case in which stop location Pc is located downstream of stop location Pa in the traveling direction.

[0160] For such a stop-by request event, the mobile sales support server 10, in cooperation with the map information server 50, calculates the required time Tfo from stop-by location Pa to stop-by location Pc and the required time Tor from stop-by location Pc to sales location D. Here, it is assumed that the required time Tfo is 10 minutes and the required time Tor is 20 minutes. In this case, since the departure time from stop-by location Pa is 13:20, the predicted arrival time at sales location D is 13:55, which is 35 minutes after adding the required time Tfo (10 minutes), the required time Tor (20 minutes), and the stop-by sales time (5 minutes). Therefore, the predicted arrival time at sales location D, 13:55, is equal to the arrival time at sales location D, 13:55, so a stop at stop-by location Pc is also permitted. As a result, a route record with record number "5" describing the location name, latitude, longitude, arrival time, and departure time of stop-off place Pc is added after the route record with record number "4" for stop-off place Pa in the date-specific route table 135. In addition, the route records with record numbers "5" and "6" are updated to route records with record numbers "6" and "7", respectively.

[0161] [Information processing explanation for the second function] Figures 23 and 24 are flowcharts showing the procedure of information processing executed by the processor 31 of the in-vehicle terminal 20 in accordance with the main program. Figures 25 to 27 are flowcharts showing the procedure of information processing executed by the processor 11 of the mobile sales support server 10 in accordance with the second mobile sales support program. Information processing related to the second function will be explained below with reference to Figures 23 to 27.

[0162] When the main program is launched, for example, by turning on the power, the processor 21 of the in-vehicle terminal 20 starts information processing according to the procedure shown in the flowchart of Fig. 23. First, the processor 21 controls the output of a travel route request event as ACT301. This control causes a signal of the travel route request event to be wirelessly transmitted via the wireless unit 24. This signal is received at an access point of the communication network 41 and transmitted to the mobile sales support server 10 via the communication network 41.

[0163] 25, the processor 11 of the mobile sales support server 10 waits for a driving route request event in ACT 401. When a driving route request event signal is received via the network interface 15, the processor 11 proceeds to ACT 402. The processor 11 detects the current date measured by the clock 14 in ACT 402.

[0164] Having detected the date, processor 11 proceeds to ACT403. Processor 11 references the date-specific route table 135 in which the date is set as ACT403, and acquires the driving route of the mobile sales vehicle 1. That is, processor 11 sets the location specified by the location name of the route record with record number "0", that is, garage S, as the starting point. Next, processor 11 sequentially acquires the location names of route records with record numbers "1" and above, stops at the sales locations or drop-off locations specified by the location names in ascending order of record numbers, and acquires a driving route that returns to the location specified by the location name of the route record with the largest record number, that is, garage S.

[0165] In principle, the date-specific route table 135 is created by the day before the mobile sales event. If a user 2 requests to stop by on the day before or even before, a date-specific route table 135 is created with the desired date of stop as the date.

[0166] After acquiring the driving route, the processor 11 proceeds to ACT404. In ACT404, the processor 11 controls the output of a driving route response event. By this control, a driving route response event signal including data on the driving route is transmitted from the network interface 15 to the in-vehicle terminal 20, which is the sender of the driving route request event. The driving route response event signal is wirelessly transmitted from a predetermined access point via the communication network 41, and is received by the in-vehicle terminal 20, which is the sender of the driving route request event.

[0167] In ACT301 of FIG. 23, the processor 21 of the in-vehicle terminal 20, which has controlled the output of the travel route request event, proceeds to ACT302. In ACT302, the processor 21 waits for a travel route response event. Then, when the processor 21 receives the travel route response event via the wireless unit 24, the processor 21 proceeds to ACT303. In ACT303, the processor 21 stores data of the travel route included in the travel route request event in the main memory 22. Then, in ACT304, the processor 21 displays an image SCa (see FIG. 28) indicating the travel route on the display 27. At this time, in ACT305, the processor 21 checks whether the travel route includes a stop. Then, if a stop is included, the processor 21 proceeds to ACT306. In ACT306, the processor 21 displays a stop mark M (see FIG. 28) on the image SCa of the travel route.

[0168] Fig. 28 is a display example of an image SCa showing a driving route. This image SCa shows a driving route created using the data in the date-specific route table 135-1 shown in Fig. 20. That is, the image SCa shows a driving route starting from garage S, stopping at sales location A, sales location B, sales location C, stop-by location Pa, and sales location D in that order, before returning to garage S, along with the arrival and departure times at each location. Furthermore, a stop-by mark M is displayed at stop-by location Pa. Therefore, the salesperson can not only check the driving route for the day from the image SCa on display 27, but also easily recognize that stop-by location Pa is included along the route.

[0169] After displaying the travel route, the processor 21 waits for the mobile sales vehicle 1 to depart in ACT 307. Although not shown, the in-vehicle terminal 20 is equipped with a sensor that detects the departure and stopping of the mobile sales vehicle 1. When the processor 21 detects the departure of the mobile sales vehicle 1, it proceeds to ACT 308. In ACT 308, the processor 21 controls the output of a departure notification event. By this control, a signal of the departure notification event is wirelessly transmitted via the wireless unit 24. This signal is received at an access point of the communication network 41 and transmitted to the mobile sales support server 10 via the communication network 41.

[0170] 25, the processor 11, which has controlled the output of the driving route response event, proceeds to ACT 405. In ACT 405, the processor 11 waits for a departure notification event. When the departure notification event is received via the network interface 15, the processor 11 proceeds to ACT 406. In ACT 406, the processor 11 communicates with the in-vehicle terminal 20 that sent the departure notification event, and detects the location information of the mobile sales vehicle 1 identified by the GPS receiver 25.

[0171] After detecting the location information of the mobile sales vehicle 1, the processor 11 proceeds to ACT 407. In ACT 407, the processor 11 identifies the next stop of the mobile sales vehicle 1 based on the location information of the mobile sales vehicle 1 and the travel route of the mobile sales vehicle 1. For example, if the location where the departure of the mobile sales vehicle 1 was detected was garage S and the next stop after garage S on the travel route was sales location A, the processor 11 identifies sales location A as the next stop.

[0172] After identifying the next stopping point, the processor 11 proceeds to ACT408. In ACT408, the processor 11 controls the output of a stop point notification event. By this control, a stop point notification event signal including information indicating the next stopping point is transmitted from the network interface 15 to the in-vehicle terminal 20, which is the sender of the call notification event. The stop point notification event signal is wirelessly transmitted from a predetermined access point via the communication network 41, and is received by the in-vehicle terminal 20, which is the sender of the call notification event.

[0173] In ACT 308 of Figure 23, the processor 21 of the in-vehicle terminal 20 that has output the departure notification event proceeds to ACT 309. In ACT 309, the processor 21 waits for a stop point notification event. When the stop point notification event is received via the wireless unit 24, the processor 21 proceeds to ACT 310. In ACT 310, the processor 21 updates the image SCa of the driving route displayed on the display 27 to an image SCb (see Figure 29) that enables the salesperson to identify the next stopping point.

[0174] FIG. 29 is an example of an updated image SCb when the next stop is sales location A. As shown in FIG. 29, the frame indicating sales location A is different from the frames indicating other stop locations. Thus, the salesperson can easily know that the next stop is sales location A. Note that the method of enabling the salesperson to identify the next stop is not limited to changing the type of frame. For example, the frame surrounding sales location A may be made identifiable by flashing it or by changing the color of the frame. Alternatively, the color of the sales location name displayed within the frame may be changed. Furthermore, similar to the stop mark M, the identification may be made possible by displaying a predetermined mark near the frame surrounding sales location A.

[0175] After displaying the stopping point, the processor 21 proceeds to ACT 311. In ACT 311, the processor 21 waits for the mobile sales vehicle 1 to be stopped for a predetermined time or longer. The predetermined time is, for example, a time to exclude detection of a stop due to waiting at a traffic light, and may be set to about one to two minutes. When it is detected that the mobile sales vehicle 1 has been stopped for a predetermined time or longer, the processor 21 proceeds to ACT 312. In ACT 312, the processor 21 controls the output of a stop notification event. By this control, a signal of the stop notification event is wirelessly transmitted via the wireless unit 24. This signal is received at an access point of the communication network 41 and transmitted to the mobile sales support server 10 via the communication network 41.

[0176] In ACT408 of Figure 25, the processor 11 of the mobile sales support server 10 that notified the stopping point proceeds to ACT409. In ACT409, the processor 11 waits for a stopping notification event. When the stopping notification event is received via the network interface 15, the processor 11 proceeds to ACT410. In ACT410, the processor 11 communicates with the in-vehicle terminal 20 that sent the stopping notification event, and detects the location information of the mobile sales vehicle 1 identified by the GPS receiver 25.

[0177] After detecting the location information of the mobile sales vehicle 1, the processor 11 proceeds to ACT411. In ACT411, the processor 11 checks whether the parking location of the mobile sales vehicle 1 is sales location A, B, C, or D. If the parking location of the mobile sales vehicle 1 is not sales location A, B, C, or D, the processor 11 checks whether the parking location of the mobile sales vehicle 1 is stop location Pa in ACT412. If the parking location of the mobile sales vehicle 1 is not stop location Pa either, the processor 11 checks whether the parking location of the mobile sales vehicle 1 is garage S in ACT413. If the parking location of the mobile sales vehicle 1 is not garage S either, the processor 11 returns to ACT405. In ACT405, the processor 11 waits for a departure notification event. In this way, when the mobile sales vehicle 1 stops for a predetermined period of time at a location that is not one of the garage S, sales locations A, B, C, D, or stop-off location Pa included in the driving route, the processor 11 waits for a departure notification event without performing any special processing.

[0178] When the mobile sales vehicle 1 stops at any of the sales locations A, B, C, or D, the processor 11 proceeds to ACT421 in Figure 26. In ACT421, the processor 11 controls the output of a registration mode notification event. By this control, a signal of the registration mode notification event is transmitted from the network interface 15 to the in-vehicle terminal 20, which is the sender of the stop point notification event. The signal of the registration mode notification event is transmitted wirelessly from a predetermined access point via the communication network 41, and is received by the in-vehicle terminal 20, which is the sender of the stop point notification event.

[0179] In ACT312 of Figure 23, the processor 21 of the in-vehicle terminal 20, which controlled the output of the stop point notification event, proceeds to ACT321 of Figure 24. The processor 21 checks whether or not a registration mode notification event has been received in ACT321. If a registration mode notification event has not been received, the processor 21 proceeds to ACT322. In ACT322, the processor 21 checks whether or not the departure of the mobile sales vehicle 1 has been detected. If the departure of the mobile sales vehicle 1 has not been detected, the processor 21 returns to ACT321. In this way, in ACT321 and ACT322, the processor 21 waits to receive a registration mode notification event or for the mobile sales vehicle 1 to depart.

[0180] In the standby state of ACT321 and ACT322, when the departure of the mobile sales vehicle 1 is detected, the processor 21 returns to ACT308 in Fig. 23. That is, the processor 21 controls the output of a departure notification event.

[0181] In the standby state of ACT321 and ACT322, when a registration mode notification event is received via the wireless unit 24, the processor 21 proceeds to ACT323. In ACT323, the processor 21 switches the screen of the display 27 to a registration screen. The registration screen is a screen for displaying the product name, price, etc. of the product identified by the barcode scanned by the scanner 26.

[0182] After switching the screen of the display 27 to the registration screen, the processor 21 proceeds to ACT 324. In ACT 324, the processor 21 checks whether or not a list of reserved items has been received. If the stopping point is sales location A, B, C, or D, the list of reserved items has not been received, so the processor 21 proceeds to ACT 326. In ACT 326, the processor 21 checks whether or not a barcode indicating a product code has been scanned by the scanner 26. If a barcode has not been scanned, the processor 21 proceeds to ACT 327. In ACT 327, the processor 21 checks whether or not the mobile sales vehicle 1 has departed. If the mobile sales vehicle 1 has not departed, the processor 21 returns to ACT 326. In this way, the processor 21 waits in ACT 326 and ACT 327 for the barcode to be scanned or for the mobile sales vehicle 1 to depart.

[0183] When a barcode is scanned in the standby state of ACT326 and ACT327, the processor 21 proceeds to ACT328. The processor 21 controls the output of a product registration request event in ACT328. By this control, a product registration request event signal is wirelessly transmitted via the wireless unit 24. This signal is received at an access point of the communication network 41 and transmitted to the mobile sales support server 10 via the communication network 41. The product registration request event includes data of the barcode scanned by the scanner 26. After controlling the output of the product registration request event, the processor 21 returns to the standby state of ACT326 and ACT327.

[0184] In the standby state of ACT326 and ACT327, when the processor 21 detects that the mobile sales vehicle 1 has started moving, the processor 21 proceeds to ACT329. In ACT329, the processor 21 erases the registration screen. As the registration screen is erased, the screen of the display 27 returns to the screen showing the image SCa of the travel route. After erasing the registration screen, the processor 21 returns to ACT308 in Figure 23. That is, the processor 21 controls the output of a start notification event.

[0185] In ACT421 of Figure 26, the processor 11, having controlled the output of the registration mode notification event, proceeds to ACT422. The processor 11 checks whether or not a product registration request event has been received in ACT422. If a product registration request event has not been received, the processor 11 proceeds to ACT423. The processor 11 checks whether or not a launch notification event has been received in ACT423. If a launch notification event has not been received, the processor 11 returns to ACT422. In this way, the processor 11 waits for the reception of a product registration request event or the reception of a launch notification event in ACT422 and ACT423.

[0186] In the standby state of ACT422 and ACT423, when a product registration request event is received via the network interface 15, the processor 11 proceeds to ACT424. The processor 11 executes product registration processing in ACT424. That is, the processor 11 acquires a product code from the barcode data included in the product registration request event, detects the product name and price of the product identified by the product code from the product database 134, and registers product sales data including the product code, product name, price, number of items sold, etc. in the main memory 12. The processor 11 also outputs the product registration event including the product sales data to the in-vehicle terminal 20, and causes the display 27 of the in-vehicle terminal 20 to display the product name, price, etc.

[0187] After executing the product registration process, the processor 11 proceeds to ACT425. In ACT425, the processor 11 updates the inventory. That is, the processor 11 subtracts the number of items sold from the inventory quantity of the product stored in the product database 134. After updating the inventory, the processor 11 returns to the standby state in ACT422 and ACT423.

[0188] When a departure notification event is received in the standby state of ACT422 and ACT423, the processor 11 returns to ACT406 in Fig. 25. That is, the processor 11 detects the location information of the mobile sales vehicle 1, and identifies the next stop point of the mobile sales vehicle 1 based on the location information and the travel route of the mobile sales vehicle 1. The processor 11 then controls the output of a stop point notification event.

[0189] Thus, when the mobile sales vehicle 1, which has the image SCa of the driving route shown in Figure 28 displayed on the display 27, finishes its mobile sales at sales location A and starts moving away, the image SCa of the driving route is updated to an image indicating that the next place the vehicle will stop is sales location B.

[0190] On the other hand, if the mobile sales vehicle 1 stops at stop-off location Pa, the processor 11 proceeds to ACT431 in Figure 27. The processor 11 creates a list of reserved items in ACT431. That is, the processor 11 searches the reserved item table 136 to extract the reservation record of the stop-off location Pa where the mobile sales vehicle 1 stops, and creates a list of reserved items that lists the product code, product name, and reservation quantity of the extracted reservation record.

[0191] Having created the reserved item list, processor 11 proceeds to ACT432. In ACT432, processor 11 controls the output of a reserved item notification event. This control causes a product list response event signal including the reserved item list to be transmitted from network interface 15 to in-vehicle terminal 20, the source of the vehicle stop notification event. The reserved item notification event is wirelessly transmitted from a predetermined access point via communication network 41 and received by in-vehicle terminal 20, the source of the vehicle stop notification event.

[0192] After controlling the output of the reserved item notification event, the processor 11 proceeds to ACT433. The processor 11 controls the output of a registration mode notification event as ACT433. By this control, a signal of the registration mode notification event is transmitted from the network interface 15 to the in-vehicle terminal 20, which is the sender of the stop point notification event. The signal of the registration mode notification event is wirelessly transmitted from a predetermined access point via the communication network 41, and is received by the in-vehicle terminal 20, which is the sender of the stop point notification event.

[0193] In this way, when the mobile sales vehicle 1 stops at sales locations A, B, C, and D, the processor 11 of the mobile sales support server 10 controls the transmission of a registration mode notification event in ACT421 of Fig. 26. On the other hand, when the mobile sales vehicle 1 stops at stop-off location Pa, the processor 11 of the mobile sales support server 10 controls the output of a reserved product notification event in ACT432 and ACT433 of Fig. 27, and then controls the transmission of a registration mode notification event.

[0194] Therefore, the processor 21 of the in-vehicle terminal 20 that has received the registration mode notification event in ACT 321 of Fig. 24 changes the screen of the display 27 to the registration screen, and then checks in ACT 324 whether or not a reserved item notification event has been received. Here, if the stopping location is stop-off location Pa, the reserved item notification event has been received, so the processor 21 proceeds to ACT 325. In ACT 325, the processor 21 obtains the reserved item list from the reserved item notification event, and displays an image SCb of the reserved item list (see Fig. 30) in a part of the registration screen of the display 27.

[0195] 30 is a display example of a reserved product list image SCb. The image SCb shows that the product to be purchased at the stop-off place Pa where the mobile sales van 1 is parked is "Product EEE" identified by product code "11111115" and that the reserved quantity is "1." Therefore, upon checking this image SCb, the salesperson can simply take one "Product EEE" from the products that have been reserved in advance and sell it to the user 2 who is waiting at the stop-off place Pa.

[0196] In ACT433 of Figure 27, the processor 11 of the mobile sales support server 10, which controlled the output of the registration mode notification event, proceeds to ACT434. The processor 11 checks whether or not a product registration request event has been received in ACT434. If a product registration request event has not been received, the processor 11 proceeds to ACT435. The processor 11 checks whether or not a departure notification event has been received in ACT435. If a departure notification event has not been received, the processor 11 returns to ACT434. In this way, the processor 11 waits to receive a product registration request event or a departure notification event in ACT434 and ACT435.

[0197] In the standby state of ACT434 and ACT435, when a product registration request event is received via the network interface 15, the processor 11 proceeds to ACT436. In ACT436, the processor 11 executes product registration processing.

[0198] After completing the product registration process, the processor 11 proceeds to ACT437. The processor 11 checks whether the registered product in ACT437 is included in the reserved product list. If the registered product is included in the reserved products, the processor 11 proceeds to ACT438. The processor 11 updates the inventory in ACT438. On the other hand, if the registered product is not included in the reserved products, the processor 11 does not update the inventory. Thereafter, the processor 11 returns to the standby state in ACT434 and ACT435.

[0199] When a departure notification event is received in the standby state of ACT434 and ACT435, the processor 11 returns to ACT406 in Fig. 25. That is, the processor 11 detects the location information of the mobile sales vehicle 1, and identifies the next stop point of the mobile sales vehicle 1 based on the location information and the travel route of the mobile sales vehicle 1. The processor 11 then controls the output of a stop point notification event.

[0200] Thus, when the mobile sales vehicle 1, which has the image SCa of the travel route shown in Figure 28 displayed on the display 27, finishes its mobile sales at the stopover point Pa and starts moving away, the image SCa of the travel route is updated to an image indicating that the next stop will be the sales point D.

[0201] In this way, when the mobile sales vehicle 1 stops at sales locations A, B, C, and D, the processor 11 of the mobile sales support server 10 determines YES in ACT411 of Fig. 25. That is, the processor 11 executes the processing of ACT421 to ACT425 shown in Fig. 26. On the other hand, when the mobile sales vehicle 1 stops at stop-off location Pa, the processor 11 determines YES in ACT412 of Fig. 25. That is, the processor 11 executes the processing of ACT431 to ACT438 shown in Fig. 27.

[0202] On the other hand, when the mobile sales vehicle 1 finishes sales at the sales location D and stops at the garage S, the processor 11 determines YES in ACT413 of Fig. 25. That is, the processor 11 ends the information processing described with reference to Fig. 25.

[0203] Here, the processor 11 of the mobile sales support server 10 realizes the function of the driving route acquisition means 71 by processing ACT401 to ACT403 in FIG. 25. The processor 11 realizes the function of the driving route notification means 72 by processing ACT404. The processor 11 realizes the function of the vehicle position acquisition means 73 by processing ACT405 and ACT406. The processor 11 realizes the function of the stopping point notification means 74 by processing ACT407 and ACT408. The processor 11 realizes the function of the stopping point determination means 75 by processing ACT409 to ACT413. The processor 11 realizes the function of the reserved product notification means 76 by processing ACT431 and ACT432 in FIG. 27. The processor 11 realizes the function of the product registration processing means 77 by processing ACT424 in FIG. 26 and ACT436 in FIG. 27. The processor 11 realizes the function of the inventory update means 78 by processing ACT425 in FIG. 26 and ACT438 in FIG.

[0204] As described above in detail, according to this embodiment, mobile sales can be used not only by residents who use designated sales locations, but also by residents who have difficulty traveling to the sales locations. Moreover, there is no risk of the mobile sales representative having to wait because the mobile sales representative has stopped at a location other than the designated sales location and is delayed in arriving at the original sales location. Therefore, a very useful mobile sales system can be constructed even in areas where there are few retail stores due to depopulation and aging.

[0205] [Other embodiments] However, the embodiment is not limited to this. For example, a person who wishes to stop by may register as a member in advance. When registering as a member, the place where the person wishes to stop by may also be registered in advance. By doing so, the person who wishes to stop by can avoid the trouble of specifying the place where the person wishes to stop by when applying for a stop.

[0206] In the above embodiment, the user 2 makes a request to stop by on a day before the desired stop date. The user 2 can also make a request to stop by on the day of the desired stop date. When making a request to stop by on the day of the desired stop date, input of the desired stop date can be omitted. If the stop request event does not include information about the desired stop date, the mobile sales support server 10 determines that the request is for a stop by on the day. The mobile sales support server 10 checks whether the stop location can be reached based on the driving route for the day, that is, whether stopping at the stop location will not delay the arrival time at the subsequent sales location. If a stop is possible, the mobile sales support server 10 updates the driving route for the day and notifies the in-vehicle terminal 20. When the driving route is updated, the in-vehicle terminal 20 changes the displayed driving route to the updated route. In this way, even if a stop request is made on the day, the salesperson can stop by the location and sell products to the user 2.

[0207] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0208] 1...Mobile sales vehicle, 2...User, 10...Mobile sales support server, 11...Processor, 12...Main memory, 13...Auxiliary storage device, 14...Clock, 15...Network interface, 16...Inter-server interface, 17...System transmission path, 20...In-vehicle terminal, 21...Processor, 22...Main memory, 23...Auxiliary storage device, 24...Wireless unit, 25...GPS receiver, 26...Scanner, 27...Display, 28...Printer, 29...System transmission path, 30...User terminal, 31...Processor, 32...Internal memory, 33...External memory, 34...Wireless unit, 35...GPS receiver, 36...Touch panel, 37...System transmission path, 41...Communication network, 42...Inter-server network, 50 ...Map information server, 61...Product handling notification means, 62...Stop-off location acquisition means, 63...Route identification means, 64...Arrival time prediction means, 65...Stop-off determination means, 66...Route determination means, 67...Product reservation means, 68...Inventory update means, 69...Result notification means, 71...Driving route acquisition means, 72...Driving route notification means, 73...Vehicle position acquisition means, 74...Stopping point notification means, 75...Stopping location determination means, 76...Reserved product notification means, 77...Product registration processing means, 78...Inventory update means, 100...Mobile sales support system, 131...Sales location database, 132...Travel time database, 133...Mobile sales database, 134...Product database, 135...Date-based route table, 136...Reserved product table.

Claims

1. a route specifying means for specifying a route from a departure point of the mobile sales vehicle to a sales point where the mobile sales vehicle will conduct the mobile sales, via a mobile sales stop-off point designated by a user; an arrival time prediction means for predicting an arrival time when the mobile sales vehicle, which departs from the departure point at a predetermined departure time, will arrive at the sales point along the route; a stop-in determination means for determining whether or not to permit a stop at the stop-in location by comparing the arrival time predicted by the arrival time prediction means with the sales start time at the sales point; a route determination means for determining a travel route of the mobile sales vehicle based on the determination result by the stop-by determination means; A mobile sales support device equipped with the above.

2. the stop-in determination means determines that a stop at the stop-in location is permitted if the arrival time is in time for the sales start time; 2. The mobile sales support device according to claim 1, wherein the route determination means determines a travel route from the departure point to the sales point via the stop-off location when a stop-off at the stop-off location is permitted.

3. a stop-off place acquisition means for acquiring a stop-off place desired by the user through communication with a user terminal used by the user; Further comprising:

2. The mobile sales support device according to claim 1, wherein said route specifying means specifies said route by determining said starting point and said sales point passing through said stop-off places acquired by said stop-off place acquisition means.

4. a result notification means for notifying the user terminal of a determination result made by the stop-by determination means; 4. The mobile sales support device according to claim 3, further comprising:

5. a vehicle position acquisition means for acquiring the position of the mobile sales vehicle by communicating with an on-board terminal mounted on the mobile sales vehicle; a stop point notifying means for notifying the on-board terminal of the next stop point of the mobile sales van based on the travel route determined by the route determining means and the position of the mobile sales van; 2. The mobile sales support device according to claim 1, further comprising:

6. A computer for a mobile sales support device that supports mobile sales by a mobile sales vehicle, a route specifying means for specifying a route from a departure point of the mobile sales vehicle to a sales point where the mobile sales vehicle will perform mobile sales, via mobile sales stopover points designated by a user; an arrival time prediction means for predicting an arrival time when the mobile sales vehicle, which departs from the departure point at a predetermined departure time, will arrive at the sales point along the route; a stop-in determination means for determining whether or not to permit a stop at the stop-in location by comparing the arrival time predicted by the arrival time prediction means with the sales start time at the sales point; and a route determination means for determining a travel route of the mobile sales vehicle based on the determination result by the stop-by determination means; A program to function as a

Images