JP2013076223A - Management system, locking device and movable body - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that costs for maintaining a bicycle parking lot or a vehicle parking lot are high.SOLUTION: A management system comprises: an identification information receiving section for receiving movable body identification information to identify a movable body and request user identification information to identify a user requesting use of the movable body, from a locking device which is attached to the movable body and locks the movable body via a communication line; a movable body information storing section for storing the movable body identification information and use user identification information to identify a user allowed to use the movable body identified by the movable body identification information in association with each other; and a determining section for comparing the movable body identification information and the use user identification information stored in the movable body information storing section with the movable body identification information and the request user identification information received by the identification information receiving section to determine whether to unlock or not.

Description

  The present invention relates to a management system, a locking device, and a moving body.

In recent years, sharing services that share mobile objects such as bicycles and automobiles have attracted attention. For example, a user of a bicycle sharing service can rent a bicycle at an arbitrary bicycle parking lot and return the bicycle at an arbitrary bicycle parking lot (see Patent Document 1).
Japanese Patent Application Laid-Open No. 2011-34335

  However, in the conventional sharing service, an embedded automatic lending device is installed in the bicycle parking lot or the parking lot, and the maintenance cost of the bicycle parking lot or the parking lot becomes high.

  In the first aspect of the present invention, from the locking device attached to the moving body and locking the moving body, the moving body identification information for identifying the moving body and the requested user identification information for identifying the user who requests use of the moving body, For receiving the identification information receiving unit via the communication line, and the mobile object identification information and the use user identification information for identifying the user who can use the mobile object identified by the mobile object identification information in association with each other The information storage unit, the mobile unit identification information and user identification information stored in the mobile unit information storage unit, and the mobile unit identification information and requested user identification information received by the identification information reception unit are compared and unlocked. There is provided a management system including a determination unit that determines whether or not.

  In the above management system, when the determination unit determines to unlock the mobile object, the determination unit notifies the locking device of the mobile object of the user identification information associated with the mobile object identification information of the mobile object. Good. The management system includes: a user information storage unit that stores requested user identification information and terminal identification information that identifies a terminal possessed by the user identified by the requested user identification information; Mobile user identification information of the mobile body that the user requests to use, and the requested user identification information stored in the user information storage unit in association with the received terminal identification information and the received mobile object identification information. A mobile body information generation unit stored in the mobile body information storage unit in association with each other may be further provided.

  In the management system, the determination unit receives a request for stopping the use of the mobile body from the terminal or the mobile body, and the identification information reception unit receives the mobile body identification information, the requested user identification information, and the mobile body from the mobile body. When the lock confirmation signal is received, the mobile object information stored in the mobile object information storage unit and the user identification information to be used are compared with the received mobile object identification information and the requested user identification information to use the mobile object. It may be determined whether or not is canceled. In the above management system, when the determination unit determines that the use of the moving object is stopped, the use unit identification information associated with the moving object identification information of the moving object is deleted from the locking device of the moving object. An erasure request may be notified.

  In the above management system, the mobile body information generation unit receives, from the terminal, a request for stopping the use of the mobile body, the terminal identification information, and the mobile body identification information of the mobile body that the user requests to stop using, The requested user identification information associated with the received terminal identification information and stored in the user information storage unit may be associated with the received mobile object identification information and stored in the mobile object information storage unit. The management system may further include a relay unit that relays communication between the locking device and the identification information receiving unit. In the above management system, the mobile body information storage unit may store the mobile body identification information of the mobile body in association with the relay unit identification information for identifying the relay unit.

  According to a second aspect of the present invention, there is provided a method in which a server provides a service to a user's terminal via a communication line, the mobile body identifying information for identifying the mobile body from the mobile body, A step of receiving request user identification information for identifying a user who requests use via a communication line, and a user who identifies a user who can use the mobile object identified by the mobile object identification information and the mobile object identification information. Using the mobile body information associated with the identification information, the mobile body identification information and user identification information associated with the mobile body information are compared with the received mobile body identification information and the requested user identification information. And determining whether or not to unlock.

  According to a third aspect of the present invention, there is provided a locking device that is attached to a moving body and locks the moving body, and requests user identification information for identifying a user who requests use of the moving body from a storage element possessed by the user. An identification information acquisition unit for acquiring a user identification information for identifying a user who can use the mobile object from the management system, and an identification information storage unit for storing the received user identification information There is provided a locking device that includes a use user identification information stored in the table and a requesting user identification information acquired by an identification information acquisition unit and a determination unit that determines whether or not to unlock. In the above-described locking device, the identification information storage unit may erase the use user identification information when receiving a deletion request for requesting deletion of the use user identification information from the management system.

  In the 4th aspect of this invention, a mobile body provided with said locking device is provided.

  It should be noted that the above summary of the invention does not enumerate all the necessary features of the present invention. In addition, a sub-combination of these feature groups can also be an invention.

An example of management system 100 is shown roughly. An example of a system configuration of key device 130 is shown roughly. An example of a system configuration of management system 100 is shown roughly. An example of data structure 400 of mobile object database 310 is shown roughly. 1 schematically shows an example of a data structure 500 of a user database 312. An example of the information processing method in management system 100 is shown roughly. An example of the information processing method in management system 100 is shown roughly. An example of a system configuration of management system 800 is shown roughly. An example of data structure 900 of processing object database 816 is shown roughly. An example of the information processing method in management system 800 is shown roughly. An example of the information processing method in management system 800 is shown roughly.

  Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. In addition, not all the combinations of features described in the embodiments are essential for the solving means of the invention. In addition, embodiments will be described with reference to the drawings, but in the description of the drawings, the same or similar parts may be denoted by the same reference numerals and redundant description may be omitted.

  FIG. 1 schematically shows an example of a management system 100 together with a mobile object 10, a bicycle parking lot 12, a bicycle parking lot 14, a communication line 102, a key device 130, and a user terminal 140. In the present embodiment, the management system 100 manages the usage status of the plurality of mobile objects 10. The management system 100 according to this embodiment includes a server 110 and a relay device 120.

  The moving body 10 moves by a user operation. The moving body 10 may be a bicycle, a motorcycle, or a car. In the present embodiment, the moving body 10 is parked in the bicycle parking lot 12 or the bicycle parking lot 14. Further, a key device 130 that locks the moving body 10 is attached to the moving body 10.

  The communication line 102 may be the Internet, a dedicated line, a wireless packet communication network, and combinations thereof. For example, the Internet is used for communication between the server 110 and the relay device 120, and ZigBee, Bluetooth (registration) is used for communication between the relay device 120 and the key device 130 and communication between the relay devices 120. Short-range wireless communication such as trademark) is used. Communication between the server 110 and the key device 130 may be relayed by a plurality of relay devices 120.

  The server 110 transmits / receives information to / from at least one of the relay device 120, the key device 130, and the user terminal 140 via the communication line 102. The server 110 may be composed of a single server or a plurality of servers. The server 110 may be a virtual server or a cloud system. The server 110 may be a system or controller specialized for the application, or may be a general-purpose information processing device such as a personal computer. The server 110 may be an example of a management system.

  In the present embodiment, the server 110 manages the usage status of the plurality of mobile objects 10. For example, the server 110 manages the state of the mobile object 10 by distinguishing between “in use”, “available”, and “unusable”. The server 110 may manage the current position of the mobile object 10. Further, the server 110 may determine whether or not unlocking is possible according to a request from the user, and may control the unlocking operation of the key device 130 via the communication line 102.

  When the use of the mobile object 10 is requested from the user terminal 140, the server 110 performs user authentication and determines whether to unlock the key device 130. If the server 110 determines that the key device 130 is unlocked, the server 110 manages the state of the moving body 10 as “in use”.

  When the server 110 is requested to return the moving body 10 from the user terminal 140, the server 110 performs user authentication and confirmation of locking of the key device 130, and determines whether the moving body 10 has been returned. When the server 110 determines that the mobile object 10 has been returned, the server 110 manages the state of the mobile object 10 as “usable”.

  For example, when the remaining capacity of the battery of the key device 130 attached to the mobile body 10 is smaller than a predetermined value, the server 110 is connected to the mobile body 10 when the mobile body 10 or the key device 130 is out of order. If the location is unknown or the mobile body 10 is discarded, the mobile body 10 manages it as “unusable”.

  The relay device 120 transmits / receives information to / from at least one of the server 110 and the key device 130 via the communication line 102. The relay device 120 may be a system or controller specialized for the application, or may be a general-purpose information processing apparatus such as a personal computer. The relay device 120 may relay communication between the key device 130 and the server 110.

  In the present embodiment, the relay device 120 is disposed in each of the bicycle parking lot 12 and the bicycle parking lot 14. Thereby, the management system 100 can manage the current position of the moving body 10.

  Note that the relay device 120 may be an example of a management system. In the present embodiment, the case where the server 110 controls the unlocking operation of the key device 130 has been described. However, the management system 100 is not limited to this, and the relay device 120 may control the unlocking operation of the key device 130.

  The key device 130 locks the moving body 10 and restricts the use of the moving body 10. The key device 130 transmits and receives information to and from at least one of the server 110 and the relay device 120 via the communication line 102. The key device 130 performs an unlocking operation in response to an instruction or request from the management system 100. The key device 130 may communicate with the relay device 120 periodically. Thereby, the management system 100 can manage the usage status, current position, and the like of the mobile object 10. The key device 130 may be an example of a locking device.

  The user terminal 140 may be any device that can send and receive information to and from the server 110 via the communication line 102, and may be a personal computer, a mobile phone, a mobile terminal, or a wireless terminal in which Web browser software is installed. The user terminal 140 may be an example of a terminal owned by the user.

  As described above, according to the management system 100 of the present embodiment, it is possible to manage the usage status of the mobile object 10 by controlling the unlocking operation of the key device 130 attached to the mobile object 10 from the server 110. it can. Although not limited to this, the management system 100 is particularly useful when managing the use of a bicycle in a bicycle sharing service or rental service.

  In the conventional bicycle sharing service or rental service, a rack-type rental system is installed in the bicycle parking lot. In addition, bicycle parking lots are often provided every few hundred meters to several kilometers. Therefore, the maintenance cost of the bicycle parking lot becomes high. However, when the management system 100 of this embodiment is used, the usage status of the mobile body 10 can be managed by attaching the key device 130 to the mobile body 10. Thereby, the maintenance cost of a bicycle parking lot can be reduced significantly. In some cases, the usage status of the moving body 10 can be managed without providing a bicycle parking lot.

  FIG. 2 schematically shows an example of the system configuration of the key device 130. FIG. 2 shows the key device 130 together with the membership card 22, the communication line 102, and the user terminal 140. In the present embodiment, the key device 130 includes a locking unit 210 and a locking control unit 220. The locking control unit 220 includes an identification information acquisition unit 230, an identification information storage unit 240, and a determination unit 250. The membership card 22 has a storage element 202. The user terminal 140 may have a storage element 204.

  The membership card 22 proves that the user is a sharing service or a rental service. The membership card 22 may be used for user authentication processing when the user terminal owned by the user does not have the storage element 204.

  In the present embodiment, the storage element 202 and the storage element 204 store identification information unique to each element (sometimes referred to as an element ID). The element IDs stored in the storage element 202 and the storage element 204 may be an example of requested user identification information that identifies a user who requests use of the mobile object 10.

  The storage element 202 and the storage element 204 may be an RF tag, an IC tag, a semiconductor memory, a magnetic disk, a magnetic card, or the like. The memory element 202 and the memory element 204 are preferably IC chips such as an RF tag, an IC tag, and a Felica chip. Thereby, information can be transmitted to and received from the identification information acquisition unit 230 by short-range wireless communication.

  The locking unit 210 may lock the moving body 10 and restrict use of the moving body 10. The type of the locking part 210 is not particularly limited, but may be a horseshoe ring lock or a cylinder lock. The locking unit 210 may be unlocked based on an instruction from the locking control unit 220. The locking unit 210 may receive the signal permitting the unlocking operation from the locking control unit 220 and perform the unlocking operation. The user may perform the locking operation of the locking unit 210 manually. Thereby, the power consumption of the key device 130 can be significantly reduced. Note that the locking operation of the locking unit 210 may be performed by the locking unit 210 based on an instruction from the locking control unit 220.

  The locking control unit 220 may control at least the unlocking operation of the locking unit 210. The locking control unit 220 may determine whether or not to unlock the locking unit 210. When the locking control unit 220 determines to unlock the locking unit 210, the locking control unit 220 may permit the locking unit 210 to perform an unlocking operation. The locking control unit 220 may control the locking operation of the locking unit 210.

  The identification information acquisition unit 230 may transmit / receive information to / from the storage element 202 or the storage element 204. The identification information acquisition unit 230 preferably transmits and receives information to and from the storage element 202 or the storage element 204 by short-range wireless communication. The identification information acquisition unit 230 may be a RFID (Radio Frequency IDentification) reader. The identification information acquisition unit 230 may acquire the element ID from the storage element 202 or the storage element 204 possessed by the user.

  The identification information storage unit 240 may store a vehicle body number (may be referred to as a vehicle number) assigned to each moving body 10 to which the key device 130 is attached. The vehicle body number may be an example of moving body identification information for identifying the moving body 10. The identification information storage unit 240 includes a vehicle body number of the moving body 10 to which the key device 130 is attached, and used user identification information for identifying a user who can use the moving body 10 to which the key device 130 is attached (use user ID). May be stored in association with each other. The user ID used is preferably an element ID associated with a user who can use the mobile object 10.

  As another example of the mobile unit identification information, identification information assigned to each communication device (sometimes referred to as a communication device ID) such as ZigBeeID and macAddress can be exemplified. In this case, at least one of the server 110 and the relay device 120 obtains, for each of the plurality of moving bodies 10, the vehicle body number assigned to the moving body 10 and the communication device ID of the key device 130 attached to the moving body 10. You may store correspondingly.

  In the present embodiment, the identification information storage unit 240 receives the user ID of the mobile object 10 to which the key device 130 is attached from the server 110. The identification information storage unit 240 may store the body number of the moving body 10 to which the key device 130 is attached and the received use user ID in association with each other.

  The server 110 may transmit the used user ID to the identification information storage unit 240 when the element ID and the used user ID match. Therefore, in such a case, the server 110 may transmit a storage command for requesting storage of the element ID instead of transmitting the use user ID. Then, when receiving a storage command from the server 110, the identification information storage unit 240 may store the vehicle body number and the element ID in association with each other. Even in this case, since the element ID and the use user ID are the same, the identification information storage unit 240 stores the vehicle body number and the use user identification information in association with each other.

  In the present embodiment, the identification information storage unit 240 deletes the used user ID when receiving a deletion request for requesting deletion of the used user ID from the server 110. Therefore, when the server 110 manages the usage status of the mobile object 10 as “in use”, the user ID is stored in the identification information storage unit 240, and the server 110 uses the mobile object 10. When the situation is not managed as “in use”, the user ID is not stored in the identification information storage unit 240. Thereby, even when the mobile body 10 is moving out of the communication area, the determination unit 250 can grasp the usage status managed by the server 110.

  The determination unit 250 may determine whether or not to unlock by comparing the use user ID stored in the identification information storage unit 240 with the element ID acquired by the identification information acquisition unit 230. The determination unit 250 may determine to unlock when the use user ID and the element ID are associated or coincident with each other. The determination unit 250 may determine to unlock when receiving an unlocking permission signal permitting unlocking from the server 110. If the determination unit 250 determines to unlock, the determination unit 250 may notify the locking unit 210 of an unlock signal. The determination unit 250 may confirm unlocking of the locking unit 210 and notify the server 110 of an unlock confirmation signal. The determination unit 250 may confirm the locking of the locking unit 210 and notify the server 110 of a locking confirmation signal when the locking operation of the locking unit 210 is performed.

  In the present embodiment, when the use state of the mobile object 10 is “in use”, the use user ID is stored in the identification information storage unit 240. Therefore, even when the mobile body 10 cannot communicate with the management system 100, the determination unit 250 can determine whether or not unlocking is possible. This embodiment can obtain a particularly great effect when the moving body 10 is a bicycle or a motorcycle.

  FIG. 3 schematically shows an example of the system configuration of the management system 100. FIG. 3 schematically shows an example of the system configuration of the server 110 and the relay device 120 together with the membership card 22, the communication line 102, the key device 130, and the user terminal 140.

  In the present embodiment, the server 110 includes a mobile database 310, a user database 312, a relay device database 314, an identification information receiving unit 320, a determination unit 330, and a request processing unit 340. The relay device 120 includes a relay unit 350 and a registration processing unit 360.

  In the present embodiment, a case will be described in which the mobile database 310, the user database 312 and the relay device database 314 are configured as individual databases. However, the configuration of the database is not limited to this. Two or more of the mobile database 310, the user database 312 and the relay device database 314 may be configured as one database.

  The mobile body database 310 stores, for each of the plurality of mobile bodies 10, each vehicle body number and a use user ID that identifies a user who can use the mobile body 10 in association with each other. The usage user ID is not particularly limited as long as it is information for identifying the user, but is preferably an element ID associated with the user. Thereby, the determination unit 330 can easily determine whether unlocking is possible. The mobile object database 310 may be an example of a mobile object information storage unit. Other examples of the user ID used include the user's membership number, the terminal ID of the user terminal 140, the user's name or email address, and the like.

  The mobile object database 310 identifies identification information (which may be referred to as a relay device ID) for identifying each relay device 120 that has received the signal from the key device 130 and the vehicle body number for each of the plurality of mobile objects 10. May be stored in association with each other. The relay device ID may be an example of relay unit identification information. The mobile body database 310 may store each vehicle body number in association with each vehicle body number and usage status.

  The mobile database 310 may be updated when the server 110 processes a request from the user terminal 140. For example, the user uses the user terminal 140 to access a website on which the server 110 provides a service, and requests the server 110 to use the mobile object 10. The server 110 acquires the terminal ID from the user terminal 140 and authenticates the user. The server 110 executes the lending process of the mobile body 10 requested to be used, associates the vehicle body number of the mobile body 10 with the element ID corresponding to the terminal ID of the user terminal 140, and moves the mobile body database 310. To store.

  For each of a plurality of users, the user database 312 corresponds to an element ID of a storage element possessed by each of the plurality of users and terminal identification information (sometimes referred to as a terminal ID) for identifying the user terminal 140 possessed by the user. You may store it. The user database 312 may be updated when the server 110 executes a member registration process. The user database 312 may be an example of a user information storage unit.

  The terminal ID is not particularly limited as long as it is information different from the element ID and can identify the user terminal 140. The terminal ID may be identification information associated with the contractor information by the communication carrier. Such identification information may be referred to as carrier open ID, and is referred to as uid, subscriber ID, i-mode ID, etc. depending on the communication carrier. The terminal ID may be a unique ID written in the cookie when the user terminal 140 accesses the website.

  The relay device database 314 stores, for each of the plurality of relay devices 120, the relay device ID for identifying each relay device 120 and the installation location of the relay device 120 in association with each other. The relay device database 314 may store, for each of the plurality of relay devices 120, each relay device ID and bicycle parking lot identification information for identifying the bicycle parking lot in which the relay device 120 is installed.

  The identification information receiving unit 320 receives the vehicle body number and the element ID via the communication line 102. For example, the identification information receiving unit 320 is acquired from the key device 130 attached to the specific mobile body 10 from the vehicle body number of the mobile body 10 and the storage element possessed by the user who requests use of the mobile body 10. The device ID is received. The identification information receiving unit 320 notifies the determination unit 330 of the received body number and element ID.

  The determination unit 330 compares the vehicle body number and user ID stored in the mobile object database 310 with the vehicle body number and element ID received by the identification information reception unit 320 to determine whether or not to unlock. . For example, the determination unit 330 compares the user ID associated with the vehicle body number that matches the vehicle body number received by the identification information receiving unit 320 with the element ID received by the identification information receiving unit 320, and When both are associated with reference to the database 312 or the like, it may be determined that unlocking is performed. When the use user ID stored in the mobile database 310 is an element ID associated with the user, the determination unit 330 opens when the use user ID and the element ID match. You may decide to lock it.

  Information stored in the mobile database 310 is updated using information transmitted from the user terminal 140. Therefore, according to the present embodiment, the security is improved by comparing the information transmitted from the key device 130 and the information transmitted from the user terminal 140 and controlling the unlocking operation of the key device 130. be able to. For example, unauthorized use of a membership card by a third party can be prevented.

  If the determination unit 330 determines that unlocking is to be performed, the determination unit 330 may access the moving object database 310 and update the usage status of the vehicle body number of the moving object 10 to “in use”. If the determination unit 330 determines to unlock, the determination unit 330 may notify the key device 130 of an unlocking permission signal for permitting unlocking. When the determination unit 330 determines to unlock, the determination unit 330 may notify the key device 130 of the user ID associated with the vehicle body number of the moving body 10 to which the key device 130 is attached.

  In the present embodiment, the determination unit 330 receives a return request for the moving body 10 from the user terminal 140 via the request processing unit 340, and receives the vehicle body number and element from the moving body 10 via the identification information receiving unit 320. When the ID and the lock confirmation signal are received, the vehicle body number and user ID stored in the mobile body database 310 are compared with the received body number and element ID, and the use of the mobile body 10 is stopped. You may decide whether or not.

  For example, the determination unit 330 compares the user ID associated with the vehicle body number that matches the vehicle body number received by the identification information receiving unit 320 with the element ID received by the identification information receiving unit 320, and When both are associated with reference to the database 312 or the like, it may be determined that the use of the mobile object 10 has been stopped. When the use user ID stored in the mobile database 310 is an element ID associated with the user, the determination unit 330 moves when the use user ID and the element ID match. It may be determined that the use of the body 10 has been stopped.

  The return request may be an example of a request for stopping the use of the mobile object 10. In another embodiment, the determination unit 330 may receive a request for stopping the use of the moving body 10 from the moving body 10.

  When determining that the use of the mobile object 10 has been stopped, the determination unit 330 may access the mobile object database 310 and update the use status of the vehicle body number of the mobile object 10 to “available”. When determining that the use of the mobile object 10 has been stopped, the determination unit 330 notifies the key device 130 of an erase request for requesting the user ID associated with the vehicle body number of the mobile object 10 to be deleted. It's okay.

  The request processing unit 340 processes the request transmitted from the user terminal 140. The request processing unit 340 may transmit a screen of a website that provides a service to the user terminal 140. Request processing unit 340 may process the request to create or update mobile database 310, user database 312, or relay device database 314. The request processing unit 340 may be an example of a moving body information generation unit.

  For example, the request processing unit 340 updates the mobile database 310 according to the following procedure. The request processing unit 340 receives from the user terminal 140 a use request for the mobile unit 10, a terminal ID, and a vehicle body number of the mobile unit 10 that the user requests to use, and uses the process (referred to as a lending process). There is.) Next, the request processing unit 340 refers to the user database 312 and extracts an element ID associated with the received terminal ID and stored in the user database 312 as a use user ID. Thereafter, the request processing unit 340 associates the extracted element ID with the received vehicle body number and stores them in the mobile object database 310.

  In the return process, for example, the mobile database 310 is updated by the following procedure. The request processing unit 340 receives a return request for the mobile object 10, a terminal ID, and the vehicle body number of the mobile object 10 for which the user is requesting a return from the user terminal 140, and starts the return process. Next, the request processing unit 340 refers to the user database 312 and extracts the element ID stored in the user database 312 in association with the received terminal ID. Similarly, the request processing unit 340 refers to the mobile body database 310 and extracts a use user ID stored in the mobile body database 310 in association with the received body number.

  The request processing unit 340 compares the extracted element ID with the extracted used user ID, and deletes the used user ID in the mobile database 310 when they are associated with each other. The request processing unit 340 may store the element ID extracted in the return process in another database in association with the received body number as a target of the return process.

  The relay unit 350 may relay communication between the key device 130 and the identification information receiving unit 320. The relay unit 350 requests the key devices 130 existing in the communication area to transmit the vehicle body number of the moving body 10 to which each key device 130 is attached every time the set time has elapsed. Good. Thereby, the server 110 can confirm the current position of the mobile object 10.

  In this case, the key device 130 may turn off the power or shift to the power saving mode between the transmission of the vehicle body number and the next transmission. Thereby, the current position of the moving body 10 can be confirmed while suppressing the power consumption of the key device 130. The relay unit 350 may change the setting so that the transmission interval is longer when the remaining battery capacity of the key device 130 is smaller than a predetermined value.

  The registration processing unit 360 functions as an interface with the user in the member registration process. The registration processing unit 360 may acquire the element ID from the storage element 202 or the storage element 204 during execution of the member registration process. The registration processing unit 360 may cause the user terminal 140 to access a Web site that provides a service and transmit the acquired element ID to the request processing unit 340 as requested user identification information.

  For example, when the user terminal 140 includes the storage element 204, the registration processing unit 360 acquires an element ID from the storage element 204. Next, the registration processing unit 360 transmits, to the user terminal 140, a signal that causes the user terminal 140 to access the website together with the acquired element ID. The user terminal 140 that has received the signal establishes communication with the request processing unit 340 and accesses the Web site. At this time, the user terminal 140 transmits the element ID received from the registration processing unit 360 and the terminal ID of the user terminal 140 to the request processing unit 340. Thereby, the request processing unit 340 can store the element ID and the terminal ID of the user terminal 140 in the user database 312 in association with each other.

  Thereafter, the user is requested to input personal information via the user terminal 140. Accordingly, the request processing unit 340 can store the element ID and the user's personal information in the user database 312 in association with each other. Thereafter, a membership number assigned for each user may be issued, and the registration process may be terminated.

  On the other hand, when the user terminal 140 does not have the storage element 204, the registration processing unit 360 acquires an element ID from the storage element 202. Next, the registration processing unit 360 displays the QR code in which the acquired element ID and the URL of the Web site are embedded. The user terminal 140 reads the QR code presented from the registration processing unit 360, establishes communication with the request processing unit 340, and accesses the website. At this time, the user terminal 140 transmits the element ID received from the registration processing unit 360 and the terminal ID of the user terminal 140 to the request processing unit 340. Thereby, the request processing unit 340 can store the element ID and the terminal ID of the user terminal 140 in the user database 312 in association with each other.

  Thereafter, the user is requested to input personal information via the user terminal 140. Accordingly, the request processing unit 340 can store the element ID and the user's personal information in the user database 312 in association with each other. Thereafter, a membership number assigned for each user may be issued, and the registration process may be terminated.

  FIG. 4 schematically shows an example of the data structure 400 of the mobile database 310. The data structure 400 stores at least a vehicle body number 402 and a use user ID 404 in association with each other. The user ID 404 used may be the user's membership number, the element ID of the storage element possessed by the user, the terminal ID of the user terminal 140, or the user's name or email address. May be. However, the use user ID 404 is preferably an element ID of a storage element possessed by the user.

  The data structure 400 may further store at least one of the relay device ID 406 and the usage status 408 in association with the vehicle body number 402. When the usage status 408 is “usable” or “unusable”, there is no user who can use the mobile object 10, so the usage user ID 404 may be blank. If the relay device ID 406 is blank or “none” even though the usage status 408 is “in use”, the relay device 120, the key device 130, etc. are out of order, or the mobile device 10 indicates that it exists outside the communication area.

  Note that the information storage method in the data structure 400 is not limited to the above method. The use user ID 404 may store not only identification information for identifying a user who can use the mobile object 10 at present, but also identification information for identifying a user who can use the mobile object 10 at the end.

  In this case, if the use status 408 is “usable”, the determination unit 330 stores the information stored in the use user ID 404 as identification information for identifying the user who was able to use the mobile object 10 last. Judge. If the usage status 408 is “in use”, it is determined that the information stored in the usage user ID 404 is identification information for identifying a user who can currently use the mobile object 10. Thereby, when a user stops using the moving body 10, it is not necessary to update data, and the frequency of data update can be reduced.

  In addition, the data structure of the mobile database 310 is not limited to this. Instead of storing the body number 402 and the relay device ID 406 in association with each other, the device type indicating the key device, the relay device, etc., and the identification information of each device may be stored in association with each other. For each of the plurality of moving bodies 10, the vehicle body number assigned to the moving body 10 and the communication device ID of the key device 130 attached to the moving body 10 may be stored in association with each other.

  FIG. 5 schematically shows an example of the data structure 500 of the user database 312. The data structure 500 stores at least an element ID 504 and a terminal ID 506 in association with each other. The data structure 500 may further store at least one of a member number 502 and personal information 508 in association with the element ID 504 and the terminal ID 506. The personal information 508 may include a user's name 582, a mail address 584, a credit number 586, and the like. The data structure 500 may store the vehicle body number 510 of the moving body 10 currently used by the user corresponding to the element ID 504 and the terminal ID 506 in association with the element ID 504 and the terminal ID 506.

  FIG. 6 schematically illustrates an example of an information processing method in the management system 100. In FIG. 6, step numbers are omitted as shown in S602. FIG. 6 schematically shows an example of a flow of lending processing of the mobile object 10 in the management system 100. In the present embodiment, first, in S602, the user terminal 140 establishes communication with the request processing unit 340 of the server 110 and accesses a Web site that provides a service.

  In step S <b> 604, the request processing unit 340 transmits the website menu screen to the user terminal 140. The menu screen may be a screen for allowing the user to select a desired process, or may be a screen that presents a process according to the usage status of the user.

  For example, the request processing unit 340 refers to the mobile database 310 and confirms whether or not the use user ID 404 corresponding to the terminal ID of the user terminal 140 is included in the use user ID 404. When the user ID corresponding to the terminal ID of the user terminal 140 is included and the usage status 408 is “in use”, this indicates that the user is already using the mobile object 10. Therefore, the request processing unit 340 transmits a screen for starting execution of the return process to the user terminal 140. On the other hand, in cases other than the above, the request processing unit 340 transmits a screen for starting execution of the lending process to the user terminal 140.

  When the user requests use of the mobile object 10, in S <b> 606, the user inputs information related to the bicycle parking lot where the mobile object 10 is desired to be rented to the user terminal 140. Based on the user input, the user terminal 140 transmits a use request for causing the server 110 to start executing the lending process of the mobile object 10 to the request processing unit 340 of the server 110 together with the information related to the bicycle parking lot.

  In S <b> 608, the request processing unit 340 refers to the mobile object database 310 and is associated with the relay device ID 406 corresponding to the bicycle parking lot selected by the user, and the vehicle body number of the mobile object 10 whose usage status 408 is “available”. 402 is extracted. The request processing unit 340 transmits the extracted body number 402 to the user terminal 140. In S608, if the request processing unit 340 refers to the mobile object database 310 and determines that the user has already used the mobile object 10, the request processing part 340 stops the lending process. Then, an error screen may be transmitted to the user terminal 140.

  In S <b> 610, the user selects the vehicle body number of the mobile body 10 that requires use from the vehicle body numbers 402 displayed on the user terminal 140. The user transmits the selected body number to the request processing unit 340. In step S612, the request processing unit 340 accesses the mobile object database 310, and changes the usage status 408 associated with the vehicle body number 402 of the mobile object 10 selected by the user from “available” to “in use”. change.

  In S620, the request processing unit 340 requests the user terminal 140 to transmit the element ID from the key device 130. In S <b> 622, the user terminal 140 that has received the request from the request processing unit 340 requests the user to input the element ID stored in the storage element 202 or the storage element 204 to the key device 130.

  For example, when the storage element 202 or the storage element 204 and the identification information acquisition unit 230 of the key device 130 communicate with each other by short-range wireless communication such as RFID, infrared communication, and specific low power wireless, a request from the user terminal 140 is received. The user brings the membership card 22 or the user terminal 140 close to the key device 130. Thereby, in S630, the key device 130 acquires the element ID stored in the storage element 202 or the storage element 204.

  In S632, the key device 130 transmits the element ID acquired by the identification information acquisition unit 230 and the vehicle body number of the moving body 10 to which the key device 130 is attached to the identification information reception unit 320. At this time, the key device 130 may transmit a use request signal for requesting use of the moving body 10 identified by the vehicle body number to the identification information receiving unit 320. The vehicle body number of the moving body 10 to which the key device 130 is attached is stored in the identification information storage unit 240, for example.

  In S634, the determination unit 330 receives the vehicle body number and the element ID received by the identification information receiving unit 320. The determination unit 330 may be configured to receive a use request signal from the identification information receiving unit 320 and start processing. The determination unit 330 compares the vehicle body number and user ID stored in the mobile object database 310 with the vehicle body number and element ID received by the identification information reception unit 320 to determine whether or not to unlock. . If the determination unit 330 determines to unlock, the determination unit 330 transmits an unlock permission signal to the key device 130. At this time, the determination unit 330 may notify the key device 130 of the use user ID associated with the vehicle body number of the moving body 10 to which the key device 130 is attached.

  In S636, the key device 130 may store the used user ID received from the determination unit 330 in the identification information storage unit 240. In S638, the determination unit 250 notifies the locking unit 210 of an unlocking signal. The locking unit 210 performs the unlocking operation to release the use restriction of the moving body 10. The locking unit 210 confirms unlocking and transmits an unlock confirmation signal to the server 110.

  In S650, when the request processing unit 340 receives the unlock confirmation signal, the request processing unit 340 starts charging processing. In S660, the user terminal 140 requests the request processing unit 340 to transmit the processing result. In S662, the request processing unit 340 transmits a completion notification screen indicating that the lending process is completed to the user terminal 140. In addition, the request processing unit 340 may transmit a mail for guiding the start of use to the user terminal 140. The request processing unit 340 ends the lending process when the completion notification screen and the transmission of the mail are finished.

  FIG. 7 schematically shows an example of an information processing method in the management system 100. FIG. 7 schematically shows an example of a flow of return processing of the moving body 10 in the management system 100. In this embodiment, first, in step S <b> 702, the user performs a locking operation of the key device 130, and then uses the user terminal 140 to access a website that provides a service.

  In step S <b> 704, the request processing unit 340 transmits a website return screen to the user terminal 140. When the user requests to return the mobile object 10, in S <b> 706, the user transmits a return request for causing the server 110 to start executing the return process of the mobile object 10 to the request processing unit 340 from the user terminal 140. .

  In S720, the request processing unit 340 requests the user terminal 140 to transmit an element ID from the key device. In S <b> 722, the user terminal 140 that has received the request from the request processing unit 340 requests the user to input the element ID stored in the storage element 202 or the storage element 204 to the key device 130.

  For example, when the storage element 202 or the storage element 204 and the identification information acquisition unit 230 of the key device 130 communicate with each other by short-range wireless communication such as RFID, infrared communication, and specific low power wireless, a request from the user terminal 140 is received. The user brings the membership card 22 or the user terminal 140 close to the key device 130. Thereby, in S730, the key device 130 acquires the element ID stored in the storage element 202 or the storage element 204.

  In S732, the key device 130 transmits the element ID acquired by the identification information acquisition unit 230, the vehicle body number of the moving body 10 to which the key device 130 is attached, and the lock confirmation signal to the identification information reception unit 320. To do. At this time, the key device 130 may transmit a return request signal requesting the return of the moving body 10 identified by the vehicle body number to the identification information receiving unit 320. The vehicle body number of the moving body 10 to which the key device 130 is attached is stored in the identification information storage unit 240, for example. The return request signal may be an example of a request for stopping the use of the moving body 10.

  In S <b> 734, the determination unit 330 receives the vehicle body number, the element ID, and the lock confirmation signal received by the identification information receiving unit 320. The determination unit 330 may be configured to receive a return request signal from the identification information reception unit 320 and start processing. The determination unit 330 compares the vehicle body number and user ID stored in the mobile body database 310 with the received vehicle body number and element ID to determine whether or not the use of the mobile body 10 has been stopped. When determining that the use of the mobile object 10 has been stopped, the determination unit 330 transmits an erasure request for requesting the user device ID associated with the vehicle body number of the mobile object 10 to be erased to the key device 130. .

  In step S <b> 736, the key device 130 deletes the used user ID stored in the identification information storage unit 240. In S738, the key device 130 transmits to the request processing unit 340 an erasure confirmation signal indicating that the erasure of the used user ID has been completed.

  In S750, when the request processing unit 340 receives the erasure confirmation signal, the request processing unit 340 stops the accounting process. In S752, a usage fee settlement process is executed. In S760, the user terminal 140 requests the request processing unit 340 to transmit the processing result. In S <b> 762, the request processing unit 340 transmits a completion notification screen indicating that the return processing is completed to the user terminal 140. Further, the request processing unit 340 may transmit an email notifying the usage details to the user terminal 140. The request processing unit 340 ends the return process when the completion notification screen and the transmission of the mail are finished.

  FIG. 8 schematically shows an example of the system configuration of the management system 800 together with the membership card 22, the communication line 102, the key device 130, and the user terminal 140. The management system 800 includes a server 810 and a relay device 820.

  In the present embodiment, the server 810 includes a mobile database 310, a user database 312, a relay device database 314, and a request processing unit 340. The relay device 820 includes an identification information receiving unit 320, a determination unit 330, a relay unit 350, a registration processing unit 360, and a processing target database 816.

  The management system 800 is different from the management system 100 in that the identification information receiving unit 320 and the determination unit 330 are arranged not in the server 810 but in the relay device 820. Further, the relay device 820 is different from the management system 100 in that the relay device 820 includes a processing target database 816. Further, part of the processing in the determination unit 330 and the request processing unit 340 is different from the management system 100.

  Hereinafter, the management system 800 will be described focusing on differences from the management system 100. If the configuration may be the same as that of the management system 100, the description may be omitted.

  The processing target database 816 stores information on the mobile object 10 that is a target of the lending process or the return process. The processing target database 816 may be an example of a moving body identification information storage unit. In the present embodiment, the processing target database 816 stores the vehicle body number of the mobile object that is the object of the lending process or the return process and the user ID of the mobile object in association with each other. The processing target database 816 may be updated when the request processing unit 340 of the server 810 processes a request from the user terminal 140.

  In the management system 100, the determination unit 330 compares the vehicle body number and user ID stored in the mobile object database 310 with the vehicle body number and element ID received by the identification information reception unit 320 to determine whether to unlock. Judged whether or not. On the other hand, in this embodiment, the determination unit 330 compares the vehicle body number and user ID stored in the processing target database 816 with the vehicle body number and element ID received by the identification information receiving unit 320. Determine whether to unlock.

  In the management system 100, the determination unit 330 receives a return request for the moving body 10 from the user terminal 140 via the request processing unit 340, and receives a vehicle body number and an element from the moving body 10 via the identification information receiving unit 320. When the ID and the lock confirmation signal were received, it was determined whether or not the use of the moving body 10 was stopped. On the other hand, in this embodiment, the determination unit 330 receives the return request signal, the vehicle body number, the element ID, and the lock confirmation signal from the key device 130 via the identification information reception unit 320. The vehicle body number and user ID stored in 816 are compared with the received vehicle body number and element ID to determine whether or not the use of the moving body 10 has been stopped.

  In the management system 100, the request processing unit 340 updates the mobile database 310 in the lending process and the return process. In contrast, in the present embodiment, the request processing unit 340 updates the processing target database 816 in the lending process and the return process. At this time, the mobile database 310 may be updated in the same manner as in the management system 100.

  For example, in the lending process, the processing target database 816 is updated by the following procedure. The request processing unit 340 receives, from the user terminal 140, a use request for the mobile object 10, a terminal ID, and a vehicle body number of the mobile object 10 that the user requests to use, and starts a lending process. Next, the request processing unit 340 refers to the user database 312 and extracts an element ID associated with the received terminal ID and stored in the user database 312 as a use user ID. Thereafter, the request processing unit 340 associates the extracted element ID with the received vehicle body number and stores them in the processing target database 816.

  In the return process, for example, the mobile database 310 is updated by the following procedure. The request processing unit 340 receives a return request for the mobile object 10, a terminal ID, and the vehicle body number of the mobile object 10 for which the user is requesting a return from the user terminal 140, and starts the return process. Next, the request processing unit 340 refers to the user database 312 and extracts an element ID associated with the received terminal ID and stored in the user database 312 as a use user ID. Thereafter, the request processing unit 340 associates the extracted element ID with the received vehicle body number and stores them in the processing target database 816.

  As described above, in the present embodiment, the determination unit 330 can determine whether or not to unlock without communicating with the server 810 via the communication line 102. Thereby, the communication time between the relay device 820 and the key device 130 during execution of the lending process and the return process is shorter than the communication time between the relay device 120 and the key device 130. As a result, the power consumption of the key device 130 can be reduced.

  FIG. 9 schematically shows an example of the data structure 900 of the processing target database 816. The data structure 900 stores at least the vehicle body number ID 902 of the mobile object 10 to be processed and the user ID 904 of the mobile object 10 in association with each other. The data structure 900 may store the vehicle body number ID 902 of the moving object 10 to be processed and the request type 906 indicating the user request in the process in association with each other.

  The user ID 404 may be a user's membership number, an element ID of a storage element possessed by the user, a terminal ID of the user terminal 140, a user's name or email address, Also good. However, the use user ID 404 is preferably an element ID of a storage element possessed by the user.

  FIG. 10 schematically shows an example of an information processing method in the management system 800. FIG. 10 schematically shows an example of a flow of lending processing of the mobile object 10 in the management system 800. This embodiment is different from the lending process flow of the management system 100 in FIG. 6 in that S1014 and S1016 are performed before S632. This embodiment is different from the lending process flow of the management system 100 in FIG. 6 in that S632 and S634 are performed between the key device 130 and the relay device 820. Furthermore, this embodiment is different from the lending process flow of the management system 100 of FIG. 6 in that S1040 is performed after S638.

  Hereinafter, the lending process in the management system 800 will be described focusing on differences from the lending process in the management system 100. The description may be omitted when the management system 100 may have the same configuration as the lending process.

  In the present embodiment, S1014 and S1016 are performed before S632. In step S <b> 1014, the request processing unit 340 updates the processing target database 816. For example, the request processing unit 340 refers to the user database 312 and extracts the element ID associated with the terminal ID received from the user terminal 140 and stored in the user database 312 as the use user ID. Thereafter, the request processing unit 340 associates the extracted element ID with the received body number, and transmits the associated element ID to the processing target database 816 of the relay device 820.

  The request processing unit 340 may transmit the element ID and the vehicle body number to all the relay devices 820 included in the management system 800. If the request processing unit 340 receives position information such as GPS information from the user terminal 140, the request processing unit 340 may transmit the element ID and the vehicle body number to the relay device 820 existing around the user terminal 140. Good.

  In step S <b> 1016, the processing target database 816 that has received the element ID and the vehicle body number transmits a receipt confirmation signal to the request processing unit 340. The processing target database 816 stores the element ID received from the request processing unit 340 and the vehicle body number in association with each other.

  In the present embodiment, S632 and S634 are performed between the key device 130 and the relay device 820. In S632, the key device 130 uses the element ID acquired by the identification information acquisition unit 230, the vehicle body number of the mobile body 10 to which the key device 130 is attached, and the use of the mobile body 10 identified by the vehicle body number. Is transmitted to the identification information receiving unit 320.

  In S634, the determination unit 330 receives the vehicle body number and the element ID received by the identification information receiving unit 320. The determination unit 330 compares the vehicle body number and user ID stored in the processing target database 816 with the vehicle body number and element ID received by the identification information reception unit 320 to determine whether or not to unlock. . If the determination unit 330 determines to unlock, the determination unit 330 transmits an unlock permission signal to the key device 130. At this time, the determination unit 330 may notify the key device 130 of the use user ID associated with the vehicle body number of the moving body 10 to which the key device 130 is attached.

  The determination unit 330 may start determining whether or not to unlock in response to the identification information reception unit 320 receiving the use request signal. The determination unit 330 may start determining whether or not to unlock based on information stored in the request type 906 of the processing target database 816.

  In the present embodiment, S1040 is performed after S638. In S1040, the request processing unit 340 completes the unlocking process with at least one of the vehicle body number and the user ID for which the unlocking process has been completed for the relay device 820 that transmitted the element ID and the vehicle body number in S1014. And a completion notification indicating that. As a result, the processing target database 816 of the relay device 820 can erase information related to the mobile object 10 for which the unlocking process has been completed.

  In this embodiment, since S1014 and S1016 are performed before S632, when the key device 130 acquires the element ID from the user, the body number and the element ID to be processed are stored in the processing target database 816. Stored. Thereby, the execution time of S632 and S634 can be shortened.

  FIG. 11 schematically shows an example of an information processing method in the management system 800. FIG. 11 schematically shows an example of a flow of return processing of the moving object 10 in the management system 800. The present embodiment is different from the return processing flow of the management system 100 of FIG. 7 in that S1114 and S1116 are performed before S732. The present embodiment is different from the return processing flow of the management system 100 in FIG. 7 in that S732 and S734 are performed between the key device 130 and the relay device 820. Furthermore, this embodiment is different from the return processing flow of the management system 100 of FIG. 7 in that S1140 is implemented after S738.

  Hereinafter, the return process in the management system 800 will be described focusing on differences from the return process in the management system 100. The description may be omitted when the management system 100 may have the same configuration as the return process.

  In the present embodiment, S1114 and S1116 are performed before S732. In S <b> 1114, the request processing unit 340 updates the processing target database 816. For example, the request processing unit 340 refers to the user database 312 and extracts an element ID associated with the received terminal ID and stored in the user database 312 as a use user ID. Thereafter, the request processing unit 340 associates the extracted element ID with the received body number, and transmits the associated element ID to the processing target database 816 of the relay device 820.

  The request processing unit 340 may transmit the element ID and the vehicle body number to all the relay devices 820 included in the management system 800. If the request processing unit 340 receives position information such as GPS information from the user terminal 140, the request processing unit 340 may transmit the element ID and the vehicle body number to the relay device 820 existing around the user terminal 140. Good.

  In S <b> 1116, the processing target database 816 that has received the element ID and the vehicle body number transmits a receipt confirmation signal to the request processing unit 340. The processing target database 816 stores the element ID received from the request processing unit 340 and the vehicle body number in association with each other.

  In the present embodiment, S732 and S734 are performed between the key device 130 and the relay device 820. In S732, the key device 130 is identified by the element ID acquired by the identification information acquisition unit 230, the vehicle body number of the moving body 10 to which the key device 130 is attached, the locking confirmation signal, and the vehicle body number. A return request signal for requesting the return of the moving body 10 is transmitted to the identification information receiving unit 320.

  In S <b> 734, the determination unit 330 receives the vehicle body number, the element ID, and the lock confirmation signal received by the identification information receiving unit 320. The determination unit 330 compares the vehicle body number and user ID stored in the processing target database 816 with the received vehicle body number and element ID to determine whether or not the use of the moving body 10 has been stopped. When determining that the use of the mobile object 10 has been stopped, the determination unit 330 transmits an erasure request for requesting the user device ID associated with the vehicle body number of the mobile object 10 to be erased to the key device 130. .

  The determination unit 330 may start determining whether or not the use of the mobile object 10 has been stopped in response to the identification information reception unit 320 receiving the return request signal. The determination unit 330 may start determining whether or not the use of the mobile object 10 has been stopped based on information stored in the request type 906 of the processing target database 816.

  In the present embodiment, S1140 is performed after S738. In S1140, the request processing unit 340 confirms that the erasure process has been completed for at least one of the body number and the user ID used for the relay device 820 that transmitted the element ID and the vehicle body number in S1114. A completion notification may be sent. As a result, the processing target database 816 of the relay device 820 can erase the information related to the mobile object 10 for which the erasure process has been completed.

  In this embodiment, since S1114 and S1116 are performed before S732, when the key device 130 acquires the element ID from the user, the body number and the element ID to be processed are stored in the processing target database 816. Stored. Thereby, the execution time of S732 and S734 can be shortened.

  In the above embodiment, the case where a vehicle body number was used as mobile body identification information was demonstrated. However, other moving body identification information for identifying the moving body 10 may be used instead of the vehicle body number. Moreover, the case where element ID was used as request | requirement user identification information was demonstrated. However, instead of the element ID, other requested user identification information for identifying a user who requests use of the mobile object 10 may be used.

  In addition, according to the above description, this specification describes a method in which a server provides a service to a user terminal via a communication line, and (1) a movement for identifying a moving body from a moving body. Receiving body identification information and requested user identification information for identifying a user who requests use of the mobile body via a communication line; (2) identified by the mobile body identification information and the mobile body identification information; Using the moving body information associated with the used user identification information for identifying the user who can use the moving body, the moving body identification information and the used user identification information associated with each other in the moving body information, and the received movement It is apparent that a method is described that includes comparing the body identification information and the requested user identification information to determine whether to unlock the mobile body.

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiment. It is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

  The order of execution of each process such as operations, procedures, steps, and stages in the apparatus, system, program, and method shown in the claims, the description, and the drawings is particularly “before” or “prior to”. It should be noted that the output can be realized in any order unless the output of the previous process is used in the subsequent process. Regarding the operation flow in the claims, the description, and the drawings, even if it is described using “first”, “next”, etc. for convenience, it means that it is essential to carry out in this order. It is not a thing.

  DESCRIPTION OF SYMBOLS 10 Mobile body, 12 Bicycle parking lot, 14 Bicycle parking lot, 22 Member card, 100 Management system, 102 Communication line, 110 Server, 120 Relay device, 130 Key device, 140 User terminal, 202 Storage element, 204 Storage element, 210 Locking part, 220 Locking control unit, 230 identification information acquisition unit, 240 identification information storage unit, 250 determination unit, 310 mobile database, 312 user database, 314 relay device database, 320 identification information reception unit, 330 determination unit, 340 request processing unit , 350 relay unit, 360 registration processing unit, 400 data structure, 402 body number, 404 user ID, 406 relay device ID, 408 usage status, 500 data structure, 502 member number, 50 Element ID, 506 Terminal ID, 508 Personal information, 510 Body number, 582 Name, 584 Email address, 586 Credit number, 800 Management system, 810 Server, 816 Target database, 820 Relay device, 900 Data structure, 902 Body number ID 904 User ID used, 906 Request type

Claims (11)

Via a communication line, mobile device identification information for identifying the mobile body and requested user identification information for identifying a user who requests use of the mobile body from a locking device attached to the mobile body and locking the mobile body. An identification information receiving unit that receives the
A mobile body information storage unit that stores the mobile body identification information in association with user identification information that identifies a user who can use the mobile body identified by the mobile body identification information;
The mobile object identification information and the user identification information stored in the mobile object information storage unit are compared with the mobile object identification information and the requested user identification information received by the identification information receiver, A determination unit for determining whether or not to lock;
Comprising
Management system. When the determination unit determines to unlock the mobile body, the determination unit notifies the locking device of the mobile body of the user identification information used associated with the mobile body identification information of the mobile body. ,
The management system according to claim 1. A user information storage unit for storing the requested user identification information and terminal identification information for identifying a terminal possessed by the user identified by the requested user identification information;
The terminal identification information and the mobile body identification information of the mobile body that the user requests to use are received from the terminal, and stored in the user information storage unit in association with the received terminal identification information. A mobile body information generating unit that associates the requested user identification information with the received mobile body identification information and stores it in the mobile body information storage unit;
Further comprising
The management system according to claim 1 or 2. The determination unit
A request for stopping the use of the mobile body is received from the terminal or the mobile body, and the identification information receiving unit receives the mobile body identification information, the requested user identification information, and a lock confirmation signal from the mobile body. Is received,
The mobile body information storage unit stores the mobile body identification information and the use user identification information, and the received mobile body identification information and the requested user identification information are compared, and the use of the mobile body is stopped. To determine whether or not
The management system according to claim 3. When the determination unit determines that the use of the mobile object has been stopped, the determination unit determines whether the user identification information associated with the mobile object identification information of the mobile object is associated with the locking device of the mobile object. Notify erase request requesting erase,
The management system according to claim 4. The mobile body information generation unit
From the terminal, the request for stopping the use of the mobile body, the terminal identification information and the mobile body identification information of the mobile body that the user requests to stop using,
The requested user identification information associated with the received terminal identification information and stored in the user information storage unit is associated with the received mobile object identification information and stored in the mobile object information storage unit ,
The management system according to claim 4 or 5. A relay unit that relays communication between the locking device and the identification information receiving unit;
The mobile body information storage unit further stores the mobile body identification information of the mobile body in association with relay section identification information for identifying the relay section.
The management system according to any one of claims 1 to 6. A method in which a server provides a service to a user's terminal via a communication line. A mobile unit identification information for identifying the mobile unit and a request for identifying a user who requests use of the mobile unit from a mobile unit Receiving user identification information via a communication line;
Corresponding in the mobile body information using mobile body information in which the mobile body identification information and use user identification information for identifying a user who can use the mobile body identified by the mobile body identification information are associated with each other. Comparing the attached mobile unit identification information and the user identification information used with the received mobile unit identification information and the requested user identification information, and determining whether to unlock,
Having a method. A locking device attached to a moving body and locking the moving body,
An identification information acquisition unit for acquiring requested user identification information for identifying a user who requests use of the mobile body from a storage element possessed by the user;
An identification information storage unit that receives use user identification information for identifying a user who can use the mobile object from the management system, and stores the received user identification information;
A determination unit that determines whether or not to unlock by comparing the use user identification information stored in the identification information storage unit with the requested user identification information acquired by the identification information acquisition unit;
Comprising
Locking device. The identification information storage unit erases the use user identification information when receiving a deletion request for erasing the use user identification information from the management system.
The locking device according to claim 9.   A moving body comprising the locking device according to claim 9.