Emergency call number indication method and system and electronic equipment

Abstract

The invention provides an emergency call number indication method and system and electronic equipment, the indication method is applied to a terminal side, and the indication method comprises the following steps: analyzing an indication signaling from a network side, the indication signaling comprising an indication identifier; the indication identifier is used for indicating whether the emergency call number in the terminal side is valid or not. According to the invention, by analyzing the indication signaling containing the indication identifier at the network side, whether the emergency call number at the terminal side is effective or not can be accurately controlled. No matter whether the emergency call number is set to be in an invalid state or a valid state, flexible adjustment can be performed according to actual requirements of an operator or a network. In addition, whether the emergency call numbers of a large number of terminal sides are effective or not is managed in a centralized mode and configured in a unified mode. The emergency call numbers on the terminal side do not need to be operated one by one, the management efficiency is greatly improved, and the management cost is reduced.

Description

Technical Field

[0001] The present disclosure relates to the field of communications, and in particular to a method, system and electronic device for indicating an emergency call number. Background Art

[0002] When a user initiates a dialing request, the terminal side (such as a mobile phone) will identify the number to determine whether it is a normal call or an emergency call. Then the number dialed by the user is compared with the list of emergency call numbers stored in the terminal side. If it is in the list, it is an emergency number and the emergency call process is initiated. Otherwise, the normal call process is initiated. The sources of the emergency call number list on the terminal side include the emergency call numbers specified in the protocol, the numbers stored in the USIM card, the numbers sent by the network through signaling, and the numbers locally configured on the terminal side.

[0003] However, with the development of the times, the emergency number list is also changing with the times. However, the emergency call number list on the terminal side will become outdated, so the following demand arises: the operator does not want the emergency call number list on the terminal side to continue to play a role, but only wants the terminal side to use the emergency call number list sent by network signaling. Summary of the invention

[0004] The technical problem to be solved by the present disclosure is to overcome the defect in the prior art that the network side cannot efficiently centrally manage and uniformly configure the emergency call number on the terminal side, and to provide a method, system and electronic device for indicating the emergency call number.

[0005] The present invention solves the above technical problems through the following technical solutions:

[0006] The present disclosure provides a method for indicating an emergency call number, the method for indicating an emergency call number being applied to a terminal side, and the method for indicating an emergency call number comprising:

[0007] The indication signaling from the network side is parsed, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number on the terminal side is valid.

[0008] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling;

[0009] or,

[0010] The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATEACCEPT signaling and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

[0011] Optionally, in response to the indication identifier being a first value, indicating that the emergency call number in the terminal side is valid in the HPLMN and its equivalent PLMN;

[0012] In response to the indication identifier being the second value, it indicates that the emergency call number in the terminal side is invalid in the HPLMN and its equivalent PLMN.

[0013] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0014] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling;

[0015] The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

[0016] Optionally, the first additional information element is of TLV-E type or TV type.

[0017] Optionally, before the step of parsing the indication signaling from the network side, the step further includes:

[0018] Sending a request message to the network side; the request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side;

[0019] The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling;

[0020] The indication identifier is located in a second additional information element in the indication signaling.

[0021] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0022] Optionally, the information element indicator is located in any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located in any spare bit position in the Extended emergency number list IE in the indication signaling;

[0023] In response to the information element indicator in the indication signaling being a third value, indicating that the indication signaling does not include the second additional information element;

[0024] In response to the information element indicator in the indication signaling being a fourth value, indicating that the indication signaling includes the second additional information element;

[0025] Among them, the several indication identifiers included in the second additional information element are used to indicate whether each of the emergency call numbers to be confirmed on the terminal side is valid.

[0026] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0027] The present disclosure provides a method for indicating an emergency call number, the method for indicating an emergency call number being applied to a network side, and the method for indicating an emergency call number comprising:

[0028] An indication signaling is sent to the terminal side, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number in the terminal side is valid.

[0029] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling;

[0030] or,

[0031] The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATEACCEPT signaling and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

[0032] Optionally, the indication identifier is a first value, which is used to indicate that the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN;

[0033] or,

[0034] The indication identifier takes a second value, which is used to indicate that the emergency call number on the terminal side is invalid in the HPLMN and its equivalent PLMN.

[0035] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0036] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling;

[0037] The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

[0038] Optionally, the first additional information element is of TLV-E type or TV type.

[0039] Optionally, before the step of sending the indication signaling to the terminal side, the step further includes:

[0040] receiving a request message from the terminal side; the request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side;

[0041] The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling;

[0042] The indication identifier is located in a second additional information element in the indication signaling.

[0043] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0044] Optionally, the information element indicator is located in any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located in any spare bit position in the Extended emergency number list IE in the indication signaling;

[0045] The value of the information element indicator in the indication signaling is a third value, which is used to indicate that the indication signaling does not include the second additional information element;

[0046] or,

[0047] The value of the information element indicator in the indication signaling is a fourth value, which is used to indicate that the indication signaling includes the second additional information element;

[0048] Among them, the several indication identifiers included in the second additional information element are used to indicate whether each of the emergency call numbers to be confirmed on the terminal side is valid.

[0049] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0050] The present disclosure provides an indication system for an emergency call number, the indication system being applied to a terminal side, the indication system comprising:

[0051] The parsing module is used to parse the indication signaling from the network side, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number on the terminal side is valid.

[0052] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling;

[0053] or,

[0054] The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATEACCEPT signaling and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

[0055] Optionally, the indication system further comprises: a first response module, configured to indicate that the emergency call number in the terminal side is valid in the HPLMN and its equivalent PLMN in response to the indication identifier being a first value;

[0056] The first response module is further configured to indicate that the emergency call number on the terminal side is invalid in the HPLMN and its equivalent PLMN in response to the indication identifier being a second value.

[0057] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0058] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling;

[0059] The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

[0060] Optionally, the first additional information element is of TLV-E type or TV type.

[0061] Optionally, the indication system further comprises: a message sending module, configured to send a request message to the network side; the request message comprises at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message comprises the emergency call number to be confirmed on the terminal side;

[0062] The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling;

[0063] The indication identifier is located in a second additional information element in the indication signaling.

[0064] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0065] Optionally, the information element indicator is located in any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located in any spare bit position in the Extended emergency number list IE in the indication signaling;

[0066] The indication system further includes: a second response module, configured to indicate that the indication signaling does not include the second additional information element in response to the information element indicator in the indication signaling being a third value;

[0067] The second response module is further configured to indicate that the indication signaling includes the second additional information element in response to the information element indicator in the indication signaling being a fourth value;

[0068] Among them, the several indication identifiers included in the second additional information element are used to indicate whether each of the emergency call numbers to be confirmed on the terminal side is valid.

[0069] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0070] The present disclosure provides an indication system for an emergency call number, the indication system being applied to a network side, and the indication system comprising:

[0071] The signaling sending module is used to send an indication signaling to the terminal side, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number in the terminal side is valid.

[0072] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling;

[0073] or,

[0074] The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATEACCEPT signaling and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

[0075] Optionally, the indication identifier is a first value, which is used to indicate that the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN;

[0076] or,

[0077] The indication identifier takes a second value, which is used to indicate that the emergency call number on the terminal side is invalid in the HPLMN and its equivalent PLMN.

[0078] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0079] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling;

[0080] The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

[0081] Optionally, the first additional information element is of TLV-E type or TV type.

[0082] Optionally, the indication system further comprises: a receiving module, configured to receive a request message from the terminal side; the request message comprises at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message comprises the emergency call number to be confirmed on the terminal side;

[0083] The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling;

[0084] The indication identifier is located in a second additional information element in the indication signaling.

[0085] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0086] Optionally, the information element indicator is located in any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located in any spare bit position in the Extended emergency number list IE in the indication signaling;

[0087] The value of the information element indicator in the indication signaling is a third value, which is used to indicate that the indication signaling does not include the second additional information element;

[0088] The value of the information element indicator in the indication signaling is a fourth value, which is used to indicate that the indication signaling includes the second additional information element;

[0089] Among them, the several indication identifiers included in the second additional information element are used to indicate whether each of the emergency call numbers to be confirmed on the terminal side is valid.

[0090] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0091] The present disclosure provides an electronic device, including a memory, a processor, and a computer program stored in the memory and used to run on the processor, wherein the processor implements any of the above-mentioned indication methods when executing the computer program.

[0092] The present disclosure provides a computer-readable storage medium having a computer program stored thereon, and the computer program implements any of the above-mentioned indication methods when executed.

[0093] The present disclosure provides a chip, wherein the chip includes at least one processor, and the processor is used to execute program instructions to perform any of the indication methods described above.

[0094] The present disclosure provides a chip module, which is applied to electronic equipment, including a transceiver component and a chip, wherein the chip includes at least one processor for executing any of the indication methods described above.

[0095] The present disclosure provides a computer program product, including a computer program, wherein when the computer program is executed by a processor, the computer program implements any of the above-mentioned indication methods.

[0096] On the basis of being in accordance with the common sense in the art, the above-mentioned preferred conditions can be arbitrarily combined to obtain the preferred embodiments of the present disclosure.

[0097] The positive and progressive effect of the present disclosure is that by parsing the indication signaling containing the indication identifier on the network side, it is possible to accurately control whether the emergency call number on the terminal side is valid. Whether the emergency call number is set to an invalid state or a valid state, it can be flexibly adjusted according to the actual needs of the operator or the network. In addition, the validity of a large number of emergency call numbers on the terminal side is centrally managed and uniformly configured. There is no need to operate the emergency call numbers on the terminal side one by one, which greatly improves management efficiency and reduces management costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0098] Figure 1 A flowchart of a method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure;

[0099] Figure 2 A flowchart of another method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure;

[0100] Figure 3 A schematic diagram of an Emergency number list IE provided for an exemplary embodiment of the present disclosure;

[0101] Figure 4 A schematic diagram of an Extended emergency number list IE provided as an exemplary embodiment of the present disclosure;

[0102] Figure 5 A schematic diagram of a TLV-E type USIM Emergency number validation Indication provided for an exemplary embodiment of the present disclosure;

[0103] Figure 6 A schematic diagram of a TV type USIM Emergency number validationIndication provided for an exemplary embodiment of the present disclosure;

[0104] Figure 7 Definition rules for TLV-E type USIM Emergency number validation Indication corresponding to 5G provided by an exemplary embodiment of the present disclosure;

[0105] Figure 8 Definition rules for TV type USIM Emergency number validation Indication corresponding to 5G provided by an exemplary embodiment of the present disclosure;

[0106] Fig. 9Definition rules of TLV-E type USIM Emergencynumber validation Indication corresponding to EPS provided by an exemplary embodiment of the present disclosure;

[0107] Fig.10 Definition rules for TV type USIM Emergency number validation Indication corresponding to EPS provided by an exemplary embodiment of the present disclosure;

[0108] Fig.11 A flowchart of another method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure;

[0109] Fig.12 A flowchart of another method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure;

[0110] Fig.13 Definition rules for the TLV type USIM Emergency numberlist corresponding to 5G provided by an exemplary embodiment of the present disclosure;

[0111] Fig.14 A schematic diagram of an Extended emergency number list IE provided as an exemplary embodiment of the present disclosure;

[0112] Fig.15 A schematic diagram of a USIM number valid bit mapping IE provided for an exemplary embodiment of the present disclosure;

[0113] Fig.16 A flowchart of a method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure;

[0114] Fig.17 A flowchart of another method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure;

[0115] Fig.18 A module schematic diagram of an emergency call number indication system provided by an exemplary embodiment of the present disclosure;

[0116] Fig.19 A module schematic diagram of another emergency call number indication system provided by an exemplary embodiment of the present disclosure;

[0117] Fig. 20 A module schematic diagram of another emergency call number indication system provided by an exemplary embodiment of the present disclosure;

[0118] Fig.21 A module diagram of another emergency call number indication system provided by an exemplary embodiment of the present disclosure;

[0119] Fig. 22 A module schematic diagram of an emergency call number indication system provided by an exemplary embodiment of the present disclosure;

[0120] Fig.23 A module schematic diagram of another emergency call number indication system provided by an exemplary embodiment of the present disclosure;

[0121] Fig.24 The present invention provides a schematic structural diagram of an electronic device according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0122] The present disclosure is further described below by way of examples, but the present disclosure is not limited to the scope of the examples.

[0123] Prefixes such as "first" and "second" are used in the embodiments of the present disclosure only to distinguish different description objects, and have no limiting effect on the position, order, priority, quantity or content of the described objects. The use of prefixes such as ordinal numbers to distinguish description objects in the embodiments of the present disclosure does not constitute a limitation on the described objects. For the statement of the described objects, please refer to the description in the context of the embodiments, and no unnecessary limitation should be constituted due to the use of such prefixes. In addition, in the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

[0124] In the embodiments of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0125] Before listing the embodiments, the English expressions and their corresponding nouns involved in the embodiments are first explained as follows:

[0126] 1. LOCATION UPDATING ACCEPT

[0127] Meaning: A signaling in a mobile communication network that is used to respond to a LOCATION UPDATING REQUEST request initiated by a terminal (such as a mobile phone). When a terminal moves to a new location area, the network uses this signaling to inform the terminal that the location update has been accepted, and may carry network configuration information (such as a list of emergency call numbers).

[0128] 2. ATTACH ACCEPT

[0129] Meaning: When the terminal is turned on or reconnected to the network, it sends an ATTACH REQUEST request, and the network responds with this signaling, allowing the terminal to attach to the network. The signaling contains a temporary identifier (such as GUTI) and configuration parameters (such as a list of emergency call numbers) assigned by the network.

[0130] 3. TRACKING AREA UPDATE ACCEPT

[0131] Meaning: In LTE / 5G networks, when a terminal detects a change in the Tracking Area, it initiates a Tracking Area Update Request. The network confirms the update completion through this signaling and may update the terminal's tracking area list or emergency call number information.

[0132] 4. REGISTRATION ACCEPT

[0133] Meaning: In a 5G network, a terminal registers with the network through a REGISTRATION REQUEST request. The network confirms the registration success through this signaling and issues network policies (such as the validity flag of the emergency call number).

[0134] 5. Emergency number list IE

[0135] Full name: Emergency Number List Information Element

[0136] Meaning: An information element (IE) used to carry a list of emergency call numbers in signaling (such as ATTACH ACCEPT). For example, it contains numbers such as 110 and 119.

[0137] Spare bits: Unused bits reserved in this IE. In this solution, they are used to insert indicator identifiers (e.g., 1 bit to indicate whether the emergency number is valid).

[0138] 6. Extended emergency number list IE

[0139] Full name: Extended Emergency Number List Information Element

[0140] Meaning: Extended emergency number list information element, used to carry more types of emergency numbers (such as international emergency numbers). Similar to the Emergency number list IE, but supports longer lists or additional information.

[0141] 7. HPLMN

[0142] Full name: Home Public Land Mobile Network

[0143] Meaning: The terminal's home network (i.e. the operator network that the user has signed up for). For example, the HPLMN of a China Mobile user is China Mobile's network.

[0144] Equivalent PLMN: A partner network that has the same service rights as the HPLMN.

[0145] 8. VPLMN

[0146] Full name: Visited Public Land Mobile Network

[0147] Meaning: The network that the terminal is currently roaming to (non-home network). For example, when a China Mobile user roams to the AT&T network in the United States, AT&T is a VPLMN.

[0148] Key point: The indication identifier is ignored by the terminal in the VPLMN, i.e. the validity of the emergency number is controlled only by the HPLMN.

[0149] 9. TLV-E type / TV type

[0150] Full Name:

[0151] TLV-E: Type-Length-Value Extension (extended TLV structure).

[0152] TV: Type-Value (type-value structure).

[0153] Meaning: Two information element encoding formats. TLV-E supports more flexible data structures (such as nested fields), and TV is a simplified key-value pair format. This solution is used to add new information elements (such as the first additional information element).

[0154] 10. REGISTRATION REQUEST / ATTACH REQUEST

[0155] Meaning: A registration or attachment request initiated by a terminal to the network to access the network. For example, when the terminal is powered on, it sends an ATTACH REQUEST request to attach to the network.

[0156] 11. USIM

[0157] Full name: Universal Subscriber Identity Module

[0158] Meaning: Universal User Identity Module, which stores user identity information (such as IMSI), keys and operator configuration (such as preset emergency call numbers). In this solution, the indicator identifier is used to control whether the emergency number configured in the USIM is valid.

[0159] 12. PLMN

[0160] Full name: Public Land Mobile Network

[0161] Meaning: Public Land Mobile Network, which is a national or regional network of an operator (such as China Mobile, Verizon). Each PLMN is uniquely identified by MCC (country code) and MNC (operator code).

[0162] 13. Spare bit

[0163] Meaning: Bits reserved in the protocol with undefined usage. In this solution, these bits are reused to transmit the validity flag of the emergency number (for example, 0 means valid, 1 means invalid).

[0164] 14. Information Element (IE)

[0165] Meaning: A data unit defined in the protocol that contains specific information (such as a list of numbers, identifiers). For example, the Emergency number list IE is an IE that specifically carries emergency numbers.

[0166] Example 1

[0167] Figure 1 A flowchart of a method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure, the method for indicating is applied to a terminal side, and the method for indicating includes:

[0168] Step 101: Parse the indication signaling from the network side. The indication signaling includes an indication identifier, which is used to indicate whether the emergency call number on the terminal side is valid. Specifically, the indication identifier can be used to indicate whether the emergency call number on the terminal side is valid in the following three ways:

[0169] Method 1

[0170] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. The indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling. The following is a specific explanation:

[0171] Among them, the LOCATION UPDATING ACCEPT signaling is when the location of the terminal side changes (for example, moving from one base station coverage area to another base station coverage area), it will send a location update request to the network side. After confirmation, the network side will return this signaling to inform the terminal side that the location update is successful, and may also carry some location-related configuration information.

[0172] Among them, ATTACH ACCEPT signaling is when the terminal side is turned on or enters a network coverage area from an area without network coverage, it will initiate an attachment request (ATTACH REQUEST) to connect to the network. After accepting the request, the network side will reply to this signaling, indicating that the terminal side is allowed to access the network and allocate necessary network resources for it.

[0173] Among them, TRACKING AREA UPDATE ACCEPT signaling is when the terminal side moves from one tracking area to another, it needs to send a tracking area update request to the network side. The network side returns this signaling after processing to confirm that the tracking area update is successful and update the tracking area information on the terminal side.

[0174] Among them, REGISTRATION ACCEPT signaling is when the terminal side needs to perform certain specific registration operations (such as service registration, location registration, etc.), it will send a registration request (REGISTRATION REQUEST) to the network side. After confirmation, the network side will send this signaling as a response, indicating that the registration is successful, and may contain some authorization and configuration information.

[0175] The Emergency number list IE is a data unit in the signaling that is used to store information related to the emergency call number. Some bits in this data unit are reserved as spare bits, and the indicator identifier will be placed in one of these spare bits. The spare bits are used to store some additional, specific information, and here it is used to store the indicator identifier to convey relevant information such as the validity of the emergency call number.

[0176] Based on the above explanation, here is a specific example. Assume that in a city's mobile communication network, the operator has adjusted the management of emergency call numbers and needs to inform the terminal side of the relevant changes through signaling. The following is a possible situation:

[0177] During a certain period of time, due to the adjustment of base stations in some areas caused by urban construction, the operator decided to change the validity of some emergency call numbers in a specific area. When the terminal side (such as a mobile phone) is turned on or enters the coverage area of ​​a new base station, it will send an ATTACH REQUEST request to the network side to attach to the network. After receiving the request, the network side verifies and processes it and decides to send an ATTACH ACCEPT signaling to the terminal side as a response, indicating that the terminal side is allowed to attach to the network. In this ATTACH ACCEPT signaling, there is a data unit of Emergency number list IE, in which a spare bit is used to indicate the position of the identifier. If the operator stipulates that a certain emergency call number is invalid in the HPLMN and its equivalent PLMN at this time, the network side will set this spare bit to 1 (assuming 1 means invalid); if the regulation is valid, the spare bit will be set to 0 (assuming 0 means valid). For example, the current operator sets the emergency call number 110 as temporarily invalid in this area, then the spare bit of the Emergency number list IE will be set to 1 in the ATTACH ACCEPT signaling sent to the terminal side. After receiving the ATTACH ACCEPT signaling, the terminal side will parse the Emergency number list IE data unit and read the value of the spare bit. When the terminal side detects that the spare bit representing the emergency call number 911 is 1, it knows that the number 911 cannot be used for emergency calls temporarily in the current HPLMN and its equivalent PLMN. If the terminal side needs to make an emergency call later, it will perform corresponding processing according to this indication, such as prompting the user that the number is temporarily unavailable or dialing other valid emergency call numbers according to the new rules.

[0178] In this way, the network side can flexibly inform the terminal side of the validity status of the emergency call number through different types of indication signaling and indication identifiers at specific locations in the signaling to adapt to different network management requirements and actual situations.

[0179] Alternatively, the indication signaling may also include at least one of the following: ATTACH ACCEPT signaling, TRACKINGAREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. Then, the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling. The indication signaling and the indication identifier have been described in the above examples and will not be repeated here.

[0180] Optionally, by Figure 2 It can be seen that based on step 101, the indication method further includes: step 102, in response to the indication identifier being a first value, indicating that the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN. In step 102, when the indication identifier is the first value, it means that the network side conveys a message to the terminal side through this identifier, that is, the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN.

[0181] Step 103: In response to the indication identifier being the second value, the emergency call number in the terminal side is indicated to be invalid in the HPLMN and its equivalent PLMN. In step 103, when the indication identifier is the second value, it means that the network side informs the terminal side through this identifier that the emergency call number in the terminal side is invalid in the HPLMN and its equivalent PLMN.

[0182] Based on step 102 and step 103, a specific example is given here. Assume that in a city's mobile communication network, the operator needs to adjust the validity of the emergency call number due to some special reasons (such as network security upgrade, emergency response, etc.). The following is a specific example process:

[0183] A large-scale event was held in a certain city. In order to ensure the smooth progress of the event and communication security, the operator decided to temporarily adjust the validity of some emergency call numbers during the event. The operator sends a signaling containing an indication identifier to the terminal side through the base station on the network side (such as ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, or REGISTRATION ACCEPT signaling, etc.). Assume that the spare bits in the Emergency number list IE of this signaling are used to store the indication identifier. For some conventional emergency call numbers (such as 110, 119, etc.), the operator hopes that they will still be valid during the event, so the network side will set the indication identifier to the first value (assuming it is 0). When the terminal side receives this signaling and parses it to find that the indication identifier is 0, it will know that these emergency call numbers are valid in the HPLMN and its equivalent PLMN. Even if there are many people using the network at the same time at the event site, these numbers can be dialed normally for help in an emergency. For some special emergency call numbers that may cause network congestion or interfere with other communications (assuming that the operator temporarily designates a number 12345 for specific emergency command at an event site), the operator hopes to temporarily make it invalid in the HPLMN and its equivalent PLMN during the event. At this time, the network side will set the indication identifier to the second value (assuming it is 1). When the terminal side receives the signaling and parses it to find that the indication identifier is 1, it will know that this number is temporarily unavailable within the current network range, avoiding users from dialing by mistake, resulting in waste of network resources or other communication problems.

[0184] In this way, the network side can flexibly control the validity of the emergency call number according to the actual situation, ensuring the reasonable allocation of communication resources and the smooth progress of emergency communications under special circumstances.

[0185] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0186] In some cases, when the terminal side is in a visited public land mobile network (VPLMN), for the received signaling containing an indicator identifier, the terminal side can choose not to pay attention to or not to process according to the information carried by the indicator identifier. VPLMN is usually the network to which the terminal side is connected when roaming, which is different from the home public land mobile network (HPLMN). Since the network configuration, service rules, etc. of different network operators may differ, in order to ensure that the terminal side can communicate normally when roaming and avoid problems caused by inconsistent settings of emergency call numbers, etc. on different networks, it is allowed to ignore certain indicator identifiers in VPLMN.

[0187] That is to say, when the terminal side is in the HPLMN and its equivalent PLMN, the validity of the emergency call number will be determined according to the value of the indicator identifier. However, when the terminal side is in the VPLMN, since the VPLMN may have its own independent settings and management rules, for the same indicator identifier, the terminal side can choose to ignore it and handle emergency call-related matters according to the VPLMN's own rules.

[0188] Here is a specific example. Suppose a business person who travels frequently has a mobile phone card with a domestic operator A. When traveling to a foreign country, the local operator is operator B. The VPLMN connected at this time is the network of operator B. The following two specific usage scenarios can explain the role of the above settings:

[0189] Scenario 1-1: Emergency call number validity indication

[0190] In the country (HPLMN), operator A informs the mobile phone through network signaling that a specific emergency call number (such as 110 in the country) is valid in the HPLMN and its equivalent PLMN, and the mobile phone will normally identify and use the number according to this instruction. When traveling abroad, operator B's network sends a signal containing an identifier indicating the validity of the emergency call number, but due to different emergency call systems and number rules in different countries, operator B hopes to use the local emergency call number (such as the local 112). At this time, according to the rule that "the indicator identifier is ignored by the terminal side in the VPLMN", the mobile phone will ignore the indication of the validity of the number 12345 sent by operator A through signaling, and use the local emergency call number 112 in the VPLMN for emergency calls according to operator B's network rules.

[0191] Scenario 1-2: Network configuration adjustment

[0192] In China, operator A may adjust the validity of certain emergency call numbers in the HPLMN and its equivalent PLMN through signaling based on network construction and business needs. For example, temporarily set a certain auxiliary emergency call number to invalid. When in operator B's VPLMN abroad, operator B has its own network configuration and management strategy, and the mobile phone will ignore the indicator identifier sent by operator A that the auxiliary emergency call number is invalid. Because operator B may not recognize or need to follow the setting of operator A, but manage emergency call-related matters according to its own rules to ensure normal communication during roaming.

[0193] In this way, in different network environments, the terminal side can flexibly adapt to and follow the corresponding network rules to ensure smooth communication and effective use of the emergency call function.

[0194] The above is a description of method 1. The following is a specific example based on the processing logic of method 1 within the framework of the 3GPP standard protocol, as follows:

[0195] The indication signaling includes any one of the following: LOCATION UPDRURING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling, wherein the position of the indication identifier in the indication signaling is defined as follows:

[0196] 1. Define a USIMCFGV bit in the spare bit of the Emergency number list IE. For details, see Figure 3 .

[0197] 2. Define a USIMCFGV bit in the spare bit position in the Extended emergency number list IE. For details, see Figure 4 .

[0198] Then, further detailed description is given based on the above position definition.

[0199] 1. Improvements to Emergency number list IE

[0200] In the traditional signaling structure, the Emergency number list IE already contains the emergency number list and basic configuration information. This solution extends its functions in the following ways:

[0201] The traditional protocol field definition can refer to 3GPP TS 24.008, such as Figure 3 As shown, the indicator identifier is defined as the USIMCFGV bit, located at the 6th bit of byte 4 (it can also be at the 7th or 8th bit). The USIMCFGV bit is used to mark the validity of the emergency call number configured in the USIM in the HPLMN and its equivalent PLMN:

[0202] When the USIMCFGV bit is 0: the emergency number is valid;

[0203] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0204] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0205] 2. Improvements to Extended emergency number list IE

[0206] For the EPS / 5GS network architecture, new fields are further added to the Extended emergency number list IE. The traditional protocol field definitions can refer to 3GPP TS 24.301, such as Figure 4 As shown, the indicator identifier is defined as the USIMCFGV bit, located at the second bit of byte 4 (or other unused bits), which is used to mark the validity of the emergency call number configured in the USIM in the HPLMN and its equivalent PLMN:

[0207] When the USIMCFGV bit is 0: the emergency number is valid;

[0208] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0209] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0210] It should be understood that, whether it is an improvement on the Emergency number list IE or the Extended emergency number list IE, the USIMCFGV bit can indicate the validity or invalidity of the emergency number corresponding to the byte where it is located. Similarly, the USIMCFGV bit can also be used on the corresponding bits on other bytes to indicate the validity or invalidity of the emergency number corresponding to the byte where it is located. Or according to actual needs, the USIMCFGV bit corresponding to any emergency number (for example, the first emergency number) can indicate the validity or invalidity of all emergency numbers in the Emergency number list IE.

[0211] Here are some specific application examples:

[0212] Scenario 2-1: Emergency number in HPLMN is invalid

[0213] Due to base station renovation in a certain city, signal optimization has been implemented in some areas. The operator needs to temporarily disable the validity of number 12345 in a specific HPLMN. The specific process is as follows:

[0214] Terminal side behavior: After the mobile phone is turned on, it sends an ATTACH REQUEST request to attach to the network.

[0215] Network side response: The base station returns ATTACH ACCEPT signaling, in which the USIMCFGV bit of the Extended emergency numberlist IE is set to 1.

[0216] Terminal side processing: After parsing the signaling, it is determined that the number 12345 stored in the USIM is invalid in the current HPLMN.

[0217] Scenario 2-2: VPLMN roaming identifier ignored

[0218] When a user roams from a domestic HPLMN (operator A) to a foreign VPLMN (operator B):

[0219] Network configuration difference: Carrier B did not set USIMCFGV=1.

[0220] Terminal-side behavior: Ignore the setting of USIMCFGV=1 of operator A and continue to use local legal emergency numbers (such as 112).

[0221] In summary, Method 1 has the following technical advantages:

[0222] 1. Precise control: By adding the USIMCFGV bit, specific emergency numbers can be enabled / disabled on demand to avoid broadcasting configurations across the entire network.

[0223] 2. Compatible with extensions: Supports both Emergency list IE and Extended IE signaling structures, and is compatible with 2G / 3G / 4G / 5G multi-standard networks.

[0224] 3. Security: Set the validity period to be limited by the USIM status to prevent misjudgment caused by illegal tampering.

[0225] Method 2

[0226] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. The indication signaling has been explained in the above-mentioned method 1, and will not be repeated here.

[0227] The indication identifier is located in any spare bit position in the first additional information element in the indication signaling. The "first additional information element" here is a part of the signaling reserved for specific functions or information in this solution, and the spare bit position can be used to store additional, specific information, which is used to store the indication identifier in this case to convey relevant information such as the validity of the emergency call number.

[0228] Here, let's take a specific example to illustrate. Suppose in a city's mobile communication network, an operator wants to adjust the management of emergency call numbers. The following is a possible scenario:

[0229] Due to the adjustment of base stations in some areas caused by urban construction, the operator decided to change the validity of some emergency call numbers in a specific area. When the terminal side (such as a mobile phone) is turned on or enters the coverage area of ​​a new base station, it will send an ATTACH REQUEST request to the network side to attach to the network. After receiving the request, the network side verifies and processes it and decides to send an ATTACH ACCEPT signaling to the terminal side as a response, indicating that the terminal side is allowed to access the network. In this ATTACHACCEPT signaling, there is a first additional information element, in which a spare bit is used as the position of the indicator identifier. If the operator stipulates that a certain emergency call number is invalid in the HPLMN and its equivalent PLMN at this time, the network side will set this spare bit to 1 (assuming 1 means invalid); if the regulation is valid, it will be set to 0 (assuming 0 means valid). For example, the current operator sets the emergency call number 110 as temporarily invalid in this area, then in the ATTACH ACCEPT signaling sent to the terminal side, the spare bit of the first additional information element will be set to 1. After receiving the ATTACH ACCEPT signaling, the terminal side will parse the first additional information element and read the value of the spare bit. When the terminal side detects that the spare bit representing the emergency call number 110 is 1, it knows that the number 110 is temporarily unavailable for emergency calls in the current HPLMN and its equivalent PLMN. If the terminal side needs to make an emergency call later, it will perform corresponding processing according to this indication, such as prompting the user that the number is temporarily unavailable or dialing other valid emergency call numbers according to the new rules.

[0230] In this way, the network side can flexibly inform the terminal side of the validity status of the emergency call number through different types of indication signaling and indication identifiers at specific locations in the signaling to adapt to different network management requirements and actual situations.

[0231] Optionally, the first additional information element is of TLV-E type or TV type.

[0232] Among them, TV type is the abbreviation of "Type-Value". Compared with TLV-E type, it may be a more concise data representation. In this type, there are only two parts, "Type" and "Value". "Type" is used to identify the type of data, and "Value" is the corresponding data value. TV type is usually used to represent some simple, fixed-format data, such as the value of a flag bit (0 or 1) to represent a certain state (valid or invalid).

[0233] Among them, TLV-E type TLV is the abbreviation of "Tag-Length-Value", which is a common data encoding format. In the TLV-E type, "Tag" is used to identify the type or meaning of the data, "Length" indicates the length of the following "Value" part, and "Value" is the specific data content. "E" may indicate that this type has some specific extended attributes or functions, depending on the relevant protocols and design requirements. For example, in some network protocols, TLV-E type data elements can be used to carry more complex configuration information or status information, and different information categories are distinguished by different "Tag" values.

[0234] The first additional information element is specified as TLV-E type or TV type here to provide flexibility to the network side during design and implementation. Different types can be selected according to specific network scenarios and requirements, as follows:

[0235] If the network needs to carry more detailed information about the validity of emergency call numbers, or needs to support more complex configuration and status representation, then TLV-E may be more appropriate. For example, TLV-E can distinguish different emergency call number categories through different "Tag" values, and each category has corresponding "Length" and "Value" to describe its specific validity status and related parameters.

[0236] If you simply want to indicate the validity of the emergency call number (such as using 0 to indicate invalid and 1 to indicate valid), then the TV type is sufficient. The simplicity of the TV type can make signaling processing more efficient and reduce the overhead of data transmission and parsing.

[0237] The following is a general example to illustrate the use of TLV-E type and TV type in the first additional information element:

[0238] Suppose in a mobile communication network of a city, the operator needs to indicate the validity of the emergency call numbers on the terminal side according to different situations. Suppose there are two main scenarios for the management of emergency call numbers in the network: one is the change in the number validity caused by regular network maintenance, and the other is the adjustment of the number validity under special events (such as large-scale activities).

[0239] Regarding the example of TLV-E type:

[0240] When performing regular network maintenance, the operator hopes to inform the terminal side through signaling that some emergency call numbers are invalid within a specific time period. At this time, the ATTACH ACCEPT signaling sent by the network side contains a first additional information element, which adopts the TLV-E type. After receiving the signaling, the terminal side parses the first additional information element of the TLV-E type, identifies that this is the emergency call number validity information according to the Tag value, and then determines that the corresponding category of emergency call numbers is invalid within the specified time period according to the Value value.

[0241] Regarding the example of TV type:

[0242] During a special event (such as a large-scale concert), the operator only wants to simply inform the terminal side that a specific emergency call number (such as 110) is temporarily invalid at the event site. At this time, the TRACKING AREA UPDATE ACCEPT signaling sent by the network side contains a first additional information element, which adopts the TV type. After receiving the signaling, the terminal side parses the first additional information element of the TV type, identifies that it is the validity information of a specific emergency call number according to the Type value, and then determines that the emergency call number 110 is temporarily invalid at the event site according to the Value value.

[0243] From these two examples, it can be seen that the TLV-E type is suitable for complex scenarios that need to carry more detailed information, while the TV type is suitable for simple and direct representation methods. Under different network requirements, choosing the appropriate information element type can more effectively implement the indication of the validity of emergency call numbers.

[0244] The above is the description of Method 2. Next, based on the processing logic of Method 1, specific examples are listed within the framework of the 3GPP standard protocol as follows:

[0245] The indication signaling includes at least one of the following: LOCATION UPDURING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. The description of the indication signaling has been explained in Method 1 above and will not be elaborated here.

[0246] 1. Regarding the location of the indicator

[0247] The indicator identifier is located in the spare bit position of the newly added first additional information element. This IE is of TLV-E (Tag-Length-Value) type or TV (Type-Value) type, and is specifically used to transmit the validity status information of the emergency call number.

[0248] TLV-E type: Applicable to scenarios that require complex configurations (such as multi-category emergency number management).

[0249] TV type: Suitable for simple validity marking (such as 0 for invalid and 1 for valid).

[0250] 2. About the specific protocol definition

[0251] (1) TLV-E type first additional information element

[0252] The signaling format takes the REGISTRATION ACCEPT signaling of 5GS as an example, and defines the first additional information element as USIMEmergency number validation Indication. For details, see Figure 5 As can be seen from the figure, the indicator identifier is defined as the USIMCFGV bit, located at the first bit of byte 3:

[0253] When the USIMCFGV bit is 0: the emergency number is valid;

[0254] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0255] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0256] (2) TV type first additional information element

[0257] The signaling format takes the REGISTRATION ACCEPT signaling of 5GS as an example, and defines the first additional information element as USIMEmergency number validation Indication. For details, see Figure 6 As can be seen from the figure, the indicator identifier is defined as the USIMCFGV bit, located at the first bit of byte 1:

[0258] When the USIMCFGV bit is 0: the emergency number is valid;

[0259] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0260] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0261] 3. Specific application examples

[0262] Scenario 3-1: Emergency number failure in 5GS network

[0263] Due to network security upgrades in a certain city, the operator needs to temporarily disable the validity of number 12345 in a specific HPLMN:

[0264] Terminal side behavior: After the phone is turned on, it sends a REGISTRATION REQUEST request to register with the network.

[0265] Network side response: The base station returns REGISTRATION ACCEPT signaling, in which a new TLV-E type IE is added:

[0266] IEI: defines unused identifiers (such as XX);

[0267] Length: content length (fixed to 3 bytes);

[0268] USIMCFGV: Set to 1 to indicate that the emergency number is invalid.

[0269] Terminal side processing: After parsing the IE, it is determined that the number 12345 is invalid in the current HPLMN, triggering a user prompt.

[0270] Scenario 3-2: Simplified configuration of TV type in EPS network

[0271] During large-scale events, operators need to temporarily disable the validity of number 12345 in the event area:

[0272] Terminal-side behavior: When the mobile phone enters a new tracking area, it sends a TRACKING AREA UPDATE REQUEST.

[0273] Network side response: The base station returns the TRACKING AREA UPDATE ACCEPT signaling, in which the TV type IE is newly added:

[0274] IEI: defines unused identifiers (such as XX);

[0275] USIMCFGV: Set to 1 to indicate that the emergency number is invalid.

[0276] Terminal side processing: directly read the USIMCFGV value of the TV type IE without parsing complex fields.

[0277] 4. Cross-network architecture adaptation

[0278] The above summary of 5GS, EPS, and GSM / UTTRAN is shown in the following table:

[0279]

[0280] Regarding the definition rules of the first additional information element, 5GS can refer to Figure 7 as well as Figure 8 , EPS can be referenced Fig. 9 as well as Fig.10 .

[0281] In summary, Method 2 has the following technical advantages:

[0282] 1. Flexible scalability: Support multi-dimensional emergency number management through TLV-E type (such as configuring validity by scenario and number category). Implement efficient marking through TV type (such as single bit controlling the status of a single emergency number).

[0283] 2. Cross-network compatibility: New IEs are added to 5GS, EPS, and GSM / UTTRAN signaling to ensure consistency of terminal-side resolution.

[0284] 3. Security assurance: The newly added IE is only effective in the HPLMN and its equivalent PLMN, and is automatically ignored in the VPLMN to avoid cross-network interference.

[0285] Method 3

[0286] Optionally, by Fig.11 It can be seen that before the step of parsing the indication signaling from the network side in step 101, it also includes: step 100, sending a request message to the network side. The request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side. The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling. The indication identifier is located in the second additional information element in the indication signaling.

[0287] In the request message sent, the terminal side will include its own emergency call number to be confirmed. This means that the terminal side hopes to obtain information from the network side about whether these emergency call numbers are valid in the current network environment. Corresponding to the request message sent by the terminal side, the network side will return the corresponding indication signaling, including at least REGISTRATION ACCEPT (registration acceptance) signaling and ATTACH ACCEPT (attachment acceptance) signaling. These signalings are responses to the terminal side's request, and are used to inform the terminal side of the processing results of the request and related configuration information. The indication identifier is located in the second additional information element in the indication signaling. The "second additional information element" here is a part of the signaling of this solution reserved specifically for specific functions or information, which is used to store the indication identifier to convey relevant information such as the validity of the emergency call number.

[0288] In the third method, the terminal side actively sends a request message containing the emergency call number to be confirmed, and the network side can inform the terminal side of the validity of these emergency call numbers through the indication identifier in the second additional information element in the returned indication signaling according to its own network status and management policy. This method enables the terminal side to actively obtain the validity information of the emergency call number when needed, rather than passively waiting for regular updates or other notifications from the network side.

[0289] Here is a specific example. Suppose that in a city's mobile communication network, the operator is upgrading the network and the validity of some emergency call numbers may change. The following is a possible scenario:

[0290] The user on the terminal side (such as a mobile phone) learns that the operator is upgrading the network and is worried that the emergency call numbers stored in his mobile phone may be affected, so he wants to actively confirm the validity of these numbers with the network side. The terminal side sends a REGISTRATION REQUEST signaling to the network side, which contains an emergency call number to be confirmed, such as 110. This request message indicates that the terminal side wants to register with the network and at the same time inquires about the validity of number 110. After receiving the request message from the terminal side, the network side will process it according to the current network upgrade situation. If it is determined that number 110 is still valid in the current HPLMN and its equivalent PLMN, the network side will send a REGISTRATION ACCEPT signaling to the terminal side as a response. In this REGISTRATION ACCEPT signaling, there is a second additional information element, in which a spare bit (assuming it is the 5th bit) is used to indicate the position of the identifier. Since number 110 is valid, the network side will set this spare bit to 0 (assuming 0 means valid). After receiving the REGISTRATION ACCEPT signaling, the terminal side will parse the second additional information element and read the value of the spare bit. When the terminal side detects that the spare bit representing number 110 is 0, it knows that number 110 is valid and can be used normally in the current network environment. If the spare bit is 1 (assuming 1 means invalid), the terminal side will prompt the user that the number is temporarily unavailable, and may provide other alternative emergency call methods or wait for further message notifications.

[0291] In this way, the terminal side can actively obtain the validity information of the emergency call number when needed, ensuring that the emergency call function can be used correctly in an emergency.

[0292] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0293] In different scenarios, the network side may need to flexibly decide whether to send specific indication information about the validity of the emergency call number to the terminal side. For example, in some network conditions, the validity of all emergency call numbers is valid by default, and the network side does not feel it is necessary to send a second additional information element containing an indication identifier every time; in other cases, due to network adjustments and other reasons, the validity of the emergency call number has changed. At this time, the network side needs to inform the terminal side of the specific validity status by setting the information element indicator and carrying the second additional information element.

[0294] Here is a specific example. Assume that in a city's mobile communication network, operators have different strategies for managing emergency call numbers at different time periods. The following is a possible scenario:

[0295] Scenario 4-1: Default Validity

[0296] Network status: During daily network operation, operators believe that all emergency call numbers are valid in the HPLMN and its equivalent PLMN, and there is no need to emphasize this to the terminal side every time.

[0297] Signaling: When the terminal sends an ATTACH REQUEST message to the network, the network replies with an ATTACH ACCEPT signaling. The ATTACH ACCEPT signaling includes an information element indicator. Since the emergency call number is valid by default at this time, the value of the information element indicator is set to indicate "does not include the second additional information element". For example, assume that the information element indicator is 0 for not including and 1 for including.

[0298] Terminal side processing: After receiving the ATTACH ACCEPT signaling, the terminal side first checks the information element indicator. When the indicator value is 0, it knows that there is no need to find the second additional information element to determine the validity of the emergency call number, but by default, the emergency call number is considered to be valid in the current network environment.

[0299] Scenario 4-2: Changes in effectiveness

[0300] Network status: During a specific period of time, such as when a city holds a large-scale event, in order to ensure the smooth progress of the event and communication security, the operator decides to adjust the validity of certain emergency call numbers. For example, the temporary emergency call number 12345 originally used for on-site command of the event is set to be temporarily invalid.

[0301] Signaling: When the terminal sends a REGISTRATION REQUEST message to the network, the network replies with a REGISTRATION ACCEPT signaling. At this time, because the validity of the emergency call number has changed, the network will set the value of the information element indicator to indicate "includes the second additional information element", for example, to 1. At the same time, in the second additional information element of the REGISTRATION ACCEPT signaling, the indicator identifier is set through a specific spare bit. Assuming that the spare bit is the 7th bit, setting the 7th bit to 1 indicates that the number 12345 is invalid, and 0 indicates that it is valid.

[0302] Terminal side processing: After receiving the REGISTRATION ACCEPT signaling, the terminal side checks the information element indicator and finds that its value is 1, so it knows to look for specific information about the validity of the emergency call number in the second additional information element. Then read the value of the spare bit corresponding to the number 12345 in the second additional information element. If the 7th bit is 1, the terminal side will prompt the user that the number 12345 is temporarily unavailable, and perform corresponding operations according to the new rules or prompts.

[0303] In this way, the network side can flexibly control whether to send detailed indication information about the validity of the emergency call number to the terminal side according to actual conditions, and the terminal side can also accurately determine the validity status of the emergency call number based on the signaling content.

[0304] Optionally, the information element indicator is located in any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located in any spare bit position in the Extended emergency number list IE in the indication signaling. This means that the information element indicator can be in the spare bit position of the Emergency number list IE (emergency number list information element) or in the spare bit position of the Extended emergency number list IE (extended emergency number list information element). The spare bit position is a pre-set location for specific functions or information storage, which is used here to place the information element indicator to convey the message about whether the second additional information element exists.

[0305] Optionally, by Fig.12 It can be seen that, based on step 101, the indication method further includes:

[0306] Step 105: In response to the information element indicator in the indication signaling being the third value, the indication signaling does not include the second additional information element. This means that when the information element indicator takes the third value, the receiving party (terminal side) can know that the second additional information element for specifically indicating the validity of the emergency call number is not included in the indication signaling. At this time, the terminal side may handle the validity of the emergency call number according to the default rule or other preset methods.

[0307] Step 106: In response to the information element indicator in the indication signaling being the fourth value, the indication signaling includes the second additional information element. This means that when the information element indicator takes the fourth value, the terminal side will understand that the second additional information element is included in the indication signaling, and further analysis of the element is required to obtain detailed information about the validity of the emergency call number.

[0308] Among them, the several indicator identifiers contained in the second additional information element are used to indicate whether each emergency call number to be confirmed on the terminal side is valid. This shows that the specific content of the second additional information element is to determine the validity status of each emergency call number through the multiple indicator identifiers therein. Different identifiers correspond to different numbers, and their values ​​(such as 0 or 1) indicate whether the number is valid in the current network environment. For the definition rules of the second additional information element, 5GS can refer to Fig.13 .

[0309] Here is a general example:

[0310] Assume that in a city's mobile communication network, the operator needs to adjust the validity of the emergency call number. The following is a possible situation: due to network upgrades, the validity of some emergency call numbers has changed, while the validity of some emergency call numbers remains unchanged. The operator hopes to inform the terminal side of these changes through indication signaling. When the validity of some emergency call numbers remains unchanged, the network side sends ATTACH ACCEPT signaling to the terminal side (assuming this method is adopted). In this signaling, the information element indicator is located in a spare bit position in the Emergency number list IE, and its value is a third value (assuming 0). This means that the indication signaling does not contain the second additional information element. After the terminal side receives the signaling, it detects that the information element indicator is 0, and then knows that it does not need to look for the second additional information element, but considers that those emergency call numbers that have not changed are still valid according to the default rule. For those emergency call numbers whose validity has changed, the network side sends REGISTRATIONACCEPT signaling to the terminal side at another time (assuming this method is adopted). In this signaling, the information element indicator is located in a spare bit position in the Extended emergency number list IE, and its value is the fourth numerical value (assuming it is 1). This indicates that the indication signaling contains a second additional information element. After the terminal side receives the signaling and detects that the information element indicator is 1, it will parse the second additional information element. Assume that there are two indication identifiers in the second additional information element, corresponding to numbers 110 and 119 respectively. If the bit position of the identifier corresponding to number 110 is 0, it means that number 110 is valid; the bit position of the identifier corresponding to number 119 is 1, which means that number 119 is invalid. The terminal side updates its knowledge of the validity of the corresponding emergency call number based on the values ​​of these identifiers, and prompts the user of the status changes of the relevant numbers.

[0311] In this way, the network side can flexibly control the content and method of sending emergency call number validity information to the terminal side according to actual conditions, and the terminal side can also accurately determine the validity status of each emergency call number based on the signaling content.

[0312] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0313] Here, the indicator identifier may also have a specific function, which is to inform the terminal side (such as a mobile phone) whether the emergency call numbers pre-configured in its USIM card can be used normally in the current network environment.

[0314] Assume that in a city's mobile communication network, the operator needs to manage the validity of the emergency call number configured in the USIM card for some special reasons (such as network security policy adjustment, network upgrade, etc.). The following is a specific example process:

[0315] Operators plan to temporarily adjust some emergency call numbers and make them invalid for a period of time to avoid possible interference or other problems during network maintenance. The specific process is as follows:

[0316] 1. Network side preparation adjustment: The operator determines the emergency call numbers that need to be adjusted and the time period for adjustment, and makes corresponding configurations through network equipment. For example, it is decided to set numbers 122 and 123 to be invalid in the next 2 hours.

[0317] 2. Sending indication signaling: When the terminal side (such as a mobile phone) interacts with the network (such as attaching, registering, or updating the location), the network side will send a signaling containing an indication identifier to the terminal side according to the current configuration. Assume that the information is conveyed through ATTACH ACCEPT signaling, and the indication identifier is located in a specific position in the signaling (such as the spare bit in the Emergency number list IE).

[0318] 3. Terminal side analysis signaling: After receiving the ATTACH ACCEPT signaling, the terminal side will parse the indicator identifier according to the pre-agreed rules. If the value of the indicator identifier indicates that the emergency call number is invalid (assuming it is 1), then the terminal side knows that the corresponding number configured in its USIM card (such as 122 and 123) is temporarily unavailable in the current network environment.

[0319] 4. The terminal side prompts the user: The terminal side will prompt the user in an appropriate way according to the analysis results. For example, when the user tries to dial the number 122, a prompt box pops up on the screen to inform the user that "the emergency call number is temporarily unavailable, please choose another method"; or these invalid numbers are displayed in gray on the dialing interface, so that users cannot dial directly.

[0320] Restoration: After network maintenance is completed, the operator needs to restore the previously invalid emergency call number to a valid state. At this time, the network side will send a new indication identifier to the terminal side through similar signaling (such as REGISTRATION ACCEPT signaling). This time the value of the identifier indicates that the emergency call number is valid (assuming it is 0). After receiving the signaling, the terminal side will update the validity status of the corresponding number and prompt the user that these numbers can be used normally.

[0321] In this way, operators can flexibly manage the validity of the emergency call numbers configured in the USIM card according to actual needs, and the terminal side can also obtain this information in a timely and accurate manner to ensure that call operations can be performed correctly in emergency situations.

[0322] The above is an explanation of the third method. The following is a specific example based on the processing logic of the first method within the framework of the 3GPP standard protocol, as follows:

[0323] The request message contains the emergency call numbers to be confirmed on the terminal side, indicating that the terminal hopes to obtain the validity information of these numbers in the current network environment from the network side. The specific instructions are as follows:

[0324] 1. About the interaction logic of the newly added information elements

[0325] Terminal side behavior: Add USIMEmergency number list IE at the end of REGISTRATION REQUEST or ATTACH REQUEST message, carrying the emergency call number configured in the USIM card (derived from the EF_ECC file). If the USIM does not have an EF_ECC file, this field is not carried.

[0326] Network side behavior: parse the emergency number in the USIM Emergency number list IE and determine its validity. Add the following to the response signaling (REGISTRATION ACCEPT or ATTACH ACCEPT):

[0327] The value of the information element indicator is 1: the USIMCFGIND bit is 1, indicating that the USIM number validbit mapping IE needs to be carried.

[0328] The value of the information element indicator is 0: the USIMCFGIND bit is 0, indicating that the USIM numbervalid bit mapping IE is not required to be carried.

[0329] Bit-mapped emergency number validity in the USIM Emergency number list IE (1 for valid, 0 for invalid).

[0330] 2. Specific signaling format

[0331] (1) Take the REGISTRATION ACCEPT signaling of the 5GS solution as an example. For details, see Fig.14 ,

[0332] New fields in the request message (REGISTRATION REQUEST):

[0333] The USIMCFGIND bit is 1, in the second bit of byte 3, indicating whether the signaling carries the USIM number valid bit mapping IE. For details about USIM number valid bit mapping IE, see Fig.15 , corresponding to the emergency number in the USIM Emergency number list IE bit by bit, 1 means valid, 0 means invalid.

[0334] 3. Specific application examples

[0335] Scenario 5-1: The terminal actively confirms the validity of the emergency number

[0336] 1. Terminal-side behavior: The mobile phone user is concerned that the network upgrade will affect the validity of the emergency number 110, so he sends a REGISTRATION REQUEST and adds a USIM Emergency number list IE including the number 110 at the end of the message.

[0337] 2. Network side processing: After network verification, it is found that 110 is valid, so the following is set in REGISTRATION ACCEPT:

[0338] USIMCFGIND = 1;

[0339] The bit corresponding to 110 in the USIM number valid bit mapping IE is set to 1.

[0340] 3. Terminal side analysis: detect USIMCFGIND = 1, parse USIM number valid bit mappingIE, find that the bit corresponding to 110 is 1, and determine that the number is valid.

[0341] Scenario 5-2: The network adjusts the validity of emergency numbers in batches

[0342] 1. Network-side configuration: The operator sets the temporary emergency number 12345 at the event site to invalid and makes it effective through base station configuration.

[0343] 2. Terminal side behavior: After entering the activity area, the user sends an ATTACH REQUEST, carrying all emergency numbers (including 12345) in the USIM.

[0344] 3. Network side response:

[0345] In ATTACH ACCEPT set:

[0346] USIMCFGIND = 1;

[0347] In the USIM number valid bit mapping IE, the bits corresponding to 12345 are set to 0, and the bits corresponding to other numbers are set to 1.

[0348] 4. Terminal-side processing: After parsing the validity mapping, 12345 is disabled and the user is prompted: "Emergency number 12345 is temporarily unavailable in the current active area."

[0349] Method 3 has the following technical advantages:

[0350] 1. Active query: The terminal can initiate a request on demand to accurately obtain the validity status of the emergency number and reduce redundant signaling transmission.

[0351] 2. Flexible configuration: The network implements batch number validity control through USIMCFGIND and USIM number valid bit mapping IE, and supports on-demand enable / disable.

[0352] 3. Cross-network compatibility: New fields are added to 5GS, EPS, and GSM / UTTRAN signaling to ensure consistency of terminal-side parsing.

[0353] 4. Security assurance: Only valid for HPLMN and equivalent PLMN, automatically ignored in VPLMN to prevent cross-network interference.

[0354] In summary, Example 1 achieves refined control of the effectiveness of emergency call numbers through dynamic signaling extension and identifier mechanism, and its main technical effects are as follows:

[0355] 1. Flexible and dynamic emergency number management

[0356] Real-time policy delivery: The network side can indicate the validity status (valid / invalid) of the terminal emergency number in real time through the USIMCFGV bit in standard signaling (such as ATTACH ACCEPT / REGISTRATIONACCEPT), without the need for network-wide broadcasting or terminal pre-storage of complex rules.

[0357] On-demand precise control: Supports independent configuration of single emergency numbers or batches of numbers (such as temporarily disabling the special number 12345 for an active area) to avoid affecting emergency services across the entire network.

[0358] 2. Seamless compatibility across networks and standards

[0359] Adaptation to multiple network architectures: The emergency number validity identifier is uniformly extended in the signaling of network architectures such as 5GS, EPS, GSM / UTTRAN, ensuring the resolution consistency of terminals in different network environments (such as HPLMN / VPLMN, roaming scenarios).

[0360] Signaling multiplexing optimization: Use the spare bits of existing signaling (such as LOCATION UPDURING ACCEPT) or add TLV-E / TV information elements to avoid increasing signaling overhead.

[0361] 3. Efficient fault tolerance of terminal and network collaboration

[0362] Intelligent terminal processing: The terminal automatically determines the validity of the emergency number based on the signaling identifier. If the identifier is invalid or undefined, it will prioritize matching international emergency numbers (such as 110 / 119 / 911) or preset whitelists to ensure basic emergency communication capabilities.

[0363] Network policy conflict resolution: When the signaling does not clearly indicate, the terminal follows the network-side dynamic policy by default (such as USIMCFGV=0) and reports abnormal scenarios through logs to facilitate rapid problem location on the network side.

[0364] 4. Enhanced security and reliability

[0365] Anti-tampering protection: The validity range of the emergency number validity identifier is limited to the period when the USIM is inserted and the terminal is powered on. It is automatically reset after the card is removed or the terminal is powered off to prevent illegal configuration from remaining for a long time.

[0366] Redundancy verification mechanism: The terminal has a built-in whitelist verification. Even if the signaling on the network side fails, the availability of core emergency services can still be guaranteed through the pre-set emergency number library.

[0367] 5. User experience optimization

[0368] Real-time feedback and guidance: When the terminal detects that the emergency number is invalid, it actively prompts the user (such as pop-up window, gray display) to avoid misdialing and guide the user to switch to a valid number or contact network support.

[0369] Reduce network load: By dynamically disabling non-essential emergency numbers (such as numbers dedicated to temporary events), the occupation of network resources by invalid calls is reduced, improving the quality of emergency communications.

[0370] Example 2

[0371] Fig.16 A flowchart of a method for indicating an emergency call number provided by an exemplary embodiment of the present disclosure, the method for indicating is applied to a network side, and the method for indicating includes:

[0372] Step 201: Send an indication signaling to the terminal side, the indication signaling includes an indication identifier. The indication identifier is used to indicate whether the emergency call number on the terminal side is valid. Specifically, the indication identifier can be used to indicate whether the emergency call number on the terminal side is valid in the following three ways:

[0373] Method 1

[0374] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. The indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling. The following is a specific explanation:

[0375] Among them, the LOCATION UPDATING ACCEPT signaling is when the location of the terminal side changes (for example, moving from one base station coverage area to another base station coverage area), it will send a location update request to the network side. After confirmation, the network side will return this signaling to inform the terminal side that the location update is successful, and may also carry some location-related configuration information.

[0376] Among them, ATTACH ACCEPT signaling is when the terminal side is turned on or enters a network coverage area from an area without network coverage, it will initiate an attachment request (ATTACH REQUEST) to connect to the network. After accepting the request, the network side will reply to this signaling, indicating that the terminal side is allowed to access the network and allocate necessary network resources for it.

[0377] Among them, TRACKING AREA UPDATE ACCEPT signaling is when the terminal side moves from one tracking area to another, it needs to send a tracking area update request to the network side. The network side returns this signaling after processing to confirm that the tracking area update is successful and update the tracking area information on the terminal side.

[0378] Among them, REGISTRATION ACCEPT signaling is when the terminal side needs to perform certain specific registration operations (such as service registration, location registration, etc.), it will send a registration request (REGISTRATION REQUEST) to the network side. After confirmation, the network side will send this signaling as a response, indicating that the registration is successful, and may contain some authorization and configuration information.

[0379] The Emergency number list IE is a data unit in the signaling that is used to store information related to the emergency call number. Some bits in this data unit are reserved as spare bits, and the indicator identifier will be placed in one of these spare bits. The spare bits are used to store some additional, specific information, and here it is used to store the indicator identifier to convey relevant information such as the validity of the emergency call number.

[0380] Based on the above explanation, here is a specific example. Assume that in a city's mobile communication network, the operator has adjusted the management of emergency call numbers and needs to inform the terminal side of the relevant changes through signaling. The following is a possible situation:

[0381] During a certain period of time, due to the adjustment of base stations in some areas caused by urban construction, the operator decided to change the validity of some emergency call numbers in a specific area. When the terminal side (such as a mobile phone) is turned on or enters the coverage area of ​​a new base station, it will send an ATTACH REQUEST request to the network side to attach to the network. After receiving the request, the network side verifies and processes it and decides to send an ATTACH ACCEPT signaling to the terminal side as a response, indicating that the terminal side is allowed to attach to the network. In this ATTACH ACCEPT signaling, there is a data unit of Emergency number list IE, in which a spare bit is used to indicate the position of the identifier. If the operator stipulates that a certain emergency call number is invalid in the HPLMN and its equivalent PLMN at this time, the network side will set this spare bit to 1 (assuming 1 means invalid); if the regulation is valid, the spare bit will be set to 0 (assuming 0 means valid). For example, the current operator sets the emergency call number 110 as temporarily invalid in this area, then the spare bit of the Emergency number list IE will be set to 1 in the ATTACH ACCEPT signaling sent to the terminal side. After receiving the ATTACH ACCEPT signaling, the terminal side will parse the Emergency number list IE data unit and read the value of the spare bit. When the terminal side detects that the spare bit representing the emergency call number 911 is 1, it knows that the number 911 cannot be used for emergency calls temporarily in the current HPLMN and its equivalent PLMN. If the terminal side needs to make an emergency call later, it will perform corresponding processing according to this indication, such as prompting the user that the number is temporarily unavailable or dialing other valid emergency call numbers according to the new rules.

[0382] In this way, the network side can flexibly inform the terminal side of the validity status of the emergency call number through different types of indication signaling and indication identifiers at specific locations in the signaling to adapt to different network management requirements and actual situations.

[0383] Alternatively, the indication signaling may also include at least one of the following: ATTACH ACCEPT signaling, TRACKINGAREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. Then, the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling. The indication signaling and the indication identifier have been described in the above examples and will not be repeated here.

[0384] Optionally, the indication identifier takes a first value, which is used to indicate that the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN. When the indication identifier is the first value, it means that the network side conveys a message to the terminal side through this identifier, that is, the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN.

[0385] Alternatively, the indication identifier is a second value, which is used to indicate that the emergency call number on the terminal side is invalid in the HPLMN and its equivalent PLMN. When the indication identifier is a second value, it means that the network side informs the terminal side through this identifier that the emergency call number on the terminal side is invalid in the HPLMN and its equivalent PLMN.

[0386] Here is a specific example. Assume that in a city's mobile communication network, the operator needs to adjust the validity of the emergency call number for some special reasons (such as network security upgrade, emergency response, etc.). The following is a specific example process:

[0387] A large-scale event was held in a certain city. In order to ensure the smooth progress of the event and communication security, the operator decided to temporarily adjust the validity of some emergency call numbers during the event. The operator sends a signaling containing an indication identifier to the terminal side through the base station on the network side (such as ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, or REGISTRATION ACCEPT signaling, etc.). Assume that the spare bits in the Emergency number list IE of this signaling are used to store the indication identifier. For some conventional emergency call numbers (such as 110, 119, etc.), the operator hopes that they will still be valid during the event, so the network side will set the indication identifier to the first value (assuming it is 0). When the terminal side receives this signaling and parses it to find that the indication identifier is 0, it will know that these emergency call numbers are valid in the HPLMN and its equivalent PLMN. Even if there are many people using the network at the same time at the event site, these numbers can be dialed normally for help in an emergency. For some special emergency call numbers that may cause network congestion or interfere with other communications (assuming that the operator temporarily designates a number 12345 for specific emergency command at an event site), the operator hopes to temporarily make it invalid in the HPLMN and its equivalent PLMN during the event. At this time, the network side will set the indication identifier to the second value (assuming it is 1). When the terminal side receives the signaling and parses it to find that the indication identifier is 1, it will know that this number is temporarily unavailable within the current network range, avoiding users from dialing by mistake, resulting in waste of network resources or other communication problems.

[0388] In this way, the network side can flexibly control the validity of the emergency call number according to the actual situation, ensuring the reasonable allocation of communication resources and the smooth progress of emergency communications under special circumstances.

[0389] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0390] In some cases, when the terminal side is in a visited public land mobile network (VPLMN), for the received signaling containing an indicator identifier, the terminal side can choose not to pay attention to or not to process according to the information carried by the indicator identifier. VPLMN is usually the network to which the terminal side is connected when roaming, which is different from the home public land mobile network (HPLMN). Since the network configuration, service rules, etc. of different network operators may differ, in order to ensure that the terminal side can communicate normally when roaming and avoid problems caused by inconsistent settings of emergency call numbers, etc. on different networks, it is allowed to ignore certain indicator identifiers in VPLMN.

[0391] That is to say, when the terminal side is in the HPLMN and its equivalent PLMN, the validity of the emergency call number will be determined according to the value of the indicator identifier. However, when the terminal side is in the VPLMN, since the VPLMN may have its own independent settings and management rules, for the same indicator identifier, the terminal side can choose to ignore it and handle emergency call-related matters according to the VPLMN's own rules.

[0392] Here is a specific example. Suppose a business person who travels frequently has a mobile phone card with a domestic operator A. When traveling to a foreign country, the local operator is operator B. The VPLMN connected at this time is the network of operator B. The following two specific usage scenarios can explain the role of the above settings:

[0393] Scenario 1-1: Emergency call number validity indication

[0394] In the country (HPLMN), operator A informs the mobile phone through network signaling that a specific emergency call number (such as 110 in the country) is valid in the HPLMN and its equivalent PLMN, and the mobile phone will normally identify and use the number according to this instruction. When traveling abroad, operator B's network sends a signal containing an identifier indicating the validity of the emergency call number, but due to different emergency call systems and number rules in different countries, operator B hopes to use the local emergency call number (such as the local 112). At this time, according to the rule that "the indicator identifier is ignored by the terminal side in the VPLMN", the mobile phone will ignore the indication of the validity of the number 12345 sent by operator A through signaling, and use the local emergency call number 112 in the VPLMN for emergency calls according to operator B's network rules.

[0395] Scenario 1-2: Network configuration adjustment

[0396] In China, operator A may adjust the validity of certain emergency call numbers in the HPLMN and its equivalent PLMN through signaling based on network construction and business needs. For example, temporarily set a certain auxiliary emergency call number to invalid. When in operator B's VPLMN abroad, operator B has its own network configuration and management strategy. The mobile phone will ignore the indicator identifier sent by operator A that the auxiliary emergency call number is invalid. Because operator B may not recognize or need to follow the setting of operator A, but manage emergency call-related matters according to its own rules to ensure normal communication during roaming.

[0397] In this way, in different network environments, the terminal side can flexibly adapt to and follow the corresponding network rules to ensure smooth communication and effective use of the emergency call function.

[0398] The above is a description of method 1. The following is a specific example based on the processing logic of method 1 within the framework of the 3GPP standard protocol, as follows:

[0399] The indication signaling includes any one of the following: LOCATION UPDRURING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling, wherein the position of the indication identifier in the indication signaling is defined as follows:

[0400] 1. Define a USIMCFGV bit in the spare bit of the Emergency number list IE. For details, see Figure 3 .

[0401] 2. Define a USIMCFGV bit in the spare bit position in the Extended emergency number list IE. For details, see Figure 4 .

[0402] Then, further detailed description is given based on the above position definition.

[0403] 1. Improvements to Emergency number list IE

[0404] In the traditional signaling structure, the Emergency number list IE already contains the emergency number list and basic configuration information. This solution extends its functions in the following ways:

[0405] The traditional protocol field definition can refer to 3GPP TS 24.008, such as Figure 3 As shown, the indicator identifier is defined as the USIMCFGV bit, located at the 6th bit of byte 4 (it can also be at the 7th or 8th bit). The USIMCFGV bit is used to mark the validity of the emergency call number configured in the USIM in the HPLMN and its equivalent PLMN:

[0406] When the USIMCFGV bit is 0: the emergency number is valid;

[0407] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0408] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0409] 2. Improvements to Extended emergency number list IE

[0410] For the EPS / 5GS network architecture, new fields are further added to the Extended emergency number list IE. The traditional protocol field definitions can refer to 3GPP TS 24.301, such as Figure 4 As shown, the indicator identifier is defined as the USIMCFGV bit, located at the second bit of byte 4 (or other unused bits), which is used to mark the validity of the emergency call number configured in the USIM in the HPLMN and its equivalent PLMN:

[0411] When the USIMCFGV bit is 0: the emergency number is valid;

[0412] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0413] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0414] It should be understood that, whether it is an improvement on the Emergency number list IE or the Extended emergency number list IE, the USIMCFGV bit can indicate the validity or invalidity of the emergency number corresponding to the byte where it is located. Similarly, the USIMCFGV bit can also be used on the corresponding bits on other bytes to indicate the validity or invalidity of the emergency number corresponding to the byte where it is located. Or according to actual needs, the USIMCFGV bit corresponding to any emergency number (for example, the first emergency number) can indicate the validity or invalidity of all emergency numbers in the Emergency number list IE.

[0415] Here are some specific application examples:

[0416] Scenario 2-1: Emergency number in HPLMN is invalid

[0417] Due to base station renovation in a certain city, signal optimization has been implemented in some areas. The operator needs to temporarily disable the validity of number 12345 in a specific HPLMN. The specific process is as follows:

[0418] Terminal side behavior: After the mobile phone is turned on, it sends an ATTACH REQUEST request to attach to the network.

[0419] Network side response: The base station returns ATTACH ACCEPT signaling, in which the USIMCFGV bit of the Extended emergency numberlist IE is set to 1.

[0420] Terminal side processing: After parsing the signaling, it is determined that the number 12345 stored in the USIM is invalid in the current HPLMN.

[0421] Scenario 2-2: VPLMN roaming identifier ignored

[0422] When a user roams from a domestic HPLMN (operator A) to a foreign VPLMN (operator B):

[0423] Network configuration difference: Carrier B did not set USIMCFGV=1.

[0424] Terminal-side behavior: Ignore the setting of USIMCFGV=1 of operator A and continue to use local legal emergency numbers (such as 112).

[0425] In summary, method 1 has the following technical advantages:

[0426] 1. Precise control: By adding the USIMCFGV bit, specific emergency numbers can be enabled / disabled on demand to avoid broadcasting configurations across the entire network.

[0427] 2. Compatible with extensions: Supports both Emergency list IE and Extended IE signaling structures, and is compatible with 2G / 3G / 4G / 5G multi-standard networks.

[0428] 3. Security: Set the validity period to be limited by the USIM status to prevent misjudgment caused by illegal tampering.

[0429] Method 2

[0430] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. The indication signaling has been explained in the above-mentioned method 1, and will not be repeated here.

[0431] The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

[0432] The "first additional information element" here is a part of the signaling reserved for specific functions or information in this solution. The spare bits therein can be used to store additional, specific information, which is used here to store an indicator identifier to convey relevant information such as the validity of the emergency call number.

[0433] Here, let's take a specific example to illustrate. Suppose in a city's mobile communication network, an operator wants to adjust the management of emergency call numbers. The following is a possible scenario:

[0434] Due to the adjustment of base stations in some areas caused by urban construction, the operator decided to change the validity of some emergency call numbers in a specific area. When the terminal side (such as a mobile phone) is turned on or enters the coverage area of ​​a new base station, it will send an ATTACH REQUEST request to the network side to attach to the network. After receiving the request, the network side verifies and processes it and decides to send an ATTACH ACCEPT signaling to the terminal side as a response, indicating that the terminal side is allowed to access the network. In this ATTACHACCEPT signaling, there is a first additional information element, in which a spare bit is used as the position of the indicator identifier. If the operator stipulates that a certain emergency call number is invalid in the HPLMN and its equivalent PLMN at this time, the network side will set this spare bit to 1 (assuming 1 means invalid); if the regulation is valid, it will be set to 0 (assuming 0 means valid). For example, the current operator sets the emergency call number 110 as temporarily invalid in this area, then in the ATTACH ACCEPT signaling sent to the terminal side, the spare bit of the first additional information element will be set to 1. After receiving the ATTACH ACCEPT signaling, the terminal side will parse the first additional information element and read the value of the spare bit. When the terminal side detects that the spare bit representing the emergency call number 110 is 1, it knows that the number 110 is temporarily unavailable for emergency calls in the current HPLMN and its equivalent PLMN. If the terminal side needs to make an emergency call later, it will perform corresponding processing according to this indication, such as prompting the user that the number is temporarily unavailable or dialing other valid emergency call numbers according to the new rules.

[0435] In this way, the network side can flexibly inform the terminal side of the validity status of the emergency call number through different types of indication signaling and indication identifiers at specific locations in the signaling to adapt to different network management requirements and actual situations.

[0436] Optionally, the first additional information element is of TLV-E type or TV type.

[0437] Among them, TV type is the abbreviation of "Type-Value". Compared with TLV-E type, it may be a more concise data representation. In this type, there are only two parts, "Type" and "Value". "Type" is used to identify the type of data, and "Value" is the corresponding data value. TV type is usually used to represent some simple, fixed-format data, such as the value of a flag bit (0 or 1) to represent a certain state (valid or invalid).

[0438] Among them, TLV-E type TLV is the abbreviation of "Tag-Length-Value", which is a common data encoding format. In the TLV-E type, "Tag" is used to identify the type or meaning of the data, "Length" indicates the length of the following "Value" part, and "Value" is the specific data content. "E" may indicate that this type has some specific extended attributes or functions, depending on the relevant protocols and design requirements. For example, in some network protocols, TLV-E type data elements can be used to carry more complex configuration information or status information, and different information categories are distinguished by different "Tag" values.

[0439] The first additional information element is specified as TLV-E type or TV type here to provide flexibility to the network side during design and implementation. Different types can be selected according to specific network scenarios and requirements, as follows:

[0440] If the network needs to carry more detailed information about the validity of emergency call numbers, or needs to support more complex configuration and status representation, then TLV-E may be more appropriate. For example, TLV-E can distinguish different emergency call number categories through different "Tag" values, and each category has corresponding "Length" and "Value" to describe its specific validity status and related parameters.

[0441] If you simply want to indicate the validity of the emergency call number (such as using 0 to indicate invalid and 1 to indicate valid), then the TV type is sufficient. The simplicity of the TV type can make signaling processing more efficient and reduce the overhead of data transmission and parsing.

[0442] The following is a general example to illustrate the use of TLV-E type and TV type in the first additional information element:

[0443] Assume that in a city's mobile communication network, the operator needs to indicate the validity of the emergency call number on the terminal side according to different situations. Assume that there are two main emergency call number management scenarios in the network: one is the change of number validity caused by regular network maintenance, and the other is the number validity adjustment under special events (such as large-scale events).

[0444] About TLV-E type example:

[0445] When performing routine network maintenance, the operator hopes to inform the terminal side through signaling that certain emergency call numbers are invalid within a specific time period. At this time, the ATTACH ACCEPT signaling sent by the network side contains the first additional information element, which uses the TLV-E type. After receiving the signaling, the terminal side parses the first additional information element of the TLV-E type, identifies that this is the validity information of the emergency call number based on the Tag value, and then determines that the corresponding category of emergency call numbers are invalid within the specified time period based on the Value value.

[0446] About TV type examples:

[0447] During special events (such as large concerts), the operator simply wants to inform the terminal that a specific emergency call number (such as 110) is temporarily invalid at the event site. At this time, the TRACKING AREA UPDATEACCEPT signaling sent by the network side contains the first additional information element, which uses the TV type. After receiving the signaling, the terminal side parses the first additional information element of the TV type, identifies the validity information of the specific emergency call number based on the Type value, and then determines that the emergency call number 110 is temporarily invalid at the event site based on the Value value.

[0448] Through these two examples, we can see that the TLV-E type is suitable for complex scenarios that need to carry more detailed information, while the TV type is suitable for simple and direct representation. Under different network requirements, choosing the appropriate information element type can more effectively indicate the validity of the emergency call number.

[0449] The above is an explanation of the second method. The following is a specific example based on the processing logic of the first method within the framework of the 3GPP standard protocol, as follows:

[0450] The indication signaling includes at least one of the following: LOCATION UPDRURING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling. The indication signaling has been explained in the above-mentioned method 1, and will not be repeated here.

[0451] 1. Regarding the location of the indicator

[0452] The indicator identifier is located in the spare bit position of the newly added first additional information element. This IE is of TLV-E (Tag-Length-Value) type or TV (Type-Value) type, and is specifically used to transmit the validity status information of the emergency call number.

[0453] TLV-E type: Applicable to scenarios that require complex configurations (such as multi-category emergency number management).

[0454] TV type: Suitable for simple validity marking (such as 0 for invalid and 1 for valid).

[0455] 2. About the specific protocol definition

[0456] (1) TLV-E type first additional information element

[0457] The signaling format takes the REGISTRATION ACCEPT signaling of 5GS as an example, and defines the first additional information element as USIMEmergency number validation Indication. For details, see Figure 5 As can be seen from the figure, the indicator identifier is defined as the USIMCFGV bit, located at the first bit of byte 3:

[0458] When the USIMCFGV bit is 0: the emergency number is valid;

[0459] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0460] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0461] (2) TV type first additional information element

[0462] The signaling format takes the REGISTRATION ACCEPT signaling of 5GS as an example, and defines the first additional information element as USIMEmergency number validation Indication. For details, see Figure 6 As can be seen from the figure, the indicator identifier is defined as the USIMCFGV bit, located at the first bit of byte 1:

[0463] When the USIMCFGV bit is 0: the emergency number is valid;

[0464] When the USIMCFGV bit is set to 1: the emergency number is invalid.

[0465] In addition, the terminal determines the emergency number status based on this bit in the HPLMN and its equivalent PLMN, and automatically ignores the identifier when roaming to the VPLMN. This setting is only effective when the USIM is inserted and the terminal is turned on, and is reset to the default state after the USIM is removed or turned off.

[0466] 3. Specific application examples

[0467] Scenario 3-1: Emergency number failure in 5GS network

[0468] Due to network security upgrades in a certain city, the operator needs to temporarily disable the validity of number 12345 in a specific HPLMN:

[0469] Terminal side behavior: After the phone is turned on, it sends a REGISTRATION REQUEST request to register with the network.

[0470] Network side response: The base station returns REGISTRATION ACCEPT signaling, in which a new TLV-E type IE is added:

[0471] IEI: defines unused identifiers (such as XX);

[0472] Length: content length (fixed to 3 bytes);

[0473] USIMCFGV: Set to 1 to indicate that the emergency number is invalid.

[0474] Terminal side processing: After parsing the IE, it is determined that the number 12345 is invalid in the current HPLMN, triggering a user prompt.

[0475] Scenario 3-2: Simplified configuration of TV type in EPS network

[0476] During large-scale events, operators need to temporarily disable the validity of number 12345 in the event area:

[0477] Terminal-side behavior: When the mobile phone enters a new tracking area, it sends a TRACKING AREA UPDATE REQUEST.

[0478] Network side response: The base station returns the TRACKING AREA UPDATE ACCEPT signaling, in which the TV type IE is newly added:

[0479] IEI: defines unused identifiers (such as XX);

[0480] USIMCFGV: Set to 1 to indicate that the emergency number is invalid.

[0481] Terminal side processing: directly read the USIMCFGV value of the TV type IE without parsing complex fields.

[0482] 4. Cross-network architecture adaptation

[0483] The above summary of 5GS, EPS, and GSM / UTTRAN is shown in the following table:

[0484]

[0485] Regarding the definition rules of the first additional information element, 5GS can refer to Figure 7 as well as Figure 8 , EPS can be referenced Fig. 9 as well as Fig.10 .

[0486] In summary, Method 2 has the following technical advantages:

[0487] 1. Flexible scalability: Support multi-dimensional emergency number management through TLV-E type (such as configuring validity by scenario and number category). Implement efficient marking through TV type (such as single bit controlling the status of a single emergency number).

[0488] 2. Cross-network compatibility: New IEs are added to 5GS, EPS, and GSM / UTTRAN signaling to ensure consistency of terminal-side resolution.

[0489] 3. Security assurance: The newly added IE is only effective in the HPLMN and its equivalent PLMN, and is automatically ignored in the VPLMN to avoid cross-network interference.

[0490] Method 3

[0491] Alternatively, see Fig.17 It can be seen that before step 201, the step of sending the indication signaling to the terminal side, the following steps are also included:

[0492] Step 202 receives a request message from the terminal side. The request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side. The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling. The indication identifier is located in the second additional information element in the indication signaling.

[0493] In the request message sent, the terminal side will include its own emergency call number to be confirmed. This means that the terminal side hopes to obtain information from the network side about whether these emergency call numbers are valid in the current network environment. Corresponding to the request message sent by the terminal side, the network side will return the corresponding indication signaling, including at least REGISTRATION ACCEPT (registration acceptance) signaling and ATTACH ACCEPT (attachment acceptance) signaling. These signalings are responses to the terminal side's request, and are used to inform the terminal side of the processing results of the request and related configuration information. The indication identifier is located in the second additional information element in the indication signaling. The "second additional information element" here is a part of the signaling of this solution reserved specifically for specific functions or information, which is used to store the indication identifier to convey relevant information such as the validity of the emergency call number.

[0494] In the third method, the terminal side actively sends a request message containing the emergency call number to be confirmed, and the network side can inform the terminal side of the validity of these emergency call numbers through the indication identifier in the second additional information element in the returned indication signaling according to its own network status and management policy. This method enables the terminal side to actively obtain the validity information of the emergency call number when needed, rather than passively waiting for regular updates or other notifications from the network side.

[0495] Here is a specific example. Suppose that in a city's mobile communication network, the operator is upgrading the network and the validity of some emergency call numbers may change. The following is a possible scenario:

[0496] The user on the terminal side (such as a mobile phone) learns that the operator is upgrading the network and is worried that the emergency call numbers stored in his mobile phone may be affected, so he wants to actively confirm the validity of these numbers with the network side. The terminal side sends a REGISTRATION REQUEST signaling to the network side, which contains an emergency call number to be confirmed, such as 110. This request message indicates that the terminal side wants to register with the network and at the same time inquires about the validity of number 110. After receiving the request message from the terminal side, the network side will process it according to the current network upgrade situation. If it is determined that number 110 is still valid in the current HPLMN and its equivalent PLMN, the network side will send a REGISTRATION ACCEPT signaling to the terminal side as a response. In this REGISTRATION ACCEPT signaling, there is a second additional information element, in which a spare bit (assuming it is the 5th bit) is used to indicate the position of the identifier. Since number 110 is valid, the network side will set this spare bit to 0 (assuming 0 means valid). After receiving the REGISTRATION ACCEPT signaling, the terminal side will parse the second additional information element and read the value of the spare bit. When the terminal side detects that the spare bit representing number 110 is 0, it knows that number 110 is valid and can be used normally in the current network environment. If the spare bit is 1 (assuming 1 means invalid), the terminal side will prompt the user that the number is temporarily unavailable, and may provide other alternative emergency call methods or wait for further message notifications.

[0497] In this way, the terminal side can actively obtain the validity information of the emergency call number when needed, ensuring that the emergency call function can be used correctly in an emergency.

[0498] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0499] In different scenarios, the network side may need to flexibly decide whether to send specific indication information about the validity of the emergency call number to the terminal side. For example, in some network conditions, the validity of all emergency call numbers is valid by default, and the network side does not feel it is necessary to send a second additional information element containing an indication identifier every time; in other cases, due to network adjustments and other reasons, the validity of the emergency call number has changed. At this time, the network side needs to inform the terminal side of the specific validity status by setting the information element indicator and carrying the second additional information element.

[0500] Here is a specific example. Assume that in a city's mobile communication network, operators have different strategies for managing emergency call numbers at different time periods. The following is a possible scenario:

[0501] Scenario 4-1: Default Validity

[0502] Network status: During daily network operation, operators believe that all emergency call numbers are valid in the HPLMN and its equivalent PLMN, and there is no need to emphasize this to the terminal side every time.

[0503] Signaling: When the terminal sends an ATTACH REQUEST message to the network, the network replies with an ATTACH ACCEPT signaling. The ATTACH ACCEPT signaling includes an information element indicator. Since the emergency call number is valid by default at this time, the value of the information element indicator is set to indicate "does not include the second additional information element". For example, assume that the information element indicator is 0 for not including and 1 for including.

[0504] Terminal side processing: After receiving the ATTACH ACCEPT signaling, the terminal side first checks the information element indicator. When the indicator value is 0, it knows that there is no need to find the second additional information element to determine the validity of the emergency call number, but by default, the emergency call number is considered to be valid in the current network environment.

[0505] Scenario 4-2: Changes in effectiveness

[0506] Network status: During a specific period of time, such as when a city holds a large-scale event, in order to ensure the smooth progress of the event and communication security, the operator decides to adjust the validity of certain emergency call numbers. For example, the temporary emergency call number 12345 originally used for on-site command of the event is set to be temporarily invalid.

[0507] Signaling: When the terminal sends a REGISTRATION REQUEST message to the network, the network replies with a REGISTRATION ACCEPT signaling. At this time, because the validity of the emergency call number has changed, the network will set the value of the information element indicator to indicate "includes the second additional information element", for example, to 1. At the same time, in the second additional information element of the REGISTRATION ACCEPT signaling, the indicator identifier is set through a specific spare bit. Assuming that the spare bit is the 7th bit, setting the 7th bit to 1 indicates that the number 12345 is invalid, and 0 indicates that it is valid.

[0508] Terminal side processing: After receiving the REGISTRATION ACCEPT signaling, the terminal side checks the information element indicator and finds that its value is 1, so it knows to look for specific information about the validity of the emergency call number in the second additional information element. Then read the value of the spare bit corresponding to the number 12345 in the second additional information element. If the 7th bit is 1, the terminal side will prompt the user that the number 12345 is temporarily unavailable, and perform corresponding operations according to the new rules or prompts.

[0509] In this way, the network side can flexibly control whether to send detailed indication information about the validity of the emergency call number to the terminal side according to actual conditions, and the terminal side can also accurately determine the validity status of the emergency call number based on the signaling content.

[0510] Optionally, the information element indicator is located in any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located in any spare bit position in the Extended emergency number list IE in the indication signaling. This means that the information element indicator can be in the spare bit position of the Emergency number list IE (emergency number list information element) or in the spare bit position of the Extended emergency number list IE (extended emergency number list information element). The spare bit position is a pre-set location for specific functions or information storage, which is used here to place the information element indicator to convey the message about whether the second additional information element exists.

[0511] If the information element indicator in the indication signaling takes the third value, it is used to indicate that the second additional information element is not included in the indication signaling. This means that when the information element indicator takes the third value, the receiving party (terminal side) can know that the second additional information element for specifically indicating the validity of the emergency call number is not included in this indication signaling. At this time, the terminal side may handle the validity of the emergency call number according to the default rule or other preset methods.

[0512] Alternatively, if the information element indicator in the indication signaling takes the fourth value, it is used to indicate that the second additional information element is included in the indication signaling. This means that when the information element indicator takes the fourth value, the terminal side will understand that the second additional information element is included in the indication signaling, and further analysis of the element is required to obtain detailed information about the validity of the emergency call number.

[0513] Among them, the several indicator identifiers contained in the second additional information element are used to indicate whether each emergency call number to be confirmed on the terminal side is valid. This shows that the specific content of the second additional information element is to determine the validity status of each emergency call number through the multiple indicator identifiers therein. Different identifiers correspond to different numbers, and their values ​​(such as 0 or 1) indicate whether the number is valid in the current network environment. For the definition rules of the second additional information element, 5GS can refer to Fig.13 .

[0514] Here is a general example:

[0515] Assume that in a city's mobile communication network, the operator needs to adjust the validity of the emergency call number. The following is a possible situation: due to network upgrades, the validity of some emergency call numbers has changed, while the validity of some emergency call numbers remains unchanged. The operator hopes to inform the terminal side of these changes through indication signaling. When the validity of some emergency call numbers remains unchanged, the network side sends ATTACH ACCEPT signaling to the terminal side (assuming this method is adopted). In this signaling, the information element indicator is located in a spare bit position in the Emergency number list IE, and its value is a third value (assuming 0). This means that the indication signaling does not contain the second additional information element. After the terminal side receives the signaling, it detects that the information element indicator is 0, and then knows that it does not need to look for the second additional information element, but considers that those emergency call numbers that have not changed are still valid according to the default rule. For those emergency call numbers whose validity has changed, the network side sends REGISTRATIONACCEPT signaling to the terminal side at another time (assuming this method is adopted). In this signaling, the information element indicator is located in a spare bit position in the Extended emergency number list IE, and its value is the fourth numerical value (assuming it is 1). This indicates that the indication signaling contains a second additional information element. After the terminal side receives the signaling and detects that the information element indicator is 1, it will parse the second additional information element. Assume that there are two indication identifiers in the second additional information element, corresponding to numbers 110 and 119 respectively. If the bit position of the identifier corresponding to number 110 is 0, it means that number 110 is valid; the bit position of the identifier corresponding to number 119 is 1, which means that number 119 is invalid. The terminal side updates its knowledge of the validity of the corresponding emergency call number based on the values ​​of these identifiers, and prompts the user of the status changes of the relevant numbers.

[0516] In this way, the network side can flexibly control the content and method of sending emergency call number validity information to the terminal side according to actual conditions, and the terminal side can also accurately determine the validity status of each emergency call number based on the signaling content.

[0517] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0518] Here, the indicator identifier may also have a specific function, which is to inform the terminal side (such as a mobile phone) whether the emergency call numbers pre-configured in its USIM card can be used normally in the current network environment.

[0519] Assume that in a city's mobile communication network, the operator needs to manage the validity of the emergency call number configured in the USIM card for some special reasons (such as network security policy adjustment, network upgrade, etc.). The following is a specific example process:

[0520] Operators plan to temporarily adjust some emergency call numbers and make them invalid for a period of time to avoid possible interference or other problems during network maintenance. The specific process is as follows:

[0521] 1. Network side preparation adjustment: The operator determines the emergency call numbers that need to be adjusted and the time period for adjustment, and makes corresponding configurations through network equipment. For example, it is decided to set numbers 122 and 123 to be invalid in the next 2 hours.

[0522] 2. Sending indication signaling: When the terminal side (such as a mobile phone) interacts with the network (such as attaching, registering, or updating the location), the network side will send a signaling containing an indication identifier to the terminal side according to the current configuration. Assume that the information is conveyed through ATTACH ACCEPT signaling, and the indication identifier is located in a specific position in the signaling (such as the spare bit in the Emergency number list IE).

[0523] 3. Terminal side analysis signaling: After receiving the ATTACH ACCEPT signaling, the terminal side will parse the indicator identifier according to the pre-agreed rules. If the value of the indicator identifier indicates that the emergency call number is invalid (assuming it is 1), then the terminal side knows that the corresponding number configured in its USIM card (such as 122 and 123) is temporarily unavailable in the current network environment.

[0524] 4. The terminal side prompts the user: The terminal side will prompt the user in an appropriate way according to the analysis results. For example, when the user tries to dial the number 122, a prompt box pops up on the screen to inform the user that "the emergency call number is temporarily unavailable, please choose another method"; or these invalid numbers are displayed in gray on the dialing interface, so that users cannot dial directly.

[0525] Restoration: After network maintenance is completed, the operator needs to restore the previously invalid emergency call number to a valid state. At this time, the network side will send a new indication identifier to the terminal side through similar signaling (such as REGISTRATION ACCEPT signaling). This time the value of the identifier indicates that the emergency call number is valid (assuming it is 0). After receiving the signaling, the terminal side will update the validity status of the corresponding number and prompt the user that these numbers can be used normally.

[0526] In this way, operators can flexibly manage the validity of the emergency call numbers configured in the USIM card according to actual needs, and the terminal side can also obtain this information in a timely and accurate manner to ensure that call operations can be performed correctly in emergency situations.

[0527] The above is an explanation of the third method. The following is a specific example based on the processing logic of the first method within the framework of the 3GPP standard protocol, as follows:

[0528] The request message contains the emergency call numbers to be confirmed on the terminal side, indicating that the terminal hopes to obtain the validity information of these numbers in the current network environment from the network side. The specific instructions are as follows:

[0529] 1. About the interaction logic of the newly added information elements

[0530] Terminal side behavior: Add USIMEmergency number list IE at the end of REGISTRATION REQUEST or ATTACH REQUEST message, carrying the emergency call number configured in the USIM card (derived from the EF_ECC file). If the USIM does not have an EF_ECC file, this field is not carried.

[0531] Network side behavior: parse the emergency number in the USIM Emergency number list IE and determine its validity. Add the following to the response signaling (REGISTRATION ACCEPT or ATTACH ACCEPT):

[0532] The value of the information element indicator is 1: the USIMCFGIND bit is 1, indicating that the USIM number validbit mapping IE needs to be carried.

[0533] The value of the information element indicator is 0: the USIMCFGIND bit is 0, indicating that the USIM numbervalid bit mapping IE is not required to be carried.

[0534] Bit-mapped emergency number validity in the USIM Emergency number list IE (1 for valid, 0 for invalid).

[0535] 2. Specific signaling format

[0536] (1) Take the REGISTRATION ACCEPT signaling of the 5GS solution as an example. For details, see Fig.14 ,

[0537] New fields in the request message (REGISTRATION REQUEST):

[0538] The USIMCFGIND bit is 1, in the second bit of byte 3, indicating whether the signaling carries the USIM number valid bit mapping IE. For details about USIM number valid bit mapping IE, see Fig.15 , corresponding to the emergency number in the USIM Emergency number list IE bit by bit, 1 means valid, 0 means invalid.

[0539] 3. Specific application examples

[0540] Scenario 5-1: The terminal actively confirms the validity of the emergency number

[0541] 1. Terminal-side behavior: The mobile phone user is concerned that the network upgrade will affect the validity of the emergency number 110, so he sends a REGISTRATION REQUEST and adds a USIM Emergency number list IE including the number 110 at the end of the message.

[0542] 2. Network side processing: After network verification, it is found that 110 is valid, so the following is set in REGISTRATION ACCEPT:

[0543] USIMCFGIND = 1;

[0544] The bit corresponding to 110 in the USIM number valid bit mapping IE is set to 1.

[0545] 3. Terminal side analysis: detect USIMCFGIND = 1, parse USIM number valid bit mappingIE, find that the bit corresponding to 110 is 1, and determine that the number is valid.

[0546] Scenario 5-2: The network adjusts the validity of emergency numbers in batches

[0547] 1. Network-side configuration: The operator sets the temporary emergency number 12345 at the event site to invalid and makes it effective through base station configuration.

[0548] 2. Terminal side behavior: After entering the activity area, the user sends an ATTACH REQUEST, carrying all emergency numbers (including 12345) in the USIM.

[0549] 3. Network side response:

[0550] In ATTACH ACCEPT set:

[0551] USIMCFGIND = 1;

[0552] In the USIM number valid bit mapping IE, the bits corresponding to 12345 are set to 0, and the bits corresponding to other numbers are set to 1.

[0553] 4. Terminal-side processing: After parsing the validity mapping, 12345 is disabled and the user is prompted: "Emergency number 12345 is temporarily unavailable in the current active area."

[0554] Method 3 has the following technical advantages:

[0555] 1. Active query: The terminal can initiate a request on demand to accurately obtain the validity status of the emergency number and reduce redundant signaling transmission.

[0556] 2. Flexible configuration: The network implements batch number validity control through USIMCFGIND and USIM number valid bit mapping IE, and supports on-demand enable / disable.

[0557] 3. Cross-network compatibility: New fields are added to 5GS, EPS, and GSM / UTTRAN signaling to ensure consistency of terminal-side parsing.

[0558] 4. Security assurance: Only valid for HPLMN and equivalent PLMN, automatically ignored in VPLMN to prevent cross-network interference.

[0559] In summary, Example 2 achieves refined control of the effectiveness of emergency call numbers through dynamic signaling extension and identifier mechanism, and its main technical effects are as follows:

[0560] 1. Flexible and dynamic emergency number management

[0561] Real-time policy delivery: The network side can indicate the validity status (valid / invalid) of the terminal emergency number in real time through the USIMCFGV bit in standard signaling (such as ATTACH ACCEPT / REGISTRATIONACCEPT), without the need for network-wide broadcasting or terminal pre-storage of complex rules.

[0562] On-demand precise control: Supports independent configuration of single emergency numbers or batches of numbers (such as temporarily disabling the special number 12345 for an active area) to avoid affecting emergency services across the entire network.

[0563] 2. Seamless compatibility across networks and standards

[0564] Adaptation to multiple network architectures: The emergency number validity identifier is uniformly extended in the signaling of network architectures such as 5GS, EPS, GSM / UTTRAN, ensuring the resolution consistency of terminals in different network environments (such as HPLMN / VPLMN, roaming scenarios).

[0565] Signaling multiplexing optimization: Use the spare bits of existing signaling (such as LOCATION UPDURING ACCEPT) or add TLV-E / TV information elements to avoid increasing signaling overhead.

[0566] 3. Efficient fault tolerance of terminal and network collaboration

[0567] Intelligent terminal processing: The terminal automatically determines the validity of the emergency number based on the signaling identifier. If the identifier is invalid or undefined, it will prioritize matching international emergency numbers (such as 110 / 119 / 911) or preset whitelists to ensure basic emergency communication capabilities.

[0568] Network policy conflict resolution: When the signaling does not clearly indicate, the terminal follows the network-side dynamic policy by default (such as USIMCFGV=0) and reports abnormal scenarios through logs to facilitate rapid problem location on the network side.

[0569] 4. Enhanced security and reliability

[0570] Anti-tampering protection: The validity range of the emergency number validity identifier is limited to the period when the USIM is inserted and the terminal is powered on. It is automatically reset after the card is removed or the terminal is powered off to prevent illegal configuration from remaining for a long time.

[0571] Redundancy verification mechanism: The terminal has a built-in whitelist verification. Even if the signaling on the network side fails, the availability of core emergency services can still be guaranteed through the pre-set emergency number library.

[0572] 5. User experience optimization

[0573] Real-time feedback and guidance: When the terminal detects that the emergency number is invalid, it actively prompts the user (such as pop-up window, gray display) to avoid misdialing and guide the user to switch to a valid number or contact network support.

[0574] Reduce network load: By dynamically disabling non-essential emergency numbers (such as numbers dedicated to temporary events), the occupation of network resources by invalid calls is reduced, improving the quality of emergency communications.

[0575] Example 3

[0576] Corresponding to the embodiment of the method for indicating an emergency call number in the aforementioned embodiment 1, the present disclosure also provides an embodiment of a system for indicating an emergency call number.

[0577] Fig.18 A module schematic diagram of an emergency call number indication system provided by an exemplary embodiment of the present disclosure, the indication system is applied to a terminal side, and the indication system includes:

[0578] The parsing module 31 is used to parse the indication signaling from the network side, where the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number on the terminal side is valid.

[0579] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling;

[0580] or,

[0581] The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

[0582] Alternatively, see Fig.19 It can be seen that the indication system further includes: a first response module 32, for indicating that the emergency call number in the terminal side is valid in the HPLMN and its equivalent PLMN in response to the indication identifier being a first value;

[0583] The first response module 32 is further configured to, in response to the indication identifier being a second value, indicate that the emergency call number in the terminal side is invalid in the HPLMN and its equivalent PLMN.

[0584] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0585] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling;

[0586] The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

[0587] Optionally, the first additional information element is of TLV-E type or TV type.

[0588] Alternatively, see Fig. 20 It can be seen that the indication system further includes: a message sending module 33, which is used to send a request message to the network side; the request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side;

[0589] The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling;

[0590] The indication identifier is located in the second additional information element in the indication signaling.

[0591] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0592] Optionally, the information element indicator is located at any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located at any spare bit position in the Extended emergency number list IE in the indication signaling;

[0593] See also Fig.21 It can be seen that the indication system further includes: a second response module 34, configured to indicate that the indication signaling does not include the second additional information element in response to the information element indicator in the indication signaling being a third value;

[0594] The second response module 34 is further configured to indicate that the indication signaling includes a second additional information element in response to the information element indicator in the indication signaling being a fourth value;

[0595] Among them, the several indication identifiers contained in the second additional information element are used to indicate whether each emergency call number to be confirmed on the terminal side is valid.

[0596] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0597] In summary, Example 3 achieves refined control of the effectiveness of emergency call numbers through dynamic signaling extension and identifier mechanism, and its main technical effects are as follows:

[0598] 1. Flexible and dynamic emergency number management

[0599] Real-time policy delivery: The network side can indicate the validity status (valid / invalid) of the terminal emergency number in real time through the USIMCFGV bit in standard signaling (such as ATTACH ACCEPT / REGISTRATIONACCEPT), without the need for network-wide broadcasting or terminal pre-storage of complex rules.

[0600] On-demand precise control: Supports independent configuration of single emergency numbers or batches of numbers (such as temporarily disabling the special number 12345 for an active area) to avoid affecting emergency services across the entire network.

[0601] 2. Seamless compatibility across networks and standards

[0602] Adaptation to multiple network architectures: The emergency number validity identifier is uniformly extended in the signaling of network architectures such as 5GS, EPS, GSM / UTTRAN, ensuring the resolution consistency of terminals in different network environments (such as HPLMN / VPLMN, roaming scenarios).

[0603] Signaling multiplexing optimization: Use the spare bits of existing signaling (such as LOCATION UPDURING ACCEPT) or add TLV-E / TV information elements to avoid increasing signaling overhead.

[0604] 3. Efficient fault tolerance of terminal and network collaboration

[0605] Intelligent terminal processing: The terminal automatically determines the validity of the emergency number based on the signaling identifier. If the identifier is invalid or undefined, it will prioritize matching international emergency numbers (such as 110 / 119 / 911) or preset whitelists to ensure basic emergency communication capabilities.

[0606] Network policy conflict resolution: When the signaling does not clearly indicate, the terminal follows the network-side dynamic policy by default (such as USIMCFGV=0) and reports abnormal scenarios through logs to facilitate rapid problem location on the network side.

[0607] 4. Enhanced security and reliability

[0608] Anti-tampering protection: The validity range of the emergency number validity identifier is limited to the period when the USIM is inserted and the terminal is powered on. It is automatically reset after the card is removed or the terminal is powered off to prevent illegal configuration from remaining for a long time.

[0609] Redundancy verification mechanism: The terminal has a built-in whitelist verification. Even if the signaling on the network side fails, the availability of core emergency services can still be guaranteed through the pre-set emergency number library.

[0610] 5. User experience optimization

[0611] Real-time feedback and guidance: When the terminal detects that the emergency number is invalid, it actively prompts the user (such as pop-up window, gray display) to avoid misdialing and guide the user to switch to a valid number or contact network support.

[0612] Reduce network load: By dynamically disabling non-essential emergency numbers (such as numbers dedicated to temporary events), the occupation of network resources by invalid calls is reduced, thus improving the quality of emergency communications.

[0613] As for the system embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The system embodiment described above is only illustrative, in which the units described as separate components may or may not be physically separated, and the components as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution.

[0614] Example 4

[0615] Corresponding to the embodiment of the method for indicating an emergency call number in the aforementioned embodiment 2, the present disclosure also provides an embodiment of a system for indicating an emergency call number.

[0616] Fig. 22 A schematic diagram of a module of an emergency call number indication system provided by an exemplary embodiment of the present disclosure, the system comprising:

[0617] The present disclosure provides an indication system for an emergency call number, the indication system being applied to a network side, and the indication system comprising:

[0618] The signaling sending module 41 is used to send an indication signaling to the terminal side, where the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number on the terminal side is valid.

[0619] Optionally, the indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergency number list IE in the indication signaling;

[0620] or,

[0621] The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

[0622] Optionally, the indication identifier is a first value, which is used to indicate that the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN;

[0623] or,

[0624] The indication identifier takes the second value, which is used to indicate that the emergency call number on the terminal side is invalid in the HPLMN and its equivalent PLMN.

[0625] Optionally, the indication identifier is ignored by the terminal side in the VPLMN.

[0626] Optionally, the indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling;

[0627] The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

[0628] Optionally, the first additional information element is of TLV-E type or TV type.

[0629] Alternatively, see Fig.23 It can be seen that the indication system further includes: a receiving module 42, which is used to receive a request message from the terminal side; the request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side;

[0630] The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling;

[0631] The indication identifier is located in the second additional information element in the indication signaling.

[0632] Optionally, the indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

[0633] Optionally, the information element indicator is located at any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located at any spare bit position in the Extended emergency number list IE in the indication signaling;

[0634] The information element indicator in the indication signaling takes a third value, which is used to indicate that the indication signaling does not include the second additional information element;

[0635] The information element indicator in the indication signaling takes a fourth value, which is used to indicate that the indication signaling includes a second additional information element;

[0636] Among them, the several indication identifiers contained in the second additional information element are used to indicate whether each emergency call number to be confirmed on the terminal side is valid.

[0637] Optionally, the indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

[0638] As for the system embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The system embodiment described above is only illustrative, in which the units described as separate components may or may not be physically separated, and the components as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution.

[0639] In summary, Example 4 achieves refined control of the effectiveness of emergency call numbers through dynamic signaling extension and identifier mechanism, and its main technical effects are as follows:

[0640] 1. Flexible and dynamic emergency number management

[0641] Real-time policy delivery: The network side can indicate the validity status (valid / invalid) of the terminal emergency number in real time through the USIMCFGV bit in standard signaling (such as ATTACH ACCEPT / REGISTRATIONACCEPT), without the need for network-wide broadcasting or terminal pre-storage of complex rules.

[0642] On-demand precise control: Supports independent configuration of single emergency numbers or batches of numbers (such as temporarily disabling the special number 12345 for an active area) to avoid affecting emergency services across the entire network.

[0643] 2. Seamless compatibility across networks and standards

[0644] Adaptation to multiple network architectures: The emergency number validity identifier is uniformly extended in the signaling of network architectures such as 5GS, EPS, GSM / UTTRAN, ensuring the resolution consistency of terminals in different network environments (such as HPLMN / VPLMN, roaming scenarios).

[0645] Signaling multiplexing optimization: Use the spare bits of existing signaling (such as LOCATION UPDURING ACCEPT) or add TLV-E / TV information elements to avoid increasing signaling overhead.

[0646] 3. Efficient fault tolerance of terminal and network collaboration

[0647] Intelligent terminal processing: The terminal automatically determines the validity of the emergency number based on the signaling identifier. If the identifier is invalid or undefined, it will prioritize matching international emergency numbers (such as 110 / 119 / 911) or preset whitelists to ensure basic emergency communication capabilities.

[0648] Network policy conflict resolution: When the signaling does not clearly indicate, the terminal follows the network-side dynamic policy by default (such as USIMCFGV=0) and reports abnormal scenarios through logs to facilitate rapid problem location on the network side.

[0649] 4. Enhanced security and reliability

[0650] Anti-tampering protection: The validity range of the emergency number validity identifier is limited to the period when the USIM is inserted and the terminal is powered on. It is automatically reset after the card is removed or the terminal is powered off to prevent illegal configuration from remaining for a long time.

[0651] Redundancy verification mechanism: The terminal has a built-in whitelist verification. Even if the signaling on the network side fails, the availability of core emergency services can still be guaranteed through the pre-set emergency number library.

[0652] 5. User experience optimization

[0653] Real-time feedback and guidance: When the terminal detects that the emergency number is invalid, it actively prompts the user (such as pop-up window, gray display) to avoid misdialing and guide the user to switch to a valid number or contact network support.

[0654] Reduce network load: By dynamically disabling non-essential emergency numbers (such as numbers dedicated to temporary events), the occupation of network resources by invalid calls is reduced, thus improving the quality of emergency communications.

[0655] Example 5

[0656] Fig.24 This is a structural diagram of an electronic device shown in an example embodiment of the present disclosure, the electronic device includes a memory, a processor, and a computer program stored in the memory and used to run on the processor, and when the processor executes the computer program, the method for indicating the emergency call number of any of the above embodiments is implemented. Fig.24 The electronic device 90 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0657] like Fig.24 As shown, the electronic device 90 may be in the form of a general-purpose computing device, for example, it may be a server device. The components of the electronic device 90 may include, but are not limited to: at least one processor 91, at least one memory 92, and a bus 93 connecting different system components (including the memory 92 and the processor 91).

[0658] The bus 93 includes a data bus, an address bus, and a control bus.

[0659] The memory 92 may include a volatile memory, such as a random access memory (RAM) 921 and / or a cache memory 922 , and may further include a read only memory (ROM) 923 .

[0660] The memory 92 may also include a program tool 925 (or utility) having a set (at least one) of program modules 924, such program modules 924 including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include the implementation of a network environment.

[0661] The processor 91 executes various functional applications and data processing by running the computer program stored in the memory 92, such as the method for indicating the emergency call number provided in any of the above embodiments.

[0662] The electronic device 90 can also communicate with one or more external devices 94 (e.g., keyboards, pointing devices, etc.). This communication can be carried out through an input / output (I / O) interface 95. In addition, the electronic device 90 can also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs) and / or public networks, such as the Internet) through a network adapter 96. As shown in the figure, the network adapter 96 communicates with other modules of the electronic device 90 through a bus 93. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 90, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems, etc.

[0663] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided into multiple units / modules to be embodied.

[0664] Example 6

[0665] The embodiments of the present disclosure further provide a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the method for indicating an emergency call number provided in any of the above embodiments is implemented.

[0666] The readable storage medium may include but is not limited to: a portable disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device or any suitable combination of the above.

[0667] Example 7

[0668] The embodiment of the present disclosure further provides a computer program product, including a computer program, which implements any of the above-mentioned methods for indicating an emergency call number when the computer program is executed by a processor.

[0669] Among them, the program code for executing the computer program product of the present disclosure can be written in any combination of one or more programming languages, and the program code can be executed completely on the terminal side, partially on the terminal side, as an independent software package, partially on the terminal side and partially on a remote device, or completely on the remote device.

[0670] Example 8

[0671] The present disclosure provides a chip, which includes at least one processor, and the processor is used to execute program instructions to perform the indication method of the above-mentioned embodiment 1 or embodiment 2.

[0672] The chip achieves efficient signaling parsing and dynamic policy decision-making through hardware-level optimization. The chip can be integrated into the terminal main control chip (such as SoC), baseband chip or independent security coprocessor, and is compatible with various terminal forms such as smartphones and IoT devices to meet the emergency communication needs of the entire industry.

[0673] Example 9

[0674] The present disclosure provides a chip module, which is applied to electronic equipment, including a transceiver component and a chip. The chip includes at least one processor for executing the indication method of any of the above-mentioned embodiments 1 or 2.

[0675] The chip module achieves efficient signaling parsing and dynamic policy decision-making through hardware-level optimization. The chip module can be integrated into the terminal main control chip (such as SoC), baseband chip or independent security coprocessor, and is compatible with various terminal forms such as smartphones and IoT devices to meet the emergency communication needs of the entire industry.

[0676] Although the specific embodiments of the present disclosure are described above, those skilled in the art should understand that this is only an example, and the protection scope of the present disclosure is defined by the appended claims. Those skilled in the art may make various changes or modifications to these embodiments without departing from the principles and essence of the present disclosure, but these changes and modifications all fall within the protection scope of the present disclosure.

Claims

1. A method for indicating an emergency call number, characterized in that: The indication method is applied to the terminal side, and the indication method includes: The indication signaling from the network side is parsed, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number on the terminal side is valid.

2. The indicating method according to claim 1, characterized in that: The indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergencynumber list IE in the indication signaling; or, The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATEACCEPT signaling and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

3. The indicating method according to claim 2, characterized in that: In response to the indication identifier being a first value, indicating that the emergency call number in the terminal side is valid in the HPLMN and its equivalent PLMN; In response to the indication identifier being the second value, it indicates that the emergency call number in the terminal side is invalid in the HPLMN and its equivalent PLMN.

4. The indicating method according to claim 3, characterized in that: The indication identifier is ignored by the terminal side in the VPLMN.

5. The indicating method according to claim 1, characterized in that: The indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling; The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

6. The indicating method according to claim 5, characterized in that: The first additional information element is of TLV-E type or TV type.

7. The indicating method according to claim 1, characterized in that: The step of parsing the indication signaling from the network side also includes: Sending a request message to the network side; the request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side; The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling; The indication identifier is located in a second additional information element in the indication signaling.

8. The indicating method according to claim 7, characterized in that: The indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

9. The indicating method according to claim 8, characterized in that: The information element indicator is located at any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located at any spare bit position in the Extended emergency number list IE in the indication signaling; In response to the information element indicator in the indication signaling being a third value, indicating that the indication signaling does not include the second additional information element; In response to the information element indicator in the indication signaling being a fourth value, indicating that the indication signaling includes the second additional information element; Among them, the several indication identifiers included in the second additional information element are used to indicate whether each of the emergency call numbers to be confirmed on the terminal side is valid.

10. The indicating method according to any one of claims 1 to 9, characterized in that: The indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

11. A method for indicating an emergency call number, characterized in that: The indication method is applied to the network side, and the indication method includes: An indication signaling is sent to the terminal side, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number in the terminal side is valid.

12. The indicating method according to claim 11, characterized in that: The indication signaling includes any one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling, and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Emergencynumber list IE in the indication signaling; or, The indication signaling includes at least one of the following: ATTACH ACCEPT signaling, TRACKING AREA UPDATEACCEPT signaling and REGISTRATION ACCEPT signaling; the indication identifier is located in any spare bit position in the Extended emergency number list IE in the indication signaling.

13. The indicating method according to claim 12, characterized in that: The indication identifier is a first value, which is used to indicate that the emergency call number on the terminal side is valid in the HPLMN and its equivalent PLMN; or, The indication identifier takes a second value, which is used to indicate that the emergency call number on the terminal side is invalid in the HPLMN and its equivalent PLMN.

14. The indicating method according to claim 13, characterized in that: The indication identifier is ignored by the terminal side in the VPLMN.

15. The indicating method according to claim 11, characterized in that: The indication signaling includes at least one of the following: LOCATION UPDATING ACCEPT signaling, ATTACH ACCEPT signaling, TRACKING AREA UPDATE ACCEPT signaling and REGISTRATION ACCEPT signaling; The indication identifier is located at any spare bit position in the first additional information element in the indication signaling.

16. The indicating method according to claim 15, characterized in that: The first additional information element is of TLV-E type or TV type.

17. The indicating method according to claim 11, characterized in that: Before the step of sending the indication signaling to the terminal side, the step further includes: Receive a request message from the terminal side; the request message includes at least one of the following: REGISTRATION REQUEST and ATTACH REQUEST; the request message includes the emergency call number to be confirmed on the terminal side; The indication signaling corresponds to the request message, and the indication signaling includes at least one of the following: REGISTRATION ACCEPT signaling and ATTACH ACCEPT signaling; The indication identifier is located in a second additional information element in the indication signaling.

18. The indicating method according to claim 17, characterized in that: The indication signaling includes an information element indicator, and the information element indicator is used to indicate whether the indication signaling includes the second additional information element.

19. The indicating method according to claim 18, characterized in that: The information element indicator is located at any spare bit position in the Emergency number list IE in the indication signaling; or, the information element indicator is located at any spare bit position in the Extended emergency number list IE in the indication signaling; The value of the information element indicator in the indication signaling is a third value, which is used to indicate that the indication signaling does not include the second additional information element; or, The value of the information element indicator in the indication signaling is a fourth value, which is used to indicate that the indication signaling includes the second additional information element; Among them, the several indication identifiers included in the second additional information element are used to indicate whether each of the emergency call numbers to be confirmed on the terminal side is valid.

20. The indicating method according to any one of claims 11 to 19, characterized in that: The indication identifier is used to indicate whether the emergency call number configured in the USIM on the terminal side is valid.

21. An emergency call number indication system, characterized in that: The indication system is applied to the terminal side, and the indication system includes: The parsing module is used to parse the indication signaling from the network side, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number on the terminal side is valid.

22. An emergency call number indication system, characterized in that: The indication system is applied to the network side, and the indication system includes: The signaling sending module is used to send an indication signaling to the terminal side, wherein the indication signaling includes an indication identifier; the indication identifier is used to indicate whether the emergency call number in the terminal side is valid.

23. An electronic device comprising a memory, a processor, and a computer program stored in the memory and used to run on the processor, characterized in that: When the processor executes the computer program, the processor implements the indication method described in any one of claims 1 to 10, or implements the indication method described in any one of claims 11 to 20.

24. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed, the instruction method described in any one of claims 1 to 10 is implemented, or the instruction method described in any one of claims 11 to 20 is implemented.

25. A chip, comprising at least one processor, wherein the processor is configured to execute program instructions to execute the indication method according to any one of claims 1 to 10, or to implement the indication method according to any one of claims 11 to 20.

26. A chip module, applied to electronic equipment, characterized in that: It comprises a transceiver component and a chip, wherein the chip comprises at least one processor, and is used to execute the indication method according to any one of claims 1 to 10, or to implement the indication method according to any one of claims 11 to 20.

27. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the indication method according to any one of claims 1 to 10, or the computer program implements the indication method according to any one of claims 11 to 20.

Images