server
A server system manages software updates and lease agreements for energy storage devices in vehicles, addressing ownership changes by ensuring efficient utilization and maintenance convenience, and motivating new owners to enter into contracts, thus optimizing system efficiency.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-11-30
- Publication Date
- 2026-03-17
AI Technical Summary
The challenge of managing and updating software for energy storage devices in vehicles after a change in ownership, particularly when the device owner cannot identify the new owner, leading to ineffective utilization and potential misuse of the energy storage system.
A server system that communicates with vehicles to manage software updates and lease agreements, determining ownership changes through registered owner information and payment status, and incentivizes new owners to enter into lease and insurance contracts, using different communication modes for efficient software updates.
Ensures effective utilization of energy storage devices by ensuring software updates and maintenance convenience for new owners, preventing misuse, and motivating them to enter into lease and insurance agreements, thereby optimizing the system's efficiency.
Smart Images

Figure 0007831254000001 
Figure 0007831254000002 
Figure 0007831254000003
Abstract
Description
Technical Field
[0001] This disclosure relates to a server.
Background Art
[0002] Japanese Unexamined Patent Application Publication No. 2002-269407 (Patent Document 1) discloses a used car sales system.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] The OTA (Over The Air) function using wireless communication between a vehicle and a server has attracted attention. According to the OTA function, the vehicle updates the in-vehicle software by downloading new data from the server. The OTA function can eliminate the need for software maintenance by a dealer, thus improving the convenience for users. The server for providing the OTA function to the vehicle is operated by an operator such as a vehicle manufacturer.
[0005] The power storage device mounted on the vehicle has its own value and may be circulated separately from the vehicle. In this case, the owner of the power storage device is, for example, the above-mentioned operator and is distinguished from the owner of the vehicle. The owner of the vehicle typically enters into a lease contract with the owner of the power storage device to use the power storage device. The owner of the power storage device manages the power storage device based on the lease contract. This owner can recover and reuse the power storage device after the expiration of the lease contract. Therefore, the lease contract of the power storage device is preferable from the viewpoint of effective use of the power storage device.
[0006] A vehicle owner may transfer ownership of a vehicle equipped with an energy storage device to another person (the transferee) as a used vehicle. If the vehicle is transferred without the permission of the energy storage device owner, the vehicle's ownership changes, while the energy storage device owner may not be able to identify the transferee. As a result, the energy storage device owner cannot enter into a lease agreement with the transferee and cannot manage the energy storage device based on that lease agreement. This is undesirable from the perspective of effective utilization of the energy storage device.
[0007] This disclosure has been made in view of the above-mentioned issues, and its purpose is to provide a server that enables improved user convenience and effective use of energy storage devices installed in vehicles based on lease agreements. [Means for solving the problem]
[0008] The server in this disclosure is configured to communicate with a vehicle. The vehicle includes an energy storage device and a storage unit for storing software. The server comprises a communication device and a processing unit. The communication device is configured to communicate wirelessly with the vehicle. The processing unit is configured to perform an update process to update the software wirelessly. The first owner, as the owner of the vehicle, has a first lease agreement to lease the energy storage device. When ownership changes from the first owner to a second owner, and the second owner enters into a second lease agreement to lease the energy storage device, the processing unit permits the update process.
[0009] With the above configuration, renewal processing is permitted when a second owner enters into a lease agreement. This allows the in-vehicle software to be updated wirelessly, improving convenience for the second owner. As a result, it can incentivize the second owner to enter into a lease agreement. Therefore, the energy storage system can be effectively utilized based on the lease agreement.
[0010] The communication device may be configured to communicate with a first management server that stores registered owner information indicating the registered owner who is registered as the owner of the vehicle during the vehicle inspection. The processing device may obtain the registered owner information from the first management server via the communication device and determine whether or not the owner has changed according to the registered owner information.
[0011] If a vehicle is transferred without the permission of the battery storage device owner, the battery storage device owner may not be able to identify the transferee (the owner of the vehicle after the transfer). On the other hand, even after the vehicle has been transferred to the transferee, it is assumed that the vehicle will undergo periodic inspections. With the above configuration, the server can determine who the current registered owner of the vehicle is according to the registered owner information, and therefore can determine that the ownership of the vehicle has changed from the first owner to the second owner.
[0012] The communication device may be configured to communicate with a second management server. The second management server stores payment status information indicating the payment status of lease payments for the energy storage device. The lease payment is defined in the first lease agreement as the fee that the first owner is required to pay in order to lease the energy storage device. The processing device may obtain payment status information from the second management server via the communication device, and if the payment status information indicates non-payment of lease payments for a predetermined threshold period, it may obtain registered owner information.
[0013] If non-payment of lease fees continues for a period longer than the threshold, the first owner may have illegally transferred the vehicle to the second owner while the vehicle was equipped with a battery storage device. With the above configuration, if non-payment continues, the server retrieves payment status information. This allows the server to determine at the appropriate time that the vehicle's ownership has changed from the first owner to the second owner.
[0014] The processing device may acquire registered owner information at predetermined intervals. It is also desirable to periodically determine whether or not the vehicle's ownership has changed. With the above configuration, the server periodically retrieves registered owner information and can periodically determine whether or not the vehicle's ownership has changed.
[0015] If the processing unit determines that the ownership has been changed to a second owner, it may send a first notice to the vehicle via a communication device to prompt the second owner to enter into a second lease agreement.
[0016] By adopting the above configuration, it is possible to incentivize the second owner to enter into a second lease agreement. This enables the energy storage equipment leasing company to make effective use of the energy storage equipment.
[0017] The processing unit may determine that the second owner will enter into a second lease agreement when it receives a first approval signal through the communication device indicating that the second owner approves of the second lease agreement.
[0018] The processing unit may, if it determines that the second owner will enter into a second lease agreement, send a second notice to the vehicle via the communication device to prompt the second owner to enter into an insurance contract for the energy storage device.
[0019] By adopting the above configuration, it is possible to incentivize the second owner to take out an insurance contract in addition to the lease agreement. As a result, it is possible to avoid a situation where the vehicle is not effectively utilized after damage to the energy storage device.
[0020] If the second owner enters into an insurance contract, the processing unit may permit renewal processing. With the above configuration, renewal processing is permitted when the second owner enters into an insurance contract in addition to the lease agreement. This incentivizes the second owner to enter into an insurance contract in addition to the lease agreement.
[0021] When the processing device receives, through the communication device, a second approval signal indicating approval of the second owner's insurance contract, it may determine that the second owner has entered into an insurance contract.
[0022] The wireless communication mode may include a first communication mode and a second communication mode having a communication speed higher than that of the first communication mode. When the second owner enters into an insurance contract for the power storage device, the processing device may permit an update process in the second communication mode.
[0023] Since the second mode has a higher communication speed than the first mode, in the second mode, the update process is completed in a shorter time than in the first mode. With the above configuration, when the second owner enters into an insurance contract in addition to the lease contract, the update process in the second mode is permitted. As a result, the time required for the update process can be shortened. Consequently, it is possible to effectively motivate the second owner to enter into an insurance contract in addition to the lease contract.
[0024] When the processing device receives, through the communication device, a second approval signal indicating approval of the second owner's insurance contract, it may determine that the second owner has entered into an insurance contract.
[0025] The vehicle may be configured to communicate with a network. When permitting the update process, the processing device may permit the use of downloaded software by the second owner. The downloaded software is software downloaded from the network to the storage unit while the vehicle is being used by the first owner.
[0026] With the above configuration, even after the owner is changed from the first owner to the second owner, the downloaded software is continuously and effectively used by the second owner. As a result, the second owner can benefit. Consequently, it is possible to motivate the second owner to enter into a lease contract.
Advantages of the Invention
[0027] This disclosure makes it possible to improve user convenience and enable the effective use of energy storage devices based on lease agreements for energy storage devices installed in vehicles. [Brief explanation of the drawing]
[0028] [Figure 1] This diagram illustrates the configuration of the information processing system in the embodiment. [Figure 2] This diagram illustrates the data structure of the vehicle database. [Figure 3] This diagram illustrates the data structure of the vehicle inspection information database. [Figure 4] This diagram illustrates the problems that arise when a vehicle is transferred from user U1 to another person as a used car. [Figure 5] This is a diagram illustrating the characteristics of the server. [Figure 6] This diagram illustrates the screens displayed on the HMI unit. [Figure 7] This flowchart illustrates the processes performed by the server in the embodiment. [Figure 8] This diagram illustrates the data structure of the account information database. [Figure 9] This flowchart illustrates the process performed by the server in the modified example 1. [Figure 10] This flowchart illustrates the process performed by the server in the modified example 2. [Figure 11] This flowchart illustrates the process performed by the server in the modified example 3. [Figure 12] This flowchart illustrates the process performed by the server in the modified example 4. [Modes for carrying out the invention]
[0029] Embodiments of this disclosure will be described in detail below with reference to the drawings. The same or corresponding parts in the drawings will be denoted by the same reference numerals and their descriptions will not be repeated. Each of the embodiments and its modifications may be combined with one another as appropriate.
[0030] Figure 1 is a diagram illustrating the configuration of an information processing system in an embodiment. Referring to Figure 1, the information processing system 10 comprises a vehicle 100, a server 300, a vehicle inspection management server 400, and an account management server (bank server) 500.
[0031] Vehicle 100 is an electric vehicle and includes a base vehicle 102 and a battery 105. The base vehicle 102 is the remaining part of vehicle 100 excluding the battery 105 and is owned by user U1.
[0032] Battery 105 stores the power required to run vehicle 100. Battery 105 is an example of a “power storage device” in this disclosure. The owner of battery 105 is business operator ENT, which is distinct from the owner of base vehicle 102 (user U1). Business operator ENT is both the manufacturer of vehicle 100 and the leasing company of battery 105.
[0033] User U1 has a lease agreement with business operator ENT to lease battery 105. In addition, User U1 has an insurance contract with business operator ENT for battery 105. This insurance contract is intended to reduce the repair costs required to repair the battery 105 if it is damaged while User U1 is using vehicle 100.
[0034] If there is no insurance contract, user U1 may have to pay a large amount of repair costs when the battery 105 is damaged. As a result, user U1 may lose the motivation to use vehicle 100 (base vehicle 102) again. This is undesirable from the standpoint of effective use of base vehicle 102. On the other hand, according to the insurance contract, when the battery 105 is damaged, user U1 only has to pay a reduced repair cost. Therefore, it is possible to avoid a situation where the owner of vehicle 100 (vehicle owner) loses the motivation to use vehicle 100 due to damage to the battery 105. As a result, it is possible to avoid a situation where vehicle 100 is not effectively used after damage to the battery 105.
[0035] The base vehicle 102 includes a communication unit 120, a memory unit 130, a PCU (Power Control Unit) 132, a motor 133, an HMI (Human Machine Interface) unit 140, an auxiliary battery 145, and an ECU (Electronic Control Unit) 150.
[0036] The communication unit 120 includes communication modules 121-A and 121-B. Communication modules 121-A and 121-B communicate wirelessly with the server 300 by connecting to the network NW via wireless base stations WBS-4G and WBS-5G, respectively. Communication modules 121-A and 121-B download update data for the in-vehicle software (software SW, described later) from the server 300 to the vehicle 100 via wireless base stations WBS-4G and WBS-5G, respectively. This updates the in-vehicle software (OTA function).
[0037] The wireless base stations WBS-4G and WBS-5G are used for the fourth-generation (4G) and fifth-generation (5G) mobile communication systems, respectively. The modes of wireless communication between the vehicle 100 and the server 300 include a 4G communication mode and a 5G communication mode. In the 4G communication mode, communication module 121-A communicates with the server 300 through the wireless base station WBS-4G. In the 5G communication mode, communication module 121-B communicates with the server 300 through the wireless base station WBS-5G. The 5G communication mode has a higher communication speed than the 4G communication mode. In this embodiment, the vehicle 100 performs OTA functionality in the 4G communication mode. The 4G communication mode and the 5G communication mode are examples of the "first communication mode" and "second communication mode" of this disclosure, respectively.
[0038] The storage unit 130 stores software SW and downloaded software DLSW. Software SW is in-vehicle software, including the operating system (OS) installed in the vehicle 100 and various application software. This application software is installed by default when user U1 purchases the vehicle 100. Downloaded software DLSW is software (including various application software) downloaded to the storage unit 130 from the network NW while the vehicle 100 is being used by user U1.
[0039] The PCU132 includes a converter and an inverter (neither of which are shown). The PCU132 receives the discharged power from the battery 105, converts this discharged power into alternating current power, and supplies the converted power to the motor 133. This causes the motor 133 to rotate and the vehicle 100 to move.
[0040] The HMI unit 140 is a touchscreen that receives user input and displays various screens. The HMI unit 140 is operated, for example, when using the downloadable software DLSW. The auxiliary battery 145 stores power to drive the HMI unit 140 and other auxiliary components.
[0041] The ECU 150 controls various components of the vehicle 100, such as the communication unit 120, the PCU 132, the motor 133, and the HMI unit 140. The ECU 150 controls the charging and discharging of the battery 105 through the control of the PCU 132 (e.g., starting and stopping).
[0042] Server 300 is operated by the operator ENT and includes a communication device 310, a storage device 320, and a processing device 330. The communication device 310 communicates wirelessly with external devices (e.g., a vehicle 100) of Server 300 by communicating with a network NW. The communication device 310 is configured to communicate with the vehicle inspection management server 400 and the account management server 500, respectively, via the network NW.
[0043] The storage device 320 stores the vehicle database 322. The data structure of the vehicle database 322 will be explained in detail later.
[0044] The processing unit 330 provides the vehicle 100 with an OTA (Over-the-Air) function. Specifically, the processing unit 330 is configured to perform a software update process that updates the software SW via wireless communication between the server 300 and the vehicle 100. The software update process is performed periodically whenever a predetermined update timing arrives, as long as this process is permitted. In this embodiment, the processing unit 330 performs the software update process in 4G mode. Specifically, the server 300 transmits update data for updating the software SW to the vehicle 100 via the network NW and the wireless base station WBS-4G.
[0045] The vehicle inspection management server 400 is operated by an organization that manages vehicle inspections (e.g., a government agency or a used car dealership) and stores the vehicle inspection information DB 450. Vehicle inspections are performed for each of multiple vehicles, including vehicle 100.
[0046] The account management server 500 is operated by the bank and stores the account information DB 550. The account information DB 550 contains information on the bank accounts of multiple users who each use one of the multiple vehicles mentioned above.
[0047] The vehicle inspection information DB450 and the account information DB550 are accessed by the server 300 via the network NW. The data structures of the vehicle inspection information DB450 and the account information DB550 will be explained in detail later.
[0048] Figure 2 illustrates the data structure of the vehicle database 322. Referring to Figure 2, each of the multiple vehicles, including vehicle 100, is assigned a vehicle ID. The vehicle database 322 shows a user ID and the vehicle's communication address for each vehicle ID. This user ID indicates the identification information of the vehicle user and corresponds to the owner ID of the corresponding vehicle. The communication address is the address of the communication device of the corresponding vehicle (in the example of vehicle 100, the communication unit 120). In this example, the vehicle with vehicle ID 001 is vehicle 100, and the user with user ID 00A is user U1.
[0049] Figure 3 illustrates the data structure of the vehicle inspection information DB450. Referring to Figure 3, the vehicle inspection information DB450 includes registered owner information 460. Registered owner information 460 includes a registered owner ID. A registered owner is a person who is registered as the owner of a vehicle (in this example, vehicle 100) at the time of its vehicle inspection. In this example, the user with registered owner ID 00D is assumed to be user U2 (described later).
[0050] Figure 4 illustrates the problems that arise when vehicle 100 is transferred from user U1 to another person as a used car.
[0051] Referring to Figure 4, user U1 uses battery 105 by entering into a lease agreement C1 (and insurance agreement C11) with business operator ENT. Lease agreement C1 and insurance agreement C11 are, respectively, for user U 1 This is a lease and insurance agreement for battery 105 between the company and operator ENT. Operator ENT manages battery 105 based on lease agreement C1. Operator ENT may recover and reuse battery 105 after the expiration of lease agreement C1. Therefore, lease agreements for battery 105, such as lease agreement C1, are preferable from the viewpoint of effective utilization of battery 105.
[0052] User U1 may transfer vehicle 100 (base vehicle 102 and battery 105) to user U2 as a used vehicle without the permission of operator ENT. If vehicle 100 is transferred from user U1 to user U2, battery 105 will also be transferred without operator ENT's permission, and the vehicle owner will change from user U1 to user U2. On the other hand, operator ENT (owner of battery 105) may not be aware that battery 105 has been transferred without permission and that user U2 is the new vehicle owner (possessor of battery 105). Specifically, if the vehicle owner indicated by vehicle DB 322 remains user U1, server 300 may not be able to determine that the vehicle owner has changed. As a result, server 300 cannot determine the new vehicle owner (user U2). Therefore, operator ENT cannot enter into a lease agreement with user U2 and cannot manage battery 105 based on this lease agreement. This is undesirable from the standpoint of effective utilization of battery 105.
[0053] The server 300 according to this embodiment has features to address the above-mentioned problems. These features will be explained in detail below.
[0054] Figure 5 is a diagram illustrating the features of server 300. Referring to Figure 5, server 300 (processing device 330) permits the aforementioned software update process when the vehicle owner changes from user U1 to user U2, and user U2 enters into lease agreement C2 with operator ENT. Lease agreement C2 is an agreement for user U2 to lease battery 105 from operator ENT.
[0055] As described above, once the software update process is permitted, the vehicle 100's OTA function continues even after the vehicle owner changes from user U1 to user U2. As a result, the software SW can be updated via wireless communication between the vehicle 100 and the server 300 during user U2's period of use of the vehicle 100. Therefore, software maintenance by the dealer can be eliminated, improving the convenience for user U2. Consequently, user U2 can be incentivized to enter into a lease agreement C2. Therefore, if a lease agreement C2 is entered into, the battery 105 can be effectively utilized based on the lease agreement C2.
[0056] The following explains how server 300 determines a change in vehicle owner. First, server 300 obtains registered owner information 460 (registered owner ID) for vehicle 100 from vehicle inspection management server 400 (vehicle inspection information DB 450) via communication device 310. Then, server 300 determines whether the vehicle owner has changed from user U1 according to the registered owner information 460. Specifically, server 300 determines the user ID (00A) related to the vehicle ID (001) of vehicle 100 according to vehicle DB 322, and determines whether this user ID matches the registered owner ID for vehicle 100. If the user ID matches the registered owner ID, server 300 determines that the vehicle owner remains user U1 and has not changed. On the other hand, if these IDs are different, server 300 determines that the vehicle owner has changed from user U1 to user U2 (the user identified by the registered owner ID in vehicle inspection information DB 450).
[0057] Even after vehicle 100 is transferred to user U2, it is assumed that vehicle inspections will be conducted periodically for vehicle 100, and user U2 will be identified as the registered owner at the time of the inspection. As described above, server 300 determines whether or not the vehicle owner has changed based on the registered owner information 460. As a result, server 300 can appropriately determine (identify) the new vehicle owner (user U2).
[0058] The server 300 preferably acquires registered owner information 460 for the vehicle 100 at predetermined intervals. Information representing the predetermined period is stored in the storage device 320. The predetermined period is, for example, j days, k weeks, m months, or n years, where each of j, k, m, and n is a natural number of 1 or more.
[0059] It is also considered preferable to periodically determine whether or not the vehicle owner has changed. When the server 300 acquires the registered owner information 460 at predetermined intervals as described above, it can periodically determine whether or not the vehicle owner has changed.
[0060] When the server 300 determines that the vehicle owner has changed from user U1 to user U2, it sends a first notification NTF1 to the vehicle 100 to prompt user U2 to enter into a lease agreement C2. The first notification NTF1 is sent based on the address of the communication unit 120, which is included in the vehicle DB 322.
[0061] Server 300 may send a second notification NTF2 to vehicle 100 to prompt user U2 to enter into insurance contract C21. Insurance contract C21 is an insurance contract for battery 105 between user U2 and operator ENT. The second notification NTF2 is sent based on the address of the communication unit 120, which is included in vehicle DB 322. Insurance contract C21 reduces the repair costs required to repair damage to battery 105 if it is damaged while user U2 is using vehicle 100. The cases in which the second notification NTF2 is sent will be explained in Modification 2.
[0062] Figure 6 is an example of a screen displayed on the HMI unit 140. This screen is displayed when the vehicle 100 (communication unit 120) receives the first notification NTF1.
[0063] Referring to Figure 6, screen 142 includes message 144 and buttons 146 and 148. Message 144 informs user U2 that battery 105 is owned by operator ENT. Message 144 prompts user U2 to enter into a lease agreement C2 with operator ENT.
[0064] Button 146 is operated when user U2 enters into lease agreement C2. In response to the operation of button 146, the communication unit 120 sends a first approval signal to the server 300. The first approval signal indicates that user U2 approves of entering into lease agreement C2.
[0065] Button 148 is operated when user U2 does not enter into lease agreement C2. In response to the operation of button 148, the communication unit 120 sends a first disapproval signal to the server 300. The first disapproval signal indicates that user U2 does not enter into lease agreement C2. When the first disapproval signal is sent to the server 300, the server 300 performs charge / discharge limiting processing to limit the charging and discharging of battery 105.
[0066] The charge / discharge limiting process corresponds to the process of sending a command to the vehicle 100 to limit (in this example, stop) the control of the PCU 132 by the ECU 150. When this command is sent to the vehicle 100, the control of the PCU 132 by the ECU 150 stops. As a result, charging and discharging of the battery 105 is prohibited. This prevents the vehicle 100 from running using the power of the battery 105 even though user U2 does not have a lease agreement C2 (i.e., user U2 illegally driving the vehicle 100).
[0067] In this way, screen 142 is displayed in response to the first notification NTF1. This can motivate user U2 to enter into lease agreement C2. As a result, it becomes possible to enable the operator ENT to make effective use of battery 105 based on lease agreement C2.
[0068] Figure 7 is a flowchart illustrating the processes performed by the server 300 in this embodiment. Hereafter, steps will be abbreviated as "S".
[0069] Referring to Figure 7, the server 300 determines whether the predetermined period has elapsed since the registration owner information 460 was previously obtained (S105). If the predetermined period has not yet elapsed (NO in S105), S105 is repeated until the predetermined period has elapsed. If the predetermined period has elapsed (YES in S105), the process proceeds to S110.
[0070] Server 300 retrieves registered owner information 460 from the vehicle inspection management server 400 (vehicle inspection information DB 450) (S110). Server 300 determines whether the owner ID for vehicle 100 (user U1's ID) based on the vehicle DB 322 matches the registered owner ID in the registered owner information 460 (S115). If the owner ID matches the registered owner ID (YES in S115), Server 300 determines that the vehicle owner has not changed from user U1 (S125) and terminates the process. If the owner ID does not match the registered owner ID, i.e., it is different from the registered owner ID (NO in S115), Server 300 determines that the vehicle owner has changed from user U1 (S120). Server 300 then determines (identifies) the new owner (user U2) based on the registered owner ID. The process then proceeds to S135.
[0071] Server 300 sends a first notification NTF1 to vehicle 100 via communication device 310, prompting user U2 to enter into lease agreement C2 (S135). The process then proceeds to S140.
[0072] The server 300 determines whether or not to receive the aforementioned first approval signal from the vehicle 100 within a predetermined first approval period (S140). Information representing the first approval period is stored in the storage device 320. The first approval period is after the first notification NTF1 (S135) and is, for example, within i1 days from the time of transmission of the first notification NTF1 (i1 is a natural number).
[0073] If the server 300 receives the first approval signal within the first approval period (YES in S140), it determines that user U2 will enter into lease agreement C2 (S141). Next, the server 300 permits the software update process (S145) and terminates the process. Subsequently, the server 300 executes the software update process each time the aforementioned update timing arrives.
[0074] If the server 300 does not receive the first approval signal within the first approval period, for example, if it receives the first disapproval signal (NO in S140), it determines that user U2 will not enter into the lease agreement C2 (S142). Next, the server 300 performs processing to restrict the charging and discharging of the battery 105 (S146) and terminates the process. In this case, the software update process is not permitted, and the vehicle 100 does not perform OTA functions during the period in which user U2 uses the vehicle 100.
[0075] According to this embodiment, the battery 105 can be effectively utilized based on the lease agreement C2 while improving the convenience of the user U2.
[0076] [Example 1] Server 300 may acquire registered owner information 460 if the situation of non-payment of the lease fee for battery 105 continues for a predetermined threshold period. This lease fee is defined by lease agreement C1 as the fee that user U1 is required to pay in order to lease battery 105. Information representing the threshold period is stored in storage device 320. The threshold period is, for example, e days, f weeks, g months, or h years, where e, f, g, and h are each natural numbers of 1 or greater.
[0077] Figure 8 illustrates the data structure of the account information DB 550. As mentioned above, the account information DB 550 is stored on the account management server 500.
[0078] Referring to Figure 8, the account information DB 550 includes payment status information 554. Payment status information 554 shows the payment status of lease payments by user U1 (specifically, whether or not the lease payments have already been debited) on a monthly basis. In this example, the threshold period is assumed to be 3 months. Payment status information 554 shows that user U1 has not paid lease payments over the threshold period (3 months from February to April).
[0079] Server 300 obtains payment status information 554 from the account management server 500 (account information DB 550) via the communication device 310. In this example, Server 300 determines that the payment status information 554 indicates non-payment of lease fees over a threshold period. Based on this determination, Server 300 obtains registered owner information 460.
[0080] If the non-payment of lease fees continues for a period longer than the threshold, user U1 may have already disappeared after illegally transferring vehicle 100 (base vehicle 102 and battery 105) to user U2. In this modified example 1, server 300 retrieves registered owner information 460 triggered by non-payment of lease fees by user U1. As a result, server 300 can determine the new vehicle owner (user U2) based on the registered owner information 460. Therefore, server 300 can determine at the appropriate time that the vehicle owner has changed from user U1 to user U2.
[0081] Figure 9 is a flowchart illustrating the processing performed by the server 300 in this modified example 1. Referring to Figure 9, this flowchart differs from the flowchart of the previously described embodiment (Figure 7) in that S202 is added and S205 is executed instead of S105. S210 to S246 are the same as S110 to S146, respectively. This flowchart is executed, for example, at the predetermined intervals mentioned above.
[0082] Server 300 obtains payment status information 554 from account management server 500 (account information DB 550) via communication device 310 (S202). Server 300 determines whether the payment status information 554 indicates non-payment of lease fees over a threshold period (S205). If the payment status information 554 indicates non-payment of lease fees over a threshold period (YES in S205), the process proceeds to S210. Otherwise (NO in S205), the process terminates.
[0083] According to Modification 1, the server 300 can determine at the appropriate time that the vehicle owner has changed from user U1 to user U2. As a result, the number of times the server 300 accesses the vehicle inspection management server 400 to obtain the registered owner information 460 can be minimized.
[0084] [Differentiation 2] Server 300 may permit software update processing if user U2 enters into an insurance contract C21 in addition to the lease contract C2. Specifically, Server 300 (processing device 330) permits software update processing when it receives a second approval signal from vehicle 100 via communication device 310 indicating that user U2 approves of entering into the insurance contract C21.
[0085] With the above configuration, when user U2 enters into an insurance contract C21 in addition to the lease contract C2, the software update process is permitted (OTA functionality continues). This incentivizes user U2 to enter into an insurance contract C21 in addition to the lease contract C2. As a result, in the event of battery 105 damage, user U2 only needs to pay the reduced repair costs. Therefore, it is possible to avoid a situation where user U2 loses motivation to use vehicle 100 due to battery 105 damage. Therefore, it is possible to avoid a situation where the base vehicle 102 is not effectively utilized after battery 105 failure.
[0086] User U2 can decide whether or not to approve insurance contract C21 using the HMI unit 140. Specifically, in response to receiving the second notification NTF2 (Figure 5), the HMI unit 140 displays an inquiry screen (not shown) to ask user U2 whether or not to approve insurance contract C21, and user U2 decides whether or not to approve insurance contract C21 by operating this screen. If user U2 performs the operation to approve insurance contract C21, the communication unit 120 sends the aforementioned second approval signal to the server 300. If user U2 does not perform the operation to approve insurance contract C21, the communication unit 120 sends a second disapproval signal to the server 300. The second disapproval signal indicates that user U2 will not enter into insurance contract C21.
[0087] Figure 10 is a flowchart illustrating the processing performed by the server 300 in this modified example 2. Referring to Figure 10, this flowchart differs from the flowchart of the previously described embodiment (Figure 7) in that S343, S344, S344A, and S344B are added. S305 to S342, S345, and S346 are the same as S105 to S142, S145, and S146, respectively.
[0088] After S341, the server 300 sends a second notification NTF2 to the vehicle 100 via the communication device 310, prompting user U2 to enter into insurance contract C21 (S343). The process then proceeds to S344.
[0089] The server 300 determines whether or not it will receive the aforementioned second approval signal from the vehicle 100 via the communication device 310 within the second approval period (S344). Information representing the second approval period is stored in the storage device 320. The second approval period is after the second notification NTF2 (S343) and is, for example, within i2 days from the time of transmission of the second notification NTF2 (i2 is a natural number). If the server 300 receives the second approval signal within the second approval period (YES in S344), it determines that user U2 will enter into insurance contract C21 (S344A). The process then proceeds to S345. If the server 300 does not receive the second approval signal within the second approval period, for example, if it receives the second disapproval signal (NO in S344), it determines that user U2 will not enter into insurance contract C21 (S344A) and terminates the process.
[0090] According to Modification 2, it is possible to avoid a situation where the vehicle 100 (base vehicle 102) is not effectively utilized after the battery 105 fails.
[0091] [Difference 3] In this modified example 3, when the server 300 obtains a second approval signal through the communication device 310 (i.e., when user U2 enters into an insurance contract C21), it authorizes the software update process using 5G communication mode. After authorizing this process, the server 300 executes the software update process using 5G mode whenever an update timing arrives. Specifically, the server 300 transmits update data for updating the software SW to the vehicle 100 via the network NW and the wireless base station WBS-5G (Figure 1).
[0092] Because 5G mode has a higher communication speed than 4G mode, software update processing is completed in 5G mode in a shorter time than in 4G mode. According to this modified example 3, when user U2 enters into an insurance contract C21 in addition to a lease contract C2, software update processing using 5G mode is permitted. This reduces the time required for software update processing (OTA function). As a result, user U2 can be effectively motivated to enter into an insurance contract C21 in addition to a lease contract C2. Thus, it is possible to avoid a situation where the owner of vehicle 100 (vehicle owner) loses motivation to use vehicle 100 due to damage to battery 105. Consequently, it is possible to avoid a situation where the base vehicle 102 is not effectively utilized after damage to battery 105.
[0093] Figure 11 is a flowchart illustrating the processing performed by the server 300 in this modified example 3. Referring to Figure 11, this flowchart differs from the flowchart of the modified example 2 (Figure 10) in that S445 is executed in place of S345, and S447 is added. S405~S444, S444A, S444B, and S446 are the same as S305~S344, S344A, S344B, and S346, respectively.
[0094] If user U2 enters into insurance contract C21 (after S444A), server 300 permits software update processing via 5G mode (S445). If user U2 does not enter into insurance contract C21 (after S444B), server 300 permits software update processing via 4G mode (S447). After S445 and S447, processing ends.
[0095] According to this modified example 3, similar to modified example 2, it is possible to avoid a situation where the vehicle 100 (base vehicle 102) cannot be effectively utilized after the battery 105 is damaged.
[0096] [Differentiation Example 4] The server 300 (processing unit 330) may allow user U2 to use the downloaded software DLSW if user U2 enters into a lease agreement C2, that is, if user U2 permits software update processing. As mentioned above, the downloaded software DLSW is software downloaded to the storage unit 130 during the period of use of the vehicle 100 by user U1.
[0097] With this configuration, even after the vehicle owner changes from User U1 to User U2, the downloaded software DLSW can continue to be used and effectively utilized by User U2 (preferably free of charge). This benefits User U2. As a result, User U2 can be incentivized to enter into a lease agreement C2.
[0098] Furthermore, if user U2 does not enter into a lease agreement C2, server 300 will erase the downloaded software DLSW from storage unit 130 via wireless communication.
[0099] Figure 12 is a flowchart illustrating the processing performed by the server 300 in this modified example 4. Referring to Figure 12, this flowchart differs from the flowchart of the embodiment (Figure 7) in that S557 and S559 are added. S505 to S546 are the same as S105 to S146, respectively.
[0100] If user U2 does not enter into lease agreement C2 (after S542), server 300 erases the downloaded software DLSW from storage unit 130 via wireless communication after limiting the charging and discharging of battery 105 (after S546) (S559). If user U2 enters into lease agreement C2 (after S541), server 300 allows user U2 to continue using the downloaded software DLSW after permitting the software update process (after S545) (S557). Specifically, server 300 does not erase the downloaded software DLSW from storage unit 130, but uses HMI unit 140 to start the downloaded software DLSW when instructed to do so by user U2. After S557 and S559, the process ends.
[0101] According to this modified version 4, user U2 can be motivated to enter into a lease agreement C2. Therefore, the effective utilization of battery 105 can be more easily achieved.
[0102] [Other variations] Server 300 may determine that the vehicle owner has changed when it receives an ownership change notification from vehicle 100 indicating that the vehicle owner has changed from user U1 to user U2.
[0103] When the server 300 determines that the vehicle owner has changed, it may restrict the charging and discharging of the battery 105 before receiving the first approval signal (for example, after S120 in Figure 7 and before YES in S140, S146 may be executed). This immediately restricts the charging and discharging of the battery 105 after the determination of a change in vehicle owner. As a result, it is possible to prevent user U2 from illegally using the battery 105 without the lease agreement C2 (illegally driving the vehicle 100) before receiving the first approval signal. Even if the charging and discharging of the battery 105 is immediately restricted before receiving the first approval signal as described above, the HMI unit 140 will still use the power of the auxiliary battery 145 to display the screen 142.
[0104] In the above, 4G communication mode and 5G communication mode were used as examples of the "first communication mode" and "second communication mode" of this disclosure, respectively. However, as long as the wireless communication between the server 300 and the vehicle 100 includes multiple communication modes, and the second communication mode among the multiple communication modes has a higher communication speed than the first communication mode, the first communication mode is not limited to 4G mode, and the second communication mode is not limited to 5G mode.
[0105] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the claims rather than by the foregoing description, and all modifications within the meaning and scope of equivalents of the claims are intended. [Explanation of Symbols]
[0106] 10 Information processing system, 100 Vehicle, 102 Base vehicle, 105 Battery, 120 Communication unit, 130 Storage unit, 300 Server, 310 Communication device, 320 Storage device, 330 Processing unit, 400 Vehicle inspection management server, 500 Account management server.
Claims
1. A server configured to communicate with a vehicle which includes an energy storage device and a storage unit for storing software, A communication device configured to perform wireless communication with the aforementioned vehicle, The system includes a processing unit configured to perform an update process for updating the software via wireless communication, The aforementioned processing apparatus is If the owner of the vehicle does not enter into a lease agreement to lease the energy storage device, the renewal process will not be permitted. A server that, when the aforementioned owner enters into the aforementioned lease agreement, permits the aforementioned renewal process.
2. The server according to claim 1, wherein the processing device determines that the owner will enter into the lease agreement when it receives a first approval signal through the communication device indicating that the owner approves of entering into the lease agreement.
3. The server according to claim 1, wherein the processing device transmits a notification to the vehicle via the communication device to prompt the owner to enter into an insurance contract for the energy storage device when the owner determines that the owner will enter into the lease agreement.
4. The server according to claim 3, wherein the processing device determines that the owner will enter into the insurance contract when it receives a second approval signal through the communication device indicating that the owner approves of the owner entering into the insurance contract.
5. The modes of wireless communication include a first communication mode and a second communication mode having a higher communication speed than the first communication mode. The server according to claim 1, wherein the processing device permits the update process in the second communication mode when the owner enters into an insurance contract for the energy storage device.
6. The server according to claim 5, wherein the processing device determines that the owner will enter into the insurance contract when it receives a second approval signal through the communication device indicating that the owner approves of entering into the insurance contract.
Citation Information
Patent Citations
System and method for selling used car with insurance using network
JP2002269407A
Remote service system for vehicle
JP2007280021A
Common battery management system for driving vehicle
JP2011096233A
Data management device, data management method, and data communication system
JP2019075134A
Battery management system, battery management method, and program
JP2022175977A