DE102018130884A1 - Information processing system and information processing method - Google Patents

Abstract

An information processing system includes: an acceptance / delivery requesting section (5021) adapted to give a terminal (200) of a carrier accepting or delivering a package information about an acceptance / delivery area where the package is to be accepted or delivered to convey; a vehicle detection section (5022) configured to detect that the delivery vehicle (20) has moved to the acceptance / delivery area; and an acceptance / delivery management section (5023) adapted to transmit, to the terminal (200) of the carrier, information about a parking position of an acceptance / delivery target vehicle (10) when the vehicle detection section (5022) detects that the delivery vehicle (50) 20) has moved to the acceptance / delivery area.

Description

BACKGROUND OF THE INVENTION

Field of the invention

The present invention relates to an information processing system and an information processing method for restricting unnecessary transmission of vehicle position information when a vehicle designated by a user is used as an acceptance / delivery point for a package.

Description of the Related Art

For some years, a system in which a cargo space of a vehicle designated by a user is provided as a delivery / delivery point for a package has been a facility for efficiently performing an acceptance and delivery of a package (piece of cargo) between a user of an acceptance - / delivery service and a parcel delivery company developed. For example, Japanese Unexamined Patent Publication No. 2006-206225 ( JP 2006-206225 A ) a system in which upon an acceptance or delivery of a package, an authentication process is performed between an acceptance / delivery communication device for the parcel delivery company and a vehicle communication device provided in the designated vehicle and the named vehicle can be locked or unlocked if the authentication is successful ,

SUMMARY OF THE INVENTION

In a system such as the above-mentioned system in which a vehicle hold is provided, or in a trunk share system in which packets are accepted and delivered using a vehicle, after this, position information about a vehicle is transmitted to the package delivery company have been designated by a user as an acceptance / delivery point for a package (hereinafter also referred to as acceptance / delivery target vehicle), this position information about the acceptance / delivery target vehicle already transmitted to the parcel delivery company becomes superfluous as soon as the user Acceptance / delivery target vehicle changes. For example, if the user sets a private car parking space as the position of the pickup / delivery target vehicle, position information is transmitted to the parcel delivery company via the private car parking lot. If the user thereafter changes the position of the acceptance / delivery target vehicle to another location, the parcel delivery company retains its knowledge of the location of the private car location, even though the information is redundant. From the point of view of data protection, the aim should be to prevent unnecessary provision of information concerning the privacy of the user.

Further, in a delivery system in which a package is delivered or accepted by tracking a vehicle designated as an acceptance / delivery destination, position information about the acceptance / delivery target vehicle can be provided to the parcel delivery company even if a parcel User is located in an area where the user does not want to be tracked as the acceptance / delivery destination.

The invention provides a technique that can prevent unnecessary provision of positional information about a vehicle designated as an acceptance / delivery destination for a package so that the privacy of a user can be protected.

According to the present inventors, when a delivery vehicle for accepting and delivering parcels moves in an acceptance / delivery area for which an acceptance / delivery of a parcel has been requested by a user, information about a parking position of a vehicle belonging to the user has been named as the acceptance / delivery destination of the package, transmitted to a terminal of a freight forwarder.

A first aspect of the invention relates to an information processing system, and the information processing system includes an acceptance / delivery requesting section, a vehicle detection section, and an acceptance / delivery management section. The acceptance / delivery requesting section is configured to transmit information about an acceptance / delivery area where the user requesting acceptance or delivery of the package wishes to accept or deliver the package to a terminal of a freight forwarder accepts or delivers a parcel. The vehicle detection section is configured to detect that a delivery vehicle with which the carrier accepts or delivers the package has moved to the acceptance / delivery area. The acceptance / delivery management section is configured to transmit, to the terminal of the carrier, information about a parking position of an acceptance / delivery destination vehicle designated by the user as an acceptance / delivery destination for the package when the vehicle detection section detects that Delivery vehicle has moved to the acceptance / delivery area.

In the information processing system, it is assumed that a vehicle is used as an acceptance / delivery point for a package. Accepting / delivering a package includes a case where a package for a user is delivered to the user, and a case where a package sent by a user is accepted. The acceptance / delivery area is an area or district in a predetermined area where the user wishes the package to be accepted or delivered. For example, the acceptance / delivery area is named after a city / administrative district / town / village, postal code or the like. The information processing system transmits information about the acceptance / delivery area including the predetermined area to the carrier of the package (the terminal of the carrier) without transmitting specific position information such as a parking position of a vehicle designated as an acceptance / delivery destination, and the like , If the acceptance / delivery destination is not named specifically, the forwarder may enter the acceptance / delivery area. When the delivery vehicle has moved to the acceptance / delivery area, the information processing system transmits to the terminal of the carrier the parking position of the acceptance / delivery target vehicle. That is, as long as the delivery vehicle has not moved into the acceptance / delivery area, information about a specific parking position of the acceptance / delivery target vehicle is not transmitted to the carrier. For that matter, in a case where an acceptance / delivery is canceled or suspended before the delivery vehicle has moved to the acceptance / delivery area, information about the parking position of the acceptance / delivery destination vehicle is not unnecessarily provided, so that the privacy of the user can be protected. Further, when placing an order for acceptance / delivery, the user does not have to specify a final acceptance / delivery destination, so that flexible acceptance / delivery is possible.

According to the above aspect, when the vehicle detection section detects that the delivery vehicle has moved to the acceptance / delivery area, the vehicle detection section may further determine whether or not the acceptance / delivery destination vehicle is in the acceptance / delivery area. If the pickup / delivery target vehicle is in the pickup / delivery area, the pickup / delivery management section may transmit the information about the parking position of the pickup / delivery target vehicle to the terminal of the carrier, and if the pickup / delivery target vehicle is not in the pickup / delivery area is located, the acceptance / delivery management section may transmit to the terminal of the carrier an order to suspend acceptance or delivery of the package without transmitting to the terminal of the carrier the information about the parking position of the acceptance / delivery target vehicle. Also, in a case where the delivery vehicle has moved to the acceptance / delivery area, the acceptance / delivery target vehicle may not be in the acceptance / delivery area, for example, when the acceptance / delivery target vehicle is moving. If the pickup / delivery target vehicle is not in the pickup / delivery area, the pickup / delivery is suspended so that information about the parking position of the pickup / delivery target vehicle is not unnecessarily provided to the forwarder, thereby allowing the privacy of the carrier Protect user.

Further, according to the above aspect, the acceptance / delivery requesting section may transmit to the terminal of the carrier information about a non-candidate acceptance / delivery area where the user does not want to receive or deliver the package. When the vehicle detecting section detects that the pickup / delivery target vehicle has moved to the ineligible pickup / delivery area, the pickup / delivery managing section may transmit a command to the terminal of the carrier to suspend acceptance or delivery of the packet without the terminal to provide the forwarder with the information about the parking position of the acceptance / delivery target vehicle. In a case where the delivery vehicle tracks the acceptance / delivery target vehicle to accept or deliver the package, the acceptance or delivery of the package in the ineligible acceptance / delivery area where the user does not accept or deliver the package Tracking wants, not allowed, so that the privacy of the user is protected.

In the above-mentioned configuration, when the instruction of suspending the acceptance or delivery of the package is transmitted to the terminal of the carrier, the acceptance / delivery management section may further transmit to the terminal of the user that the acceptance or delivery of the package is suspended. This allows the user to recognize that the package is being accepted or delivered and may order an acceptance / delivery resumption.

Further, if the acceptance / delivery target vehicle is not parked, then according to the above aspect, the acceptance / Delivery management section to the user's terminal to send a message that the user should be asked to park the acceptance / delivery target vehicle. When the user parks the vehicle as the acceptance / delivery destination, the forwarder's terminal may thereby determine a parking position of the vehicle so that the forwarder can easily accept or deliver the package.

Further, according to the above aspect, when the terminal of the forwarder is instructed to suspend the acceptance or delivery of the package, the acceptance / delivery management section can retrieve information about the acceptance / delivery area re-set by the user's terminal. This allows the forwarder to resume suspended delivery / delivery of the parcel.

Note that the information processing system according to the aspect of the invention may consist of one or more processing devices such as computers. In a case where the information processing system consists of a plurality of processing devices, the respective components of the information processing system are distributedly provided in the processing devices, and the processing devices cooperate to implement the information processing system processes.

Furthermore, the invention can be realized from the viewpoint of a method. For example, a second aspect of the invention relates to an information processing method, and the information processing method includes: transmitting information about an acceptance / delivery area designated by a user who has made a request for acceptance or delivery of a parcel as an acceptance / delivery point for the package has been requested, by a computer, to a terminal of a freight forwarder accepting or delivering a package; Detecting that a delivery vehicle by which the forwarder accepts or delivers the package has moved to the acceptance / delivery area; and transmitting information about the parking position of an acceptance / delivery target vehicle designated by the user as an acceptance / delivery destination for the package to the terminal of the carrier when it is detected that the delivery vehicle is moving to the acceptance / delivery area Has. Note that the technical idea disclosed herein with respect to the information processing system is also applicable to the information processing method as long as there are no technical inconsistencies.

According to the above aspect, unnecessary provision of position information about a vehicle designated as an acceptance / delivery destination for a package can be prevented, so that the privacy of a user can be protected.

list of figures

• 1 ist eine Ansicht, die eine schematische Konfiguration eines Trunk Share Systems gemäß einer Ausführungsform der Erfindung darstellt;
• 2 ist ein Blockdiagramm, das Konfigurationen einer Fahrzeug-Bordvorrichtung, eines Teilnehmerendgeräts eines annehmenden/ausliefernden Teilnehmers, eines Teilnehmerendgeräts eines beauftragenden Teilnehmers, eines Annahme-/Auslieferungsverwaltungsservers und eines zentralen Servers veranschaulicht, aus denen das in 1 dargestellte Trunk Share System besteht;
• 3 ist eine Ansicht, die einen Annahme-/Auslieferungsinformationeneintragungsbildschirm veranschaulicht, über den der beauftragende Teilnehmer Annahme-/Auslieferungsinformationen über ein Paket einträgt;
• 4 ist eine Ansicht, die eine Datenstruktur von Annahme-/Auslieferungsinformationen, die im Annahme-/Auslieferungsverwaltungsserver gespeichert sind, veranschaulicht;
• 5 ist eine Ansicht, die eine Datenstruktur von Fahrzeugverwaltungsinformationen, die im Annahme-/Auslieferungsverwaltungsserver gespeichert sind, veranschaulicht;
• 6 ist ein Ablaufschema, das einen Annahme-/Auslieferungszielübermittlungsprozess veranschaulicht, der vom Annahme-/Auslieferungsverwaltungsserver ausgeführt wird, und
• 7 ist ein Ablaufschema, das einen Annahme-/Auslieferungsneuanfrageempfangsprozess veranschaulicht.

Features, advantages and technical and industrial significance of exemplary embodiments of the invention will be described below with reference to the accompanying drawings, in which like reference numerals designate like elements:

• 1 Fig. 10 is a view illustrating a schematic configuration of a trunk share system according to an embodiment of the invention;
• 2 FIG. 12 is a block diagram illustrating configurations of a vehicle on-board device, an accepting / delivering subscriber's terminal, a calling subscriber's terminal, an acceptance / delivery management server, and a central server from which the in 1 illustrated trunk share system exists;
• 3 Fig. 15 is a view illustrating an acceptance / delivery information registration screen through which the instructing party inputs acceptance / delivery information about a packet;
• 4 Fig. 13 is a view illustrating a data structure of acceptance / delivery information stored in the acceptance / delivery management server;
• 5 Fig. 13 is a view illustrating a data structure of vehicle management information stored in the acceptance / delivery management server;
• 6 FIG. 10 is a flowchart illustrating an acceptance / delivery destination transmission process executed by the acceptance / delivery management server, and FIG
• 7 Fig. 10 is a flowchart illustrating an acceptance / delivery request reception process.

DETAILED DESCRIPTION OF EMBODIMENTS

Hereinafter, a specific embodiment of the invention will be described with reference to the accompanying drawings. The configurations described in the present embodiment are not intended to exceed the limits of the technical Area of the invention, unless otherwise specified.

First embodiment

system configuration

1 FIG. 13 is a view illustrating a schematic configuration of a system in which a cargo space is provided and a trunk share system according to the present embodiment, respectively. FIG. The trunk share system 1 is a system intended to provide an acceptance / delivery service involving a cargo space (luggage compartment) of a vehicle 10 which is designated by a customer requesting an acceptance / delivery action for a package (piece of cargo) shared by the customer and a person making the requested acceptance / delivery action for the package, such that the cargo space is designated as Acceptance / delivery point is used. Accordingly, both the "customer making an inquiry for an acceptance / delivery action for the package" and the "person performing the acceptance / delivery action for the package" are those who use the cargo space of the vehicle distinguishing them, the former is referred to as the "assigning subscriber" or "customer user", and the latter being referred to as an "accepting / delivering subscriber" or "delivery / delivery user". designated. The assignee is an example of a "user" and the accepting / dropping participant is an example of a "carrier". Further, the trunk share system 1 an example of an "information processing system".

In an example of 1 has the trunk share system 1 on: a vehicle on-board device 10A in the vehicle 10 is provided, a delivery vehicle 20 Used for acceptance and delivery, a subscriber terminal 200 for the accepting / delivering subscriber, a subscriber terminal 50 for the commissioning participant, a central server 400 and an acceptance / delivery management server 500 , The vehicle on-board device 10A , the subscriber terminal 200 , the subscriber terminal 50 , the central server 400 and the acceptance / delivery management server 500 are over a network N1 connected with each other. Note that the network N1 A global public communications network, such as the Internet, can be used and a Wide Area Network (WAN) or other communications networks can be used. Furthermore, the network N1 a telecommunications network such as a cellular telephone and a wireless communication network, such as Wi-Fi. Further, the on-vehicle device is 10A with the subscriber terminal 200 of the accepting / delivering subscriber via a network N2 including wireless short-range communication and the like. Note that for illustration only one Acceptance / Delivery Management Server 500 in the trunk share system 1 but that two or more acceptance / delivery management servers may be included. The subscriber terminal 200 of the accepting / delivering subscriber is an example of a "terminal of the carrier", and the subscriber terminal 50 of the instructing participant is an example of a "terminal of the user".

The acceptance / delivery management server 500 receives from the subscriber terminal 50 the assigning participant registers an article (hereinafter also referred to as acceptance / delivery package) to be accepted or delivered. For example, in a case where a product purchased at a merchandise purchasing website set up by an e-commerce company is delivered by the accepting / delivering participant as an acceptance / delivery package, the customer may receive delivery / delivery information about the acceptance / delivery package via a delivery / delivery package Application (also referred to as a given application in the following) in the acceptance / delivery management server 500 sign up for a Trunk Share System service 1 to use, with the application in the subscriber terminal 50 of the contracting subscriber is installed. As below in 4 is described, include the acceptance / delivery information: identification information of the charging subscriber, information about an area (hereinafter also referred to as acceptance / delivery area) where the calling party desires an acceptance or delivery of the package, and an area (hereinafter deemed to be an ineligible acceptance / delivery area) where the commissioning agent does not wish to receive or deliver the package, and so on. The identification information of the charging subscriber will also be in advance with the vehicle 10 in the Acceptance / Delivery Management Server 500 is associated with the assignee, and the instructing party may select a suitable receiving / delivery point to be used among possible receiving / delivery points related to the assignee, including the vehicle 10 , choose. The selected acceptance / delivery point is included in the acceptance / delivery information. Note that the following description is based on the premise that the accepting / delivery point of the charging subscriber is the vehicle 10 is. Further close the acceptance / delivery information also information about the status of the acceptance / delivery package. As examples of status information, information about whether acceptance / delivery of the acceptance / delivery packet has been carried out or not may be given.

The acceptance / delivery management server 500 receives an order for acceptance / delivery of the packet from the subscriber terminal 50 of the instructing participant. The acceptance / delivery management server 500 sends the acceptance / delivery information entered by the instructing subscriber to the subscriber terminal 200 of the accepting / delivering participant. The accepting / delivering subscriber goes to the acceptance / delivery area included in the acceptance / delivery information. If the adoption / delivery management server 500 detects that the delivery vehicle 20 has moved to the acceptance / delivery area, the acceptance / delivery management server sends 500 Position information about the vehicle 10 as an acceptance / delivery destination to the subscriber terminal 200 of the accepting / delivering participant. The position information of the vehicle 10 as an acceptance / delivery destination, based on the position information about the vehicle 10 that are included in the acceptance / delivery information, from the central server 400 be retrieved. If the accepting / delivering subscriber is the vehicle 10 reached, the accepting / delivering subscriber to the central server 400 a request for an output of authentication information for locking and unlocking the cargo compartment of the vehicle 10 in which the acceptance / delivery package is to be accommodated, to the subscriber terminal 200 of the accepting / delivering participant. The request is based on a request from the subscriber terminal 200 of the accepting / delivering participant as a starting point. The central server 400 sends authentication information about the vehicle based on the identifying information of the charging agent included in the acceptance / delivery information 10 that is associated with the identifying information of the charging party via the acceptance / delivery management server 500 to the subscriber terminal 200 of the accepting / delivering participant. The accepting / delivering subscriber then locks or unlocks the cargo compartment of the vehicle 10 using the authentication information provided by the subscriber terminal 200 were accessed so that the accepting / delivering subscriber access to the cargo compartment of the vehicle 10 to deliver or accept the acceptance / delivery package. Here, the authentication information is digital information provided by the user terminal 200 via wireless short-range communication to the onboard vehicle device 10A be transmitted and the an authentication process by the vehicle on-board device 10A be subjected, so that the vehicle on-board device 10A a process of locking / unlocking the cargo compartment of the vehicle 10 performs. Further, the process of locking / unlocking the cargo compartment of the vehicle 10 a process that causes the vehicle on-board device 10A (described in detail below) the door of the cargo compartment of the vehicle 10 in which the acceptance / delivery package is to be accommodated, locked or unlocked.

2 FIG. 10 is a block diagram showing vehicle on-board device configurations. FIG 10A , the subscriber terminal 200 the accepting / delivering subscriber, the subscriber terminal 50 of the submitting subscriber, the acceptance / delivery management server 500 and the central server 400 illustrates the Trunk Share System 1 consists. With reference to 2 will now be hardware configurations and functional configurations of the vehicle on-board device 10A , the subscriber terminal 200 the accepting / delivering subscriber, the subscriber terminal 50 of the submitting subscriber, the acceptance / delivery management server 500 and the central server 400 described.

The vehicle on-board device 10A has a key unit 100 and a lock / unlock device 300 on. The key unit 100 has a wireless interface similar to an electronic key of a smart key (hereinafter referred to as a portable device). By communicating with the existing lock / unlock device 300 used in the vehicle on-board device 10A is provided, a locking and unlocking of the cargo compartment of a vehicle interior of the vehicle 10 (hereinafter also referred to simply as "locking and unlocking the vehicle 10") without the use of a physical key. Furthermore, the key unit leads 100 a wireless short-range communication with the subscriber terminal 200 the accepting / delivering subscriber, and determines based on a result of the authentication process performed at the subscriber terminal 200 of the accepting / delivering subscriber, whether the key unit 100 as an electronic key for the vehicle 10 works or not.

When the subscriber terminal 200 of the accepting / delivering participant to the cargo compartment of the vehicle 10 accesses that To deliver or accept acceptance / delivery package, then provides the subscriber terminal 200 a request to the central server 400 after issuing authentication information for locking and unlocking the hold via the acceptance / delivery management server 500 , as described above. The from the subscriber terminal 200 of the accepting / delivering subscriber to the key unit 100 The authentication information sent is verified with the authentication information provided in advance in the key unit 100 were saved. If the authentication process succeeds, the subscriber terminal becomes 200 accepted as a terminal that is entitled to the vehicle on-board device 10A to use. When the subscriber terminal 200 is authenticated sends the key unit 100 a key ID of the vehicle 10 in advance in the key unit 100 has been stored and associated with the authentication information, together with a lock / unlock signal to the lock / unlock device 300 , If that of the key unit 100 received key ID with a key ID, the advance in the lock / unlock device 300 has been stored, locks or unlocks the locking / unlocking device 300 the vehicle 10 , The key unit 100 and the lock / unlock device 300 work with electrical power that comes from a battery in the vehicle 10 is provided. Note that the key ID that precedes in the key unit 100 has been stored, can be encrypted by the authentication information. If the authentication process at the subscriber terminal 200 the accepting / delivering subscriber is successful, the key unit 100 In this case, decrypt the key ID by the authentication information and send it to the lock / unlock device 300 send.

Now the locking / unlocking device 300 described in detail. The locking / unlocking device 300 is a device for locking and unlocking doors of the vehicle interior and the cargo compartment of the vehicle 10 , For example, the door of the vehicle 10 in response to a lock signal and an unlock signal from a portable device for the vehicle 10 via a radio wave of a high frequency band (hereinafter referred to as RF band), locks and unlocks. Furthermore, the locking / unlocking device 300 Also, a function to transmit a radio wave of a low frequency band (hereinafter referred to as LF band) for searching the portable device.

In the present embodiment, instead of the portable device, the key unit transmits and receives 100 the radio waves of the RF band and the LF band to and from the locking / unlocking device 300 to the door of the vehicle 10 to lock and unlock. The following description is based on the assumption that a communication partner of the lock / unlock device 300 on the key unit 100 is limited unless otherwise specified.

The locking / unlocking device 300 has an LF transmitter 301 , an RF receiver 302 , a verification ECU 303 , a body-ECU 304 and a door lock actuator 305 on. The LF transmitter 301 is means for transmitting a radio wave of a low frequency band (eg 100 kHz to 300 kHz) to search for the key unit 100 (to retrieve data). The LF transmitter 301 is provided, for example, in the vicinity of a center console or a lever in the vehicle interior. The RF transmitter 302 is a device for receiving a radio wave of a high frequency band (eg 100 MHz to 1 GHz) transmitted by the key unit 100 is sent. The RF receiver 302 is provided at any point in the vehicle interior.

The verification ECU 303 is a computer for performing a control for locking and unlocking the doors of the vehicle interior and the cargo compartment of the vehicle 10 based on a signal (a lock signal or an unlock signal) received from the key unit 100 is sent over the RF band radio wave. The verification ECU 303 For example, it consists of a microcomputer. Note that, in the following description, the lock signal and the unlock signal are collectively referred to as a lock / unlock signal. The term "lock / unlock signal" stands for at least one of the lock signal and the unlock signal.

The verification ECU 303 authenticates that from the key unit 100 transmitted locking / unlocking signal is sent from an authorized device. Specifically, the verification ECU determines 303 whether a key ID included in the lock / unlock signal coincides with a key ID stored in advance in a storage section (not shown) stored in the verification ECU 303 is included. Then the verification ECU sends 303 on the basis of the determination result, an unlocking command or a lock command to the body ECU 304 , The unlock command or the lock command are sent via a vehicle electrical system, such as a Controller Area Network (CAN).

The door lock actuator 305 is an actuator designed to doors the vehicle 10 (A vehicle interior door that is opened and closed when a passenger gets in and out of the vehicle interior as a passenger compartment and a cargo door that is opened and closed when the cargo space is loaded and unloaded) to lock and unlock. The door lock actuator 305 works on the basis of a signal coming from the body ECU 304 is sent. Note that the door lock actuator 305 can be designed to the vehicle interior door and the cargo door on the vehicle 10 independently lock and unlock.

The body-ECU 304 is a computer for performing a body control of the vehicle 10 , The body-ECU 304 has a function of locking and unlocking the vehicle interior door and the cargo door of the vehicle 10 by controlling the door lock actuator 305 based on the lock command or the unlock command issued by the verification ECU 303 be received simultaneously or independently. Note that the verification ECU 303 and the body-ECU 304 can be integrated.

Now the key unit 100 described. The key unit 100 is a device in a predetermined position (for example, in a glove box) in the vehicle interior of the vehicle 10 is placed. The key unit 100 has the function, the subscriber terminal 200 the accepting / delivering subscriber via wireless short-range communication with the subscriber terminal 200 and the like, and a function of transmitting a lock / unlock signal using the RF band radio wave based on the authentication result. The key unit 100 consists of an LF receiver 101 , an RF transmitter 102 , a short-range communication section 103 and a control section 104 ,

The LF receiver 101 is means for receiving a data fetch signal from the lock / unlock device 300 is sent over the LF band radio wave. The LF receiver 101 has an antenna (hereinafter referred to as LF antenna) configured to receive the LF band radio wave. The RF receiver 102 is means for sending a lock / unlock signal to the lock / unlock device 300 via the RF band radio wave.

The short-range communication section 103 is a device for communicating with the subscriber terminal 200 of the accepting / delivering participant. The short-range communication section 103 performs communication in a vicinity (to such an extent that communication between the interior of the vehicle interior and the exterior environment of the vehicle interior can be performed) using a predetermined wireless communication standard. In the present embodiment, the short-range communication section performs 103 a data communication by the Bluetooth (Registered Trade Mark) Low Energy Standard (hereinafter referred to as BLE) by. BLE is a low power Bluetooth telecommunications standard and has as a feature that it instantly starts a communication on acquisition of a partner without the need for inter-device coupling. Note that in the present embodiment, BLE is mentioned as an example, but other wireless communication standards are usable as well. For example, near-field communication (NFC), ultra-wideband (UWB), Wi-Fi (registered trademark) and the like can be used.

The control section 104 is a computer designed for short-range wireless communication with the subscriber terminal 200 of the accepting / delivering subscriber via the short-range communication section 103 perform and a controller for authentication of the subscriber terminal 200 and send a controller for transmitting a lock / unlock signal based on the authentication result. The control section 104 For example, it consists of a microcomputer.

The control section 104 has a memory section 1041 and an authentication section 1042 on. A control program for controlling the key unit 100 is in the memory section 1041 saved. The control section 104 can be done by running control programs in the control section 1041 stored to implement various functions, including the authentication section 1042 , For example, the control section implements 104 a function of receiving a data interrogation signal from the lock / unlock device 300 as LF band radio wave is transmitted via the LF receiver 101 , a function of sending a lock / unlock signal as an RF band radio wave to the lock / unlock device 300 via the RF transmitter 102 , a function of processing a communication with the subscriber terminal 200 of the accepting / delivering subscriber via the short-range communication section 103 , a function of generating one Lock / Unlock signal when the authentication of the subscriber terminal 200 of the accepting / delivering subscriber by the authentication section 1042 is successful, and so on.

The authentication section 1042 performs authentication at the subscriber terminal 200 based on authentication information provided in one of a subscriber terminal 200 of the accepting / delivering subscriber, the lock request or unlock request (hereinafter collectively referred to as the lock / unlock request). More specifically, the authentication section compares 1042 Authentication information stored in the memory section 1041 stored with the authentication information provided by the subscriber terminal 200 of the accepting / delivering subscriber, and if they have a predetermined relationship, the authentication section determines 1042 that the authentication is successful. Unless both the authentication information units satisfy the predetermined relationship, the authentication section determines 1042 that the authentication failed. Here, the predetermined relationship includes a case where those in the memory section 1041 stored authentication information with the user terminal 200 match a case where the processing results of the predetermined encryption / decryption and the like using two authentication information units agree with each other, a case where a result of a decryption process performed on one of the two authentication information units with the the other agrees, and so on.

If the authentication section 1042 the subscriber terminal 200 of the accepting / delivering subscriber is successfully authenticated, a lock / unlock signal is generated in response to a user terminal 200 received request is generated via the RF transmitter 102 to the locking / unlocking device 300 Posted. The following is the authentication information that is in the key unit 100 are stored, referred to as device authentication information, and the authentication information provided by the subscriber terminal 200 of the accepting / delivering subscriber are referred to as terminal authentication information, as the description requires.

Further, the key unit sends 100 the key ID together with the lock / unlock signal to the lock / unlock device 300 , The key ID may be in the key unit 100 may be stored in advance as plain text, or it may be stored in an encrypted state where the key ID is encrypted by a digit code assigned to the subscriber terminal 200 of the accepting / delivering participant. When the key ID is stored in the encrypted state, the thus encrypted key ID may be encrypted by the subscriber terminal 200 decrypted authentication information sent by the accepting / delivering subscriber, so that an original key ID can be obtained.

Thus, the on-vehicle device operates 10A the lock / unlock device 300 through the authentication process performed by the key unit 100 is carried out on the basis of the subscriber terminal 200 of the accepting / delivering subscriber as the starting point and performs a series of locking / unlocking processes of locking and unlocking the vehicle interior and the cargo compartment of the vehicle 10 out.

Now the subscriber terminal 200 of the accepting / delivering subscriber. The subscriber terminal 200 is a small computer such as a smart phone, a mobile phone, a tablet terminal, a personal information terminal, and a wearable computer (a smartwatch and the like). Note that the subscriber terminal 200 a personal computer (PC) can be over the network N1 such as the Internet, that is, a public communication network, and the like, with the acceptance / delivery management server 500 can be connected. The subscriber terminal 200 of the accepting / delivering subscriber consists of a short-range communication section 201 , a communication section 202 a control section 203 and an input / output section 204 ,

The short-range communication section 201 is a device for communicating with the key unit 100 by means of the same telecommunication standard as the short-range communication section 103 the key unit 100 , The network that exists between the short-range communication section 201 and the key unit 100 is trained in 1 denoted by N2. The communication section 202 is a communication device for connecting the subscriber terminal 200 with the net N1 , In the present embodiment, the subscriber terminal 200 using a mobile communication service such as 35rd Generation (3G) and Long Term Evolution (LTE), via the web N1 with other devices (eg the acceptance / delivery management server 500 and so on) communicate.

The control section 203 is a computer for managing a controller of the subscriber terminal 200 , The control section 203 For example, a process of retrieving the terminal authentication information, a process of generating a lock / unlock request, including the retrieved terminal authentication information, performs a process of sending the generated lock / unlock request to the key unit 100 and the like. Note that the control section 203 For example, it consists of a microcomputer and implements a function of performing various processes by causing a CPU (not shown) to execute programs stored in a storage device (a ROM and the like).

Furthermore, the control section leads 203 an interaction with the accepting / delivering participant via the input / output section 204 by. The input / output section 204 is means for receiving an input operation performed by the accepting / delivering subscriber and for providing information to the accepting / delivering subscriber. More specifically, the input / output section 204 from a touch panel, its control device, a liquid crystal display and its control device. The touch panel and the liquid crystal display consist of a touch panel display in the present embodiment.

The control section 203 shows a control screen on the input / output section 204 and generates a lock / unlock request corresponding to the operation performed by the accepting / delivering subscriber. For example, the control section 203 an unlock icon, a lock icon, and the like to the touch panel display, and generates an unlock request or a lock request based on the operation performed by the accepting / delivering subscriber. Note that the operation performed by the accepting / delivering subscriber is not limited to an operation performed via the touch panel display. For example, the operation may be an operation performed via a hardware switch and the like.

Furthermore, the control section leads 203 a process in which terminal authentication information from the central server 400 be retrieved. Note that the terminal authentication information is not information (not a key ID) on the basis of which the lock / unlock device 300 the key unit 100 but information is based on the key unit 100 the subscriber terminal 200 authenticated (for example, authentication information corresponding to authentication information that the key unit 100 in the vehicle 10 is provided). More precisely, the control section 203 that the communication section 202 via the acceptance / delivery management server 500 a request for an output of terminal authentication information to the central server 400 sends. The "request for issuance of terminal authentication information" as used herein includes the identification information of the subscriber terminal 200 and a signal requesting output of terminal authentication information, that of the key unit 100 to own, one. The central server 400 that receives the request for outputting terminal authentication information sends the terminal authentication information that is in the vehicle 10 provided key unit 100 to own, to the subscriber terminal 200 , As a result, at the subscriber terminal 200 an operation will be performed to the vehicle 10 to unlock. Note that if the subscriber terminal 200 does not have the terminal authentication information, no interlocking operation or unlocking operation on the vehicle from an operation screen 10 can be carried out.

In the present embodiment, the terminal authentication information provided by the subscriber terminal 200 be retrieved, a one-time key, which becomes invalid if the cargo door is locked at the conclusion of the acceptance / delivery operation by the accepting / delivering subscriber. For example, when receiving the from the central server 400 sent terminal authentication information by the subscriber terminal 200 the terminal authentication information in a memory section (not shown) of the subscriber terminal 200 and then the terminal authentication information is deleted from the storage section as soon as a lock message issued by the key unit 100 is sent when the cargo door is locked at the completion of the acceptance / delivery operation, at the subscriber terminal 200 Will be received.

Note that a time at which the memory portion of the subscriber terminal 200 stored terminal authentication information is deleted, not limited to the above example and the procedure a predetermined time from a time at which the subscriber terminal 200 that from the central server 400 sent terminal authentication information (from a time when the central server 400 the terminal authentication information to the subscriber terminal 200 has sent). Further, the terminal authentication information is not limited to the above-mentioned one-time key, and may be a limited key that is valid only during a predetermined time zone. Regardless of whether the terminal authentication information is a one-time key or a limited key, device authentication information corresponding to the terminal authentication information must be pre-set in the key unit 100 get saved.

Now the subscriber terminal 50 described by the instructing participant. Similar to the subscriber terminal 200 can the subscriber terminal 50 a small computer such as a smart phone, a mobile phone, a tablet terminal, a personal information terminal and a wearable computer (a smartwatch and the like), or may be a personal computer. The subscriber terminal 50 of the instructing participant consists of a communication section 51 a control section 52 and an input / output section 53 ,

The communication section 51 is functionally the communication section 202 is equivalent and is a communication device for connection of the subscriber terminal 50 with the net N1 , The control section 52 is a computer for managing a controller of the subscriber terminal 50 , The control section 52 For example, it consists of a microcomputer and implements a function of performing various processes by causing a CPU (not shown) to execute programs stored in a storage device (a ROM and the like). For example, the control section performs 52 the default application to go over the input / output section 53 an acceptance / delivery request for an acceptance / delivery package to the acceptance / delivery management server 500 a given parcel delivery company. The input / output section 53 functionally similar to the input / output section 204 as means for receiving an input operation performed by the assignee and providing the information to the assignee.

Now, a screen where the instructing party becomes an input operation for the acceptance / delivery request for the acceptance / delivery packet via the input / output section 53 performs, with reference to 3 described. 3 FIG. 10 is an example of an acceptance / delivery information registration screen through which the instructing party inputs acceptance / delivery information about a package. An acceptance / delivery information registration screen SC1 is provided by an application to service through the trunk share system 1 to use. At the acceptance / delivery information registration screen SC1 are each fields for one SC11 for information about an assigning participant (ID, full name), for an acceptance / delivery package ID SC12 for an acceptance / delivery category SC13 for an acceptance / delivery target vehicle SC14 , for a vehicle position SC15 , for an acceptance / delivery area SC16 and for one SC17 for an ineligible acceptance / delivery area and a registration button SC18 displayed as "ENTRY".

The SC11 for information about the instructing party (ID, full name) is a field for displaying information about the instructing party. The information about the instructing participant is entered in advance by a given application. The acceptance / delivery package ID SC12 is a field for entering identification information about the acceptance / delivery packet. The acceptance / delivery package ID may be a delivery note number of the acceptance / delivery package or may be from the acceptance / delivery management server 500 numbered at the time of entry of the acceptance / delivery information. The acceptance / delivery category SC13 is a field for selecting a category according to whether a package is to be delivered or accepted as an acceptance / delivery object. The acceptance / delivery target vehicle SC14 is a field for the assignee to the vehicle 10 selected as the acceptance / delivery target vehicle for the package. For example, on the pickup / delivery target vehicle SC14 the vehicle entered in advance by a given application 10 , which is associated with the assigning participant, displayed as an option. The vehicle position SC15 is a field for inputting a parking position of the vehicle 10 , which is designated by the commissioning participant as acceptance / delivery vehicle. The commissioning participant can determine the parking position of the vehicle 10 as an acceptance / delivery destination by inputting the parking position of the vehicle 10 into the field of the vehicle position SC15 to name. Note that the commissioning participant the specific parking position of the vehicle 10 as an acceptance / delivery target not already in a request for an acceptance / delivery, that is at the Entry of acceptance / delivery information into the field of vehicle position SC15 must enter. In a case where the contracting subscriber the parking position of the vehicle 10 does not indicate as the acceptance / delivery destination, the accepting / delivering subscriber may determine the parking position of the vehicle 10 upon acceptance / delivery via the acceptance / delivery management server 500 from the central server 400 Interrogate. The acceptance / delivery area- SC16 is a field for entering the address of an area where the instructing party desires to accept or deliver the package, eg, a city, a district, a community, a village, a postal code, or the like. The field for the SC17 for a disqualifying acceptance / delivery area is a field for entering the address of an area where the calling party does not want to accept or deliver the package, eg a city, a district, a community, a village, a postal code or like. The registration button SC 18 is an operator button to display information displayed on the Acceptance / Delivery Information Registration screen. SC1 can be selected or entered as acceptance / delivery information to the acceptance / delivery management server 500 to send. When clicking on the entry button SC18 is pressed, stores the acceptance / delivery management server 500 the received acceptance / delivery information in an acceptance / delivery management DB 503 ,

Note that in 2 the subscriber terminal 50 has no configuration corresponding to the short-range communication section 201 is really similar, but the subscriber terminal 50 may have such a configuration that the locking / unlocking device 300 from the subscriber terminal 50 is pressed out, so that the control section 52 a process of retrieving terminal authentication information from the central server 400 performs as the control section 203 , and the terminal authentication information about short-range wireless communication to the key unit 100 sends.

Now, the Acceptance / Delivery Management Server 500 described. The acceptance / delivery management server 500 has a universal computer configuration and, if a plurality of parcel delivery companies, the trunk share system 1 Each of the parcel delivery companies sets up at least one Acceptance / Delivery Management Server as their own management server. The acceptance / delivery management server 500 is a computer including a processor (not shown), such as a central processing unit (CPU) or a digital signal processor (DSP), a main memory section (not shown), such as random access memory (RAM) and read-only memory. Memory (RAM), and an auxiliary memory section (not shown), such as an erasable programmable ROM (EPROM), a hard disk drive (HDD) and a removable medium includes. Note that the removable medium is, for example, a universal serial bus (USB) memory or a disc recording medium such as a compact disc (CD) and a digital versatile disc (DVD). In the auxiliary storage section, an operating system (OS), various programs, various tables, and the like are stored, and a program stored therein is loaded into a work area of the main storage section and executed so that each component and the like is controlled to execute the program, thereby making it possible is to implement a function that corresponds to a given object.

Further, the acceptance / delivery management server has 500 a communication section 501 on. The communication section 501 is connected to other devices and performs communication between the acceptance / delivery management server 500 and the other devices (eg the central server 400 , the subscriber terminal 200 and the like). The communication section 501 is, for example, a Local Area Network (LAN) interface board or a wireless communication circuit for wireless communication. The LAN interface board or radio communication circuit is connected to the network N1 , such as the Internet, which is a public communications network.

Further, the acceptance / delivery management server has 500 the acceptance / delivery DB (database) 503 in which the acceptance / delivery information is stored. The acceptance / delivery DB 503 is arranged to store the acceptance / delivery information in the auxiliary storage section and to associate the charging agent with the acceptance / delivery information contained therein. The acceptance / delivery DB 503 is set up so that a program of a database management system (DBMS) to be executed by a processor manages data to be stored in the auxiliary storage section. The acceptance / delivery DB 503 is, for example, a relational database.

Now, a configuration of the in the acceptance / delivery DB 503 stored information with reference to 4 described. 4 FIG. 12 illustrates an example of a data structure of the acceptance / delivery information. An acceptance / delivery information table in which the acceptance / delivery information is stored has fields for an ID of an ID instructor, an article ID, an acceptance / delivery category, a date and time for an acceptance / delivery, an acceptance / delivery target vehicle, an acceptance / delivery area, and an acceptance / delivery status.

Identification information for specifying the instructing party is stored in the ID field of the instructing party. Identification information about a package to be accepted or delivered is stored in the Acceptance / Delivery Package ID field. The acceptance / delivery package ID may be a delivery note number assigned to a package as an acceptance / delivery object by the package delivery company. Information indicating whether an acceptance / delivery package is being delivered or accepted by the accepting / delivering participant is stored in the acceptance / delivery category field. Information indicating a date and time for acceptance or delivery of the acceptance / delivery package is stored in the date and time of acceptance / delivery field. More specifically, the acceptance / delivery time may be a certain time or may be a certain time zone in which an acceptance / delivery is requested. Identification information about the vehicle 10 that is designated by the assignee as the acceptance / delivery destination is stored in the accept / delivery destination vehicle ID field. The acceptance / delivery destination vehicle ID is identification information about the vehicle 10 which is registered in advance by a given application or the like in connection with the ID of the instructing party. Information for specifying an area where the assignee wishes to accept or deliver the parcel is stored in the acceptance / delivery area field. The acceptance / delivery area is an area requested by a user as an acceptance / delivery destination without the parking position of the vehicle 10 Specify exactly, and the acceptance / delivery area can be named, for example, according to a city, a district, a community, a village, an area specified by a postal code, or the like. Information for specifying an area where the assignee does not wish to accept or deliver the parcel is stored in the acceptance / delivery area field. The ineligible acceptance / delivery area is an area that is not requested by a user as an acceptance / delivery destination, and the disqualified acceptance / delivery area may be, for example, a city, a district, a community, a village , an area indicated by a postal code, or the like. Information showing whether acceptance / delivery of the acceptance / delivery package has been carried out by the accepting / delivering agent is stored in the acceptance / delivery status field. When the acceptance / delivery of the acceptance / delivery package has been carried out, "COMPLETED" is entered in the acceptance / delivery status field, and if the acceptance / delivery of the acceptance / delivery package has not been carried out, "NOT PERFORMED" is included in the acceptance - / delivery status field entered. Further, in a case where the vehicle 10 is not parked at a notified body, or in a case where the vehicle 10 is parked in the ineligible acceptance / delivery area, is suspended for delivery / delivery of the package, and "ISSUED" is entered in the acceptance / delivery status.

Furthermore, vehicle management information in which the charging subscriber with the vehicle 10 as the corresponding acceptance / delivery point, in the Acceptance / Delivery Management DB 503 saved. A configuration of the vehicle management information will be described with reference to FIG 5 described. 5 FIG. 12 illustrates an example of a data structure of the vehicle management information. A vehicle management information table in which the vehicle management information is stored includes fields for an ID of the charging subscriber, an acceptance / delivery target vehicle ID, a vehicle type, a number, and a vehicle position.

Identification information for specifying the instructing party is stored in the ID field of the instructing party. Identification information about the vehicle 10 that is associated with the assignee is stored in the accept / delivery destination vehicle ID field. The commissioning participant can use several vehicles 10 be associated. In this case, the commissioning participant can use different vehicles 10 designate as acceptance / delivery targets for the individual packages as acceptance / delivery objects. Information (the type of vehicle, the color of the vehicle, its number) to identify the vehicle 10 are stored in the vehicle type field, in the color field and in the number field so that the accepting / delivering subscriber designates the vehicle designated as the acceptance / delivery destination 10 Can be found. Information about the parking position of the vehicle 10 are stored in the vehicle position field. The vehicle position may be from an input of the instructing subscriber via the subscriber terminal 50 be determined, or the position information about the vehicle 10 coming from the central server 400 detected can be transmitted via a data communication device (not shown) in the vehicle 10 is provided from the central server 400 be retrieved.

In the acceptance / delivery management server 500 becomes a control section by executing a program by the processor 502 designed as a functional part. The control section 502 performs management control such as entry, update and the like of the acceptance / delivery information at the acceptance / delivery management DB 503 and a management controller such as one to the subscriber terminal 200 the acceptance / delivery request addressed by the accepting / delivering participant and transmission of the acceptance / delivery information. The control section 502 has an acceptance / delivery requesting section 5021 a vehicle detection section 5022 and an acceptance / delivery management section 5023 on.

The acceptance / delivery request section 5021 addresses a request for acceptance / delivery of the packet to the subscriber terminal 200 the accepting / delivering participant based on the acceptance / delivery information included in the acceptance / delivery management DB 503 are stored. For example, if the acceptance / delivery request section 5021 the request for acceptance / delivery of the package from the charging subscriber via the subscriber terminal 50 receives, then generates the acceptance / delivery requesting section 5021 Acceptance / delivery information corresponding to the instructing party, by associating identification information about the instructing party with identification information (an acceptance / delivery package ID) of the acceptance / delivery packet, identification information (an acceptance / delivery destination vehicle ID) of the vehicle 10 as an acceptance / delivery destination, an acceptance / delivery area, and the like, and stores the acceptance / delivery information in the acceptance / delivery management DB 503 Further, in a case where the transmission of a change of information on the date and time of an acceptance / delivery or on the acceptance / delivery area is inputted from a calling party after the acceptance / delivery information has been generated, the thus stored assumption - / delivery information updated according to the change. As for the acceptance / delivery information having an acceptance / delivery status of "NOT PERFORMED", the acceptance / delivery requesting section transmits 5021 the subscriber terminal 200 of the accepting / delivering participant, the acceptance / delivery information other than information about an acceptance / delivery point, which is the parking position of the vehicle 10 and thus the acceptance / delivery requesting section 5021 a request for an acceptance / delivery of the package. The accepting / delivering subscriber may be based on the subscriber's terminal 200 move received acceptance / delivery information to the acceptance / delivery area designated as the acceptance / delivery destination for the acceptance / delivery package.

The vehicle detection section 5022 detects that the delivery vehicle 20 has moved to the acceptance / delivery area for acceptance / delivery of the acceptance / delivery package, or that the vehicle 10 as the acceptance / delivery destination has moved into the ineligible acceptance / delivery area. The vehicle detection section 5022 For example, it retrieves position information that is measured based on a signal from one in the delivery vehicle 20 provided GPS receiver via one in the delivery vehicle 20 provided data communication device (not shown) is received, so that the vehicle detection section 5022 Location information about the delivery vehicle 20 can call. Note that the vehicle detection section 5022 Position information about the subscriber terminal 200 of the accepting / delivering subscriber over the network N1 and retrieve this as position information about the delivery vehicle 20 can use. Further, the vehicle detection section may 5022 also position information about the vehicle 10 as the acceptance / delivery destination, similar to the delivery vehicle 20 , The vehicle detection section 5022 can the position information about the vehicle 10 as the acceptance / delivery destination from the central server 400 recall.

The vehicle detection section 5022 can provide the position information (information about latitude and longitude via gps) relevant to the delivery vehicle 20 or the vehicle 10 as an acceptance / delivery destination, using a database with position reference information, which are provided by public institutions and the like, convert into address information. If the converted address is included in the acceptance / delivery area or in the ineligible acceptance / delivery area, the vehicle detection section may 5022 capture that the delivery vehicle 20 or the vehicle 10 when the acceptance / delivery destination has moved to the Acceptance / Delivery area or the ineligible Acceptance / Delivery area. The vehicle detection section 5022 retrieves the position information about these vehicles at regular intervals, so that the Vehicle detection section 5022 can capture that the delivery vehicle 20 has moved into the acceptance / delivery area or that the vehicle 10 as the acceptance / delivery destination has moved into the ineligible acceptance / delivery area.

When it detects that the delivery vehicle 20 has moved to the acceptance / delivery area, the acceptance / delivery management section transmits 5023 the subscriber terminal 200 the receiving / delivering subscriber information about the parking position of the vehicle 10 which has been designated as the acceptance / delivery destination for the package. By receiving information about the parking position of the vehicle 10 at the subscriber terminal 200 the accepting / delivering subscriber gives the vehicle 10 as the acceptance / delivery destination so that the accepting / delivering participant can accept or deliver the package.

When it detects that the delivery vehicle 20 has moved to the acceptance / delivery area, the accept / delivery management section calls 5023 Information about a current position of the vehicle 10 which has been named as the acceptance / delivery destination for the package, for example from the central server 400 from. When the vehicle 10 not in the acceptance / delivery area, the acceptance / delivery management section 5023 a message with the command to suspend the acceptance / delivery, to the subscriber terminal 200 of the accepting / delivering subscriber without the subscriber terminal 200 Information about the parking position of the vehicle 10 to convey.

In a case where the vehicle is 10 as the acceptance / delivery destination moves and the vehicle 10 is tracked for acceptance / delivery, the acceptance / delivery management section 5023 when it detects that the vehicle 10 has moved to the disqualified acceptance / delivery area, a message with the command to suspend acceptance / delivery to the subscriber terminal 200 the receiving / delivering subscriber.

Further, the acceptance / delivery management section communicates 5023 with the subscriber terminal 200 of the accepting / delivering subscriber via the communication section 501 and updates status of the acceptance / delivery package included in the acceptance / delivery information. For example, the acceptance / delivery management section receives 5023 from the subscriber terminal 200 Status information (eg, information showing execution of an acceptance / delivery) received from the accepting / delivering subscriber through the input / output section 204 and updates appropriate acceptance / delivery information. When the acceptance / delivery management section 5023 the subscriber terminal 200 command to suspend acceptance / delivery, the acceptance / delivery management section updates 5023 the acceptance / delivery status in the acceptance / delivery information table in "SUSPENDED".

Further, the acceptance / delivery management section sends 5023 an acceptance / delivery command to the subscriber terminal 200 such that the accepting / delivering subscriber sets the acceptance / delivery package on the vehicle based on the acceptance / delivery information and the vehicle management information associated with the charging agent 10 accept or deliver. Note that the acceptance / delivery command not only once, but several times to the subscriber terminal 200 can be sent. For example, on the day prior to the scheduled delivery / delivery date, acceptance / delivery instructions associated with next day acceptance / delivery collectively to the subscriber terminal 200 of the accepting / delivering participant, and the acceptance / delivery commands may be resent on the day the acceptance / delivery is scheduled. Note that in a case where the acceptance / delivery information is updated on the second transmission, the update content is reflected.

Each of the functional components of the acceptance / delivery management server 500 or some of their processes can be executed by other computers connected to the network N1 are connected. Further, a number of processes may be performed by the Acceptance / Delivery Management Server 500 are executed by hardware and can also be executed by software.

Now the central server 400 described. The central server 400 also has the configuration of a general-purpose computer and its basic hardware configuration is the same as the adoption / delivery management server 500 , The central server 400 has a processor (not shown), a main memory section and an auxiliary memory section. Thus, a program stored in the auxiliary storage section is loaded into a work area of the main memory section and executed so that each component and the like are controlled via the execution of the program, thereby making it possible to implement a function that is predetermined Object corresponds. Furthermore, the central server points 400 also a communication section 401 on. The communication section 401 is functional to the communication section 501 equivalent in the Acceptance / Delivery Management Server 500 is included, and performs communication between the central server 400 and other devices (eg, the acceptance / delivery management server 500 and so on).

Furthermore, the central server points 400 in the auxiliary memory section, a subscriber information DB 403 in which various information is stored, and an authentication information DB 404 on. These databases (DB) are set up so that a program of a database management system to be executed by a processor manages data to be stored in the auxiliary storage section. The subscriber information DB 403 and the authentication information DB 404 are for example relational databases.

Identification information about a subscriber who owns the vehicle 10 used (for example, the accepting / delivering participant, the an acceptance / delivery package to the vehicle 10 deliverer, or the instructing participant who accepts the thus delivered acceptance / delivery package) and the like are stored in the subscriber information DB 403 saved.

Authentication information about the vehicle 10 that correspond to the terminal authentication information are included in the authentication information DB 404 saved. The authentication information about the vehicle 10 are information that matches the identification information (the key ID) of the vehicle 10 and can be identification information belonging to the key unit 100 to own, for example, in the vehicle on-board device 10A is provided. Further, in addition to the authentication information about the vehicle 10 a validity period (including a validity time zone) of the authentication information, information on whether the authentication information is expired or not, and the like in the authentication information DB 404 get saved. The validity period of the authentication information, together with the authentication information to the subscriber terminal 200 sent by the accepting / delivering subscriber. When the subscriber terminal 200 of the accepting / delivering subscriber receives the validity period of the authentication information, the subscriber terminal 200 Dropping authentication information that exceeds its validity period so that the authentication information becomes invalid. Further, the information as to whether the authentication information expires or not shows whether the authentication information is sent to the user terminal 200 are sent and valid, or whether the authentication information exceeds the validity period and expire. In a case where the authentication information to the subscriber terminal 200 are sent and valid, prevents an authentication information management section 4021 (described below) that authentication information is issued with a validity period overlap, whereby redundant outputs of the authentication information can be prevented.

Further, in the central server 400 by executing a program by the processor, a control section 402 formed as a functional part. The control section 402 performs control with respect to the output of the authentication information to the subscriber terminal 200 and the like. More specifically, the control section 402 the authentication information management section 4021 as a functional part.

The authentication information management section 4021 manages the issue of authentication information for locking and unlocking the vehicle 10 , More specifically, the authentication information management section receives 4021 a request for an output of authentication information for locking and unlocking the vehicle 10 from the subscriber terminal 200 of the accepting / delivering subscriber via the acceptance / delivery management server 500 , The authentication information management section 4021 receives the request for an output of the authentication information and the information about the subscriber terminal 200 as the destination to which the authentication information is output. The authentication information management section 4021 sends authentication information (terminal authentication information) to the key unit 100 correspond to the subscriber terminal 200 via the acceptance / delivery management server 500 , The authentication information management section 4021 can generate authentication information, including information about a validity period. Also in a case where the key unit 100 the vehicle on-board device 10A receives the authentication information including the validity period information, determines the key unit 100 the vehicle on-board device 10A in that the authentication information is invalid when the validity period has ended and does not lock or unlock the vehicle 10 out.

Each of the functional components of the central server 400 or some of their processes can be run by other computers connected to the network N1 are connected. Furthermore, a number of processes can be performed by the central server 400 are executed by hardware and can also be executed by software.

process flow

6 Fig. 10 is a flowchart illustrating an acceptance / delivery destination transmission process executed by the acceptance / delivery management server. For example, the flow of the process begins when the Acceptance / Delivery Management Server 500 an entry of acceptance / delivery information from the subscriber terminal 50 of the instructing subscriber.

First, the acceptance / delivery requesting section determines 5021 in S101 Whether there is an inadvertent acceptance / delivery request or not. For example, the acceptance / delivery requesting section determines 5021 whether acceptance / delivery information having an acceptance / delivery status "NOT EXECUTED" in the acceptance / delivery information table of the acceptance / delivery management DB 503 are present or not, so that it can be determined whether or not there is an inadvertent acceptance / delivery request. If there is an inaccurate acceptance / delivery request ( S101 : Yes), the process is going on S102 continue. If there is no unused delivery / delivery request ( S101 : No), the acceptance / delivery destination submission process that is in 6 is shown finished.

In S102 transmits the acceptance / delivery request section 5021 the subscriber terminal 200 of the accepting / delivering participant acceptance / delivery information including an acceptance / delivery area requested by the calling party, as an acceptance / delivery destination to make requests for acceptance / delivery of a package as acceptance / delivery object. Note that the in S102 to the subscriber terminal 200 transmitted acceptance / delivery information does not contain any detailed information regarding the parking position of the vehicle 10 specify. The accepting / delivering subscriber makes on the basis of information about the acceptance / delivery area, which he from the subscriber terminal 200 receives in the acceptance / delivery area.

Note that the acceptance / delivery requesting section 5021 may include in the acceptance / delivery information information about a non-eligible acceptance / delivery area where the assigning agent does not wish to accept or deliver the package. As a result, for example, in a case where the vehicle 10 is tracked as the acceptance / delivery destination for the acceptance / delivery of the parcel while the vehicle 10 moved, the subscriber terminal 200 order the receiving / delivering subscriber to suspend the acceptance / delivery of the package, if it is detected that the vehicle 10 when the acceptance / delivery target has entered the ineligible acceptance / delivery area.

In S103 the vehicle detection section calls 5022 Location information about the delivery vehicle 20 while this is moving. The vehicle detection section 5022 can be considered the position information about the delivery vehicle 20 Position information measured based on a signal from that in the delivery vehicle 20 provided GPS receiver, or position information on the subscriber terminal 200 of the accepting / delivering subscriber over the network N1 recall. The process of S103 is repeatedly performed at predetermined intervals, so that the vehicle detection section 5022 can capture that the delivery vehicle 20 moved into the acceptance / delivery area.

In S104 the vehicle detection section determines 5022 whether the delivery vehicle 20 moved to the receiving / delivery area or not. The vehicle detection section 5022 converts the position information about the delivery vehicle 20 , in the S103 in address information and determines whether the converted address in the to the subscriber terminal 200 the receiving / delivering participant's receiving / delivering area or not. If the converted address is included in the acceptance / delivery area, the vehicle detection section may 5022 determine that the delivery vehicle 20 moved into the acceptance / delivery area. If it is determined (detected) that the delivery vehicle 20 has moved to the receiving / delivery area ( S104 : Yes), the process is going on S105 continue. If it is not determined that the delivery vehicle 20 has moved to the receiving / delivery area ( S104 : No), the process goes on S107 continue.

In S105 call the Acceptance / Delivery Management section 5023 Position information about the vehicle 10 as the acceptance / Delivery destination. The acceptance / delivery management section 5023 can the position information about the vehicle 10 as the acceptance / delivery destination, for example via the central server 400 recall.

In S106 the acceptance / delivery management section determines 5023 whether the vehicle is 10 as the acceptance / delivery destination is in the acceptance / delivery area or not. The acceptance / delivery management section 5023 converts the position information about the vehicle 10 as the acceptance / delivery destination, which in S105 in address information and determines whether the converted address is included in the accept / delivery area sent to the subscriber terminal 200 of the accepting / delivering participant or not. If the converted address is included in the acceptance / delivery area, the vehicle detection section may 5022 determine that the vehicle is 10 as the acceptance / delivery destination in the acceptance / delivery area. If it is determined that the vehicle 10 as the acceptance / delivery destination in the acceptance / delivery area ( S106 : Yes), the process is going on S109 continue. If it is determined that the vehicle 10 as the acceptance / delivery destination is not in the acceptance / delivery area ( S106 : No), the acceptance / delivery destination submission process that is in 6 is shown finished.

In S107 the vehicle detection section determines 5022 whether the vehicle is 10 when the acceptance / delivery destination has moved to the ineligible acceptance / delivery area or not. The vehicle detection section 5022 converts the position information about the vehicle 10 as the acceptance / delivery destination, which in S105 in address information and determines whether or not the converted address is included in the disqualified acceptance / delivery area. Note that the information about the acceptance / delivery area is included in the acceptance / delivery information included in S102 to the subscriber terminal 200 be transmitted. If the converted address is included in the disqualified acceptance / delivery area, the vehicle detection section may 5022 determine that the vehicle is 10 as the acceptance / delivery destination has moved into the ineligible acceptance / delivery area. If it is determined (detected) that the vehicle 10 when the acceptance / delivery destination moved into the ineligible acceptance / delivery area ( S106 : Yes), the process is going on S108 continue. If it is not determined that the vehicle 10 when the acceptance / delivery destination moved into the ineligible acceptance / delivery area ( S107 : No), the process returns S103 back.

Note that the process of S107 is a process that is passed to when the vehicle is moving 10 as the acceptance / delivery destination moves and the package by tracking the vehicle 10 accepted or delivered. That is, due to the tracking of the vehicle 10 the case occurs that the vehicle 10 moves into the non-eligible acceptance / delivery area where the commissioning agent does not wish to accept or deliver the package. The vehicle detection section 5022 can capture that the vehicle is 10 when the acceptance / delivery destination has moved to the ineligible acceptance / delivery area, which in S102 was transmitted. If it is detected that the vehicle 10 when the acceptance / delivery destination has moved to the ineligible acceptance / delivery area, the Acceptance / Delivery Management section orders 5023 the subscriber terminal 200 the accepting / delivering participant to suspend the acceptance / delivery destination of the package. This allows the accepting / delivering subscriber to suspend acceptance / delivery by tracking in the ineligible acceptance / delivery area.

In S108 detects the acceptance / delivery management section 5023 that the vehicle is 10 as the acceptance / delivery destination is not in the acceptance / delivery area and that the vehicle 10 has moved into the ineligible acceptance / delivery area, and the Acceptance / Delivery Management section 5023 commands the subscriber terminal 200 the accepting / delivering participant to suspend acceptance / delivery of the parcel. In order to command the suspension of acceptance / delivery, the acceptance / delivery management section 5023 for example, via a predetermined application in the subscriber terminal 200 of the accepting / delivering subscriber is installed at the input / output section 204 Display a message requesting suspension of acceptance / delivery. Further, the acceptance / delivery management section 5023 by an e-mail, a short message service (SMS), a multimedia message service (MMS) and the like to the subscriber terminal 200 the receiving / delivering subscriber send a message instructing him / her to suspend the acceptance / delivery. If the acceptance / delivery is suspended, the acceptance / delivery requesting section may 5021 the subscriber terminal 50 the assigning participant via a given application or an e-mail, an SMS, a MMS and the like, that the acceptance / delivery of the parcel is suspended.

In S109 transmitted by the acceptance / delivery management section 5023 a parking position of the vehicle 10 as an acceptance / delivery destination to the subscriber terminal 200 of the accepting / delivering participant. If the vehicle 10 is not parked as an acceptance / delivery destination, the acceptance / delivery management section 5023 to the subscriber terminal 50 send a message to the instructing participant requesting that the instructing participant be called the vehicle 10 to park. If the vehicle 10 is parked, the acceptance / delivery management section transmits 5023 the subscriber terminal 200 of the accepting / delivering subscriber his parking position. The parking position of the vehicle 10 as the acceptance / delivery destination is the subscriber terminal 200 of the accepting / delivering participant, and that in 6 The acceptance / delivery destination transmission process shown is ended.

The accepting / delivering subscriber identifies the vehicle 10 as the acceptance / delivery destination based on the parking position of the vehicle 10 to the subscriber terminal 200 has been transmitted. The accepting / delivering subscriber places the subscriber terminal 200 the accepting / submitting subscriber requests authentication information to the vehicle 10 to the acceptance / delivery management server 500 , The acceptance / delivery management server 500 puts to the central server 400 a request for sending the authentication information for unlocking the vehicle 10 to the subscriber terminal 200 of the accepting / delivering participant. The acceptance / delivery management server 500 can the authentication information from the central server 400 and retrieve them from the Acceptance / Delivery Management server 500 to the subscriber terminal 200 the receiving / delivering subscriber. Further, the acceptance / delivery management section 5023 of the acceptance / delivery management server 500 the authentication information for unlocking the vehicle 10 together with the parking position of the vehicle 10 to the subscriber terminal 200 of the accepting / delivering participant.

Effects of the first embodiment

If the trunk share system 1 detects that the delivery vehicle 20 has moved to the acceptance / delivery area, transmits the trunk share system 1 the subscriber terminal 200 of the accepting / delivering subscriber, the parking position of the vehicle 10 as acceptance / delivery target. As long as the delivery vehicle 20 has not moved to the receiving / delivery area, transmits the trunk share system 1 the subscriber terminal 200 the receiving / delivering subscriber does not have information about the exact parking position of the vehicle 10 as acceptance / delivery target. This gives the forwarder information about the parking position of the vehicle 10 as an acceptance / delivery target is not provided unnecessarily, whereby it is possible to protect the privacy of the assigning participant. Furthermore, the commissioning participant does not have a final parking position of the vehicle 10 as an acceptance / delivery destination while making a request for acceptance / delivery so that flexible acceptance and delivery of an acceptance / delivery package can be achieved.

Also in a case where the delivery vehicle 20 in the acceptance / delivery area, for example, when vehicle 10 As the acceptance / delivery destination moves, a case occurs that the vehicle 10 not in the acceptance / delivery area. In a case where the vehicle is 10 if the acceptance / delivery destination is not in the acceptance / delivery area, the Trunk Share System transmits 1 the subscriber terminal 200 the receiving / delivering subscriber has no information about the parking position of the vehicle 10 as acceptance / delivery target. This gives the forwarder information about the parking position of the vehicle 10 not unnecessarily provided, which makes it possible to protect the privacy of the assigning party.

If it is detected that the vehicle 10 when the acceptance / delivery destination has moved to the non-eligible acceptance / delivery area where the charging agent does not wish to receive or deliver the package by tracking, the Trunk Share System transmits 1 the subscriber terminal 200 the accepting / delivering participant orders to suspend acceptance / delivery of the parcel. This makes it possible to prohibit acceptance / delivery of the package in the not eligible acceptance / delivery area, so that the privacy of the assigning participant is protected.

When acceptance / delivery of the package is suspended, the trunk share system transmits 1 the subscriber terminal 50 of the instructing participant that the acceptance / delivery of the parcel is suspended. In this way, the commissioning participant can recognize that the acceptance / delivery of the package is suspended and he can make a request for acceptance / resumption of delivery.

If the vehicle 10 is not parked as an acceptance / delivery destination, sends the trunk share system 1 the subscriber terminal 50 the instructing participant a message that the assigning participant is to be prompted to the vehicle 10 to park. If the vehicle 10 is parked, the subscriber terminal is calling 200 of the accepting / delivering subscriber a parking position of the vehicle 10 so that the accepting / delivering subscriber can easily accept or deliver the parcel.

Second embodiment

If the delivery / delivery of the package is suspended, because the vehicle 10 in the second embodiment, when the acceptance / delivery destination is not in the acceptance / delivery area or has moved to the ineligible acceptance / delivery area, the acceptance / delivery management server receives 500 an acceptance / delivery resume request from the assignee. After receiving the acceptance / delivery resumption request, an acceptance / delivery resumption process is performed in a similar manner as the acceptance / delivery process in the first embodiment, so that a detailed description thereof is omitted here. The following is a description of an acceptance / delivery resume request receiving process.

7 Fig. 10 is a flowchart illustrating a pickup / delivery new order receiving process. The process flow begins when the adoption / delivery management server 500 the subscriber terminal 200 of the accepting / delivering subscriber sends an order to suspend acceptance / delivery of a parcel.

First, the acceptance / delivery requesting section determines 5021 in S201 Whether there is information about suspended delivery / delivery. For example, the acceptance / delivery requesting section determines 5021 whether acceptance / delivery information having an acceptance / delivery status "SUSPENDED" in the acceptance / delivery information table of the acceptance / delivery management DB 503 exist or not, so that it can be determined whether or not there is information about suspended delivery / delivery. If information about suspended delivery / delivery is available ( S201 : Yes), the process is going on S202 continue. If there is no information about suspended delivery / delivery ( S101 : No), the acceptance / delivery recovery receiving process which is in 7 is shown finished.

In S202 transmits the acceptance / delivery request section 5021 the subscriber terminal 50 of the instructing participant that the acceptance / delivery is suspended. The acceptance / delivery request section 5021 can via a given application in the subscriber terminal 50 of the assigning party is installed at the input / output section 53 display a message stating that acceptance / delivery is suspended. Further, the acceptance / delivery requesting section 5021 via an e-mail, an SMS, an MMS and the like, that the acceptance / delivery of the package is suspended.

In S203 determines the acceptance / delivery request section 5021 Whether there is an acceptance / delivery resume request or not. The instructing party can display the acceptance / delivery information registration screen (in 3 represented) via a predetermined application in the subscriber terminal 50 is installed, display and, for example, enter acceptance / delivery information for the acceptance / delivery resumption. The registered acceptance / delivery information is sent to the acceptance / delivery management server 500 so that its corresponding acceptance / delivery information in the acceptance / delivery information table is updated (reset). When the acceptance / delivery information for the acceptance / delivery resumption is entered, the acceptance / delivery requesting section may 5021 determine that there is an acceptance / delivery resume request. If there is an acceptance / delivery resume request ( S203 : Yes), the process is going on S204 continue. If there is no acceptance / delivery resume request ( S203 : No), the in 7 completed process finished.

In S204 calls the acceptance / delivery request section 5021 Acceptance / delivery information newly set by the acceptance / delivery resume request. In S205 be based on the in S204 retrieved acceptance / delivery information executes the same processes as the processes of S102 to S109 in 7 so that the in 7 process is terminated.

Effects of the second embodiment

When in Trunk Share System 1 If an acceptance / delivery of a parcel is suspended, the accepting / submitting participant may Acceptance / delivery of the parcel by retrieving information about an acceptance / delivery area located in the subscriber terminal 50 resumed by the assigning participant.

recording medium

A program that causes a computer, other machines and devices (hereinafter referred to as the computer and the like) to implement (implement) the output controller may be recorded on a recording medium that can be read by the computer and the like. By causing the computer and the like to read and execute the program on the recording medium, the computer functions as a central server 400 ,

Here, the recording medium that can be read by the computer and the like is a nonvolatile recording medium on which information such as data or a program is electrically, magnetically, optically, mechanically or chemically stored and from which the information is read by the computer or the like can be. As for such a recording medium, a recording medium which can be taken out of the computer and the like, for example, a flexible disk, a magneto-optical disk, a CD-ROM, a CD-R / W, a DVD, a Blu-ray disk ray disk, a DAT, an 8mm tape, a memory card such as a flash memory and the like. Further, a recording medium fixedly installed in the computer and the like includes a hard disk, a ROM (Read Only Memory), and the like. Further, a solid state drive (SSD) is also usable as a recording medium that can be taken out of the computer and the like or as a recording medium that is fixedly installed in the computer and the like.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited patent literature

• JP 2006206225 A [0002]

Claims (7)

Information processing system, comprising: an acceptance / delivery requesting section (5021) adapted to communicate to a terminal (200) of a carrier accepting or delivering a package information about an acceptance / delivery area where a user is awaiting acceptance or delivery of the package requesting acceptance or delivery of the package; a vehicle detection section (5022) adapted to detect that a delivery vehicle (20) with which the carrier accepts or delivers the package has moved to the acceptance / delivery area; and an acceptance / delivery management section (5023) adapted to provide to the terminal (200) of the carrier information about a parking position of an acceptance / delivery destination vehicle (10) designated by the user as an acceptance / delivery destination for the package, when the vehicle detection section (5022) detects that the delivery vehicle (20) has moved to the acceptance / delivery area. Information processing system according to Claim 1 wherein: when the vehicle detection section (5022) detects that the delivery vehicle (20) has moved to the acceptance / delivery area, the vehicle detection section (5022) determines whether the acceptance / delivery destination vehicle (10) is in acceptance / delivery. Delivery territory or not; and when the pickup / delivery target vehicle (10) is in the pickup / delivery area, the pickup / delivery management section (5023) transmits the information about the parking position of the pickup / delivery target vehicle (10) to the terminal (200) of the carrier; and if the pickup / delivery target vehicle (10) is not in the pickup / delivery area, the pickup / delivery management section (5023) sends a command to the terminal (200) of the carrier to suspend acceptance or delivery of the packet without the terminal (200) to provide the forwarder with information about the parking position of the receiving / delivery target vehicle (10). Information processing system according to Claim 1 wherein: the acceptance / delivery requesting section (5021) transmits to the terminal (200) of the carrier information about a non-eligible acceptance / delivery area where the user does not wish to receive or deliver the package; and then, when the vehicle detecting section (5022) detects that the pickup / delivery target vehicle (10) has moved to the ineligible pickup / delivery area, the pickup / delivery management section (5023) inputs to the terminal (200) of the carrier Sends command to suspend acceptance or delivery of the parcel without transmitting to the terminal (200) of the carrier the information about the parking position of the acceptance / delivery target vehicle (10). Information processing system according to Claim 2 or 3 wherein, when the dispatcher's terminal (200) is instructed to suspend acceptance or delivery of the packet, the acceptance / delivery management section (5023) transmits to the user's terminal (50) suspending the acceptance or delivery of the packet is. Information processing system according to one of Claims 1 to 4 wherein, when the pickup / delivery target vehicle (10) is not parked, the pickup / delivery management section (5023) sends a message to the user's terminal (50) requesting that the user request the pickup / delivery target vehicle (50) 10) to park. Information processing system according to one of Claims 1 to 5 wherein, when the dispatcher's terminal (200) is instructed to suspend acceptance or delivery of the package, the acceptance / delivery management portion (5023) updates information about the acceptance / delivery area received from the user's terminal (50) are discontinued. An information processing method comprising: Communicating information about an acceptance / delivery area requested by a user requesting acceptance or delivery of a parcel as the parcel receiving / delivering location from a computer to a terminal (200) of a freight forwarder; accept or deliver the package; Detecting that a delivery vehicle (20) with which the forwarder accepts or delivers the parcel has moved to the acceptance / delivery area; and when it is detected that the delivery vehicle (20) has moved to the acceptance / delivery area, transmitting information about a parking position of an acceptance / delivery destination vehicle (10) designated by the user as an acceptance / delivery destination for the package, to the terminal (200) of the freight forwarder.

Images