Incident handling system, method, apparatus, storage medium, and vehicle

Abstract

The present disclosure relates to an accident handling system, method, device, storage medium and vehicle. The system is applied to a vehicle and comprises a plurality of domain controllers. Each domain controller comprises an application layer and a service layer. The application layer integrates one or more vehicle function modules, which are used to implement vehicle functions. The service layer integrates one or more vehicle service modules, which are used to provide vehicle services. The plurality of domain controllers comprises a general domain controller. The vehicle function modules integrated in the application layer of the general domain controller comprise an accident handling function module. By layering the system of the vehicle and modularizing the function and service modules, a service-oriented architecture is formed, and flexible expansion of the function and service is achieved. The embodiments of the present disclosure can achieve flexible expansion of the vehicle accident handling function and application scenarios, and make it possible to quickly and flexibly deploy more demand experience functions.

Description

Technical Field

[0001] This disclosure relates to the field of automotive technology, and more specifically, to an accident handling system, method, apparatus, storage medium, and vehicle. Background Technology

[0002] Currently, high-end vehicles can generally automatically deploy airbags, cut off fuel and shut off the engine, turn on hazard lights, and call for roadside assistance in the event of a collision, but they do not have many other intelligent functions. In contrast, low-end vehicles rely on manual operation for most functions, except for deploying airbags.

[0003] Because the existing architecture design of vehicle functions is based on control signals and specific hardware, the vehicle functions are not decoupled from hardware and software, making it difficult to reconstruct and expand the functions in subsequent scenarios, and making it difficult to deploy new functions flexibly and quickly. Summary of the Invention

[0004] To overcome the deficiencies in related technologies, according to a first aspect of the present disclosure, an accident handling system is provided, applied to a vehicle. The system includes: multiple domain controllers, each domain controller including an application layer and a service layer, the application layer integrating one or more vehicle function modules for implementing vehicle functions, and the service layer integrating one or more vehicle service modules for providing vehicle services; wherein the multiple domain controllers include a vehicle master domain controller, and the vehicle function modules integrated in the application layer of the master domain controller include an accident handling function module.

[0005] The main domain controller is used to receive an accident trigger signal and, in response to the accident trigger signal, send a call instruction to one or more domain controllers through the accident handling function module. The call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling.

[0006] The one or more domain controllers are used to enable the service of the vehicle service module indicated by the call instruction after receiving the call instruction from the accident handling function module.

[0007] Optionally, the plurality of domain controllers further includes: one or more sub-domain controllers, each of the sub-domain controllers managing at least a portion of the functions of the vehicle;

[0008] The system further includes a gateway, which is used to establish a communication connection between the master domain controller and the sub-domain controllers.

[0009] Optionally, the one or more domain controllers include: a body domain controller and a cockpit domain controller, wherein the body domain controller is used to manage the functions of the vehicle body, and the cockpit domain controller is used to manage the functions of the vehicle cockpit.

[0010] Optionally, the vehicle service module associated with vehicle accident handling includes one or more of the following:

[0011] A fuel cut-off service module is used to stop the fuel supply to the vehicle after an accident, so as to shut down the vehicle.

[0012] An accident braking service module is used to perform braking control on the vehicle after an accident occurs.

[0013] Hazard warning light activation service module, which is used to activate the hazard warning lights of the vehicle;

[0014] A warning sign projection service module, which is used to project warning signs around the vehicle;

[0015] A warning sound service module, which is used to emit warning sounds;

[0016] A rescue service module, which is used to provide rescue services;

[0017] The map reporting service module is used to report maps that indicate the location of the vehicle.

[0018] The traffic system reporting service module is used to report vehicle accident information to the traffic system.

[0019] Optionally, the main domain controller further includes an operation layer; the service layer of the main domain controller integrates an incident triggering service module, which is used to provide triggering services for the incident handling function module; the main domain controller is used for:

[0020] In response to the accident triggering signal, the operation layer triggers the accident triggering service module. After the accident handling function module of the application layer detects the start of the accident triggering service module, it sends a call instruction to one or more domain controllers through the accident handling function module. The call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling.

[0021] Optionally, the system further includes a collision sensor, which is used to send an accident trigger signal to the domain controller after detecting a collision involving the vehicle.

[0022] The overall domain controller is used to receive the accident trigger signal sent by the collision sensor;

[0023] And / or, the system further includes: an incident button, the incident button being used to send an incident trigger signal to the main domain controller after a trigger operation is detected.

[0024] The main domain controller is used to receive the accident trigger signal sent by the accident button.

[0025] According to a second aspect of the present disclosure, an accident handling method is provided, applied to an accident handling system as described in any of the first aspects, the method comprising:

[0026] The vehicle's main domain controller receives an accident trigger signal and, in response to the accident trigger signal, sends a call instruction to one or more domain controllers through the accident handling function module. The call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling.

[0027] After receiving the call instruction from the accident handling function module, the domain controller starts the service of the vehicle service module indicated by the call instruction.

[0028] According to a third aspect of the present disclosure, an accident handling apparatus is provided, applied to a domain controller, comprising:

[0029] A memory on which computer programs are stored;

[0030] A processor for executing the computer program in the memory to implement the steps of the method described in the second aspect.

[0031] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method described in the second aspect.

[0032] According to a fifth aspect of the present disclosure, a vehicle is provided, including an accident handling system as described in any of the first aspects.

[0033] In summary, this disclosure provides an accident handling system applied to a vehicle. The system includes multiple domain controllers, each comprising an application layer and a service layer. The application layer integrates one or more vehicle function modules for implementing vehicle functions, and the service layer integrates one or more vehicle service modules for providing vehicle services. Among the multiple domain controllers is a central domain controller. The application layer of the central domain controller integrates an accident handling function module. The central domain controller receives an accident trigger signal and, in response to the accident trigger signal, sends a call instruction to one or more domain controllers through the accident handling function module. The call instruction instructs the invocation of a vehicle service module associated with vehicle accident handling. Upon receiving the call instruction, the domain controller activates the service of the vehicle service module indicated by the call instruction. By layering the vehicle system and modularizing functions and services, a service-oriented architecture is formed, enabling flexible expansion of functions and services. This disclosure solves the problem of single, fixed functions in vehicle accident handling systems, which cannot support flexible development and expansion of intelligent scenario functions. The technical solution of this disclosure improves the flexibility of vehicle function development, enables flexible expansion of vehicle accident handling functions and application scenarios, and makes it possible to quickly and flexibly deploy more demand-driven experience functions.

[0034] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description

[0035] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the following detailed description to explain the present disclosure, but do not constitute a limitation thereof. In the drawings:

[0036] Figure 1 This is a schematic diagram illustrating an accident handling system according to an exemplary embodiment;

[0037] Figure 2 This is a schematic diagram illustrating an accident handling system according to an exemplary embodiment;

[0038] Figure 3 This is a flowchart illustrating an accident handling method according to an exemplary embodiment;

[0039] Figure 4 This is a block diagram illustrating an accident handling device 400 according to an exemplary embodiment;

[0040] Figure 5 This is a block diagram illustrating an accident handling device 500 according to an exemplary embodiment. Detailed Implementation

[0041] The specific embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit this disclosure.

[0042] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0043] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0044] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0045] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0046] It should be noted that the terms "one" and "multiple" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that they should be understood as "one or more" unless explicitly stated in the context. In the description of this disclosure, unless otherwise stated, "multiple" means two or more, and other quantifiers are similar; "at least one," "one or more," or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one 'a' can represent any number of 'a's; as another example, one or more of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple; "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural.

[0047] Although operations or steps are described in a specific order in the accompanying drawings in the embodiments of this disclosure, it should not be construed as requiring these operations or steps to be performed in the specific order or serial order shown, or requiring all of the shown operations or steps to be performed to obtain the desired result. In the embodiments of this disclosure, these operations or steps may be performed serially; they may be performed in parallel; or a portion of these operations or steps may be performed.

[0048] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0049] The present disclosure will now be described in conjunction with specific embodiments.

[0050] First, the application scenario of this disclosure is explained. The applicant has found that current vehicle accident handling systems do not adopt a service-oriented design architecture, making it impossible to provide services based on vehicle accident scenarios. The corresponding vehicle functions are based on signal and hardware binding, which also fails to meet the needs of flexible expansion and reconstruction of accident scenario service functions, as well as agile development. Firstly, existing vehicle functions are rigid, singular, and have a low level of intelligence, failing to meet users' experience needs for more intelligent scenarios, causing inconvenience and even safety hazards for drivers. Secondly, the current vehicle function design involves binding functions to software and ECUs (Electronic Control Units). Because the hardware and software are not decoupled, it is not conducive to developing and changing new vehicle functions according to user or scenario requirements. Furthermore, the development and modification process requires changes to a series of related controller logic or CAN (Controller Area Network) signals, which does not support agile development, subsequent function reconstruction and expansion, and makes it difficult to achieve a personalized user experience.

[0051] The purpose of this disclosure is to extend vehicle functionality by layering applications and services to decouple vehicle functions from hardware, enabling flexible expansion and reconfiguration of vehicle functions. For example, after a collision, the vehicle can perform a series of intelligent and automated safety control operations without driver intervention, achieving intelligent and safe vehicle operation and improving user experience. By using a service-oriented architecture to solve the hardware-software binding problem of vehicle accident handling functions, the development difficulty of new functions is reduced, development efficiency is improved, and development costs are saved. Furthermore, other related vehicle functions can be expanded and customized according to user needs, enabling flexible expansion and reconfiguration of accident scenario service functions, rapid deployment of new functional designs, and improved user experience.

[0052] Figure 1 This is a schematic diagram illustrating an accident handling system according to an exemplary embodiment, such as... Figure 1 As shown, the system includes multiple domain controllers. Each domain controller includes an application layer and a service layer. The application layer integrates one or more vehicle function modules, which are used to implement vehicle functions. The service layer integrates one or more vehicle service modules, which are used to provide vehicle services. Among the multiple domain controllers, there is a main domain controller for vehicles. The vehicle function modules integrated in the application layer of the main domain controller include an accident handling function module.

[0053] The main domain controller receives accident trigger signals and, in response to these signals, sends invocation commands to one or more domain controllers via the accident handling function module. These commands instruct the invocation of the vehicle service module associated with the vehicle accident handling function. Upon receiving the invocation command, one or more domain controllers activate the service of the vehicle service module specified in the command.

[0054] In some implementations, the plurality of domain controllers may further include: one or more sub-domain controllers, each sub-domain controller managing at least some of the functions of the vehicle, and the system further includes: a gateway (not shown) for establishing communication connections between the master domain controller and the sub-domain controllers.

[0055] In some implementations, the main domain controller further includes an operation layer (not shown in the figure); the service layer of the main domain controller integrates an accident triggering service module (not shown in the figure), which is used to provide triggering services for the accident handling function module; the main domain controller is used to: trigger the accident triggering service module in response to an accident triggering signal through the operation layer; after the accident handling function module in the application layer detects that the accident triggering service module has started, send a call instruction to one or more domain controllers through the accident handling function module; the call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling.

[0056] In some embodiments, the system further includes: a collision sensor (not shown), which sends an accident trigger signal to the main domain controller after detecting a vehicle collision, and the main domain controller receives the accident trigger signal sent by the collision sensor; and / or, the system further includes: an accident button (not shown), which sends an accident trigger signal to the main domain controller after detecting a trigger operation, and the main domain controller receives the accident trigger signal sent by the accident button.

[0057] In summary, this disclosure provides an accident handling system applied to a vehicle. The system includes multiple domain controllers, each comprising an application layer and a service layer. The application layer integrates one or more vehicle function modules for implementing vehicle functions, and the service layer integrates one or more vehicle service modules for providing vehicle services. Among the multiple domain controllers is a central domain controller. The application layer of the central domain controller integrates an accident handling function module. The central domain controller receives an accident trigger signal and, in response to the accident trigger signal, sends a call instruction to one or more domain controllers through the accident handling function module. The call instruction instructs the invocation of a vehicle service module associated with vehicle accident handling. Upon receiving the call instruction, one or more domain controllers activate the service of the vehicle service module indicated by the call instruction. By layering the vehicle system and modularizing applications and services, a service-oriented architecture is formed, enabling flexible expansion of applications and services. This disclosure solves the problem of single, fixed functions in vehicle accident handling systems, which cannot support flexible development and expansion of scenario-based service functions. The technical solution of this disclosure improves the flexibility of vehicle function development, enables flexible expansion of vehicle accident handling functions and application scenario services, and makes it possible to quickly and flexibly deploy more demand-driven experience functions.

[0058] Figure 2 This is a schematic diagram illustrating an accident handling system according to an exemplary embodiment. For example, the master domain controller may be a vehicle control domain controller, and multiple sub-domain controllers may include a body domain controller and a cockpit domain controller. The body domain controller manages the functions of the vehicle body, and the cockpit domain controller manages the functions of the vehicle cockpit. Figure 2 As shown, the system includes a vehicle control domain controller, a body domain controller, a cockpit domain controller, and a central gateway. The vehicle control domain controller, body domain controller, and cockpit domain controller are connected to the central gateway via Ethernet. For example, the central gateway may include a switch for information exchange. The vehicle control domain controller receives an accident trigger signal and, in response to the accident trigger signal, activates the vehicle control domain accident handling service. For example, the vehicle control domain accident handling service can be executed by the vehicle control domain hardware layer. The body domain controller activates the body domain accident handling service in response to an accident handling function call command. For example, the body domain accident handling service can be executed by the body domain hardware layer. The cockpit domain controller activates the cockpit domain accident handling service in response to an accident handling function call command. For example, the cockpit domain accident handling service can be executed by the cockpit domain hardware layer. The central gateway is used to receive and send call commands via Ethernet.

[0059] For example, in some embodiments, the vehicle service module associated with vehicle accident handling may include one or more of the following: a fuel cut-off service module, used to stop fuel supply to the vehicle after an accident, so as to shut down the vehicle; an accident braking service module, used to brake the vehicle after an accident, such as automatically engaging the handbrake; a hazard warning light activation service module, used to activate the vehicle's hazard warning lights; a warning sign projection service module, used to project warning signs, such as patterns or text with a warning of danger, around the vehicle; a warning sound service module, used to emit warning sounds, such as a voice prompt saying "Danger, do not approach"; a rescue service module, used to provide rescue services, such as automatically dialing a rescue phone number; a map reporting service module, used to report a map showing the vehicle's location, such as automatically sending the vehicle's location to a rescue center or 4S shop; and a traffic system reporting service module, used to report the vehicle accident situation to the traffic system.

[0060] For example, vehicle control domain accident handling services may include: accident triggering service, collision fuel cut-off service, and accident braking service. Body domain accident handling services may include: hazard warning light activation service, warning sign projection service, door unlocking service, and warning sound service. Cockpit domain accident handling services may include: rescue service, map reporting service, and traffic system reporting service.

[0061] In some implementations, the vehicle control domain controller further includes an operation layer; the service layer of the vehicle control domain controller integrates an accident triggering service module, which provides triggering services for the accident handling function module; the vehicle control domain controller is used to: trigger the accident triggering service module in response to an accident triggering signal through the operation layer; and after the accident handling function module of the vehicle control domain application layer detects the activation of the accident triggering service module, send a call instruction to one or more domain controllers, such as the body domain controller and the cockpit domain controller, through the accident handling function module. The call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling. For example, the relevant services can be executed by the corresponding domain hardware layer.

[0062] In some embodiments, the system further includes: a collision sensor, which sends an accident trigger signal to a vehicle control domain controller after detecting a vehicle collision, and the vehicle control domain controller receives the accident trigger signal sent by the collision sensor; and / or, the system further includes: an accident button, which sends an accident trigger signal to the vehicle control domain controller after detecting a trigger operation, and the vehicle control domain controller receives the accident trigger signal sent by the accident button.

[0063] In summary, this disclosure provides an accident handling system including a vehicle control domain controller, a body domain controller, a cockpit domain controller, and a central gateway. The vehicle control domain controller, body domain controller, and cockpit domain controller are connected to the central gateway via Ethernet. The vehicle control domain controller receives accident trigger signals and, in response to these signals, activates the vehicle control domain accident handling service. The body domain controller activates the body domain accident handling service in response to an accident handling function call command. The cockpit domain controller activates the cockpit domain accident handling service in response to an accident handling function call command. The central gateway receives and sends call commands via Ethernet. By layering the vehicle system and modularizing applications and services, a service-oriented architecture is formed, enabling flexible expansion of applications and services. This disclosure solves the problem of single, fixed functions in vehicle accident handling systems, which cannot support flexible development and expansion of scenario-based service functions. The technical solution of this disclosure can improve the flexibility of vehicle function development, enabling flexible expansion of vehicle accident handling functions and application scenario services, and making it possible to quickly and flexibly deploy more demand-driven experience functions.

[0064] Figure 3 This is a flowchart illustrating an accident handling method according to an exemplary embodiment, such as... Figure 3 As shown, this accident handling method can be applied to the aforementioned accident handling system, and the method may include the following steps:

[0065] In step S310, the vehicle's main domain controller receives an accident trigger signal and, in response to the accident trigger signal, sends a call instruction to one or more domain controllers through the accident handling function module. The call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling.

[0066] In this step, the operation layer of the vehicle's main domain controller receives an accident trigger signal. In response to the accident trigger signal, the accident trigger service module of the vehicle's main domain controller's service layer sends a call instruction to one or more domain controllers through the accident handling function module of the application layer. The call instruction is used to instruct the call to the service module of the vehicle service layer associated with vehicle accident handling.

[0067] In step S320, after receiving the call instruction from the accident handling function module, one or more domain controllers enable the service of the vehicle service module indicated by the call instruction.

[0068] In this step, after receiving a call instruction for the accident handling function, one or more domain controllers of the vehicle enable the service module of the service layer of the domain controller indicated by the call instruction.

[0069] The incident handling system used in the above-described incident handling method, as well as the methods executed by the master domain controller and one or more domain controllers receiving the invocation instructions from the master domain controller, have been disclosed in the foregoing embodiments and can be referred to therein. Figures 1 to 2 The contents of the illustrated embodiments will not be repeated.

[0070] In summary, this disclosure provides an accident handling method. The vehicle's main domain controller receives an accident trigger signal and, in response to the accident trigger signal, sends a call instruction to one or more domain controllers through the accident handling function module. The call instruction instructs the invocation of a vehicle service module associated with vehicle accident handling. Upon receiving the call instruction from the accident handling function module, one or more domain controllers activate the service of the vehicle service module indicated by the call instruction. This method forms a service-oriented architecture by layering the vehicle system and modularizing applications and services, enabling flexible expansion of applications and services. The technical solution of this disclosure can improve the flexibility of vehicle function development, realize the flexible expansion of vehicle accident handling functions and application scenario services, and make it possible to quickly and flexibly deploy more demand-driven experience functions.

[0071] Figure 4 This is a block diagram illustrating an accident handling apparatus 400 according to an exemplary embodiment. Figure 4 As shown, the incident handling device 400 may include a processor 401 and a memory 402. The incident handling device 400 may also include one or more of a multimedia component 403, an input / output (I / O) interface 404, and a communication component 405. The incident handling device may be a domain controller in the aforementioned incident handling system.

[0072] The processor 401 controls the overall operation of the incident handling device 400 to complete all or part of the steps in the incident handling method described above. The memory 402 stores various types of data to support the operation of the incident handling device 400. This data may include, for example, instructions for any application or method operating on the incident handling device 400, and application-related data such as contact data, sent and received messages, images, audio, video, etc. The memory 402 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. Multimedia component 403 may include a screen and an audio component. The screen may be, for example, a touchscreen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in memory 402 or transmitted via communication component 405. The audio component also includes at least one speaker for outputting audio signals. I / O interface 404 provides an interface between processor 401 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual or physical buttons. Communication component 405 is used for wired or wireless communication between the incident handling device 400 and other devices. Wireless communication includes, for example, Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, or 5G, NB-IoT (Narrow Band Internet of Things), or one or more combinations thereof. Therefore, the corresponding communication component 405 may include a Wi-Fi module, a Bluetooth module, or an NFC module.

[0073] In an exemplary embodiment, the incident handling device 400 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the incident handling method described above.

[0074] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the above-described accident handling method. For example, the computer-readable storage medium may be the memory 402 including program instructions, which may be executed by the processor 401 of the accident handling device 400 to complete the above-described accident handling method.

[0075] Figure 5 This is a block diagram illustrating an incident handling device 500 according to an exemplary embodiment. For example, the incident handling device 500 may be provided as a server. (Refer to...) Figure 5 The incident handling device 500 includes a processor 522, which may be one or more, and a memory 532 for storing computer programs executable by the processor 522. The computer programs stored in the memory 532 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processor 522 may be configured to execute the computer program to perform the incident handling method described above.

[0076] Additionally, the incident handling device 500 may also include a power supply component 526 and a communication component 550. The power supply component 526 can be configured to perform power management of the incident handling device 500, and the communication component 550 can be configured to enable communication of the incident handling device 500, such as wired or wireless communication. Furthermore, the incident handling device 500 may also include an input / output (I / O) interface 558. The incident handling device 500 can operate on an operating system stored in memory 532.

[0077] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the above-described accident handling method. For example, the computer-readable storage medium may be the memory 532 including program instructions, which may be executed by the processor 522 of the accident handling device 500 to complete the above-described accident handling method.

[0078] In another exemplary embodiment, a computer program product is also provided, the computer program product comprising a computer program executable by a programmable device, the computer program having a code portion for performing the above-described accident handling method when executed by the programmable device.

[0079] In another exemplary embodiment, this disclosure also provides a vehicle including the accident handling system described above.

[0080] The preferred embodiments of this disclosure have been described in detail above with reference to the accompanying drawings. However, this disclosure is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this disclosure, various simple modifications can be made to the technical solutions of this disclosure, and these simple modifications all fall within the protection scope of this disclosure.

[0081] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this disclosure will not describe the various possible combinations separately.

[0082] Furthermore, various different embodiments of this disclosure can be combined in any way, as long as they do not violate the spirit of this disclosure, they should also be regarded as the content disclosed in this disclosure.

Claims

1. An accident handling system, characterized in that, The system, applied to vehicles, includes: multiple domain controllers, each domain controller including an application layer and a service layer; the application layer integrates one or more vehicle function modules for implementing vehicle functions; and the service layer integrates one or more vehicle service modules for providing vehicle services; wherein the multiple domain controllers include a vehicle master domain controller, and the vehicle function modules integrated in the application layer of the master domain controller include an accident handling function module. The main domain controller also includes an operation layer; the service layer of the main domain controller integrates an accident triggering service module, which is used to provide triggering services for the accident handling function module; the main domain controller is used to receive an accident triggering signal, and in response to the accident triggering signal through the operation layer, trigger the accident triggering service module; after the accident handling function module of the application layer detects that the accident triggering service module has started, it sends a call instruction to one or more domain controllers through the accident handling function module, and the call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling; The one or more domain controllers are used to enable the service of the vehicle service module indicated by the call instruction after receiving the call instruction from the accident handling function module.

2. The accident handling system according to claim 1, characterized in that, The plurality of domain controllers further includes: one or more sub-domain controllers, each of the sub-domain controllers managing at least a portion of the functions of the vehicle; The system further includes a gateway, which is used to establish a communication connection between the master domain controller and the sub-domain controllers.

3. The accident handling system according to claim 2, characterized in that, The one or more domain controllers include: a body domain controller and a cockpit domain controller, wherein the body domain controller is used to manage the functions of the vehicle body and the cockpit domain controller is used to manage the functions of the vehicle cockpit.

4. The accident handling system according to any one of claims 1 to 3, characterized in that, The vehicle service module associated with vehicle accident handling includes one or more of the following: A fuel cut-off service module is used to stop the fuel supply to the vehicle after an accident, so as to shut down the vehicle. An accident braking service module is used to perform braking control on the vehicle after an accident occurs. Hazard warning light activation service module, which is used to activate the hazard warning lights of the vehicle; A warning sign projection service module, which is used to project warning signs around the vehicle; A warning sound service module, which is used to emit warning sounds; A rescue service module, which is used to provide rescue services; The map reporting service module is used to report maps that indicate the location of the vehicle. The traffic system reporting service module is used to report vehicle accident information to the traffic system.

5. The accident handling system according to any one of claims 1 to 3, characterized in that, The system further includes a collision sensor, which sends an accident trigger signal to the domain controller after detecting a collision involving the vehicle. The overall domain controller is used to receive the accident trigger signal sent by the collision sensor; And / or, the system further includes: an incident button, the incident button being used to send an incident trigger signal to the main domain controller after a trigger operation is detected. The main domain controller is used to receive the accident trigger signal sent by the accident button.

6. An accident handling method, characterized in that, The method, applied to the accident handling system as described in any one of claims 1-5, comprises: The operation layer of the vehicle's main domain controller receives an accident trigger signal. In response to the accident trigger signal, the accident trigger service module of the service layer of the vehicle's main domain controller sends a call instruction to one or more domain controllers through the accident handling function module. The call instruction is used to instruct the invocation of the vehicle service module associated with vehicle accident handling. Upon receiving a call instruction from the accident handling function module, the one or more domain controllers activate the service of the vehicle service module indicated by the call instruction.

7. An accident handling device, characterized in that, Applied to domain controllers, including: A memory on which computer programs are stored; A processor for executing the computer program in the memory to implement the steps of the method of claim 6.

8. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the method of claim 6.

9. A vehicle, characterized in that, Includes the accident handling system as described in any one of claims 1-5.

Images