CN119649493A - Vehicle, method for operating a vehicle, computer program product and controller - Google Patents
Vehicle, method for operating a vehicle, computer program product and controller Download PDFInfo
- Publication number
- CN119649493A CN119649493A CN202510008084.1A CN202510008084A CN119649493A CN 119649493 A CN119649493 A CN 119649493A CN 202510008084 A CN202510008084 A CN 202510008084A CN 119649493 A CN119649493 A CN 119649493A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- event
- user
- data
- locking
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Lock And Its Accessories (AREA)
Abstract
The application relates to a vehicle comprising a data recording module, an acquisition module and a locking module, wherein the data recording module can record event data when the vehicle collides, the acquisition module is used for acquiring user settings of a user for locking the event data, the user is especially a driver and/or a vehicle owner of the vehicle, and the locking module is used for locking the recorded event data based on the acquired user settings. The application also relates to a corresponding method, computer program product and controller for operating a vehicle. The application has the advantage that the locking of event data of a crash event, in particular a crash event initiated by an active device protecting pedestrians, can be set autonomously by the user.
Description
Technical Field
The application relates to a vehicle, a method for operating a vehicle, a computer program product and a controller. The application relates in particular to the locking of event data of a crash event of a vehicle.
Background
The vehicle has a data recording module that can record event data when the vehicle is involved in a collision event. A collision event refers to a physical event that a vehicle collides with a vehicle, a vehicle collides with a pedestrian, and a vehicle collides with other objects. The event data can, for example, help to investigate the cause of the crash event and thus to determine responsibility for the crash event, and can also provide data support for subsequent safety studies.
Event data of a collision event sometimes needs to be locked. If not locked, it may be overwritten by data of a subsequent event before the user extracts the data.
Currently, a fixed locking condition is usually preset, and thus frequent locking may occur. This may lead to frequent replacement of the domain controller, especially in case the data logging module is an autopilot data logging system.
Disclosure of Invention
The object of the present application is to provide a vehicle enabling autonomous setting of the locking of event data of a collision event, in particular of a collision event initiated by an active device protecting a pedestrian, by a user, i.e. providing the user with the function of autonomously setting the locking of event data of a collision event.
According to a first aspect of the present application, there is provided a vehicle having:
The data recording module can record event data when the vehicle collides with the event;
the system comprises an acquisition module for acquiring user settings of a user, in particular a driver and/or a vehicle owner of the vehicle, for locking of event data;
and a locking module for performing locking of the recorded event data based on the acquired user settings.
According to an alternative embodiment of the application, the user settings comprise user presets for future crash events and/or field settings for handling current crash events.
According to an alternative embodiment of the application, the user settings for the locking of event data include whether to lock event data, what type of collision event data to lock, how long to lock data as event data and/or which data of the event data to lock.
According to an alternative embodiment of the application, the event data comprises vehicle status data, crash related data, driver operation and status information, occupant status data, vehicle system data, time and environment data, navigation data, vehicle and autopilot data logging system basic information and/or autopilot system operation information.
According to an alternative embodiment of the application, the data logging module is an autopilot data logging system, in particular a car event data logging system and/or an intelligent networked car autopilot data logging system.
According to an alternative embodiment of the present application, the user settings include user settings made by a user for locking event data of a collision event of the vehicle colliding with a pedestrian, and the locking module is configured to perform locking of event data of a collision event of the vehicle colliding with a pedestrian based on the acquired user settings.
According to an alternative embodiment of the application, the user settings comprise user settings made by a user for locking of the pedestrian protection active device-initiated crash event data record of the vehicle, the locking module being adapted to perform locking of the pedestrian protection active device-initiated crash event data record of the vehicle based on the obtained user settings.
According to an alternative embodiment of the application, the pedestrian protection active device comprises a pedestrian protection airbag and/or a deployable hood.
According to an alternative embodiment of the application, the vehicle has a determination module for determining whether a pedestrian-protecting active device of the vehicle is activated in the current crash event.
According to an alternative embodiment of the application, the vehicle has an interactive interface, in particular a central control screen of the vehicle and/or an external mobile device, in particular an application of the external mobile device, which can communicate with the vehicle, on which interactive interface a user can set up for locking of event data, in particular can select whether to lock event data.
According to an alternative embodiment of the application, the interactive interface allows the user to set the user's locking of the event data of the crash event, in particular to choose whether to lock the event data of the crash event, only after the crash event, in particular within a preset time threshold after a crash event initiated by the active pedestrian protection means of the vehicle.
According to an alternative embodiment of the application, the interactive interface allows the user to make a user setting for the locking of the event data of the current crash event, in particular allows the user to select whether to lock the event data of the current crash event, if the determination module determines that the active pedestrian protection means of the vehicle is activated in the current crash event.
According to an alternative embodiment of the application, the vehicle gives the user a visually, audibly and/or tactilely settable reminder to lock the event data of the current crash event.
According to an alternative embodiment of the application, a pop-up for the user to lock settings is automatically popped up on the interactive interface or the interactive interface is automatically switched to a lock settings interface, in particular to select by the user whether to lock event data of the current crash event.
According to a second aspect of the present application, there is provided a method for operating a vehicle, the method comprising the steps of:
an acquisition step of acquiring user settings by a user for locking of event data;
A locking step in which locking of event data of a collision event of the vehicle is performed based on the acquired user setting.
According to an alternative embodiment of the application, the vehicle is the aforementioned vehicle.
According to an alternative embodiment of the application, the method comprises a determining step, after the vehicle has perceived a collision, in which determining step it is determined whether an active pedestrian protection arrangement of the vehicle is activated.
According to an alternative embodiment of the application, the acquisition step comprises a setting guidance step, in which, in particular in the event that it is determined that the active device of the vehicle for pedestrian protection is activated in the event of a current crash, a user-settable reminder is issued to the user for locking of event data of the current crash event and/or a pop-up for the user to set the lock or an automatic switching of the interactive interface of the vehicle to a lock setting interface is automatically carried out on the interactive interface of the vehicle, the reminder being carried out in particular visually, audibly and/or tactilely.
According to an alternative embodiment of the application, the method comprises a lock setting function closing step, in which the interactive interface of the vehicle is not provided with a lock setting function for the user of the corresponding event data, if the user does not make a lock setting, in particular does not select whether to lock or not, within a preset time threshold.
According to a third aspect of the present application there is provided a computer program product comprising computer program instructions which, when executed by at least one processor, perform the aforementioned method for operating a vehicle.
According to a fourth aspect of the present application there is provided a controller comprising a processor and a memory in which computer program instructions are stored, wherein the processor is capable of performing the aforementioned method for operating a vehicle when the computer program instructions are executed by the processor.
Drawings
The principles, features and advantages of the present application may be better understood by describing the present application in more detail with reference to the drawings. The drawings include:
fig. 1 schematically shows an example of a situation in which a vehicle is involved in a collision event.
Fig. 2 schematically shows an example of several modules of the vehicle of the application for recording and locking event data.
Fig. 3 schematically shows an example of the flow of the method of the application for operating a vehicle.
Detailed Description
In order to make the technical problems, technical solutions and advantageous technical effects to be solved by the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and a plurality of exemplary embodiments. It should be understood that the detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the application.
Fig. 1 schematically illustrates one example of a situation in which a vehicle 10 is involved in a collision event. Here, the vehicle 10 collides with the pedestrian 12, for example. The vehicle 10 generally has a data logging module 208 that is capable of logging event data when the vehicle 10 is involved in a crash event. The data logging module 208 may be, for example, an automobile event data logging system (EDR) and/or an intelligent networked automobile autopilot data logging system (DSSAD). The data logging module 208 logs event data when a collision event occurs with the vehicle 10. It is also contemplated that the data logging module 208 is another data logging module 208. The recorded event data can, for example, help to investigate the cause of the crash event and thus to determine the responsibility for the crash event, and can also provide data support for subsequent safety studies.
Event data of a collision event sometimes needs to be locked. If not locked, it may be overwritten by data of a subsequent event before the user extracts the data. However, if the locking condition is too low, locking of a plurality of event data may occur based on the occurrence frequency of the collision event, and the vehicle-mounted electronic control unit may need to be replaced after the locking event fills the preset storage space. This may result in frequent replacement of expensive domain controllers, especially if the data logging module 208 is an autopilot data logging system. In view of this, the national standard also allows the pedestrian protection apparatus to be deployed without definition as a lockout event when defining an event lockout condition.
To this end, the present application proposes a vehicle 10.
Fig. 2 schematically illustrates one example of several modules of the vehicle 10 of the present application for recording and locking event data.
As shown in fig. 2, the vehicle 10 has:
A data logging module 208, said data logging module 208 capable of logging event data when said vehicle 10 is involved in a crash event;
An acquisition module 204, the acquisition module 204 being configured to acquire user settings for locking of event data by a user, in particular a driver and/or owner of the vehicle 10;
A locking module 206, the locking module 206 being configured to perform locking of the recorded event data based on the acquired user settings.
It is thus possible for the user to decide whether to lock the event data of the crash event and/or how to lock, thus balancing the contradiction of the user's potential needs with the system design. The driver may be set up, for example, by the vehicle system, while the owner may be set up, for example, by the APP-associated account.
According to an exemplary embodiment of the application, the event data comprises vehicle status data, collision related data, driver operation and status information, occupant status data, vehicle system data, time and environment data, navigation data, vehicle and autopilot data logging system basic information and/or autopilot system operation information.
The vehicle state data may include speed data, acceleration data, vehicle direction data, steering wheel angle data, engine speed data, and/or brake data of the vehicle 10.
The crash-related data may include the time at which the crash began and ended, the crash intensity, and/or the crash trigger event.
The driver operation and status information may include whether the driver is belted, whether the driver is in a driving position, the driver's operation of the accelerator pedal, brake pedal, and steering wheel, the driver's physical state of mind, and/or whether the driver has intervened in autopilot, etc.
The occupant status data may include seat occupancy information for an occupant.
The vehicle system data may include data on airbag status, vehicle body stability control system status, whether automatic emergency braking is activated, and/or electrical system status, among others.
The time and environment data may include pre-event data (typically including detailed recordings of seconds prior to the occurrence of an event) and/or environmental information (including external conditions such as light, temperature, etc.). The time and environment data may include, inter alia, external images and/or external videos of the vehicle.
The vehicle and autopilot data recording system basic information may include a vehicle identification code, a hardware version number that implements autopilot data recording system functionality, a serial number that implements autopilot data recording system functionality, an autopilot data recording system software version number and/or event type encoding, and the like.
The autopilot system operation information may include information of various parameters requested by the autopilot system (e.g., lateral acceleration requested by the autopilot system, steering wheel steering angle, steering curvature, gear, vehicle speed, etc.).
According to an exemplary embodiment of the application, the user settings comprise user presets for future crash events and/or field settings for handling current crash events.
According to an exemplary embodiment of the present application, the user settings for locking of event data include whether to lock event data, what type of collision event data to lock, how long to lock data as event data (i.e., determining a time start and a time end of event data), and/or which data to lock event data.
For example, the user may set:
other event data, except for the mandatory lock event, are either all locked or none locked;
For a pedestrian protection apparatus deployment event, only event data that collides with a pedestrian 12 is locked, while event data that collides with other objects is not locked;
In addition to the mandatory lock event, only the event data of the front side collision is locked;
Locking event data for only one week, one month, one year, or three years;
Locking data from 10 seconds before the collision to 2 seconds after the collision is completed as event data except for the compulsory locking event;
In addition to the mandatory locking event, only the vehicle state data and the driver operation and state information in the event data are locked.
It is apparent that a person skilled in the art can envisage various variants of such as user settings.
According to an exemplary embodiment of the present application, the user settings include user settings made by a user for locking of event data of a collision event of the vehicle 10 colliding with the pedestrian 12, and the locking module 206 is configured to perform locking of event data of a collision event of the vehicle 10 colliding with the pedestrian 12 based on the acquired user settings. That is, the collision event in which the vehicle 10 collides with the pedestrian 12 is provided with a function of autonomously setting the lock of the event data to the user.
The user settings may include, among other things, user settings made by a user for locking of the crash event triggered event data record initiated by the pedestrian protection active device 14 of the vehicle 10, the locking module 206 being configured to perform locking of the crash event triggered event data record initiated by the pedestrian protection active device 14 of the vehicle 10 based on the obtained user settings.
Particularly for the automated driving data recording system of the vehicle 10, it should record event data that protects the pedestrian 12 from a collision event initiated by the active device 14. For such locking of event data, there is a degree of freedom that can be freely determined. It is conceivable here that the autonomous setting function is provided for the user only for the locking of event data recorded by the autopilot data recording system for a crash event initiated by the active device 14 of the vehicle 10 protecting the pedestrian 12, whereas for event data of other types of crash events, the locking condition can be determined in accordance with regulations or preset by the manufacturer, without providing the user with a function of setting the locking.
Alternatively or additionally, it is also conceivable to provide the user with a lock setting function of the event data for other types of crash events, in particular crash events in which a certain setting degree of freedom exists in terms of locking of the event data.
According to an exemplary embodiment of the present application, as shown in FIG. 2, the vehicle 10 has a determination module 200, the determination module 200 being configured to determine whether an active device 14 of the vehicle 10 that protects the pedestrian 12 is activated during a current crash event. If the pedestrian 12-protecting active device 14 of the vehicle 10 is activated during a current crash event, the current crash event is a crash event that the pedestrian 12-protecting active device 14 of the vehicle 10 is activated, and conversely, the current crash event is not a crash event that the pedestrian 12-protecting active device 14 of the vehicle 10 is activated.
According to an exemplary embodiment of the present application, referring to FIG. 1, the active device 14 for pedestrian protection 12 includes a pedestrian protection airbag and/or a deployable hood. The pedestrian protection airbag is provided, for example, at a front bumper of the vehicle 10 and/or a side surface of the vehicle 10. The distance between the deployable hood and the underlying cabin becomes greater when deployed, thereby providing more cushioning space for the pedestrian 12.
According to an exemplary embodiment of the present application, as shown in fig. 2, the vehicle 10 has an interactive interface 202, in particular a central control screen of the vehicle 10 and/or an external mobile device, in particular an application of the external mobile device, which can communicate with the vehicle 10, on which interactive interface 202 a user can set a lock for event data, in particular can select whether to lock event data. The external mobile device comprises in particular a mobile phone.
Corresponding to the foregoing description, the user may, for example, make user presets on the interactive interface 202 for future crash events and/or field settings for current crash events.
In particular, in the case where the user settings relate to field settings for a current crash event, if the determination module 200 determines that the active device 14 of the vehicle 10 that protects the pedestrian 12 is activated during the current crash event, the interactive interface 202 allows the user to make user settings for locking of event data of the current crash event, in particular allows the user to select whether to lock event data of the current crash event.
For example, it is contemplated that if the determination module 200 determines that the active device 14 of the vehicle 10 protecting the pedestrian 12 is activated during a current crash event, the vehicle 10 visually, audibly, and/or tactilely issues a reminder to the user that the locking of event data for the current crash event can be user-set.
In the case of a visual alert, in particular a pop-up window for a user to lock settings may be automatically popped up on the interactive interface 202 or the interactive interface 202 may be automatically switched to a lock settings interface to select, in particular by the user, whether to lock event data of the current crash event. An example of the interactive interface 202 providing the user with a "Y" and "N" lock option is schematically shown in FIG. 2, where "Y" represents a lock and "N" represents an unlock.
It is furthermore conceivable that if the user is not operating at all times, the pop-up window and/or the lock setting interface automatically disappears from the interactive interface after a certain time has elapsed. The user can thereafter reach the lock interface, for example, by operating the interactive interface 202, to make a lock setting, and in particular to be able to select whether to lock the event data.
It may also be arranged that the popup window is not automatically popped up or that it is not automatically switched to the lock setting interface, but that the user can reach the lock setting interface by operating the interactive interface 202 for lock setting, in particular to be able to select whether or not to lock event data.
In addition, audible alerts are, for example, voice alerts or alert tones, while tactile alerts are, for example, vibration or the like.
According to an exemplary embodiment of the present application, the interactive interface 202 allows a user to set, and in particular to select whether to lock, the event data of a collision event only after the collision event, and in particular within a preset time threshold after the collision event initiated by the active device 14 of the vehicle 10 protecting the pedestrian 12.
The preset time threshold is, for example, one day. After a preset time threshold, the default user need not lock the collision event. Accordingly, after a preset time threshold, the event data of the subsequent event is allowed to be overridden by the data logging module 208 without the need for a lock.
In accordance with the above-described functional modules of the vehicle, the application also relates to a method for operating the vehicle 10.
Fig. 3 schematically illustrates one example of a flow of the method of the present application for operating the vehicle 10.
The method comprises the following steps:
An acquisition step 302, in which user settings for locking of event data by a user are acquired in the acquisition step 302;
A locking step 306, in the locking step 306, locking of event data of a collision event of the vehicle 10 is performed based on the acquired user setting.
According to an exemplary embodiment of the present application, as shown in fig. 3, the method includes a determining step 300, in which it is determined whether an active device 14 of the vehicle 10 that protects the pedestrian 12 is activated after the vehicle 10 senses a collision, in the determining step 300.
After determining that the active device 14 of the vehicle 10 protecting the pedestrian 12 is activated, an obtaining step 302 may be performed, in which obtaining step 302 a user setting by a user for locking of event data of a collision event activated by the active device 14 of the vehicle 10 protecting the pedestrian 12 is obtained. Here, if the user has preset for the lock, the user preset is acquired. If the user does not preset for locking, the user is alerted and/or provided with a lock setting function or lock setting interface. The acquisition step 302 includes, for example, a setting guidance step 304, in which a reminder is issued to the user that the locking of the event data of the current crash event can be set by the user and/or a pop-up window for the user to set the locking or the interactive interface 202 of the vehicle 10 is automatically switched to a locking setting interface to set, in particular, whether to lock the event data. The alert is in particular made visually, audibly and/or tactilely.
According to an exemplary embodiment of the present application, the method comprises a lock setting function closing step 308, in which, if the user does not make a lock setting, in particular does not select whether to lock, within a preset time threshold, the interactive interface 202 of the vehicle 10 is no longer provided with a lock setting function of the corresponding event data for the user in the lock setting function closing step 308. The interactive interface 202 in particular no longer displays the lock setting options of the corresponding event data. In addition, the data recording module 208 may also perform corresponding data processing.
Corresponding to the method for operating the vehicle 10, the application also relates to a corresponding computer program product comprising computer program instructions, wherein the computer program instructions, when executed by one or more processors, are capable of carrying out the above-described method for operating the vehicle.
The application further relates to a corresponding controller comprising a processor and a memory in which computer program instructions are stored, wherein the processor is capable of performing the above-described method for operating a vehicle when the computer program instructions are executed by the processor.
In the description, various embodiments may be described separately. The individual features of the embodiments described in the description can be regarded as being independent and can be combined with one another in any desired manner, as long as they are possible in principle, without departing from the scope of protection of the application.
Although specific embodiments of the application have been described in detail herein, they are presented for purposes of illustration only and are not to be construed as limiting the scope of the application. Various substitutions, alterations, and modifications can be made without departing from the spirit and scope of the application.
List of reference numerals
10 Vehicle
12 Pedestrians
14 Active device for pedestrian protection
200 Determination Module
202 Interaction interface
204 Acquisition module
206 Locking module
208 Data recording module
300 Determination step
302 Acquisition step
304 Set-up guidance procedure
306 Locking step
308 Lock setup function off step
Claims (10)
1. A vehicle (10), characterized in that the vehicle (10) has:
A data recording module (208), the data recording module (208) being capable of recording event data when a collision event occurs with the vehicle (10);
-an acquisition module (204), the acquisition module (204) being adapted to acquire user settings made by a user, in particular a driver and/or owner of the vehicle (10), for locking of event data;
A locking module (206), the locking module (206) being configured to perform locking of the recorded event data based on the acquired user settings.
2. The vehicle (10) according to claim 1, characterized in that,
The user settings include user presets for future crash events and/or field settings for handling current crash events, and/or
User settings for locking of event data include whether to lock event data, what type of collision event data to lock, how long to lock data as event data and/or which data in the event data to lock, and/or
The event data includes vehicle state data, collision related data, driver operation and state information, occupant state data, vehicle system data, time and environment data, navigation data, vehicle and autopilot data recording system base information and/or autopilot system operation information, and/or
The data recording module (208) is an autopilot data recording system, in particular a car event data recording system and/or an intelligent network-connected car autopilot data recording system.
3. The vehicle (10) of any of the preceding claims, characterized in that the user settings comprise user settings made by a user for locking of event data of a collision event of the vehicle (10) colliding with a pedestrian (12), the locking module (206) being for performing locking of event data of a collision event of the vehicle (10) colliding with a pedestrian (12) based on the acquired user settings;
The user settings in particular comprising user settings made by a user for a locking of a collision event triggered event data record initiated by an active device (14) protecting a pedestrian (12) of the vehicle (10), the locking module (206) being adapted to perform a locking of a collision event triggered event data record initiated by an active device (14) protecting a pedestrian (12) of the vehicle (10) based on the acquired user settings;
the active device (14) for protecting a pedestrian (12) comprises in particular a pedestrian protection airbag and/or a deployable bonnet.
4. A vehicle (10) according to claim 3, characterized in that the vehicle (10) has a determination module (200), the determination module (200) being adapted to determine whether an active device (14) of the vehicle (10) protecting a pedestrian (12) is activated in the current crash event.
5. The vehicle (10) according to any of the preceding claims, characterized in that the vehicle (10) has an interactive interface (202), in particular a central screen of the vehicle (10) and/or an external mobile device, in particular an application of the external mobile device, which can communicate with the vehicle (10), on which interactive interface (202) a user can set a lock for event data, in particular can select whether to lock event data;
the interactive interface (202) allows a user to set, in particular to select whether or not to lock, event data of a collision event only after the collision event, in particular within a preset time threshold after a collision event initiated by an active device (14) of the vehicle (10) protecting a pedestrian (12).
6. The vehicle (10) of claim 4, wherein if the determination module (200) determines that an active device (14) of the vehicle (10) protecting a pedestrian (12) is activated in the current crash event,
The interactive interface (202) allows a user to make user settings for the locking of event data of a current crash event, in particular allows the user to select whether to lock event data of a current crash event;
The vehicle (10) particularly visually, audibly and/or tactilely emits a user-settable reminder to the user of the locking of event data of the current crash event;
In particular, a pop-up window for a user to lock is automatically popped up on the interactive interface (202) or the interactive interface (202) is automatically switched to a lock setting interface to select, in particular, by the user, whether to lock event data of a current crash event.
7. Method for operating a vehicle, in particular according to any of claims 1 to 6, characterized in that it comprises the following steps:
an acquisition step (302), in which user settings by a user for locking of event data are acquired;
A locking step (306), in the locking step (306), locking of event data of a collision event of the vehicle (10) is performed based on the acquired user setting.
8. The method for operating a vehicle of claim 7, wherein,
The method comprises a determining step (300), after the vehicle (10) has perceived a collision, in which determining step (300) it is determined whether an active device (14) of the vehicle (10) that protects the pedestrian (12) is activated, and/or
The acquisition step (302) comprises a setting guidance step (304), in which, in particular in the event of a determination that the active device (14) of the vehicle (10) for protecting the pedestrian (12) is activated in the event of a current crash, a user-settable reminder is issued to the user for locking of event data of the current crash event and/or a pop-up of a pop-up window for the user to set the locking or an automatic switching of the interactive interface (202) of the vehicle (10) to a locking setting interface is automatically carried out on the interactive interface (202) of the vehicle (10), in particular in a visual, audible and/or tactile manner, and/or
The method comprises a lock setting function closing step (308), wherein if the user does not make a lock setting, in particular does not select whether to lock, within a preset time threshold, the interactive interface (202) of the vehicle (10) is no longer provided with a lock setting function of corresponding event data for the user in the lock setting function closing step (308).
9. Computer program product, characterized in that it comprises computer program instructions which, when executed by at least one processor, perform the method for operating a vehicle according to claim 7 or 8.
10. A controller, characterized in that it comprises a processor and a memory in which computer program instructions are stored, wherein the processor is capable of executing the method for operating a vehicle according to claim 7 or 8, when the computer program instructions are executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510008084.1A CN119649493A (en) | 2025-01-03 | 2025-01-03 | Vehicle, method for operating a vehicle, computer program product and controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510008084.1A CN119649493A (en) | 2025-01-03 | 2025-01-03 | Vehicle, method for operating a vehicle, computer program product and controller |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN119649493A true CN119649493A (en) | 2025-03-18 |
Family
ID=94954641
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202510008084.1A Pending CN119649493A (en) | 2025-01-03 | 2025-01-03 | Vehicle, method for operating a vehicle, computer program product and controller |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119649493A (en) |
-
2025
- 2025-01-03 CN CN202510008084.1A patent/CN119649493A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108621883B (en) | Monitoring vehicle carriage | |
| US9545879B2 (en) | Vehicle seat back haptic alert systems and methods | |
| US20040019426A1 (en) | Method and device for automatically triggering a deceleration in a motor vehicle | |
| US9266451B2 (en) | Alert systems and methods for a vehicle | |
| US7617048B2 (en) | Method for determining an accident risk between a first object with at least one second object | |
| US10308249B2 (en) | Adaptive cruise control system and vehicle comprising an adaptive cruise control system | |
| US7233235B2 (en) | Apparatus and method for using vehicle status information in safety restraint systems | |
| US20130342334A1 (en) | Alert systems and methods for a vehicle with improved actuator placement | |
| US9286773B2 (en) | Alert systems and methods for a vehicle with improved actuator installation | |
| DE102013211132A1 (en) | Method for warning driver about collision hazards in vision range of driver of vehicle, involves coordinating warning patterns between two haptic warning devices, between visual warning devices or between acoustic warning devices | |
| DE102013211444A1 (en) | Warning systems and methods for a vehicle | |
| CN108454557B (en) | Two-point auxiliary safety belt with second buckle | |
| US10055993B2 (en) | Systems and methods for control of mobile platform safety systems | |
| WO2019029832A1 (en) | Automated driving system and method of stimulating a driver | |
| US20040017288A1 (en) | Potential collision detection and reversing aid system | |
| CN113715815A (en) | Vehicle assist feature control | |
| Zaman | Automotive electronics design fundamentals | |
| US20070296565A1 (en) | Method for Initiating Safety Measures for a Motor Vehicle | |
| CN115416547A (en) | Vehicle seat adjusting method, device, equipment and storage medium | |
| CN119649493A (en) | Vehicle, method for operating a vehicle, computer program product and controller | |
| DE102004010541B4 (en) | Safety device for a motor vehicle | |
| WO2003096068A1 (en) | Method for determining a risk of an accident between a first object and at least one second object | |
| WO2017215874A1 (en) | Method and device for providing information relating to an activation process for activating a personal protection system of a vehicle | |
| CN108622001B (en) | Method for triggering a security function | |
| US12109946B2 (en) | Cabin child seat monitoring methods and systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |