JP7854955B2 - Business terminal equipment, pre-work health check program, and delivery system - Google Patents

Description

This invention relates to devices, programs, and systems used by persons who perform transportation services using mobile vehicles such as bicycles, mopeds, motorcycles, automobiles, and trucks.

Patent Document 1, which will be described later, discloses an invention relating to a method and device that automatically prevents a vehicle from starting and driving if the driver is intoxicated, in light of the fact that there are many cases of traffic accidents caused by intoxicated driving. The invention disclosed in Patent Document 1 basically involves installing a driver's seat alcohol sensor 1 near the driver's seat, and if it is determined that the driver is intoxicated based on its output signal, it prevents the vehicle from starting and driving.

Furthermore, Patent Document 2, which will be described later, discloses an invention relating to a driver assistance device that prevents the deterioration of a driver's physical condition while driving a vehicle. The invention disclosed in Patent Document 2 involves a driver monitoring unit detecting the driver's physical information, a physical condition diagnosis unit performing a physical condition diagnosis based on that information, and if the judgment unit determines that the result of the physical condition diagnosis is below a threshold for recommending a rest, the information provision unit provides guidance to the driver encouraging them to take a rest.

The invention disclosed in Patent Document 1 can effectively prevent drunk driving. Furthermore, the invention disclosed in Patent Document 2 can effectively prevent prolonged driving. These inventions can deter drunk driving and driving by drivers with accumulated fatigue, thereby contributing to the prevention of traffic accidents.

Japanese Patent Publication No. 2004-249847 Japanese Patent Publication No. 2013-109447

In recent years, the transportation industry has seen legal revisions aimed at improving drivers' working conditions. For example, it has become necessary to record and manage information such as health status and alcohol checks. In other words, it is required to conduct health checks on drivers before they get behind the wheel (before starting work) and to take measures such as preventing them from driving if necessary. However, in the case of relatively large-scale transportation companies, it is possible for managers to check and understand the health status of drivers at the business premises before they start work. By having managers conduct health checks, appropriate health checks can be performed without the possibility of fraud.

However, in recent years, there has been an increase in small-scale transportation businesses operated by just a few people, as well as individual business owners who use light commercial vehicles to deliver goods and food from restaurants. In the case of these small-scale transportation businesses and individual business owners, the drivers themselves must conduct, record, and manage their own health checks. However, if drivers are left to input their health status and perform alcohol checks, they may forget to do so due to their busy schedules and lack of time. Conducting and recording health checks is effective in preventing traffic accidents, but it also benefits the drivers themselves, as it serves as a useful means of proving that they are in good health if they are involved in an accident.

In light of the above, this invention aims to enable those engaged in transportation work to perform health checks themselves at an appropriate time before starting work, without being consciously aware of it, and to record and store the results.

To solve the above problems, the business terminal device of the invention described in claim 1 is
A business terminal device used by users performing transportation services, which is carried by the user during work and used by launching a prescribed business application software,
When the aforementioned business application software is launched, a determination means is provided to determine whether or not it is the start of the workday.
When the aforementioned determination means determines that it is the start of work, a reception means is provided to receive the user's pre-work health management information.
The system is characterized by comprising a storage means for storing the health management information received through the reception means.

According to this invention, individuals performing transportation duties can, without conscious effort, conduct a health check at an appropriate time before starting work, and record and store the results. This allows them to objectively understand their own physical condition before starting work and provides a useful means of proving that they are in good health.

This is a diagram illustrating an example configuration of the delivery service system according to the embodiment. This is a block diagram illustrating an example configuration of a business terminal device according to the embodiment. This figure illustrates an example of data stored in the user information file of the business terminal device according to the embodiment. This figure illustrates an example of data stored in the operation log file of the business terminal device according to the embodiment. This figure illustrates an example of data stored in a health check file of a business terminal device according to an embodiment. This diagram illustrates the cooperation between the business terminal device and the external measuring device in this embodiment. This is a flowchart illustrating the process that occurs when business application software is executed on the business terminal device of the embodiment. This is a flowchart illustrating the process performed in step S103 of Figure 7. This is a block diagram illustrating an example configuration of the management server device in the embodiment.

The following describes one embodiment of the apparatus, program, and system according to this invention, with reference to the figures. The apparatus, program, and system of the embodiment described below can be widely applied to businesses engaged in transportation services. In this specification, transportation services include various types of services involving the transport of goods and people, such as transporting goods using bicycles, motorcycles, and automobiles, and transporting people primarily by bus and taxi.

This invention can, of course, be used by individual employees of large-scale transportation companies. Furthermore, this invention is particularly suitable for small businesses involved in delivery services, such as home delivery, where goods and packages are delivered to individual homes, and for sole proprietors who perform delivery services alone. Therefore, in order to simplify the explanation, the embodiments described below will use the example of a sole proprietor performing delivery services alone using this invention.

In the embodiments described below, a sole proprietor performing delivery services alone is either a subcontractor for a relatively large transportation (delivery) company, or someone who independently undertakes the delivery of packages and uses their own vehicle (e.g., a light commercial vehicle). Furthermore, "package" originally refers to items carried or transported. However, in this embodiment, it includes various items to be delivered to individual homes, such as letters, documents, parcels, goods purchased through e-commerce (so-called internet shopping), and meals from restaurants.

[Example of a delivery system configuration]
Figure 1 is a diagram illustrating an example configuration of a delivery service system according to an embodiment. In Figure 1, users U1, U2, ... are individual business owners who perform delivery services using their own, for example, light commercial vehicles CV1, CV2, ... and who perform delivery services using business terminal devices 1(1), 1(2), .... Business terminal devices 1(1), 1(2), ... are implemented as mobile communication terminals such as smartphones and tablet PCs (Personal Computers).

The business terminal devices 1(1), 1(2), ... connect to network 2 via nearby base stations BS(1), BS(2), and can communicate with the management server device 3 through this network 2. Network 2 is primarily the internet, but also includes the mobile phone network, public telephone network, and wireless LAN (Local Area Network) connecting the business terminal devices 1(1), 1(2), ... and the management server device 3 to the internet. Therefore, in Figure 1, base stations BS(1) and BS(2) are mobile phone network base stations and wireless LAN access points.

The management server device 3 stores and manages information about users authorized to use the management server device 3 through the business terminal devices 1(1), 1(2), ... . The management server device 3 has functions to provide map information to authorized users, perform route searches according to the packages to be delivered, and provide the searched delivery routes. The operating company of the management server device 3 has created business application software (hereinafter referred to as "business app") for business mobile terminals to support delivery operations using the management server device 3, and makes it available for download through a designated website.

This business application provides functions for mobile devices such as registering packages to be delivered, acquiring and displaying map information of the delivery area, requesting delivery route searches based on the packages, and providing route guidance (navigation) according to the searched delivery route. In other words, this business application enables various mobile devices to function as business terminals. Therefore, users U1, U2, ... can download and run this business application on their smartphones or tablet PCs, thereby enabling those devices to function as business terminals 1(1), 1(2), ...

Please note that downloading the business application may require payment, or it may be free but with limited usage periods or features. Furthermore, using the management server device 3 through the business application requires authentication using a user ID and password, and remaining logged in.

Users U1, U2, ... go to the collection center (distribution center) of the transportation company that has contracted them for delivery services, run the business application on their own business terminal devices 1(1), 1(2), ... and register the packages they will deliver on the business terminal devices 1(1), 1(2), .... Users U1, U2, ... load the registered packages into their own light commercial vehicles CV1, CV2, ... and proceed to deliver them. At this time, users U1, U2, ... use the business application on their own business terminal devices 1(1), 1(2), ... to provide the registered package information to the management server device 3 and request a search for a delivery route.

The map information of the delivery route and delivery area, which is the result of the search, is provided from the management server device 3 to the requesting business terminal devices 1(1), 1(2), ... and the map information of the delivery area and the delivery route are displayed on the display screens of the business terminal devices 1(1), 1(2), ... Users U1, U2, ... can perform package delivery work by referring to the map and delivery route displayed on the display screens of their own business terminal devices 1(1), 1(2), .... Furthermore, if the route to a delivery destination is unfamiliar, the navigation function can be used to perform the delivery.

In this way, users U1, U2, ... can perform package delivery tasks smoothly and quickly using the business terminal devices 1(1), 1(2), ... and the management server device 3, on which the business application is downloaded. Furthermore, in this embodiment of the delivery system, users U1, U2, ... are prompted to perform a health check at an appropriate time before starting work through the business terminal devices 1(1), 1(2), ... on which the business application is downloaded. This allows each user U1, U2, ... to perform a health check through their own business terminal device 1(1), 1(2), ... and input and store their health management information.

In other words, in this embodiment of the delivery system, the implementation of pre-work health checks is not left to the discretion of users U1, U2, ... . In this embodiment, users U1, U2, ... are prompted to perform health checks at appropriate times before starting work via the work terminal devices 1(1), 1(2), ..., thereby ensuring that pre-work health checks are carried out reliably and appropriately.

Furthermore, since the business terminal devices 1(1), 1(2), ... have the same basic configuration, in the following explanation, unless otherwise specified, business terminal devices 1(1), 1(2), ... will be collectively referred to as business terminal device 1. Similarly, users U1, U2, ... will be collectively referred to as user U in the following explanation unless otherwise specified.

[Example configuration of business terminal device 1]
Figure 2 is a block diagram illustrating an example configuration of the business terminal device 1 according to the embodiment. The transmitting/receiving antenna 101A and the wireless communication unit 101 realize the function of communicating through the network 2. Therefore, communication with the management server device 3 is performed through the transmitting/receiving antenna 101A and the wireless communication unit 101. The control unit 102, although not shown, is a microprocessor configured with a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), non-volatile memory, etc. The control unit 302 has the function of controlling each part of the business terminal device 1.

The storage device 103 includes, for example, a semiconductor memory and its device driver, and performs data recording, modification, deletion, and retrieval. It is also used as a work area to hold intermediate results of various processes. The operation unit 104 is equipped with, for example, a power on/off key and several function keys, and receives user operations, notifying the control unit 102 of the received operation content as an electrical signal.

The user information file 105 stores and holds basic information about user U who uses the business terminal device 1. Figure 3 is a diagram illustrating an example of the data stored in the user information file 105 of the business terminal device 1. As shown in Figure 3, the user information file 105 registers information that identifies the user and various other information about the user. This information is registered, for example, when a business application is downloaded and used on the business terminal device 1.

Of course, this is not limited to the time of download; at any appropriate time, user U can input personal information into their business terminal device 1 and register it in the user information file 105. Furthermore, the business terminal device 1 can be lent to employees by, for example, a transportation company. Therefore, if user U belongs to a transportation company and receives the business terminal device 1 from that company, the transportation company can also register the employee's personal information held by that company in the user information file 105 of the business terminal device 1. In this case, user U themselves does not need to register their own user information on the business terminal device 1 they are using.

In Figure 3, the Company ID is company identification information assigned to a company to uniquely identify the company when user U belongs to a company organization and that company uses the management server device 3 and business applications of this embodiment. The User ID is user identification information assigned to user U to uniquely identify the user using the business terminal device 1. The password is authentication information used together with the User ID when user U logs in to the management server device 3 through their business terminal device 1.

In Figure 3, the name, date of birth and age, email address, telephone number, and address are basic information about user U. In the transportation industry, drivers are required to undergo a health checkup at least once a year, or at least every six months if they work night shifts. In Figure 3, the health checkup date is the date of user U's most recent health checkup. The health checkup information is the result of the most recent health checkup, and is imported as electronic data in a specified format.

Furthermore, user U's health information includes disease information, work conditions, and medication conditions. Disease information includes, for example, the name and status of any disease that requires attention when engaging in delivery work, such as diabetes, hypertension, epilepsy, or heart disease. Work conditions indicate the requirements for working if the user has a disease that requires attention when engaging in delivery work, such as "8 hours of work per day" or "no night shifts." Medication conditions indicate the requirements for taking medication necessary for working if the user has a disease that requires attention when engaging in delivery work, such as "take medication X three times a day" or "take medication Y at the start of work."

Furthermore, as shown under "Other" in Figure 3, any other necessary information besides the information mentioned above can be registered and managed as user information. In this way, the data stored in the user information file 105 allows for the registration and management of basic information and health management information related to user U using the business terminal device 1.

The operation log file 106 stores operation history data (log data) that shows the past operating status of the business terminal device 1. Figure 4 is a diagram illustrating an example of the data stored in the operation log file of the business terminal device 1 in this embodiment. The operation log file 106 contains log data generated and recorded by the control unit 102, which allows for the understanding of what operations were performed in the business terminal device 1, when, and where. The time information indicating "when" can be obtained through the clock circuit 170 (described later) provided in the business terminal device 1, and the location information indicating "where" can be determined through the GPS unit 160 (described later).

Specifically, Figure 4 primarily shows log data from February 10, 2023. As shown in Figure 4, on February 10, 2023, the business application was launched at 7:50 AM, and the package registration process was scheduled to begin at 7:52 AM. However, before package registration, a health check began at 7:53 AM and ended at 7:58 AM. After this, the actual package registration process took place, and the process was completed at 8:40 AM.

Subsequently, a route search request corresponding to the registered package was sent to the management server device 3 at 8:41 AM. The route search results were obtained at 8:45 AM, and the route was set. Based on this route setting, navigation (route guidance) began at 9:00 AM, and package delivery commenced. It can be understood that all operations up to this point are performed at the same location identified by latitude x1 and longitude y1, for example, the collection point (distribution center) of the contracting transportation company.

At 9:18 AM, the first delivery was completed at the location indicated by latitude x2 and longitude y2. At 9:25 AM, the second delivery was completed at the location indicated by latitude x3 and longitude y3. After the deliveries were completed, navigation was terminated at 12:03 PM. The work application was stopped at 12:03 PM for a lunch break. The work application was restarted at 1:00 PM, and navigation was resumed at 1:01 PM, resuming deliveries. It can be determined that the lunch break took place at the location indicated by latitude a1 and longitude b1.

Subsequently, at 7:27 PM, the business application was terminated at the location indicated by latitude c1 and longitude d1, and at 7:52 AM on February 11, 2023, the business application was started again at the location indicated by latitude x1 and longitude y1. Therefore, it can be determined that the work on February 10, 2023, was performed from 7:50 AM to 7:27 PM. In this way, the data in the operation log file 106 allows the business terminal device 1 to understand when, where, and what was done. The operation log file 106 is capable of storing at least one month's worth of log data.

The health check file 107 stores various health management information obtained from health checks performed on user U of the business terminal device 1 before the start of work. Figure 5 is a diagram illustrating an example of the data stored in the health check file 107 of the business terminal device 1 in this embodiment. As shown in Figure 5, the health check file 107 stores information used to identify user U, such as company ID, user ID, password, and name, as well as health management information below the check date and time, for each health check date and time.

In this embodiment, health management information includes the date and time of the health check, as well as information such as body temperature, heart rate, blood pressure, blood oxygen saturation, alcohol concentration, medication information, mood, drowsiness, fatigue, diarrhea, abdominal pain, and headache. Furthermore, during the health check, facial image data of user U captured through the camera unit 130 (described later) and voice data of user U captured through the microphone 141 (described later) are also recorded. This facial image data and voice data are used to objectively recognize user U's health status. The voice data may be, for example, a reading of a relatively short, predetermined sentence such as, "It's [date]. Today's weather is [weather condition]."

Figure 6 illustrates the coordination between the business terminal device 1 and the external measuring device in this embodiment. As shown in Figure 7, the business terminal device 1 can receive and store body temperature, heart rate, blood pressure, and blood oxygen saturation, which are automatically measured and transmitted via short-range wireless communication by a wristwatch-type measuring device 4 (such as a smartwatch) worn on the user U's arm. In other words, body temperature, heart rate, blood pressure, and blood oxygen saturation do not need to be measured individually and input individually into the business terminal device by the user U; they can be measured and registered collectively by the smartwatch 4.

Furthermore, the alcohol concentration indicates the concentration of alcohol in one liter of user U's breath. A concentration of 0.15 mg/L or higher indicates intoxication, and 0.25 mg/L indicates drunkenness. As shown in Figure 6, the alcohol concentration can be measured using a commercially available alcohol checker 5, and the data transmitted via short-range wireless communication can be received and stored.

Medication information, as shown in Figure 6, is entered via the touch panel 120 of the business terminal device 1 (described later). Specifically, the name of the medication taken is entered. Alternatively, the medication package or prescription can be photographed using the camera unit 130 (described later) to input this information. Furthermore, mood, drowsiness, and fatigue are selected and entered via the touch panel 120 of the business terminal device 1 (described later), as shown in Figure 6. Similarly, the presence or absence of diarrhea, abdominal pain, and headache are also selected and entered via the touch panel 120 of the business terminal device 1 (described later), as shown in Figure 6.

This health management information is acquired each time a health check is performed and recorded in the health check file 107. Furthermore, standard values have been established for body temperature, heart rate, blood pressure, blood oxygen saturation, and alcohol concentration to confirm that the individual is fit to work. Therefore, as shown in Figure 4, the work terminal device 1 also records and maintains a distinction between whether the individual is fit to work (OK) or not (NG) based on these standard values.

Furthermore, the business terminal device 1 can distinguish between whether a user is able to work (OK) or unable to work (NG) by comparing medication information with the medication conditions in the user information file 105 mentioned above. Also, even if user U does not have any medication conditions, the business terminal device 1 can distinguish between whether a user is able to work (OK) or unable to work (NG) by identifying the components of the medication and understanding its effects.

Furthermore, the work terminal device 1 can distinguish between being able to work (OK) and being unable to work (NG) based on the degree of mood, drowsiness, and fatigue, and based on the presence or absence of diarrhea, abdominal pain, and headache. Therefore, as shown in Figure 4, the work terminal device 1 also distinguishes between being able to work (OK) and being unable to work (NG) based on medication information, mood, drowsiness, fatigue, diarrhea, abdominal pain, and headache information, and records and retains the results. In this way, the work terminal device 1 of this embodiment can perform a health check for user U, record the obtained health management information in the health check file 107, and store it.

The package data file 108 stores information about packages that user U is responsible for delivering. For packages that user U is responsible for delivering, user U registers the package by photographing the two-dimensional code or destination label attached to the package through the camera unit 130 of the business terminal device 1 (described later). This allows the business terminal device 1 to capture information such as the package's identification ID, the recipient's name (or company name), address, telephone number, and, if specified, the delivery time slot, and record this information in the package data file 108.

The route information file 109 stores information and map information indicating the delivery route of packages from the management server device 3. As mentioned above, the business terminal device 1 sends a route search request to the management server device 3, for example, containing the package data imported into the package data file 108. In response, the management server device 3 performs a route search considering the address and delivery time of the package to be delivered, and returns the resulting delivery route and map information of the delivery area.

The business terminal device 1 in this embodiment receives this information, stores it in the route information file 109, and is capable of performing navigation processing using this information. While it is certainly possible to manage delivery routes and map information in separate files, for the sake of simplicity in this embodiment, the data used for navigation processing is assumed to be managed in the route information file 109.

In this embodiment, the short-range wireless communication antenna 110A and the short-range wireless communication unit 110 implement the short-range wireless communication function of the Bluetooth® standard. Therefore, as explained with reference to Figure 6, the business terminal device 1 can perform short-range wireless communication with the smartwatch 4 and alcohol checker 5 via the short-range wireless communication antenna 110A and the short-range wireless communication unit 110 to acquire necessary information. While this embodiment describes the implementation of the Bluetooth® standard for short-range wireless communication, it is not limited to this. It is also possible to employ various other short-range wireless communication standards.

The business terminal device 1 is equipped with a touch panel 120 as a user interface. The touch panel 120 is configured with touch sensors 122 that cover the entire surface of the display screen of a thin display unit (display device) 121, such as an LCD (Liquid Crystal Display), and realizes both display and instruction input reception functions. The camera unit 130 realizes the function of capturing images of subjects and acquiring them as image data. The camera unit 130 is capable of capturing both moving and still images. Image data obtained through the camera unit 130 can be recorded, for example, in a predetermined area of the storage device 103. Furthermore, as mentioned above, during a health check, a moving image of the user U's face can be captured through the camera unit 130 and recorded as data to be included in the health check file 107.

The microphone 141 functions to capture sound, convert it into an electrical signal, and supply it to the audio processing unit 142. The audio processing unit 142 receives the electrical signal (analog audio signal) from the microphone 141, converts it into a digital signal, and captures it. The audio data captured through the microphone 141 and the audio processing unit 142 can be recorded, for example, as an audio memo in a predetermined area of the storage device 103. Furthermore, as mentioned above, during a health check, the voice of user U can be captured through the microphone 141 and the audio processing unit 142 and recorded as data to be included in the health check file 107.

The health check unit 151 functions when a business application is launched on the business terminal device 1 and determines whether it is time to perform a pre-work health check for user U. If it is time to perform a health check, the health check unit 151 controls the various components to perform the health check. Furthermore, in this embodiment, if the health check unit 151 detects a problem during the health check, it can also terminate the business application.

The package management processing unit 152 performs package-related processing, such as executing package registration and delivery completion processing, based on instructions input from the user U via the touch panel 120. Specifically, if the user U selects package registration, the package management processing unit 152 acquires package data via the camera unit 130 and registers it in the package data file 108. If the user U selects delivery completion processing, the package management processing unit 152 receives delivery completion input via the touch panel 120 and updates the corresponding package data in the package data file 108 with delivery completion information. In addition, the package management processing unit 152 can also perform other tasks, such as aggregating and processing package data for packages that could not be delivered due to the recipient being absent.

As described above, the route setting processing unit 153 performs processes such as making a route search request to the management server device 3, including the data of the package to be delivered, and receiving delivery route information and map information provided by the management server device 3 and storing it in the route information file 109. Furthermore, the route setting processing unit 153 can also perform processes such as requesting and obtaining a residential map of the area around the delivery destination of the package in response to instructions from the user U, and displaying it on the display unit 121.

The navigation processing unit 154 implements a function to perform navigation processing based on the map information and delivery route information stored in the route information file 109. Specifically, the navigation processing unit 154 displays a map on the display unit 121 according to the map information in the route information file 109, and also displays the route and the location of the business terminal device 1 according to the delivery route information in the route information file 109, providing guidance along the delivery route. In this case, voice guidance can also be emitted through the voice output processing unit and speaker (not shown) of the business terminal device 1, allowing for voice guidance as well.

The GPS unit 160 and GPS antenna 160A implement a positioning function that uses signals from artificial satellites to determine the current location. Therefore, the navigation processing unit 154 can display the current location of the business terminal device 1 on the map shown on the display screen of the display unit 121, as described above, and guide the user along the delivery route. Furthermore, as explained using Figure 4, the location where the business application was launched, and the locations where various operations within the business application began and ended can be determined. The clock circuit 170 can provide the current date, day of the week, and time. This allows, as explained using Figure 4, the date and time when the business application was launched, and the dates and times when various operations within the business application began and ended to be determined.

In the business terminal device 1 with this configuration, the function of the health check unit 151 is particularly important. The health check unit 151 enables individual business owners performing delivery work to conduct health checks—which are difficult to manage on their own—at an appropriate time before starting work, and to collect and store health management information.

[Summary of processing in the health check unit 151 of the business terminal device 1]
Figure 7 is a flowchart illustrating the process when a business application is executed on the business terminal device 1 of this embodiment. When power is turned on to the business terminal device 1 and the business application is started from the initial screen, the control unit 102 executes the process shown in Figure 7, and the control unit 102 controls each part to proceed with the process.

When the business application is started, the control unit 102 displays a menu, which is a list of processes that can be executed by the business application, on the display unit 121 and accepts selection input via the touch panel 120 (step S101). This menu allows selection of processes related to delivery operations that can be executed by the business application, such as package registration, package search, route search request, route setting, and delivery completion input, and also allows input of a command to terminate the business application.

Upon receiving a selection input through the process in step S101, the control unit 102 determines whether the selection input received via the touch panel 120 is an end command or not (step S102). If the determination process in step S102 determines that the received selection input is an end command, the control unit performs predetermined termination processing, such as returning the menu display to the initial screen (step S113), and terminates the process shown in Figure 7.

In the determination process of step S102, if it is determined that the received selection input is not a termination instruction, the health check timing determination process is executed (step S103). The health check timing determination process in step S103 determines whether or not it is time to perform a health check on user U of the business terminal device 1. Details of this process will be described later. After the process in step S103, the control unit 102 determines, based on the determination result in step S103, whether or not a health check is required, that is, whether or not it is time to perform a health check (step S104).

In the determination process of step S104, if it is determined that a health check is required, that is, that it is time to perform a health check before starting work, the control unit 102 controls the health check unit 151 to perform the health check. In this case, under the control of the control unit 102, the health check unit 151 first displays the health check screen shown in Figure 6 on the display unit 121 of the work terminal device 1 (step S105). After this, the health check unit 151 controls the short-range wireless communication unit 110 to receive measurement information (step S106). Specifically, as explained using Figure 6, the measurement information received includes body temperature, heart rate, blood pressure, and blood oxygen saturation from the smartwatch 4 used by user U, and the alcohol concentration in 1 liter of exhaled breath from the alcohol checker 5 (step S106).

Next, the health check unit 151 receives necessary information through the touch panel 120 (step S107). Specifically, as explained using Figure 6, it receives the name of the medication taken, the degree of mood, drowsiness, fatigue, and the presence or absence of diarrhea, abdominal pain, and headache through the touch panel 120. After this, the health check unit 151 records a video of the user U's face and predetermined audio through the camera unit 130, microphone 141, and audio processing unit 142 (step S108). The predetermined audio, as mentioned above, is audio information of a length sufficient to recognize the user U's speech (tone of voice), such as, "It's [date]. Today's weather is [weather condition]."

The health check unit 151 forms health check data (Figure 5) containing health management information based on the information received in steps S106 to S108, and records this in the health check file 107 (step S109). Furthermore, the health check unit 151 evaluates the received health management information and determines whether or not the person is fit to work in delivery (step S110). Specifically, as explained using Figure 5, the health check unit 151 evaluates the person as unfit for work if their body temperature, heart rate, blood pressure, or alcohol concentration is above the standard value. Similarly, if their blood oxygen saturation is below the standard value, they are also evaluated as unfit for work.

Furthermore, the health check unit 151 evaluates whether the user is able to work (OK) or unable to work (NG) by comparing the medication information with the medication conditions in the user information file 105, as described above. In other words, if the user has taken medication in accordance with the medication conditions, they are able to work; however, if they have not taken medication, they are unable to work. Even if user U does not have any medication conditions, the health check unit 151 identifies the components of the medication and understands its effects to evaluate whether they are able to work (OK) or unable to work (NG). For example, if a user has taken a cold medicine that causes drowsiness, they will be unable to work. The components of the taken medication can be identified by querying a predetermined server device on the internet via the wireless communication unit 101 and the transmitting/receiving antenna 101A.

Furthermore, regarding mood, drowsiness, and fatigue, the assessment of whether or not an individual is able to work can be based on combinations of these factors. For example, if an individual is feeling unwell, highly drowsy, and highly fatigued, they may be deemed unable to work. Similarly, if an individual experiences diarrhea, abdominal pain, or headache, they may be deemed unable to work, as these symptoms indicate poor health. It should be noted that the assessment of whether or not an individual is able to work described here is merely an example; other assessment methods are also applicable.

After the processing in step S110, the health check unit 151 determines, based on the evaluation results in step S110, whether or not user U of the work terminal device 1 is able to work (step S111). Suppose that the determination in step S111 determines that the user is unable to work. In this case, the health check unit 151 outputs a message indicating that the user is unable to work based on the health check results (step S112). For example, messages such as "Your body temperature is 38.2 degrees. You cannot work," or "Your alcohol concentration is above the standard value. You cannot work because you would be driving under the influence of alcohol," may be displayed on the display unit 121 or output as audio. After this, the control unit 102 performs a predetermined termination process (step S113), and the process shown in Figure 7 is terminated.

Furthermore, if the determination process in step S104 determines that a health check is unnecessary, i.e., that it is not time to perform a health check before starting work, the control unit 102 proceeds to the process in step S114. Similarly, if the determination process in step S111 determines that the person is fit to work based on the health check results, the control unit 102 also proceeds to the process in step S114. As a result, the control unit 102 executes the process selected in step S101 (step S114) and determines whether the executed process has been completed (step S115).

In the determination process of step S115, if it is determined that the executed process has not finished, the determination process of step S115 is repeated, and the system waits for the process to finish. If the determination process of step S115 determines that the executed process has finished, the control unit 102 repeats the process from step S101, enabling it to terminate the business application or execute other processes.

<Process for determining the timing of health checks>
Figure 8 is a flowchart illustrating the process for determining the timing of a health check, which is performed in step S103 of Figure 7. The health check unit 151 obtains the current time from the clock circuit 170, refers to the operation log file 106 to obtain the end date and time of the previous health check, and determines whether a predetermined time (for example, 8 hours) or more has passed since the previous health check (step S201). In the determination process of step S201, if it is determined that a predetermined time (for example, 8 hours) or more has passed since the previous health check, the health check unit 151 determines that a health check is required (step S208). In this case, because a long time has passed since the previous health check, there is a high probability that the delivery work for the previous day has been completed and it is before the start of work the next day. Here, the predetermined time is set to 8 hours, for example, but it is of course possible to set it to a longer time or a shorter time.

In the determination process of step S201, it is determined that a predetermined time (for example, 8 hours) has not elapsed since the previous health check. In this case, the health check unit 151 refers to the operation log file 106 to obtain the end date and time of the previous business application and determines whether the end date and time of the previous business application was the previous day or not (step S202). Here, the current time can be the one obtained in step S201. In the determination process of step S202, if it is determined that the end date and time of the previous business application was the previous day, the health check unit 151 determines that a health check is required (step S208). This is because if the end date and time of the previous business application was the previous day, it is considered highly probable that the delivery work has resumed across the day, the delivery work for the previous day has finished, and it is before the start of work on the new day.

In the determination process in step S202, let's assume it's determined that the end date and time of the previous business application was not the previous day. In this case, the health check unit 151 determines whether a predetermined time (for example, 6 hours) or more has passed since the end date and time of the previous business application (step S203). Here, the current time can be the one obtained in step S201, and the end date and time of the previous business application can be the one obtained in step S202. In the determination process in step S203, if it is determined that a predetermined time or more has passed since the end date and time of the previous business application, the health check unit 151 determines that a health check is required (step S208). This is because if a long time has passed between ending the business application and starting it again, it is highly likely that the delivery work for the previous day has been completed and the current time is before the start of work, rather than being a break.

In the determination process of step S203, suppose it is determined that less than a predetermined time has elapsed since the end time of the previous business application. In this case, the health check unit 151 determines whether the process selected in step S101 in Figure 7 is a package registration process or not (step S204). In the determination process of step S204, suppose it is determined that it is a package registration process. In this case, the health check unit 151 refers to the operation log file 106, obtains the end time of the previous navigation process, and determines whether more than a predetermined time (e.g., 6 hours) has elapsed since the end time of the previous navigation process (step S205). Here, the current time can be the one obtained in step S201.

The reason the end time of the navigation process is used as the basis here is because the navigation process is used during delivery operations. However, in the case of familiar delivery areas, delivery operations can sometimes be carried out smoothly even without using the navigation process, as long as the map and delivery route are displayed on the display unit 121. Therefore, instead of using only the end time of the navigation process as the basis, it is also possible to use the end time of the process that displays the map and delivery route, or the map and delivery destination, on the display unit 121, including the navigation process. Accordingly, the "navigation end time" in Figure 8 could be changed to the "end time of display of map information, etc.," and the previous end time of display of map information, etc. could be obtained from the operation log file 106 and used to determine whether a predetermined time has elapsed or not.

In the determination process of step S205, if it is determined that a predetermined time (e.g., 6 hours) has elapsed since the end of the previous navigation process, it is determined that a health check is required (step S208). This is because, if the process being performed is a package registration process and a predetermined time has elapsed since the end of the navigation process for delivery work, there is a high probability that the work has not yet started. Furthermore, if the determination process of step S205 determines that a predetermined time (e.g., 6 hours) has not elapsed since the end of the previous navigation process, the process proceeds to step S206. Similarly, if the determination process of step S204 determines that it is not a package registration process, the process proceeds to step S206.

In this case, the health check unit 151 refers to the operation log file 106, obtains the end date and time of the previous package registration process, and determines whether a predetermined time (e.g., 6 hours) or more has elapsed since the end date and time of the previous package registration process (step S206). Here, the current time can be the one obtained in step S201. If the determination process in step S206 determines that a predetermined time or more has elapsed since the end date and time of the previous package registration process, the health check unit 151 determines that a health check is required (step S208). This is because if the elapsed time since the previous package registration process is greater than the predetermined time, there is a high probability that the current time when the current package registration process is being attempted is before the start of a new workday.

In the determination process of step S206, if it is determined that less than a predetermined time has passed since the end date and time of the previous package registration process, it is determined that the probability of it being before the start of work is low, and therefore a health check is unnecessary (step S207). After the process in step S207 and after the process in step S208, the process shown in Figure 8 is exited, and the process returns to the process in step S103 of the flowchart shown in Figure 7, and the process from step S104 is carried out.

In this way, the business terminal device 1 can identify the appropriate timing before the start of work when a health check is required and perform the health check. Note that the health check timing determination process shown in Figure 8 is just one example; it can be modified, for example, by performing only step S201, or only steps S201 and S202. It is also possible to add other conditions. In other words, the health check timing determination process shown in Figure 8 can be modified by deleting, adding, or changing the determination conditions to perform determination processing according to, for example, the work pattern of user U.

[Example configuration of management server device 3]
Figure 9 is a block diagram illustrating an example configuration of the management server device 3 according to the embodiment. The connection terminal 301T constitutes the connection end to the network 2. The communication interface 301 realizes communication functionality through the network 2. Therefore, communication with the business terminal device 1 is performed through the connection terminal 301T and the communication interface 301. The control unit 302, although not shown, is a microprocessor configured with a CPU, ROM, RAM, non-volatile memory, etc. The control unit 302 has the function of controlling each part of the management server device 3.

The storage device 303 is a device consisting of a recording medium such as an HDD (Hard Disk Drive) or SSD (Solid State Drive) and its driver, and performs various data recording, modification, deletion, and retrieval operations. In addition to storing necessary data and programs, the storage device 303 is also used as a temporary storage area for intermediate data generated during various processes.

The user management database (DB) 304 stores at least the company ID, user ID, and password assigned to users who can use the management server device 3. In addition, it stores user information for a large number of users, for example, in the manner described using Figure 3. The user-specific health check file 305 receives and stores health check data (Figure 5) from the business terminal devices 1 of numerous users.

Map DB306 stores map information for displaying residential maps, city maps, road maps, regional maps, and national maps, which are formed on HDDs, SSDs, etc., and can be used for route guidance. The map information for displaying residential maps, city maps, road maps, regional maps, and national maps includes, for example, vector data, raster data, and annotation data for drawing the maps.

The Road Network DB 307 stores road network data for automobiles. The road network data stored in the Road Network DB 307 is used when searching for delivery routes. Specifically, the road network data consists of node data and link data. Node data represents points such as landmarks, buildings, facilities, intersections, and junctions. Link data indicates roads accessible by automobiles, such as national and prefectural roads, through line segments connecting the node data. Furthermore, the Road Network DB 307 associates each link with its link cost and link type.

Typically, link cost is determined by the length (distance) of the link or the time required for travel. Link cost is referenced when searching for the route with the minimum link cost using Dijkstra's algorithm. The link type indicates whether the ground link is a national, prefectural, municipal, or private road.

The delivery destination management database (DB) 308 stores information about the delivery destination of packages. It stores information that identifies the delivery destination, such as the address, and also allows for the determination of information such as the presence or absence of a delivery box. The user-specific package management file 309 receives package data registered in the business terminal device 1, stores it separately for each user, and updates the delivery completion information for each user's package data in response to delivery completion notifications from the business terminal device 1. Based on the user-specific package data in the user-specific package management file 309, it becomes possible to track the progress of deliveries and notify recipients of delivery completion, for example, via email.

The health check function unit 311 receives health check data provided from the business terminal device 1 and processes it to record in a user-specific health check file. Furthermore, the health check function unit 311 processes data such as providing health check data for users belonging to an organization, such as a company with multiple employees.

The map information provision function unit 312 performs processing such as extracting map information for the delivery area of the package from the map DB 306 in response to a request from the business terminal device 1 and providing it to the business terminal device 1. As mentioned above, the route search function unit 313 searches for a delivery route by referring to the road network data of the road network D307 in response to a route search request that includes package data provided by the business terminal device 1. The route search function unit 313 also performs processing such as obtaining information indicating the delivery route obtained as a result of the search and map information used for navigation from the map DB and providing it to the requesting business terminal device 1. Note that the package data used for searching for the delivery route can also be the data stored in the user-specific package management file 309.

The package management function unit 314 stores package data provided from the business terminal device 1 in the user-specific package management file 309, and updates the delivery completion information for each user's package data in response to the delivery completion notification provided from the business terminal device 1. As a result, the package management function unit 314 can, as described above, grasp the delivery progress based on the user-specific package data in the user-specific package management file 309, and also notify the recipient of the delivery completion, for example, via email.

In this way, the management server device 3, by cooperating with the business terminal device 1, can support the delivery operations of user U of the business terminal device 1, and can also store, retain, and manage the health check data of user U of the business terminal device 1. Therefore, even if user U of the business terminal device 1 loses or damages their business terminal device 1 and renders it inoperable, they can safely manage not only their package data but also their health check data.

[Effects of the embodiment]
As described above, the business terminal device 1 of this delivery system can prompt user U to perform a health check at an appropriate time before starting work without the user being aware of it. Furthermore, if a health check is performed, the system can acquire and store health management information about user U. If a problem is identified during the health check, the system can advise the user not to work.

Furthermore, by linking the business terminal device 1 and the management server device 3, the health management information of user U on the business terminal device 1 can also be stored in the management server device 3. This means that even if the business terminal device 1 is lost or malfunctions, the health status of user U can be determined using the health management information in the management server device 3. In addition, in organizations such as companies with multiple users, the organization's administrator can understand the health status of each user based on the health management information of each user stored in the management server device 3.

[Variations]
In the business terminal device 1 of the above-described embodiment, as explained with reference to Figures 7 and 8, the system automatically determines whether or not it is time for a pre-work health check when the business application is launched, but it is not limited to this. For example, it may be decided that health checks will be conducted between 8:00 AM and 8:30 AM from Monday to Friday. In this case, the time period for conducting health checks can be set in advance, and the system can be configured to automatically conduct health checks if the time the business application is launched falls between 8:00 AM and 8:30 AM from Monday to Friday.

Furthermore, if you want to conduct health checks multiple times a day, such as at the start of work in the morning and at the start of work in the afternoon, you can set the timing of the health checks, for example, once in the morning and once in the afternoon. This allows the system to distinguish between the start of work in the morning and the start of work in the afternoon and perform the set number of health checks accordingly. In this case, one way to determine whether or not to perform a health check is, for example, to decide whether or not to perform a health check when the business application is launched and the display of a map or the start of navigation is instructed.

Specifically, if the startup time is in the morning, the system checks the data stored in health check file 107 to see if the morning health check has been performed. If it is confirmed that the check has not been performed, the system should be configured to execute the morning health check. Similarly, if the startup time is in the afternoon, the system checks the data stored in health check file 107 to see if the afternoon health check has been performed. If it is confirmed that the check has not been performed, the system should be configured to execute the afternoon health check.

In this way, it is possible to set the time and frequency of health checks and guide users to the health check screen. However, in recent years, flexible changes to working hours have become common. For example, working hours may not be fixed and may vary, such as working only in the morning on Monday, from the afternoon to the evening on Tuesday, taking Wednesday off, and working all day on Thursday. In such cases, by taking the measures explained in the flowcharts in Figures 7 and 8, it is possible to conduct health checks at an appropriate time before the start of work, regardless of changes in working hours.

Furthermore, as explained using Figure 4, the operation log file 106 also records the location (latitude and longitude) where actions such as launching the business application and starting package registration were performed. Therefore, in the case of delivery operations, since delivery often begins after loading packages at the collection point, a health check may be performed when package registration begins at a location corresponding to a designated collection point. In other words, the timing of a health check may be determined not only by the start and end dates and times of various actions, but also by considering the location where various actions started and ended.

Furthermore, while the above-described embodiment uses the example of a self-employed individual performing delivery services using the business terminal device 1, it is not limited to this. For example, individuals who deliver food from restaurants to private homes, private taxi drivers, long-distance truck drivers, and tour bus drivers can also carry the business terminal device 1 and perform health checks at appropriate times. In cases where package registration is unnecessary, such as with private taxi drivers and tour bus drivers, a method for determining the timing of health checks that does not rely on the completion time of package registration can be used.

Furthermore, while the business terminal device 1 was described as being implemented using a smartphone or tablet PC, it can also be implemented as a dedicated terminal device specifically for delivery operations. Similarly, while the management server device 3 was described as a single device, it is not limited to this. The management server device 3 can also be implemented as a so-called cloud system consisting of multiple server devices located on the internet.

[others]
As can be seen from the description of the above embodiment, the business terminal device of the claim corresponds to the business terminal device 1 of the embodiment. The function of the determination means of the claim is realized by the health check unit 151 of the business terminal device 1. Furthermore, the function of the receiving means of the claim is realized by the short-range wireless communication antenna 110A, the short-range wireless communication unit 110 and the touch panel 120 of the business terminal device 1, and the storage means of the claim is realized by the health check file 107 of the business terminal device 1.

Furthermore, the function of the employment eligibility determination means described in the claim is implemented by the health check unit 151 of the business terminal device 1, and the function of the output means is implemented by the display unit 121 and a speaker (not shown) of the business terminal device 1. Also, the function of the termination processing means described in the claim is implemented through the cooperation of the health check unit 151 and the control unit 102 of the business terminal device 1.

Furthermore, a program that implements the process described using the flowcharts in Figures 7 and 8 is an example of one embodiment of the pre-work health check program according to this invention. The function of the health check unit 151 of the business terminal device 1 is to execute the process described using Figures 7 and 8. Therefore, a program that implements the process described using the flowcharts in Figures 7 and 8 is created, installed on a smartphone or tablet PC, and made executable by the control unit 102. This allows the function of the health check unit 151 to be realized as a function of the control unit 102, and by installing this program on an existing smartphone or tablet PC, the business terminal device of this invention can be realized.

1...Business terminal device, 101A...Transmit/receive antenna, 101...Wireless communication unit, 102...Control unit, 103...Storage device, 104...Operation unit, 105...User information file, 106...Operation log file, 107...Health check file, 108...Luggage data file, 109...Route information file, 110A...Short-range wireless communication antenna, 110...Short-range wireless communication unit, 120...Touch panel, 121...Display unit, 122...Touch sensor, 130...Camera unit, 141...Macrophone, 142...Voice processing unit, 151...Health check unit, 152...Luggage management processing unit, 153...Route setting processing unit, 154...Navigation processing unit, 160...GPS unit, 1 60A…GPS antenna, 170…Clock circuit, 2…Network, 3…Management server device, 301T…Connection terminal, 301…Communication I/F, 302…Control unit, 303…Storage device, 304…User management DB, 305…User health check file, 306…Map DB, 307…Road network data, 308…Delivery destination management DB, 309…User-specific package management file, 311…Health check function unit, 312…Map information provision function unit, 313…Route search function unit, 314…Package management function unit, 4…Smartwatch, 5…Alcohol checker, U, U1, U2…User, CV1, CB2…Light cargo vehicle, BS(1), BS(2)…Base station

Claims (6)

A business terminal device used by users performing transportation services, which is carried by the user during work and used by launching a prescribed business application software,
When the aforementioned business application software is launched, a determination means is provided to determine whether or not it is the start of the workday.
When the aforementioned determination means determines that it is the start of work, a reception means is provided to receive the user's pre-work health management information.
A business terminal device characterized by comprising a storage means for storing the health management information received through the reception means. A business terminal device according to claim 1, comprising: a means for determining whether or not it is possible to work based on the health management information received through the reception means;
If the aforementioned workability determination means determines that employment is not possible, an output means outputs a notification message,
A business terminal device characterized by comprising: termination processing means for terminating the execution of the business application software when the employment feasibility determination means determines that employment is not possible. A business terminal device according to claim 1,
The aforementioned determination means, based on the operation history information, determines at least:
A business terminal device characterized by determining that it is the start of work when a predetermined amount of time has elapsed since the last time health management information was entered. A business terminal device according to claim 1,
The aforementioned determination means, based on the operation history information, determines at least:
If more than the specified time has passed since the last time health management information was entered,
If the previous termination date and time of the aforementioned business application software is the day before or earlier,
If a specified time has elapsed since the termination date and time of the aforementioned business application software,
If the task performed is a package registration task, and a specified amount of time has elapsed since the completion date and time of the previous delivery destination guidance task,
A business terminal device characterized by determining that it is the start of the workday if either the executed task is other than the task of registering packages, and a predetermined amount of time has elapsed since the end date and time of the previous task of registering packages. A pre-work health check program that is executed on a computer installed in a business terminal device that is carried by a user performing transportation work during work hours and used by launching a prescribed business application software,
When the aforementioned business application software is launched, a determination step is made to determine whether or not it is the start of the workday.
If the determination step determines that it is the start of work, the reception step accepts the user's pre-work health management information,
A pre-work health check program characterized by performing a recording step of recording the health management information received through the reception step into a storage means. A delivery service system comprising a business terminal device, which is carried by users performing transportation services during their work and used by launching a predetermined business application software, and a management server device connected via a network,
The aforementioned business terminal device is,
When the aforementioned business application software is launched, a determination means is provided to determine whether or not it is the start of the workday.
When the aforementioned determination means determines that it is the start of work, a reception means is provided to receive the user's pre-work health management information.
The system comprises a transmission means for transmitting the health management information received through the reception means to the management server device,
The aforementioned management server device is
Receiving means for receiving the health management information from the business terminal device,
A delivery service system characterized by comprising a storage means for storing the health management information received through the receiving means for each user.