Patent Grant
12128787
The present invention relates to a battery use system, a charging device, an information processing device, a battery use method, a program, and a storage medium.
Priority is claimed on Japanese Patent Application Nos. 2018-223833 and 2018-223834, filed Nov. 29, 2018, the content of which is incorporated herein by reference.
In recent years, electric vehicles such as electric vehicles (EVs) and hybrid electric vehicles (HEVs), which travel using electric motors driven with electric power supplied from batteries, have been developed. In the electric vehicles, when a battery, which is a drive source, has run out of power, it is necessary to charge the battery to continue subsequent traveling.
Incidentally, some of recent electric vehicles adopt batteries configured to be removable (hereinafter referred to as “removable batteries”). When a currently mounted removable battery has run out of power in an electric vehicle adopting a removable battery, it is possible to continue traveling by performing replacement with another removable battery storing sufficient electric power such as a spare removable battery whose charging is completed. The development of a so-called battery sharing service in which a removable battery is shared by a plurality of users using electric vehicles has been studied.
In the above-described battery sharing service, the user replaces the removable battery at charging stations installed at a plurality of locations. At the charging station, a returned removable battery is charged and stored, and the charged removable battery is rented out when another user comes to replace a removable battery (see, for example, Patent Document 1).
As another example of a movable object from which a battery can be removed, a portable power charging/supplying device including a battery and a power charging/supplying unit in which an accommodation chamber for accommodating the battery is formed is known (see, for example, Patent Document 2).
[Patent Document 1]
Here, after a system is operated, a battery manufacturer may notify that a lot has a defect with respect to batteries. However, in the conventional technology, because a returned battery is charged and the charged battery is rented out to another user, it may not be possible to avoid charging of a battery from a defective lot.
Also, in the conventional technology, electric power capable of being supplied to a battery replacement device for charging a removable battery may differ according to an environment in which a charging station is installed. For example, when the charging station is operated for a limited period, the existing electrical equipment may be utilized without the construction of electrical equipment. For example, a battery replacement device has a plurality of slots for accommodating removable batteries. In this case, electric power for charging all the removable batteries respectively accommodated in the slots may be insufficient.
As described above, in the conventional technology, it is difficult to appropriately charge a battery according to various situations.
Aspects of the present invention have been made in view of the above problems and an objective of the present invention is to provide a battery use system, a charging device, an information processing device, a battery use method, a program, and a storage medium capable of appropriately charging a battery according to various situations.
A battery use system, a charging device, an information processing device, a battery use method, a program, and a storage medium according to the present invention adopt the following configurations.
According to any one aspect described above, it is possible to appropriately charge a battery according to various situations.
Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings used in the following description, the scale of each member is appropriately changed to make each member recognizable. In the following description, a case in which a shared battery management system of the embodiment manages the replacement of a plurality of removable batteries shared by a plurality of saddle riding-type electric vehicles (hereinafter referred to as “electric motorcycles”), which have adopted a battery configured to be removable (hereinafter referred to as a “removable battery”) will be described.
First, an example of an overall configuration of a shared battery management system according to a first embodiment will be described.
As shown in
The electric motorcycle 50 is an electric vehicle that travels using an electric motor driven with electric power supplied from a removable battery 510. The electric motorcycle 50 may be a hybrid electric vehicle that travels according to driving based on a combination of a removable battery 510 and an internal combustion engine such as a diesel engine or a gasoline engine. The electric motorcycle 50 is an example of an “electric power device.”
The “electric power device” is not limited to the electric motorcycle 50 and may be, for example, a vehicle (a one-wheel vehicle, a three-wheel vehicle, a four-wheel vehicle, or the like) which can travel with electric power and on which a removable battery 510 can be removably mounted, or an assist-type bicycle. Instead of these vehicle-type movable objects, the “electric power device” may be a portable power charging/supplying device carried by a person or a vehicle described in Japanese Unexamined Patent Application, First Publication No. 2019-068552. Also, the “electric power device” may be a movable robot, an autonomous traveling device, an electric bicycle, an autonomous traveling vehicle, another electric vehicle, a drone flying object, or another electric movable device (electric mobility). Hereinafter, an example in which the “electric power device” is the electric motorcycle 50 will be described.
The removable battery 510 is, for example, a cassette-type power storage device (secondary battery) that is removably mounted on the electric motorcycle 50. At least one removable battery 510 is mounted on one electric motorcycle 50. In the following description, the electric motorcycle 50 will be described as an electric vehicle equipped with one removable battery 510.
The removable battery 510 is shared by a plurality of electric vehicles. Identification information (hereinafter referred to as a “battery ID” (battery identification information)) for identifying the removable battery 510 is exclusively assigned to the removable battery 510.
The battery ID may be a serial number (a manufacture's serial number) of the removable battery 510. The removable battery 510 is returned and stored in any one of slots 120-1 to 120-8 of the battery replacement device 100.
In the following description, when one of the slots 120-1 to 120-8 is not specified, it is referred to as a slot 120. In the following description, the removable battery 510 returned to the slot 120 by a user of the electric motorcycle 50 due to the consumption of electric power is referred to as a “used removable battery 510u.” The removable battery 510 whose charging is completed by the battery replacement device 100 and which is taken out from the slot 120 by the user of the electric motorcycle 50 is referred to as a “charged removable battery 510c.” In the first embodiment, the term “charged” means that the charging rate is not limited to 100% and the charging rate may be a predetermined value (for example, 80%) or more.
The battery replacement device 100 is installed within a charging/replacement station (not shown). For example, charging/replacement stations are installed at a plurality of locations. The battery replacement device 100 exchanges information with the operation server 200 through communication via the network NW and controls whether or not to perform charging and replacement of the removable battery 510.
More specifically, for example, when the used removable battery 510u has been returned, the battery replacement device 100 transmits a battery state list S in which information about stored and charged removable batteries 510 is recorded to the operation server 200 via the network NW.
The battery replacement device 100 receives an instruction R (a charging stop instruction or a rental prohibition instruction) for each slot 120 transmitted by the operation server 200. The battery state list S, the charging stop instruction (an instruction regarding whether or not charging is available), and a rental prohibition instruction will be described below.
When the charging stop instruction for each slot 120 transmitted by the operation server 200 has been received, the battery replacement device 100 performs control so that charging of the removable battery 510 of a target slot 120 is avoided based on the received charging stop instruction. The charging stop instruction received by the battery replacement device 100 from the operation server 200 is an example of “reception information.”
When the rental prohibition instruction for each slot 120 transmitted by the operation server 200 has been received, the battery replacement device 100 performs control so that rental of the removable battery 510 of the target slot 120 is avoided based on the received rental prohibition instruction. The rental prohibition instruction received by the battery replacement device 100 from the operation server 200 is another example of the “reception information.”
The battery replacement device 100 selects the removable battery 510 to be rented out from the charged removable batteries 510c accommodated in the slot 120 which is not included in each of the charging stop instruction and the rental prohibition instruction and rents out the selected removable battery 510.
The operation server 200 is a server facility that manages a removable battery 510 capable of being replaced by the battery replacement device 100. The operation server 200 generates a charging stop instruction or a rental prohibition instruction based on the information included in the battery state list S transmitted from the battery replacement device 100 and the information stored in the operation server. When the charging stop instruction or the rental prohibition instruction has been generated, the operation server 200 transmits the generated charging stop instruction or rental prohibition instruction to the battery replacement device 100. The information stored in the operation server is, for example, a battery ID of a removable battery 510 of a defective lot or the like. The charging stop instruction or the rental prohibition instruction transmitted by the operation server 200 to the battery replacement device 100 is an example of “transmission information.”
(Configuration of Removable Battery 510)
Next, an example of a configuration of the removable battery 510 will be described.
The power storage 511 is configured to include a storage battery that stores electric power through charging and is discharged with the stored power. As the storage battery included in the power storage 511, for example, a secondary battery such as a lead storage battery or a lithium-ion battery, a capacitor such as an electric double layer capacitor, a composite battery in which a secondary battery and a capacitor are combined, or the like is used.
The measurement sensor 512 is configured to include various types of sensors for measuring the state of the power storage 511. The measurement sensor 512 measures a voltage stored in the power storage 511 using, for example, a voltage sensor. The measurement sensor 512 measures an electric current flowing through the power storage 511 using, for example, an electric current sensor. Also, the measurement sensor 512 measures a temperature at which the power storage 511 is charged or the power storage 511 is discharged using, for example, a temperature sensor. The measurement sensor 512 outputs a measured value representing a measured state of the power storage 511 to a processor on the BMU 513.
The BMU 513 is a battery management unit and controls charging and discharging of the power storage 511. The BMU 513 is configured to include a processor such as, for example, a central processing unit (CPU), and a memory such as, for example, a read only memory (ROM) or a random access memory (RAM), as the storage 514. In the BMU 513, the CPU implements a control function of the power storage 511 by reading and executing a program stored in the storage 514. The BMU 513 causes the storage 514 to store information such as content of the control performed on the power storage 511 based on the measured value representing the state of the power storage 511 output from the measurement sensor 512.
The storage 514 stores battery state information such as a battery ID assigned to the removable battery 510. In addition to the battery ID, the battery state information includes, for example, information such as the number of times of charging, a date of manufacture, a capacity in an initial state, and a charging rate. The storage 514 stores information such as an abnormality or a failure detected by the BMU 513 itself, an abnormality or a failure of the power storage 511 ascertained using the measurement sensor 512, and the like.
The connector 515 is a connector for supplying the electric power stored in the power storage 511 to the electric motor that is the drive source of the electric motorcycle 50 when the removable battery 510 has been mounted on the electric motorcycle 50. The connector 515 is connected to a structure that connects to the removable battery 510 provided on the back side of the accommodating portion 120H when the removable battery 510 has been accommodated in the slot 120 provided in the battery replacement device 100. The connector 515 is also a connector for transmitting information such as a battery ID exchanged, the number of times of charging, and a measured value indicating the state of the power storage 511 between the removable battery 510 and the battery replacement device 100 and transmitting electric power.
(Configuration of Battery Replacement Device 100)
Subsequently, an example of a configuration of the battery replacement device 100 will be described.
When the battery replacement device 100 includes eight slots 120 as shown in
The display 110 is, for example, a liquid crystal display device, an organic electro luminescence (EL) display device, or the like. The display 110 displays image information output by the processor 144. The image information includes, for example, the number of the slot 120 in which the rentable removable battery 510 is accommodated, a usage fee, and the like. The display 110 includes an inputter based on a touch panel sensor or the like. The touch panel sensor detects a result of an operation performed by the user and outputs the operation result, which has been detected, to the processor 144. For example, the operation result includes a replacement instruction for the removable battery 510 or the like.
The connector 120T is a connector including a structure that electrically connects to the connector 515 included in the accommodated removable battery 510 in the slot 120. The connector 120T is provided, for example, on the back side of the accommodation unit 120H, for each slot 120. Each connector 120T transmits information such as a battery ID, the number of times of charging, a deterioration state, and a measured value representing a state of the power storage 511 exchanged between the removable battery 510 accommodated in the corresponding slot 120 and the replacement device controller 140. The connector 120T transmits electric power to the removable battery 510. That is, the connector 120T supplies the power storage 511 with electric power for charging. When there are eight slots 120 as shown in
The charger 120C is a charger for charging the removable battery 510 in accordance with control from the replacement device controller 140 when the removable battery 510 is accommodated in the slot 120 and the connector 515 of the accommodated removable battery 510 is connected to the connector 120T. The charger 120C charges the removable battery 510 by supplying electric power to the power storage 511 of the removable battery 510 via the connector 120T. In the battery replacement device 100, the charger 120C is provided for each slot 120. When there are eight slots 120 as shown in
The replacement device storage 130 stores various information in the battery replacement device 100. The replacement device storage 130 stores a program for the replacement device controller 140 to execute the function of the battery replacement device 100. The replacement device storage 130 stores information about whether or not the removable battery 510 has been accommodated in each slot 120 and a battery ID of the removable battery 510 accommodated in each slot 120. The replacement device storage 130 stores a slot ID of each slot 120. The replacement device storage 130 stores a corresponding relationship between the slot 120 and the slot ID. The replacement device storage 130 may store information such as the number of times the removable battery 510 has been charged, a deteriorated state, a charging rate, and a measured value representing a state of the power storage 511.
The replacement device controller 140 controls the entire battery replacement device 100. The replacement device controller 140 is configured to include, for example, a processor such as a CPU. The replacement device controller 140 implements the function of the battery replacement device 100 by reading and executing the program stored in the replacement device storage 130. More specifically, the replacement device controller 140 controls the charging and rental of the removable batteries 510 respectively accommodated in the slots 120.
The measurement sensor 142 includes various sensors that measure the state when the charger 120C is charging the removable battery 510. The measurement sensor 142 is configured to include, for example, a voltage sensor, an electric current sensor, and a temperature sensor. The measurement sensor 142 measures a voltage applied to the power storage 511 when the removable battery 510 is being charged using the voltage sensor and measures an electric current flowing through the power storage 511 using the current sensor. The measurement sensor 142 measures the temperature of the power storage 511 when the removable battery 510 is being charged using the temperature sensor. The measurement sensor 142 outputs a measured value representing a measured state of the removable battery 510 to the charging controller 141.
The information acquirer 143 acquires the battery state information of the removable battery 510 accommodated in the slot 120, i.e., the removable battery 510 stored in the battery replacement device 100, via the connector 120T. The battery state information includes at least the battery ID. The battery state information may include information such as the number of times of charging and a measured value representing the state of the power storage 511. The information acquirer 143 outputs the acquired battery state information to the processor 144. The information acquirer 143 may cause the replacement device storage 130 to store the acquired battery state information.
The processor 144 carries out a procedure process of replacing the removable battery 510 in the battery replacement device 100. When the processor 144 has acquired the rental prohibition instruction via the replacement device communicator 150, the processor 144 performs control for preventing the opening/closing lid 120L (
The processor 144 generates the battery state list S in which the battery ID is associated with the slot ID for each slot with respect to all the slots 120 included in the battery replacement device 100. The battery state list S may include information representing that slot 120-N is empty and information representing that slot 120-N has failed. The processor 144 outputs the generated battery state list S to the replacement device communicator 150. Thereby, the replacement device communicator 150 communicates with the operation server 200 via the network NW and transmits the battery state list S to the operation server 200. The processor 144 updates the battery state list S when the used removable battery 510u is returned and transmits the updated battery state list S to the operation server 200. Alternatively, the processor 144 may be configured to acquire the battery IDs of the removable batteries 510 of all the slots 120 at each predetermined time or a predetermined time or for each predetermined time period, update the battery state list S, and transmit the updated battery state list S to the operation server 200.
The charging controller 141 controls a state of charge of the removable battery 510. When the charging stop instruction has been acquired via the replacement device communicator 150, the charging controller 141 performs control so that charging is stopped or so that the charging is not performed with respect to the slot 120 corresponding to the slot ID included in the charging stop instruction. The charging stop instruction is an instruction for stopping charging of the removable battery 510 or an instruction for preventing charging from being performed and includes a slot ID of the target slot 120.
Also, the charging controller 141 controls charging of the removable battery 510 by controlling the charger 120C in consideration of a measured value of the removable battery 510 output from the measurement sensor 142 when the charging stop instruction has not been acquired or with respect to the slot 120 corresponding to the slot ID not included in the acquired charging stop instruction. That is, the charging controller 141 excludes the slot 120 included in the charging stop instruction and performs control so that a used removable battery 510u of a charging target is charged.
The charging controller 141 calculates the current charging rate of the removable battery 510 being charged, i.e., the current charging rate of the power storage 511 provided in the removable battery 510, based on the measured value of the removable battery 510 output from the measurement sensor 142 when the charging stop instruction has not been acquired or with respect to the slot ID not included in the acquired charging stop instruction. When the charging of the removable battery 510 has been completed, the charging controller 141 outputs information representing that the charging has been completed to the processor 144.
The replacement device communicator 150 performs wireless communication with the operation server 200 via the network NW in accordance with an instruction from the replacement device controller 140 and transmits the battery state list S to the operation server 200. The replacement device communicator 150 acquires the instruction R (the charging stop instruction or the rental prohibition instruction) from the operation server 200. The replacement device communicator 150 outputs the charging stop instruction or the rental prohibition instruction acquired from the operation server 200 to the replacement device controller 140.
(Configuration of Operation Server 200)
Next, an example of a configuration of the operation server 200 will be described.
The server storage 210 stores various information in the operation server 200. The server storage 210 stores at least the battery state list S transmitted from the battery replacement device 100 via the network NW. The server storage 210 stores a program for the server controller 220 to execute the function of the operation server 200. The server storage 210 stores the battery ID of the removable battery 510 whose charging is desired to be avoided (whose rental is desired to be avoided) based on the information provided from the information provider. An information provider is, for example, a manufacturer of the removable battery 510, an owner who owns the removable battery 510 and rents out his or her own removable battery 510 to another person (for example, a person who has made a lease contract for the removable battery 510 with another person), a manager of the removable battery 510, or the like. The owner or the manager may be, for example, a person who indirectly provides the information provided from the manufacturer to the operation server 200 or a person who performs processing, modification, or the like on the information provided from the manufacturer and indirectly provides information on which the processing, the modification, or the like has been performed to the operation server 200. Also, the owner or the manager may be a person who provides the operation server 200 with independently generated information other than the information provided from the manufacturer. The information provided from the information provider includes, for example, a battery ID of the removable battery 510 whose charging is desired to be avoided (whose rental is desired to be avoided). The server storage 210 may store the information of the battery replacement device ID exclusively assigned to the battery replacement device 100. Hereinafter, an example in which the information provider is the manufacturer of the removable battery 510 will be described.
The server controller 220 controls the entire operation server 200. The server controller 220 is configured to include, for example, a processor such as a CPU. The server controller 220 implements the function of the operation server 200 by reading and executing the program stored in the server storage 210. More specifically, the server controller 220 generates a charging stop instruction or a rental prohibition instruction based on the battery state list S transmitted from the battery replacement device 100 and the battery ID of the removable battery 510 whose charging is desired to be avoided stored in the server storage 210. The server controller 220 outputs the generated charging stop instruction to the server communicator 230. The server controller 220 outputs the generated rental prohibition instruction to the server communicator 230.
The server communicator 230 performs wireless communication with the replacement device communicator 150 provided in the battery replacement device 100 via the network NW. The server communicator 230 receives the battery state list S transmitted from the battery replacement device 100 via the network NW and causes the server storage 210 to store the received battery state list S. The server communicator 230 transmits the charging stop instruction output by the processor 144 to the battery replacement device 100 via the network NW. The server communicator 230 transmits the rental prohibition instruction output by the processor 144 to the battery replacement device 100 via the network NW.
Here, the charging stop instruction and the rental prohibition instruction will be further described. The removable battery 510 whose charging is required to be stopped is, for example, a removable battery 510 of a lot in which a defect has occurred. It is preferable to stop charging or prevent charging from being performed with respect to the above removable battery 510. Also, it is preferable to prevent the removable battery 510 from being rented out.
However, the charged removable battery 510c whose charging has been completed before the charged removable battery 510c becomes a charging stop target may be accommodated in the slot 120. As described above, the charged removable battery 510c may be rented out when it is difficult to perform charging due to a rolling blackout or the like. In this situation, the operation server 200 may be configured to transmit the charging stop instruction for the target removable battery to the battery replacement device 100 without transmitting the rental prohibition instruction. The operation server 200 may be configured to transmit the charging stop instruction and the rental prohibition instruction and determine whether or not rental is to be performed based on the instruction R received by the battery replacement device 100.
(Battery State List)
Next, an example of the battery state list S transmitted by the battery replacement device 100 to the operation server 200 will be described.
As shown in
The battery state list may include the number of times the removable battery 510 has been charged, information representing the deterioration state of the removable battery 510, information representing the charging rate of the removable battery 510, information representing that the slot 120 has failed, information representing that the battery replacement device 100 has failed, information representing the creation date and time (or the update date and time) of the battery state list, and the like.
Next, an example of a processing procedure of the shared battery management system 10 of the first embodiment will be described.
In other words, the server controller 220 determines whether or not there is a battery ID identical with a battery ID of the removable battery 510 whose charging is desired to be avoided (or whose rental is desired to be avoided) registered in step S11 within one or more battery IDs included in the received battery state list S.
When it is determined that the removable battery 510 whose charging is desired to be avoided (or whose rental is desired to be avoided) is in the received battery state list S (step S16; YES), the server controller 220 proceeds to the processing of step S17. When it is determined that the removable battery 510 whose charging is desired to be avoided (or whose rental is desired to be avoided) is not in the received battery state list S (step S16; NO), the server controller 220 returns to the processing of step S16.
In other words, when one or more battery IDs included in the battery state list S include the battery ID of the removable battery 510 whose charging is desired to be avoided (or whose rental is desired to be avoided), the server controller 220 proceeds to the processing of step S17. When one or more battery IDs included in the battery state list S do not include the battery ID of the removable battery 510 whose charging is desired to be avoided (or whose rental is desired to be avoided), the server controller 220 proceeds to the processing of step S16.
Although the example in which the battery replacement device 100 transmits the battery state list S to the operation server 200 has been described in the above-described example, the present invention is not limited thereto. The battery replacement device 100 may be configured to transmit only the battery state information of the returned removable battery 510 to the operation server 200. In this case, the operation server 200 may be configured to determine whether or not the charging is to be stopped or whether or not the rental is to be prohibited with respect to the returned used removable battery 510u.
As described above, in the first embodiment, one slot (one slot 120) is assigned to each of the removable batteries 510 within the battery replacement device 100 and the state of the removable battery 510 for each slot (the presence or absence of the removable battery 510 or the like) and information of the removable battery 510 (a unique value such as a serial number, a charging rate, or the like) are transmitted to the operation server 200. Also, in the first embodiment, the operation server 200 can set whether or not the removable battery 510 can be charged with respect to a slot (a slot 120) of one unit.
Thereby, according to the first embodiment, the information (the unique value such as the serial number) of the removable battery 510 within the battery replacement device 100 can be ascertained on the operation server 200 side of the network destination. Thereby, the operation server 200 can mechanically determine whether or not the product is a defective lot product and perform control so that charging is not performed by transmitting a charging stop instruction with respect to a slot where charging is desired to be stopped.
Also, according to the first embodiment, it is possible to control whether or not charging is available or whether or not rental is available with respect to a returned removable battery because the battery state list is updated and transmitted when the removable battery 510 has been returned.
The operation server 200 may determine whether or not the number of slots for which charging is desired to be avoided (rental is desired to be avoided) hinders the continuation of business of the charging/replacement station where the battery replacement device 100 is installed. For example, when one battery replacement device 100 is installed in the charging/replacement station, the battery replacement device 100 includes eight slots 120, and removable batteries 510 accommodated in four slots 120 are a charging stop target, it may be determined that the continuation of business is hindered. For example, when one battery replacement device 100 is installed in the charging/replacement station, the battery replacement device 100 includes eight slots 120, and removable batteries 510 accommodated in two slots 120 are the charging stop target, it may be determined that the continuation of business is not hindered.
In the above-described first embodiment, an example in which the operation server 200 generates a charging stop instruction or a rental prohibition instruction based on the battery state list S received from the battery replacement device 100 and the information stored in the operation server 200 has been described.
However, when the battery replacement device 100 has been installed in an area where the communication environment is vulnerable, a state in which communication with the operation server 200 may not be possible may occur. Even if the battery is originally a battery whose charging is desired to be avoided (whose rental is desired to be stopped), it is feared that the battery will be rented out without being excluded from rental when the information is not updated due to a communication failure. Thus, an example in which the battery replacement device 100 performs the rental selection even if the communication is unstable as described above will be described in the modified example.
In the modified example, the operation server 200 creates a rentable battery list B in which information of the rentable removable battery 510 and the order of rental has been recorded and transmits the created rentable battery list B to the battery replacement device 100 when communication is possible. The battery replacement device 100 stores the received rentable battery list B. The rentable battery list B includes a rechargeable removable battery 510, i.e., a removable battery 510 whose charging is desired to be avoided is excluded. The rentable battery list B includes information of whether or not rental is available for each slot.
When communication with the operation server 200 is not possible as shown in
The rentable battery list B is, for example, a list in which the battery IDs of the removable batteries 510 with which rental (replacement) can be performed in the battery replacement device 100 are arranged in the order of rental (replacement) or the like. The operation server 200 generates the above-described rentable battery list B based on the battery state information (for example, the date of manufacture, the number of times of charging, the charging rate, or the like) included in the received battery state list S.
As shown in
The battery replacement device 100 can continue a procedure for replacing the removable batteries 510 independently for the number of removable batteries 510 recorded in the rentable battery list B. Thus, in the battery sharing service adopting the shared battery management system 10, when the user P desires to replace the used removable battery 510u, he or she can replace it with the charged removable battery 510c.
Generally, the user P uses the battery sharing service at a timing when it is expected that it becomes difficult for the electric motorcycle 50 to travel due to power consumption of the removable battery 510. Thus, the shared battery management system 10 is very effective in maintaining the provision of the battery sharing service in accordance with the rentable battery list B as in the modified example.
Although a case in which the operation server 200 transmits an instruction such as a charging stop instruction or a rental prohibition instruction to the battery replacement device 100 has been described in the above-described first embodiment, the present invention is not limited thereto. For example, the operation server 200 may transmit a result of determining whether to permit or prohibit charging of the removable battery 510 or a result of determining whether to permit or prohibit rental of the removable battery 510 (detachment of the removable battery 510) to the battery replacement device 100 in place of or in addition to the charging stop instruction or the rental prohibition instruction.
Although a case in which the operation server 200 determines whether or not to stop charging of the removable battery 510 or whether or not to prohibit rental of the removable battery 510 and the instruction (the charging stop instruction or the rental prohibition instruction) based on a determination result is transmitted to the battery replacement device 100 has been described in the above-described first embodiment, the present invention is not limited thereto. For example, the battery replacement device 100 may be configured to determine whether or not to stop charging of the removable battery 510 or whether or not to prohibit rental of the removable battery 510 and control the charging of the removable battery 510 or the rental of the removable battery 510 in accordance with a determination result.
Hereinafter, a second embodiment will be described. In the first embodiment described above, a case in which charging of the removable battery 510 is stopped or rental of the removable battery 510 (detachment of the removable battery 510 from the slot) is prohibited with respect to the removable battery 510 having the same slot ID as the removable battery 510 for which the avoidance of charging or rental is requested from a manufacturer among the removable batteries 510 respectively accommodated in the plurality of slots has been described.
On the other hand, the second embodiment is different from the first embodiment in that charging of removable batteries 510 respectively accommodated in a plurality of slots is controlled based on a constraint condition regarding the electric power capable of being supplied to a battery replacement device 100. Hereinafter, the differences from the first embodiment will be mainly described and features in common with the first embodiment will be omitted. In the description of the second embodiment, the same parts as those of the first embodiment will be described with the same reference signs.
An operation server 200 according to the second embodiment generates a charging stop instruction based on information included in a battery state list S transmitted from the battery replacement device 100 and the information stored in the operation server. The operation server 200 transmits the generated charging stop instruction to the battery replacement device 100. The information stored in the operation server includes electric power capable of being received by the battery replacement device 100 (hereinafter referred to as receivable electric power) and information about the receivable electric power. The receivable electric power may be, for example, electric power (for example, the unit is [W]) or may be an amount of electric power obtained by integrating the electric power with time (for example, the unit is [Wh]). The information about the receivable electric power includes, for example, an upper limit value of the number of slots where charging can be performed simultaneously by the battery replacement device 100 (hereinafter referred to as the upper limit number of slots).
A server storage 210 according to the second embodiment stores the upper limit number of slots of the battery replacement device 100 and stores the battery state list S transmitted from the battery replacement device 100 via a network NW.
A server controller 220 according to the second embodiment generates a charging stop instruction based on the battery state list S transmitted from the battery replacement device 100 and the upper limit number of slots stored in the server storage 210.
For example, the server controller 220 generates a charging stop instruction when a sum of the number of removable batteries 510 being charged included in the battery state list S and the number of removable batteries 510 waiting to be charged are larger than the upper limit number of slots. In this case, for example, the server controller 220 may be configured to permit charging in slots up to the upper limit number of slots in descending order of charging rates. The server controller 220 outputs the generated charging stop instruction to a server communicator 230.
The server controller 220 determines the upper limit number of slots based on, for example, the power consumption of the battery replacement device 100, an electric current value required for charging the removable battery 510, and a value of an electric current capable of being supplied to the battery replacement device 100. The value of the electric current capable of being supplied to the battery replacement device 100 may be read as a value of an electric current capable of being received by the battery replacement device 100.
As in the first embodiment, the server communicator 230 according to the second embodiment performs wireless communication with the replacement device communicator 150 provided in the battery replacement device 100 via the network NW. The server communicator 230 receives the battery state list S transmitted from the battery replacement device 100 via the network NW and causes the server storage 210 to store the received battery state list S. The server communicator 230 transmits the charging stop instruction output by a processor 144 to the battery replacement device 100 via the network NW.
Here, the charging stop instruction will be further described. As for the battery replacement device 100, it is expected that devices having the same specifications will be installed in various environments. The installation environment may be a new store that involves the construction of the electrical equipment, a store that uses the existing electrical equipment, or the like. In the case of a store that uses the existing electrical equipment, it may not be necessary to construct a dedicated power supply environment with the installation of the battery replacement device 100 (for example, a store for a limited period or the like). In the battery replacement device 100 installed in such a store, the number of removable batteries 510 capable of being charged at the same time may be limited. For example, even if the battery replacement device 100 includes eight slots 120 and charging is required in all the eight slots 120 as shown in
Thus, in the second embodiment, the operation server 200 stores the upper limit number of slots for the battery replacement device 100 of each store and determines whether or not it is necessary to stop charging based on the battery state list S and the upper limit number of slots transmitted from each store. For example, when the upper limit number of slots of the battery replacement device 100 installed in a store A is four and the number of removable batteries 510 included in the battery state list S required to be charged is six, the charging stop instruction is transmitted to the two slots 120.
In the example shown in
Although an example in which the removable batteries 510 are accommodated in all the slots 120 is shown in relation to the battery state list S shown in
The battery state list may include the number of times the removable battery 510 has been charged, information representing a deterioration state of the removable battery 510, information representing that the slot 120 has failed, information representing the date and time when the removable battery 510 has been returned, information representing that the battery replacement device 100 has failed, information representing the creation date and time (or an update date and time) of the battery state list, and the like.
Next, an example of a processing procedure in the shared battery management system 10 of the second embodiment will be described.
Normally, the server controller 220 transmits a charging stop command for “(number of slots waiting to be charged)—(upper limit number of slots where simultaneous charging is possible—number of slots where charging is in progress).” However, the server controller 220 may be configured to generate the charging stop instruction so that the number of slots does not exceed an upper limit slot value by preferentially stopping charging when the removable battery 510 is charged at a level higher than or equal to a capacity serving as a rental criterion in the battery replacement device 100 or the like.
As described above, in the second embodiment, one slot (one slot 120) is assigned to each of the removable batteries 510 within the battery replacement device 100 and the state of the removable battery 510 for each slot (the presence or absence of the removable battery 510 or the like) and information of the removable battery 510 (a unique value such as a serial number, a charging rate, or the like) are transmitted to the operation server 200. Also, in the second embodiment, the operation server 200 can set whether or not the removable battery 510 can be charged for a slot (a slot 120) of one unit based on the information about the battery replacement device 100. The information about the battery replacement device 100 includes the upper limit number of slots as described above.
Thereby, according to the first modified example, it is possible to efficiently charge the removable battery 510 because charging is stopped for each slot when the electric power exceeds electric power capable of being supplied to the removable battery 510 in accordance with electric power capable of being supplied to the battery replacement device 100.
In other words, according to the second embodiment, when a maximum load of a replacement device is kept at a specific value or less because there is dependency on the installation environment of the battery replacement device 100, the operation server 200 side can preset the number of slots where simultaneous charging is possible in the battery replacement device 100 and issue the charging stop instruction to the battery replacement device 100 so that the number of slots does not exceeds the number of slots where simultaneous charging is possible. The reason why there is dependency on the installation environment of the battery replacement device 100 is that, for example, the indoor wiring of connected system power cannot withstand the maximum load of the replacement device or the like.
As a result, according to the second embodiment, it is not necessary to take an individual measure such as rewriting the program for each battery replacement device 100 because the process of the battery replacement device 100 is executed by the command from the operation server 200 side and the operation cost can be reduced because implementation is enabled using the same housing at multiple locations.
Also, according to the second embodiment, when the removable battery 510 has been returned, the battery state list is updated and transmitted, so that it is possible to control whether or not the returned removable battery can be charged.
Although an example in which the operation server 200 stores the upper limit number of slots in the battery replacement device 100 has been described in the above-described second embodiment, the present invention is not limited thereto.
As shown in
On the other hand, in the example shown in
The charging characteristics shown in
The components of the battery replacement device 100, the operation server 200, and the removable battery 510 in the first modified example are the same as those in
The server storage 210 of the operation server 200 stores an upper limit electric current value (or an upper limit electric power value) for a value of an electric current (electric power) capable of being supplied to the battery replacement device 100 for each battery replacement device 100 as constraint information. The server storage 210 stores the charging characteristics (see
The server controller 220 generates the charging stop instruction based on the battery state list S transmitted from the battery replacement device 100 and the upper limit electric current value stored in the server storage 210. For example, the server controller 220 generates the charging stop instruction when a sum of a value of electric power consumed in the slot 120 (hereinafter referred to as a consumed electric power value) according to charging the removable battery 510 being charged included in the battery state list S, a consumed electric power value of the slot 120 according to charging of the removable battery 510 waiting to be charged, and an operating basic electric power value of the battery replacement device 100 is larger than the upper limit electric power value.
Alternatively, for example, the server controller 220 generates the charging stop instruction when a sum of a value of electric current consumed in the slot 120 (hereinafter referred to as a consumed electric current value) according to charging the removable battery 510 being charged included in the battery state list S, a consumed electric current value of the slot 120 according to charging of the removable battery 510 waiting to be charged, and an operating basic electric current value of the battery replacement device 100 is larger than the upper limit electric current value.
The server controller 220 calculates an electric current value for charging based on the charging rate of each removable battery 510 being charged and waiting to be charged included in the battery state list S. In this case, for example, the server controller 220 may be configured to permit charging in slots up to the upper limit number of slots in descending order of charging rates. The server controller 220 outputs the generated charging stop instruction to the server communicator 230. The battery state list S is an example of “corresponding information.”
Next, an example of a processing procedure in the shared battery management system 10 of the first modified example will be described.
Processing similar to that in
When it is determined that the sum of a consumed electric current value (or a consumed electric power value) of the slot 120 where the removable battery 510 being charged is accommodated, a consumed electric current value (or a consumed electric power value) of the slot 120 where the removable battery 510 waiting to be charged is accommodated, and an operating basic electric current value of the battery replacement device 100 is larger than the upper limit electric current value (or the upper limit electric power value) (step S21; YES), the server controller 220 proceeds to the processing of step S15.
When it is determined that the sum of a consumed electric current value (or a consumed electric power value) of the slot 120 where the removable battery 510 being charged is accommodated, the consumed electric current value (or a consumed electric power value) of the slot 120 where the removable battery 510 waiting to be charged is accommodated, and an operating basic electric current value of the battery replacement device 100 is smaller than or equal to the upper limit electric current value (or the upper limit electric power value) (step S21; NO), the server controller 220 returns to the processing of step S13.
When the upper limit electric current value (or the upper limit electric power value) is used as described above, it is desirable that the battery replacement device 100 periodically (for example, every 1 or 5 minutes) transmit the battery state list to the operation server 200. The operation server 200 can accurately control the slot where charging is stopped by acquiring the charging rate of the removable battery 510 accommodated in each slot 120 based on the received battery state list.
As described above, in the first modified example, one slot (one slot 120) is assigned to each of the removable batteries 510 within the battery replacement device 100 and the state of the removable battery 510 for each slot (the presence or absence of the removable battery 510 or the like) and information of the removable battery 510 (a unique value such as a serial number, a charging rate, or the like) are transmitted to the operation server 200. In the second embodiment, the operation server 200 can set whether or not the removable battery 510 can be charged for a slot (a slot 120) of one unit based on the information about the battery replacement device 100. As described above, the information about the battery replacement device 100 is an upper limit electric current value or an upper limit electric power value and is information representing electric power capable of being supplied to the battery replacement device.
Thereby, according to the first modified example, it is possible to efficiently charge the removable battery 510 because charging is stopped for each slot when the electric power exceeds electric power capable of being supplied to the removable battery 510 in accordance with electric power capable of being supplied to the battery replacement device 100.
As a result, according to the first modified example, effects similar to those of the second embodiment can be obtained. According to the first modified example, it is not necessary to take an individual measure such as rewriting the program for each battery replacement device 100 because the process of the battery replacement device 100 is executed by the command from the operation server 200 side and the operation cost can be reduced because implementation is enabled using the same housing at multiple locations.
Even in the modified example, because the battery state list is updated and transmitted when the removable battery 510 has been returned, it is possible to control whether or not the returned removable battery can be charged.
In the first modified example of the second embodiment described above, an example in which the operation server 200 generates a charging stop instruction and a rental prohibition instruction based on the battery state list S received from the battery replacement device 100 and the information stored in the operation server 200 has been described.
However, when the battery replacement device 100 has been installed in an area where the communication environment is vulnerable, a state in which communication with the operation server 200 may not be possible may occur.
Thus, in the modified example, an example in which the battery replacement device 100 performs charging stop control even if the communication is unstable as described above will be described.
In the second modified example, the operation server 200 creates the upper limit number of slots B, which is information representing the number of slots where charging is possible, and transmits the created upper limit number of slots B to the battery replacement device 100 when communication is possible. The operation server 200 generates the upper limit number of slots B based on, for example, the maximum charging electric current value of the charging characteristics shown in
When the battery replacement device 100 cannot communicate with the operation server 200 as shown in
As shown in
Although a case in which the operation server 200 transmits instructions such as a charging stop instruction and a rental prohibition instruction to the battery replacement device 100 has been described in the above-described second embodiment, the present invention is not limited thereto. For example, the operation server 200 may transmit a slot ID of a slot 120 where a rechargeable removable battery 510 has been accommodated or the like to the battery replacement device 100 in place of or in addition to the charging stop instruction or the rental prohibition instruction.
Although a case in which the operation server 200 determines whether or not charging of the removable battery 510 is to be stopped or whether or not rental of the removable battery 510 is to be prohibited and the instruction (the charging stop instruction or the rental prohibition instruction) based on a determination result is transmitted to the battery replacement device 100 has been described in the above-described second embodiment, the present invention is not limited thereto. For example, the battery replacement device 100 may be configured to determine whether or not charging of the removable battery 510 is to be stopped or whether or not rental of the removable battery 510 is to be prohibited and control the charging of the removable battery 510 or the rental of the removable battery 510 in accordance with a determination result.
Also, all or a part of a process to be performed by the battery replacement device 100 or the operation server 200 may be performed by recording a program for implementing all or some of the functions of the battery replacement device 100 or the operation server 200 according to the present invention on a computer-readable recording medium and causing a computer system to read and execute the program recorded on the recording medium. Also, the “computer system” used here is assumed to include an operating system (OS) and hardware such as peripheral devices. Also, the “computer system” is assumed to include a homepage providing environment (or displaying environment) when a World Wide Web (WWW) system is used. The “computer-readable recording medium” refers to a storage device, including a flexible disk, a magneto-optical disc, a read only memory (ROM), a portable medium such as a compact disc (CD)-ROM, and a hard disk embedded in the computer system. Further, the “computer-readable recording medium” is assumed to include a computer-readable recording medium for retaining the program for a given time period as in a volatile memory (a random access memory (RAM)) inside the computer system including a server and a client when the program is transmitted via a network such as the Internet or a communication circuit such as a telephone circuit.
Also, the above-described program may be transmitted from a computer system storing the program in a storage device or the like via a transmission medium or transmitted to another computer system by transmission waves in a transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium including a function of transmitting information, like a network (a communication network) such as the Internet or a communication circuit (a communication line) such as a telephone circuit. Also, the above-described program may be a program for implementing some of the above-described functions. Further, the above-described program may be a program capable of implementing the above-described function in combination with a program already recorded on the computer system, i.e., a so-called differential file (differential program).
The above-described embodiments can be expressed as follows.
According to (1-1), the battery state list in which the identification information of the removable battery accommodated in each slot and the slot identification information are associated is transmitted to the operation server and the operation server is configured to determine whether or not the charging is available for each slot. Thereby, according to (1-1), it is possible to avoid charging of the removable battery whose charging is desired to be avoided.
According to (1-2), the operation server is configured to determine whether or not the charging is available for each slot based on the battery state list and the information from the manufacturer of the removable battery. Thereby, according to (1-1), for example, it is possible to avoid rental of a removable battery of a defective lot.
According to (1-3), because the battery state list is updated and transmitted when the removable battery has been returned, it is possible to control whether or not charging is available or whether or not rental is available with respect to the returned removable battery.
According to (1-4), in the shared battery management system, it is possible to avoid the rental of a removable battery that has deteriorated beyond a limit. According to (1-4), in the shared battery management system, a removable battery having a charging rate of a predetermined proportion or more can be included in the removable batteries for which rental (replacement) is possible. According to (1-4), in the shared battery management system, a flexible method of charging or renting out a removable battery according to the way of thinking or an intention of a manager of the shared battery management system and an operator of the battery sharing service adopting the shared battery management system can be provided.
According to (1-5), even if a state in which communication is disabled between the battery replacement device and the operation server has occurred, the battery replacement device can rent out the removable battery based on the rentable battery list acquired from the operation server.
Also, the above-described embodiment can be expressed as follows.
According to (2-1), the battery state list in which the identification information of the removable battery accommodated in each slot and the slot identification information are associated is transmitted to the operation server and the operation server is configured to determine whether or not the charging is available for each slot based on the received battery state list and the reception information representing the electric power capable of being supplied to the battery replacement device. Thereby, according to (2-1), it is possible to control charging of the removable battery for each slot in accordance with the electric power capable of being supplied to the battery replacement device.
According to (2-2), the operation server is configured to determine whether or not charging is available based on the upper limit number of slots, the number of slots where charging is in progress included in the battery state list received by the battery replacement device, and the number of slots waiting for charging. Thereby, according to (2-2), it is possible to perform control so that charging of the removable battery accommodated in the slot exceeding charging based on the number of slots according to the electric power capable of being supplied to the battery replacement device is stopped.
According to (2-3), the operation server may be configured to determine whether or not charging is available for each slot based on a consumed electric current value of a slot where charging is in progress included in the battery state list received by the battery replacement device, a consumed electric current value of a slot waiting for charging, and an electric current value required to operate the battery replacement device. Thereby, according to (2-3), it is possible to perform control so that charging of the removable battery accommodated in the slot exceeding charging based on the number of slots according to a value of an electric current capable of being supplied to the battery replacement device is stopped.
According to (2-4), the operation server may be configured to determine whether or not charging is available for each slot based on a consumed electric power value of a slot where charging is in progress included in the battery state list received by the battery replacement device, a consumed electric power value of a slot waiting for charging, and an electric power value required to operate the battery replacement device. Thereby, according to (2-4), it is possible to perform control so that charging of the removable battery accommodated in the slot exceeding charging based on the number of slots according to a value of electric power capable of being supplied to the battery replacement device is stopped.
According to (2-5), because the battery state list is updated and transmitted when the removable battery has been returned, it is possible to control whether or not charging is available or whether or not rental is available with respect to the returned removable battery.
According to (2-6), in the shared battery management system, it is possible to avoid the rental of a removable battery that has deteriorated beyond a limit. According to (2-6), in the shared battery management system, a removable battery having a charging rate of a predetermined proportion or more can be included in the removable batteries for which rental (replacement) is possible. According to (2-6), in the shared battery management system, a flexible method of charging or renting out a removable battery according to the way of thinking or an intention of a manager of the shared battery management system and an operator of the battery sharing service adopting the shared battery management system can be provided.
According to (2-7), even if a state in which communication is disabled between the battery replacement device and the operation server has occurred, the battery replacement device can rent out the removable battery based on the rentable battery list acquired from the operation server.
Although modes for carrying out the present invention have been described above using the embodiments, the present invention is not limited to the embodiments and various modifications and replacements can be applied without departing from the spirit and scope of the present invention.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2018-223833 | Nov 2018 | JP | national |
| 2018-223834 | Nov 2018 | JP | national |
This application is a Continuation of application Ser. No. 17/296,566 filed on May 25, 2021, which is a Section 371 National Phase of PCT International application No. PCT/JP2019/046821 filed on Nov. 29, 2019, the entire content of both of which are incorporated herein by reference. Priority is claimed on Japanese Patent Application No. 2018-223833 and Japanese Patent Application No. 2018-223834, both filed Nov. 29, 2018, the entire content of both of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5349535 | Gupta | Sep 1994 | A |
| 5631536 | Tseng | May 1997 | A |
| 5831350 | McConkey et al. | Nov 1998 | A |
| 6154006 | Hatanaka et al. | Nov 2000 | A |
| 6184655 | Malackowski | Feb 2001 | B1 |
| 6522101 | Malackowski | Feb 2003 | B2 |
| 6921939 | Zeng | Jul 2005 | B2 |
| 7723951 | Poisner | May 2010 | B2 |
| 7948207 | Scheucher | May 2011 | B2 |
| 7993155 | Heichal et al. | Aug 2011 | B2 |
| 8006793 | Heichal et al. | Aug 2011 | B2 |
| 8013571 | Agassi et al. | Sep 2011 | B2 |
| 8022666 | Li | Sep 2011 | B2 |
| 8026698 | Scheucher | Sep 2011 | B2 |
| 8098046 | Poisner | Jan 2012 | B2 |
| 8100210 | Takeuchi et al. | Jan 2012 | B2 |
| 8164300 | Agassi et al. | Apr 2012 | B2 |
| 8454377 | Heichal et al. | Jun 2013 | B2 |
| 8516687 | Hozumi et al. | Aug 2013 | B2 |
| 8517132 | Heichal et al. | Aug 2013 | B2 |
| 8560147 | Taylor et al. | Oct 2013 | B2 |
| 8710795 | Scheucher | Apr 2014 | B2 |
| 8729865 | Scheucher | May 2014 | B2 |
| 8796987 | Scheucher | Aug 2014 | B2 |
| 8860377 | Scheucher | Oct 2014 | B2 |
| 8862304 | Chen et al. | Oct 2014 | B2 |
| 8963481 | Prosser et al. | Feb 2015 | B2 |
| 8996212 | Chen et al. | Mar 2015 | B2 |
| 9007020 | Prosser et al. | Apr 2015 | B2 |
| 9070923 | Yu et al. | Jun 2015 | B2 |
| 9103686 | Pettersson | Aug 2015 | B2 |
| 9124085 | Wu et al. | Sep 2015 | B2 |
| 9176680 | Chen et al. | Nov 2015 | B2 |
| 9275505 | Taylor et al. | Mar 2016 | B2 |
| 9280654 | Peterson | Mar 2016 | B1 |
| 9348381 | Khoo et al. | May 2016 | B2 |
| 9352905 | Fly | May 2016 | B2 |
| 9381822 | Scheucher | Jul 2016 | B2 |
| 9390566 | Taylor et al. | Jul 2016 | B2 |
| 9424697 | Wu et al. | Aug 2016 | B2 |
| 9525293 | Ito et al. | Dec 2016 | B2 |
| 9537336 | Suzuki et al. | Jan 2017 | B2 |
| 9566954 | Moskowitz | Feb 2017 | B2 |
| 9711868 | Scheucher | Jul 2017 | B2 |
| 9758030 | Newman | Sep 2017 | B2 |
| 9770996 | Chen et al. | Sep 2017 | B2 |
| 9834183 | Moskowitz | Dec 2017 | B2 |
| 9857863 | Kobayashi | Jan 2018 | B2 |
| 9866046 | Ito et al. | Jan 2018 | B2 |
| 9868421 | Hassounah | Jan 2018 | B2 |
| 9908506 | Taylor et al. | Mar 2018 | B2 |
| 9932019 | Hassounah | Apr 2018 | B2 |
| 9937818 | Newman | Apr 2018 | B2 |
| 9960637 | Sanders et al. | May 2018 | B2 |
| 10040359 | Chen et al. | Aug 2018 | B2 |
| 10040364 | Nishi et al. | Aug 2018 | B2 |
| 10084329 | Hamilton et al. | Sep 2018 | B2 |
| 10110029 | Toya | Oct 2018 | B2 |
| 10144307 | Newman et al. | Dec 2018 | B2 |
| 10160344 | Newman | Dec 2018 | B2 |
| 10169783 | Khoo et al. | Jan 2019 | B2 |
| 10185977 | Khoo et al. | Jan 2019 | B2 |
| 10185978 | Khoo et al. | Jan 2019 | B2 |
| 10192245 | Khoo et al. | Jan 2019 | B2 |
| 10210552 | Khoo et al. | Feb 2019 | B2 |
| 10288439 | Pederson | May 2019 | B2 |
| 10345843 | Luke et al. | Jul 2019 | B2 |
| 10387688 | Toya | Aug 2019 | B2 |
| 10406931 | Nakano et al. | Sep 2019 | B2 |
| 10459471 | Luke et al. | Oct 2019 | B2 |
| 10467827 | Taylor et al. | Nov 2019 | B2 |
| 10476284 | Suzuki et al. | Nov 2019 | B2 |
| 10529151 | Luke et al. | Jan 2020 | B2 |
| 10532667 | Chen et al. | Jan 2020 | B2 |
| 10546438 | Chen et al. | Jan 2020 | B2 |
| 10549729 | Moskowitz | Feb 2020 | B2 |
| 10551442 | Horie et al. | Feb 2020 | B2 |
| 10573103 | Taylor et al. | Feb 2020 | B2 |
| 10586258 | Khoo et al. | Mar 2020 | B2 |
| 10622834 | Sanders et al. | Apr 2020 | B2 |
| 10622835 | Sanders et al. | Apr 2020 | B2 |
| 10661676 | Takatsuka et al. | May 2020 | B2 |
| 10719867 | Uchida | Jul 2020 | B2 |
| 10763692 | Pelletier et al. | Sep 2020 | B2 |
| 10819145 | Luke et al. | Oct 2020 | B2 |
| 10839433 | Khoo et al. | Nov 2020 | B2 |
| 10846674 | Rayner | Nov 2020 | B2 |
| 10846763 | Khoo et al. | Nov 2020 | B2 |
| 10861066 | Khoo et al. | Dec 2020 | B2 |
| 10866108 | Pederson | Dec 2020 | B2 |
| 10872361 | Khoo et al. | Dec 2020 | B2 |
| 10894484 | Han et al. | Jan 2021 | B2 |
| 10926742 | Lai et al. | Feb 2021 | B2 |
| 10992155 | Meriac et al. | Feb 2021 | B2 |
| 10935606 | Takatsuka et al. | Mar 2021 | B2 |
| 10938221 | Tenorio | Mar 2021 | B1 |
| 10944278 | Kang et al. | Mar 2021 | B1 |
| 10944279 | Chen et al. | Mar 2021 | B1 |
| 11002557 | Pederson | May 2021 | B2 |
| 11014468 | Shiiyama et al. | May 2021 | B2 |
| 11084365 | Chen et al. | Aug 2021 | B2 |
| 11095140 | Chen et al. | Aug 2021 | B1 |
| 11097632 | Üyeki | Aug 2021 | B2 |
| 11101677 | Shih et al. | Aug 2021 | B2 |
| 11133690 | Chen et al. | Sep 2021 | B1 |
| 11136008 | Lai et al. | Oct 2021 | B2 |
| 11139684 | Wu et al. | Oct 2021 | B2 |
| 11169555 | Luke et al. | Nov 2021 | B2 |
| 11180049 | Kim et al. | Nov 2021 | B2 |
| 11203266 | Ikui et al. | Dec 2021 | B2 |
| 11239674 | Hamilton, IV et al. | Feb 2022 | B2 |
| 11258301 | Sanders et al. | Feb 2022 | B2 |
| 11271425 | Sanders et al. | Mar 2022 | B2 |
| 11315057 | Ikui | Apr 2022 | B2 |
| 11403609 | Rayner | Aug 2022 | B2 |
| 11422000 | Pederson | Aug 2022 | B2 |
| 11423378 | Rayner | Aug 2022 | B2 |
| 11861638 | Hidaka | Jan 2024 | B2 |
| 11862987 | Daga | Jan 2024 | B2 |
| 11916419 | Takahashi | Feb 2024 | B2 |
| 12001983 | Ikui | Jun 2024 | B2 |
| 20010020838 | Malackowski | Sep 2001 | A1 |
| 20020008284 | Zeng | Jan 2002 | A1 |
| 20030209375 | Suzuki et al. | Nov 2003 | A1 |
| 20070182576 | Proska et al. | Aug 2007 | A1 |
| 20070188130 | Scheucher | Aug 2007 | A1 |
| 20070188137 | Scheucher | Aug 2007 | A1 |
| 20080007211 | Poisner | Jan 2008 | A1 |
| 20080053716 | Scheucher | Mar 2008 | A1 |
| 20080157722 | Nobutaka et al. | Jul 2008 | A1 |
| 20080258682 | Li | Oct 2008 | A1 |
| 20090198372 | Hammerslag | Aug 2009 | A1 |
| 20100071979 | Heichal et al. | Mar 2010 | A1 |
| 20100094496 | Hershkovitz et al. | Apr 2010 | A1 |
| 20100112843 | Heichal et al. | May 2010 | A1 |
| 20100141206 | Agassi et al. | Jun 2010 | A1 |
| 20100201307 | Poisner | Aug 2010 | A1 |
| 20100250043 | Scheucher | Sep 2010 | A1 |
| 20110044791 | Agassi et al. | Feb 2011 | A1 |
| 20110106294 | Bebbington | May 2011 | A1 |
| 20110221384 | Scheucher | Sep 2011 | A1 |
| 20110297470 | Heichal et al. | Dec 2011 | A1 |
| 20110303509 | Agassi et al. | Dec 2011 | A1 |
| 20120009804 | Heichal et al. | Jan 2012 | A1 |
| 20120080941 | Scheucher | Apr 2012 | A1 |
| 20120233850 | Hozumi et al. | Sep 2012 | A1 |
| 20120299531 | Prosser et al. | Nov 2012 | A1 |
| 20120299544 | Prosser et al. | Nov 2012 | A1 |
| 20120303213 | Prosser et al. | Nov 2012 | A1 |
| 20120303259 | Prosser | Nov 2012 | A1 |
| 20120303397 | Prosser | Nov 2012 | A1 |
| 20120316671 | Hammerslag et al. | Dec 2012 | A1 |
| 20130027183 | Wu et al. | Jan 2013 | A1 |
| 20130030608 | Taylor et al. | Jan 2013 | A1 |
| 20130031318 | Chen et al. | Jan 2013 | A1 |
| 20130046457 | Pettersson | Feb 2013 | A1 |
| 20130110296 | Khoo et al. | May 2013 | A1 |
| 20130153315 | Yu et al. | Jun 2013 | A1 |
| 20140012462 | Chen et al. | Jan 2014 | A1 |
| 20140053620 | Taylor et al. | Feb 2014 | A1 |
| 20140163813 | Chen et al. | Jun 2014 | A1 |
| 20140312845 | Scheucher | Oct 2014 | A1 |
| 20140316939 | Uyeki | Oct 2014 | A1 |
| 20140350716 | Fly | Nov 2014 | A1 |
| 20140361740 | Suzuki et al. | Dec 2014 | A1 |
| 20150015205 | Ito et al. | Jan 2015 | A1 |
| 20150042157 | Chen et al. | Feb 2015 | A1 |
| 20150123468 | Wu et al. | May 2015 | A1 |
| 20150134142 | Taylor et al. | May 2015 | A1 |
| 20150149015 | Nakano et al. | May 2015 | A1 |
| 20150153967 | Chen et al. | Jun 2015 | A1 |
| 20150165917 | Robers et al. | Jun 2015 | A1 |
| 20150249353 | Hamilton, IV et al. | Sep 2015 | A1 |
| 20150306967 | Cohen | Oct 2015 | A1 |
| 20150336465 | Luke et al. | Nov 2015 | A1 |
| 20160001748 | Moskowitz | Jan 2016 | A1 |
| 20160068075 | Chen et al. | Mar 2016 | A1 |
| 20160075247 | Uyeki | Mar 2016 | A1 |
| 20160099590 | Velderman | Apr 2016 | A1 |
| 20160145903 | Taylor et al. | May 2016 | A1 |
| 20160178678 | Pelletier et al. | Jun 2016 | A1 |
| 20160190866 | Pelletier et al. | Jun 2016 | A1 |
| 20160280089 | Uyeki et al. | Sep 2016 | A1 |
| 20160292937 | Taylor et al. | Oct 2016 | A1 |
| 20160339792 | Khoo et al. | Nov 2016 | A1 |
| 20160339793 | Khoo et al. | Nov 2016 | A1 |
| 20160347281 | Wu et al. | Dec 2016 | A1 |
| 20160362016 | Khoo et al. | Dec 2016 | A1 |
| 20160364658 | Khoo et al. | Dec 2016 | A1 |
| 20160364776 | Khoo et al. | Dec 2016 | A1 |
| 20160368464 | Hassounah | Dec 2016 | A1 |
| 20170005474 | Sanders et al. | Jan 2017 | A1 |
| 20170005477 | Sanders et al. | Jan 2017 | A1 |
| 20170005515 | Sanders et al. | Jan 2017 | A1 |
| 20170070067 | Suzuki et al. | Mar 2017 | A1 |
| 20170070068 | Ito et al. | Mar 2017 | A1 |
| 20170097652 | Luke et al. | Apr 2017 | A1 |
| 20170113661 | Moskowitz | Apr 2017 | A1 |
| 20170193250 | Toya | Jul 2017 | A1 |
| 20170201110 | Toya | Jul 2017 | A1 |
| 20170217326 | Nishi et al. | Aug 2017 | A1 |
| 20170225557 | Newman | Aug 2017 | A1 |
| 20170225587 | Newman | Aug 2017 | A1 |
| 20170225588 | Newman | Aug 2017 | A1 |
| 20170225662 | Newman et al. | Aug 2017 | A1 |
| 20170355354 | Hassounah | Dec 2017 | A1 |
| 20180045786 | Takatsuka et al. | Feb 2018 | A1 |
| 20180118174 | Moskowitz | May 2018 | A1 |
| 20180178669 | Kudo et al. | Jun 2018 | A1 |
| 20180182188 | Luke et al. | Jun 2018 | A1 |
| 20180222343 | Uchida | Aug 2018 | A1 |
| 20180257603 | Taylor et al. | Sep 2018 | A1 |
| 20180262019 | Homma | Sep 2018 | A1 |
| 20180272990 | Chen et al. | Sep 2018 | A1 |
| 20190006862 | Hamilton, IV et al. | Jan 2019 | A1 |
| 20190023138 | Takatsuka et al. | Jan 2019 | A1 |
| 20190028903 | Carpenter et al. | Jan 2019 | A1 |
| 20190028904 | Carpenter et al. | Jan 2019 | A1 |
| 20190061552 | Amari et al. | Feb 2019 | A1 |
| 20190126775 | Han et al. | May 2019 | A1 |
| 20190139107 | Khoo et al. | May 2019 | A1 |
| 20190148690 | Newman | May 2019 | A1 |
| 20190156382 | Khoo et al. | May 2019 | A1 |
| 20190156383 | Khoo et al. | May 2019 | A1 |
| 20190156384 | Khoo et al. | May 2019 | A1 |
| 20190168627 | Chen et al. | Jun 2019 | A1 |
| 20190180336 | Khoo et al. | Jun 2019 | A1 |
| 20190202415 | Lai et al. | Jul 2019 | A1 |
| 20190202416 | Lai et al. | Jul 2019 | A1 |
| 20190207393 | Shih et al. | Jul 2019 | A1 |
| 20190207398 | Shih et al. | Jul 2019 | A1 |
| 20190213809 | Luke et al. | Jul 2019 | A1 |
| 20190261194 | Carpenter et al. | Aug 2019 | A1 |
| 20190287324 | Wu et al. | Sep 2019 | A1 |
| 20190288555 | Sanders et al. | Sep 2019 | A1 |
| 20190288556 | Sanders et al. | Sep 2019 | A1 |
| 20190316930 | Luke et al. | Oct 2019 | A1 |
| 20190333037 | Rayner | Oct 2019 | A1 |
| 20190359076 | Nakano et al. | Nov 2019 | A1 |
| 20190387416 | Carpenter et al. | Dec 2019 | A1 |
| 20200001738 | Sohmshetty et al. | Jan 2020 | A1 |
| 20200009984 | Shiiyama et al. | Jan 2020 | A1 |
| 20200035046 | Luke et al. | Jan 2020 | A1 |
| 20200084639 | Carpenter et al. | Mar 2020 | A1 |
| 20200164760 | Sohmshetty et al. | May 2020 | A1 |
| 20200198494 | Chen et al. | Jun 2020 | A1 |
| 20200231058 | Hishida et al. | Jul 2020 | A1 |
| 20200235602 | Hishida et al. | Jul 2020 | A1 |
| 20200244089 | Nishida | Jul 2020 | A1 |
| 20200244100 | Sanders et al. | Jul 2020 | A1 |
| 20200343764 | Sanders et al. | Oct 2020 | A1 |
| 20200384879 | Ebisu et al. | Dec 2020 | A1 |
| 20200391602 | Ikui et al. | Dec 2020 | A1 |
| 20200402075 | Ebisu et al. | Dec 2020 | A1 |
| 20210019720 | Rayner | Jan 2021 | A1 |
| 20210035077 | Rayner | Feb 2021 | A1 |
| 20210061124 | Kim et al. | Mar 2021 | A1 |
| 20210073876 | Khoo et al. | Mar 2021 | A1 |
| 20210090139 | Khoo et al. | Mar 2021 | A1 |
| 20210090140 | Khoo et al. | Mar 2021 | A1 |
| 20210090141 | Khoo et al. | Mar 2021 | A1 |
| 20210110446 | Khoo et al. | Apr 2021 | A1 |
| 20210192645 | Kawamura et al. | Jun 2021 | A1 |
| 20210248535 | Ikui | Aug 2021 | A1 |
| 20210257847 | Takahashi | Aug 2021 | A1 |
| 20210261013 | Kazuno | Aug 2021 | A1 |
| 20210276449 | Kazuno | Sep 2021 | A1 |
| 20210376629 | Chen et al. | Dec 2021 | A1 |
| 20220001767 | Kim et al. | Jan 2022 | A1 |
| 20220021220 | Matsumoto et al. | Jan 2022 | A1 |
| 20220045546 | Ikui et al. | Feb 2022 | A1 |
| 20220230111 | Ikui | Jul 2022 | A1 |
| 20220261829 | Hidaka et al. | Aug 2022 | A1 |
| 20220305949 | Liu | Sep 2022 | A1 |
| 20230080952 | Okawa | Mar 2023 | A1 |
| 20230179026 | Daga | Jun 2023 | A1 |
| 20230417837 | Lee | Dec 2023 | A1 |
| 20240083394 | Zhang | Mar 2024 | A1 |
| 20240100987 | Lu | Mar 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 1211844 | Mar 1999 | CN |
| 101202777 | Jun 2008 | CN |
| 102129640 | Jul 2011 | CN |
| 104160546 | Nov 2014 | CN |
| 105493378 | Apr 2016 | CN |
| 205862454 | Jan 2017 | CN |
| 107026484 | Aug 2017 | CN |
| 107128194 | Sep 2017 | CN |
| 107599882 | Jan 2018 | CN |
| 107757408 | Mar 2018 | CN |
| 107945397 | Apr 2018 | CN |
| 0902521 | Mar 1999 | EP |
| 3018789 | May 2016 | EP |
| 10-293874 | Nov 1998 | JP |
| 11-098699 | Apr 1999 | JP |
| 11-150809 | Jun 1999 | JP |
| 2001-057711 | Feb 2001 | JP |
| 2001-283931 | Oct 2001 | JP |
| 2009-542190 | Nov 2009 | JP |
| 2010-212048 | Sep 2010 | JP |
| 2011-103048 | May 2011 | JP |
| 2011-146921 | Jul 2011 | JP |
| 2015-015827 | Jan 2015 | JP |
| 105667464 | Jun 2016 | JP |
| 2017-135922 | Aug 2017 | JP |
| 2019-068552 | Apr 2019 | JP |
| 2008005813 | Jan 2008 | WO |
| 2013080211 | Jun 2013 | WO |
| 2015001930 | Jan 2015 | WO |
| 20200111915 | Jun 2020 | WO |
| Entry |
|---|
| Chinese Office Action for Chinese patent Application No. 201980078213.7 mailed Dec. 1, 2023. |
| Japanese Office Action for Japanese Patent Application No. 2021-184277 mailed Nov. 21, 2023. |
| International Search Report and Written Opinion for International Application No. PCT/JP2019/046821 mailed on Mar. 3, 2020, 15 pages. |
| Japanese Notice of Allowance for Japanese Patent Application No. 2020-557858 mailed Oct. 12, 2021. |
| Extended European Search Report for European Patent Application No. 19891426.9 mailed Dec. 10, 2021. |
| Extended European Search Report for European Patent Application No. 19891426.9 mailed Apr. 8, 2022. |
| Japanese Decision to Grant a Patent for Japanese Patent Application No. 2020-557858 dated Oct. 12, 2021. |
| Japanese Decision to Grant a Patent for Japanese Patent Application No. 2021-184276 dated Apr. 19, 2022. |
| Non-Final Office Action for U.S. Appl. No. 17/296,566 mailed Sep. 22, 2022. |
| Number | Date | Country | |
|---|---|---|---|
| 20230365022 A1 | Nov 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17296566 | US | |
| Child | 18221514 | US |
