An emergency call method, device and computer readable storage medium
Patent Information
- Application Number
- CN202611305663.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-26
- Publication Date
- 2026-09-22
AI Technical Summary
[0005]为了克服现有技术中的不足，本发明的目的在于提供一种紧急呼叫方法、设备及计算机可读存储介质，以解决目前实际网络部署中，UE发起紧急呼叫时仍面临多种异常场景，导致紧急呼叫失败的问题
[0016] The emergency call method, device, and computer-readable storage medium of the present invention identify the type of obstacle that does not meet the initiation conditions when an emergency call is triggered; match and execute the adjustment strategy corresponding to the obstacle type in a preset strategy set, and then re-attempt to initiate the emergency call; if the call fails, it iterates through other adjustment strategies in the strategy set and re-attempts to initiate the emergency call until the call succeeds, or after executing all adjustment strategies and all calls fail, it initiates a full-band, full-mode network search and triggers the emergency call again; thereby realizing an emergency call optimization scheme in multiple scenarios, enabling user equipment to automatically identify and intelligently decide on the optimal remedial strategy when encountering different types of obstacles, thereby improving the success rate of emergency calls.
Smart Images
Figure CN122802946A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of wireless communication technology, and in particular to an emergency call method, device, and computer-readable storage medium. Background Technology
[0002] In existing technologies, with the rapid development of wireless communication technologies, from GSM to WCDMA, TD-SCDMA, and then to LTE and 5G NR, network modes are becoming increasingly diverse. User equipment (UE) needs to support multiple modes and frequency bands to adapt to different network environments. The 3GPP protocol stipulates that UE should be able to initiate emergency calls even without a SIM card, and emergency calls should have priority access to network resources. However, in actual network deployments, UEs still face various abnormal scenarios when initiating emergency calls, leading to call failures.
[0003] Specifically, UEs face at least the following problems when initiating emergency calls: First, when a UE is locked in LTE Only mode, if the network returns a 380 (Alternative Service) response requesting Circuit Switched Fallback (CSFB), the UE will fail to search for and camp on a 2G / 3G network, resulting in an emergency call failure. Although there are existing CSFB emergency call handling methods where the network-side MME triggers the UE to switch from the LTE network to the CS domain of the 3G network, this method does not solve the problem of the UE being unable to execute CSFB when it is locked in "LTE Only" mode. Second, in a SIM-free state, after a UE camps on a certain LTE cell, it discovers by reading the SIB (System Information Block) that the cell does not support IMS emergency calls, but the UE does not actively migrate to other cells that support emergency calls; although there are SIM-free emergency communication methods in the existing technology, these methods do not solve the problem when the cell on which the UE is camped does not support IMS emergency calls. Third, for UEs configured with multiple SIM cards, such as DSDS (Dual SIM Dual Standby), when an emergency call fails through the first SIM card, no attempt is made to re-initiate the call using the second SIM card, resulting in the underutilization of multi-card hardware resources. Fourth, when the network is congested, the network side may enable ACB (Access Class Barring) to restrict access for ordinary users. Although emergency calls should theoretically be exempted, in actual networks, there may be situations where ACB is misconfigured or the UE fails to correctly identify the emergency call exemption, resulting in emergency calls being mistakenly blocked.
[0004] In summary, there is a lack of an emergency call optimization solution in the existing technology that can uniformly handle the above-mentioned multiple abnormal scenarios. Summary of the Invention
[0005] In order to overcome the shortcomings of the prior art, the present invention aims to provide an emergency call method, device and computer-readable storage medium to solve the problem that in current actual network deployments, UEs still face a variety of abnormal scenarios when initiating emergency calls, which leads to emergency call failure.
[0006] This invention proposes an emergency call method applied to user equipment, the method comprising: When an emergency call is triggered but the conditions for initiating an emergency call are not currently met, identify the type of obstacle that prevents the initiation of the call from being met. After matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, re-attempt the emergency call; If the call fails, iterate through other adjustment policies in the policy set and retry the emergency call until the call succeeds. Alternatively, after all adjustment policies have been executed and all calls have failed, initiate a full-band, full-mode network search and trigger the emergency call again.
[0007] Optionally, the initiation conditions include one or more of the following: the current operating mode supports initiating an emergency call, the current cell supports emergency calls, the currently used user identification card supports emergency calls, and network access control allows initiating an emergency call.
[0008] Optionally, the obstacle type includes one or more of the following: mode lock conflict, insufficient cell capacity, unused multi-card resources, and access control erroneous blocking.
[0009] Optionally, if the obstacle type is a pattern lock conflict, after matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is re-attempted, specifically including: Temporarily remove the current LTE-only mode restriction, execute the CSFB procedure, and access the 2G or 3G network; Initiate an emergency call and automatically revert to LTE-only mode after the emergency call ends.
[0010] Optionally, if the fault type is insufficient cell capacity, after matching and executing the adjustment strategy corresponding to the fault type in the preset strategy set, the emergency call is re-attempted, specifically including: Trigger an emergency fast reselection, in which other LTE cells are searched first, and if no LTE cells meet the criteria, the search scope is expanded to other RAT cells. Search for cells that support emergency calls in LTE or RAT cells, camp on the cell and initiate an emergency call.
[0011] Optionally, if the obstacle type is "multiple SIM card resources not used," after matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call will be re-attempted, specifically including: The system checks whether the secondary user identification card meets the preset activation conditions, which include the secondary user identification card having a network signal, not being subject to roaming restrictions, and supporting emergency calls. If the secondary user ID card meets the activation conditions, switch to the secondary user ID card and retry the emergency call.
[0012] Optionally, if the obstacle type is access control mis-blocking, after matching and executing the adjustment policy corresponding to the obstacle type in the preset policy set, the emergency call is re-attempted, specifically including: By including an emergency indication in the connection request for radio resource control, access level control checks can be bypassed. If the emergency call is rejected again, switch to a neighboring cell or another RAT cell and try to make the emergency call again.
[0013] Optionally, the method further includes: Construct a strategy set based on the mapping relationship between various obstacle types and adjustment strategies; Update or expand the strategy set based on application feedback information of the adjusted strategy.
[0014] The present invention also proposes an emergency call device, the device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the emergency call method as described in any of the preceding claims.
[0015] The present invention also proposes a computer-readable storage medium storing an emergency call program, wherein when the emergency call program is executed by a processor, the steps of the emergency call method as described in any of the preceding claims are implemented.
[0016] The emergency call method, device, and computer-readable storage medium of the present invention identify the type of obstacle that does not meet the initiation conditions when an emergency call is triggered; match and execute the adjustment strategy corresponding to the obstacle type in a preset strategy set, and then re-attempt to initiate the emergency call; if the call fails, it iterates through other adjustment strategies in the strategy set and re-attempts to initiate the emergency call until the call succeeds, or after executing all adjustment strategies and all calls fail, it initiates a full-band, full-mode network search and triggers the emergency call again; thereby realizing an emergency call optimization scheme in multiple scenarios, enabling user equipment to automatically identify and intelligently decide on the optimal remedial strategy when encountering different types of obstacles, thereby improving the success rate of emergency calls. Attached Figure Description
[0017] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings: Figure 1 This is a flowchart of the first embodiment of the emergency call method of the present invention; Figure 2 This is a flowchart of the second embodiment of the emergency call method of the present invention; Figure 3 This is a flowchart of the third embodiment of the emergency call method of the present invention; Figure 4 This is a flowchart of the fourth embodiment of the emergency call method of the present invention; Figure 5 This is a flowchart of the fifth embodiment of the emergency call method of the present invention; Figure 6 This is a flowchart of the sixth embodiment of the emergency call method of the present invention; Figure 7 This is a flowchart of the seventh embodiment of the emergency call method of the present invention; Figure 8 This is a flowchart of the eighth embodiment of the emergency call method of the present invention. Detailed Implementation
[0018] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.
[0019] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.
[0020] Example 1 Figure 1 This is a flowchart of the first embodiment of the emergency call method of the present invention. An emergency call method, applied to a user equipment, includes: S1. When an emergency call is triggered and the conditions for initiating an emergency call are not currently met, identify the type of obstacle that prevents the initiation conditions from being met. S2. After matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, re-attempt to initiate the emergency call; S3. If the call fails, iterate through other adjustment strategies in the strategy set and retry to initiate the emergency call until the call succeeds, or after all adjustment strategies have been executed and all calls have failed, initiate a full-band, full-mode network search and trigger the emergency call again.
[0021] In this embodiment, when an emergency call is triggered but the initiation conditions are not currently met, the obstacle type that does not meet the initiation conditions is identified; after matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is retried; if the call fails, other adjustment strategies in the strategy set are traversed and the emergency call is retried until the call succeeds, or after all adjustment strategies have been executed and all calls have failed, a full-band, full-mode network search is initiated and the emergency call is triggered again; thus, an emergency call optimization method in multiple scenarios is provided, enabling the UE to automatically identify, intelligently decide and select the optimal remedial strategy when encountering different types of obstacles, thereby improving the success rate of emergency calls.
[0022] In this embodiment, the limitation of existing user equipment (UE) in handling emergency calls according to a single process is overcome. By establishing a closed-loop processing mechanism of obstacle identification → policy matching → adaptive adjustment → call retry, UE can autonomously select the optimal remedial strategy in various abnormal scenarios such as mode lock conflict, insufficient cell capacity, underutilization of multi-card resources, and restricted access control, significantly improving the success rate of emergency calls. At the same time, all adjustment behaviors in this embodiment are implemented within the 3GPP protocol framework, without the need to modify network-side equipment, and have good compatibility and scalability.
[0023] In this embodiment, an emergency call initiation process is triggered when a user dials an emergency number (such as 110, 119, 911, etc.). After the emergency call is triggered, it is checked whether the conditions for initiating an emergency call are met. If not, the obstacle type is identified. The obstacle type is identified by parsing signaling messages sent by the network side (such as 380 response), reading the system information block of the currently camped cell, detecting the working status of each SIM card, and monitoring access control feedback during the RRC (Radio Resource Control) connection process. Based on the identified obstacle type, a corresponding adjustment policy is matched from a stored preset policy set. The matched adjustment policy is executed, and the emergency call is re-attempted under the adjusted conditions. In this embodiment, the preset policy set contains various mapping relationships between obstacle types and adjustment policies. Furthermore, the policy is updated and expanded via OTA or AT commands.
[0024] In a specific example: The UE triggers an emergency call, for example, when a user dials an emergency number; it determines whether the conditions for initiating an emergency call are met. Specifically, it checks one or more of the following conditions: whether the current operating mode supports initiating an emergency call, whether the currently camped cell supports emergency calls, whether the currently used SIM card supports emergency calls, and whether network access control allows initiating an emergency call; if the conditions are met, the emergency call is initiated directly; if the conditions are not met, the type of obstacle is detected and identified. The obstacle types include at least: mode lock conflict, insufficient cell capacity, unused multi-SIM resources, and access control erroneous blocking; based on the identified obstacle type, the corresponding adjustment policy is matched from the stored preset policy set; the matched adjustment policy is executed; the emergency call is retried under the adjusted conditions; it is determined whether the emergency call is successful. If successful, the process ends; if it still fails, it is determined whether there are any untried adjustment policies. If so, it returns to continue matching the next policy; if all policies have been traversed and it still fails, a full-band, full-mode network search is initiated.
[0025] The beneficial effect of this embodiment is that, when an emergency call is triggered and the conditions for initiating the emergency call are not currently met, the obstacle type that does not meet the initiation conditions is identified; after matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is retried; if the call fails, other adjustment strategies in the strategy set are traversed and the emergency call is retried until the call is successful, or after all adjustment strategies have been executed and all calls have failed, a full-band, full-mode network search is initiated and the emergency call is triggered again; thereby, an emergency call optimization scheme in multiple scenarios is realized, enabling user equipment to automatically identify and intelligently decide to select the optimal remedial strategy when encountering different types of obstacles, thereby improving the success rate of emergency calls.
[0026] Example 2 Based on the above embodiments, the initiation conditions include one or more of the following: the current working mode supports initiating an emergency call, the current cell supports emergency calls, the currently used user identification card supports emergency calls, and network access control allows initiating an emergency call.
[0027] Figure 2 This is a flowchart of the second embodiment of the emergency call method of the present invention, in a specific example: Step S100: The UE triggers the emergency call initiation process.
[0028] Step S200: The UE checks whether the conditions for initiating an emergency call are met. If they are met, proceed to step S400 to directly initiate the call; otherwise, proceed to step S300.
[0029] Step S300: The UE identifies the obstacle type, matches the corresponding adjustment strategy from the preset strategy set according to the obstacle type, and executes it.
[0030] Step S400: The UE re-attempts to initiate the emergency call under the adjusted conditions.
[0031] Step S500: If the call is successful, the process ends; if it still fails, iterate through steps S200 to S400.
[0032] Example 3 Based on the above embodiments, the obstacle types include one or more of the following: mode lock conflict, insufficient cell capacity, unused multi-card resources, and access control erroneous blocking.
[0033] In this embodiment, when the UE encounters abnormal scenarios such as mode locking conflict, insufficient cell capacity, underutilization of multi-card resources, or limited access control, it can intelligently identify the type of obstacle and adaptively adjust the strategy to ensure the success of emergency calls.
[0034] Figure 3 This is a flowchart of the third embodiment of the emergency call method of the present invention, in a specific example: Obstacle type A is mode lock conflict: When the UE is in LTE-only mode and receives a message from the network indicating circuit-switched fallback (CSFB) (such as a 380 response), the adjustment strategy includes: the UE automatically and temporarily releases the LTE-only mode restriction, executes the CSFB procedure to access the 2G or 3G network, and initiates the emergency call on the 2G or 3G network.
[0035] Obstacle type B is insufficient cell capability: When the UE is in a cardless state and the first cell currently camped does not support IMS emergency calls, the adjustment strategy includes: the UE triggers an emergency fast reselection process, searches for a second cell that supports IMS emergency calls and camps there.
[0036] Obstacle type C is unused multi-SIM resources: The UE is configured with multiple SIM cards. When an emergency call fails through the first SIM card, the adjustment strategy includes: the UE detects the availability of the second SIM card, and if it is available, automatically switches the emergency call to the second SIM card to re-initiate.
[0037] Obstacle type D is access control misblocking: When emergency calls are rejected due to network access control (ACB), the adjustment strategy includes: the UE carrying an emergency indication in the RRC connection request to bypass the ACB check; if it is still rejected, it switches to a neighboring cell or reduces the radio access technology (RAT) to retry.
[0038] Example 4
[0039] Figure 4 This is a flowchart of the fourth embodiment of the emergency call method of the present invention. Based on the above embodiment, the obstacle type is a pattern lock conflict. After matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is re-attempted, specifically including: S21. Temporarily remove the current LTE-only mode restriction, execute the CSFB procedure, and access the 2G or 3G network; S22, Initiate an emergency call and automatically revert to LTE-only mode after the emergency call ends.
[0040] In this embodiment, the automatic temporary lifting of the LTE-only mode restriction is only effective for the current emergency call session. After the emergency call ends, the UE will automatically revert to LTE-only mode.
[0041] Example 5 Figure 5 This is a flowchart of the fifth embodiment of the emergency call method of the present invention. Based on the above embodiment, the obstacle type is insufficient cell capacity. After matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is re-attempted, specifically including: S23. Trigger emergency fast reselection, in which other LTE cells are searched first. If no LTE cell meets the conditions, the search range is expanded to other RAT cells. S24. Search for cells that support emergency calls in LTE or RAT cells, camp on the cell and initiate an emergency call.
[0042] Example 6 Figure 6 This is a flowchart of the sixth embodiment of the emergency call method of the present invention. Based on the above embodiment, the obstacle type is unused multi-card resources. After matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is re-attempted, specifically including: S25. Detect whether the secondary user identification card meets the preset activation conditions, wherein the activation conditions include the secondary user identification card having a network signal, not being subject to roaming restrictions, and supporting emergency calls; S26. If the secondary user identification card meets the activation conditions, switch to the secondary user identification card and retry initiating the emergency call.
[0043] Example 7 Figure 7 This is a flowchart of the seventh embodiment of the emergency call method of the present invention. Based on the above embodiment, the obstacle type is access control mis-blocking. After matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is re-attempted, specifically including: S27. By including an emergency indication in the connection request for radio resource control, bypassing access level control checks; S28. If the emergency call is rejected again, switch to a neighboring cell or another RAT cell and try to make the emergency call again.
[0044] Example 8 Figure 8 This is a flowchart of the eighth embodiment of the emergency call method of the present invention. Based on the above embodiment, the method further includes: S01. Construct a strategy set based on the mapping relationship between various obstacle types and adjustment strategies; S02. Update or expand the strategy set based on the application feedback information of the adjustment strategy.
[0045] In this embodiment, after the obstacle type is identified, the corresponding adjustment strategy is matched according to the mapping relationship; each strategy in the strategy set is executed in a preset priority order, or the execution order can be dynamically adjusted according to the current network environment; optionally, the above-mentioned types A, B, C and D are set to policy priorities from high to low by default.
[0046] In this embodiment, the preset policy set is scalable; for example, operators or users can issue new policy entries or update existing policies to user equipment via OTA or AT commands; specifically, when a new abnormal scenario is discovered, the corresponding obstacle type and adjustment policy can be added to the preset policy set via OTA without upgrading the UE's software version.
[0047] In this embodiment, after the user equipment successfully completes an emergency call through one of the above-mentioned adjustment strategies, the successful status information is fed back to the user equipment's system, thereby enabling the user equipment to correspondingly increase the priority of the strategy in the preset strategy set so that it can match an effective strategy more quickly when encountering the same type of obstacle next time.
[0048] In this embodiment, when the user equipment still fails to initiate an emergency call after traversing all policies in the preset policy set, a full-band, full-mode network search is initiated as a last resort.
[0049] Example 9 Based on the above embodiments, the present invention also proposes an emergency call device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the emergency call method as described in any of the preceding embodiments.
[0050] It should be noted that the above-described device embodiments and method embodiments belong to the same concept. The specific implementation process can be found in the method embodiments, and the technical features in the method embodiments are also applicable to the device embodiments, which will not be repeated here.
[0051] Example 10 Based on the above embodiments, the present invention also proposes a computer-readable storage medium storing an emergency call program, wherein when the emergency call program is executed by a processor, the steps of the emergency call method as described in any of the above embodiments are implemented.
[0052] It should be noted that the above-described medium embodiments and method embodiments belong to the same concept. The specific implementation process can be found in the method embodiments, and the technical features in the method embodiments are also applicable to the medium embodiments, which will not be repeated here.
[0053] The emergency call method, device, and computer-readable storage medium of the present invention identify the type of obstacle that does not meet the initiation conditions when an emergency call is triggered; match and execute the adjustment strategy corresponding to the obstacle type in a preset strategy set, and then re-attempt to initiate the emergency call; if the call fails, it iterates through other adjustment strategies in the strategy set and re-attempts to initiate the emergency call until the call succeeds, or after executing all adjustment strategies and all calls fail, it initiates a full-band, full-mode network search and triggers the emergency call again; thereby realizing an emergency call optimization scheme in multiple scenarios, enabling user equipment to automatically identify and intelligently decide on the optimal remedial strategy when encountering different types of obstacles, thereby improving the success rate of emergency calls.
[0054] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0055] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0056] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.
[0057] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.
Claims
1. An emergency call method, applied to user equipment, characterized in that, The method includes: When an emergency call is triggered and the conditions for initiating an emergency call are not currently met, identify the type of obstacle that does not meet the initiation conditions; After matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, the emergency call is re-initiated; If the call fails, the other adjustment strategies in the strategy set are traversed and the emergency call is retried until the call is successful, or after all the adjustment strategies have been executed and all calls have failed, a full-band, full-mode network search is initiated and the emergency call is triggered again. in, The initiation conditions include one or more of the following: the current working mode supports initiating an emergency call, the current cell supports emergency calls, the currently used user identification card supports emergency calls, and network access control allows initiating an emergency call. The types of obstacles include one or more of the following: mode lock conflict, insufficient cell capacity, unused multi-card resources, and access control erroneous blocking. The strategy set is constructed based on the mapping relationship between various obstacle types and the adjustment strategies, and the strategy set is updated or expanded based on the application feedback information of the adjustment strategies.
2. The emergency call method according to claim 1, characterized in that, The obstacle type is a pattern lock conflict. The step of matching and executing the adjustment strategy corresponding to the obstacle type within a preset strategy set, and then re-attempting to initiate the emergency call, specifically includes: Temporarily remove the current LTE-only mode restriction, execute the CSFB procedure, and access the 2G or 3G network; Initiate an emergency call and automatically revert to LTE-only mode after the emergency call ends.
3. The emergency call method according to claim 1, characterized in that, The obstacle type is insufficient cell capacity. The step of matching and executing the adjustment strategy corresponding to the obstacle type from a preset strategy set, and then re-attempting to initiate an emergency call, specifically includes: Trigger an emergency fast reselection, in which other LTE cells are searched first, and if no LTE cells meet the criteria, the search scope is expanded to other RAT cells. Search for cells that support emergency calls in LTE or RAT cells, camp on the cell and initiate an emergency call.
4. The emergency call method according to claim 1, characterized in that, The obstacle type is unused multi-card resources. The step of matching and executing the adjustment strategy corresponding to the obstacle type in the preset strategy set, and then re-attempting to initiate an emergency call, specifically includes: The system detects whether the secondary user identification card meets the preset activation conditions, wherein the activation conditions include the secondary user identification card having a network signal, not being subject to roaming restrictions, and supporting emergency calls; If the secondary user identification card meets the activation conditions, the system switches to the secondary user identification card and attempts to initiate an emergency call again.
5. The emergency call method according to claim 1, characterized in that, The obstacle type is access control mis-blocking. The step of matching and executing the adjustment strategy corresponding to the obstacle type in a preset strategy set, and then re-attempting to initiate the emergency call, specifically includes: By including an emergency indication in the connection request for radio resource control, access level control checks can be bypassed. If the emergency call is rejected again, switch to a neighboring cell or another RAT cell and try to make the emergency call again.
6. An emergency call device, characterized in that, The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the emergency call method as described in any one of claims 1 to 5.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an application emergency call program, which, when executed by a processor, implements the steps of the emergency call method as described in any one of claims 1 to 5.