Management system

Abstract

To provide a management system which further enhances convenience while preventing steal of a battery.SOLUTION: A management system 10 according to the present invention manages a battery 14 detachably mounted on equipment 16. The battery has a battery storage unit 80 for storing an equipment ID unique to the equipment, and a control circuit 56. The control circuit supplies electricity to the battery if it is determined that an authentication ID input upon use and the equipment ID match with each other, and, on the other hand, stops supply of electricity if it is determined that the authentication ID input upon use and the equipment ID do not match with each other. The management system has a battery station rental control unit and a management server both functioning as a management unit for storing the equipment ID in the battery storage unit when obtaining a user ID.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to a management system for managing a battery that is detachably mounted in a device. [Background technology]

[0002] In devices such as work machines and vehicles that are equipped with and run on removable batteries, there is a possibility that the battery may be stolen by another person when the user temporarily leaves the device. For this reason, a technology has been proposed that prevents unauthorized use of the battery by performing authentication when the battery (power supply device) is mounted on the carrier device (device), such as the authentication system disclosed in JP2019-187231A.

[0003] Specifically, the battery disclosed in JP 2019-187231 A has multiple reference carrier identifiers, and in authentication when mounted, acquires a unique carrier identifier from the device and determines whether the reference carrier identifier matches the unique carrier identifier. The battery then allows power supply to the device if authentication is successful, but stops power supply to the device if authentication is not successful. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-187231 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in a system that performs authentication between a battery and a device, such as that disclosed in JP 2019-187231 A, the identification information stored in the battery cannot be changed (registered or deleted) by the user. For example, in a sharing system in which a battery is lent to a user or shared by multiple users, the system is configured so that only the business operator can register and delete the identification information for authentication.

[0006] However, such a configuration cannot immediately respond to changes in circumstances (such as when the device is no longer in use, or when the battery is reused for another device), resulting in inconveniences such as reduced convenience for users and increased burden on businesses that set identification information.

[0007] The present invention has been made in consideration of the above-mentioned circumstances, and has an object to provide a management system that can further increase convenience while suppressing battery theft. [Means for solving the problem]

[0008] An aspect of the present disclosure is a management system that manages a battery that is removably mounted on an apparatus and can supply power to the apparatus, the battery having a battery-side memory unit that stores unique apparatus identification information of the apparatus, and a control unit that, when attached to the apparatus, supplies power from the battery when it is determined that the in-use authentication identification information held by the apparatus matches the apparatus identification information, and stops the supply of power from the battery when it is determined that the in-use authentication identification information and the apparatus identification information do not match, and a management unit that, when user identification information for identifying a user who owns the battery is obtained, stores the apparatus identification information in the battery-side memory unit or deletes it from the battery-side memory unit. Effect of the Invention

[0009] The present disclosure makes it possible to further increase convenience while preventing battery theft. [Brief description of the drawings]

[0010] [Figure 1] 1 is an explanatory diagram illustrating an overall configuration of a management system according to an embodiment of the present invention; [Diagram 2] FIG. 1 is a flow chart showing the procedure for using the sharing system. [Diagram 3] FIG. 2 is a perspective view showing a battery rented out in a sharing system. [Figure 4] FIG. 2 is an explanatory diagram showing a flow when signing a battery usage contract. [Diagram 5] 1 is a table illustrating a usage contract database. [Figure 6] 11 is a block diagram for explaining the operation of the battery station and the management server when acquiring user identification information. FIG. [Figure 7] 10 is a flowchart illustrating a process when a user borrows a battery. [Figure 8] FIG. 2 is a block diagram for explaining an operation when the battery is mounted on a device. [Figure 9] 4 is a flowchart showing a process flow when a battery is mounted. [Figure 10] 11 is a flowchart illustrating a process performed when a user finishes using a battery. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will now be described in detail with reference to preferred embodiments thereof and accompanying drawings.

[0012] A management system 10 according to an embodiment of the present invention is applied to a sharing system 12 in which a business lends (leases or rents) batteries 14 to multiple users U, as shown in Fig. 1. The user U who borrows the battery 14 in the sharing system 12 installs the battery 14 in a device 16 and uses the device 16 based on the power supply of the battery 14. Note that the "user U" in the sharing system 12 refers to both an individual and an organization of multiple people (a company, a group, etc.). Furthermore, the sharing system 12 is not limited to a form in which a business lends a battery 14 to a user U, and may be a form in which one or more batteries 14 are shared among multiple users U.

[0013] The battery 14 lent to the user U is a general-purpose detachable battery that can be detachably mounted on various devices 16. The device 16 of the user U may be owned by the user U, or may be rented separately from the battery 14. Examples of the device 16 include working machines (e.g., construction machines, heavy machinery, industrial equipment, and household equipment) and moving objects (e.g., four-wheeled vehicles, two-wheeled vehicles, electric bicycles, carts, and robots). FIG. 1 shows an electric excavator that operates by power supply from the battery 14 as a representative example of the device 16. The device 16 includes a driving source 18 such as a motor, electrical equipment 20 including a control device 20a, and the like, and operates when power is supplied from the mounted battery 14 to the driving source 18 or the electrical equipment 20. The device 16 may be configured to include a battery unit (not shown) for driving the electrical equipment 20 with low power when the battery 14 is not mounted.

[0014] Here, in order to facilitate understanding of the present invention, a procedure for using the sharing system 12 according to this embodiment will be described with reference to FIG.

[0015] In using the sharing system 12, the user U first makes a contract for the use of the battery 14 with the operator of the sharing system 12 (step S1). During the usage period according to the contract, the user U goes to an appropriate battery station 22 (see FIG. 1) and borrows the battery 14 (step S2).

[0016] The user U then installs the borrowed battery 14 in the device 16 and uses the device 16 (step S3). If the remaining power of the battery 14 becomes low during the usage period, the user U stores the battery 14 in the battery station 22 from which it was received or in a different battery station 22 from which it was received. In this way, the battery station 22 charges the stored battery 14. If the user U wishes to continue using the battery 14, he or she borrows a new charged battery 14 from the battery station 22.

[0017] When the user U finishes using the battery 14, the user U returns the battery 14 to the battery station 22 and further carries out a procedure for ending the use, thereby terminating the usage contract (step S4).

[0018] In order to carry out the above-mentioned usage procedure, the sharing system 12 is constructed by a system operator as a client-server type using a network 24 such as the Internet or an intranet, as shown in Fig. 1. The sharing system 12 includes an operator terminal 26, a management server 28, and the above-mentioned battery station 22, as components connected to the network 24. Alternatively, the battery 14 itself may have a wireless communication function that can be connected to the network 24, and may communicate with the management server 28 while the user U is using the battery 14 or while the battery 14 is waiting at the battery station 22.

[0019] The operator of the sharing system 12 has an operator facility 30 that the user U visits when signing a contract to use the battery 14. An operator terminal 26 operated by an operator's person in charge P is installed in the operator facility 30. For example, the operator terminal 26 is a computer (desktop computer, laptop computer) capable of communicating via the network 24. Note that the operator terminal 26 may be an information processing terminal such as a PDA, tablet, smartphone, mobile phone, or wearable computer. The operator may carry the operator terminal 26 around while doing business, and may not have the operator facility 30.

[0020] The business operator assigns user identification information (hereinafter referred to as user ID) to the user U who has signed a service contract. The user ID is information for individually identifying the user U who owns (including the concepts of "loaned" or "owned") the battery 14. The user ID is set by the user U or automatically assigned by the business operator, and is managed by the business operator terminal 26 and the management server 28 by being transmitted to the management server 28 via the business operator terminal 26. The business operator facility 30 also has an IC card 32 with an RF tag built in, and a writer 34 that is connected to the business operator terminal 26 and writes information into the IC card 32. The business operator issues the IC card 32, on which information including the user ID is stored, to the user U who has signed a service contract.

[0021] The battery station 22 is formed in a shelf shape with slots 36 arranged in a matrix, each capable of housing a plurality of batteries 14, and is installed, for example, outdoors of a business facility 30. When a user U or a business person P houses a battery 14, the battery station 22 functions as a charger that charges the battery 14, and also functions as an exchanger that exchanges the battery 14 for another battery 14. It is more preferable that the battery station 22 is installed in various locations around town. The battery station 22 may be temporarily installed, for example, at a location (work site) where work is performed using the device 16.

[0022] The battery station 22 has a computer (rental control unit 38) including one or more processors, memory, and input / output interfaces (not shown), and is configured to be able to communicate with the management server 28. In this sharing system 12, the rental control unit 38 and management server 28, which are configured to be able to communicate information with each other, correspond to a management unit 40 that manages user IDs and device identification information (described later).

[0023] Provided on the outside of the battery station 22 are a touch panel 42 or other operation unit that displays images under the control of the rental control unit 38 and recognizes image operations by the user U, and a reader 44 (input unit) that reads information from the IC card 32 of the user U. Furthermore, the slot 36 of the battery station 22 has a communication module (not shown) that communicates information with the accommodated battery 14, and a battery lock mechanism 46 that switches the battery 14 between a removal-permitted state and a removal-prohibited state.

[0024] The rental control unit 38 of the battery station 22 acquires information such as battery identification information (hereinafter referred to as battery ID) and the remaining battery charge of the battery 14 from the accommodated battery 14 via the communication module, and automatically transmits the acquired information to the management server 28. The rental control unit 38 also processes the operation of the touch panel 42 by the user U and the information of the IC card 32 acquired by the reader 44, and communicates information with the management server 28, thereby appropriately managing the battery 14 rented to the user U.

[0025] 3, the battery 14 lent to the user U is generally formed in a rectangular column shape, with a handle 50 at one end for the user U to grasp. The battery 14 also has a battery cell body 52 that actually stores and releases power, multiple terminals 54 that can input and output power, and a control circuit 56 that controls the charging and discharging of the battery 14.

[0026] The battery cell body 52 is configured to have an appropriate output voltage, battery capacity, etc. by connecting multiple battery cells (not shown), such as liquid batteries, all-solid-state batteries, etc. The multiple terminals 54 are provided, for example, on the opposite side (or the same side) as the handle 50, and contact terminals on the device side (not shown) when the battery 14 is mounted on the device 16, and contact terminals on the battery station side (not shown) when the battery 14 is accommodated in the battery station 22.

[0027] The control circuit 56 is configured in a computer including one or more processors, memories, and input / output interfaces (not shown). The control circuit 56 performs authentication when the battery 14 is installed in the device 16, and controls the discharge of the battery cell main body 52. ​​This configuration will be described in detail later.

[0028] The configuration of the sharing system 12 according to this embodiment will be described in more detail below in accordance with the usage procedure in Fig. 2. A user U who wishes to use the sharing system 12 goes to a business operator facility 30 and makes a usage contract for the battery 14 with the business operator (step S1). Before going to the business operator to make the usage contract, the user U prepares in advance device identification information (hereinafter referred to as device ID) as information on the device 16 equipped with the battery 14, as shown in Fig. 4.

[0029] The device ID is an identifier that is normally attached to the device 16 and is set to a different code even for the same model. For example, the device ID is set by a manufacturer when the device 16 is manufactured and is attached to an instruction manual or warranty card as information for identifying the device 16. The control device 20a of the device 16 stores the device ID in advance. The sharing system 12 may be configured such that a user terminal 60 (a portable information processing device such as a smartphone, laptop computer, PDA, tablet, etc.) owned by a user U and the device 16 can communicate with each other. In this case, as shown in FIG. 4, an application (not shown) of the user terminal 60 can be configured to automatically acquire the device ID from the device 16 by communicating with the device 16.

[0030] In a contract for the use of the battery 14, the user U who goes to the business operator facility 30 conveys the conditions of use of the battery 14 and the device ID to the person in charge P at the business operator facility 30 to make the contract. The conditions of use include the user U's personal information (e.g., name, address, telephone number, email address), start date and time of use, end date and time of use, number of uses, and location of use. The person in charge P inputs the conditions of use and the device ID into the business operator terminal 26, and also accesses the management server 28 via the business operator terminal 26 to set a user ID unique to the user U. Note that if the user ID has already been set by using the sharing system 12, the person in charge P reads out the user ID and inputs the conditions of use so as to be linked to the user ID.

[0031] The user ID, terms of use, and device ID input to the business operator terminal 26 are transmitted to the management server 28 and managed by the business operator terminal 26 and the management server 28. When using multiple devices 16 to utilize the battery 14, the user U prepares a device ID for each device 16. The business operator terminal 26 and the management server 28 manage the multiple input device IDs by linking them to the user ID.

[0032] The management server 28 has a usage contract database 62 (hereinafter referred to as the usage contract DB 62) in advance, and when a user ID, usage conditions, and one or more device IDs are transmitted from the business operator terminal 26, they are registered in the usage contract DB 62. As shown in Fig. 5, the usage contract DB 62 stores the user ID, personal information, usage start date and time, usage end date and time, number of uses, usage location, and one or more device IDs in a mutually linked state. The management server 28 monitors the loan status of the battery 14 to the user U who has signed the usage contract at a predetermined point in time by measuring the date and time and referring to the usage contract DB 62.

[0033] Returning to Fig. 4, the business operator issues the IC card 32 by writing the user ID and one or more device IDs stored in the business operator terminal 26 to the IC card 32 via the writer 34. Note that the sharing system 12 is not limited to storing the user ID and device ID in the IC card 32, and may be configured to store them in the user terminal 60 or the like. The user terminal 60 has a communication module capable of communicating with the reader 44 of the battery station 22, and transmits the user ID and the like to the rental control unit 38 when the user U brings the user terminal 60 close to the reader 44. The sharing system 12 may be configured to write only the user ID to the IC card 32.

[0034] When the usage contract is completed, the user U borrows the battery 14 from the battery station 22 for the usage period (step S2 in FIG. 2). At this time, as shown in FIG. 6, the rental control unit 38 of the battery station 22 and the management server 28 communicate information with each other while performing appropriate processing, thereby lending the battery 14 to the user U. The rental control unit 38 is formed with a rental processing unit 70, a charging control unit 72, and a return processing unit 74. Also, a user authentication unit 64, a battery monitoring unit 66, and a battery database 68 (hereinafter referred to as battery DB 68) are built within the management server 28.

[0035] The battery DB 68 stores information on a plurality of batteries 14 provided by the business operator. For example, the battery DB 68 stores a battery ID, the battery station 22 to which the battery belongs (or the current location), the remaining battery level, a rental status such as rented / not rented, a usage period (usage start date and time, usage end date and time) of the rented user U, a user ID of the rented user U, etc. The usage contract DB 62 and the battery DB 68 are linked to each other so as to be able to federate with each other, and when information common to both is rewritten in one of them, the information in the other is also rewritten.

[0036] The rental processing unit 70 of the rental control unit 38 performs processing for renting the battery 14 to the user U, for example, following the processing flow of FIG. 7. Specifically, the user U carries the IC card 32 and approaches the battery station 22, and performs an operation to rent the battery 14 via the touch panel 42 of the battery station 22. When the rental processing unit 70 recognizes this rental operation, it guides the user to hold the IC card 32 over the reader 44 (step S2-1). When the user U brings the IC card 32 close to the reader 44, the reader 44 reads the information (user ID, device ID) of the IC card 32 and transmits this information to the rental control unit 38.

[0037] Then, the lending processing unit 70 obtains and stores information on the IC card 32 from the reader 44 (step S2-2). Furthermore, the lending processing unit 70 transmits the user ID together with lending request information indicating a lending request from the user U to the management server 28 (step S2-3).

[0038] When the user authentication unit 64 of the management server 28 receives the rental request information and the user ID from the battery station 22, it reads the usage contract DB 62 and extracts the usage conditions of the user U registered in the usage contract DB 62 based on the user ID (step S2-4). Furthermore, the user authentication unit 64 determines whether the current date and time match the usage start date and time and usage end date and time of the extracted usage conditions, and compares the number of batteries 14 currently being rented to the user U with the usage number of the usage conditions by referring to the battery DB 68. In other words, the sharing system 12 according to this embodiment authenticates in the management server 28 whether the user U is a legitimate user who can currently rent out batteries 14 (step S2-5).

[0039] Then, in the user authentication, when the user authentication unit 64 determines that the user U is eligible to lend the battery 14, it transmits a lending permission instruction to the battery station 22 (step S2-6). The lending permission instruction includes the number of batteries to be used and a device ID in addition to information permitting lending of the battery 14. Note that the user authentication unit 64 transmits a lending denial instruction to the battery station 22 in cases where the user U has not signed a usage contract, the timing of the lending request does not match the usage period, the planned number of batteries to be used has already been lent out, etc. When the lending processing unit 70 receives the lending denial instruction, it displays on the touch panel 42 the fact that the battery 14 cannot be lent out and information on the reason why.

[0040] On the other hand, when the rental processing unit 70 receives and stores the rental permission instruction, it checks the remaining battery power of the stored batteries 14 and selects a battery 14 having a sufficient remaining battery power according to the number of batteries to be used (step S2-7). At this time, if multiple batteries 14 have not been rented out, the rental control unit 38 selects multiple batteries 14. Also, for example, if the number of batteries to be used under the usage contract is two and one battery 14 has been rented out to the user U, the rental control unit 38 selects one battery 14 based on the rental permission information.

[0041] Furthermore, the lending processing unit 70 writes the device ID linked to the user ID to the control circuit 56 of the selected battery 14 (step S2-8). The control circuit 56 of the battery 14 has an internal battery side memory unit 80 capable of storing and erasing one or more device IDs, and the battery 14 is lent to the user U with the device ID stored in this battery side memory unit 80. When multiple batteries 14 are lent to the user U, the lending processing unit 70 assigns a device ID to each battery 14. When multiple device IDs are associated with the user ID, the lending processing unit 70 assigns multiple device IDs to each battery 14.

[0042] Then, the rental processing unit 70 unlocks the battery lock mechanism 46 that has prevented the selected battery 14 from being removed (step S2-9), and notifies the user U of the location of the unlocked battery 14. This allows the user U to borrow the battery 14 by removing the unlocked battery 14.

[0043] Furthermore, the rental processing unit 70 transmits information (battery ID, remaining battery power, etc.) of the battery 14 rented to the user U to the management server 28 (step S2-10). Upon receiving the information of the battery 14, the management server 28 reads the battery DB 68, associates the battery ID with the user ID, and performs processing to change the rental status of the battery 14 to "rented," thereby updating the battery DB 68 (step S2-11).

[0044] The process flow when borrowing the battery 14 is not limited to the above. For example, when the battery station 22 from which the user U borrows the battery 14 is determined, the management server 28 may transmit the usage conditions of the user U (user ID, number of uses) according to the date and time to the rental control unit 38 in advance, and the rental control unit 38 may perform user authentication. Also, for example, the sharing system 12 may be configured to assign a device ID acquired from the IC card 32 to the battery 14, rather than assigning a device ID transmitted from the management server 28 to the rental control unit 38 to the battery 14.

[0045] Next, the process when the user U uses the borrowed battery 14 (step S3 in FIG. 2) will be described. At this time, the sharing system 12 performs device authentication between the battery 14 and the device 16 to authenticate whether the device 16 is one that the user U has registered in advance for use. Through this device authentication, the sharing system 12 supplies charging power for the battery 14 to the device 16 registered by the user U, while prohibiting power supply to unregistered devices 16.

[0046] 8, the control circuit 56 of the battery 14 stores the device ID transmitted from the battery station 22 in a battery-side storage unit 80 when the user U borrows the battery 14. In addition, various functional units are formed in the control circuit 56 by a processor executing a program (not shown) stored in a memory. In detail, the control circuit 56 includes a communication unit 82 that communicates information with the device 16, a device authentication unit 84 that authenticates the device, and a discharge control unit 86 that controls discharge from the battery 14 to the device 16.

[0047] When the battery 14 is attached to the holder of the device 16, the communication unit 82 of the control circuit 56 communicates with the control device 20a of the device 16 to acquire use authentication identification information (hereinafter referred to as use authentication ID) stored in the control device 20a. This use authentication ID is the device ID itself (information related to the device ID) that the device 16 has in advance. With acquisition of the use authentication ID, the device authentication unit 84 compares the device ID with the use authentication ID and determines whether the device ID and the use authentication ID match or not. If the IDs match, it authenticates that the device 16 is capable of supplying power from the battery 14 (hereinafter, the device 16 whose IDs match is referred to as a genuine device). It is preferable that the device authentication unit 84 continues to confirm the continuous use of the battery 14 for the device 16 by periodically performing device authentication even after once determining that the device is a genuine device.

[0048] The discharge control unit 86 keeps the battery 14 in a discharge prohibited state, prohibiting power supply from the battery 14 to the device 16, until the device authentication unit 84 authenticates the device as genuine. Therefore, the device 16 remains stopped. Even if the device authentication unit 84 authenticates that the device ID and the use authentication ID do not match, the discharge control unit 86 maintains the discharge prohibited state. This allows the sharing system 12 to prevent the battery 14 from being used by a device 16 other than a genuine device, thereby preventing theft of the battery 14.

[0049] When the discharge control unit 86 authenticates that the device ID matches the usage authentication ID (genuine device), the device transitions from a discharge prohibited state to a discharge permitted state that permits power supply from the battery 14. As a result, the device 16 receives power supply from the battery 14 to the driving source 18 or the electrical equipment 20, and performs appropriate operations under the operation of the user U.

[0050] Moreover, the device 16 preferably includes a detachment prevention mechanism 88 (see FIG. 1) that prevents the battery 14 from being detached. The detachment prevention mechanism 88 is composed of, for example, a lid 88a that closes a case that houses the battery 14, and a locking unit (not shown) that locks the lid 88a. When the control device 20a receives information that the device is genuine from the control circuit 56 of the battery 14, it operates the detachment prevention mechanism 88 to lock the lid 88a. This makes it possible for the device 16 to prevent theft of the battery 14 in cases where, for example, the user U temporarily leaves the device 16 while using the device.

[0051] 9, a process flow when the battery 14 is mounted will be described below. When the user U mounts the borrowed battery 14 in the holder of the target device 16, the control circuit 56 (communication unit 82) of the battery 14 automatically acquires a usage authentication ID from the device 16 (step S3-1).

[0052] Then, the device authentication unit 84 of the control circuit 56 performs device authentication to determine whether or not the pre-stored device ID matches the acquired usage authentication ID (step S3-2).

[0053] In the device authentication, if the device ID and the use authentication ID match (step S3-2: YES), the device authentication unit 84 authenticates that the device 16 equipped with the battery 14 is a genuine device (step S3-3). As a result, the discharge control unit 86 of the control circuit 56 switches from a discharge prohibited state to a discharge permitted state, thereby enabling power supply from the battery 14 to the device 16 (step S3-4). The control circuit 56 also transmits information indicating that the device is genuine (authentication OK) to the control device 20a of the device 16 (step S3-5). As a result, the control device 20a can output a lock command to the detachment prevention mechanism 88, for example, so that the detachment prevention mechanism 88 can lock the battery 14.

[0054] On the other hand, if the device ID and the in-use authentication ID do not match in the device authentication (step S3-2: NO), the device authentication unit 84 recognizes that the device 16 equipped with the battery 14 is not a genuine device (a non-genuine device) (step S3-6). As a result, the discharge control unit 86 of the control circuit 56 continues the discharge prohibited state in which discharging of the battery 14 is prohibited (step S3-7).

[0055] As described above, when the battery 14 is attached to the device 16, device authentication using the device ID is performed, so that the battery 14 can supply charging power only to the device 16 registered by the user U.

[0056] Returning to FIG. 6, when the remaining battery level of the battery 14 becomes low during the period of use of the battery 14, the user U charges or replaces the battery 14 by storing the battery 14 in the battery station 22 or another charger. The charging control unit 72 of the battery station 22 communicates with the control circuit 56 when storing the battery 14, acquires the battery ID and the remaining battery level, and manages the charging state. At this time, the charging control unit 72 can charge the battery 14 while storing the device ID, so that the user U can easily take out the same battery 14. Note that when the battery 14 is stored for charging, the management unit 40 may be configured to acquire the user ID from the IC card 32 and perform user authentication. This allows the battery 14 to be charged only when it is stored by the legitimate user U, further preventing theft of the battery 14.

[0057] Alternatively, when the user U wishes to exchange the current battery 14 for another battery 14 that has been charged, the user U performs an operation to request an exchange via the touch panel 42. At this time, the charging control unit 72 guides the user to hold the IC card 32 over the reader 44. When the user ID of the IC card 32 is read, the charging control unit 72 erases the device ID of the current battery 14 accommodated in the slot 36 (see also the process when returning the battery 14 described later), and selects another battery 14 that has been charged. Furthermore, the charging control unit 72 assigns a device ID to the selected battery 14, so that the battery 14 can be rented to the user U. When the battery 14 is exchanged, the rental control unit 38 transmits the battery ID of the exchanged battery 14 to the management server 28, and the management server 28 updates the association between the battery ID in the battery DB 68 and the user ID and device ID based on the transmitted information.

[0058] Next, the process when the user U ends use of the rented battery 14 (step S4 in FIG. 2) will be described. As shown in FIG. 10, the rental control unit 38 of the battery station 22 and the management server 28 communicate information with each other while performing appropriate processes, thereby processing the end of use of the battery 14. At this time, the return processing unit 74 (see FIG. 6) of the rental control unit 38 deletes the device ID stored in the accommodated battery 14, based on the user U's operation to return the battery 14 and the acquisition of the user ID from the IC card 32.

[0059] In detail, when the return processing unit 74 recognizes a return operation by the user U via the touch panel 42, it guides the user to place the battery 14 to be returned in the slot 36 and also guides the user to hold the IC card 32 over the reader 44 (step S4-1). When the user U brings the IC card 32 close to the reader 44, the reader 44 reads the information (user ID) of the IC card 32 and transmits this information to the rental control unit 38. As a result, the return processing unit 74 acquires and stores the information of the IC card 32 (step S4-2).

[0060] The return processing unit 74 also transmits the obtained user ID to the management server 28 (step S4-3). The battery monitoring unit 66 of the management server 28 extracts the battery ID (hereinafter referred to as the "rented ID") lent to the user U based on the user ID from the battery DB 68 (step S4-4), and transmits the rented ID to the battery station 22 (step S4-5).

[0061] Meanwhile, the return processing unit 74 acquires and stores the battery ID from the battery 14 accommodated in the slot 36 (step S4-6). Then, the return processing unit 74 compares the acquired battery ID with the received loaned ID, and determines whether the IDs match each other (step S4-7).

[0062] Then, when the battery ID and the loaned ID match, the return processing unit 74 deletes the device ID stored in the battery 14 (step S4-8). That is, the battery station 22 deletes the device ID of the battery 14 based on the user ID acquired from the IC card 32. This puts the battery 14 in a blank state with no device ID, and the return of the battery 14 by the user U is completed.

[0063] At this time, the return processing unit 74 deletes the multiple device IDs collectively by acquiring the user ID even if the battery 14 stores multiple device IDs. Also, when the user U places multiple batteries 14 in each slot 36, the return processing unit 74 deletes the device IDs of each battery 14 collectively.

[0064] Furthermore, the return processing unit 74 transmits information (battery ID, remaining battery power, etc.) of the battery 14 that has been returned by the user U to the management server 28 (step S4-9). Upon receiving the information of the battery 14, the management server 28 reads the battery DB 68, deletes the user ID and device ID linked to the battery ID, and updates the lending status of the battery 14 to not yet lent (step S4-10).

[0065] As described above, the sharing system 12 can prevent theft of the battery 14 by having the battery 14 perform device authentication based on the device ID and switch between permission and prohibition of discharging. Moreover, the device ID in the battery 14 can be easily stored or deleted by the battery station 22 (charger or exchange) by acquiring the user ID.

[0066] Furthermore, the sharing system 12 manages the number of batteries 14 lent to users U (number of batteries to be used) for each user ID, and assigns device IDs to the number of batteries 14 linked to the user ID. This allows the sharing system 12 to avoid lending a large number of batteries 14 to only one user U, thereby preventing other users U from being unable to borrow batteries.

[0067] The present invention is not limited to the above-described embodiment, and various modifications are possible in accordance with the gist of the invention. The sharing system 12 (management system 10) may be configured such that a user U accesses the management server 28 from a user terminal 60 owned by the user U to enter into a contract for use of the battery 14 (including application for a device ID). At this time, the management server 28 transmits the user ID to the user terminal 60, so that the user terminal 60 can manage the user ID. When the user U goes to the battery station 22 to borrow the battery 14, the user inputs the user ID into the battery station 22, and the battery station 22 stores the device ID in the battery 14 and lends out the battery 14.

[0068] As another variation, the management system 10 can be configured with a battery 14, a charger (not shown), and a device 16 owned or rented by the user U. In this case, the charger has the functions of the above-mentioned management unit 40 consisting of a computer having one or more processors, memories, and input / output interfaces. The charger is configured to be able to write a device ID to the battery-side memory unit 80 of the battery 14 and to be able to delete the device ID from the battery-side memory unit 80 based on obtaining a user ID.

[0069] In this way, by performing device authentication using the device ID for the battery 14 owned or borrowed by the user U, it is possible to prevent theft of the battery 14. Furthermore, since the charger stores and deletes the device ID based on the user ID, the user U can easily switch the device 16 to which the battery 14 is applied.

[0070] Alternatively, the management system 10 may include the functions of the management unit 40 described above in the control circuit 56 of the battery 14 owned or borrowed by the user U. For example, the battery 14 has an acquisition unit (not shown) such as a reader capable of acquiring a user ID, and stores the user ID and device ID in advance in the control circuit 56. When the control circuit 56 acquires a user ID via the acquisition unit, it collates the user ID with the stored user ID, and if the IDs match, deletes the stored device ID.

[0071] In this case, the discharge control unit 86 performs the above-mentioned device authentication when the device ID is held, and supplies power if the IDs match, and prohibits power supply when the IDs do not match. On the other hand, when the device ID is not held, the discharge control unit 86 may be configured to supply power to the attached device 16 without performing device authentication. In this way, when the user U suddenly needs to use a device 16 other than the device 16 that he or she had intended to use, the user U can apply the battery 14 to the other device 16 by deleting the device ID.

[0072] The device authentication unit 84 and the discharge control unit 86 may be provided not only in the control circuit 56 of the battery 14, but also in the control device 20a of the device 16. The user ID is not limited to being read from the IC card 32 or user terminal 60 of the user U by the reader 44 of the battery station 22, but may be input by the user U operating the touch panel 42 or another operation unit. The battery station 22 is not limited to having both a function as a charger that charges the battery 14 and a function as an exchanger that exchanges the battery 14, but may have a function of either a charger or an exchanger.

[0073] The technical ideas and effects that can be understood from the above-described embodiments will be described below.

[0074] A first aspect of the present invention is a management system 10 that manages a battery 14 that is removably mounted on a device 16 and can supply power to the device 16, the battery 14 having a battery side memory unit 80 that stores unique device identification information (device ID) of the device 16, and a control unit (control circuit 56) that, when attached to the device 16, supplies power from the battery 14 when it is determined that the in-use authentication identification information (in-use authentication ID) held by the device 16 matches the device identification information, and stops the power supply from the battery 14 when it is determined that the in-use authentication identification information and the device identification information do not match, and is equipped with a management unit 40 that, when user identification information (user ID) for identifying a user U who owns the battery 14 is obtained, stores the device identification information in the battery side memory unit 80 or deletes it from the battery side memory unit 80.

[0075] According to the above, the management system 10 supplies power from the battery 14 when the control unit (control circuit 56) of the battery 14 determines that the device identification information (device ID) and the use authentication identification information (use authentication ID) match. Therefore, the management system 10 can easily use the target device 16 when the battery 14 is installed. Moreover, since the management unit 40 stores or deletes the device identification information in the battery side storage unit 80 based on the acquisition of the user identification information (user ID), the device identification information of the battery 14 can be easily updated. Therefore, the management system 10 further enhances the convenience of using the battery 14 for various devices 16. Since the user identification information is required to store or delete the device identification information, it becomes impossible for anyone other than the user U of the battery 14 to use the power of the battery 14, and as a result, theft of the battery 14 is suppressed. Furthermore, with such a system, it is possible to eliminate a key (physical key, immobilizer, etc.) for starting the device 16 and simplify the configuration of the device 16.

[0076] Furthermore, the management unit 40 has at least one of a charger that charges the battery 14 and an exchange that replaces the battery 14. In this way, by providing the charger or exchange with the function of the management unit 40 that stores and deletes device identification information (device ID), the management system 10 does not need a structure for storing and deleting device identification information in the battery 14, and the configuration of the battery 14 can be simplified.

[0077] The charger or exchange also has an input unit (reader 44) into which user identification information (user ID) is input by the user U, and when the battery 14 is lent to the user U, the charger or exchange stores device identification information (device ID) in the battery-side storage unit 80 based on the user identification information acquired from the input unit, and when the user U returns the battery 14, the charger or exchange deletes the device identification information from the battery-side storage unit 80 based on the user identification information acquired from the input unit. This allows the charger or exchange to easily switch between storing device identification information when the battery 14 is lent to the user U and deleting device identification information when the user U returns the battery 14.

[0078] The charger or exchange can switch the battery 14 between a removable state and an unremovable state, setting the battery 14 that does not store device identification information (device ID) in the unremovable state, and transitioning the battery 14 that stores device identification information from the unremovable state to the removable state when lending the battery 14 to a user U. This allows the user U to remove the battery 14 that reliably stores device identification information from the charger or exchange.

[0079] The management unit 40 also includes a management server 28 capable of communicating with the charger or the exchange and having a database that associates and stores user identification information (user ID) of a user U who has signed a contract to use the battery 14 with device identification information (device ID), and the management server 28 extracts the device identification information from the database based on the user identification information acquired from the charger or the exchange and transmits the extracted device identification information to the charger or the exchange. In this way, by transmitting the device identification information from the management server 28 to the charger or the exchange, the management system 10 can store the device identification information in the battery 14 even if the charger or the exchange does not hold the device identification information.

[0080] The management unit 40 also has a user authentication unit 64 that authenticates whether or not the user U is authorized to use the battery 14 based on the acquired user identification information (user ID). In this way, by having the user authentication unit 64, the management system 10 can prevent a person who is not authorized to use the battery 14 from taking the battery 14.

[0081] Furthermore, when lending batteries 14 to a user U, the management unit 40 manages the number of batteries 14 to be lent in association with user identification information (user ID), and allows the user U to take out batteries 14 when the number of batteries 14 taken out by the user U is equal to or less than the lending number, and restricts the user U from taking out batteries 14 when the number of batteries 14 taken out by the user U exceeds the lending number. In this way, the management system 10 can limit the number of batteries 14 taken out by the user U, and can prevent a situation in which a battery 14 cannot be lent to another person.

[0082] Furthermore, the battery-side storage unit 80 can store a plurality of pieces of device identification information (device IDs). This allows the management system 10 to reuse the battery 14 among a plurality of devices 16 owned by the user U, while disabling the battery 14 from being used in devices other than the plurality of devices 16, thereby preventing theft.

[0083] Furthermore, when the management unit 40 acquires user identification information (user ID) from the user U, the management unit 40 collectively stores multiple pieces of device identification information (device IDs) in the battery side storage unit 80 or collectively deletes the multiple pieces of device identification information from the battery side storage unit 80. This allows the management system 10 to easily store or delete multiple pieces of device identification information for the battery 14.

[0084] A second aspect of the present invention is a battery 14 that is detachably mounted on a device 16 and can supply power to the device 16, and includes a battery-side storage unit 80 that stores device identification information (device ID) unique to the device 16, and a control unit (control circuit 56) that, when mounted on the device 16, supplies power from the battery 14 when it is determined that the in-use authentication identification information (in-use authentication ID) held by the device 16 matches the device identification information, and stops the power supply from the battery 14 when it is determined that the in-use authentication identification information does not match the device identification information, and the device identification information is stored in the battery-side storage unit 80 or deleted from the battery-side storage unit 80 by a management unit 40 that has acquired user identification information (user ID) for identifying a user U who owns the battery 14. This makes it possible for the battery 14 to be more convenient while suppressing theft of the battery 14.

[0085] In addition to the above disclosure, the following notes are also disclosed.

[0086] (Appendix 1) The management system (10) of the present disclosure is a management system that manages a battery (14) that is detachably mounted on a device (16) and can supply power to the device, the battery having a battery-side memory unit (80) that stores device identification information unique to the device, and a control unit (56) that supplies power from the battery when it is determined that the device identification information matches the in-use authentication identification information held by the device while the battery is mounted on the device, and stops the power supply from the battery when it is determined that the in-use authentication identification information does not match the device identification information, and a management unit (40) that stores the device identification information in the battery-side memory unit or deletes it from the battery-side memory unit when user identification information for identifying a user who owns the battery is obtained. This allows the management system to easily use a target device when a battery is mounted. [Explanation of symbols]

[0087] 10...Management system 14...Battery 16...Equipment 40...Management Department 56... Control circuit (control unit) 80... Battery side memory unit

Claims

[Claim 1] A management system for managing a battery that is detachably mounted on a device and can supply power to the device, comprising: The battery includes: a battery side storage unit that stores device identification information unique to the device; a control unit that, when attached to the device, supplies power from the battery when it is determined that in-use authentication identification information held by the device matches the device identification information, and stops the supply of power from the battery when it is determined that the in-use authentication identification information does not match the device identification information, A management system comprising a management unit that, when user identification information for identifying a user who owns the battery is acquired, stores the device identification information in the battery side memory unit or deletes the device identification information from the battery side memory unit.

Images