WO2024120055A1

WO2024120055A1 - Vehicle emergency call recovery method and system, electronic device, and storage medium

Info

Publication number: WO2024120055A1
Application number: PCT/CN2023/127686
Authority: WO
Inventors: 黄志强
Original assignee: 锐凌无线有限责任公司; 锐凌无线通讯科技(深圳)有限公司
Priority date: 2022-12-05
Filing date: 2023-10-30
Publication date: 2024-06-13

Abstract

Disclosed are a vehicle emergency call (eCall) recovery method and system, an electronic device, and a storage medium. The method comprises: acquiring call data in an eCall system, the call data comprising a call state before call interruption of the eCall system; determining a current call mode on the basis of the call state; and performing call processing on a rescue platform in the eCall system on the basis of the call mode.

Description

Vehicle emergency call recovery method, system, electronic device and storage medium

Citation of Related Applications

This disclosure claims all rights and interests in the invention patent application with application number 202211551471.2, filed with the State Intellectual Property Office of the People's Republic of China on December 5, 2022, and with the invention name "Vehicle Emergency Call Recovery Method, System, Electronic Device and Storage Medium", and incorporates its entire contents into this disclosure by reference.

field

The present disclosure generally relates to the field of communication technology, and more particularly to a method, system, electronic device and storage medium for recovering a vehicle emergency call.

background

Since the 1990s, cars and communications have come together, and cars have been equipped with mobile communication devices based on 2G, 3G, 4G and 5G. With these devices, services such as navigation and information forecasting based on communication capabilities have gradually been realized. After having 2G cellular communication capabilities, intelligent transportation has adopted an on-board emergency call platform (emergency Call, abbreviated as eCall, also often called "emergency rescue") to solve traffic safety. The core idea of eCall is to use the on-board satellite positioning platform to obtain the location information of the vehicle. After the accident occurs, the sensor detection triggers an automatic alarm or the user manually initiates an emergency call to alarm. While establishing a voice call, the vehicle-related data is automatically sent to the rescue center PSAP (public safety answering point), so that the rescue center can quickly locate the accident vehicle and organize rescue.

The main network elements of the eCall system include the cellular network that supports circuit domain voice services, the IVS (in-vehicle system, also known as the vehicle-mounted station) that supports the eCall function, and the PSAP (public safety answering point, i.e., rescue platform) that supports the eCall function. Each network element device completes the eCall-related business functions through message interaction.

In the related art, an eCall is initiated when a vehicle accident occurs. However, if during a certain link of the entire eCall processing process, such as call initiation, vehicle-related data transmission and reception, voice communication, etc., If some abnormalities occur in IVS or PSAP (such as software abnormalities or hardware abnormalities leading to soft reset or hard reset), there is no relevant mechanism to ensure the recovery of eCall, and the call cannot be quickly restored, which poses a potential risk to the entire eCall function and delays the implementation of rescue.

Overview

In a first aspect, the present disclosure provides a method for recovering a vehicle emergency call, which is applied to a vehicle-mounted platform and includes:

Acquire call data in the eCall system, the call data including a call state before the call of the eCall system is interrupted;

Based on the call status, determine the current call mode; and

Based on the calling mode, call processing is performed on the rescue platform in the eCall system.

In some embodiments, determining the calling mode based on the calling state includes:

When the call status is in progress, determining the call mode is to determine whether the vehicle data in the call data is successfully sent to the rescue platform, if it is successfully sent, waiting for the rescue platform to call back according to the call data, if it is not successfully sent, initiating a call to the rescue platform according to the call data;

When the call state is in progress, determining the call mode is to initiate a call to the rescue platform according to the call data; and

When the call state is waiting for callback, the call mode is determined to be waiting for callback by the rescue platform according to the call data.

In some embodiments, the waiting for a call back from the rescue platform according to the call data includes:

Start its own timer;

Within the preset time period set by the timer, the call back from the rescue platform is automatically answered.

In some embodiments, after performing call processing on the target platform in the eCall system based on the call mode, the method further includes:

The data obtained after call processing is stored in the non-erasable storage memory.

In a second aspect, the present disclosure provides a method for recovering a vehicle emergency call, which is applied to a rescue platform and includes:

Acquire call data in the eCall system, wherein the call data includes a call state before the call of the eCall system is interrupted;

Based on the call status, determine the current call mode; and

Based on the calling method, a call back process is performed on the vehicle-mounted platform in the eCall system.

In some embodiments, determining the current calling mode based on the calling state includes:

When the call state is in the process of initiating a call or in the process of speaking, determining the call mode is to initiate a callback to the vehicle-mounted platform according to the call data; and

When the call state is not in the calling state or the talking state, the calling mode is determined to be waiting for the vehicle-mounted platform to initiate the call.

In some embodiments, the calling back processing to the vehicle-mounted platform in the eCall system based on the calling mode includes:

A callback call is initiated to the vehicle-mounted platform according to the call data to establish a call connection with the vehicle-mounted platform.

In some embodiments, after initiating a callback call to the vehicle-mounted platform according to the call data to establish a call connection with the vehicle-mounted platform, the method further includes:

determining whether the vehicle data in the call data is successfully received;

If not, a request message is sent to the vehicle-mounted platform, so that after the vehicle-mounted platform obtains the request message, the vehicle data is sent to the rescue platform.

In a third aspect, the present disclosure provides a vehicle emergency call recovery system, which includes: a vehicle-mounted platform and a rescue platform;

The vehicle-mounted platform is configured to obtain call data in the eCall system, the call data including the call status of the eCall system before the call is interrupted; determine its current call mode based on the call status; and perform call processing on the rescue platform in the eCall system based on the call mode; and

The rescue platform is configured to obtain call data in the eCall system, wherein the call data The method comprises the following steps: determining a call state before the eCall system call is interrupted; determining a current call mode based on the call state; and performing a call back process on the vehicle-mounted platform in the eCall system based on the call mode.

In a fourth aspect, the present disclosure provides an electronic device, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

The memory is configured to store a computer program; and

The processor is configured to execute the program stored in the memory to implement the vehicle emergency call recovery method described in the present disclosure.

In a fifth aspect, the present disclosure provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the vehicle emergency call recovery method described in the present disclosure.

In certain implementation schemes, when an eCall system interruption occurs, the vehicle-mounted platform can automatically determine the call mode based on the call status in the call data through the call data in the eCall system, and process the call to the rescue platform based on the determined call mode, thereby achieving rapid call recovery after the interruption without waiting for manual operation, thereby improving the safety of the vehicle during driving.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

In order to more clearly illustrate the technical solution of the embodiment of the present disclosure, the drawings required for use in the embodiment 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 labor.

FIG1 is a structural diagram of a vehicle emergency call recovery system provided by an embodiment of the present disclosure;

FIG2 is a flow chart of a method for restoring a vehicle emergency call provided by an embodiment of the present disclosure;

FIG3 is a flow chart of a method for restoring a vehicle emergency call provided by another embodiment of the present disclosure;

FIG4 is a flow chart of a method for restoring a vehicle emergency call provided by another embodiment of the present disclosure;

FIG5 is a flow chart of a method for restoring a vehicle emergency call provided by yet another embodiment of the present disclosure; and

FIG. 6 is a structural diagram of an electronic device provided in an embodiment of the present disclosure.

Details

In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

The present disclosure provides a vehicle emergency call recovery system. In certain embodiments, referring to FIG1 , the vehicle emergency call recovery system includes a vehicle-mounted platform and a rescue platform; wherein:

The vehicle-mounted platform is configured to obtain call data in the eCall system, the call data including the call status of the eCall system before the call is interrupted; determine its current call mode based on the call status; and perform call processing on the rescue platform in the eCall system based on the call mode;

The rescue platform is configured to obtain call data in the eCall system, wherein the call data includes a call status before the call of the eCall system is interrupted; determine its own current call mode based on the call status; and perform a call back process to the vehicle-mounted platform in the eCall system based on the call mode.

The vehicle emergency call recovery method of the embodiment of the present disclosure may be executed by a server, or by a terminal, or by both a server and a terminal. So it is executed by the client installed on it.

Taking the terminal executing the vehicle emergency call recovery method of the embodiment of the present disclosure as an example, FIG. 2 is a flow chart of an optional vehicle emergency call recovery method according to the embodiment of the present disclosure. As shown in FIG. 2, the process of the method may include the following steps:

Step 201: Acquire call data in the eCall system, where the call data includes the call status before the call is interrupted in the eCall system;

Step 202: Determine the current calling mode based on the calling state; and

Step 203: Perform call processing on the rescue platform in the eCall system based on the call mode.

In certain embodiments, call data before the interruption is stored in the in-vehicle platform's non-erasable storage memory, so that after the eCall system is interrupted, the in-vehicle platform can obtain the call data from the in-erasable storage memory.

In some implementation schemes, call data includes the call status before the eCall system call is interrupted, and may also include call mode, MSD (eCall minimum set of data) data information, MSD sending status, etc.

In certain embodiments, the call status includes in-call, initiating a call, and waiting for callback. The call mode includes manual call and automatic call. The MSD data message includes, but is not limited to, information such as vehicle location, driving direction, vehicle license plate and model, and number of passengers.

In certain implementation schemes, when the call status before the interruption of the vehicle-mounted platform is different, the calling method adopted is also different.

In some embodiments, based on the call state, determining the call mode includes:

When the call state is waiting for callback, the calling mode is determined as follows: The data is waiting for the call back from the rescue platform.

In certain embodiments, the vehicle-mounted platform can directly initiate a call to the rescue platform when the call status is in progress, speeding up the establishment of a call connection with the rescue platform, so that the vehicle-mounted platform can send a rescue signal in time. When the call status is waiting for callback, the rescue platform is waited for to be called back based on the call data, so that the connection is established in time after the rescue platform calls back to the vehicle-mounted platform. When the call status is in progress, it means that a connection has been established with the rescue platform before the interruption, and by judging whether the vehicle data has been successfully sent to the rescue platform, if it has been successfully sent, it waits for the rescue platform to call back, and if it has not been successfully sent, it initiates a call to the rescue platform to establish a call connection.

In some embodiments, waiting for a call back from the rescue platform according to the call data includes:

Start its own timer; and

In certain implementation schemes, by starting a timer, if the rescue platform calls back the vehicle-mounted platform within a preset time period, the vehicle-mounted platform can automatically answer the call, thereby establishing a call connection with the rescue platform without manual operation, thereby ensuring the safety of the passengers.

In certain implementation schemes, after determining the calling mode, the vehicle-mounted platform processes the call to the rescue platform, thereby being able to automatically process the call to the rescue platform and quickly resume the call after interruption without waiting for manual operation, thereby improving the safety of the vehicle during driving.

In certain implementations, by storing the data obtained after call processing in a non-erasable storage memory, the data in the non-erasable storage memory is updated. By updating the data in the non-erasable storage memory in real time, the call data before the interruption can be obtained in time when an interruption occurs next time, so that the eCall call can be quickly restored.

The vehicle emergency call recovery method provided by the present invention is based on the eCall technical specification, and focuses on proposing a vehicle emergency call self-recovery method. Through this method, when certain abnormalities occur in IVS or PSAP, such as software abnormalities or hardware abnormalities, resulting in soft reset or hard reset, causing eCall interruption, the eCall can be quickly self-recovered and the relevant processing flow can be continued, thereby improving robustness and ensuring that emergency rescue can be responded to and processed in a timely manner.

In certain embodiments, the vehicle emergency call recovery method provided by the present disclosure, referring to FIG. 3 , includes the following steps on the IVS side:

First, IVS is successfully started (regardless of abnormal soft reset, hard reset or normal startup);

Second, read the non-erasable storage memory to obtain the latest stored eCall call-related data, such as call progress, manual call or automatic call, MSD data information, MSD sending status, etc.

Third, the call process is in the process of initiating a call, in a conversation, or waiting for a callback. If the eCall call is in a conversation, jump to step 4; if it is in the process of initiating a call, jump to step 5; if it is waiting for a callback, jump to step 6; if there is no call, jump to step 10;

Fourth, determine whether the MSD data has been sent successfully, if not, jump to step 5, if yes, jump to step 6;

Fifth, immediately initiate an eCall call and perform relevant processing according to the stored call data; then jump to step eight;

Sixth, immediately enter eCall call callback related processing according to the stored call data, such as starting the T9 timer, setting automatic answering, etc.;

7. Process PSAP callback and perform related eCall processing;

Eighth, eCall call related processing, and timely store the relevant call data into the non-erasable storage memory at each key processing link (such as call initiation, call connection, MSD sending success, timer status update, etc.);

Ninth, the eCall call ends normally, and the relevant call data is stored in the non-erasable storage memory in a timely manner; and

Tenth, there is no eCall call being processed or the call has been normally ended, waiting for the IVS system to manually or automatically initiate an eCall and perform related eCall call processing.

Based on the same concept, the present disclosure provides a method for restoring a vehicle emergency call. The specific implementation of the method can be found in the description of the method embodiment part, and the repeated parts will not be repeated. As shown in FIG4, the method mainly includes:

Step 401: Acquire call data in the eCall system, where the call data includes the call status before the call is interrupted in the eCall system;

Step 402: Determine the current calling mode based on the calling state; and

Step 403: Call back the vehicle-mounted platform in the eCall system based on the calling method.

In some embodiments, the call data before the interruption is stored in the non-erasable storage memory of the rescue platform, so that after the eCall system is interrupted, the rescue platform can obtain the call data from the non-erasable storage memory.

In certain implementation schemes, when the calling state of the rescue platform before the interruption is different, the calling manner adopted is also different.

In some embodiments, based on the call state, determining the current call mode includes:

In certain implementation schemes, the call mode of the rescue platform after the interruption is determined by the call state between the rescue platform and the vehicle-mounted platform before the interruption, so that the call recovery can be performed more quickly and in a more targeted manner.

In certain implementation schemes, when an eCall system interruption occurs, the rescue platform can automatically determine the call mode based on the call status in the call data through the call data in the eCall system, and process the call to the vehicle platform based on the determined call mode, thereby achieving rapid call recovery after the interruption without waiting for manual operation, thereby improving the safety of the vehicle during driving.

In some embodiments, performing a call back process on the vehicle-mounted platform in the eCall system based on the calling mode includes:

In certain embodiments, after determining the calling mode of the rescue platform, a callback is initiated to the vehicle-mounted platform based on the stored calling data, so that after the vehicle-mounted platform receives the callback, a call connection is established with the rescue platform, thereby resuming the call between the two.

determining whether the vehicle data in the call data is successfully received;

In certain embodiments, by determining whether the rescue platform has successfully received the vehicle data, if the vehicle data has not been successfully received, a request message is sent to the vehicle-mounted platform, and the vehicle-mounted platform sends the vehicle data to the rescue platform based on the obtained request message, thereby realizing call recovery between the rescue platform and the vehicle-mounted platform.

In certain embodiments, the vehicle emergency call recovery method provided by the present disclosure, referring to FIG. 5 , includes the following steps on the PSAP side:

First, the PSAP is successfully started (regardless of abnormal soft reset, hard reset or normal start);

Second, read the non-erasable storage memory to obtain the latest stored eCall call-related data, such as call progress, MSD data information, MSD reception status, etc.

Third, whether the call process is in the process of initiating a call or in a call. If the eCall call is in the process of initiating a call or in a call, jump to step 4. If there is no call, jump to step 10.

Fourth, immediately initiate an eCall callback call based on the stored call data, call back the IVS and perform related call processing, and update and store the call process data (such as call initiation, call connection, etc.) in a non-erasable storage memory in a timely manner;

Fifth, according to the stored MSD information, whether the MSD has been successfully received, if not, jump to step 6, if yes, jump to step 7;

Sixth, request IVS to send MSD information; then jump to step 8;

Seventh, there is no need to request IVS to send MSD information; then jump to step 8;

Eighth, eCall call related processing, and timely store the relevant call data into the non-erasable storage memory at each key processing link (such as voice call, MSD reception status, timer status update, etc.);

Tenth, if no eCall call is being processed or the call has been normally ended, wait for IVS to initiate an eCall call connection request and perform related eCall call processing.

Based on the same concept, the present disclosure also provides an electronic device, as shown in FIG6 , the electronic device mainly includes: a processor 601, a memory 602 and a communication bus 603, wherein the processor 601 and the memory 602 communicate with each other through the communication bus 603. The memory 602 stores a program executable by the processor 601, and the processor 601 executes the program stored in the memory 602 to implement the following steps:

Based on the call status, determine the current call mode;

Performing call processing on the rescue platform in the eCall system based on the call mode. Or,

Based on the call status, determine the current call mode;

The communication bus 603 mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 603 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in FIG6 , but it does not mean that there is only one bus or one type of bus.

The memory 602 may include a random access memory (RAM) or a non-volatile memory, such as at least one disk storage. In some embodiments, the memory may also be at least one storage device located away from the processor 601.

The above-mentioned processor 601 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., and can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

In certain embodiments, the electronic device of the present disclosure may be a module capable of realizing a communication function or a terminal device including the module, etc., and the terminal device may be a mobile terminal or a smart terminal. The mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a laptop computer, etc.; the smart terminal may specifically be a terminal including a wireless communication module such as a smart car, a smart watch, a shared bicycle, a smart cabinet, etc.; the module may specifically be a wireless communication module, such as any one of a 2G communication module, a 3G communication module, a 4G communication module, a 5G communication module, and a NB-IOT communication module, etc.

The present disclosure further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed on a computer, the computer executes the vehicle emergency call recovery method described in the present disclosure.

In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instruction is loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction may be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium, for example, a computer instruction is transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape, etc.), an optical medium (e.g., a DVD) or a semiconductor medium (e.g., a solid-state hard disk), etc.

It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

The vehicle emergency call recovery method is applied to the vehicle platform, which includes:

Acquire call data in the eCall system, the call data including a call state before the call of the eCall system is interrupted;

Based on the call status, determine the current call mode; and

Based on the calling mode, call processing is performed on the rescue platform in the eCall system.
The vehicle emergency call recovery method according to claim 1, wherein the determining the calling mode based on the calling state comprises:

When the call status is in progress, determining the call mode is to determine whether the vehicle data in the call data is successfully sent to the rescue platform, if it is successfully sent, waiting for the rescue platform to call back according to the call data, if it is not successfully sent, initiating a call to the rescue platform according to the call data;

When the call state is in progress, determining the call mode is to initiate a call to the rescue platform according to the call data; and

When the call state is waiting for callback, the call mode is determined to be waiting for callback by the rescue platform according to the call data.
The vehicle emergency call recovery method according to claim 2, wherein the waiting for the rescue platform to call back according to the call data comprises:

Start its own timer; and

Within the preset time period set by the timer, the call back from the rescue platform is automatically answered.
The vehicle emergency call recovery method according to any one of claims 1 to 3, wherein after the call processing is performed on the target platform in the eCall system based on the call mode, it also includes:

The data obtained after call processing is stored in the non-erasable storage memory.
The vehicle emergency call recovery method is applied to the rescue platform, which includes:

Acquire call data in the eCall system, the call data including a call state before the call of the eCall system is interrupted;

Based on the call status, determining the current call mode; and

Based on the calling method, a call back process is performed on the vehicle-mounted platform in the eCall system.
The vehicle emergency call recovery method according to claim 5, wherein the determining of the current calling mode based on the calling state comprises:

When the call state is in the process of initiating a call or in the process of speaking, determining the call mode is to initiate a callback to the vehicle-mounted platform according to the call data;

When the call state is not in the calling state or the talking state, the calling mode is determined to be waiting for the vehicle-mounted platform to initiate the call.
The vehicle emergency call recovery method according to claim 5 or 6, wherein the call back processing to the vehicle platform in the eCall system based on the call mode includes:

A callback call is initiated to the vehicle-mounted platform according to the call data to establish a call connection with the vehicle-mounted platform.
The vehicle emergency call recovery method according to claim 7, wherein after initiating a callback call to the vehicle-mounted platform according to the call data to establish a call connection with the vehicle-mounted platform, it also includes:

determining whether the vehicle data in the call data is successfully received;

If not, a request message is sent to the vehicle-mounted platform, so that after the vehicle-mounted platform obtains the request message, the vehicle data is sent to the rescue platform.
A vehicle emergency call recovery system, comprising: a vehicle-mounted platform and a rescue platform;

The vehicle-mounted platform is configured to obtain call data in the eCall system, wherein the call data includes a call status before the eCall system call is interrupted; based on the call status, determine Determine its current calling mode; perform call processing on the rescue platform in the eCall system based on the calling mode; and

The rescue platform is configured to obtain call data in the eCall system, wherein the call data includes a call status before the call of the eCall system is interrupted; determine its own current call mode based on the call status; and perform a call back process on the vehicle-mounted platform in the eCall system based on the call mode.
An electronic device, comprising: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

The memory is configured to store a computer program; and

The processor is configured to execute the program stored in the memory to implement the vehicle emergency call recovery method described in any one of claims 1 to 4 or the vehicle emergency call recovery method described in any one of claims 5 to 8.
A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the vehicle emergency call recovery method described in any one of claims 1 to 4 or the vehicle emergency call recovery method described in any one of claims 5 to 8.