Vehicle management system and electric vehicle

Abstract

A vehicle management system is applied to an electric vehicle that uses an electric motor as a power device for running. The vehicle management system generates a sound, and outputs the sound through a speaker mounted on the electric vehicle. The vehicle management system acquires driving state information indicating a driving state of the electric vehicle. The vehicle management system acquires an aggressive driving degree indicating a degree of safe driving and / or energy-saving driving of the electric vehicle, based on the driving state information. The vehicle management system changes the sound and / or changes an option of the sound in accordance with the aggressive driving degree.

Description

Technical Field

[0001] This disclosure relates to electric vehicles in which an electric motor is used as a power source for driving. Background Technology

[0002] Patent Document 1 discloses a sound control device mounted on a vehicle capable of being driven by an electric motor. The sound control device displays the engine sound generated during gear shifting in a motor-driven vehicle in real time.

[0003] Existing technical documents

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent Application Publication No. 2011-215437 Summary of the Invention

[0006] The problem that the invention aims to solve

[0007] Safe / energy-efficient driving is preferred for traffic flow and the environment. However, in reality, there are drivers who are inclined to actively practice safe / energy-efficient driving, and there are drivers who are not. When there is no difference in their approaches, the motivation for safe / energy-efficient driving may decrease. In the aforementioned Patent Document 1, safe / energy-efficient driving is not considered at all.

[0008] Methods for solving problems

[0009] The first point concerns a vehicle management system applied to electric vehicles that use electric motors as the power source for driving.

[0010] The vehicle management system has one or more processors.

[0011] One or more processors generate sound, which is then output through speakers mounted on an electric vehicle.

[0012] One or more processors acquire driving status information representing the driving status of the electric vehicle.

[0013] One or more processors obtain an active driving level that represents the degree of safe and / or energy-efficient driving of an electric vehicle based on driving state information.

[0014] One or more processors have the option to change the sound and / or change the sound based on the level of active driving.

[0015] The second viewpoint concerns electric vehicles that use electric motors as the power source for driving.

[0016] Electric vehicles have one or more processors.

[0017] One or more processors generate sound, which is then output through speakers mounted on an electric vehicle.

[0018] One or more processors acquire driving status information representing the driving status of the electric vehicle.

[0019] One or more processors obtain an active driving level that represents the degree of safe and / or energy-efficient driving of an electric vehicle based on driving state information.

[0020] One or more processors have the option to change the sound and / or change the sound based on the level of active driving.

[0021] The third perspective concerns vehicle management systems applied to electric vehicles that use electric motors as the power source for driving.

[0022] Electric vehicles have a simulation mode that simulates the driving characteristics of virtual vehicles.

[0023] The vehicle management system has one or more processors.

[0024] One or more processors acquire driving status information representing the driving status of the electric vehicle.

[0025] One or more processors obtain an active driving level that represents the degree of safe and / or energy-efficient driving of an electric vehicle based on driving state information.

[0026] One or more processors can vary the options for virtual vehicles that can be used in simulation mode, depending on the level of active driving.

[0027] Invention Effects

[0028] According to the first and second viewpoints, sound is output through a speaker mounted on the electric vehicle. Furthermore, the sound changes and / or the sound options change according to the level of active driving, which indicates the degree of safe / energy-efficient driving of the electric vehicle. Drivers engaging in safe / energy-efficient driving can enjoy these changes in sound and / or sound options. These changes in sound and / or sound options can also be seen as a privilege or reward given to drivers engaging in safe / energy-efficient driving. Drivers engaging in safe / energy-efficient driving feel satisfied with the privilege or reward given to them. This becomes an incentive for safe / energy-efficient driving. As a result, safe / energy-efficient driving is promoted.

[0029] According to the third perspective, electric vehicles possess a simulation mode that mimics the driving characteristics of a virtual vehicle. Furthermore, the virtual vehicle options available in the simulation mode change based on the level of active driving, representing the degree of safe / energy-efficient driving of the electric vehicle. Drivers engaging in safe / energy-efficient driving can enjoy these changing virtual vehicle options. These changing virtual vehicle options can also be seen as privileges and rewards given to drivers engaging in safe / energy-efficient driving. Drivers engaging in safe / energy-efficient driving feel satisfied with these privileges and rewards, thus becoming an incentive for safe / energy-efficient driving. As a result, safe / energy-efficient driving is promoted. Attached Figure Description

[0030] Figure 1 This is a conceptual diagram representing electric vehicles and vehicle management systems.

[0031] Figure 2 This is a block diagram illustrating an example of the basic functional structure of a vehicle management system.

[0032] Figure 3 This is a block diagram representing other examples of the basic functional structure of a vehicle management system.

[0033] Figure 4 This is a concept diagram used to illustrate an overview of sound management that takes into account safe driving / energy-saving driving.

[0034] Figure 5 This is a block diagram illustrating an example of the functional structure of a vehicle management system.

[0035] Figure 6 These are conceptual diagrams illustrating various examples of benchmarks used to explain the degree of active driving.

[0036] Figure 7 This is a block diagram illustrating an example of the functional structure of the engine sound generation unit.

[0037] Figure 8 This is another block diagram illustrating the functional structure of a vehicle management system.

[0038] Figure 9 This is another example of a block diagram illustrating the functional structure of a vehicle management system.

[0039] Figure 10 This is a block diagram used to illustrate the vehicle-mounted device and the management server.

[0040] Figure 11 This is a block diagram used to illustrate the first example of how a vehicle management system is used.

[0041] Figure 12 This is a block diagram illustrating the second example of how a vehicle management system is used.

[0042] Figure 13 This is a block diagram used to illustrate the third example of how a vehicle management system is used.

[0043] Figure 14 This is the fourth example of a block diagram used to illustrate how a vehicle management system is used.

[0044] Figure 15 This is a block diagram representing a first structural example of the power control system of an electric vehicle.

[0045] Figure 16 This is a diagram showing examples of the engine model, clutch model, and transmission model that make up the MT vehicle model.

[0046] Figure 17 This is a graph showing the torque characteristics of the electric motor achieved through electric motor control using the MT vehicle model.

[0047] Figure 18 This is a block diagram representing a second structural example of the power control system for an electric vehicle.

[0048] Figure 19 This is another example of a block diagram illustrating the functional structure of a vehicle management system. Detailed Implementation

[0049] The embodiments of this disclosure will be described with reference to the accompanying drawings.

[0050] 1. Electric vehicles and vehicle management systems

[0051] Figure 1 This is a conceptual diagram illustrating the electric vehicle 10 and the vehicle management system 100 according to this embodiment. The electric vehicle 10 includes an electric motor 44. Examples of electric motors 44 include a brushless DC motor and a three-phase AC synchronous motor. The electric vehicle 10 uses the electric motor 44 as a power unit for driving.

[0052] In addition, the electric vehicle 10 is equipped with various sensors 11. These sensors 11 detect the driving status of the electric vehicle 10. Examples of these sensors 11 include accelerator position sensors, brake position sensors, steering angle sensors, steering torque sensors, wheel speed sensors, acceleration sensors, speed sensors, position sensors, and recognition sensors. The accelerator position sensor detects the amount of accelerator pedal operation. The brake position sensor detects the amount of brake pedal operation. The steering angle sensor detects the steering angle of the steering wheel. The steering torque sensor detects the steering torque of the steering wheel. The wheel speed sensors detect the rotational speed of the wheels of the electric vehicle 10. The acceleration sensors detect the lateral acceleration and longitudinal acceleration of the electric vehicle 10. The rotational speed sensor detects the rotational speed of the electric motor 44. The position sensors detect the position of the electric vehicle 10. An example of a position sensor is a GNSS (Global Navigation Satellite System) sensor. The recognition sensor is used to identify (detect) the surrounding conditions of the electric vehicle 10. Examples of recognition sensors include cameras, LiDAR (Light Detection and Ranging), and radar.

[0053] Furthermore, the electric vehicle 10 is equipped with one or more speakers 70. For example, the speaker 70 is an interior speaker that outputs sound into the interior of the electric vehicle 10. As another example, the speaker 70 may also be an exterior speaker that outputs sound into the exterior of the electric vehicle 10. The electric vehicle 10 may also have both interior and exterior speakers.

[0054] The vehicle management system 100 is applied to and manages the electric vehicle 10. The entire vehicle management system 100 can also be integrated into the electric vehicle 10. As another example, at least a portion of the vehicle management system 100 can be contained in a management server external to the electric vehicle 10. In this case, the vehicle management system 100 can also remotely manage the electric vehicle 10. As yet another example, the vehicle management system 100 can also be distributed across the electric vehicle 10 and the management server.

[0055] Generally, a vehicle management system 100 includes one or more processors 101 (hereinafter referred to as processor 101) and one or more storage devices 102 (hereinafter referred to as storage device 102). The processor 101 performs various processes. Examples of processors 101 include general-purpose processors, dedicated processors, central processing units (CPUs), graphics processing units (GPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), integrated circuits, conventional circuits, and / or combinations thereof. The processor 101 may also be referred to as a circuitry or processing circuitry. A circuitry is hardware programmed to implement or perform functions. The storage device 102 stores (saves) various information. Examples of storage devices 102 include volatile memory, non-volatile memory, HDDs (hard disk drives), SSDs (solid state drives), etc. The functions of the vehicle management system 100 are realized through the cooperation of the processor 101 and the storage device 102.

[0056] One or more vehicle management programs 105 (hereinafter referred to as vehicle management programs 105) are computer programs executed by processor 101. The functions of the vehicle management system 100 can also be implemented through the cooperation of processor 101 executing vehicle management programs 105 and storage device 102. Vehicle management programs 105 are stored in storage device 102. Alternatively, vehicle management programs 105 can also be recorded on a computer-readable recording medium.

[0057] For example, the vehicle management system 100 has the function of a sound management system for managing sounds related to the electric vehicle 10. In particular, the vehicle management system 100 generates and manages the sound output from the speaker 70 mounted on the electric vehicle 10. Furthermore, the vehicle management system 100 outputs the generated sound through the speaker 70 mounted on the electric vehicle 10.

[0058] For example, the vehicle management system 100 generates a "simulated engine sound" that mimics the engine sound of a motorized vehicle. Furthermore, the vehicle management system 100 outputs the simulated engine sound through a speaker 70 mounted on the electric vehicle 10. Additionally, a motorized vehicle refers to a vehicle equipped with an engine (internal combustion engine) and using the engine as a power unit for propulsion.

[0059] The sound output from speaker 70 is not limited to simulated engine sounds. For example, the sound could also be simulated driving sounds that mimic the driving sounds of a moving body other than a car (e.g., a tram, an airplane, etc.). As another example, the sound could be navigation voice. As yet another example, the sound could be music.

[0060] In the following description, as an example, "analog engine sound" is considered as the sound output from speaker 70. However, this disclosure can also be applied to other sounds. In general, "analog engine sound" and "engine sound" in the following description will be replaced with "sound".

[0061] Figure 2 This is a block diagram illustrating an example of the basic functional structure of a vehicle management system 100. The vehicle management system 100 includes a driving status acquisition unit 110, an audio source data management unit 120, an engine sound generation unit 130, and an output unit 140 as functional blocks. These functional blocks can also be implemented, for example, through the cooperation of a processor 101 executing a vehicle management program 105 and a storage device 102.

[0062] The driving state acquisition unit 110 acquires driving state information (DRV) indicating the driving state of the electric vehicle 10. The driving state information DRV includes information related to the driver's driving operations, information related to the driving state of the electric vehicle 10, and information related to the surrounding conditions of the electric vehicle 10. Typically, the driving state information DRV includes information detected by sensors 11 mounted on the electric vehicle 10. For example, the driving state information DRV includes the amount of accelerator pedal operation (accelerator opening), the amount of brake pedal operation (brake opening), steering angle, steering speed, steering torque, wheel speed, vehicle speed, front-rear acceleration, lateral acceleration, and the rotational speed of the electric motor 44. The driving state information DRV may also include the position of the electric vehicle 10. The driving state information DRV may also include the surrounding conditions of the electric vehicle 10 identified (detected) by identification sensors.

[0063] Furthermore, the operating status information DRV includes the virtual engine speed Ne. Here, it is assumed that the electric vehicle 10 uses a virtual engine as its driving power unit. The virtual engine speed Ne is assumed to be the speed of the virtual engine when the electric vehicle 10 is driven by the virtual engine. For example, the operating status acquisition unit 110 can also calculate the virtual engine speed Ne in a manner that increases with the wheel speed. In addition, when the electric vehicle 10 has a manual mode (MT mode) as described later, the driving status acquisition unit 110 can also calculate the virtual engine speed Ne in manual mode based on the wheel speed, the combined reduction ratio, and the slip ratio of the virtual clutch. Details of the calculation method for the virtual engine speed Ne in manual mode will be described later.

[0064] The sound source data management unit 120 stores and manages the basic sound source data 200 used to generate simulated engine sounds. The sound source data management unit 120 is primarily implemented by one or more storage devices 102. Typically, the basic sound source data 200 includes various types of sound source data. These various types of sound source data include, for example, sound source data for sounds caused by engine combustion (for low speed, medium speed, and high speed), sound source data for sounds caused by drive systems such as gears (for low speed, medium speed, and high speed), noise sound source data, and sound source data for event sounds (e.g., creaking sounds, engine stop sounds), etc. Each sound source data is pre-generated through simulations based on engine models and vehicle models of an engine vehicle. Each sound source data can be flexibly adjusted; that is, at least one of the sound pressure level and frequency of the sound represented by the sound source data can be flexibly adjusted.

[0065] The engine sound generation unit 130 (engine sound simulator) is a simulator that generates simulated engine sounds. The engine sound generation unit 130 obtains at least a portion of the operating state information DRV from the operating state acquisition unit 110. Specifically, the engine sound generation unit 130 obtains information about the virtual engine speed Ne and vehicle speed from the operating state acquisition unit 110. Additionally, the engine sound generation unit 130 reads basic sound source data 200 from the sound source data management unit 120. Furthermore, the engine sound generation unit 130 generates simulated engine sounds corresponding to the operating state (virtual engine speed Ne, vehicle speed) of the electric vehicle 10 by combining one or more sound source data included in the basic sound source data 200. Engine sound data ES is data representing the generated simulated engine sound.

[0066] Furthermore, the generation of simulated engine sounds is a well-known technique and is not particularly limited in this embodiment. For example, simulated engine sounds can also be generated using well-known engine sound simulators used in games, etc. Alternatively, a method can be employed that includes a virtual engine speed Ne-frequency mapping and a virtual engine torque-sound pressure mapping, where the frequency of the simulated engine sound is increased or decreased proportionally to the virtual engine speed Ne, and the sound pressure is increased or decreased proportionally to the virtual engine torque.

[0067] The output unit 140 receives engine sound data ES generated by the engine sound generation unit 130. Furthermore, based on the engine sound data ES, the output unit 140 outputs analog engine sound through the speaker 70.

[0068] Figure 3 This is a block diagram illustrating other examples of the basic functional structure of a vehicle management system 100. Figure 3In the example shown, the audio source data management unit 120 stores and manages various basic audio source data 200 (200-A, 200-B, 200-C, etc.) corresponding to multiple vehicle models (A, B, C, etc.). That is, the audio source data management unit 120 stores and manages the basic audio source data 200 for each vehicle model. Each basic audio source data 200 is pre-generated based on the engine model and vehicle model of the corresponding vehicle model. The driver can also specify their preferred vehicle model from among the multiple models. In this case, the engine sound generation unit 130 retrieves the basic audio source data 200 corresponding to the vehicle model specified by the driver. Then, the engine sound generation unit 130 uses the retrieved basic audio source data 200 (e.g., basic audio source data 200-B corresponding to vehicle model B) to generate a simulated engine sound. Thus, the driver can experience the feeling of driving their preferred vehicle model.

[0069] If Figure 3 The example shown can be generalized to suggest that there are multiple options for the sounds being simulated. For instance, multiple options could include simulated engine sounds for different car models. As other examples, multiple options could also include simulated drive sounds for various virtual moving objects (e.g., vehicles, trams, airplanes). In short, the driver can choose their preferred sound from multiple options.

[0070] 2. Sound management for safe / energy-efficient driving has been considered.

[0071] 2-1. Overview

[0072] Safe driving / energy-efficient driving is preferred for traffic flow and the environment (in this specification, " / " means and / or). However, in reality, there are drivers who are inclined to actively practice safe driving / energy-efficient driving, and there are drivers who are not. When there is no difference in their approach, the motivation for safe driving / energy-efficient driving may decrease. Therefore, this embodiment proposes a technology that can promote safe driving / energy-efficient driving.

[0073] Figure 4 This is a conceptual diagram used to illustrate an overview of sound management considering safe driving / energy-saving driving. According to this embodiment, an "active driving level POS" is used to represent the degree of safe driving / energy-saving driving of the electric vehicle 10. The vehicle management system 100 can obtain the active driving level POS based on the driving state information DRV described above. Specific examples of obtaining the active driving level POS will be described later.

[0074] Furthermore, the vehicle management system 100 changes the simulated engine sound output from the speaker 70 according to the active driving level POS. For example, the vehicle management system 100 increases the audibility of the simulated engine sound as the active driving level POS increases. As another example, the vehicle management system 100 may also reduce the noise component in the simulated engine sound as the active driving level POS increases. As yet another example, the vehicle management system 100 may also reduce the "roaring" sound of the simulated engine sound as the active driving level POS increases. As yet another example, the vehicle management system 100 may also increase the sound pressure level of the simulated engine sound as the active driving level POS increases. As yet another example, the vehicle management system 100 may also improve the sound quality of the simulated engine sound as the active driving level POS increases. When changing the simulated engine sound according to the active driving level POS, the simulated engine sound may also be changed from a default sound. Here, the default sound is the normal sound without considering the active driving level POS.

[0075] As another example, the vehicle management system 100 can also change the option for simulated engine sound based on the level of active driving (POS) (see [reference]). Figure 3 For example, the vehicle management system 100 increases the option to simulate engine sound as the active driving level POS increases. While the option to simulate engine sound is changed according to the active driving level POS, it can also be changed from the default option. Here, the default option is the normal option when the active driving level POS is not considered.

[0076] As another example, the vehicle management system 100 can also change the simulated engine sound and the options for the simulated engine sound based on the level of active driving (POS).

[0077] Thus, according to this embodiment, the simulated engine sound changes and / or the option to simulate the engine sound changes based on the active driving level POS, which indicates the degree of safe / energy-efficient driving. Drivers engaging in safe / energy-efficient driving can enjoy these changes in the simulated engine sound and / or the option to simulate the engine sound. These changes in the simulated engine sound and / or the option to simulate the engine sound can also be seen as a privilege or reward given to drivers engaging in safe / energy-efficient driving. Drivers engaging in safe / energy-efficient driving feel satisfied with the privilege or reward given to them. This becomes an incentive for safe / energy-efficient driving. As a result, safe / energy-efficient driving is promoted. The promotion of safe / energy-efficient driving is also beneficial for traffic flow and the environment.

[0078] As the Active Driving Level (POS) increases, the audibility of the simulated engine sound also increases. Furthermore, the noise or unwanted sound components in the simulated engine sound can decrease. Alternatively, the "roar" of the simulated engine sound may be reduced. The sound quality of the simulated engine sound can also improve as the Active Driving Level (POS) increases. This provides a strong incentive for safe / fuel-efficient driving for drivers who want to enjoy the simulated engine sound. Consequently, it further promotes safe / fuel-efficient driving.

[0079] As the Active Driving Level (POS) increases, the option to simulate engine sounds also increases. This provides a strong incentive for drivers who want to enjoy simulated engine sounds, thus further promoting safe and fuel-efficient driving.

[0080] The following details the Active Driving POS and specific examples of its voice management.

[0081] 2-2. Specific examples of active driving

[0082] Figure 5 This is a block diagram illustrating an example of the functional structure of the vehicle management system 100 according to this embodiment. The vehicle management system 100, in addition to... Figure 2 In addition to the functional blocks shown, an active driving level acquisition unit 150 is also included. These functional blocks can also be implemented through the cooperation of the processor 101 executing the vehicle management program 105 and the storage device 102.

[0083] As described above, the driving state acquisition unit 110 acquires driving state information (DRV) indicating the driving state of the electric vehicle 10. The driving state information (DRV) includes information related to the driver's driving operations, information related to the driving state of the electric vehicle 10, and information related to the surrounding conditions of the electric vehicle 10. The active driving level acquisition unit 150 receives the driving state information (DRV) from the driving state acquisition unit 110. Furthermore, based on the driving state information (DRV), the active driving level acquisition unit 150 acquires an active driving level (POS) indicating the degree of safe driving / energy-saving driving of the electric vehicle 10.

[0084] Figure 6 This is a conceptual diagram illustrating various examples of benchmarks used to explain Active Driving Level (POS). Active Driving Level (POS) is based on... Figure 6 It is obtained by at least one of the benchmarks shown.

[0085] 2-2-1. Relationship with speed limit

[0086] Adhering to speed limits means safe driving. Therefore, the Active Driving Level Acquisition Unit 150 can also acquire the Active Driving Level POS based on whether or not the speed limit has been exceeded.

[0087] The speed limit of the road on which the electric vehicle 10 is traveling is obtained, for example, from a speed limit sign S set up on that road. The speed limit sign S is identified using a camera mounted on the electric vehicle 10. The driving state acquisition unit 110 identifies the speed limit sign S by analyzing the image captured by the camera. Furthermore, the driving state acquisition unit 110 identifies the number recorded on the speed limit sign S based on the identified image of the speed limit sign S. That is, the driving state acquisition unit 110 acquires information about the speed limit indicated by the speed limit sign S. Typically, the driving state acquisition unit 110 identifies the speed limit sign S and the speed limit from the image using image recognition AI (Artificial Intelligence). The image recognition AI is pre-generated using learning methods such as deep learning.

[0088] As another example, if speed limit information is registered in the map information, the driving status acquisition unit 110 can also obtain the speed limit information based on the current position of the electric vehicle 10 and the map information. The current position of the electric vehicle 10 is obtained by a position sensor. The map information is pre-stored in the storage device 102.

[0089] Alternatively, the driving state acquisition unit 110 acquires the speed of the electric vehicle 10 from the wheel speed sensors. Or, the driving state acquisition unit 110 may calculate the speed based on the position change of the electric vehicle 10.

[0090] The driving status acquisition unit 110 determines whether the speed limit has been exceeded based on the speed of the electric vehicle 10 and the speed limit. In this case, the operating status information DRV includes whether the speed limit has been exceeded.

[0091] The active driving level acquisition unit 150 acquires (calculates) the active driving level POS based on whether or not speed limits are exceeded. More specifically, active time is the time during which no speeding occurs, i.e., the time when the speed is below the speed limit. Total active time is the sum of active times. If speeding occurs, the total active time can be reduced by the time during which speeding occurred. Active ratio is the proportion of active time to a certain period. Active parameter is the total active time, active ratio, or a combination thereof. The active driving level acquisition unit 150 increases the active driving level POS as the active parameter increases. Here, the active driving level POS can increase continuously or in stages. The relationship between the active parameter and the active driving level POS can also be given by a mapping.

[0092] 2-2-2. Acceleration and deceleration

[0093] Avoiding rapid acceleration implies safe driving. Therefore, the drivability acquisition unit 150 can also acquire the drivability POS based on the acceleration of the electric vehicle 10.

[0094] The driving status acquisition unit 110 acquires the acceleration of the electric vehicle 10 from the acceleration sensor. The driving status information (DRV) includes the acceleration of the electric vehicle 10.

[0095] The active driving level acquisition unit 150 acquires (calculates) the active driving level POS based on acceleration. More specifically, active time is the time when acceleration is below a threshold. Total active time is the sum of active times. When acceleration exceeds the threshold, the total active time can be reduced by decreasing the time acceleration exceeds the threshold. Active ratio is the proportion of active time relative to a certain period. Active parameter is the total active time, active ratio, or a combination thereof. The active driving level acquisition unit 150 increases the active driving level POS as the active parameter increases. Here, the active driving level POS can increase continuously or in stages. The relationship between the active parameter and the active driving level POS can also be given by a mapping.

[0096] Not decelerating suddenly also means safe driving. Therefore, the active driving level acquisition unit 150 can also acquire the active driving level POS based on the deceleration of the electric vehicle 10. The method for acquiring the active driving level POS in this case is the same as in the case of acceleration described above, except that "acceleration" in the above description is replaced with "deceleration (absolute value)".

[0097] 2-2-3. Steering speed

[0098] Avoiding sharp turns signifies safe driving. Therefore, the active driving level acquisition unit 150 can acquire the active driving level POS based on the steering speed of the electric vehicle 10's steering wheel.

[0099] The driving status acquisition unit 110 calculates the steering speed based on the steering angle detected by the steering angle sensor. The driving status information (DRV) includes the steering speed.

[0100] The active driving level acquisition unit 150 acquires (calculates) the active driving level POS based on steering speed. More specifically, active time is the time when the steering speed is below a threshold. Total active time is the sum of active times. When the steering speed exceeds the threshold, the total active time can be reduced by the time the steering speed exceeds the threshold. Active ratio is the proportion of active time relative to a certain period. Active parameter is the total active time, active ratio, or a combination thereof. The active driving level acquisition unit 150 increases the active driving level POS as the active parameter increases. Here, the active driving level POS can increase continuously or in stages. The relationship between the active parameter and the active driving level POS can also be given by mapping.

[0101] 2-2-4. Workshop distance, TTC

[0102] A sufficient distance between the vehicle and the preceding vehicle implies safe driving. Therefore, the active driving level acquisition unit 150 can also acquire the active driving level POS based on the distance between the vehicle and the preceding vehicle.

[0103] The driving status acquisition unit 110 uses identification sensors to acquire surrounding condition information representing the conditions around the electric vehicle 10. Examples of identification sensors include cameras, lidar, and radar. For example, the surrounding condition information includes images captured by a camera. As another example, the surrounding condition information may also include point group information obtained by lidar. The surrounding condition information also includes object information related to objects around the electric vehicle 10. Examples of objects around the electric vehicle 10 include pedestrians, bicycles, other vehicles (e.g., vehicles ahead, following, parallel, and parked), roadside structures (e.g., curbs, guardrails, and walls), white lines, signs, and signals. The object information represents the relative position and relative speed of the object relative to the electric vehicle 10. For example, by analyzing images obtained by a camera, objects can be identified and their relative positions calculated. Alternatively, objects can be identified and their relative positions and speeds obtained based on point group information obtained by lidar. The driving status information (DRV) includes object information. The relative distance to the vehicle ahead is equivalent to the inter-vehicle distance.

[0104] The active driving level acquisition unit 150 acquires (calculates) the active driving level POS based on the inter-vehicle distance to the preceding vehicle. More specifically, the active time is the time when the inter-vehicle distance is above a threshold. This threshold can be a function of the speed of the electric vehicle 10. That is, the threshold can also increase as the speed increases. The total active time is the sum of the active times. When the inter-vehicle distance is less than the threshold, the total active time can be reduced by the time when the inter-vehicle distance is less than the threshold. The active ratio is the proportion of active time relative to a certain period. The active parameter is the total active time, the active ratio, or a combination thereof. The active driving level acquisition unit 150 increases the active driving level POS as the active parameter increases. Here, the active driving level POS can increase continuously or in stages. The relationship between the active parameter and the active driving level POS can also be given by a mapping.

[0105] The existence of a sufficient TTC (Time-To-Collision) relative to the preceding vehicle also implies safe driving. TTC is calculated based on the inter-vehicle distance and the speed of the electric vehicle 10. The active driving level acquisition unit 150 can also acquire the active driving level POS based on the TTC. The method for acquiring the active driving level POS in this case is the same as in the case of inter-vehicle distance described above, except that "inter-vehicle distance" in the above description is replaced with "TTC". The threshold can also be a predetermined threshold independent of speed.

[0106] 2-2-5. Distance from surrounding objects

[0107] The distance (margin) between the electric vehicle 10 and surrounding objects is sufficient for safe driving. Examples of surrounding objects include pedestrians, bicycles, parallel vehicles, parked vehicles, roadside structures (e.g., curbs, guardrails, walls), etc. Therefore, the active driving level acquisition unit 150 can also acquire the active driving level POS based on the distance to surrounding objects.

[0108] As described above, the Driving Status Information (DRV) includes object information related to surrounding objects around the electric vehicle 10. This object information includes the distance to the surrounding objects.

[0109] The active driving level acquisition unit 150 acquires (calculates) the active driving level POS based on the distance to surrounding objects. More specifically, the active time is the time spent at or above a threshold distance from surrounding objects. This threshold can be a function of the speed of the electric vehicle 10. That is, the threshold can also increase as the speed increases. The total active time is the sum of active times. When the distance to surrounding objects is less than the threshold, the total active time can be reduced by the time spent at or above the threshold distance from surrounding objects. The active ratio is the proportion of active time relative to a certain period. The active parameter is the total active time, the active ratio, or a combination thereof. The active driving level acquisition unit 150 increases the active driving level POS as the active parameter increases. Here, the active driving level POS can increase continuously or in stages. The relationship between the active parameter and the active driving level POS can also be given by a mapping.

[0110] 2-2-6. Lane Changing Status

[0111] Infrequent lane changes indicate safer driving. Furthermore, changing lanes within permitted lane-changing zones also signifies safer driving. Therefore, the active driving level acquisition unit 150 can also acquire an active driving level POS based on the state of lane changes.

[0112] The driving status acquisition unit 110 detects the driver's active steering operation based on the detection results from the steering sensor and / or steering torque sensor. Additionally, the driving status acquisition unit 110 identifies the white lines surrounding the electric vehicle 10 and their types based on images captured by a camera. The driving status acquisition unit 110 can identify lane changes based on the detection results of the driver's steering operation and the identification results of the white lines. In the event of a lane change, the driving status acquisition unit 110 can determine whether the lane change was performed within a permitted lane-changing area based on the type of white line.

[0113] As another example, when lane information is registered in the map information, the driving status acquisition unit 110 can identify the occurrence of a lane change based on the location of the electric vehicle 10 and the map information. When lane change permitted areas and lane change prohibited areas are registered in the map information, the driving status acquisition unit 110 can determine whether the lane change was performed in a lane change permitted area.

[0114] Driving status information (DRV) includes lane change status. Lane change status can also include the frequency of lane changes within a certain period. Lane change status can also include whether a lane change was made within a permitted lane-changing area.

[0115] The active driving level acquisition unit 150 acquires (calculates) the active driving level POS based on the lane change status. For example, the lower the frequency of lane changes, the higher the active driving level POS. Here, the active driving level POS can increase continuously or in stages. The relationship between the frequency of lane changes and the active driving level POS can also be provided through mapping.

[0116] As another example, the active driving level acquisition unit 150 can also increase the active driving level POS when a lane change is made in a lane change permitted area. Conversely, the active driving level acquisition unit 150 can also decrease the active driving level POS when a lane change is made in a lane change prohibited area.

[0117] 2-2-7. Energy-saving operation

[0118] Methods of fuel-efficient driving are illustrated, for example, by Japan's Ministry of the Environment (see: https: / / www.env.go.jp / air / car / ecodrive / susume.html, https: / / www.env.go.jp / content / 900397998.pdf). For instance, suppressing rapid acceleration contributes to fuel-efficient driving. As other examples, maintaining sufficient distance between vehicles and driving at a reasonable speed also contributes to fuel-efficient driving. Based on parameters such as speed, acceleration, accelerator operation, and distance between vehicles, fuel-efficient driving conditions (driving range) are preset.

[0119] The active driving level acquisition unit 150 determines whether the driving state of the electric vehicle 10 meets the conditions for energy-saving driving based on the driving state information DRV. Active time is the time during which the driving state of the electric vehicle 10 meets the conditions for energy-saving driving. Total active time is the sum of active times. The total active time can be reduced by the time during which the driving state of the electric vehicle 10 does not meet the conditions for energy-saving driving. Active ratio is the proportion of active time relative to a certain period. Active parameter is the total active time, active ratio, or a combination thereof. The active driving level acquisition unit 150 increases the active driving level POS as the active parameter increases. Here, the active driving level POS can increase continuously or in stages. The relationship between the active parameter and the active driving level POS can also be given by a mapping.

[0120] 2-2-8. Combination

[0121] It can also be a combination of two or more of the sub-segments 2-2-1 to 2-2-7 mentioned above. That is, the active driving level acquisition unit 150 can also integrate multiple active driving level POS obtained based on each of multiple benchmarks to obtain the final active driving level POS.

[0122] 2-3. Sound management corresponding to the level of active driving

[0123] exist Figure 5 In the example shown, the active driving level acquisition unit 150 outputs the active driving level POS to the engine sound generation unit 130. The engine sound generation unit 130 changes the generated simulated engine sound according to the active driving level POS.

[0124] For example, as the active driving level POS increases, the engine sound generation unit 130 increases the listenability of the simulated engine sound. For example, as the active driving level POS increases, the engine sound generation unit 130 increases listenability by reducing the noise components included in the simulated engine sound. As another example, the engine sound generation unit 130 can also increase listenability by reducing unpleasant sounds (creaking, gurgling) included in the simulated engine sound as the active driving level POS increases. As yet another example, the engine sound generation unit 130 can also increase listenability by reducing unwanted sound components (sounds unrelated to the engine sound) included in the simulated engine sound as the active driving level POS increases. The sound source data for noise, unpleasant sounds, and unwanted sounds are included in the basic sound source data 200.

[0125] As another example, the engine sound generation unit 130 can also increase listenability by reducing the "roar" of the simulated engine sound as the active driving level POS increases. The adjustment of the simulated engine sound's "roar" can also utilize a DSP (Digital Signal Processor). As yet another example, the engine sound generation unit 130 can also increase listenability by increasing the sound pressure level of the simulated engine sound as the active driving level POS increases. As yet another example, the engine sound generation unit 130 can also increase listenability by improving the sound quality of the simulated engine sound as the active driving level POS increases. Sound quality is determined by frequency characteristics, distortion rate, SN ratio, dynamic range, etc.

[0126] In a generalized manner, the engine sound generation unit 130 changes at least one of the timbre, tone quality, sound pressure level, and range of the simulated engine sound according to the active driving level POS. DSP can also be used for adjusting the timbre, tone quality, sound pressure level, and range.

[0127] Figure 7 This is a block diagram illustrating an example of the functional configuration of the engine sound generation unit 130. Figure 7In the example shown, the engine sound generation unit 130 includes a default sound generation unit 131 and a correction unit 132. The default sound generation unit 131 generates a default analog engine sound ES0 based on driving state information DRV and basic sound source data 200. The default analog engine sound ES0 is a typical analog engine sound without considering the active driving level POS. The correction unit 132 receives the default analog engine sound ES0 and the positive driving level POS. Furthermore, the correction unit 132 generates an analog engine sound that reflects the active driving level POS by correcting the default analog engine sound ES0 according to the active driving level POS. For example, as the active driving level POS increases, the correction unit 132 generates an analog engine sound by increasing the audibility of the default analog engine sound ES0. The correction unit 132 may also include a DSP.

[0128] like Figure 5 As shown, the vehicle management system 100 may include a user interface 160. The user interface 160 includes input devices and output devices. Examples of input devices include touch panels, buttons, switches, keyboards, microphones, etc. Examples of output devices include touch panels, displays, speakers, etc. When the current driving state is safe driving / energy-saving driving, the vehicle management system 100 may also notify the user (driver) of the status of safe driving / energy-saving driving via the user interface 160. For example, when the active driving level POS is above a threshold, the vehicle management system 100 may also notify the user (driver) of the status of safe driving / energy-saving driving via the user interface 160. For example, the vehicle management system 100 may display visual information indicating that safe driving / energy-saving driving is in progress on a display device. As another example, the vehicle management system 100 may also output voice information indicating that safe driving / energy-saving driving is in progress from a speaker.

[0129] Figure 8 This is another block diagram illustrating the functional structure of a vehicle management system 100. (Appropriate omissions are allowed.) Figure 5 The example shown is a repetitive illustration. In Figure 8 In the example shown, the Active Driving Level Acquisition Unit 150 outputs the Active Driving Level POS to the Audio Source Data Management Unit 120. Based on the Active Driving Level POS, the Audio Source Data Management Unit 120 changes the types of available basic audio source data 200. The available basic audio source data 200 is provided, for example, from a management server. The change in the types of available basic audio source data 200 is equivalent to the change in the available options for simulated engine sounds.

[0130] For example, the audio source data management unit 120 increases the variety of available basic audio source data 200 as the active driving level POS increases. In other words, the audio source data management unit 120 increases the option for simulated engine sound as the active driving level POS increases. While changing the option for simulated engine sound according to the active driving level POS, the option for simulated engine sound can also be changed from the default option. Here, the default option is the normal option when the active driving level POS is not considered.

[0131] The user (driver) of the electric vehicle 10 can specify a desired sound source from multiple types of basic sound source data 200 via the user interface 160. The engine sound generation unit 130 generates a simulated engine sound using the basic sound source data 200 specified by the user. That is, the user of the electric vehicle 10 can specify a desired simulated engine sound from the options via the user interface 160.

[0132] Figure 9 This is another example of a block diagram illustrating the functional structure of a vehicle management system 100. Figure 9 The example shown is Figure 5 and Figure 8 The combination of these factors means that, based on the level of active driving (POS), the simulated engine sound changes, and the options for simulating the engine sound also change.

[0133] Furthermore, as stated above, the sounds described in this disclosure are not limited to simulated engine sounds. This disclosure can also be applied to other sounds different from simulated engine sounds.

[0134] 2-4. Effects

[0135] As explained above, according to this embodiment, sound is output through a speaker 70 mounted on the electric vehicle 10. Furthermore, the sound changes and / or the sound options change according to the active driving level POS, which indicates the degree of safe / energy-efficient driving of the electric vehicle 10. Drivers engaging in safe / energy-efficient driving can enjoy these changes in sound and / or sound options. These changes in sound and / or sound options can also be considered privileges or rewards given to drivers engaging in safe / energy-efficient driving. Drivers engaging in safe / energy-efficient driving feel satisfied with these privileges and rewards. This becomes an incentive for safe / energy-efficient driving. As a result, safe / energy-efficient driving is promoted. The promotion of safe / energy-efficient driving is also beneficial for traffic flow and the environment.

[0136] As the Active Driving Level (POS) increases, the audibility of the sound also increases. The noise component in the sound also decreases. The "roaring" sound also diminishes. The sound quality also improves. This becomes a strong reward for drivers who want to enjoy the sound, promoting safe / fuel-efficient driving. Consequently, it further promotes safe / fuel-efficient driving.

[0137] As the Active Driving Level (POS) increases, more sound options become available. This provides a strong incentive for drivers who want to enjoy the audio, thus further promoting safe and fuel-efficient driving.

[0138] 3. Various application methods

[0139] The following describes various ways of using the vehicle management system 100 of this embodiment.

[0140] Figure 10 This is a block diagram illustrating the on-board device 400 and the management server 300 that constitute the vehicle management system 100. The on-board device 400 and the management server 300 can communicate via a communication network.

[0141] The vehicle-mounted device 400 is mounted on an electric vehicle 10. The vehicle-mounted device 400 includes one or more processors 401 (hereinafter simply referred to as processor 401), one or more storage devices 402 (hereinafter simply referred to as storage devices 402), and a communication device 403. The processor 401 performs various processes. Examples of processor 401 include general-purpose processors, special-purpose processors, CPUs, GPUs, ASICs, FPGAs, integrated circuits, conventional circuits, and / or combinations thereof. The processor 401 may also be referred to as circuitry or processing circuitry. The storage device 402 stores (saves) various information. Examples of storage devices 402 include volatile memory, non-volatile memory, HDDs, SSDs, etc. The communication device 403 communicates with a management server 300. The functions of the vehicle-mounted device 400 are realized through the cooperation of the processor 401 and the storage device 402. Program 405 is a computer program executed by the processor 401. The functions of the vehicle-mounted device 400 can also be realized through the cooperation of the processor 401 executing program 405 and the storage device 402. The program 405 is stored in the storage device 402. Alternatively, the program 405 may also be recorded on a computer-readable recording medium.

[0142] The management server 300 includes one or more processors 301 (hereinafter referred to as processor 301), one or more storage devices 302 (hereinafter referred to as storage devices 302), and a communication device 303. The processor 301 performs various processes. Examples of processors 301 include general-purpose processors, special-purpose processors, CPUs, GPUs, ASICs, FPGAs, integrated circuits, conventional circuits, and / or combinations thereof. The processor 301 may also be referred to as a circuitry or processing circuitry. The storage device 302 stores (saves) various information. Examples of storage devices 302 include volatile memory, non-volatile memory, HDDs, SSDs, etc. The communication device 303 communicates with the on-board units 400 of multiple electric vehicles 10. The functions of the management server 300 are realized through the cooperation of the processor 301 and the storage device 302. Program 305 is a computer program executed by the processor 301. The functions of the management server 300 can also be realized through the cooperation of the processor 301 executing program 305 and the storage device 302. Program 305 is stored in the storage device 302. Alternatively, program 305 may be recorded on a computer-readable recording medium.

[0143] The processor 401 of the vehicle-mounted device 400 and the processor 301 of the management server 300, or a combination thereof, are equivalent to Figure 1 One or more processors 101 are shown. Any one or a combination of the storage device 402 of the vehicle-mounted device 400 and the storage device 302 of the management server 300 is equivalent to... Figure 1 One or more storage devices 102 are shown. Any one or a combination of the program 405 of the vehicle-mounted device 400 and the program 305 of the management server 300 is equivalent to... Figure 1 The vehicle management procedure 105 is shown.

[0144] 3-1. The first example

[0145] Figure 11 This is a block diagram illustrating a first example of how the vehicle management system 100 is used. In this first example, the driving state acquisition unit 110, the sound source data management unit 120, the engine sound generation unit 130, the output unit 140, and the active driving level acquisition unit 150 are all included in the on-board unit 400. The management of simulated engine sound is performed within the electric vehicle 10.

[0146] 3-2. Second case

[0147] Figure 12This is a block diagram illustrating a second example of how the vehicle management system 100 is used. In this second example, compared to the first example described above, the audio source data management unit 120 is included within the management server 300. The audio source data management unit 120 uniformly manages the basic audio source data 200 used in multiple electric vehicles 10. Therefore, the basic audio source data 200 is associated with a vehicle ID. The audio source data management unit 120 manages the available basic audio source data 200 for each vehicle ID.

[0148] The engine sound generation unit 130 of the vehicle-mounted device 400 downloads the basic audio source data 200 associated with the vehicle ID from the audio source data management unit 120 of the management server 300.

[0149] The active driving level acquisition unit 150 of the vehicle-mounted device 400 can upload a set of vehicle ID and active driving level POS to the management server 300. The upload frequency is arbitrary. The audio source data management unit 120 of the management server 300 changes the type of available basic audio source data 200 associated with the vehicle ID based on the received active driving level POS. For example, the audio source data management unit 120 increases the types of available basic audio source data 200 as the active driving level POS increases. The engine sound generation unit 130 of the vehicle-mounted device 400 downloads the available basic audio source data 200 associated with the vehicle ID from the audio source data management unit 120 of the management server 300.

[0150] Thus, according to the second example, the basic audio source data 200 used in multiple electric vehicles 10 is uniformly managed in the management server 300. This is preferred from the viewpoint of managing the basic audio source data 200.

[0151] 3-3. The Third Case

[0152] Figure 13 This is a block diagram illustrating a third example of how the vehicle management system 100 is used. In this third example, compared to the first example described above, the active driving level acquisition unit 150 is included in the management server 300. The active driving level acquisition unit 150 manages the active driving level POS associated with multiple electric vehicles 10. Therefore, the active driving level POS is associated with a vehicle ID. The active driving level acquisition unit 150 manages the active driving level POS for each vehicle ID.

[0153] The on-board unit 400 uploads a set of vehicle ID and driving status information (DRV) to the management server 300. The upload frequency is arbitrary. The active driving level acquisition unit 150 of the management server 300 acquires the active driving level (POS) associated with the vehicle ID based on the received driving status information (DRV). Furthermore, the active driving level acquisition unit 150 sends the active driving level (POS) to the electric vehicle 10 of that vehicle ID. The on-board unit 400 of the electric vehicle 10 of that vehicle ID performs voice management based on the received active driving level (POS).

[0154] According to the third example, the vehicle-mounted device 400 does not need to have an active drivability acquisition unit 150. Therefore, the storage capacity of the vehicle-mounted device 400 can be saved. In addition, the processing load of the vehicle-mounted device 400 can be reduced. Furthermore, it is not necessary to update the algorithm of the active drivability acquisition unit 150 in each of the multiple electric vehicles 10, but can be done simply all at once.

[0155] 3-4. Fourth case

[0156] Figure 14 This is a block diagram illustrating a fourth example of how the vehicle management system 100 is used. In this fourth example, compared to the first example described above, the audio source data management unit 120 and the active driving level acquisition unit 150 are included in the management server 300. That is, the fourth example is a combination of the second and third examples described above.

[0157] 4. Application of electric vehicles with manual mode (MT mode)

[0158] The electric motor used as the power source in a typical electric vehicle (EV) has significantly different torque characteristics compared to the internal combustion engine used in a conventional vehicle (CV). Due to this difference in torque characteristics, CVs require a transmission, whereas electric vehicles typically do not. Furthermore, typical electric vehicles lack a manual transmission (MT) where the driver manually changes gear ratios. Therefore, the driving experience differs considerably between driving a conventional vehicle with an MT and driving an electric vehicle.

[0159] On the other hand, the torque of an electric motor can be relatively easily controlled by adjusting the applied voltage and excitation. Therefore, by implementing appropriate control, the desired torque characteristics can be obtained within the operating range of the electric motor. Utilizing this feature, the torque of an electric vehicle can be controlled to simulate the torque characteristics unique to a manual transmission (MT) vehicle. Furthermore, a simulated gear shifter can be installed in the electric vehicle to allow the driver to experience the driving feel of a MT vehicle. Thus, a MT vehicle can be simulated within an electric vehicle.

[0160] In other words, the electric vehicle controls the motor output in a manner that simulates the driving characteristics (torque characteristics) unique to a manual transmission (MT) vehicle. The driver operates a simulated gearshift to perform simulated manual shifting operations. In response to the driver's simulated manual shifting operations, the electric vehicle changes its driving characteristics (torque characteristics) in a manner that mimics that of an MT vehicle. Thus, the driver of the electric vehicle can experience a feeling similar to driving a MT vehicle. Hereinafter, this motor control mode used to simulate the driving characteristics and manual shifting operations of an MT vehicle will be referred to as "manual mode" or "MT mode."

[0161] The electric vehicle 10 according to this disclosure can have a manual mode (MT mode). In MT mode, the electric vehicle 10 generates a simulated engine sound corresponding to the driver's driving operation and outputs the simulated engine sound via a speaker 70. Not only is the driving operation of the MT vehicle reproduced, but also the engine sound of the MT vehicle is reproduced, thus improving the satisfaction of drivers who require a realistic driving experience.

[0162] The following describes a structural example of an electric vehicle 10 equipped with a manual mode (MT mode).

[0163] 4-1. First Construction Example (Sequence Shifter)

[0164] Figure 15 This is a block diagram illustrating a first structural example of the power control system of the electric vehicle 10 according to this embodiment. The electric vehicle 10 includes an electric motor 44, a battery 46, and a converter 42. The electric motor 44 is a power unit for driving. The battery 46 stores electrical energy that drives the electric motor 44. That is, the electric vehicle 10 is a battery electric vehicle (BEV) that uses the electrical energy stored in the battery 46 for driving. The converter 42 converts the DC power input from the battery 46 during acceleration into driving power for the electric motor 44. In addition, the converter 42 converts the regenerative power input from the electric motor 44 into DC power during deceleration and charges the battery 46.

[0165] The electric vehicle 10 is equipped with an accelerator pedal 22 for the driver to input acceleration requirements for the electric vehicle 10. An accelerator position sensor 32 for detecting the accelerator opening is provided on the accelerator pedal 22.

[0166] The electric vehicle 10 is equipped with a sequential shifter 24. The sequential shifter 24 can be a paddle shifter or a lever-type virtual shifter.

[0167] A paddle shifter is a virtual shifter, distinct from a traditional paddle shifter. It has a similar structure to the paddle shifters found in clutchless manual transmission (MT) vehicles. The paddle shifter is mounted on the steering wheel. It includes upshift and downshift switches that determine the operating position. The upshift switch sends an upshift signal 34u when pulled forward, and the downshift switch sends a downshift signal 34d when pulled forward.

[0168] On the other hand, the lever-type pseudo-shifter, like the paddle shifter, is a virtual shifter that differs from the original shifter. The lever-type simulated shifter has a similar structure to the lever-type shifter found in clutchless MT vehicles. The lever-type simulated shifter outputs an upshift signal 34u by tilting the shift lever forward and a downshift signal 34d by tilting the shift lever backward.

[0169] Wheel speed sensors 36 are provided on the wheels 26 of the electric vehicle 10. The wheel speed sensors 36 are used as vehicle speed sensors to detect the speed of the electric vehicle 10. In addition, a rotation speed sensor 38 is provided on the electric motor 44 to detect its rotation speed.

[0170] The electric vehicle 10 includes a control device 50. The control device 50 is typically an electronic control unit (ECU) mounted on the electric vehicle 10. The control device 50 can also be a combination of multiple ECUs. The control device 50 includes an interface, memory, and a processor. An in-vehicle network is connected to the interface. The memory includes RAM for temporarily recording data and ROM for storing programs executable by the processor and various data associated with the programs. The program consists of multiple instructions. The processor reads the program and data from the memory and executes them, generating control signals based on signals obtained from various sensors.

[0171] For example, control unit 50 controls motor 44 via PWM control of converter 42. Signals from accelerometer position sensor 32, sequential shifter 24 (which serves as upshift and downshift switches in the case of a paddle shifter), wheel speed sensor 36, and speed sensor 38 are input to control unit 50. Control unit 50 processes these signals and calculates the motor torque command value for PWM control of converter 42.

[0172] The control device 50 includes an automatic mode (EV mode) and a manual mode (MT mode) as control modes. The automatic mode is the normal control mode for driving the electric vehicle 10 as a regular electric vehicle. The automatic mode is programmed to continuously change the output of the electric motor 44 based on the operation of the accelerator pedal 22. On the other hand, the manual mode is the control mode for driving the electric vehicle 10 like a manual transmission (MT) vehicle. The manual mode is programmed to change the output characteristics of the electric motor 44 in response to upshifting and downshifting operations relative to the accelerator pedal 22 based on the sequential shifter 24. In other words, the manual mode is a control mode capable of changing the output of the electric motor 44 in response to driving operations of vehicle components other than the accelerator pedal 22 and brake pedal. The automatic mode (EV mode) and the manual mode (MT mode) are switchable.

[0173] The control device 50 includes an automatic mode torque calculation unit 54 and a manual mode torque calculation unit 56. Each unit 54 and 56 can be a separate independent ECU, or the function of an ECU can be obtained by a processor executing a program recorded in memory.

[0174] The automatic mode torque calculation unit 54 has the function of calculating the motor torque when controlling the motor 44 in automatic mode. The automatic mode torque calculation unit 54 stores a motor torque command map. The motor torque command map is determined based on the accelerator opening and the rotational speed of the motor 44. Signals from the accelerator position sensor 32 and the speed sensor 38 are input to the parameters of the motor torque command map. The motor torque corresponding to these signals is output from the motor torque command map. Therefore, in automatic mode, even if the driver operates the sequence shifter 24, this operation will not be reflected in the motor torque.

[0175] The manual mode torque calculation unit 56 has an MT vehicle model. The MT vehicle model is used to calculate the drive wheel torque that should be obtained by operating the accelerator pedal 22 and the sequential shifter 24 when the electric vehicle 10 is assumed to be an MT vehicle.

[0176] Reference Figure 16 The MT vehicle model included in the manual mode torque calculation unit 56 is explained. For example... Figure 16 As shown, the MT vehicle model includes an engine model 561, a clutch model 562, and a transmission model 563. Furthermore, the engine, clutch, and transmission, virtually implemented through the MT vehicle model, are respectively referred to as a virtual engine, a virtual clutch, and a virtual transmission. In engine model 561, the virtual engine is modeled. In clutch model 562, the virtual clutch is modeled. In transmission model 563, the virtual transmission is modeled.

[0177] Engine model 561 calculates the virtual engine speed Ne and the virtual engine output torque Teout. The virtual engine speed Ne is calculated based on the wheel speed Nw, the combined reduction ratio R, and the slip ratio Rslip of the virtual clutch. For example, the virtual engine speed Ne is represented by the following equation (1).

[0178] Equation (1): Ne = Nw × R / (1 - Rslip)

[0179] The virtual engine output torque Teout is calculated based on the virtual engine speed Ne and the accelerator opening Pap. In the calculation of the virtual engine output torque Teout, as follows... Figure 16 As shown, a mapping is used that defines the relationship between accelerator opening Pap, virtual engine speed Ne, and virtual engine output torque Teout. In this mapping, each accelerator opening Pap is assigned a virtual engine output torque Teout relative to the virtual engine speed Ne. Figure 16 The torque characteristics shown can be set to the characteristics of a hypothetical gasoline engine or a hypothetical diesel engine. Alternatively, the characteristics of a naturally aspirated engine or a turbocharged engine can be set to the hypothetical characteristics.

[0180] Clutch model 562 calculates the torque transmission gain k. The torque transmission gain k is used to calculate the torque transmission degree of the virtual clutch corresponding to the virtual clutch opening Pc. The virtual clutch opening Pc is typically 0%, temporarily opening to 100% in conjunction with the switching of virtual gear stages in the virtual transmission. Clutch model 562 has the following characteristics: Figure 16 The mapping shown is used. In this mapping, the torque transfer gain k is assigned to the virtual clutch opening Pc. Figure 16 In the model, Pc0 corresponds to the position where the virtual clutch opening Pc is 0%, and Pc3 corresponds to the position where the virtual clutch opening Pc is 100%. The ranges from Pc0 to Pc1 and from Pc2 to Pc3 are the dead zones where the torque transfer gain k does not change according to the virtual clutch opening Pc. Clutch model 562 uses the torque transfer gain k to calculate the clutch output torque Tcout. The clutch output torque Tcout is the torque output from the virtual clutch. For example, the clutch output torque Tcout is given by the product of the virtual engine output torque Teout and the torque transfer gain k (Tcout = Teout × k).

[0181] Additionally, clutch model 562 calculates the slip ratio Rslip. The slip ratio Rslip is used to calculate the virtual engine speed Ne in engine model 561. In the calculation of the slip ratio Rslip, similar to the torque transmission gain k, a mapping of the slip ratio Rslip to the virtual clutch opening Pc can be used.

[0182] The transmission model 563 calculates the gear ratio (gear shift ratio) r. The gear ratio r is determined by the virtual gear stage GP in the virtual transmission. Upon receiving an upshift operation from the sequential shifter 24, the virtual gear stage GP moves up one gear. Conversely, upon receiving a downshift operation from the sequential shifter 24, the virtual gear stage GP moves down one gear. The transmission model 563 has the following characteristics: Figure 16 The mapping is shown. In this mapping, the virtual gear stage GP is assigned a gear ratio r such that the larger the virtual gear stage GP, the smaller the gear ratio r. The transmission model 563 uses the gear ratio r obtained from the mapping and the clutch output torque Tcout to calculate the transmission output torque Tgout. For example, the transmission output torque Tgout is given by the product of the clutch output torque Tcout and the gear ratio r (Tgout = Tcout × r). The transmission output torque Tgout varies discontinuously according to the switching of the gear ratio r. This discontinuous variation of the transmission output torque Tgout produces shift shocks, exhibiting the potential of vehicles with stepped transmissions.

[0183] The MT vehicle model uses a specified reduction ratio rr to calculate the drive wheel torque Tw. The reduction ratio rr is a fixed value determined by the mechanical structure from the virtual transmission to the drive wheels. Multiplying the reduction ratio rr by the gear ratio r yields the aforementioned combined reduction ratio R. The MT vehicle model calculates the drive wheel torque Tw based on the transmission output torque Tgout and the reduction ratio rr. For example, the drive wheel torque Tw is given by the product of the transmission output torque Tgout and the reduction ratio rr (Tw = Tgout × rr).

[0184] The control unit 50 converts the drive wheel torque Tw calculated from the MT vehicle model into the required motor torque Tm. The required motor torque Tm is the motor torque required to achieve the drive wheel torque Tw calculated from the MT vehicle model. In the conversion from drive wheel torque Tw to required motor torque Tm, a reduction ratio from the output shaft of the motor 44 to the drive wheel is used. Furthermore, the control unit 50 controls the motor 44 according to the required motor torque Tm by controlling the converter 42.

[0185] Figure 17 This graph compares the torque characteristics of motor 44 implemented using motor control in an MT vehicle model with the torque characteristics of motor 44 implemented using conventional motor control in an electric vehicle (EV). Based on the motor control using the MT vehicle model, such as... Figure 17 As shown, the torque characteristics (solid line in the figure) simulating the torque characteristics of a manual transmission vehicle can be achieved based on the virtual gear stages set by the sequential shifter 24. Furthermore, in Figure 17 In the middle, the number of gear stages is 6.

[0186] 4-2. Example of the second structure

[0187] Figure 18 This is a block diagram illustrating a second structural example of the power control system of the electric vehicle 10 according to this embodiment. Here, only the configuration different from the first configuration example described above will be described. Specifically, in the second structural example, the electric vehicle 10 has a simulated gear shift lever (simulated gear shifting device) 27 and a simulated clutch pedal 28 instead of the sequential gear shifter 24 provided in the first structural example. The simulated gear shift lever 27 and the simulated clutch pedal 28 are simply dummy components different from the original gear shift lever and clutch pedal.

[0188] The simulated gear shift lever 27 has the structure of a gear shift lever found in a manual transmission (MT) vehicle. The configuration and operation of the simulated gear shift lever 27 are identical to those of an actual MT vehicle. The simulated gear shift lever 27 has positions corresponding to gears such as 1st, 2nd, 3rd, 4th, 5th, 6th, reverse, and neutral. A gear position sensor 27a is provided on the simulated gear shift lever 27, which detects the gear position by determining the location of the simulated gear shift lever 27.

[0189] The simulated clutch pedal 28 has the structure of a clutch pedal found in a manual transmission (MT) vehicle. The configuration and operating feel of the simulated clutch pedal 28 are identical to those of an actual MT vehicle. The simulated clutch pedal 28 is operated when the simulated shift lever 27 is used. That is, the driver depresses the simulated clutch pedal 28 when they wish to change the gear position using the simulated shift lever 27, and releases the pedal when the gear position change is complete, allowing the simulated clutch pedal 28 to return to its original position. The simulated clutch pedal 28 is equipped with a clutch position sensor 28a for detecting the amount of depressurization of the simulated clutch pedal 28.

[0190] Signals from the accelerator position sensor 32, gear position sensor 27a, clutch position sensor 28a, wheel speed sensor 36, and speed sensor 38 are input to the control unit 50. The control unit 50 processes these signals and calculates the motor torque command value for PWM control of the converter 42.

[0191] Similar to the first structural example described above, the control device 50 includes an automatic mode and a manual mode as control modes. The automatic mode is programmed to continuously change the output of the electric motor 44 based on the operation of the accelerator pedal 22. On the other hand, the manual mode is a control mode for driving the electric vehicle 10 like a manual transmission (MT) vehicle. The manual mode is programmed to change the output and output characteristics of the electric motor 44 in response to the operation of the accelerator pedal 22 based on the operation of the simulated clutch pedal 28 and the simulated gear shift lever (simulated gear shifting device) 27. In other words, the manual mode is a control mode capable of changing the output of the electric motor 44 in response to driving operations of vehicle components other than the accelerator pedal 22 or the brake pedal.

[0192] The vehicle model and manual mode torque calculation unit 56 are equipped with Figure 16 The vehicle model shown is the same. However, the virtual clutch opening Pc is replaced by the amount of pressure applied to the virtual clutch pedal 28 detected by the clutch position sensor 28a. Additionally, the virtual gear shift GP is determined by the position of the simulated gear shift lever 27 detected by the shift position sensor 27a.

[0193] 5. Driving characteristic management considering safe driving / energy-saving driving.

[0194] The electric vehicle 10 in this embodiment can also have a simulation mode that simulates the driving characteristics of a virtual vehicle.

[0195] For example, as explained in section 4 above, the electric vehicle 10 may also have a manual mode (MT mode) that simulates the driving characteristics of a MT vehicle. In this case, the virtual vehicle is an MT vehicle. The simulation mode includes the manual mode (MT mode).

[0196] As another example, electric vehicle 10 could also have an EV mode that simulates the driving characteristics of a different type of electric vehicle than electric vehicle 10. In this case, the virtual vehicle is a different type of electric vehicle than electric vehicle 10.

[0197] The vehicle management system 100 of this embodiment can also change the options for virtual vehicles in simulation mode based on the level of active driving (POS). For example, the vehicle management system 100 increases the number of virtual vehicle options in simulation mode as the level of active driving (POS) increases.

[0198] Figure 19 This is a block diagram illustrating another example of the functional structure of the vehicle management system 100. The vehicle management system 100 includes a driving state acquisition unit 110, an active driving level acquisition unit 150, and a virtual vehicle management unit 170 as functional blocks. These functional blocks can also be implemented, for example, through the cooperation of a processor 101 executing the vehicle management program 105 and a storage device 102.

[0199] The driving status acquisition unit 110, the active driving level acquisition unit 150, and the user interface 160 are the same as in the above embodiment.

[0200] The Virtual Vehicle Management Unit 170 manages virtual vehicle model data 270, which represents the model of the virtual vehicle, the simulated object in simulation mode. For example, in the case of manual mode (MT mode) simulating the driving characteristics of a manual transmission (MT) vehicle, the virtual vehicle model data 270 includes... Figure 16The MT vehicle model shown is as follows (engine model 561, clutch model 562, and transmission model 563). If the MT vehicle being simulated is different, then the MT vehicle model, i.e., the virtual vehicle model data 270, will also be different. Figure 17 The driving characteristics (torque characteristics) shown are also different.

[0201] The Active Driving Level Acquisition Unit 150 outputs the Active Driving Level POS to the Virtual Vehicle Management Unit 170. Based on the Active Driving Level POS, the Virtual Vehicle Management Unit 170 changes the types of available virtual vehicle model data 270. The available virtual vehicle model data 270 is provided, for example, from a management server. The changes in the types of available virtual vehicle model data 270 are equivalent to the changes in the options for available virtual vehicles in simulation mode.

[0202] For example, as the active driving level POS increases, the virtual vehicle management unit 170 increases the variety of available virtual vehicle model data 270. In other words, as the active driving level POS increases, the virtual vehicle management unit 170 increases the options of virtual vehicles that can be used in simulation mode. When changing the virtual vehicle options according to the active driving level POS, the virtual vehicle options can also be changed from the default options. The default options are the normal options without considering the active driving level POS.

[0203] The user (driver) of the electric vehicle 10 can specify a desired virtual vehicle model from a variety of virtual vehicle model data 270 via the user interface 160. The control device 50 uses the virtual vehicle model data 270 specified by the user to simulate the driving characteristics of the virtual vehicle. That is, the user of the electric vehicle 10 can specify a desired option from the virtual vehicle options via the user interface 160.

[0204] As explained above, the electric vehicle 10 has a simulation mode that simulates the driving characteristics of a virtual vehicle. Furthermore, the virtual vehicle options available in the simulation mode change according to the active driving level POS, which represents the degree of safe / energy-efficient driving of the electric vehicle 10. Drivers engaging in safe / energy-efficient driving can enjoy these changes in virtual vehicle options. These changes in virtual vehicle options can be seen as a privilege or reward given to drivers engaging in safe / energy-efficient driving. Drivers engaging in safe / energy-efficient driving feel satisfied with the privilege and reward given to them. This becomes an incentive for safe / energy-efficient driving. As a result, safe / energy-efficient driving is promoted. The promotion of safe / energy-efficient driving is also beneficial for traffic flow and the environment.

[0205] As the Active Driving Points (POS) increase, the number of virtual vehicle options also increases. This provides a strong incentive for drivers who want to enjoy simulation mode, promoting safer / more fuel-efficient driving. Consequently, it further promotes safer / more fuel-efficient driving.

[0206] In addition, the above Figures 11-14 The audio source data management department 120 was replaced by the virtual vehicle management department 170.

[0207] 6. Combination

[0208] Combinations of sections 2 and 5 above are also possible. That is, the vehicle management system 100 may also consider safe driving / energy-saving driving, implementing both the sound management described in section 2 and the driving characteristic management described in section 5.

[0209] [Explanation of reference numerals in the attached figures]

[0210] 10…Electric vehicle, 11…Sensor, 44…Electric motor, 70…Speaker, 100…Vehicle management system, 110…Driving status acquisition unit, 120…Audio source data management unit, 130…Engine sound generation unit, 140…Output unit, 150…Active driving level acquisition unit, 160…User interface, 170…Virtual vehicle management unit, 200…Basic audio source data, 270…Virtual vehicle model data, 300…Management server, 400…On-board device, DRV…Driving status information, ES…Engine sound data, POS…Active driving level.

Claims

1. A vehicle management system applied to an electric vehicle, wherein the electric vehicle uses an electric motor as a power unit for driving, wherein, The vehicle management system includes one or more processors configured to generate sound and output the sound through speakers mounted on the electric vehicle. The one or more processors are further configured to: Obtain driving status information representing the driving state of the electric vehicle. Based on the driving state information, an active driving level is obtained, representing the degree of safe and / or energy-efficient driving of the electric vehicle. The sound may be changed and / or the options for the sound may be changed depending on the level of active driving.

2. The vehicle management system according to claim 1, wherein, The one or more processors are configured to increase the audibility of the sound as the level of active driving increases.

3. The vehicle management system according to claim 1, wherein, The one or more processors are configured to reduce the noise component in the sound as the level of active driving increases.

4. The vehicle management system according to claim 1, wherein, The one or more processors are configured to increase the sound pressure level of the sound as the level of active driving increases.

5. The vehicle management system according to claim 1, wherein, The one or more processors are configured to change at least one of the timbre, sound quality, sound pressure level, and sound range of the sound according to the level of active driving.

6. The vehicle management system according to claim 1, wherein, The one or more processors are configured to increase the option of the sound as the level of active driving increases.

7. The vehicle management system according to claim 1, wherein, The driving state of the electric vehicle includes at least one of the following: presence or absence of speed limit, speed, acceleration, deceleration, steering speed, inter-vehicle distance, TTC (Time-To-Collision), distance to surrounding objects, frequency of lane changes, and state of lane changes.

8. The vehicle management system according to claim 1, wherein, The sound is a simulated engine sound.

9. The vehicle management system according to any one of claims 1-8, wherein, The electric vehicle has a simulation mode that simulates the driving characteristics of a virtual vehicle.

10. The vehicle management system according to claim 9, wherein, The one or more processors are also configured to vary the options for the virtual vehicle that can be used in the simulation mode, depending on the level of active driving.

11. The vehicle management system according to claim 9, wherein, The virtual vehicle is a manual transmission vehicle. The simulation mode includes a manual mode that simulates the driving characteristics of the manually driven vehicle.

12. The vehicle management system according to claim 11, wherein, The electric vehicle is equipped with an accelerator pedal and a sequential gear shifter. In the manual mode, the electric vehicle is configured such that the output characteristics of the electric motor, in relation to the operation of the accelerator pedal, change according to the shifting operation of the sequential shifter.

13. The vehicle management system according to claim 11, wherein, The electric vehicle is equipped with an accelerator pedal, a simulated clutch pedal, and a simulated gear shifting device. The simulated clutch pedal is operated when the simulated gear shifting device is used. In the manual mode, the electric vehicle is configured to change the output of the electric motor in response to the operation of the accelerator pedal, based on the operation of the simulated clutch pedal and the operation of the simulated gear shifting device.

14. An electric vehicle that uses an electric motor as a power unit for driving, wherein, The electric vehicle includes one or more processors configured to generate sound and output the sound through speakers mounted on the electric vehicle. The one or more processors are further configured to: Obtain driving status information representing the driving state of the electric vehicle. Based on the driving state information, an active driving level is obtained, representing the degree of safe and / or energy-efficient driving of the electric vehicle. The sound may be changed and / or the options for the sound may be changed depending on the level of active driving.

15. A vehicle management system applied to an electric vehicle, wherein the electric vehicle uses an electric motor as a power unit for driving, wherein... The electric vehicle has a simulation mode that simulates the driving characteristics of a virtual vehicle. The vehicle management system has one or more processors. The one or more processors are configured as follows: Obtain driving status information representing the driving state of the electric vehicle. Based on the driving state information, an active driving level is obtained, representing the degree of safe and / or energy-efficient driving of the electric vehicle. The options for the virtual vehicle that can be used in the simulation mode vary depending on the level of active driving.

16. The vehicle management system according to claim 15, wherein, The one or more processors are configured to increase the options for the virtual vehicle that can be used in the simulation mode as the level of active driving increases.

Images