Emergency call system and vehicle
By designing separate service modules and emergency call modules, the emergency call system can dynamically adjust emergency call services according to the regulatory information and user needs of different regions, solving the usage limitations caused by regional differences in the existing system, and achieving higher adaptability and flexibility.
Patent Information
- Application Number
- CN202411991897.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-30
- Publication Date
- 2025-04-11
AI Technical Summary
Due to the differences in communication protocols, data formats and triggering conditions in different regions, existing emergency call systems must be developed separately for each region, which has limitations in use.
An emergency call system is designed, including a service service module and an emergency call module. The service service module is equipped with an emergency call interface corresponding to call regulatory information in multiple different regions. An emergency call programming interface is installed in the emergency call module. Through the separate design of these modules, emergency call services can be dynamically adjusted according to target regulatory information and call definition requirements.
The multi-regional adaptation of the emergency call system and dynamic adjustment of user needs are achieved, avoiding the limitations of separate development and improving the system's adaptability and flexibility.
Smart Images
Figure CN119814927A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle technology, and in particular to an emergency call system and a vehicle. Background Art
[0002] With the popularity of automobiles around the world, a rapid response mechanism in emergency situations is particularly important. At present, the eCall (emergency call) system on vehicles has become an important safety technology. The system can automatically call emergency services when a vehicle accident occurs and transmit key information, including the location of the vehicle, the time of the accident, and the status of the vehicle. The application of this system significantly improves the speed of accident response and helps reduce casualties caused by accidents.
[0003] However, due to the significant differences in communication protocols, data formats, trigger conditions, etc. between emergency call systems in different regions, the eCall system must comply with various regulatory requirements and the call definition requirements required by users. At present, in order to adapt to these differentiated eCall regulatory requirements and specific call definition requirements, vehicle manufacturers usually develop a separate emergency call system for each region and the corresponding users in each region. This means that vehicles will be equipped with specific eCall systems according to the regions where they are sold and used, so that the eCall system can only support specific regions and specific users, which has great limitations in use.
[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0005] The main purpose of the present application is to provide an emergency call system and a vehicle, aiming to solve the technical problem that conventional emergency call systems have usage limitations.
[0006] To achieve the above-mentioned purpose, the present application proposes an emergency call system, which includes a business service module and an emergency call module, wherein the business service module is provided with an emergency call interface corresponding to call regulation information of multiple different regions, and the emergency call module is provided with an emergency call programming interface;
[0007] The business service module is used to call the target emergency call interface according to the read target regulatory information, and execute the target emergency call service corresponding to the trigger instruction in the target emergency call interface according to the trigger instruction;
[0008] The emergency call module establishes a communication connection with the business service module through the emergency call programming interface;
[0009] The emergency call module is used to pass the incoming call definition requirements to the business service module through the emergency call programming interface;
[0010] The business service module is also used to adjust the emergency call service in the emergency call interface corresponding to the call definition requirement according to the call definition requirement.
[0011] In one embodiment, the business service module is provided with a positioning management module and a configuration management module;
[0012] A positioning management module is used to determine the target area where the target vehicle belonging to the emergency call system is located;
[0013] The configuration management module is used to obtain target regulatory information corresponding to the target area.
[0014] In one embodiment, the trigger instruction includes a call dialing instruction, the target emergency call service includes a call dialing service, the service service module is further provided with a call state management module and a vehicle condition diagnosis module, and the emergency call module is provided with a system state management module;
[0015] A call status management module is used to call a target emergency call interface according to target regulatory information;
[0016] A system status management module, for generating an executable call instruction when detecting that the emergency call system is in an operating state, and sending the executable call instruction to the vehicle condition diagnosis module through the emergency call programming interface;
[0017] The vehicle condition diagnosis module is used to generate a call dialing instruction according to the executable call instruction when detecting that the target vehicle triggers the emergency call operation;
[0018] The call state management module is also used to execute the call dialing service corresponding to the call dialing instruction in the target emergency call interface according to the call dialing instruction.
[0019] In one embodiment, the emergency call module is further provided with a call state switching module;
[0020] A call state switching module, used to transfer a call state switching instruction to a call state management module through an emergency call programming interface;
[0021] The call state management module is also used to execute the call state service corresponding to the call state switching instruction in the target emergency call interface according to the call state switching instruction.
[0022] In one embodiment, the configuration management module is further used to:
[0023] According to the call regulation information corresponding to each region, multiple call actions related to each call regulation information are classified to obtain multiple call action subcategories; and,
[0024] Adjust the corresponding emergency call service according to the incoming call definition requirements.
[0025] In one embodiment, the configuration management module is further used to:
[0026] After determining the call logics that can be realized by the combination of various call actions, each call logic is classified based on the call regulation information corresponding to each region to obtain multiple call logic subclasses.
[0027] In one embodiment, the business service module is further provided with an emergency call regulation module;
[0028] The configuration management module is also used to set interfaces corresponding to each region in the emergency call regulations module, and then respectively compile multiple call logic subclasses into the interfaces corresponding to the regions to which the call logic subclasses belong, and encapsulate each interface to form emergency call interfaces corresponding to each region in the emergency call regulations module.
[0029] In one embodiment, each region includes a first region, a second region, and a third region, and the configuration management module is specifically used for:
[0030] Generate an action abstract class, compile the obtained multiple call actions into the action abstract class, and obtain the total call action class;
[0031] Set a first action abstract subclass inherited from the general call action class, and according to the call regulations information, compile the call actions that can be executed in all regions into the first action abstract subclass to obtain a general call action subclass;
[0032] Set a second action abstract subclass, a third action abstract subclass and a fourth action abstract subclass inherited from the general call action subclass, and according to each call regulation information, compile the call actions that can be executed in the first region that are different from those in the second region and / or the third region into the second action abstract subclass to obtain the first region call action subclass; and
[0033] Compile the call actions that can be executed in the second region, which are different from those in the first region and / or the third region, into the third action abstract subclass to obtain the second region call action subclass; and
[0034] The calling actions that can be performed in the third region, which are different from those in the first region and / or the second region, are compiled into a fourth action abstract subclass to obtain a third region calling action subclass;
[0035] The call action subclasses include a general call action subclass, a first region call action subclass, a second region call action subclass, and a third region call action subclass.
[0036] In one embodiment, the configuration management module is further used to:
[0037] Generate a logic abstract class, and compile each determined call logic into the logic abstract class to obtain the total call logic class;
[0038] Set a first logic abstract subclass inherited from the general call logic class, and according to the call regulation information, compile the call logic that can be implemented in each region into the first logic abstract subclass to obtain a general call logic subclass;
[0039] Setting a second logic abstract subclass, a third logic abstract subclass and a fourth logic abstract subclass inherited from the general call logic subclass, and according to each call regulation information, incorporating the call logic that can be implemented in the first region that is different from the second region and / or the third region into the second logic abstract subclass to obtain the first region call logic subclass; and
[0040] Incorporating the call logic that can be implemented in the second region, which is different from that in the first region and / or the third region, into the third logic abstract subclass to obtain a second region call logic subclass; and
[0041] The call logic that can be implemented in the third region, which is different from that in the first region and / or the second region, is compiled into a fourth logic abstract subclass to obtain a third region call logic subclass;
[0042] The call logic subclasses include a general call logic subclass, a first-region call logic subclass, a second-region call logic subclass, and a third-region call logic subclass.
[0043] In addition, to achieve the above objectives, the present application also proposes a vehicle, which includes the emergency call system as described above.
[0044] One or more technical solutions proposed in this application have at least the following technical effects:
[0045] An emergency call system is proposed, which includes a business service module and an emergency call module. The business service module is provided with emergency call interfaces corresponding to call regulation information of multiple different regions, and the emergency call module is provided with an emergency call programming interface; the business service module is used to call the target emergency call interface according to the read target regulation information, and execute the target emergency call service corresponding to the trigger instruction in the target emergency call interface according to the trigger instruction; the emergency call module establishes a communication connection with the business service module through the emergency call programming interface; the emergency call module is used to transfer the accessed call definition requirements to the business service module through the emergency call programming interface; the business service module is also used to adjust the emergency call service in the emergency call interface corresponding to the call definition requirements according to the call definition requirements.
[0046] In the present application, by splitting the module used to adapt to the call regulation information of different regions and the call definition requirements required by the configured users into a business service module and an emergency call module, the emergency call operation and call definition functions on the emergency call system can be separately executed and adjusted according to the corresponding requirements, thereby avoiding the problem that the conventional emergency call system can only adapt to vehicles with the same call requirements in the same area due to the mixing of the business service module and the emergency call module. The adaptability of the emergency call system to different regions and different users is improved, and the usage limitations of the emergency call system are avoided to a certain extent. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0048] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0049] Figure 1 A schematic diagram of the modules of the emergency call system for this application;
[0050] Figure 2 A schematic diagram of the specific internal structure of the emergency call system for this application;
[0051] Figure 3 This is a schematic diagram of the functional flow that can be performed by the configuration management module in the emergency call system of this application.
[0052] Description of Figure Numbers:
[0053] 10. Emergency call system; 20. Business service module; 30. Emergency call programming interface; 40. Emergency call module.
[0054] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0055] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0056] It should be noted that if the embodiments of the present application involve directional indications (such as up, down, left, right, front, back, etc.), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components in a certain specific posture. If the specific posture changes, the directional indication will also change accordingly.
[0057] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features limited to "first" and "second" may explicitly or implicitly include at least one of the features. In addition, if "and / or" or "and / or" appears in the full text, its meaning includes three parallel schemes. Taking "A and / or B" as an example, it includes scheme A, or scheme B, or a scheme that satisfies both A and B. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the ability of ordinary technicians in the field to implement. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by this application.
[0058] Based on this, the embodiment of the present application provides an emergency call system 10, referring to Figure 1 , Figure 1 It is a module diagram of the emergency call system 10 of the present invention.
[0059] In this embodiment, the emergency call system 10 includes a business service module 20 and an emergency call module 40. The business service module 20 is provided with emergency call interfaces corresponding to call regulations information of multiple different regions, and the emergency call module 40 is provided with an emergency call programming interface 30.
[0060] The business service module 20 is used to call the target emergency call interface according to the read target regulatory information, and execute the target emergency call service corresponding to the trigger instruction in the target emergency call interface according to the trigger instruction;
[0061] The emergency call module 40 establishes a communication connection with the business service module 20 through the emergency call programming interface 30;
[0062] The emergency call module 40 is used to transfer the incoming call definition requirements to the business service module 20 through the emergency call programming interface 30;
[0063] The business service module 20 is further used to adjust the emergency call service in the emergency call interface corresponding to the call definition requirement according to the call definition requirement.
[0064] It should be noted that the business service module 20 in this embodiment is used to execute the emergency call service related to the call regulation information, and the emergency call module 40 is used to interact with the user.
[0065] according to Figure 1 It can be seen that the present embodiment proposes a module that structurally separates the emergency call operations related to call regulation information and the emergency call operations related to the call definition requirements required by the user of the emergency call. The calling of the emergency call operations related to the corresponding call regulation information and the adjustment of the call definition requirements required by the user are respectively implemented through corresponding modules, thereby avoiding the problem of large workload of subsequent related emergency call operation adjustments caused by the conventional emergency call system 10 setting these two emergency call operations in one module.
[0066] At the same time, the business service module 20 in this embodiment can directly call the corresponding target emergency call interface according to the target regulatory information required in various regions, and implement emergency call operations that meet the requirements of the corresponding call regulatory information in various regions, that is, an emergency call system 10 can quickly implement emergency call operations corresponding to the call regulatory information of different regions by calling the target emergency call interface corresponding to the target regulatory information without the need for subsequent manual adaptation and program adjustment, thereby avoiding the problem of high subsequent maintenance costs caused by the need to configure multiple sets of emergency call systems 10 in different regions due to the conventional single emergency call system 10 that can only adapt to the call regulatory information of one region, and then the need to maintain multiple sets of different emergency call systems 10 in the later stage.
[0067] Furthermore, because the emergency call module 40 can interact with the user, the user can pass the call definition requirements he needs into the emergency call module 40, and then send the call definition requirements to the business service module 20 through the emergency call module 40, so that the business service module 20 can also make corresponding adjustments to the emergency call service in the emergency call interface set in the business service module 20 according to the call definition requirements, thereby realizing dynamic and flexible adjustment of the emergency call operations related to the call definition requirements required by the user in the business service module 20, avoiding the mixing of conventional emergency call operations related to call regulation information, so that the conventional emergency call system 10 can only adapt to vehicles with the same user requirements in the same area, and there are problems such as a large number of new vehicles to be transplanted and a large workload for adaptation.
[0068] Through the module structure design as described above and the functions that can be achieved by the corresponding modules, it can be obtained that the emergency call system 10 constructed in this embodiment is no longer limited in scope of use by the call regulation information corresponding to different regions and the call definition requirements required by different users compared to the conventional emergency call system 10. The single emergency call system 10 proposed based on this embodiment can be adapted to vehicles of different users in different regions, greatly broadening the application scope of the emergency call system 10 and avoiding the usage limitations of the conventional emergency call system 10.
[0069] In a feasible implementation manner, the specific internal structure of the emergency call system 10 shown in the present application can be referred to Figure 2 shown.
[0070] The business service module 20 included in the emergency call system 10 is provided with a positioning management module and a configuration management module.
[0071] The positioning management module is used to determine the target area where the target vehicle to which the emergency call system 10 belongs is located. Specifically, the positioning management module is a GPS, so it can accurately determine the target area where the target vehicle driven by the user is currently located.
[0072] The configuration management module is used to obtain the target regulatory information corresponding to the target area. Specifically, because the target area can be accurately determined by the positioning management module, the configuration management module can obtain the call regulatory information corresponding to the target area, that is, the target regulatory information, so that the emergency call interface that can adapt to the target area can be called based on the target regulatory information to perform the emergency call operation that conforms to the area.
[0073] Furthermore, the business service module 20 is also provided with a call status management module and a vehicle condition diagnosis module, and the emergency call module 40 is provided with a system status management module.
[0074] The call state management module is used to call the target emergency call interface according to the target regulatory information. Specifically, the call state management module provided in this embodiment can call the target emergency call interface adapted to the target regulatory information according to the target regulatory information determined by the configuration management module, and each emergency call service programmed in the target emergency call interface complies with the target regulatory information.
[0075] The system status management module is used to generate an executable call instruction when it is detected that the emergency call system 10 is in an operating state, and send the executable call instruction to the vehicle condition diagnosis module through the emergency call programming interface 30. Specifically, because the emergency call system 10 can only perform emergency call operations normally when it is in a normal operating state, it is necessary to perform real-time detection operations on the emergency call system 10 through the system status management module, and when it is detected that the emergency call system 10 is in an operating state that can operate normally, an executable call instruction for performing emergency call operations through the business service module 20 is generated.
[0076] The vehicle condition diagnosis module is used to generate a call dialing instruction according to the executable call instruction when it is detected that the target vehicle triggers an emergency call operation. Specifically, the vehicle condition diagnosis module is used to perform real-time detection on whether the target vehicle has a vehicle condition that requires an emergency call operation. When the vehicle condition that requires an emergency call operation is detected, it is considered that the target vehicle at this time triggers an emergency call operation, and a call dialing instruction is generated according to the accessed executable call instruction, so that the business service module 20 can perform the emergency call telephone service.
[0077] The call state management module is also used to execute the call dialing service corresponding to the call dialing instruction in the target emergency call interface according to the call dialing instruction. Specifically, the call state management module is used to execute the corresponding service in the target emergency call interface called by the configuration management module according to the corresponding instruction. For example, when the accessed instruction is a call dialing instruction, the call state management module at this time will execute the call dialing service in the called target emergency call interface, that is, the emergency call phone service, to perform the emergency call phone operation.
[0078] Furthermore, the emergency call module 40 is also provided with a call state switching module.
[0079] The call state switching module is used to transfer the call state switching instruction to the call state management module through the emergency call programming interface 30. Specifically, because there are different call requirements in the emergency call operation, such as call replay, call callback, etc., the call state switching instruction can be generated according to the call state switching set by the emergency call system 10 or the call state switching uploaded by the user, and the call state switching instruction is sent to the call state management module.
[0080] The call state management module is also used to execute the call state service corresponding to the call state switching instruction in the target emergency call interface according to the call state switching instruction. Specifically, the call state management module executes the replay emergency call telephone service corresponding to the call replay in the called target emergency call interface according to the received call state switching instruction, in the case where the call state switching instruction is a call replay, to perform the replay emergency call telephone operation; for example, in the case where the call state switching instruction is a call callback, the emergency call telephone callback service corresponding to the call callback in the called target emergency call interface is executed to perform the emergency call telephone callback operation.
[0081] In a feasible implementation, for example, if the target area where the target vehicle is located is determined to be a general area through the positioning management module, then after obtaining the target regulatory information corresponding to the business area through the configuration management module, the call state management module calls the Base business emergency call interface (i.e., the target emergency call interface) according to the target regulatory information. When the system state management module detects that the emergency call system 10 is processing the running state, an executable call instruction is generated, and the executable call instruction is sent to the vehicle condition diagnosis module. When the vehicle condition diagnosis module detects that the target vehicle triggers an emergency call operation, a call dialing instruction is generated, so that the call state management module can execute the emergency call telephone service in Base according to the call dialing instruction.
[0082] After executing the emergency call service, if a call replay instruction uploaded by the user or a call replay instruction automatically triggered by the system is received through the call state switching module, the emergency call replay service in Base is executed; if a call callback instruction uploaded by the user or a call callback instruction automatically triggered by the system is received through the call state switching module, the emergency call callback service in Base is executed.
[0083] That is, based on the target emergency call interface called, if the area where the vehicle is traveling changes, it is possible to perform emergency call operations that comply with regulatory requirements without making any changes to the emergency call system 10, that is, it is possible to flexibly and dynamically switch to emergency call operations that comply with the corresponding area without modifying the business logic in the emergency call system 10.
[0084] It should be noted that the business service module 20 in this embodiment also includes an audio management module, and the audio management module can select a corresponding call channel according to the target area where the target vehicle is located.
[0085] Specifically, a further detailed description will be given.
[0086] During the configuration process, the configuration management module is used to classify multiple call actions related to each call regulation information according to the call regulation information corresponding to each region, and obtain multiple call action subcategories; and adjust the corresponding emergency call service according to the uploaded call definition requirements.
[0087] according to Figure 2 It can be seen that a configuration management module is provided in the business service module 20 of the present embodiment, which can classify all uploaded call actions according to the call regulation information corresponding to different regions (i.e., regulatory requirements), and package the different types of call action sets obtained by classification to form multiple call action subcategories, so that in the later stage, the corresponding call action can be directly and quickly called according to the call regulation information required by the target area where the current vehicle is located to implement the corresponding emergency call operation.
[0088] At the same time, the configuration management module can also quickly modify the corresponding emergency call service according to the call definition requirements uploaded by the user, thereby realizing fast and convenient adjustment of the corresponding emergency call service.
[0089] Specifically, refer to Figure 3 As shown, assuming that there are three regions, namely, the first region, the second region and the third region, the corresponding regulatory requirements, the specific functions that the configuration management module can perform include S10 to S30:
[0090] Step S10, generating an action abstract class, compiling the obtained multiple call actions into the action abstract class, and obtaining a total call action class.
[0091] from Figure 3 It can be seen that an action abstract class will be generated first, and all the call actions uploaded by the operator will be compiled into the action abstract class. After all the call actions are compiled into the action abstract class, a general call action class IECallLawProcess will be formed.
[0092] Step S20, setting a first action abstract subclass inherited from the general call action class, and according to the call regulation information, compiling the call actions executable in all regions into the first action abstract subclass to obtain a general call action subclass.
[0093] Next, define a first action abstract subclass that inherits from the general call action class. According to the call regulation information corresponding to the three regions, the call actions that can comply with the three call regulation information are incorporated into the first action abstract subclass to obtain the general call action subclass BaseECallLawProcess, which will help to subsequently separate the interface and implementation encapsulated based on the general call action subclass, so that when the subsequent related call regulation information changes, the relevant call actions in the communication call action subclass can be improved to achieve rapid adjustment of the emergency call service that can be achieved based on the corresponding emergency call interface.
[0094] Step S30, setting a second action abstract subclass, a third action abstract subclass and a fourth action abstract subclass inherited from the general call action subclass, according to each call regulation information, the call actions that can be executed in the first region as distinguished from the second region and / or the third region are compiled into the second action abstract subclass to obtain the first region call action subclass; and, the call actions that can be executed in the second region as distinguished from the first region and / or the third region are compiled into the third action abstract subclass to obtain the second region call action subclass; and, the call actions that can be executed in the third region as distinguished from the first region and / or the second region are compiled into the fourth action abstract subclass to obtain the third region call action subclass.
[0095] based on Figure 3 From the above steps, it can be seen that assuming that the regions designed in this embodiment include the first region, the second region and the third region, in order to enable vehicles running in different regions to quickly and conveniently implement corresponding emergency call operations, this embodiment proposes to set an action abstract subclass of the emergency call service required by the call regulation information corresponding to different regions, specifically:
[0096] The second action abstract subclass, the third action abstract subclass and the fourth action abstract subclass are defined to inherit from the general call action subclass respectively, and according to the call regulations information corresponding to the first region, the second region and the third region, the call actions that can be performed by the vehicle in the first region but cannot be performed in the second and third regions are incorporated into the second action abstract subclass to obtain the first region call action subclass EUECallLawProcess; the call actions that can be performed by the vehicle in the second region but cannot be performed in the first and third regions are incorporated into the third action abstract subclass to obtain the second region call action subclass R144ECallLawProcess; the call actions that can be performed by the vehicle in the third region but cannot be performed in the second and third regions are incorporated into the fourth action abstract subclass to obtain the third region call action subclass ERAECallLawProcess, so as to realize differentiated call actions between different regions in the corresponding derived classes, and at the same time facilitate the subsequent rapid modification of the corresponding call action subclasses based on the execution requirements in different regions.
[0097] It should be noted that Figure 3 +ecall_dial(type):type, +ecall_dial_retry(type):type, +ecall_dial_back(type):type, +ecall_msd_upload(type):type and +ecall_msd_rmake(type):type are the codes corresponding to different call actions.
[0098] The configuration management module in the business service module 20 is also used for:
[0099] After determining the call logics that can be realized by the combination of the call actions, the call logics are classified based on the call regulation information corresponding to each region to obtain a plurality of call logic subclasses.
[0100] according to Figure 2 It can be seen that the configuration management module of this embodiment determines the combination logic between the uploaded call actions, obtains a variety of call logics composed of several call actions, and classifies the determined call logics according to the call regulation information corresponding to different regions (i.e., regulatory requirements), and packages the different types of call logic sets obtained by classification to form multiple call logic subclasses, so that in the later stage, it can directly and quickly call the call actions in the corresponding call logic according to the call regulation information required by the area where the current vehicle is located to realize emergency call services that comply with the call regulation information.
[0101] Specifically, refer to Figure 3As shown, the specific functions that the configuration management module can perform include S40 to S60:
[0102] Step S40, generating a logic abstract class, and compiling each determined call logic into the logic abstract class to obtain a total call logic class.
[0103] from Figure 3 It can be seen that a logic abstract class inherited from the general call action class IECallLawProcess will be defined first. The logic abstract class incorporates multiple call logics that can be combined by the call actions in the general call action class IECallLawProcess, thereby forming a general call logic class ICallStateManager.
[0104] Step S50, setting a first logic abstract subclass inherited from the general call logic class, and according to each call regulation information, compiling the call logic that can be implemented in each region into the first logic abstract subclass to obtain a general call logic subclass.
[0105] Next, define a first logic abstract subclass that inherits from the general call logic class ICallStateManager. According to the call regulation information corresponding to the three regions, the call logic that can comply with the three call regulation information is incorporated into the first logic abstract subclass to obtain the general call logic subclass BaseCallStateManager, which will help to subsequently separate the interface and implementation encapsulated based on the general call logic subclass, so that when the subsequent related call regulation information changes, the relevant call logic in the communication call logic subclass can be improved to achieve rapid adjustment of the emergency call service that can be achieved based on the corresponding emergency call interface.
[0106] Step S60, setting a second logic abstract subclass, a third logic abstract subclass and a fourth logic abstract subclass inherited from the general call logic subclass, according to each call regulation information, the call logic that can be implemented in the first region as distinguished from the second region and / or the third region is compiled into the second logic abstract subclass to obtain the first region call logic subclass; and, the call logic that can be implemented in the second region as distinguished from the first region and / or the third region is compiled into the third logic abstract subclass to obtain the second region call logic subclass; and, the call logic that can be implemented in the third region as distinguished from the first region and / or the second region is compiled into the fourth logic abstract subclass to obtain the third region call logic subclass.
[0107] based on Figure 3From the above steps, it can be seen that assuming that the regions designed in this embodiment include the first region, the second region and the third region, in order to enable vehicles running in different regions to quickly and conveniently implement corresponding emergency call operations, this embodiment proposes to set logical abstract subclasses of emergency call services required by call regulation information corresponding to different regions, specifically:
[0108] The second logic abstract subclass, the third logic abstract subclass and the fourth logic abstract subclass are defined to inherit from the general call logic subclass respectively, and according to the call regulation information corresponding to the first region, the second region and the third region, the call logic that can be executed by the vehicle in the first region but cannot be executed in the second and third regions is incorporated into the second logic abstract subclass to obtain the first region call logic subclass EUCallStateManager; the call logic that can be executed by the vehicle in the second region but cannot be executed in the first and third regions is incorporated into the third logic abstract subclass to obtain the second region call logic subclass R144CallStateManager; the call logic that can be executed by the vehicle in the third region but cannot be executed in the second and third regions is incorporated into the fourth logic abstract subclass to obtain the third region call logic subclass ERACallStateManager, so as to implement differentiated call logics between different regions in the corresponding derived classes, and at the same time facilitate the subsequent rapid modification of the corresponding call logic subclasses based on the execution requirements in different regions.
[0109] It should be noted that Figure 3 +init(type):type, +ecall_idle_state(type):type, +ecall_connecting_state(type):type, +ecall_connected_state(type):type, +ecall_end_state(type):type and +ecall_callback_state(type):type are codes corresponding to different call logics.
[0110] The business service module 20 included in the emergency call system 10 also includes an emergency call regulations module.
[0111] The configuration management module is also used to set interfaces corresponding to each region in the emergency call regulations module, and then respectively compile multiple call logic subclasses into the interfaces corresponding to the regions to which the call logic subclasses belong, and encapsulate each interface to form emergency call interfaces corresponding to each region in the emergency call regulations module.
[0112] according to Figure 2It can be seen that the business service module 20 of this embodiment is also provided with an emergency call regulations module. After the configuration management module sets the interfaces corresponding to each region in the emergency call regulations module, according to the call action subclasses formed and the call logic subclasses formed in the call status management module, according to the call actions required in each call logic subclass, each call action subclass and each call logic subclass are matched one by one, and then the corresponding call action subclass and call logic subclass are passed to the interface belonging to the corresponding region, and the interface is encapsulated to obtain an emergency call interface that can quickly respond to feasible emergency call operations in the area where the vehicle is located.
[0113] Specifically: after obtaining each call action subclass and each call logic subclass, the configuration management module will match the general call action subclass according to the call action required by the general call logic subclass, and incorporate the general call logic subclass and the general call action subclass into the corresponding interface in the emergency call regulation module to encapsulate the general emergency call interface (i.e. Figure 2 Base), according to Figure 2 It can be seen that the call logic corresponding to the emergency call service, MSD (Minimum Set of Data) upload service, emergency call replay service, emergency call callback service and MSD data management service in the universal emergency call interface and the call actions included in each call logic all belong to emergency call operations that can be implemented in various regions.
[0114] According to the call action required by the first regional call logic subclass, the first regional call action subclass is matched, the first regional call logic subclass and the first regional call action subclass are incorporated into the corresponding interface in the emergency call regulation module, and the first regional emergency call interface (i.e. Figure 2 in the EU), according to Figure 2 It can be seen that the call logic corresponding to the emergency call service, MSD upload service, emergency call replay service, emergency call callback service and MSD data management service in the first area emergency call interface and the call actions included in each call logic all belong to emergency call operations that can be implemented in all regions.
[0115] According to the call action required by the second regional call logic subclass, the second regional call action subclass is matched, and the second regional call logic subclass and the second regional call action subclass are incorporated into the corresponding interface in the emergency call regulation module to encapsulate the second regional emergency call interface (i.e. Figure 2 R144 in), according to Figure 2It can be seen that the call logics and call actions included in the emergency call service, MSD upload service and MSD data management service in the emergency call interface of the second region respectively belong to the emergency call service that can only be executed in the second region, and the call logic corresponding to the emergency call callback service and the call actions included in the call logic are all emergency call operations that can be implemented in all regions. Specifically, the emergency call service in the second area is to dial an ordinary phone, the MSD upload service is to upload through the http (hypertext transfer protocol) protocol, and the MSD data management service is data in json encoded form.
[0116] According to the call action required by the third region call logic subclass, the third region call action subclass is matched, the third region call logic subclass and the third region call action subclass are compiled into the corresponding interface in the emergency call regulation module, and the third region emergency call interface (i.e. Figure 2 ERA in Figure 2 It can be seen that the call logics and call actions included in the emergency call interface of the third region for the emergency call service, MSD upload service and MSD data management service respectively belong to emergency call operations that can only be performed in the third region, and the call logic corresponding to the emergency call callback service and the call actions included in the call logics belong to emergency call operations that can be implemented in all regions. Specifically, the emergency call service in the third region is to make calls through SMS (Short Message Service), the MSD upload service is to upload through SMS, and the MSD data management service is data in ASN encoded form.
[0117] It should be noted that the replay emergency call telephone service in the second area emergency call interface and the third area emergency call interface is an emergency call service that can be changed according to the call definition requirements required by the user. When the vehicle is in the second area or the third area, the configuration management module will receive the call definition requirements related to the replay emergency call telephone service and adjust the replay emergency call telephone service on the corresponding interface according to the call definition requirements.
[0118] The present application also provides a vehicle, which includes the emergency call system as described above.
[0119] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. An emergency call system, characterized in that: The emergency call system includes a business service module and an emergency call module, wherein the business service module is provided with emergency call interfaces corresponding to call regulation information of multiple different regions, and the emergency call module is provided with an emergency call programming interface; The business service module is used to call the target emergency call interface according to the read target regulatory information, and execute the target emergency call service corresponding to the trigger instruction in the target emergency call interface according to the trigger instruction; The emergency call module establishes a communication connection with the business service module through the emergency call programming interface; The emergency call module is used to transfer the incoming call definition requirements to the business service module through the emergency call programming interface; The business service module is further used to adjust the emergency call service in the emergency call interface corresponding to the call definition requirement according to the call definition requirement.
2. The emergency call system according to claim 1, characterized in that: The business service module is provided with a positioning management module and a configuration management module; The positioning management module is used to determine the target area where the target vehicle to which the emergency call system belongs is located; The configuration management module is used to obtain target regulatory information corresponding to the target area.
3. The emergency call system according to claim 2, characterized in that: The trigger instruction includes a call dialing instruction, the target emergency call service includes a call dialing service, the business service module is further provided with a call state management module and a vehicle condition diagnosis module, and the emergency call module is provided with a system state management module; The call state management module is used to call the target emergency call interface according to the target regulatory information; The system status management module is used to generate an executable call instruction when detecting that the emergency call system is in an operating state, and send the executable call instruction to the vehicle condition diagnosis module through the emergency call programming interface; The vehicle condition diagnosis module is used to generate a call dialing instruction according to the executable call instruction when detecting that the target vehicle triggers an emergency call operation; The call state management module is further configured to execute a call dialing service corresponding to the call dialing instruction in the target emergency call interface according to the call dialing instruction.
4. The emergency call system according to claim 3, characterized in that: The emergency call module is also provided with a call state switching module; The call state switching module is used to transfer the call state switching instruction to the call state management module through the emergency call programming interface; The call state management module is further used to execute the call state service corresponding to the call state switching instruction in the target emergency call interface according to the call state switching instruction.
5. The emergency call system according to claim 2, characterized in that: The configuration management module is also used for: According to the call regulation information corresponding to each region, multiple call actions related to each call regulation information are classified to obtain multiple call action subcategories; and According to the accessed call definition requirement, the corresponding emergency call service is adjusted.
6. The emergency call system according to claim 5, characterized in that: The configuration management module is also used for: After determining the call logics that can be realized by the combination of the call actions, the call logics are classified based on the call regulation information corresponding to each region to obtain a plurality of call logic subclasses.
7. The emergency call system according to claim 6, characterized in that: The business service module is also provided with an emergency call regulations module; The configuration management module is also used to, after setting interfaces corresponding to each region in the emergency call regulations module, respectively incorporate the multiple call logic subclasses into the interfaces corresponding to the regions to which the call logic subclasses belong, and encapsulate each of the interfaces to form emergency call interfaces corresponding to each region in the emergency call regulations module.
8. The emergency call system according to claim 6, characterized in that: The regions include a first region, a second region and a third region, and the configuration management module is specifically used for: Generate an action abstract class, compile the obtained multiple call actions into the action abstract class, and obtain a total call action class; Setting a first action abstract subclass inherited from the general call action class, and according to the call regulation information, compiling the call actions that can be executed in all regions into the first action abstract subclass to obtain a general call action subclass; Setting a second action abstract subclass, a third action abstract subclass and a fourth action abstract subclass inherited from the general call action subclass, and according to each of the call regulation information, incorporating the call actions that can be executed in the first region that are different from those in the second region and / or the third region into the second action abstract subclass to obtain a first region call action subclass; as well as, Compose the call action that can be executed in the second region, which is different from that in the first region and / or the third region, into the third action abstract subclass to obtain a second region call action subclass; as well as, Incorporating the call actions that can be executed in the third region, which are different from those in the first region and / or the second region, into the fourth action abstract subclass to obtain a third region call action subclass; The call action subclasses include the general call action subclass, the first region call action subclass, the second region call action subclass and the third region call action subclass.
9. The emergency call system according to claim 8, characterized in that: The configuration management module is also specifically used for: Generate a logic abstract class, and compile each of the determined call logics into the logic abstract class to obtain a total call logic class; Setting a first logic abstract subclass inherited from the general call logic class, and according to each of the call regulations information, incorporating the call logic that can be implemented in each region into the first logic abstract subclass to obtain a general call logic subclass; Setting a second logic abstract subclass, a third logic abstract subclass and a fourth logic abstract subclass inherited from the general call logic subclass, and according to each of the call regulation information, incorporating the call logic that can be implemented by the first region and / or the second region into the second logic abstract subclass to obtain the first region call logic subclass; as well as, Incorporating the call logic that can be implemented in the second region and is different from that in the first region and / or the third region into the third logic abstract subclass to obtain a second region call logic subclass; as well as, Incorporating the call logic that can be implemented in the third region, which is different from that in the first region and / or the second region, into the fourth logic abstract subclass to obtain a third region call logic subclass; The call logic subclass includes the general call logic subclass, the first region call logic subclass, the second region call logic subclass and the third region call logic subclass.
10. A vehicle, characterized in that: The vehicle comprises an emergency call system as claimed in any one of claims 1 to 9.