Vehicle and emergency call method, apparatus and system thereof

[0001] This application is a continuation of International Application No. PCT/CN2020/137675, filed on Dec. 18, 2020, the disclosure of which is hereby incorporated by reference in its entirety.

[0002] This application relates to the field of vehicle technologies, and in particular, to a vehicle and an emergency call method, apparatus, and system thereof.

[0003] An emergency call (ECALL) system configured in a vehicle generally includes a telematics box (TBOX), and the TBOX is further connected to an airbag controller of the vehicle. The TBOX can automatically make a rescue call to an emergency rescue center after detecting a collision signal sent by the airbag controller.

[0004] However, if a mobile communication function of the TBOX is damaged due to a vehicle collision, the TBOX cannot normally make the rescue call. As a result, reliability of the emergency call system is poor.

[0005] This application provides a vehicle and an emergency call method, apparatus, and system thereof, to resolve a technical problem of poor reliability of an emergency call system of a vehicle.

[0006] In an embodiment, this application provides an emergency call system of a vehicle. The system includes an in-vehicle communication component, a mobile terminal, and a fault detection component. The fault detection component is connected to the in-vehicle communication component. The fault detection component is configured to send obtained detection information to the in-vehicle communication component. The detection information includes at least one of fault information of the vehicle and a rescue request. The in-vehicle communication component is configured to: if it is determined, based on the detection information, that the vehicle has an emergency rescue requirement, send an assistance call request to the mobile terminal through wireless communication. The mobile terminal is configured to send an emergency call request to a rescue platform based on the assistance call request.

[0007] According to the system provided in this application, even if a mobile communication function of the in-vehicle communication component is damaged, the in-vehicle communication component can indicate the mobile terminal to assist in sending the emergency call request. This effectively improves reliability of the emergency call system.

[0008] In an embodiment, the in-vehicle communication component is configured to: if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, and it is determined that the in-vehicle communication component does not meet a first call condition, send the assistance call request to the mobile terminal through wireless communication.

[0009] Correspondingly, if determining that the in-vehicle communication component meets the first call condition, the in-vehicle communication component may directly send the emergency call request to the rescue platform, without sending the assistance call request to the mobile terminal. In this way, efficiency of sending the emergency call request can be effectively improved, to ensure timely rescue, and a power consumption waste caused by sending the assistance call request to the mobile terminal can be avoided.

[0010] In an embodiment, the in-vehicle communication component is further configured to: if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, send performance information of the in-vehicle communication component to the mobile terminal through wireless communication. The mobile terminal is configured to: if it is determined, based on the performance information of the in-vehicle communication component, that the in-vehicle communication component does not meet a first call condition, send the emergency call request to the rescue platform based on the assistance call request.

[0011] When determining that the in-vehicle communication component is not capable of sending the emergency call request, the mobile terminal may send the emergency call request to the rescue platform in time, to ensure that the vehicle and a user in the vehicle can be rescued in time. In addition, if determining that the in-vehicle communication component meets the first call condition, the mobile terminal may not need to send the emergency call request. This avoids not only a waste of a battery level of the mobile terminal, but also a case that signal interference caused by simultaneous sending of emergency call requests by a plurality of components affects communication quality.

[0012] In an embodiment, the first call condition includes at least one of the following conditions. A communication status of the in-vehicle communication component meets a communication condition: the in-vehicle communication component maintains a connection to a multimedia interaction component of the vehicle: the in-vehicle communication component can obtain the fault information of the vehicle; and the in-vehicle communication component can obtain location information of the vehicle.

[0013] It should be understood that, because the emergency call request can be normally sent only when the communication status of the in-vehicle communication component meets the communication condition, the first call condition may include at least: the communication status of the in-vehicle communication component meets the communication condition.

[0014] In an embodiment, the in-vehicle communication component may be configured to: send a connection request to the mobile terminal, and after establishing a wireless connection to the mobile terminal, send the assistance call request to the mobile terminal based on the wireless connection, or broadcast the assistance call request within a target frequency band. The mobile terminal is further configured to: if the assistance call request is detected within the target frequency band, broadcast an assistance call response within the target frequency band.

[0015] The in-vehicle communication component may send the assistance call request to the mobile terminal in a plurality of different manners. This effectively improves flexibility of sending the assistance call request.

[0016] In an embodiment, the mobile terminal is further configured to send performance information of the mobile terminal to the in-vehicle communication component through wireless communication. The in-vehicle communication component is further configured to: if it is determined, based on the performance information of the mobile terminal, that the mobile terminal does not meet a second call condition, send the emergency call request to the rescue platform.

[0017] The mobile terminal may send the performance information to the in-vehicle communication component based on the assistance call request sent by the in-vehicle communication component. Alternatively, the mobile terminal obtains a request based on the performance information sent by the in-vehicle communication component, to send the performance information to the in-vehicle communication component. If determining, based on the performance information, that the mobile terminal is not capable of sending the emergency call request, the in-vehicle communication component may directly send the emergency call request to the rescue platform, to ensure timely rescue. In this scenario, if determining that the in-vehicle communication component is also not capable of sending the emergency call request (that is, the first call condition is not met), the in-vehicle communication component may still attempt to send the emergency call request, to improve a probability of successfully sending the emergency call request as much as possible.

[0018] In an embodiment, the second call condition may include: a communication status of the mobile terminal meets the communication condition, and/or a remaining battery level of the mobile terminal is greater than a battery level threshold. The communication status may be represented by signal strength. Correspondingly, the communication condition may be that the signal strength is greater than a strength threshold.

[0019] In an embodiment, the in-vehicle communication component is further configured to send rescue information to the mobile terminal through wireless communication. The mobile terminal is further configured to send the rescue information to the in-vehicle communication component through wireless communication. A target component in the mobile terminal and the in-vehicle communication component is further configured to send the obtained rescue information to the rescue platform. The target component is a component that sends the emergency call request to the rescue platform. The rescue information includes at least one of the following information: the location information of the vehicle, the fault information of the vehicle, an identifier of the rescue platform, and vehicle information of the vehicle.

[0020] In the system provided in this application, the in-vehicle communication component and the mobile terminal may further exchange the rescue information obtained by the in-vehicle communication component and the mobile terminal, to ensure that the rescue information sent by the target component to the rescue platform is complete. Further, rescue efficiency can be effectively improved.

[0021] In an embodiment, the system further includes a cockpit domain controller connected to the fault detection component. The cockpit domain controller is configured to: if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, send the assistance call request to the mobile terminal through wireless communication.

[0022] When the vehicle has the emergency rescue requirement, the in-vehicle communication component cannot send the assistance call request due to functional damage. Therefore, the cockpit domain controller is enabled to also have a function of sending the assistance call request. This ensures that when the vehicle has the emergency rescue requirement, the mobile terminal can be timely indicated to assist in sending the emergency call request, thereby effectively improving reliability of the entire system.

[0023] In an embodiment, the cockpit domain controller may be further configured to send the fault information of the vehicle to the mobile terminal through wireless communication. The mobile terminal may further send the fault information to the rescue platform, to improve rescue efficiency.

[0024] In an embodiment, an emergency call method is provided, which is applied to an in-vehicle communication component in an emergency call system. The system further includes a mobile terminal and a fault detection component. The method includes: receiving detection information sent by the fault detection component, where the detection information includes at least one of fault information of a vehicle and a rescue request; and sending an assistance call request to the mobile terminal through wireless communication if it is determined, based on the detection information, that the vehicle has an emergency rescue requirement, where the assistance call request indicates the mobile terminal to send an emergency call request to a rescue platform.

[0025] In an embodiment, if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, a process of sending the assistance call request to the mobile terminal through wireless communication may include: if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, and it is determined that the in-vehicle communication component does not meet a first call condition, sending the assistance call request to the mobile terminal through wireless communication.

[0026] In an embodiment, a process of sending the assistance call request to the mobile terminal through wireless communication may include: sending a connection request to the mobile terminal, and after establishing a wireless connection to the mobile terminal, sending the assistance call request to the mobile terminal based on the wireless connection, or broadcasting the assistance call request within a target frequency band.

[0027] In an embodiment, the method may further include: receiving, through wireless communication, performance information that is of the mobile terminal and that is sent by the mobile terminal based on the assistance call request; and sending the emergency call request to the rescue platform if it is determined, based on the performance information of the mobile terminal, that the mobile terminal does not meet a second call condition.

[0028] In an embodiment, an emergency call method is provided, and is applied to a mobile terminal in an emergency call system. The system further includes an in-vehicle communication component and a fault detection component. The method includes: receiving, through wireless communication, an assistance call request sent by the in-vehicle communication component, where the assistance call request is sent by the in-vehicle communication component after the in-vehicle communication component determines, based on detection information obtained by the fault detection component, that a vehicle has an emergency rescue requirement, and the detection information includes at least one of fault information of the vehicle and a rescue request; and sending an emergency call request to a rescue platform based on the assistance call request.

[0029] In an embodiment, a process of receiving, through wireless communication, the assistance call request sent by the in-vehicle communication component may include: receiving a connection request sent by the in-vehicle communication component, and after establishing a wireless connection to the in-vehicle communication component, receiving the assistance call request sent by the in-vehicle communication component based on the wireless connection: or receiving the assistance call request broadcast by the in-vehicle communication component within a target frequency band.

[0030] In an embodiment, the method may further include: receiving, through wireless communication, performance information that is of the in-vehicle communication component and that is sent by the in-vehicle communication component. Correspondingly, a process of sending the emergency call request to the rescue platform based on the assistance call request may include: sending the emergency call request to the rescue platform based on the assistance call request if it is determined, based on the performance information of the in-vehicle communication component, that the in-vehicle communication component does not meet a first call condition.

[0031] In an embodiment, the system further includes a cockpit domain controller that establishes the wireless connection to the mobile terminal. The method may further include: receiving the assistance call request sent by the cockpit domain controller through wireless communication.

[0032] In an embodiment, an in-vehicle communication component is provided, and is applied to an emergency call system. The system further includes a mobile terminal and a fault detection component. The in-vehicle communication component includes a programmable logic circuit and/or program instructions, and the in-vehicle communication component is configured to implement the method that is provided in the foregoing aspect and that is applied to the in-vehicle communication component.

[0033] In an embodiment, a mobile terminal is provided, and is applied to an emergency call system. The system further includes an in-vehicle communication component and a fault detection component. The mobile terminal includes a memory, a processor, and a computer program that is stored in the memory and that can run on the processor. When the processor executes the computer program, the method that is provided in the foregoing aspect and that is applied to the mobile terminal is implemented.

[0034] In an embodiment, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions, and the instructions are executed by a processor to implement the method that is applied to the in-vehicle communication component and that is provided in the foregoing aspect, or implement the method that is applied to the mobile terminal and that is provided in the foregoing aspect.

[0035] In an embodiment, a vehicle is provided. The vehicle includes: a body, and the emergency call system provided in the foregoing aspect. Both the in-vehicle communication component and the fault detection component in the emergency call system are fastened to the body, and the mobile terminal in the emergency call system can move relative to the body.

[0036] The technical solutions provided in this application include at least the following beneficial effects.

[0037] Embodiments of this application provide the vehicle and the emergency call method, apparatus, and system thereof. When determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component in the system may send the assistance call request to the mobile terminal through wireless communication. The mobile terminal may further send the emergency call request to the rescue platform based on the assistance call request.

[0038] Therefore, even if the mobile communication function of the in-vehicle communication component is damaged or a hard line between the in-vehicle communication component and another component is disconnected, the in-vehicle communication component can indicate the mobile terminal to assist in sending the emergency call request. This effectively improves reliability of the emergency call system.

[0048] To make objectives, technical solutions, and advantages of this application clearer, the following further describes implementations of this application in detail with reference to the accompanying drawings.

[0049] An embodiment of this application provides an emergency call system of a vehicle. The vehicle may be an intelligent vehicle or a connected vehicle, and the vehicle may be a new energy vehicle (for example, an electric vehicle) or a fuel vehicle. As shown in FIG. 1, the system includes an in-vehicle communication component 01, a mobile terminal 02, and a fault detection component 03.

[0050] The fault detection component 03 is connected to the in-vehicle communication component 01. The fault detection component 03 is configured to send obtained detection information to the in-vehicle communication component 01. The detection information includes at least one of fault information of a vehicle and a rescue request.

[0051] The in-vehicle communication component 01 is configured to: if it is determined, based on the detection information, that the vehicle has an emergency rescue requirement, send an assistance call request to the mobile terminal 02 through wireless communication. A wireless communication manner may include Bluetooth, wireless fidelity (Wi-Fi), or communication in a target frequency band. The target frequency band may be a rescue frequency band.

[0052] The mobile terminal 02 is configured to send an emergency call request to a rescue platform based on the assistance call request.

[0053] In an embodiment of the application, both the in-vehicle communication component 01 and the fault detection component 03 are fastened in the vehicle, but the mobile terminal 02 is not fastened in the vehicle, that is, the mobile terminal 02 can move relative to a body of the vehicle. For example, the mobile terminal 02 may be a movable device that has a communication function, such as a mobile phone, a phone watch, a notebook computer, a tablet computer, or a wearable device. The in-vehicle communication component 01 may be a module with a mobile communication function. For example, the in-vehicle communication component 01 may be a TBOX, and at least one subscriber identification module (SIM) card is installed in the TBOX. The TBOX may send the emergency call request to the rescue platform by using the SIM card.

[0054] In conclusion, an embodiment of the application provides the emergency call system of the vehicle. When determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component in the system may send the assistance call request to the mobile terminal through wireless communication. The mobile terminal may further send the emergency call request to the rescue platform based on the assistance call request. Therefore, even if the mobile communication function of the in-vehicle communication component is damaged, the in-vehicle communication component can indicate the mobile terminal to assist in sending the emergency call request. This effectively improves reliability of the emergency call system.

[0055] FIG. 2 is a schematic diagram of a structure of another emergency call system according to an embodiment of this application. As shown in FIG. 2, the emergency call system may further include a microphone 04, a speaker 05, an antenna 06, and a positioning component 07. The positioning component 07 may be a global positioning system (GPS) module. The in-vehicle communication component 01 may be separately connected to the microphone 04, the speaker 05, the antenna 06, and the positioning component 07 through a connection cable (also referred to as a hard wire). After determining that a vehicle has an emergency rescue requirement, the in-vehicle communication component 01 may send an emergency call request to a rescue platform 10 through the antenna 06. In addition, after receiving an emergency call response sent by the rescue platform 10, the in-vehicle communication component 01 may further send, to the rescue platform 10, location information of the vehicle collected by the positioning component 07. A voice call between a user (for example, a user in a vehicle) and the rescue platform 10 is implemented by using the microphone 04 and the speaker 05.

[0056] When the vehicle has the emergency rescue requirement, but the connection cable between the in-vehicle communication component 01 and at least one of the microphone 04, the speaker 05, the antenna 06, and the positioning component 07 is disconnected, the in-vehicle communication component 01 cannot normally exchange information with the rescue platform 10. However, in the system provided in an embodiment of the application, the mobile terminal 02 may be a terminal with a positioning function and a voice call function. This ensures that after the connection cable between the in-vehicle communication component 01 and another component is disconnected, the mobile terminal 02 can further normally exchange information with the rescue platform 10, thereby effectively improving rescue efficiency.

[0057] In an embodiment, as shown in FIG. 2, both the in-vehicle communication component 01 and the mobile terminal 02 may send the emergency call request to the rescue platform 10 through a base station 20. Both the in-vehicle communication component 01 and the mobile terminal 02 may establish a communication connection to the base station 20 by using an air interface network, and the base station 20 may establish a communication connection to the rescue platform 10 by using a public network. For example, both the in-vehicle communication component 01 and the mobile terminal 02 may send the emergency call request to the rescue platform 10 by using a second generation mobile communication network (2-generation mobile network, 2G), 3G, 4G, or 5G.

[0058] The rescue platform 10 may also be referred to as a rescue center. Sending the emergency call request to the rescue platform 10 may also be understood as dialing an emergency rescue call to the rescue center.

[0059] Refer to FIG. 2. In an embodiment of the application, the fault detection component 03 may include at least one of a fault detection subcomponent 031 and an emergency rescue button (which may also be referred to as an SOS button) 032. The fault detection subcomponent 031 is configured to collect fault information of the vehicle, and the emergency rescue button 032 is configured to trigger generation of a rescue request when a pressing operation is detected.

[0060] In an embodiment, the emergency rescue button 032 may be a physical button in the vehicle, or may be a virtual button displayed on a human-computer interaction interface in the vehicle. The fault detection subcomponent 031 may include at least one of the following components: an airbag controller, a temperature sensor, a smoke sensor, a speed sensor, an accelerometer, a gravity sensor, and the like. Correspondingly, the fault information may include at least one of the following information: information indicating that an airbag is ejected, a temperature in the vehicle, smoke concentration in the vehicle, a speed of the vehicle, an acceleration of the vehicle, a posture of the vehicle, and the like.

[0061] The in-vehicle communication component 01 may determine, when detecting that the detection information includes the rescue request, that the vehicle has the emergency rescue requirement. The in-vehicle communication component 01 may further determine, when detecting that the detection information meets at least one of the following conditions, that the vehicle has the emergency rescue requirement.

[0062] The conditions are that the detection information includes the information indicating that an airbag is ejected, the temperature in the vehicle is beyond a target temperature range, the smoke concentration in the vehicle is greater than a concentration threshold, the speed of the vehicle is greater than a speed threshold, the acceleration of the vehicle is greater than a speed threshold, and the posture of the vehicle is an abnormal posture (for example, the vehicle is in a rollover state).

[0063] The information indicating that an airbag is ejected may include a quantity and locations of ejected airbags. The target temperature range, the concentration threshold, the speed threshold, the speed threshold, and the abnormal posture may all be prestored in the in-vehicle communication component 01.

[0064] In an embodiment of the application, the in-vehicle communication component 01 may send the assistance call request to the mobile terminal 02 in a plurality of different manners.

[0065] In an embodiment, the in-vehicle communication component 01 may be configured to: send a connection request to the mobile terminal 02, and after establishing a wireless connection to the mobile terminal 02, send the assistance call request to the mobile terminal 02 based on the wireless connection.

[0066] For example, the in-vehicle communication component 01 may establish the wireless connection to the mobile terminal 02 through Bluetooth, Wi-Fi, near field communication (NFC), or the like.

[0067] In an embodiment, after establishing a wireless connection to the mobile terminal 02, the in-vehicle communication component 01 may further first obtain performance information of the mobile terminal 02, and detect, based on the performance information, whether the mobile terminal 02 meets a second call condition. If determining that the mobile terminal 02 meets the second call condition, the in-vehicle communication component 01 may send the assistance call request to the mobile terminal 02. If determining that the mobile terminal 02 does not meet the second call condition, the in-vehicle communication component 01 may search for another mobile terminal, and send a connection request to the another mobile terminal. Alternatively, if detecting no mobile terminal that meets the second call condition, the in-vehicle communication component 01 may directly send the emergency call request to the rescue platform 10.

[0068] The performance information of the mobile terminal 02 may include a communication status of the mobile terminal 02, and/or a remaining battery level of the mobile terminal 02. If the performance information includes the communication status of the mobile terminal 02, the second call condition may include: the communication status of the mobile terminal 02 meets a communication condition. If the performance information includes the remaining battery level of the mobile terminal 02, the second call condition may include: the remaining battery level of the mobile terminal 02 is greater than a battery level threshold.

[0069] In an embodiment, the in-vehicle communication component 01 may be configured to broadcast the assistance call request within a target frequency band. In other words, the in-vehicle communication component 01 may send the assistance call request to the mobile terminal 02 in a broadcast manner. The target frequency band may be a rescue frequency band.

[0070] Correspondingly, if the mobile terminal 02 detects the assistance call request within the target frequency band, the mobile terminal 02 may further broadcast an assistance call response within the target frequency band. The in-vehicle communication component 01 may further determine, based on the assistance call response, that the mobile terminal 02 has received the assistance call request.

[0071] In an embodiment, after detecting the assistance call response within the target frequency band, the in-vehicle communication component 01 may further establish a wireless connection to the mobile terminal 02 that broadcasts the assistance call response. For example, the wireless connection may be established through Bluetooth, Wi-Fi, NFC, or the like.

[0072] It can be learned based on the foregoing description that the in-vehicle communication component 01 may send the assistance call request to the mobile terminal 02 in a plurality of different manners. This effectively improves flexibility of sending the assistance call request.

[0073] In a first optional implementation, the in-vehicle communication component 01 may be configured to: if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, and it is determined that the in-vehicle communication component 01 does not meet a first call condition, send the assistance call request to the mobile terminal 02 through wireless communication.

[0074] Correspondingly, if determining that the in-vehicle communication component 01 meets the first call condition, the in-vehicle communication component 01 may directly send the emergency call request to the rescue platform 10, without sending the assistance call request to the mobile terminal 02. In this way, efficiency of sending the emergency call request can be effectively improved, to ensure timely rescue, and a power consumption waste caused by sending the assistance call request to the mobile terminal 02 can be avoided.

[0075] For example, in an embodiment of the application, the first call condition may include at least one of the following conditions:

• • [0076] a communication status of the in-vehicle communication component 01 meets the communication condition;
  • [0077] the in-vehicle communication component 01 maintains a connection to a multimedia interaction component of the vehicle;
  • [0078] the in-vehicle communication component 01 can obtain the fault information of the vehicle; and
  • [0079] the in-vehicle communication component 01 can obtain the location information of the vehicle.

[0080] That the communication status meets the communication condition may mean that a mobile communication function of the in-vehicle communication component 01 is normal, and signal strength of the in-vehicle communication component 01 is greater than a strength threshold. The multimedia interaction component may include at least an audio interaction component. For example, refer to FIG. 2. The audio interaction component may include the microphone 04 and the speaker 05. Certainly, the multimedia interaction component may further include an image interaction component. For example, the image interaction component may include a display and a camera.

[0081] When the vehicle has the emergency rescue requirement, if the mobile communication function of the in-vehicle communication component 01 is damaged, or the vehicle is in an area with a weak mobile communication signal, the in-vehicle communication component 01 cannot normally send the emergency call request. Therefore, if the emergency call request needs to be sent by the in-vehicle communication component 01, it needs to be ensured that at least the communication status of the in-vehicle communication component 01 meets the communication condition.

[0082] In addition, the in-vehicle communication component 01 is connected to the fault detection component 03, the multimedia interaction component, the antenna 06, and the positioning component 07 through hard wires. Therefore, when the vehicle has the emergency rescue requirement, the hard wires between the in-vehicle communication component 01 and the foregoing components may be broken or poorly connected. As a result, the in-vehicle communication component 01 cannot normally exchange information with the rescue platform 10. For example, when the connection cable between the in-vehicle communication component 01 and the positioning component 07 is broken, the in-vehicle communication component 01 cannot obtain and report location information of the vehicle. When the connection cable between the in-vehicle communication component 01 and the multimedia interaction component is broken, the in-vehicle communication component 01 cannot implement a call between a user in the vehicle and the rescue platform. Correspondingly, in an embodiment of the application, to ensure rescue efficiency, it further needs to be ensured that the in-vehicle communication component 01 remains a connection to the foregoing components.

[0083] In the foregoing first optional implementation, the mobile terminal 02 may establish a wireless connection to the in-vehicle communication component 01 in a passive connection manner. In other words, after determining, based on the detection information, that the vehicle has the emergency rescue requirement and determining that the in-vehicle communication component 01 does not meet the first call condition, the in-vehicle communication component 01 may establish a wireless connection to the mobile terminal 02, and send the assistance call request.

[0084] In a second optional implementation, the in-vehicle communication component 01 may be further configured to: if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, send performance information of the in-vehicle communication component 01 to the mobile terminal 02 through wireless communication.

[0085] The mobile terminal 02 may be configured to: if it is determined, based on the performance information of the in-vehicle communication component 01, that the in-vehicle communication component 01 does not meet the first call condition, send the emergency call request to the rescue platform based on the assistance call request.

[0086] In other words, after receiving the assistance call request, the mobile terminal 02 may first detect, based on the performance information of the in-vehicle communication component 01, whether the in-vehicle communication component 01 meets the first call condition. If determining that the in-vehicle communication component 01 does not meet the first call condition, the mobile terminal 02 may send the emergency call request to the rescue platform, to ensure that the vehicle and the user in the vehicle can be rescued in time.

[0087] In addition, if determining that the in-vehicle communication component 01 meets the first call condition, the mobile terminal 02 may not need to send the emergency call request. This avoids not only a waste of a battery level of the mobile terminal 02, but also a case that signal interference caused by simultaneous sending of emergency call requests by a plurality of components affects communication quality.

[0088] The performance information of the in-vehicle communication component 01 may include a performance parameter related to the first call condition. For example, refer to FIG. 3. The performance information of the in-vehicle communication component 01 may include at least a communication status, and may further include at least one of the following information: a connection status to the multimedia interaction component, a connection status to the fault detection component 03, and a connection status to the positioning component 07.

[0089] In the second optional implementation, before determining that the vehicle has a rescue requirement, the in-vehicle communication component 01 may already establish a wireless connection to the mobile terminal 02. For example, in this implementation, the mobile terminal 02 may actively establish a wireless connection to the in-vehicle communication component 01 through Bluetooth, Wi-Fi, NFC, or the like.

[0090] In the second optional implementation, the mobile terminal 02 may be further configured to send performance information of the mobile terminal 02 to the in-vehicle communication component 01 through wireless communication based on the assistance call request. As shown in FIG. 3, the performance information of the mobile terminal 02 may include a communication status of the mobile terminal 02 and/or a remaining battery level of the mobile terminal 02.

[0091] The in-vehicle communication component 01 is further configured to: if it is determined, based on the performance information of the mobile terminal 02, that the mobile terminal 02 does not meet the second call condition, send the emergency call request to the rescue platform 10. When determining that the mobile terminal 02 cannot normally send the emergency call request, the in-vehicle communication component 01 may directly send the emergency call request to the rescue platform 10, to ensure that the emergency call request can be sent successfully.

[0092] It can be learned from the foregoing description that, after receiving the assistance call request, the mobile terminal 02 may exchange performance information with the in-vehicle communication component 01. In addition, if the mobile terminal 02 determines that the in-vehicle communication component 01 does not meet the first call condition, and the in-vehicle communication component 01 determines that the mobile terminal 02 does not meet the second call condition, both the in-vehicle communication component 01 and the mobile terminal 02 send the emergency call request to the rescue platform 10. This can increase a probability of successfully sending the emergency call request as much as possible.

[0093] In an embodiment, for a scenario in which the in-vehicle communication component 01 meets the first call condition and the mobile terminal 02 meets the second call condition, the in-vehicle communication component 01 may send the emergency call request, and the mobile terminal 02 does not need to send the emergency call request. Alternatively, both the in-vehicle communication component 01 and the mobile terminal 02 may send the emergency call request. Alternatively, the emergency call request may be sent by a component with better communication quality in the in-vehicle communication component 01 and the mobile terminal 02. The communication quality may be determined based on a communication status, and the communication status may be represented by signal strength. Correspondingly, better communication quality may mean stronger signal strength.

[0094] In an embodiment, as shown in FIG. 3, the in-vehicle communication component 01 may be further configured to send rescue information to the mobile terminal 02 through wireless communication. The mobile terminal 02 may be further configured to send the rescue information to the in-vehicle communication component 01 through wireless communication.

[0095] A target component in the mobile terminal 02 and the in-vehicle communication component 01 may be further configured to send the obtained rescue information to the rescue platform 10.

[0096] The target component is a component that sends the emergency call request to the rescue platform 10. The rescue information obtained by the target component may include rescue information stored or collected by the target component, and rescue information sent by another component through wireless communication. For example, refer to FIG. 3. The rescue information may include at least one of the following information: location information of the vehicle, fault information of the vehicle, an identifier of the rescue platform 10, and vehicle information of the vehicle.

[0097] The identifier of the rescue platform 10 may include a telephone number of the rescue platform 10, or may further include a network address of the rescue platform 10, for example, an Internet Protocol (IP) address. The in-vehicle communication component 01 may use a Voice over Internet Protocol (VOIP) technology to communicate with the rescue platform 10. The vehicle information of the vehicle may include at least one of the following information: a vehicle identification number (VIN), fuel consumption, mileage, a vehicle model, a vehicle color, a license plate number, and the like.

[0098] It may be understood that the in-vehicle communication component 01 and/or the mobile terminal 02 may prestore the identifier of the rescue platform 10 and the vehicle information of the vehicle. The in-vehicle communication component 01 may obtain the location information of the vehicle by using the positioning component 07, and may obtain the fault information of the vehicle by using the fault detection subcomponent 031. The mobile terminal 02 may obtain the location information of the vehicle by using a positioning module configured by the mobile terminal 02.

[0099] It may be further understood that, in addition to the foregoing information, the rescue information may further include user information (for example, vehicle owner information) prestored in the in-vehicle communication component 01 and/or the mobile terminal 02. For example, the user information may include a name, a gender, an age, a height, a weight, a blood type, and the like. Alternatively, the rescue platform 10 may further establish a communication connection with a back-end server of the vehicle, and the rescue platform 10 may obtain the user information of the vehicle from the back-end server based on the vehicle information reported by the in-vehicle communication component 01 and/or the mobile terminal 02.

[0100] In the system provided in an embodiment of the application, because the in-vehicle communication component 01 and the mobile terminal 02 may exchange the rescue information obtained by the in-vehicle communication component 01 and the mobile terminal 02, it can be ensured that the rescue information sent by the target component to the rescue platform 10 is complete. Further, rescue efficiency can be effectively improved.

[0101] It may be further understood that, if the target component is the in-vehicle communication component 01, after successfully sending the emergency call request, the in-vehicle communication component 01 may further exchange multimedia data with the rescue platform 10 by using the multimedia interaction component connected to the in-vehicle communication component 01. The multimedia data indication includes audio data, or may further include image data.

[0102] If the target component is the mobile terminal 02, after successfully sending the emergency call request, the mobile terminal 02 may automatically enable a multimedia interaction module of the mobile terminal 02, and exchange multimedia data with the rescue platform 10 by using the multimedia interaction module. The multimedia interaction module may include at least a microphone and a speaker, or may further include a display and a camera.

[0103] In an embodiment, still refer to FIG. 2. The system may further include a cockpit domain controller 08 connected to the fault detection component 03. For example, the cockpit domain controller 08 may be connected to a gateway (GW) through a controller area network (CAN) bus, and the GW is connected to the fault detection component 03 through the CAN bus. In addition, the cockpit domain controller 08 further establishes a wireless connection to the mobile terminal 02. For example, the cockpit domain controller 08 may establish a wireless connection to the mobile terminal 02 through Bluetooth, Wi-Fi, NFC, or the like.

[0104] The cockpit domain controller 08 is configured to: if it is determined, based on the detection information, that the vehicle has the emergency rescue requirement, send the assistance call request to the mobile terminal 02 through wireless communication.

[0105] When the vehicle has the emergency rescue requirement, the in-vehicle communication component 01 cannot send the assistance call request due to functional damage, or the in-vehicle communication component 01 cannot detect that the vehicle has the emergency rescue requirement because a connection cable between the in-vehicle communication component 01 and the fault detection component 03 is disconnected. Therefore, in an embodiment of the application, the cockpit domain controller 08 is also enabled to have a function of sending the assistance call request. This can ensure that when the vehicle has the emergency rescue requirement, the mobile terminal can be timely indicated to assist in sending the emergency call request, thereby effectively improving reliability of the entire system.

[0106] In an embodiment, the cockpit domain controller 08 may further send obtained fault information of the vehicle to the mobile terminal 02. The mobile terminal 02 may send the fault information to the rescue platform 10, to improve rescue efficiency. Alternatively, the mobile terminal 02 may share the fault information with the in-vehicle communication component 01. Therefore, even if the connection cable between the in-vehicle communication component 01 and the fault detection component 03 is broken, the in-vehicle communication component 01 can provide complete rescue information to the rescue platform 10. This effectively improves rescue efficiency.

[0107] In conclusion, an embodiment of the application provides the emergency call system of the vehicle. When determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component in the system may send the assistance call request to the mobile terminal through wireless communication. The mobile terminal may further send the emergency call request to the rescue platform based on the assistance call request. Therefore, even if a mobile communication function of the in-vehicle communication component is damaged or a hard line between the in-vehicle communication component and another component is disconnected, the in-vehicle communication component can indicate the mobile terminal to assist in sending the emergency call request. This effectively improves reliability and robustness of the emergency call system.

[0108] In addition, because a connection between the mobile terminal and the in-vehicle communication component is a wireless connection, an emergency call system fault caused by a hard wire disconnection due to a vehicle collision can be avoided. In other words, the system provided in an embodiment of the application enhances connection reliability, and may reduce a probability that an emergency call request cannot be triggered because an internal component of a vehicle is damaged due to a vehicle collision, thereby improving reliability of the entire system.

[0109] An embodiment of this application further provides an emergency call method. The method may be applied to the in-vehicle communication component 01 and the mobile terminal 02 in the emergency call system provided in the foregoing embodiment. Refer to FIG. 1 and FIG. 2. The system further includes the fault detection component 03 connected to the in-vehicle communication component 01. As shown in FIG. 4A and FIG. 4B, the method provided in an embodiment of the application includes the following operations.

[0110] Operation 101: An in-vehicle communication component receives detection information sent by a fault detection component.

[0111] The detection information may include at least one of fault information of a vehicle and a rescue request. The fault detection component may include a fault detection subcomponent and an emergency rescue button. The fault detection subcomponent may be configured to collect the fault information of the vehicle, and the emergency rescue button may trigger generation of the rescue request when a pressing operation is detected.

[0112] Operation 102: A cockpit domain controller receives the detection information sent by the fault detection component.

[0113] As shown in FIG. 2, the cockpit domain controller may obtain, by using a gateway, the detection information sent by the fault detection component.

[0114] Operation 103: The in-vehicle communication component determines, based on the detection information, whether the vehicle has an emergency rescue requirement.

[0115] If the in-vehicle communication component determines that the vehicle has the emergency rescue requirement, the following operation 104 may be performed. If the in-vehicle communication component determines that the vehicle does not have the emergency rescue requirement, an operation may be ended. In an embodiment, when determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may perform operation 105 in addition to operation 104.

[0116] Operation 104: Send an assistance call request to the mobile terminal through wireless communication.

[0117] If determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may send the assistance call request to the mobile terminal through wireless communication, to indicate the mobile terminal to assist in sending an emergency call request. Then, the in-vehicle communication component may continue to perform the following operation 109.

[0118] Operation 105: Send the emergency call request to a rescue platform.

[0119] In an embodiment of the application, if determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may directly send the emergency call request to the rescue platform.

[0120] Operation 106: If determining, based on the detection information, that the vehicle has the emergency rescue requirement, the cockpit domain controller sends the assistance call request to the mobile terminal through wireless communication.

[0121] After receiving the detection information sent by the fault detection component, the cockpit domain controller may first determine, based on the detection information, whether the vehicle has the emergency rescue requirement. If it is determined that the vehicle has the emergency rescue requirement, the assistance call request may be sent to the mobile terminal. This can ensure that when the in-vehicle communication component cannot send the assistance call request or cannot detect that the vehicle has the emergency rescue requirement, the cockpit domain controller can also timely indicate the mobile terminal to assist in sending the emergency call request.

[0122] Operation 107: The mobile terminal sends the emergency call request to the rescue platform based on the received assistance call request.

[0123] After receiving the assistance call request sent by the in-vehicle communication component and/or the cockpit domain controller, the mobile terminal may send the emergency call request to the rescue platform in response to the assistance call request.

[0124] Operation 108: The mobile terminal sends rescue information to the in-vehicle communication component based on the received assistance call request.

[0125] In an embodiment of the application, the mobile terminal may further send the rescue information to the in-vehicle communication component in response to the assistance call request. The rescue information may include location information of the vehicle, vehicle information, user information, and the like.

[0126] Operation 109: The in-vehicle communication component sends the rescue information to the mobile terminal.

[0127] The in-vehicle communication component may also share the rescue information with the mobile terminal. The rescue information may include location information of the vehicle, fault information, vehicle information, and the like.

[0128] In an embodiment of the application, because the rescue information may be shared between the mobile terminal and the in-vehicle communication component, it can be ensured that a target component configured to communicate with the rescue platform can obtain and send sufficient and complete rescue information, thereby effectively improving rescue efficiency.

[0129] Operation 110: The mobile terminal sends obtained rescue information to the rescue platform.

[0130] After operation 108, if the mobile terminal successfully sends the emergency call request, for example, a rescue phone is dialed, the mobile terminal may send the obtained rescue information to the rescue platform. The rescue information obtained by the mobile terminal may include rescue information collected by the mobile terminal (for example, location information of the vehicle, vehicle information, and user information), rescue information sent by the cockpit domain controller (for example, fault information of the vehicle), and rescue information shared by the in-vehicle communication component.

[0131] Operation 111: The in-vehicle communication component sends obtained rescue information to the rescue platform.

[0132] After operation 105, if the in-vehicle communication component successfully sends the emergency call request, the in-vehicle communication component may send the obtained rescue information to the rescue platform. The rescue information obtained by the in-vehicle communication component may include rescue information collected by the in-vehicle communication component and rescue information shared by the in-vehicle communication component.

[0133] It may be understood that a sequence of operations of the emergency call method provided in an embodiment shown in FIG. 4A and FIG. 4B may be properly adjusted, and the operations may also be correspondingly added or deleted according to a situation. For example, operation 102 and operation 106 may be deleted according to a situation, that is, only the in-vehicle communication component may indicate the mobile terminal to assist in sending the emergency call request. Alternatively, operation 108 and operation 109 may be deleted according to a situation, that is, rescue information may not be shared between the mobile terminal and the in-vehicle communication component. Alternatively, the foregoing operation 111 and operation 110 may be deleted according to a situation, that is, the mobile terminal and the in-vehicle communication component may not need to report rescue information.

[0134] In an embodiment, after determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may first determine whether the in-vehicle communication component is capable of sending the emergency call request. In addition, when determining that the in-vehicle communication component cannot send the emergency call request, the in-vehicle communication component may indicate the mobile terminal to assist in sending the emergency call request. Correspondingly, refer to FIG. 5. An implementation process of operation 104 may include the following operations.

[0135] Operation 1041: Detect whether the in-vehicle communication component meets a first call condition.

[0136] In an embodiment, if determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may first detect whether the in-vehicle communication component meets the first call condition. If the in-vehicle communication component determines that the in-vehicle communication component meets the first call condition, the foregoing operation 105 may be performed, that is, the emergency call request is directly sent to the rescue platform. If the in-vehicle communication component determines that the in-vehicle communication component does not meet the first call condition, the following operations 1042a to 1046a may be performed, or the following operation 1042b may be performed.

[0137] The first call condition may include at least one of the following conditions:

• • [0138] a communication status of the in-vehicle communication component meets a communication condition;
  • [0139] the in-vehicle communication component maintains a connection to a multimedia interaction component of the vehicle;
  • [0140] the in-vehicle communication component can obtain fault information of the vehicle: and
  • [0141] the in-vehicle communication component can obtain location information of the vehicle.

[0142] Operation 1042a: Search for a surrounding mobile terminal.

[0143] If determining that the in-vehicle communication component does not meet the first call condition, the in-vehicle communication component may enable a wireless connection function of the in-vehicle communication component, and search for a surrounding mobile terminal that has the wireless connection function within a range. For example, the in-vehicle communication component may enable a Bluetooth connection function, and search for a surrounding mobile terminal that has the Bluetooth connection function, that is, search for a surrounding Bluetooth device.

[0144] Operation 1043a: Send a connection request to the found mobile terminal.

[0145] After finding a mobile terminal with the wireless connection function, the in-vehicle communication component may actively send the connection request to the mobile terminal. For example, the in-vehicle communication component may send a Bluetooth connection request to a found Bluetooth device.

[0146] Operation 1044a: Establish a wireless connection to the mobile terminal.

[0147] The mobile terminal may establish a wireless connection to the in-vehicle communication component in response to the connection request. For example, the Bluetooth device may send a Bluetooth connection response to the in-vehicle communication component in response to the Bluetooth connection request, and further establish a Bluetooth connection to the in-vehicle communication component.

[0148] Operation 1045a: Detect whether the mobile terminal meets a second call condition.

[0149] In an embodiment of the application, after establishing a wireless connection to the in-vehicle communication component, the mobile terminal may send performance information of the mobile terminal to the in-vehicle communication component. For example, the in-vehicle communication component may send a performance information obtaining request to the mobile terminal, and the mobile terminal may send the performance information of the mobile terminal to the in-vehicle communication component in response to the performance information obtaining request.

[0150] The in-vehicle communication component may further determine, based on the received performance information, whether the mobile terminal meets the second call condition. If determining that the mobile terminal does not meet the second call condition, the in-vehicle communication component may determine that the mobile terminal cannot assist in sending the emergency call request, and therefore the foregoing operation 1042a may continue to be performed, that is, another mobile terminal continues to be searched for. If the in-vehicle communication component determines that the mobile terminal meets the second call condition, operation 1046a may be performed.

[0151] The performance information of the mobile terminal may include a communication status of the mobile terminal and/or a remaining battery level of the mobile terminal. If the performance information includes the communication status of the mobile terminal, the second call condition may include: the communication status of the mobile terminal meets a communication condition. If the performance information includes the remaining battery level of the mobile terminal, the second call condition may include: the remaining battery level of the mobile terminal is greater than a battery level threshold.

[0152] Operation 1046a: Send an assistance call request to the mobile terminal based on the wireless connection.

[0153] If determining that the mobile terminal meets the second call condition, the in-vehicle communication component may determine that the mobile terminal can normally send the emergency call request, and may further send the assistance call request to the mobile terminal based on the wireless connection.

[0154] It may be understood that the foregoing operation 1045a may also be deleted according to a situation, that is, after the in-vehicle communication component establishes a wireless connection to the mobile terminal, operation 1046a may be directly performed.

[0155] Operation 1042b: Broadcast an assistance call request within a target frequency band.

[0156] If determining that the in-vehicle communication component does not meet the first call condition, in addition to sending the assistance call request in the manner shown in operation 1042a to operation 1046a, the in-vehicle communication component may directly broadcast the assistance call request within the target frequency band. The target frequency band may be a rescue frequency band.

[0157] In an embodiment, refer to FIG. 6. After operation 1042b, the mobile terminal may further perform the following operation.

[0158] Operation 112: After the assistance call request is detected within the target frequency band, detect whether the mobile terminal meets the second call condition.

[0159] The mobile terminal may monitor a signal within the target frequency band. If detecting, within the target frequency band, the assistance call request broadcast by the in-vehicle communication component, the mobile terminal may first detect whether the mobile terminal meets the second call condition. If the mobile terminal determines that the mobile terminal meets the second call condition, operation 113 may continue to be performed. If the mobile terminal determines that the mobile terminal does not meet the second call condition, the operation may be ended, that is, the mobile terminal does not need to respond to the assistance call request.

[0160] Operation 113: Determine whether an assistance call response broadcast by another mobile terminal is detected within the target frequency band.

[0161] If the mobile terminal detects, within the target frequency band, the assistance call response broadcast by the another mobile terminal, it may be determined that there is another surrounding mobile terminal that can assist in sending the emergency call request. Therefore, the operation may be ended, that is, there is no need to repeatedly respond to the assistance call request. If the mobile terminal detects no assistance call response broadcast by the another mobile terminal within the target frequency band, operation 114 may be performed.

[0162] Operation 114: Broadcast the assistance call response within the target frequency band.

[0163] If the mobile terminal detects, within the target frequency band, no assistance call response broadcast by the another mobile terminal, the assistance call response may be broadcast within the target frequency band. After detecting the assistance call response within the target frequency band, the in-vehicle communication component may determine that the mobile terminal can assist in sending the emergency call request.

[0164] In an embodiment, after detecting the assistance call response within the target frequency band, the in-vehicle communication component may further establish, by using the method shown in operation 1043a and operation 1044a, a wireless connection to the mobile terminal that broadcasts the assistance call response. After that, the mobile terminal and the in-vehicle communication component may exchange rescue information based on the wireless connection. Because a data volume of the rescue information is large, the rescue information is exchanged through the wireless connection, so that the target frequency band can be avoided from being occupied for a long time due to exchange of rescue information.

[0165] It may be understood that operation 113 may be deleted according to a situation. In other words, after detecting the assistance call request and determining that the mobile terminal meets the second call condition, the mobile terminal may broadcast the assistance call response within the target frequency band, without considering whether another mobile terminal has responded to the assistance call request. Correspondingly, a plurality of mobile terminals may assist in sending the emergency call request. Alternatively, operation 113 may be performed before operation 112. That is, when determining that another mobile terminal has not responded to the assistance call request, the mobile terminal may detect whether the mobile terminal meets the second call condition.

[0166] In an embodiment, after determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may first exchange performance information with the mobile terminal. Then, the in-vehicle communication component and the mobile terminal may determine, based on the received performance information, whether to send the emergency call request. Correspondingly, refer to FIG. 6. After operation 103, the method provided in an embodiment of the application may further include the following operations.

[0167] Operation 115: The in-vehicle communication component sends performance information of the in-vehicle communication component to the mobile terminal through wireless communication.

[0168] In an embodiment, the mobile terminal may establish a wireless connection to the in-vehicle communication component before operation 103. For example, the mobile terminal may actively establish a wireless connection to the in-vehicle communication component. Correspondingly, if determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may first send the performance information of the in-vehicle communication component to the mobile terminal based on the wireless connection.

[0169] It may be understood that operation 115 may be performed before operation 104, or may be performed simultaneously with operation 104. This is not limited in an embodiment of the application.

[0170] Operation 116: The mobile terminal sends performance information of the mobile terminal to the in-vehicle communication component through wireless communication based on the assistance call request.

[0171] After receiving the assistance call request sent by the in-vehicle communication component and/or the cockpit domain controller, the mobile terminal may send the performance information of the mobile terminal to the in-vehicle communication component in response to the assistance call request.

[0172] Operation 117: The in-vehicle communication component detects, based on the performance information of the mobile terminal, whether the mobile terminal meets the second call condition.

[0173] If the in-vehicle communication component determines that the mobile terminal does not meet the second call condition, the foregoing operation 105 may be performed, that is, the emergency call request is directly sent to the rescue platform. If determining that the mobile terminal meets the second call condition, the in-vehicle communication component may determine that the mobile terminal can send the emergency call request, and then operation 109 may be performed.

[0174] It may be understood that if determining that the mobile terminal meets the second call condition, and the in-vehicle communication component also meets the first call condition, the in-vehicle communication component may perform both operation 105 and operation 109. In other words, both the in-vehicle communication component and the mobile terminal may send the emergency call request. Alternatively, the in-vehicle communication component may perform operation 105, and may not perform operation 109. In other words, when both the in-vehicle communication component and the mobile terminal meet a condition for sending the emergency call request, only the in-vehicle communication component may send the emergency call request. Alternatively, the in-vehicle communication component may compare communication quality of the in-vehicle communication component with that of the mobile terminal. If the in-vehicle communication component determines that the communication quality of the in-vehicle communication component is better than that of the mobile terminal, operation 105 may be performed, and operation 109 is not performed. If the in-vehicle communication component determines that the communication quality of the mobile terminal is better, operation 109 may be performed, and operation 105 is not performed. That is, the emergency call request may be sent by a component with better communication quality.

[0175] Operation 118: The mobile terminal detects, based on the performance information of the in-vehicle communication component, whether the in-vehicle communication component meets the first call condition.

[0176] If the mobile terminal determines that the in-vehicle communication component does not meet the first call condition, the foregoing operation 107 may be performed, that is, the emergency call request is directly sent to the rescue platform. If determining that the in-vehicle communication component meets the first call condition, the mobile terminal may determine that the in-vehicle communication component can send the emergency call request, and then operation 108 may be performed.

[0177] It may be understood that if determining that the in-vehicle communication component meets the first call condition and the mobile terminal also meets the second call condition, the mobile terminal may perform both operation 108 and operation 107. In other words, both the in-vehicle communication component and the mobile terminal may send the emergency call request. Alternatively, the mobile terminal may compare communication quality of the mobile terminal with that of the in-vehicle communication component. If the mobile terminal determines that the communication quality of the mobile terminal is better than that of the in-vehicle communication component, operation 107 may be performed, and operation 108 is not performed. If the mobile terminal determines that the communication quality of the in-vehicle communication component is better, operation 108 may be performed, and operation 107 is not performed. That is, the emergency call request may be sent by a component with better communication quality.

[0178] It may be further understood that operation 116 and operation 117 may be deleted according to a situation, that is, only the mobile terminal may determine which component sends the emergency call request. Alternatively, operation 115 and operation 118 may be deleted according to a situation, that is, only the in-vehicle communication component may determine which component sends the emergency call request.

[0179] In conclusion, an embodiment of the application provides the emergency call method. When determining that the vehicle has the emergency rescue requirement, the in-vehicle communication component may send the assistance call request to the mobile terminal through wireless communication, and the mobile terminal may further send the emergency call request to the rescue platform based on the assistance call request. Therefore, even if the mobile communication function of the in-vehicle communication component is damaged or a hard line between the in-vehicle communication component and another component is disconnected, the in-vehicle communication component can indicate the mobile terminal to assist in sending the emergency call request. This effectively improves reliability of the emergency call system.

[0180] In addition, because a connection between the mobile terminal and the in-vehicle communication component is the wireless connection, an emergency call system fault caused by a hard wire disconnection due to a vehicle collision can be avoided. In other words, the method provided in an embodiment of the application can reduce a probability that the emergency call request cannot be triggered because an internal component of the vehicle is damaged due to a vehicle collision, and reliability is high.

[0181] It may be clearly understood by one of ordinary skilled in the art that, for a purpose of convenient and brief description, for an implementation process of the emergency call method described above, refer to the related description in the foregoing system embodiment. Details are not described herein again.

[0182] An embodiment of this application further provides an in-vehicle communication component. The in-vehicle communication component may be applied to the emergency call system provided in the foregoing embodiment. Refer to FIG. 1 and FIG. 2. The system may further include the mobile terminal 02 and the fault detection component 03.

[0183] The in-vehicle communication component 01 includes a programmable logic circuit and/or program instructions. The in-vehicle communication component 01 may be configured to implement the method performed by the in-vehicle communication component in the foregoing method embodiment.

[0184] For example, the in-vehicle communication component 01 may be configured to implement the method shown in operation 101, operation 103 to operation 105, operation 109, and operation 111 in the embodiment shown in FIG. 4A and FIG. 4B. In addition, the in-vehicle communication component 01 may be further configured to implement the method in the embodiment shown in FIG. 5. In addition, the in-vehicle communication component 01 may be further configured to implement the method shown in operation 115 and operation 117 in the embodiment shown in FIG. 7.

[0185] In an embodiment, the in-vehicle communication component 01 may be a TBOX. At least one SIM card is installed in the in-vehicle communication component 01, and the in-vehicle communication component 01 may further include a baseband chip connected to the SIM card, and a data exchange module configured to exchange data with another component.

[0186] An embodiment of this application further provides a mobile terminal. The mobile terminal may be applied to the emergency call system provided in the foregoing embodiment. Refer to FIG. 1 and FIG. 2. The system further includes the in-vehicle communication component 01 and the fault detection component 03. FIG. 8 is a schematic diagram of a structure of a mobile terminal according to an embodiment of this application. Refer to FIG. 8. The mobile terminal may include a processor 801, a memory 802, a network interface 803, and a bus 804. The bus 804 is configured to connect the processor 801, the memory 802, and the network interface 803. A communication connection to another component may be implemented through the network interface 803 (which may be wired or wireless). The memory 802 stores a computer program 8021. The computer program 8021 is used to implement various application functions.

[0187] It should be understood that in an embodiment of the application, the processor 801 may be a CPU, or the processor 801 may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a GPU or another programmable logic device, a discrete gate, a transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, any conventional processor, or the like.

[0188] The memory 802 may be a volatile memory or a nonvolatile memory, or may include both a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), used as an external cache. Through an example but not limitative description, many forms of RAMs may be used, for example, a static random access memory (static RAM, SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and a direct rambus random access memory (direct rambus RAM, DR RAM).

[0189] In addition to a data bus, the bus 804 may further include a power bus, a control bus, a status signal bus, and the like. However, for clear description, various types of buses in the figure are denoted as the bus 804.

[0190] The processor 801 is configured to execute the computer program stored in the memory 802, and the processor 801 implements, by executing the computer program 8021, the method that is applied to the mobile terminal and that is shown in the foregoing method embodiment. For example, the processor 801 may execute the computer program 8021 to implement the method shown in operation 107, operation 108, and operation 110 in the embodiment shown in FIG. 4A and FIG. 4B. In addition, the method in the embodiment shown in FIG. 6 may be further implemented. In addition, the method shown in operation 116 and operation 118 in the embodiment shown in FIG. 7 may be further implemented.

[0191] It should be understood that both the in-vehicle communication component and the mobile terminal that are provided in embodiments of this application may be implemented by using an application-specific integrated circuit (ASIC), or a programmable logic device (PLD). The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0192] Certainly, the emergency call method provided in the foregoing method embodiment may also be implemented by using software. When the emergency call method provided in the foregoing method embodiment is implemented by using software, both the in-vehicle communication component and the mobile terminal may include software modules configured to implement the foregoing method.

[0193] An embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores instructions, and the instructions are executed by a processor to implement the method applied to the in-vehicle communication component in the foregoing method embodiment, or implement the method applied to the mobile terminal in the foregoing method embodiment.

[0194] An embodiment of this application further provides a computer program product including instructions. When the computer program product runs on a computer, the computer is enabled to perform the method applied to the in-vehicle communication component in the foregoing method embodiment, or perform the method applied to the mobile terminal in the foregoing method embodiment.

[0195] An embodiment of this application further provides a vehicle. As shown in FIG. 9, the vehicle may include a body 00, and the emergency call system provided in the foregoing embodiment. For example, the vehicle may include the system shown in FIG. 1 or FIG. 2.

[0196] Both the in-vehicle communication component 01 and the fault detection component 03 in the emergency call system are fastened to the body 00, and the mobile terminal 02 in the emergency call system can move relative to the body 00. For example, the mobile terminal 02 may be a mobile phone, a phone watch, a notebook computer, a tablet computer, a wearable device, or the like of a user in the vehicle.

[0197] In an embodiment, the vehicle may be an intelligent vehicle or a connected vehicle, and the vehicle may be a new energy vehicle (for example, an electric vehicle) or a fuel vehicle.

[0198] All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement embodiments, the foregoing embodiments may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, all or some of the procedures or functions according to embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium may be a solid state drive (SSD).

[0199] In this application, terms such as “first” and “second” are used to distinguish same items or similar items that have basically same effects and functions. It should be understood that there is no logical or time sequence dependency between “first”, “second”, and “n^th”. A quantity and an execution sequence are not limited.

[0200] In addition, in this application, a term “at least one” means one or more, and a term “a plurality of” means two or more.

[0201] The foregoing descriptions are only optional implementations of this application, but a protection scope of this application is not limited thereto. Any equivalent modification or replacement readily figured out by one of ordinary skilled in the art within a technical scope disclosed in this application should fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to a protection scope of the claims.