Schedule management system and program

Abstract

To provide a schedule management system and program which allow for communication at a cost lower than a communication cost of short message service (SMS) when communicating with a terminal used by a driver of a carrying-in / out vehicle which carries in and out equipment and materials in a construction field.SOLUTION: A schedule management system 90 comprises: a terminal 30 which is mounted on a carrying-in / out vehicle for carrying in and out equipment and materials in a construction field or is held by a driver and to which a peculiar telephone number is given; and a schedule management server 10 which manages a schedule of carrying-in / out of equipment and materials by the carrying-in / out vehicle in the construction field. The schedule management server 10 comprises a transmission unit 11A which transmits, to the terminal 30, information urging to log in an application program which allows for push communication when logged in at preliminarily determined timing by SMS using the telephone number, and the terminal 30 comprises a presentation unit 31A which presents the information transmitted from the schedule management server 10.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a schedule management system and a program.

Background Art

[0002] Conventionally, the following technologies have existed as technologies related to a terminal such as a mobile terminal receiving various information from a server.

[0003] Patent Document 1 discloses an information distribution system aimed at providing an information distribution service that efficiently uses network resources.

[0004] This information distribution system is an information distribution system including a first server, a second server, and a terminal, wherein the first server includes means for storing summary content that is a summary of detailed content, and means for transmitting the summary content to the terminal, the second server includes means for storing the detailed content, and means for transmitting the detailed content to the terminal in response to an instruction from the terminal, and the terminal includes means for receiving the summary content from the first server, means for displaying the received summary content, means for instructing the second server to transmit detailed content corresponding to the received summary content, and means for receiving the detailed content corresponding to the received summary content from the second server.

[0005] Patent Document 2 discloses an information providing system aimed at enabling detailed information to be provided to a person possessing a terminal using an e-mail even if the destination of the e-mail is a small mobile terminal.

[0006] This information providing system includes: an email sending means for sending a request receiving email containing a request receiving means for receiving a request for information to be provided to a user mobile terminal capable of receiving and displaying an email; a destination receiving means for receiving a designation of a destination to which the information to be provided is to be sent; and an information sending means for sending the requested information to be provided to the designated destination when the information to be provided is requested via the request receiving means included in the request receiving email received and displayed by the user mobile terminal.

[0007] Patent Document 3 discloses a method for downloading an application aimed at enabling an application to be more easily downloaded and installed.

[0008] This method includes sensing an outgoing call from a mobile device to a preset incoming number, and when the outgoing call is sensed, sending a message for downloading an application to the mobile device, responding to a user gesture for the message, and downloading the application from an application server storing the application to the mobile device.

[0009] Patent Document 4 discloses a system aimed at promoting the download of an application without causing the user to perform troublesome operations.

[0010] This system is a system comprising a server that provides content via a network and a terminal that receives the content. When a first application for viewing the content is launched on the terminal, a link for guiding the installation of a second application is displayed within the execution screen. When the link is selected, an induction history transmission unit transmits to the server an induction history for identifying the terminal, the first application, and the second application. When the installation of the second application is completed and launched, an installation information notification unit notifies the server of installation information for identifying the terminal and the second application. The server includes an induction source identification unit that identifies the first application that induced the installation of the second application based on the induction history and the installation information, and a privilege granting unit that permits viewing of content for which there is no viewing right in the first application identified by the induction source identification unit.

Prior Art Documents

Patent Documents

[0011]

Patent Document 1

Patent Document 2

Patent Document 3

Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0012] By the way, in a schedule management system including a terminal used by a driver of a loading / unloading vehicle that transports materials and equipment in and out of a construction site, and a schedule management server that manages the schedule of transporting materials and equipment in and out of the construction site by the loading / unloading vehicle, it is assumed that frequent communication is performed from the schedule management server to the terminal. For example, it is communication for transmitting to the driver the scheduled use time of the loading / unloading gate, map information indicating the route to the loading / unloading gate, the state of the loading / unloading vehicle, etc.

[0013] On the other hand, many terminals are assigned a telephone number. In this case, since communication can be performed by SMS (Short Message Service) using the telephone number, when the above-mentioned driver uses a terminal with a telephone number assigned, it is possible to transmit various information from the schedule management server to the terminal by SMS.

[0014] However, if communication is performed only by SMS between the terminal used by the driver of the loading / unloading vehicle and the schedule management server, there is a problem that the burden of communication cost is large compared to the case of performing communication by push communication. In particular, in the case of a construction site for constructing a large-scale building, since there are many loading / unloading vehicles and many frequencies of loading / unloading are required, the communication cost will increase, and this problem is serious.

[0015] In addition, the technologies described in the above patent documents do not consider this problem and are powerless regarding this problem.

[0016] The present invention has been made in view of the above facts, and an object thereof is to provide a schedule management system and a program capable of enabling communication at a lower cost than the communication cost by SMS when communicating with a terminal used by a driver of a loading / unloading vehicle that transports materials and equipment in and out of a construction site.

Means for Solving the Problem

[0017] The scheduling management system according to the present invention described in claim 1 is a terminal mounted on a loading and unloading vehicle that performs loading and unloading of materials and equipment at a construction site or held by a driver of the loading and unloading vehicle, and to which a unique telephone number is assigned, and a scheduling management server that manages the schedule of loading and unloading of materials and equipment at the construction site by the loading and unloading vehicle. The scheduling management server transmits, at a predetermined timing, information for prompting the terminal to log in to an application program that enables push communication by logging in using the short message service using the telephone number. The terminal presents the information transmitted from the scheduling management server.

[0018] According to the scheduling management system according to the present invention described in claim 1, it includes a terminal mounted on a loading and unloading vehicle that performs loading and unloading of materials and equipment at a construction site or held by a driver of the loading and unloading vehicle, and to which a unique telephone number is assigned, and a scheduling management server that manages the schedule of loading and unloading of materials and equipment at the construction site by the loading and unloading vehicle. The scheduling management server transmits, at a predetermined timing, information for prompting the terminal to log in to an application program that enables push communication by logging in using the short message service using the telephone number. The terminal presents the information transmitted from the scheduling management server. As a result, the possibility of enabling push communication between the scheduling management server and the terminal can be increased. When communicating with the terminal used by the driver of the loading and unloading vehicle that performs loading and unloading of materials and equipment at the construction site, communication at a lower cost than the communication cost by SMS can be enabled.

[0019] The scheduling management system according to the present invention described in claim 2 is the scheduling management system described in claim 1, wherein the predetermined timing is a plurality of timings before the application program has not been logged in and before the scheduled loading and unloading time of the materials and equipment at the construction site.

[0020] According to the schedule management system according to the present invention described in claim 2, by setting a plurality of timings that are before the timing determined in advance, when there is no login to the application program, and before the scheduled loading and unloading time at the construction site of the equipment, compared with the case where the timing is set as a single timing, it is possible to increase the possibility that push communication can be performed after the scheduled loading and unloading time at the construction site of the equipment.

[0021] The schedule management system according to the present invention described in claim 3 is the schedule management system described in claim 2, wherein the plurality of timings are timings where the closer the position of the loading and unloading vehicle is to the loading and unloading gate, the more frequent the timings are.

[0022] According to the schedule management system according to the present invention described in claim 3, by setting a plurality of timings where the closer the position of the loading and unloading vehicle is to the loading and unloading gate, the more frequent the timings are, it is possible to more effectively prompt login to the application program.

[0023] The schedule management system according to the present invention described in claim 4 is the schedule management system described in claim 2 or claim 3, wherein the plurality of timings are timings where the closer the scheduled use time of the loading and unloading gate by the loading and unloading vehicle is, the more frequent the timings are.

[0024] According to the schedule management system according to the present invention described in claim 4, by setting a plurality of timings where the closer the scheduled use time of the loading and unloading gate by the loading and unloading vehicle is, the more frequent the timings are, it is possible to more effectively prompt login to the application program.

[0025] The schedule management system according to the present invention described in claim 5 is the schedule management system described in claim 1, wherein the application program has a function of acquiring position information indicating the position of the loading and unloading vehicle from the terminal and transmitting information about the loading and unloading vehicle obtained using the position information to the terminal by push communication.

[0026] According to the scheduling management system of the present invention described in claim 5, by making the application program a program having a function of acquiring position information indicating the position of the incoming and outgoing vehicle from the terminal and transmitting information regarding the incoming and outgoing vehicle obtained using the position information to the terminal by push communication, the transmission and reception of the position information and the information regarding the incoming and outgoing vehicle between the terminal and the scheduling management server can be performed by push communication.

[0027] The scheduling management system according to the present invention described in claim 6 is the scheduling management system described in claim 1, wherein the terminal is a mobile terminal.

[0028] According to the scheduling management system of the present invention described in claim 6, by making the terminal a mobile terminal, the communication frequency by push communication can be increased compared to the case where the terminal is a stationary type, and as a result, communication at low cost can be made more effectively possible.

[0029] The program according to the present invention described in claim 7 is a program executed by the scheduling management server in a scheduling management system including a terminal mounted on an incoming and outgoing vehicle that performs the incoming and outgoing of capital equipment and materials at a construction site or held by a driver of the incoming and outgoing vehicle and assigned a unique telephone number, and a scheduling management server that manages the schedule of the incoming and outgoing of capital equipment and materials at the construction site by the incoming and outgoing vehicle. The computer is made to execute a process of transmitting, at a predetermined timing, information prompting login to an application program that enables push communication by logging in to the terminal by short message service using the telephone number.

[0030] According to the program of the present invention described in claim 7, by sending information prompting login to an application program that enables push communication by logging in via the Short Message Service using a telephone number from a schedule management server to a terminal at a predetermined timing, when communicating with a terminal used by a driver of a loading / unloading vehicle that performs loading and unloading of materials and equipment at a construction site, communication at a lower cost than the communication cost by SMS can be enabled.

Effect of the Invention

[0031] As described above, according to the present invention, when communicating with a terminal used by a driver of a loading / unloading vehicle that performs loading and unloading of materials and equipment at a construction site, communication at a lower cost than the communication cost by SMS can be enabled.

Brief Description of the Drawings

[0032]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Mode for Carrying Out the Invention

[0033] Hereinafter, with reference to the drawings, embodiments for carrying out the present invention will be described in detail. In this embodiment, the schedule management system according to the present invention is held by a driver of a loading / unloading vehicle (hereinafter simply referred to as the "driver") that performs loading and unloading of materials and equipment at a construction site, and a mobile terminal (hereinafter simply referred to as the "terminal") to which a unique telephone number is assigned, and a schedule management server (hereinafter simply referred to as the "schedule management server") that manages the schedule of loading and unloading of materials and equipment at the construction site by the loading / unloading vehicle. A case where it is applied to a schedule management system including will be described. Here, in order to avoid complication, a case where materials and equipment are carried into the construction site by the loading / unloading vehicle will be described, but the same applies to the case where materials and equipment are carried out of the construction site by the loading / unloading vehicle.

[0034] First, with reference to FIG. 1, the configuration of the schedule management system 90 according to this embodiment will be described. FIG. 1 is a block diagram showing an example of the hardware configuration of the schedule management system 90 according to this embodiment.

[0035] As shown in FIG. 1, the schedule management system 90 according to this embodiment includes a schedule management server 10 and a plurality of terminals 30 that are each accessible to the network 80. Examples of the schedule management server 10 include information processing devices such as personal computers and server computers. Examples of the terminal 30 include portable terminals such as smartphones, tablet terminals, and PDAs (Personal Digital Assistants, portable information terminals). However, it is not limited to this form, and if it is possible to mount it on a loading / unloading vehicle, a form in which a stationary information processing device or the like is applied as the terminal 30 may be used. In this case, it is not necessary for the driver to hold the terminal 30.

[0036] The terminal 30 according to this embodiment is given a unique telephone number, and includes a CPU (Central Processing Unit) 31 as a processor, a memory 32 as a temporary storage area, a non-volatile storage unit 33, an input unit 34 such as a touch panel, a display unit 35 such as a liquid crystal display, and a medium reading / writing device (R / W) 36. Further, the terminal 30 includes a wireless communication unit 38 and a position detection unit 39. The CPU 31, the memory 32, the storage unit 33, the input unit 34, the display unit 35, the medium reading / writing device 36, the wireless communication unit 38, and the position detection unit 39 are connected to each other via a bus B3. The medium reading / writing device 36 reads information written in the recording medium 37 and writes information to the recording medium 37.

[0037] The storage unit 33 is realized by an HDD (Hard Disk Drive), an SSD (Solid State Drive), a flash memory, or the like. A terminal processing program 33A is stored in the storage unit 33 as a storage medium. The terminal processing program 33A is stored (installed) in the storage unit 33 when the recording medium 37 in which the program 33A is written is set in the medium reading / writing device 36 and the medium reading / writing device 36 reads the program 33A from the recording medium 37. The CPU 31 appropriately reads the terminal processing program 33A from the storage unit 33, expands it in the memory 32, and sequentially executes the processes included in the terminal processing program 33A.

[0038] Also, the position detection unit 39 is for detecting its own position and transmitting position information indicating the position. In this embodiment, a system using GPS (Global Positioning Systems) is applied as a system for detecting the position by the position detection unit 39, but the present invention is not limited to this. For example, a system using a beacon, a two-dimensional code, or atmospheric pressure may be applied as a system for detecting the position by the position detection unit 39.

[0039] On the one hand, the schedule management server 10 according to the present embodiment includes a CPU 11 as a processor, a memory 12 as a temporary storage area, a non-volatile storage unit 13, an input unit 14 such as a keyboard and a mouse, a display unit 15 such as a liquid crystal display, a medium reading / writing device 16, and a communication interface (I / F) unit 18. The CPU 11, the memory 12, the storage unit 13, the input unit 14, the display unit 15, the medium reading / writing device 16, and the communication I / F unit 18 are connected to each other via a bus B1. The medium reading / writing device 16 reads information written in the recording medium 17 and writes information to the recording medium 17.

[0040] The storage unit 13 is realized by an HDD, an SSD, a flash memory, or the like. In the storage unit 13 as a storage medium, a schedule management program 13A is stored. The schedule management program 13A is stored (installed) in the storage unit 13 when the recording medium 17 on which the program 13A is written is set in the medium reading / writing device 16 and the medium reading / writing device 16 reads the program 13A from the recording medium 17. The CPU 11 appropriately reads the schedule management program 13A from the storage unit 13, expands it in the memory 12, and sequentially executes the processes included in the schedule management program 13A.

[0041] In addition, a schedule management database 13B, a construction site information database 13C, and a terminal information database 13D are stored in the storage unit 13. Details of the schedule management database 13B, the construction site information database 13C, and the terminal information database 13D will be described later.

[0042] Next, with reference to FIG. 2, the functional configuration of the schedule management system 90 according to the present embodiment will be described. FIG. 2 is a block diagram showing an example of the functional configuration of the schedule management system 90 according to the present embodiment.

[0043] As shown in FIG. 2, the schedule management server 10 according to the present embodiment includes a transmission unit 11A. The CPU 11 of the schedule management server 10 functions as the transmission unit 11A by executing a schedule management program 13A. Further, the terminal 30 according to the present embodiment includes a presentation unit 31A. The CPU 31 of the terminal 30 functions as the presentation unit 31A by executing a terminal processing program 33A.

[0044] The transmission unit 11A of the schedule management server 10 according to the present embodiment transmits, at a predetermined timing, information prompting login to an application program that enables push communication by logging in to the terminal 30 via a short message service using a telephone number previously assigned to the terminal 30.

[0045] On the other hand, the presentation unit 31A of the terminal 30 according to the present embodiment presents the information transmitted from the schedule management server 10. In the present embodiment, as the presentation of information by the presentation unit 31A of the terminal 30, presentation by display using the display unit 35 is applied, but the present invention is not limited to this. For example, presentation by voice or presentation by both voice and display may be applied as the presentation of information by the presentation unit 31A.

[0046] Here, in the schedule management system 90 according to the present embodiment, as the above-mentioned predetermined timing, a plurality of timings before the loading / unloading scheduled time at the construction site of the equipment, where the application program has not been logged in, are applied. In the schedule management system 90 according to the present embodiment, as the above-mentioned plurality of timings, the timings at 15:00 on the day before the loading / unloading scheduled date, 6:00 on the loading / unloading scheduled date, 3 hours before the loading / unloading scheduled time, 2 hours before, and 1 hour before are applied.

[0047] As described above, in the schedule management system 90 according to this embodiment, as the plurality of timings, timings that increase as the scheduled use time of the access gate by the access vehicle approaches are applied, but it is not limited to this. For example, as the plurality of timings, a form may be applied in which timings that increase as the position of the access vehicle is closer to the access gate are applied.

[0048] Further, in the schedule management system 90 according to this embodiment, as the application program, a program having a function of acquiring position information indicating the position of the access vehicle from the terminal 30 and transmitting information regarding the access vehicle obtained using the position information to the terminal 30 by push communication is applied. Thereby, in the schedule management system 90 according to this embodiment, when the driver logs in to the above application program on the terminal 30, the above-described position information and the exchange between the schedule management server 10 and the terminal 30 of the information obtained using the position information can be performed by push communication by the application program. Thereby, compared with the case where all communication between the schedule management server 10 and the terminal 30 is performed by SMS, the communication cost can be significantly suppressed.

[0049] FIG. 3 is a schematic diagram showing the overall processing flow in the schedule management system 90 according to this embodiment.

[0050] As shown in FIG. 3, in the schedule management system 90 according to this embodiment, first, a reserving person such as the foreman of the driver reserves the use of the gate used when the driver transports capital equipment to the construction site. At this time, the reserving person also registers the phone number of the terminal 30 used by the driver.

[0051] In response, the schedule management server 10 of the schedule management system 90 issues a temporary account to the driver, and by means of SMS using the registered phone number, notifies the terminal 30 that a temporary account has been issued, prompts the change of the temporary password, indicates that push communication becomes possible by logging in, and notifies a message prompting the download (installation) and login of the above-described application program (hereinafter referred to as "app") for performing the process of managing the schedule of the incoming and outgoing vehicles.

[0052] In response, the driver changes the password using the terminal 30 held by himself / herself, downloads the above app, and then performs the first login to the app.

[0053] As a result of being able to obtain the device information of the terminal 30 and the like through this first login, the schedule management server 10 can subsequently perform push notifications to the terminal 30.

[0054] Therefore, when the driver logs in to the above app on the day of the scheduled date of the incoming and outgoing of capital equipment and materials, etc., the schedule management server 10 acquires position information indicating the position of the terminal 30 held by the driver from the terminal 30, and performs a display corresponding to the position information to the terminal 30 by push notification.

[0055] FIG. 4 is a diagram showing the flow of processing in chronological order in the schedule management system 90 according to the present embodiment.

[0056] As shown in FIG. 4, in the processing according to the present embodiment, first, by the day before the scheduled date of the incoming and outgoing at the construction site of the capital equipment and materials, the reserving person reserves the use of the gate as described above.

[0057] In response, the schedule management server 10 issues a temporary account on the day before the scheduled date of the incoming and outgoing (in the present embodiment, 15:00 on the day before), and notifies the terminal 30 held by the corresponding driver of the various types of information described above by SMS.

[0058] Accordingly, the driver uses the terminal 30 to change the password, download (install) the application, and perform the first login to the application as described above. As described above, the scheduling management server 10 can then perform push notifications to the terminal 30.

[0059] Therefore, when the driver performs the first login, the scheduling management server 10 performs a notification (hereinafter referred to as a "reservation confirmation notification") for checking the reservation status by push notification at 15:00 on the day before the scheduled date of loading / unloading (in this embodiment).

[0060] On the other hand, the scheduling management server 10, at 6:00 on the day of the scheduled date of loading / unloading (in this embodiment), if the password has not been changed by the previous day, notifies the terminal 30 held by the driver of the above various types of information by SMS.

[0061] Also, the scheduling management server 10 performs a reservation confirmation notification by SMS if the password has not been changed, and by push notification if the password has been changed, at 6:00 on the day of the scheduled date of loading / unloading (in this embodiment).

[0062] Furthermore, the scheduling management server 10, at 3 hours before, 2 hours before, and 1 hour before the scheduled loading time on the scheduled date of loading / unloading, if the password has not been changed, notifies the application to prompt login by SMS, and if the password has been changed, by push notification.

[0063] Accordingly, the driver logs in to the application using the terminal 30. Thereafter, the terminal 30 appropriately acquires position information indicating its own position and transmits it to the scheduling management server 10.

[0064] Next, referring to FIG. 5, the schedule management database 13B according to the present embodiment will be described. FIG. 5 is a schematic diagram showing an example of the configuration of the schedule management database 13B according to the present embodiment.

[0065] As shown in FIG. 5, the schedule management database 13B according to the present embodiment stores information on each of a company, a schedule, a vehicle ID (Identification), a construction site, a loading / unloading gate, a scheduled arrival time, and an arrival completion time.

[0066] The above-mentioned company is information indicating the name of the company that undertakes the loading and unloading of capital equipment and materials targeted by the schedule management system 90. The above-mentioned schedule is information indicating the day on which the corresponding company conducts the loading of capital equipment and materials to the construction site. Also, the above-mentioned vehicle ID is information for individually identifying each of the loading / unloading vehicles belonging to the corresponding company, and is information allocated in advance as being different for each of the loading / unloading vehicles. Further, the above-mentioned construction site is information indicating the name of the construction site where the corresponding loading / unloading vehicle loads capital equipment and materials in the corresponding company, and the above-mentioned loading / unloading gate is information indicating the name of the loading / unloading gate used when the corresponding loading / unloading vehicle enters the corresponding construction site.

[0067] Also, the above-mentioned scheduled arrival time and the above-mentioned arrival completion time are information indicating the scheduled arrival time and the scheduled completion time of the loading of capital equipment and materials, respectively, when the corresponding loading / unloading vehicle uses the corresponding loading / unloading gate.

[0068] In the example shown in FIG. 5, the loading / unloading vehicle belonging to Company A and assigned the vehicle ID "A001" is registered to perform the loading of capital equipment and materials at 10:00 as the scheduled arrival time and 11:00 as the arrival completion time on February 25, 2023, via the north gate of the construction site of Factory A.

[0069] Therefore, the company, schedule, vehicle ID, construction site, loading / unloading gate, scheduled arrival time, and arrival completion time in the schedule management database 13B are all information registered in advance.

[0070] In the scheduling management system 90 according to this embodiment, the information on the company, schedule, vehicle ID, construction site, and loading / unloading gate is registered by the person in charge of the corresponding company, and the information on the scheduled arrival time and the completion time of arrival is registered by the above-mentioned booker. However, the present invention is not limited to this case. For example, some or all of this information may be registered by an administrator or the like of the scheduling management server 10.

[0071] Next, with reference to FIG. 6, the construction site information database 13C according to this embodiment will be described. FIG. 6 is a schematic diagram showing an example of the configuration of the construction site information database 13C according to this embodiment.

[0072] As shown in FIG. 6, the construction site information database 13C according to this embodiment stores information on the construction site, construction work content, loading / unloading gate, and location information.

[0073] The above construction site and the above loading / unloading gate are the same information as the construction site and the loading / unloading gate in the scheduling management database 13B, respectively. The above construction work content is information indicating the content of the construction work carried out at the corresponding construction site, and the above location information is information indicating the location of the corresponding loading / unloading gate at the corresponding construction site. In this embodiment, as the location information, information in the same coordinate system as the location information obtained by the location detection unit 39 provided in the terminal 30 (in this embodiment, information indicating latitude and longitude) is applied, but the present invention is not limited to this. For example, a coordinate value in a predetermined coordinate system with a predetermined point in the area to be managed in the scheduling management system 90 (in this embodiment, the Kanto region) as the origin may be applied as the location information indicating the location of the loading / unloading gate.

[0074] In the scheduling management system 90 according to this embodiment, the case where each piece of information in the construction site information database 13C is registered by the administrator of the scheduling management server 10 will be described, but it goes without saying that the present invention is not limited to this.

[0075] Next, referring to FIG. 7, the terminal information database 13D according to the present embodiment will be described. FIG. 7 is a schematic diagram showing an example of the configuration of the terminal information database 13D according to the present embodiment.

[0076] As shown in FIG. 7, the terminal information database 13D according to the present embodiment stores information such as a terminal ID, a telephone number, an account, a password, and a login flag.

[0077] The above terminal ID is information for individually identifying each of the terminals 30, and is information assigned in advance as different for each of the terminals 30. The above telephone number is information indicating a telephone number pre-assigned to the corresponding terminal 30, and the above account is information indicating an account assigned to the corresponding terminal 30. Further, the above password is information indicating a password registered by the driver who holds the corresponding terminal 30, and the above login flag is information indicating whether or not the first login to the application has been performed on the corresponding terminal 30. As shown in FIG. 7, in the present embodiment, a hyphen ("-") is registered by default as information indicating the login flag when the first login to the application has not been performed, but it goes without saying that it is not limited to this. Also, as shown in FIG. 7, in the present embodiment, fixed information ("12345678" in the example shown in FIG. 7) is registered by default as information indicating the password, but it goes without saying that it is not limited to this.

[0078] In the schedule management system 90 according to the present embodiment, the terminal ID and the telephone number in the terminal information database 13D will be described for the case where the above-described reserving person registers, but it goes without saying that it is not limited to this.

[0079] Next, with reference to FIGS. 8 to 22, the operation of the schedule management system 90 according to the present embodiment will be described. In the schedule management system 90 according to the present embodiment, the schedule management program 13A is composed of three types of programs: a first schedule management program that executes a first schedule management process, a second schedule management program that executes a second schedule management process, and a third schedule management program that executes a third schedule management process. Here, in order to avoid complication, a case where the schedule management database 13B, the construction site information database 13C, and the terminal information database 13D have already been constructed will be described.

[0080] First, with reference to FIG. 8, the operation of the schedule management server 10 when executing the first schedule management process according to the present embodiment will be described. When the CPU 11 of the schedule management server 10 executes the first schedule management program, the first schedule management process shown in FIG. 8 is executed. The first schedule management process shown in FIG. 8 is executed at 15:00 on the day before the schedule for which the scheduled arrival time is registered in the schedule management database 13B and at 6:00 on the day of the schedule for each of the transfer vehicles in which the driver holding the terminal 30 rides, targeting each of the terminals 30 whose terminal ID is registered in the terminal information database 13D. Here, the terminal 30 targeted for processing is referred to as the "processing target terminal".

[0081] In step 100 of FIG. 8, the CPU 11 determines whether information indicating the phone number corresponding to the processing target terminal (hereinafter referred to as the "target phone number") is already registered in the terminal information database 13D. If the determination is negative, the first schedule management process ends without giving any notification to the processing target terminal. On the other hand, if the determination in the process of step 100 is affirmative, the process proceeds to step 102.

[0082] In step 102, the CPU 11 determines whether information indicating an account corresponding to the terminal to be processed is already registered in the terminal information database 13D. If a negative determination is made, the process proceeds to step 104. In step 104, the CPU 11 temporarily issues an account for the terminal to be processed, registers it as information indicating the corresponding account in the terminal information database 13D, and then proceeds to step 108.

[0083] On the other hand, if an affirmative determination is made in the process of step 102, the process proceeds to step 106. In step 106, the CPU 11 determines whether information indicating a password corresponding to the terminal to be processed in the terminal information database 13D has been changed. If a negative determination is made, the process proceeds to step 108.

[0084] In step 108, the CPU 11 notifies the target telephone number by SMS to display a predetermined first display screen, and then ends this first schedule management process.

[0085] FIG. 11 shows an example of the first display screen 35A displayed on the display unit 35 of the terminal to be processed in response to the process of step 108. As shown in FIG. 11, on the first display screen 35A, a message indicating that a temporary account has been issued and a message prompting password setting are displayed. Therefore, when the first display screen 35A is displayed, the driver specifies the displayed URL (Uniform Resource Locator) to set the password.

[0086] When the driver specifies the above URL, a web page screen shown in FIG. 12 is displayed on the display unit 35 of the processing target terminal. As shown in FIG. 12, on this web page screen, the target telephone number is displayed, and a message prompting the input of a password after confirmation of the target telephone number, and an input area for the password are displayed. When this web page screen is displayed, the driver checks that the displayed telephone number matches the telephone number assigned to the processing target terminal, then inputs the password, and then specifies the save button. Note that on the web page screen shown in FIG. 12, in order to indicate that the telephone number is to be input when logging in to the application, a cautionary note "※ When logging in to the application, enter in the UserID field" is displayed directly below the display area of the target telephone number.

[0087] When the driver specifies the save button, a pop-up screen shown in FIG. 13 is displayed on the display unit 35 of the processing target terminal. As shown in FIG. 13, on this pop-up screen, a message indicating a warning is displayed. The driver specifies the OK button when registering the password entered on the web page screen shown in FIG. 12, while specifying the cancel button when not registering the password.

[0088] When the driver specifies the OK button, the CPU 11 stores (updates) the input password in the corresponding storage area of the terminal information database 13D, and performs the main registration of the account for the processing target terminal. At this time, the CPU 11 also notifies the target telephone number of a display screen with a URL for downloading the application by SMS.

[0089] On the other hand, at this time, as an example, the Web page screen shown in FIG. 14 is displayed on the display unit 35 of the processing target terminal. As shown in FIG. 14, on this Web page screen, a message indicating that the main registration of the account has been completed is displayed, together with a message prompting the download of the application. Therefore, the driver specifies the URL for downloading the application displayed in the SMS and downloads the application. In addition, when the cancel button is specified by the driver on the pop-up screen shown in FIG. 13, the CPU 11 prompts the driver to input the password again by displaying the Web page screen shown in FIG. 12 again.

[0090] In addition, on the first display screen 35A shown in FIG. 11, since it is conceivable that a reserving person such as a foreman may register an incorrect phone number, a message prompting that an unrelated person should not access the URL is also displayed for unrelated persons.

[0091] Also, on the first display screen 35A shown in FIG. 11, when the application cannot be used because the processing target terminal is a terminal other than a smartphone, the URL (hereinafter referred to as the "delivery stop URL") specified when stopping the SMS delivery is displayed in order to stop the delivery. Therefore, when the processing target terminal is other than a smartphone, the driver specifies the delivery stop URL.

[0092] When the delivery stop URL is specified by the driver, as an example, the Web page screen shown in FIG. 15 is displayed on the display unit 35 of the processing target terminal. As shown in FIG. 15, on this Web page screen, the target phone number is displayed, and after confirming the target phone number, a message prompting the registration of the stop of SMS delivery is displayed. When this Web page screen is displayed, the driver confirms that the displayed phone number matches the phone number assigned to the processing target terminal and then specifies the registration button.

[0093] When the driver designates the registration button, a pop-up screen shown in FIG. 16, for example, is displayed on the display unit 35 of the processing target terminal. As shown in FIG. 16, in this pop-up screen, a message indicating that attention is being called is displayed. When the driver wishes to stop the SMS delivery to the phone number confirmed on the web page screen shown in FIG. 15, the driver designates the OK button. On the other hand, when the driver does not wish to stop the SMS delivery, the driver designates the cancel button.

[0094] When the driver designates the OK button, the CPU 11 performs a process of setting not to perform SMS delivery to the subsequent target phone numbers.

[0095] On the other hand, when the driver designates the OK button, a web page screen shown in FIG. 17, for example, is displayed on the display unit 35 of the processing target terminal. As shown in FIG. 17, in this web page screen, a message indicating that SMS delivery to the target phone number will not be performed hereafter is displayed. Therefore, the driver can grasp that the SMS delivery has been stopped.

[0096] On the other hand, if an affirmative determination is made in the process of step 106 in FIG. 8, the process proceeds to step 110. In step 110, the CPU 11 determines whether the login flag corresponding to the processing target terminal in the terminal information database 13D indicates that the first login has been performed. If a negative determination is made, the process proceeds to step 112.

[0097] In step 112, the CPU 11 notifies the target phone number by SMS to display a predetermined second display screen, and then ends this first scheduled management process.

[0098] FIG. 18 shows an example of the second display screen 35B displayed on the display unit 35 of the processing target terminal in response to the process of step 112.

[0099] As shown in FIG. 18, on the second display screen 35B, information indicating a schedule corresponding to the driver who holds the processing target terminal (hereinafter referred to as "reservation information") is displayed, and a URL for downloading the application is displayed. Therefore, when the driver downloads the application, the driver specifies the URL and performs an operation for downloading the application.

[0100] Also, on the second display screen 35B, a URL for logging in to the application is displayed. Therefore, when the driver logs in to the application, the driver specifies the URL and performs an operation for logging in to the application. When the driver logs in to the application, the CPU 11 updates the corresponding login flag in the terminal information database 13D to information indicating that the login has been performed.

[0101] On the other hand, when an affirmative determination is made in the process of step 110, that is, when the first login to the application has been completed, the process proceeds to step 114, and the CPU 11 causes the processing target terminal to display a predetermined third display screen by push communication, and then ends this first schedule management process.

[0102] FIGS. 19 to 21 each show an example of the third display screens 35C1 to 35C3 displayed on the display unit 35 of the processing target terminal according to the process of step 114.

[0103] As shown in FIG. 19, on the third display screen 35C1, information regarding the schedule related to the driver who holds the processing target terminal is displayed, and a message prompting the driver to log in to the application two hours before the reservation time is displayed. When the third display screen 35C1 is displayed, if the driver wants to display more detailed information, the driver designates the display area of the third display screen 35C1. In response to the designation, a web page screen shown in the center or the right end of FIG. 19 is displayed on the display unit 35 of the processing target terminal as an example. Therefore, the driver can check his / her detailed schedule.

[0104] Also, as shown in FIG. 20, on the third display screen 35C2, information indicating that the schedule for the driver who holds the processing target terminal has been changed is displayed. When the third display screen 35C2 is displayed, if the driver wants to display more detailed information, the driver designates the display area of the third display screen 35C2. In response to the designation, a web page screen shown at the right end of FIG. 20 is displayed on the display unit 35 of the processing target terminal, for example. Therefore, the driver can confirm the schedule regarding himself / herself after the change.

[0105] Furthermore, as shown in FIG. 21, on the third display screen 35C3, information indicating that the schedule for the driver who holds the processing target terminal has been deleted is displayed. When the third display screen 35C3 is displayed, if the driver wants to display more detailed information, the driver designates the display area of the third display screen 35C3. In response to the designation, a web page screen shown at the right end of FIG. 21 is displayed on the display unit 35 of the processing target terminal, for example. Therefore, the driver can confirm the deleted schedule regarding himself / herself.

[0106] Next, with reference to FIG. 9, the operation of the schedule management server 10 when executing the second schedule management process according to the present embodiment will be described. By the CPU 11 of the schedule management server 10 executing the second schedule management program, the second schedule management process shown in FIG. 9 is executed. The second schedule management process shown in FIG. 9 is executed three hours before the scheduled arrival time on the day of the schedule for which the scheduled arrival time is registered in the schedule management database 13B, for each of the terminals 30 whose terminal IDs are registered in the terminal information database 13D, regarding the loading / unloading vehicle in which the driver who holds the terminal 30 rides. Here too, the terminal 30 to be processed is referred to as the "processing target terminal".

[0107] In step 200 of FIG. 9, the CPU 11 determines whether or not the information indicating the password corresponding to the processing target terminal in the terminal information database 13D has been changed, in the same manner as the process in step 106 of the first schedule management process. If the determination is negative, the process proceeds to step 202.

[0108] In step 202, the CPU 11 notifies, by SMS, the telephone number of the processing target terminal, that is, the target telephone number, to display a predetermined first display screen in the same manner as the processing in step 108 of the first schedule management process, and then ends this second schedule management process.

[0109] On the other hand, if an affirmative determination is made in the process of step 200, the process proceeds to step 204. In the same manner as the process in step 110 of the first schedule management process, the CPU 11 determines whether or not the login flag corresponding to the processing target terminal in the terminal information database 13D indicates that the first login has been completed. If a negative determination is made, the process proceeds to step 206.

[0110] In step 206, the CPU 11 notifies, by SMS, the target telephone number to display a predetermined second display screen in the same manner as the processing in step 112 of the first schedule management process, and then ends this second schedule management process.

[0111] On the other hand, if an affirmative determination is made in the process of step 204, the second schedule management process ends without performing any process.

[0112] Next, with reference to FIG. 10, the operation of the schedule management server 10 when executing the third schedule management process according to this embodiment will be described. By the CPU 11 of the schedule management server 10 executing the third schedule management program, the third schedule management process shown in FIG. 10 is executed. The third schedule management process shown in FIG. 10 is executed at two hours before and one hour before the scheduled arrival time on the day of the schedule for which the scheduled arrival time is registered in the schedule management database 13B for each of the terminals 30 whose terminal IDs are registered in the terminal information database 13D, for the loading / unloading vehicle in which the driver who holds the terminal 30 rides. Here too, the terminal 30 to be processed is referred to as the "processing target terminal".

[0113] In step 300 of FIG. 10, the CPU 11 determines, in the same manner as the process of step 106 of the first schedule management process, whether or not the information indicating the password corresponding to the processing target terminal in the terminal information database 13D has been changed. If the determination is negative, the process proceeds to step 302.

[0114] In step 302, the CPU 11 notifies, by SMS, the telephone number of the processing target terminal, that is, the target telephone number, to display a predetermined first display screen, in the same manner as the process of step 108 of the first schedule management process, and then ends this third schedule management process.

[0115] On the other hand, if the determination in the process of step 300 is affirmative, the process proceeds to step 304. The CPU 11 determines, in the same manner as the process of step 110 of the first schedule management process, whether or not the login flag corresponding to the processing target terminal in the terminal information database 13D indicates that the first login has been performed. If the determination is negative, the process proceeds to step 306.

[0116] In step 306, the CPU 11 notifies, by SMS, the target telephone number to display a predetermined second display screen, in the same manner as the process of step 112 of the first schedule management process, and then ends this third schedule management process.

[0117] On the other hand, if the determination in the process of step 304 is affirmative, the process proceeds to step 308. The CPU 11 determines at this time whether or not the application is logged in on the processing target terminal. If the determination is affirmative, this third schedule management process is ended. If the determination is negative, the process proceeds to step 310.

[0118] In step 310, the CPU 11 causes the processing target terminal to display a predetermined fourth display screen by push communication, and then ends this third schedule management process.

[0119] FIG. 22 shows an example of a fourth display screen 35D displayed on the display unit 35 of the processing target terminal in response to the process of step 310.

[0120] As shown in FIG. 22, on the fourth display screen 35D, a message indicating that the time for implementing the schedule related to the driver who holds the processing target terminal is approaching and prompting the driver to log in to the application is displayed. When the fourth display screen 35D is displayed, if the driver is to log in to the application, the driver designates the display area of the fourth display screen 35D. In response to the designation, a web page screen, shown in the center of FIG. 22 as an example, is displayed on the display unit 35 of the processing target terminal. Therefore, the driver can log in to the application via this screen. At this time, as shown on the right end of FIG. 22, after the login, information indicating the driver's schedule may be displayed. When the driver logs in to the application, the CPU 11 sets the information indicating the corresponding login flag in the terminal information database 13D as information indicating that the login has been performed.

[0121] Note that in the second schedule management process shown in FIG. 9, the processes after step 308 of the third schedule management process shown in FIG. 10 are not included because it is desired to strongly encourage the driver to log in to the application two hours before the scheduled arrival time, while such login is not required at earlier stages. That is, in the schedule management system 90 according to the present embodiment, after two hours before the scheduled arrival time, position information indicating the position of the loading / unloading vehicle is acquired, and various processes using the position information are executed.

[0122] Also, in the above processes, the display of various screens on the display unit 35 of the processing target terminal and the exchange of various information with the schedule management server 10 are performed in cooperation with the processes of the terminal processing program 33A executed by the CPU 31 of the processing target terminal.

[0123] As described above, according to the present embodiment, the schedule management server transmits to the terminal information for prompting login to an application program that enables push communication by logging in via the Short Message Service using a telephone number at a predetermined timing, and the terminal presents the information transmitted from the schedule management server. Therefore, the possibility of enabling push communication between the schedule management server and the terminal can be increased. As a result, when communicating with the terminal used by the driver of the loading / unloading vehicle that performs the loading / unloading of capital equipment and materials at the construction site, communication at a lower cost than the communication cost by SMS can be enabled.

[0124] Also, according to the present embodiment, the predetermined timing is set as a plurality of timings before the time when login to the application program has not been performed and before the scheduled loading / unloading time of the capital equipment and materials at the construction site. Therefore, compared with the case where the timing is a single timing, the possibility of enabling push communication after the scheduled loading / unloading time of the capital equipment and materials at the construction site can be increased.

[0125] Also, according to the present embodiment, the plurality of timings are set such that the closer the scheduled time of using the loading / unloading gate by the loading / unloading vehicle approaches, the more timings there are. Therefore, it is possible to more effectively prompt login to the application program.

[0126] Also, according to the present embodiment, the application program is a program having a function of acquiring position information indicating the position of the loading / unloading vehicle from the terminal and transmitting information regarding the loading / unloading vehicle obtained using the position information to the terminal by push communication. Therefore, the transmission and reception of the position information and the information regarding the loading / unloading vehicle between the terminal and the schedule management server can be performed by push communication.

[0127] Furthermore, according to the present embodiment, the terminal is a mobile terminal. Therefore, compared with the case where the terminal is a stationary type, the communication frequency by push communication can be increased, and as a result, communication at a lower cost can be enabled more effectively.

[0128] In the above embodiment, the case where the incoming and outgoing vehicles to be managed include incoming and outgoing vehicles belonging to different companies has been described, but the present invention is not limited thereto. For example, it may be a form in which only the incoming and outgoing vehicles belonging to a single company are the incoming and outgoing vehicles to be managed.

[0129] Also, in the above embodiment, for example, as the hardware structure of the processing unit that executes each process of the transmission unit 11A and the presentation unit 31A, various types of processors shown below can be used. Among the various types of processors, as described above, in addition to the CPU, which is a general-purpose processor that executes software (program) and functions as a processing unit, there are programmable logic devices (PLDs) such as FPGAs (Field-Programmable Gate Arrays), which are processors whose circuit configuration can be changed after manufacture, and dedicated electric circuits, which are processors having a circuit configuration designed specifically to execute specific processes such as ASICs (Application Specific Integrated Circuits).

[0130] The processing unit may be configured by one of these various types of processors, or may be configured by a combination of two or more processors of the same type or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA). Further, the processing unit may be configured by one processor.

[0131] As an example of configuring the processing unit with one processor, first, as represented by computers such as clients and servers, one processor is configured with a combination of one or more CPUs and software, and this processor functions as the processing unit. Second, as represented by a System On Chip (SoC) or the like, there is a form in which a processor that realizes the functions of the entire system including the processing unit is used with one IC (Integrated Circuit) chip. Thus, the processing unit is configured using one or more of the above various processors as a hardware structure.

[0132] Furthermore, as a hardware structure of these various processors, more specifically, circuitry combining circuit elements such as semiconductor elements can be used.

Explanation of Signs

[0133] 10 Scheduling Management Server 11 CPU 11A Transmission Unit 12 Memory 13 Storage Unit 13A Scheduling Management Program 13B Scheduling Management Database 13C Construction Site Information Database 13D Terminal Information Database 14 Input Unit 15 Display Unit 16 Media Reading / Writing Device 17 Recording Medium 18 Communication I / F Unit 30 Terminal 31 CPU 31A Presentation Unit 32 Memory 33 Storage Unit 33A Terminal Processing Program 34 Input Unit 35 Display Unit 35A First Display Screen 35B Second Display Screen 35C1 to 35C3, Third Display Screen 35D, Fourth Display Screen 36, Media Reading / Writing Device 37, Recording Medium 38, Wireless Communication Unit 39, Position Detection Unit 80, Network 90, Schedule Management System

Claims

1. A scheduling management system comprising a terminal mounted on a loading and unloading vehicle for loading and unloading materials and equipment at a construction site, or held by a driver of the loading and unloading vehicle, and assigned a unique telephone number, and a scheduling management server for managing the schedule of loading and unloading materials and equipment at the construction site by the loading and unloading vehicle, wherein the scheduling management server sends information to prompt logging in to an application program that enables push communication by logging in to the terminal at a predetermined timing by using the short message service with the telephone number, the terminal presents the information sent from the scheduling management server, Scheduling management system.

2. The predetermined timing is a plurality of timings before the time of scheduled loading and unloading at the construction site of the materials and equipment and when the application program has not been logged in, The scheduling management system according to Claim 1.

3. The plurality of timings are timings such that the closer the position of the loading and unloading vehicle is to the loading and unloading gate, the more frequent, The scheduling management system according to Claim 2.

4. The plurality of timings are timings such that the closer the scheduled time of using the loading and unloading gate by the loading and unloading vehicle approaches, the more frequent, The scheduling management system according to Claim 2 or Claim 3.

5. The application program is a program having a function of acquiring position information indicating the position of the loading and unloading vehicle from the terminal and transmitting information about the loading and unloading vehicle obtained by using the position information to the terminal by push communication, The scheduling management system according to Claim 1.

6. The terminal is a mobile terminal, The scheduling management system according to Claim 1.

7. A program executed by the scheduling management server in a scheduling management system comprising a terminal mounted on a loading and unloading vehicle for loading and unloading materials and equipment at a construction site, or held by a driver of the loading and unloading vehicle, and assigned a unique telephone number, and a scheduling management server for managing the schedule of loading and unloading materials and equipment at the construction site by the loading and unloading vehicle, wherein the program causes a computer to execute a process of sending information to prompt logging in to an application program that enables push communication by logging in to the terminal at a predetermined timing by using the short message service with the telephone number, Program for causing a computer to execute.

Images