Calling method and device and electronic equipment
By receiving and processing general call information through a first electronic device, and combining it with special information, the problem of failed emergency calls from different locations was solved, and the call success rate was improved.
Patent Information
- Application Number
- CN202511900936.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-16
- Publication Date
- 2026-02-10
AI Technical Summary
Emergency call regulations vary from country to country and region to region. Non-local calling devices may not meet local requirements in other locations, resulting in emergency call failure.
The first electronic device receives general call information sent by the second electronic device when the conditions for an emergency call are not met, and, in conjunction with its own dedicated call information, initiates an emergency call that meets network requirements.
It improves the success rate of emergency calls and reduces the risk of call failures due to insufficient conditions.
Smart Images

Figure CN121509967A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of communication technology, specifically relating to a calling method, device, and electronic device. Background Technology
[0002] With the development of transportation technology, people are traveling more and more frequently, both domestically and internationally, leading to a growing demand for communication. During travel, users may encounter various situations requiring emergency calls, such as medical emergencies, fires, or crimes. Therefore, a stable and reliable emergency call function is crucial for ensuring user safety and convenience.
[0003] However, local regulations in different countries and regions have different requirements for the calling devices used to make emergency calls. Non-local calling devices are difficult to meet these requirements, and when users make emergency calls in other countries or regions, the local network may reject the emergency call. Summary of the Invention
[0004] The purpose of this application is to provide a calling method, apparatus, and electronic device that can improve the success rate of electronic device calls.
[0005] In a first aspect, embodiments of this application provide a calling method, the method comprising: a first electronic device receiving first calling information from a second electronic device; wherein the first calling information is sent by the second electronic device when the calling conditions for an emergency call are not met, and the first calling information is general calling information for initiating an emergency call; the first electronic device meeting the calling conditions; and the first electronic device initiating an emergency call based on the first calling information and the second calling information, wherein the second calling information is dedicated calling information for the first electronic device to initiate an emergency call.
[0006] Secondly, embodiments of this application provide a calling method, which includes: when a second electronic device does not meet the calling conditions for an emergency call, sending a first calling information to a first electronic device that meets the calling conditions, wherein the first calling information is general calling information for initiating an emergency call; wherein the calling condition is that the area code of the location of the electronic device is the same as the code corresponding to the home public land mobile network (HPLMN) of the electronic device.
[0007] Thirdly, embodiments of this application provide a calling device, comprising: a receiving module and a calling module. The receiving module is configured to receive first calling information from a second electronic device; wherein the first calling information is sent by the second electronic device when the calling conditions for an emergency call are not met, and the first calling information is general calling information for initiating an emergency call; the first electronic device meets the calling conditions. The calling module is configured to initiate an emergency call based on the first and second calling information received by the receiving module, wherein the second calling information is dedicated calling information for the first electronic device to initiate an emergency call.
[0008] Fourthly, embodiments of this application provide a calling device, which includes a sending module. The sending module is configured to send first calling information to a first electronic device that meets the calling conditions when a second electronic device does not meet the calling conditions for an emergency call. The first calling information is general calling information for initiating an emergency call. The calling condition is that the area code of the location of the second electronic device is the same as the code corresponding to the HPLMN of the electronic device.
[0009] Fifthly, embodiments of this application provide an electronic device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.
[0010] In a sixth aspect, embodiments of this application provide an electronic device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the second aspect.
[0011] In a seventh aspect, embodiments of this application provide a readable storage medium on which a program or instructions are stored, wherein when the program or instructions are executed by a processor, they implement the steps of the method described in the first aspect, or, when the program or instructions are executed by a processor, they implement the steps of the method described in the second aspect.
[0012] Eighthly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.
[0013] Ninthly, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first aspect.
[0014] In this embodiment, a first electronic device can receive first call information from a second electronic device. This first call information is sent by the second electronic device when the call conditions for an emergency call are not met. This first call information is a general call information used to initiate an emergency call. The first electronic device meets the call conditions, and then it can initiate an emergency call based on the first and second call information, where the second call information is a dedicated call information for initiating the emergency call. In this solution, since the first electronic device can receive the general call information sent by the second electronic device when the call conditions for an emergency call are not met, and the first electronic device meets the call conditions for an emergency call, it can directly initiate an emergency call that meets network requirements based on the received general call information and its dedicated call information. This allows the first electronic device to make calls to the second electronic device, reducing the risk of call failure due to insufficient conditions and thus improving the success rate of electronic device calls. Attached Figure Description
[0015] Figure 1 This is one of the flowcharts of the calling method provided in the embodiments of this application;
[0016] Figure 2 This is one of the schematic diagrams of the second electronic device provided in the embodiments of this application;
[0017] Figure 3 This is one of the schematic diagrams of the first electronic device and the second electronic device provided in the embodiments of this application;
[0018] Figure 4 This is a second schematic diagram of the first electronic device and the second electronic device provided in the embodiments of this application;
[0019] Figure 5 This is the second flowchart of the calling method provided in the embodiments of this application;
[0020] Figure 6 This is the third flowchart of the calling method provided in the embodiments of this application;
[0021] Figure 7 This is a second schematic diagram of the first electronic device and the second electronic device provided in the embodiments of this application;
[0022] Figure 8 This is the fourth flowchart of the calling method provided in the embodiments of this application;
[0023] Figure 9 This is the fifth flowchart of the calling method provided in the embodiments of this application;
[0024] Figure 10This is a schematic diagram illustrating the execution process of a calling method provided in an embodiment of this application;
[0025] Figure 11 This is a schematic diagram illustrating another execution process of the calling method provided in the embodiments of this application;
[0026] Figure 12 This is one of the schematic diagrams of the calling device provided in the embodiments of this application;
[0027] Figure 13 This is a second schematic diagram of the calling device provided in the embodiments of this application;
[0028] Figure 14 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;
[0029] Figure 15 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0030] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0031] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0032] The terms "at least one," "at least one," etc., in this application refer to any one, any two, or a combination of two or more of the included objects. For example, at least one of a, b, and c can mean: "a," "b," "c," "a and b," "a and c," "b and c," and "a, b, and c," where a, b, and c can be single or multiple. Similarly, "at least two" refers to two or more, and its meaning is similar to that of "at least one."
[0033] The calling method, apparatus, and electronic device provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.
[0034] The embodiments of this application can be applied to scenarios where electronic devices cannot directly complete a call because they do not meet local emergency call requirements or network coverage is inadequate.
[0035] The following uses some specific scenarios from the embodiments of this application as examples to illustrate the calling method provided in the embodiments of this application.
[0036] Scenario 1: A user encounters a fire while traveling abroad and urgently needs to make an emergency call. Local regulations require that emergency calls must include altitude data, but the user's mobile phone does not support a barometer. When the user makes an emergency call using their mobile phone, the network side rejects the call due to the missing location field.
[0037] Scenario 2: A user is traveling in a city where 2G / 3G networks have been phased out and only 4G / 5G networks are available. The user needs to book a hotel, but cannot make calls via 4G / 5G because their phone does not support 4G / 5G networks.
[0038] It should be noted that the above scenarios 1 and 2 are merely exemplary examples of some scenarios that may be applied to the embodiments of this application. In actual implementation, the embodiments of this application can also be applied to more possible scenarios of demand calls, and the embodiments of this application are not limited here.
[0039] This application provides a calling method, apparatus, and electronic device. Since the first electronic device can receive general calling information sent by the second electronic device when the calling conditions for an emergency call are not met, and the first electronic device meets the calling conditions for an emergency call, the first electronic device can directly initiate an emergency call that meets network requirements based on the received general calling information and its own dedicated calling information. Thus, the second electronic device can be called through the first electronic device, reducing the risk of call failure due to insufficient conditions. In this way, the success rate of electronic device calls can be improved.
[0040] The execution subject of the calling method provided in this application embodiment can be a calling device, which can be an electronic device, or a functional module or functional entity in an electronic device. The following uses an electronic device as an example to illustrate the technical solution provided in this application embodiment.
[0041] Figure 1 A flowchart of a calling method provided in an embodiment of this application is shown, such as... Figure 1 As shown, the calling method provided in this application embodiment may include the following steps 201 and 202.
[0042] Step 201: The first electronic device receives the first call information from the second electronic device.
[0043] In some embodiments of this application, the first call information is sent by the second electronic device when the call conditions for an emergency call are not met, and the first call information is general call information for initiating an emergency call.
[0044] In some embodiments of this application, the first electronic device described above meets the call conditions for an emergency call.
[0045] In some embodiments of this application, the aforementioned emergency call refers to a call initiated by a user in an emergency to obtain timely rescue or assistance, and the conditions for an emergency call must be met before the call can be made. In contrast to an emergency call, a normal call refers to a non-emergency call initiated by a user in daily life for routine communication with others.
[0046] For example, a user encounters an emergency while traveling abroad and needs to dial the local emergency number, but cannot directly initiate an emergency call due to a lack of specific functionality in their device.
[0047] In some embodiments of this application, the call conditions for satisfying an emergency call refer to satisfying the conditions for initiating an emergency call locally, and the first electronic device refers to a device that satisfies the conditions for initiating an emergency call locally.
[0048] In some embodiments of this application, the conditions for initiating an emergency call by a local call refer to the current national or regional regulatory requirements for emergency calls, which include, but are not limited to:
[0049] 1. The number needs to be certified by the local telecommunications authority;
[0050] 2. A Subscriber Identity Module (SIM) card needs to be installed in the phone;
[0051] 3. The mobile phone needs to support Internet Protocol Multimedia Subsystem (IMS);
[0052] 4. Requires support for high-precision positioning and barometers;
[0053] 5. Mountain Model functionality needs to be supported;
[0054] 6. Caller ID (caller identification) functionality is required;
[0055] 7. Support for Real-Time Text (RTT) functionality is required.
[0056] In some embodiments of this application, the aforementioned second electronic device refers to a device that does not meet the conditions for initiating a local emergency call. For example... Figure 2 As shown, if a roaming user's electronic device does not meet the conditions for initiating an emergency call locally, the emergency call will be rejected due to the lack of necessary parameters.
[0057] For example, if a user from country Z travels to country M, their mobile phone, typically from country Z, lacks a barometer. In country M, emergency calls will lack altitude information and be rejected. In this case, the mobile phone from country Z becomes the second electronic device. However, country M mandates that mobile phones support barometers, allowing the phone from country M to dial emergency numbers normally. In this case, the mobile phone from country M becomes the first electronic device.
[0058] In some embodiments of this application, the aforementioned general call information may also be referred to as basic information, which refers to information describing the basic intent and necessary parameters of a call in a general format.
[0059] In some embodiments of this application, the aforementioned general call information includes at least one of the following: a request for a Uniform Resource Identifier, a call identifier, and a priority parameter.
[0060] In some embodiments of this application, when initiating an emergency call, the general call information may include, but is not limited to: a Request Uniform Resource Identifier (Request-URI) parameter, a Call Identifier (Call-ID) parameter, and a Priority parameter. Wherein:
[0061] (1) The format of the Request-URI parameter is urn:service:<emergency type> or <emergency type>, such as urn:service:sos or sos, which is used to identify the emergency session type. Specific parameters can be appended after this parameter. For example, in the case of a fire, .fire can be appended after this parameter, such as urn:service:sos.fire, to indicate that this is a fire-related emergency call.
[0062] (2) The Call-ID parameter is in the format of <special prefix>-<random or unique identifier>, such as EMER-Identifier Example, which is used to identify emergency call flows to ensure that the network recognizes that it is an emergency call flow, thereby preventing network filtering and giving priority routing.
[0063] (3) The Priority parameter is in the format of Priority: <priority type>, for example Priority:emergency, which is used to indicate that this is an emergency call that needs to be processed first in order to trigger network QoS guarantee and assign the highest priority. For example, setting the Quality of Service Class Identifier (QCI) to 5 indicates the highest priority.
[0064] In some embodiments of this application, when initiating a normal call, the second electronic device may also be an electronic device that does not meet the requirements for initiating a normal call. In this case, the first electronic device may be a device with a network connection.
[0065] For example, a user traveling abroad needs to contact their hotel or family, but cannot make a regular call because their device does not support the local network standard or is in an area with no network coverage. In this case, the user is using a second electronic device.
[0066] In some embodiments of this application, having network connectivity means that there is network coverage available to the device in the local area. For example, if there is 4G / 5G network coverage in the local area, but no 2G / 3G network coverage, then an electronic device that only supports 2G / 3G networks and does not support 4G / 5G networks does not have network connectivity in the local area, while an electronic device that supports 4G / 5G networks has network connectivity in the local area.
[0067] In some embodiments of this application, when initiating a normal call, the general call information may include, but is not limited to: Request-URI parameters, From parameters, and To parameters. Wherein:
[0068] (1) The format of the Request-URI parameter is Sip:<mobile number>@<operator domain name>, for example Sip:number example@domain example.com, which is an invitation message used to initiate a call, containing the target mobile number and operator information.
[0069] (2) The format of the From parameter is Sip:<local mobile phone number>, for example, Sip: number example 1, which is used for the mobile phone number of the caller. It can be encrypted to protect user privacy. The encryption algorithm is also a standard protocol, which will only be explained here without expanding the encryption process. We will only focus on the original meaning of this field, that is, the local mobile phone number.
[0070] (3) The format of the To parameter is Sip:<target mobile number>, for example Sip:number example 2, which is used to identify the target mobile number of the call.
[0071] In some embodiments of this application, the first electronic device can receive the first call information from the second electronic device through short-range communication technologies such as Bluetooth, Wireless Fidelity (WiFi Direct), and Ultra-Wideband (UWB). The specific transmission method can be determined according to actual usage requirements, and this application embodiment does not impose any limitations.
[0072] Step 202: The first electronic device initiates an emergency call based on the first call information and the second call information.
[0073] In some embodiments of this application, the aforementioned second call information is dedicated call information for an emergency call initiated by the first electronic device.
[0074] In some embodiments of this application, the aforementioned dedicated call information includes at least one of the following: geographic location information, Internet Protocol Multimedia Subsystem capability identifier, altitude information, real-time text function parameters, caller ID parameters, mountain model parameters, vehicle emergency call data, and network priority parameters.
[0075] In some embodiments of this application, when an emergency call is initiated, the second call information is specialized call information required to initiate an emergency call in the current country or region, which can supplement the first call information to meet the requirements of the local network. Examples include geolocation information, vertical precision extended (PIDF-LO) information, altitude information, medical record information, vehicle collision data (ecall.MSD), and dynamic location update information.
[0076] For example, suppose a user encounters an emergency while traveling abroad and needs to call a local emergency number. Local emergency calls require location information, but the user's second electronic device does not support geolocation and therefore cannot directly initiate an emergency call. In this case, the user sends a first call message to a nearby first electronic device via the second electronic device. Upon receiving the first call message, the first electronic device generates location information, i.e., a second call message, and then combines the first and second call messages to initiate an emergency call.
[0077] In some embodiments of this application, after receiving the first call information sent by the second electronic device, the first electronic device can generate second call information according to the requirements of the local network to supplement the special call information needed for the call, such as high-precision positioning information, medical record information, etc. Then, the first electronic device can merge the first call information and the second call information to generate complete call request information, and then initiate an emergency call.
[0078] In some embodiments of this application, the aforementioned call request information refers to the Session Initiation Protocol (SIP) message. SIP is an application-layer signaling protocol used to create, modify, and terminate multimedia sessions, such as voice calls, video conferencing, and instant messaging.
[0079] For example, the following provides a complete SIP example with specific code.
[0080] sip
[0081] 1 INVITE uniservices:sos SIP / 2.0
[0082] 2 Via: SIP / 2.0 / TLS 192.0.2.1:5061;branch=29hG4bKemerg
[0083] 3 Max-Forwards: 70
[0084] 4 From: <sip:+12155551212@example.com>;tag=9fxed7651
[0085] 5 To: <urn:service:sos>
[0086] 6 Call-ID: EMER-309847c0@192.0.2.1
[0087] 7 CSeq: 1 INVITE
[0088] 8 Priority: emergency
[0089] 9 Resource-Priority: dsn.flash / / Defense-level priority
[0090] 10 Geolocation:<cid:loc123@example.com> / / Location data identifier
[0091] 11 Geolocation-Routing: yes
[0092] 12 Call-Info:<cid:medical@ex> ;purpose=emergency-call-data / / Medical records
[0093] 13 Feature-Caps: *;+g.3gpp.icsi-ref="urn:im-7:3gpp-service.ims.icsi.emergency"
[0094] 14 Content-Type: application / sdp
[0095] 15 Content-Length: 365 16
[0097] 17 / / Message Body (SDP)
[0098] 18 v=0
[0099] 19 o=- 29879336613 29879336613 IN IP4 192.0.2.1.1
[0100] 20 s = Emergency
[0101] 21 c=IN IP4 192.0.2.1
[0102] 22 t=0 0
[0103] 23 m=audio 49178 RTP / AVP 0 101
[0104] 24 a a=rtpmap:0 PCMU / 8000
[0105] 25 a=rtpmap:101 telephone-event / 8000 / / VoLTE handover capability
[0106] 26 a=fmtp:101 0-16
[0107] 27 a=essvc:yes
[0108] 28 a=e-ccall.MSD: AA0EBNF...HEX / / Vehicle collision data
[0109] 29 a=curr:qos local sendrecv
[0110] 30 a=desigs mandatory local sendrecv
[0111] The code example ends.
[0112] Among them, the 1st, 6th, and 8th lines are parameters in the first call information. The 1st line is the Request-URI parameter, the 6th line is the Call-ID parameter, the 8th line is the Priority parameter. The 9th - 12th lines and the 28th line are parameters in the second call information. The 9th line is the national defense priority parameter, the 10th and 11th lines are location data identification parameters, the 12th line is the medical record parameter, and the 28th line is the vehicle collision data encoded in hexadecimal (HEX).
[0113] Exemplarily, taking the location information as an example, in the Geolocation in the SIP main message, the detailed content can be split into information such as location and altitude. Such information requires hardware support, so it is calculated by the local electronic device and then provided and reported to the network. The following uses specific code to exemplify the specific location information.
[0114] 1. Location Data (Geolocation Header)
[0115] xml
[0116] I <!-- PIDF-LO data (RFC 4119) -->
[0117] II <gp:location-info>
[0118] 3 <gp:point id="point1" srsname="urn:ogc:def:crs:EPSG:4979">
[0119] 4 <gp:pos> 37.775 -122.419 27.4< / gp:pos> <!-- Latitude, longitude, altitude -->
[0120] 5 <gp:verticalaccuracy uom="urn:ogc:def:uom:EPSG:9001"> 3.5< / gp:verticalaccuracy> <!-- Vertical accuracy 3.5 meters -->
[0121] 6 <method> Barometer + WIFI + A-GPS< / method> <!-- Barometer involved in positioning -->
[0122] 7< / gp:point>
[0123] 8 <confidence> 95< / confidence> <!-- Confidence level 95% -->
[0124] 9
[0125] [[ID=#]]The pseudo-code example ends.
[0126] Among them, the barometer function is to enable floor mapping when VerticalAccuracy ≤ 3 meters. The matching formula between altitude data and the building 3D database is shown in the following formula (1):
[0127] Formula (1)
[0128] The default floor height is 3 meters.
[0129] In some embodiments of this application, such as Figure 3 As shown, after the SIP message carries all the parameters required by the operator, a successful call can be made, connecting to the emergency call center. Using call relay mode, roaming electronic devices can call the emergency call center. For example... Figure 4 As shown, after the above steps, the second electronic device can change from being unable to make an emergency call to being able to make an emergency call through the first electronic device.
[0130] In some embodiments of this application, when the call is initiated as a normal call, the aforementioned second call information may also be dedicated call information required to initiate a normal call in the current network environment. For example, network connection status information, network protocol support information, session description protocol information, etc.
[0131] For example, suppose a user is in a city with 4G / 5G network coverage but no 2G / 3G network coverage and needs to contact a hotel to confirm a booking, but the user's mobile phone only supports 2G / 3G networks and not 4G / 5G networks. In this case, the user sends a first call message to other nearby mobile phones. After receiving the first call message, the other mobile phones generate network connection status and network protocol support information, i.e., a second call message, and then combine the first call message and the second call message to initiate a call.
[0132] This application provides a calling method. Since the first electronic device can receive general calling information sent by the second electronic device when the calling conditions for an emergency call are not met, and the first electronic device meets the calling conditions for an emergency call, the first electronic device can directly initiate an emergency call that meets network requirements based on the received general calling information and the dedicated calling information of the first electronic device. Thus, the second electronic device can be called through the first electronic device, reducing the risk of call failure due to insufficient conditions. In this way, the success rate of electronic device calls can be improved.
[0133] In some embodiments of this application, the above-mentioned calling condition is that the region code of the electronic device's location is the same as the code corresponding to the electronic device's HPLMN.
[0134] In some embodiments of this application, the aforementioned region code may also be referred to as the Mobile Country Code (MCC), which consists of 3 digits and is used to uniquely identify a mobile network in a country or region.
[0135] In some embodiments of this application, the aforementioned location refers to the country or region where the electronic device is currently located.
[0136] In some embodiments of this application, the HPLMN mentioned above refers to the subscribed home network. The HPLMN code consists of two parts: MCC and Mobile Network Code (MNC), totaling 5-6 digits. Among them, the MNC is 2-3 digits used to identify the operator.
[0137] In some embodiments of this application, the code corresponding to the above-mentioned HPLMMN refers to the code of the MCC part in the HPLMMN, which can represent the country or region to which the electronic device belongs.
[0138] In some embodiments of this application, when the area code of the current region of the first electronic device is the same as the area code of the home region of the first electronic device, the first electronic device can determine that the first electronic device is currently in the home region of the first electronic device, thus satisfying all the regulatory requirements of the local operator for the call, and can complete the call in place of the second electronic device.
[0139] In some embodiments of this application, the aforementioned second call information is dedicated call information used when an emergency call is initiated through the HPLMN of the first electronic device.
[0140] In some embodiments of this application, combined with Figure 1 ,like Figure 5 As shown, step 202 can be implemented through steps 202a and 202b below.
[0141] Step 202a: The first electronic device obtains the first emergency number corresponding to the region where the emergency call is located based on the first call information.
[0142] In some embodiments of this application, the aforementioned first emergency number refers to the number used for emergency calls in the current region of the first electronic device.
[0143] It's important to note that electronic devices capable of making calls typically include an emergency call number mapping table. This table is a whitelist specifically used to store and configure local emergency phone numbers. Engineers can configure this whitelist to change local emergency numbers. Electronic devices can read this whitelist to accurately obtain numbers for fire, ambulance, fire services, etc.
[0144] In some embodiments of this application, after receiving the first call information, the first electronic device can obtain the Request-URI parameter from the first call information to know the emergency call type corresponding to the emergency call.
[0145] For example, assuming that the Request-URI parameter obtained by the first electronic device from the first call information is urn:service:sos.fire, the first electronic device can determine that this is a fire emergency call.
[0146] In some embodiments of this application, after learning the emergency call type corresponding to the emergency call, the first electronic device can look up the emergency number corresponding to the emergency call type from the emergency call number mapping table according to the emergency call type.
[0147] For example, assuming the current region of the first electronic device is region A, and the emergency call type corresponding to the emergency call is a fire emergency call, the first electronic device can look up the emergency number corresponding to the fire emergency call type in region A from the emergency call number mapping table according to the type of fire emergency call.
[0148] Step 202b: The first electronic device initiates an emergency call to the first emergency number based on the first call information and the second call information.
[0149] In some embodiments of this application, after finding the emergency number corresponding to the emergency call type from the emergency call number mapping table, the first electronic device can generate second call information according to the requirements of the local network to supplement the special call information required for the call, such as geographical location information, altitude information, medical record information, vehicle collision data, etc. Then, the first electronic device can merge the first call information and the second call information to generate complete call request information, and then initiate an emergency call to the first emergency number.
[0150] In this way, the first electronic device can accurately identify the specific type of emergency call and obtain the corresponding first emergency number to initiate a call to the first emergency number, thereby avoiding the problem that users cannot initiate an emergency call in time due to unfamiliarity with the local emergency number and improving the success rate of emergency calls.
[0151] In some embodiments of this application, when initiating a normal call, the first electronic device may be an electronic device with a network connection.
[0152] In some embodiments of this application, the first electronic device can initiate a normal call based on the first call information and the second call information through the network connection of the first electronic device.
[0153] In some embodiments of this application, the aforementioned second call information is dedicated call information for initiating a regular call using the network connection of the first electronic device.
[0154] The calling method provided in this application can slightly improve the pain point of electronic devices being unable to make calls in areas without network support. For example, if a user's mobile phone does not support local Voice over Long-Term Evolution (VoLTE) / VoNR functions, which require 4G / 5G network support, while local mobile phones can support these functions, and roaming mobile phones do not support the VoLTE / VoNR functions of local operators, then they can only use the traditional Circuit Switched Fallback (CSFB) service to make calls. However, in some countries, 2G / 3G networks have been completely phased out, and 2G / 3G networks cannot be found anywhere. In this case, roaming users will 100% fail to make calls, resulting in dropped calls. Using the relay function of this solution, roaming mobile phones can also successfully make calls.
[0155] VoLTE is the function for making voice calls on a 4G network, while VoNR is the function for making voice calls on a 5G network. CSFB is a standard protocol for a mobile phone to fall back to 2G / 3G to make a call. If a user cannot establish a call under 4G VoLTE, according to the protocol, the mobile phone will fall back to 2G / 3G to retry the call.
[0156] In some embodiments of this application, after receiving the first call information, the first electronic device can generate second call information based on its network connection to supplement the dedicated call information required for the call, such as network connection status information, network protocol support information, session description protocol information, etc. Then, the first electronic device can merge the first and second call information to generate complete call request information and initiate a normal call through its network connection.
[0157] The calling method provided in this application can improve the pain point of electronic devices being unable to make calls overseas, or for older local electronic devices that do not support IMS services.
[0158] For example, if a mobile phone does not support the local VoLTE / VoNR function, while the local mobile phone can support it, and the roaming mobile phone does not support the VoLTE / VoNR function of the local operator, then only the traditional CSFB service can be used for calls. However, in some countries, 2G / 3G has been completely withdrawn from the network, and 2G / 3G networks cannot be found anywhere. Then, the dialing of roaming users will fail 100%, and the call will drop. With the relay of this solution, the mobile phone can also successfully dial.
[0159] In some embodiments of the present application, when the first electronic device receives the first call information sent by the second electronic device, it can start dialing the target number. The basic information for dialing is replaced with the first call information, and the remaining information is provided by the first electronic device. After the SIP message carries all the parameters required by the operator, the call can be successfully made.
[0160] Exemplarily, taking the number of the second electronic device as number c, the target number as number d, and the operator domain name as domain name a, the following uses specific codes to exemplify SIP in a 2G network.
[0161] 2G CS Call sip
[0162] INVITE sip:number d@domain name a SIP / 1.0
[0163] [[ID=14G / 5G IMS Call sip
[0173] INVITE sip:Code d@Domain Name b SIP / 2.0
[0174] **Via**: SIP / 2.0 / UDP [10.1.1.1]:5060;branch=z9hG4bK34a7
[0175] **Max-Forwards**: 70
[0176] **From**: "User" <tel:Number c>;tag=7s2d8
[0177] **To**: <tel:Number d>
[0178] **Call-ID**: 8a7f3d10@10.1.1.1
[0179] **CSeq**: 1 INVITE
[0180] **Contact**: <sip:Number c@10.1.1.1:5060>
[0181] **Supported**: 100rel,timer
[0182] **Content-Type**: application / sdp
[0183] **Content-Length**: 215<q
[0184] v=0
[0185] o=- 298793 298793 IN IP4 10.1.1.1
[0186] s=-
[0187] c=IN IP4 10.1.1.1
[0188] [[ID=4P]]t=P P
[0189] **m=audio 5004 RTP / AVP 98 99**<0000q09>
[0190] a=rtpmap:98 AMR / 8000
[0191] a=fmtp:98 mode-set=0,7
[0192] It should be noted that in the translation, for the sake of consistency with the original format, the tags and are kept as they are in the original text. If there is a specific rule or correction for these tags in the actual context, it may need to be adjusted accordingly. Also, the "t=0 0" in the original is translated as "t=P P" here because the specific meaning of "P" is not clear from the given text. If it's a known placeholder or has a specific value, it should be translated accurately.a=rtpmap:99 telephone-event / 8000
[0193] **m=video 5006 RTP / AVP 102**
[0194] a=rtpmap:102 H.264 / 90000 / /
[0195] End of code example.
[0196] In this way, the first electronic device can initiate a normal call based on the first call information and the second call information using its own network connection, so that even when the second electronic device has no network, the first electronic device can still successfully help the second electronic device make a normal call.
[0197] Figure 6 A flowchart of a calling method provided in an embodiment of this application is shown, such as... Figure 6 As shown, the calling method provided in this application embodiment may include the following step 301.
[0198] Step 301: If the second electronic device does not meet the call conditions for an emergency call, the second electronic device sends a first call message to the first electronic device that meets the call conditions.
[0199] In some embodiments of this application, the first call information described above is general call information used to initiate an emergency call.
[0200] In some embodiments of this application, the above-mentioned calling condition is that the region code of the electronic device's location is the same as the code corresponding to the electronic device's HPLMN.
[0201] In some embodiments of this application, the conditions for the second electronic device not to meet the emergency call conditions include any of the following: the area code of the current region of the second electronic device is different from the area code of the home region of the second electronic device, or the second electronic device does not have a network connection.
[0202] In some embodiments of this application, if the second electronic device does not meet the calling conditions for an emergency call, the second electronic device can search for nearby electronic devices that meet the calling conditions for an emergency call and identify that electronic device as the first electronic device.
[0203] In some embodiments of this application, the second electronic device can scan surrounding electronic devices through a wireless communication module and identify electronic devices that meet the call conditions for an emergency call by means of broadcasting or scanning signals.
[0204] In some embodiments of this application, if the region code of the current region of the second electronic device is different from the region code of the home region of the second electronic device, the electronic device can identify the electronic device whose home region code is the same as the region code of the current region as the first electronic device.
[0205] In some embodiments of this application, when a user encounters an emergency, they need to dial an emergency number. For example, if a user encounters a robbery, they need to dial the police; if they encounter an emergency requiring first aid, they need to dial the ambulance, and so on.
[0206] In some embodiments of this application, when a user dials an emergency number, the first electronic device can detect whether the user is in the user's country. This can be achieved, for example, by using network detection to determine whether the Home Public Land Mobile Network (HPLMN) and Roaming Public Land Mobile Network (RPLMN) are roaming, or by using a system-stored default country. If the device detects that the phone is not in the user's usual country, the first electronic device can activate internet connectivity and connect to a nearby local phone. This includes, but is not limited to, connection technologies such as Bluetooth, Wi-Fi, and UWB.
[0207] In some embodiments of this application, even if the second electronic device does not have a network connection, the electronic device may identify an electronic device with a network connection as the first electronic device.
[0208] In some embodiments of this application, after the second electronic device finds the first electronic device that meets the calling conditions, the second electronic device can establish a connection with the first electronic device through short-range wireless communication technologies such as Bluetooth, Wi-Fi Direct, UWB, etc.
[0209] In some embodiments of this application, after the second electronic device finds a first electronic device that meets the calling conditions, the second electronic device can send a pairing request to the first electronic device to request the establishment of a connection. Upon receiving the request, the first electronic device can verify its legitimacy, such as checking whether the request comes from a trusted device or whether the user has authorized it. After successful verification, the first electronic device can accept the pairing request, and the first and second electronic devices can establish a stable communication link through a specified communication protocol, preparing for subsequent data transmission.
[0210] In some embodiments of this application, after establishing a connection with the first electronic device, the second electronic device can send a first call message to the first electronic device through the connection.
[0211] In some embodiments of this application, when a user dials an emergency number using a second electronic device, the second electronic device can query the HPLMN of its current SIM card and the corresponding emergency session type, and transmit this information to an interconnected first electronic device. The call will then carry basic emergency call information, and the call will be relayed to a nearby local user's first electronic device to continue dialing.
[0212] In some embodiments of this application, after the first electronic device receives the call information from the second electronic device, it can find the corresponding local emergency number in the emergency call number mapping table stored in the first electronic device and make the call.
[0213] For example, such as Figure 7 As shown, the alarm phone number of the second electronic device's home location is number 'a'. When a user dials number 'a', if the area code of the second electronic device's current location is different from the area code of its home location, the second electronic device can determine the emergency session type corresponding to number 'a' as an alarm type. It will then include parameters identifying the alarm type in its basic parameters, encapsulate these basic parameters into first call information, and send it to the first electronic device. Upon receiving the first call information, the first electronic device can determine the alarm type based on the basic parameters, and then search for the corresponding local emergency number. Assuming the local emergency number for this alarm type is number 'b', the first electronic device can begin calling number 'b'. The basic call information is replaced with the information transmitted by the second electronic device, plus locally required parameters provided by the first electronic device. These parameters could be GeoLocation, PIDF-LO, ecall.MSD, UPDATE, etc.
[0214] In some embodiments of this application, after establishing a connection with the first electronic device, the second electronic device can encapsulate the first call information, such as key parameters like call type, target number, or user identity information, into a structured data packet. For example, the first electronic device can use the SIP protocol to construct an INVITE request, which includes key parameters such as Request-URI, From, and To.
[0215] In some embodiments of this application, after encapsulating the first call information, the electronic device can send the encapsulated first call information to the first electronic device through the established wireless communication link.
[0216] In some embodiments of this application, during transmission, the second electronic device may encode and encrypt the data according to the requirements of the communication protocol to ensure the integrity and security of the data.
[0217] In some embodiments of this application, after receiving the first call information, the first electronic device can verify and parse the first call information to confirm the integrity and accuracy of the data. If the data is correct, the first electronic device can send a confirmation message to the second electronic device, indicating that the call information has been successfully received and preparations are made for subsequent call operations.
[0218] In some embodiments of this application, after the first electronic device dials an emergency call, the call data of the emergency call can be transmitted through the connection between the first electronic device and the second electronic device, and the user can answer the emergency call through the second electronic device.
[0219] This application provides a calling method. Since the second electronic device does not meet the conditions for an emergency call, the second electronic device can send general calling information for initiating an emergency call to the first electronic device that meets the conditions for initiating an emergency call, thereby enabling the first electronic device to initiate an emergency call. This reduces the risk of call failure due to insufficient conditions and improves the success rate of electronic device calls.
[0220] Figure 8 A flowchart of a calling method provided in an embodiment of this application is shown, such as... Figure 8 As shown, the calling method provided in this application embodiment may include the following steps 401 to 407.
[0221] Step 401: If the second electronic device does not meet the call conditions for an emergency call, the second electronic device sends a first call message to the first electronic device that meets the call conditions.
[0222] Step 402: The first electronic device receives the first call information from the second electronic device.
[0223] Step 403: The first electronic device initiates an emergency call based on the first call information and the second call information.
[0224] In some embodiments of this application, combined with Figure 8 ,like Figure 9 As shown, step 403 can be implemented through steps 403a and 403b as described below.
[0225] Step 403a: The first electronic device obtains the first emergency number corresponding to the region where the emergency call is located based on the first call information.
[0226] Step 403b: The first electronic device initiates an emergency call to the first emergency number based on the first call information and the second call information.
[0227] This application provides a calling method. When the second electronic device does not meet the conditions for an emergency call, the second electronic device can send general call information for initiating an emergency call to the first electronic device that meets the conditions for initiating an emergency call. The first electronic device can receive the general call information. Therefore, the first electronic device can directly initiate an emergency call that meets the network requirements based on the received general call information and its own dedicated call information. This allows the second electronic device to make a call through the first electronic device, reducing the risk of call failure due to insufficient conditions and thus improving the success rate of electronic device calls.
[0228] The calling method provided in this application embodiment can utilize devices around the user to assist in making emergency calls. The basic information is carried by the roaming emergency call user when initiating the emergency call. The auxiliary device will provide the local emergency number and auxiliary information required by regulations, which can preserve the information of the user who actually initiates the emergency call to the greatest extent possible and maximize the success rate of the emergency call.
[0229] Figure 10 The diagram illustrates an execution process of a calling method provided in an embodiment of this application, as shown below. Figure 10 As shown, the calling method provided in this application embodiment may include the following steps 10 to 16.
[0230] Step 10: When a user encounters an emergency, they need to dial the emergency number.
[0231] Step 11: The second electronic device detects whether the user is in the user's country when dialing the emergency number.
[0232] The second electronic device can use the network to detect whether HPLMN and RPLMN are roaming; if they are roaming, proceed to step 12.
[0233] Step 12: The second electronic device turns on the interconnection function and connects to the nearby first electronic device.
[0234] Step 13: When the second electronic device dials an emergency number, it transmits the information to the first interconnected electronic device, carrying the most basic emergency call information, and the call is relayed to the nearby first electronic devices to continue dialing.
[0235] Step 14: When the first electronic device receives a request from a roaming user to dial an emergency number, it finds the corresponding local emergency number in the emergency call number mapping table stored in the mobile phone and makes the call.
[0236] Step 15: After receiving the basic parameters, the first electronic device initiates a call to the emergency number. The basic information for the call is replaced with the information transmitted by the roaming user, and the parameters required locally are provided by the local first electronic device to make the emergency call.
[0237] Step 16: After the IP message carries all the parameters required by the operator, the call can be successfully made and connected to the emergency call center. Using the call relay mode, the second electronic device can call the emergency call center, and the process ends.
[0238] Figure 11 A schematic diagram illustrating another execution process of the calling method provided in an embodiment of this application is shown, such as... Figure 11 As shown, the calling method provided in this application embodiment may include the following steps 20 to 26.
[0239] Step 20: When the user needs to make a phone call.
[0240] Step 21: The second electronic device detects whether the user has a network connection when making a phone call.
[0241] If the second electronic device does not have a network connection, proceed to step 12.
[0242] Step 22: The second electronic device turns on the interconnection function and connects to the nearby first electronic device.
[0243] Step 23: When the second electronic device makes a call, it transmits the information to the first interconnected electronic device, carrying the most basic ordinary call information, and the call is relayed to the nearby first electronic device to continue making the call.
[0244] Step 24: The first electronic device receives the roaming user's request to make a call and then makes the call.
[0245] Step 25: After receiving the basic parameters, the first electronic device initiates a call to the target number. The basic information for the call is replaced with the information transmitted by the roaming user, plus the parameters required by the operator and provided by the networked first electronic device, and a normal call is made.
[0246] Step 26: After the IP message carries all the parameters required by the operator, the call can be successfully made. The call is connected, and the second electronic device can make the call using the call relay mode. The process ends.
[0247] The calling method provided in this application addresses two problems that plague users in roaming scenarios: First, not knowing the local emergency phone number prevents them from making calls, thus missing the opportunity for rescue. Second, due to the regulations of various countries, local electronic devices often meet local requirements, but many roaming electronic devices do not, making it impossible to dial emergency numbers.
[0248] This application's embodiments solve the problem of not knowing the local emergency number by using a dual-device interconnection and call relay technology and a conversion method between RPLMN and HPLMMN. Furthermore, the roaming electronic device carries basic information to ensure that the emergency call center can find the correct user. Leveraging the high adaptability of the local electronic device, it carries locally mandated parameter information and reports it to the network, thereby significantly improving the success rate of emergency calls in roaming scenarios.
[0249] Each of the above-described method embodiments, or various possible implementations of each method embodiment, can be executed individually or in combination of any two or more. The specific implementation can be determined according to actual usage requirements, and this application does not impose any restrictions on this.
[0250] The calling method provided in this application can be executed by a calling device. This application uses the example of a calling device executing the calling method to illustrate the calling device provided in this application.
[0251] Figure 12 A schematic diagram of a possible structure of a calling device involved in some embodiments of this application is shown. For example... Figure 12 As shown, the calling device 70 may include a receiving module 71 and a calling module 72.
[0252] The receiving module 71 is used to receive first call information from the second electronic device; wherein the first call information is sent by the second electronic device when the call conditions for an emergency call are not met, and the first call information is general call information for initiating an emergency call; the first electronic device meets the call conditions.
[0253] The aforementioned call module 72 is used to initiate an emergency call based on the first call information and the second call information received by the receiving module 71. The second call information is dedicated call information for the first electronic device to initiate an emergency call.
[0254] In one possible implementation, the aforementioned call condition is that the area code of the electronic device's location is the same as the code corresponding to the electronic device's HPLMN. The second call information is dedicated call information used when initiating an emergency call through the first electronic device's HPLMN.
[0255] In one possible implementation, the call module 72 is specifically used to: obtain the first emergency number corresponding to the region where the first electronic device is located based on the first call information; and initiate an emergency call to the first emergency number based on the first call information and the second call information.
[0256] In one possible implementation, the aforementioned general call information includes at least one of the following: a request for a Uniform Resource Identifier, a call identifier, and a priority parameter. The aforementioned special call information includes at least one of the following: geographic location information, Internet Protocol Multimedia Subsystem Capability Identifier, altitude information, real-time text function parameters, caller ID parameters, mountain model parameters, vehicle emergency call data, and network priority parameters.
[0257] This application provides a calling device. Since the calling device can receive general calling information sent by a second electronic device when the calling conditions for an emergency call are not met, and the calling device meets the calling conditions for an emergency call, the calling device can directly initiate an emergency call that meets network requirements based on the received general calling information and the calling device's dedicated calling information. Thus, the calling device can realize the calling of the second electronic device, reducing the risk of call failure due to insufficient conditions, thereby improving the success rate of electronic device calls.
[0258] Figure 13 A schematic diagram of a possible structure of a calling device involved in some embodiments of this application is shown. For example... Figure 13 As shown, the calling device 73 may include a sending module 74.
[0259] The aforementioned sending module 74 is used to send a first call message to a first electronic device that meets the call conditions when the second electronic device does not meet the call conditions for an emergency call. The first call message is a general call message used to initiate an emergency call.
[0260] The above-mentioned call condition is that the region code of the location of the electronic device is the same as the code corresponding to the HPLMN of the second electronic device.
[0261] This application provides a calling device. When the calling device does not meet the conditions for an emergency call, it can send general calling information for initiating an emergency call to a first electronic device that meets the conditions for initiating an emergency call. This allows the first electronic device to initiate an emergency call, reducing the risk of call failure due to insufficient conditions and thus improving the success rate of calls made by the electronic device.
[0262] The calling device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the scope of the device.
[0263] The calling device in this application embodiment can be a device with an operating system. The operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.
[0264] The calling device provided in this application embodiment can implement the various processes implemented in the above method embodiments, and will not be described again here to avoid repetition.
[0265] Optionally, such as Figure 14 As shown, this application embodiment also provides an electronic device 1000, including a processor 1001 and a memory 1002. The memory 1002 stores a program or instructions that can run on the processor 1001. When the program or instructions are executed by the processor 1001, they implement the various steps of the above-described calling method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.
[0266] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.
[0267] Figure 15 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.
[0268] The electronic device 100 includes, but is not limited to, components such as: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.
[0269] Those skilled in the art will understand that the electronic device 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 15 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.
[0270] In one implementation, the network module 102 is used to receive first call information from a second electronic device. This first call information is sent by the second electronic device when the call conditions for an emergency call are not met; the first call information is general call information for initiating an emergency call; and the first electronic device meets the call conditions.
[0271] The aforementioned radio frequency unit 101 is used to initiate an emergency call based on first call information and second call information, wherein the second call information is dedicated call information for the first electronic device to initiate an emergency call.
[0272] Optionally, the above-mentioned call condition is that the area code of the electronic device's location is the same as the code corresponding to the HPLMN of the first electronic device. The second call information is dedicated call information used when the HPLMN of the first electronic device initiates an emergency call.
[0273] Optionally, the radio frequency unit 101 is specifically used to: obtain the first emergency number corresponding to the region where the first electronic device is located based on the first call information; and to initiate an emergency call to the first emergency number based on the first call information and the second call information.
[0274] Optionally, the aforementioned general call information includes at least one of the following: a request for a Uniform Resource Identifier, a call identifier, and a priority parameter. The aforementioned special call information includes at least one of the following: geographic location information, Internet Protocol Multimedia Subsystem Capability Identifier, altitude information, real-time text function parameters, caller ID parameters, mountain model parameters, vehicle emergency call data, and network priority parameters.
[0275] This application provides an electronic device that can receive general call information sent by a second electronic device when the call conditions for an emergency call are not met, and the electronic device meets the call conditions for an emergency call. Therefore, the electronic device can directly initiate an emergency call that meets network requirements based on the received general call information and the electronic device's dedicated call information. This allows the electronic device to make a call to the second electronic device, reducing the risk of call failure due to insufficient conditions and thus improving the success rate of the electronic device's calls.
[0276] In another implementation, the network module 102 is used to send a first call message to a first electronic device that meets the call conditions when the second electronic device does not meet the call conditions for an emergency call. The first call message is a general call message for initiating an emergency call.
[0277] The above-mentioned call condition is that the region code of the location of the electronic device is the same as the code corresponding to the HPLMN of the second electronic device.
[0278] This application provides an electronic device that, when the electronic device does not meet the conditions for making an emergency call, can send general call information for initiating an emergency call to a first electronic device that meets the conditions for initiating an emergency call, thereby enabling the first electronic device to initiate an emergency call. This reduces the risk of call failure due to insufficient conditions and improves the success rate of calls made by the electronic device.
[0279] The electronic device provided in this application embodiment can implement all the processes implemented in the above method embodiments and achieve the same technical effects. To avoid repetition, it will not be described again here. The beneficial effects of the various implementation methods in this embodiment can be found in the beneficial effects of the corresponding implementation methods in the above method embodiments. To avoid repetition, it will not be described again here.
[0280] It should be understood that, in this embodiment, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.
[0281] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.
[0282] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.
[0283] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described calling method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0284] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.
[0285] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described calling method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0286] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0287] This application provides a computer program product that is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described calling method embodiments, and achieves the same technical effects. To avoid repetition, further details are omitted here.
[0288] 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. Without further limitations, 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. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
[0289] 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 this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer 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, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0290] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application 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 this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.< / urn:service:sos>
Claims
1. A calling method, characterized in that, include: A first electronic device receives a first call message from a second electronic device; wherein the first call message is sent by the second electronic device when the call conditions for an emergency call are not met, and the first call message is a general call message for initiating an emergency call; the first electronic device meets the call conditions. The first electronic device initiates the emergency call based on the first call information and the second call information, wherein the second call information is dedicated call information for the first electronic device to initiate the emergency call.
2. The method according to claim 1, characterized in that, The calling condition is that the area code of the electronic device's location is the same as the code corresponding to the electronic device's home Public Land Mobile Network (HPLMN). The second call information is a dedicated call information used when the emergency call is initiated through the HPLMN of the first electronic device.
3. The method according to claim 2, characterized in that, The first electronic device initiates the emergency call based on the first call information and the second call information, including: Based on the first call information, the first electronic device obtains the first emergency number corresponding to the emergency call in the region where the first electronic device is located; The first electronic device initiates the emergency call to the first emergency number based on the first call information and the second call information.
4. The method according to any one of claims 1 to 3, characterized in that, The general call information includes at least one of the following: a request for a Uniform Resource Identifier, a call identifier, and a priority parameter; The dedicated call information includes at least one of the following: geographic location information, Internet Protocol Multimedia Subsystem capability identifier, altitude information, real-time text function parameters, caller ID parameters, mountain model parameters, vehicle emergency call data, and network priority parameters.
5. A calling method, characterized in that, include: If the second electronic device does not meet the calling conditions for an emergency call, a first calling message is sent to the first electronic device that meets the calling conditions. The first calling message is a general calling message used to initiate the emergency call. The calling condition is that the region code of the electronic device's location is the same as the code corresponding to the electronic device's HPLMN.
6. A calling device, characterized in that, The calling device, applied to a first electronic device, comprises: a receiving module and a calling module; The receiving module is configured to receive first call information from a second electronic device; wherein the first call information is sent by the second electronic device when the call conditions for an emergency call are not met, and the first call information is general call information for initiating the emergency call; the first electronic device meets the call conditions; The call module is used to initiate the emergency call based on the first call information and the second call information received by the receiving module, wherein the second call information is dedicated call information for the first electronic device to initiate the emergency call.
7. The apparatus according to claim 6, characterized in that, The calling condition is that the area code of the electronic device's location is the same as the code corresponding to the electronic device's home Public Land Mobile Network (HPLMN). The second call information is a dedicated call information used when the emergency call is initiated through the HPLMN of the first electronic device.
8. The apparatus according to claim 7, characterized in that, The call module is specifically used for: Based on the first call information, obtain the first emergency number corresponding to the location of the first electronic device in the region where the emergency call is located; and... Based on the first call information and the second call information, the emergency call is initiated to the first emergency number.
9. The apparatus according to claim 6, characterized in that, The general call information includes at least one of the following: a request for a Uniform Resource Identifier, a call identifier, and a priority parameter; The dedicated call information includes at least one of the following: geographic location information, Internet Protocol Multimedia Subsystem capability identifier, altitude information, real-time text function parameters, caller ID parameters, mountain model parameters, vehicle emergency call data, and network priority parameters.
10. A calling device, characterized in that, include: Sending module; The sending module is configured to send first call information to a first electronic device that meets the call conditions when the second electronic device does not meet the call conditions for an emergency call. The first call information is general call information for initiating the emergency call. The calling condition is that the region code of the electronic device's location is the same as the code corresponding to the electronic device's HPLMN.
11. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the calling method as described in any one of claims 1 to 4, or to implement the steps of the calling method as described in claim 5.