An exception handling method, apparatus, device, medium and product

Abstract

An embodiment of the present application provides an exception handling method, apparatus, device, medium, and product. In the embodiment of the present application, after the SIM card is recognized, the tracking area code provided by the network side is obtained; the authentication request corresponding to the tracking area code provided by the network side is received; if the authentication results of the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, it is determined that the authentication file of the SIM card is abnormal. By excluding the factors that may affect the authentication process one by one, it is finally determined that the authentication file is abnormal. Since there are many contents involved in the two-way authentication process and the problem of abnormal authentication files is relatively hidden, through the above solution, the problem of abnormal authentication files in the SIM card can be accurately determined without the support of professional personnel and professional equipment.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to an exception handling method, apparatus, device, medium, and product. Background Art

[0002] When a SIM card is installed in a user terminal device, it can be used normally only after authentication and registration by the network side. During the authentication and registration process, the SIM card, the user terminal, and the network side need to cooperate with each other. Moreover, a lot of authentication-related information is required during the authentication and registration process. Any link or any piece of information being incorrect will cause the authentication to fail. However, some problems are very hidden (for example, a file in the SIM card is damaged), and it is inevitable that the user terminal cannot determine the cause of the exception, or the user terminal gives the wrong cause of the exception. In order to accurately determine the cause of the exception, professional personnel often need to use professional tools for analysis to accurately determine the cause of the exception, which is a cumbersome process and cannot meet the user's needs. Summary of the Invention

[0003] Multiple aspects of this application provide an exception handling method, apparatus, device, medium, and product to solve the problem that the cause of the authentication and registration exception cannot be accurately determined.

[0004] In a first aspect, an embodiment of this application provides an exception handling method, including:

[0005] After a SIM card is recognized, obtain a tracking area code provided by the network side; receive an authentication request corresponding to the tracking area code provided by the network side; if the authentication results of using the authentication file provided by the SIM card for the authentication requests corresponding to different tracking area codes are all authentication failures, determine that the authentication file of the SIM card is abnormal.

[0006] After the user terminal successfully recognizes the SIM card, it will continue to perform two-way authentication. During the authentication process, the authentication requests received by the user terminal include authentication parameters provided by the network side. After determining the authentication result of authentication failure, an authentication request will be initiated again by changing different tracking area codes. During the multiple authentication initiations, without changing the SIM card, the authentication file provided by the SIM card is fixed.

[0007] The user terminal does not have more permissions to investigate whether the tracking area code and the authentication file are correct. Therefore, it can only determine the cause of the authentication failure by excluding controllable authentication information, that is, by changing the tracking area code participating in the two-way authentication link in the authentication and registration and keeping the authentication file unchanged. Thus, the problem of abnormal authentication files in the SIM card can be accurately determined without the support of professional personnel and professional equipment.

[0008] Optionally, receiving the authentication request corresponding to the tracking area code provided by the network side includes: receiving a first authentication request corresponding to a first tracking area code provided by the network side; after receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes: after determining an authentication failure result corresponding to the first authentication request, obtaining a second tracking area code provided by the network side; receiving a second authentication request corresponding to the second tracking area code provided by the network side; and authenticating the second authentication request using the authentication file provided by the SIM card. During the authentication process, if the first authentication request fails authentication, the user needs to move the user terminal to another tracking area to obtain the second tracking area code. After the user terminal sends a registration request to the network side, the network side responds to the registration request, and then the network side sends a second authentication request corresponding to the second tracking area code to the user terminal. By changing different tracking area codes, the interference of the tracking area code on the authentication result is excluded. That is to say, if the authentication is successful after changing the tracking area code, it means that the tracking area code used in the previous authentication process may have problems. If the authentication still fails after changing the tracking area code, it means that the authentication failure has nothing to do with the tracking area code. Because the probability of multiple consecutive tracking area codes having problems is extremely low.

[0009] Optionally, receiving the first authentication request corresponding to the first tracking area code provided by the network side includes: receiving the first authentication request corresponding to the first tracking area code provided by the network side; counting the number of times the first authentication request is received; when the number of receptions is greater than the retry times threshold corresponding to the first tracking area code, terminating the reception of the first authentication request; and recording an authentication failure result corresponding to the first authentication request. During the process of performing the authentication task using the first authentication request, it is inevitable that the network is temporarily unstable. Therefore, the same authentication request can be used to repeatedly attempt authentication multiple times. If the authentication results of multiple attempts are still authentication failures, the influence of network instability can be excluded.

[0010] Optionally, if the authentication results of authenticating the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, determining that the authentication file of the SIM card is abnormal includes: counting the number of area codes of the different tracking area codes whose authentication results are authentication failures; if the number of area codes is greater than or equal to the area code number threshold, determining that the authentication file of the SIM card is abnormal. When changing the tracking area code, the area code number threshold of the tracking area code can be set. Only when the replacement meets a certain threshold condition is it considered to confirm the exclusion of the adverse impact of the tracking area code on the authentication failure result, and then the investigation of other possible interference factors can be carried out, such as investigating factors such as the cell and the authentication file.

[0011] Optionally, if the authentication results of the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, determining that the authentication file of the SIM card is abnormal includes: starting a first authentication timer; counting the number of area codes of the different tracking area codes for which the authentication result is an authentication failure; if the timing duration is within the time limit of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, determining that the authentication file of the SIM card is abnormal; if the timing duration reaches the time limit of the first authentication timer and the number of area codes is less than the code number threshold, clearing the first authentication timer. Before successful authentication, the user terminal cannot establish a connection with the network, which means that during this period, the user cannot normally use the user terminal or interact with the network for data. Therefore, in order to shorten the authentication process, when analyzing whether the authentication file is abnormal, a first authentication timer can be set for the analysis process. If the first authentication timer is exceeded, all authentication attempts can be terminated, and the user can be directly notified to find a professional to help solve the problem, or other methods can be used to further assist in determining the reason for the authentication failure (for example, analyzing the reason for the authentication failure by changing the cell).

[0012] Optionally, receiving the authentication request corresponding to the tracking area code provided by the network side includes: receiving a first authentication request corresponding to a first tracking area code provided by the network side; after receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes: after determining an authentication failure result corresponding to the first authentication request, if it fails to obtain a second tracking area code provided by the network side, obtaining a plurality of cell identifiers corresponding to the first tracking area code; receiving the first authentication request provided by the cell base station corresponding to the plurality of cell identifiers; authenticating the first authentication request provided by the cell base station corresponding to the plurality of cell identifiers using the authentication file provided by the SIM card. In practical applications, if the tracking area code needs to be changed, usually the user needs to move the user terminal from one tracking area to another. If the user's moving space is limited (only moving within the same or two tracking area ranges), more tracking area codes cannot be obtained. Therefore, the method of changing the cell can be used to exclude the influence of network side anomalies (such as network instability, base station anomalies) on the authentication process. After excluding network side anomalies, it can be further analyzed to determine whether the authentication file is abnormal.

[0013] Optionally, if the authentication results of authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, it includes: starting a first authentication timer; counting the number of area codes of the different tracking area codes for which the authentication result is an authentication failure; if the timing duration is within the time limit of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, determining that the authentication file of the SIM card is abnormal; if the timing duration reaches the time limit of the first authentication timer and the number of area codes is less than the code number threshold, clearing the first authentication timer and starting a second authentication timer; counting the number of identifiers of multiple cell identifiers for which the authentication result is an authentication failure; if the timing duration is within the time limit of the second authentication timer and the number of identifiers is greater than the identifier number threshold, determining that the authentication file of the SIM card is abnormal; if the timing duration reaches the time limit of the second authentication timer and the number of identifiers is less than the identifier number threshold, clearing the second authentication timer. Before successful authentication, the user terminal cannot establish a connection with the network, which means that during this period, the user cannot normally use the user terminal and cannot interact with the network for data. Therefore, in order to shorten the authentication process, when analyzing whether the authentication file is abnormal, a first authentication timer and a second authentication timer can be set for the analysis process. When the first authentication timer is exceeded, the second authentication timer is started. When the time limit of the second authentication timer is exceeded, various authentication attempts are terminated, and the user can be directly notified to find a professional to help solve the problem, or other methods can be used to further assist in determining the cause of the authentication failure (for example, analyzing the cause of the authentication failure by changing the cell).

[0014] Optionally, after determining that the authentication file of the SIM card is abnormal, it further includes: outputting a prompt message for guiding the user to replace the SIM card. This prompt message is the operation content for guiding the user to solve the SIM card authentication anomaly subsequently, rather than just prompting the user that the SIM card authentication file is damaged. Such a prompt message enables the user to more simply and clearly understand how to operate to eliminate this anomaly problem.

[0015] In a second aspect, an embodiment of the present application further provides an anomaly handling device, including:

[0016] An acquisition module, configured to acquire a tracking area code provided by a network side after identifying the SIM card.

[0017] A receiving module, configured to receive an authentication request corresponding to the tracking area code provided by the network side.

[0018] A determination module, configured to determine that the authentication file of the SIM card is abnormal if the authentication results of authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures.

[0019] Optionally, a receiving module, configured to receive a first authentication request corresponding to a first tracking area code provided by the network side;

[0020] After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes:

[0021] After determining an authentication result of authentication failure corresponding to the first authentication request, obtain a second tracking area code provided by the network side;

[0022] Receive a second authentication request corresponding to the second tracking area code provided by the network side;

[0023] Authenticate the second authentication request by using an authentication file provided by the SIM card.

[0024] Optionally, the receiving module is further configured to receive a first authentication request corresponding to the first tracking area code provided by the network side;

[0025] Count the number of times of receiving the first authentication request;

[0026] When the number of times of receiving is greater than a retry times threshold corresponding to the first tracking area code, terminate receiving the first authentication request;

[0027] Record an authentication result of authentication failure corresponding to the first authentication request.

[0028] Optionally, a determining module, configured to count the number of area codes of different tracking area codes whose authentication result is authentication failure;

[0029] If the number of area codes is greater than or equal to a code number threshold, determine that the authentication file of the SIM card is abnormal.

[0030] Optionally, the determining module is configured to start a first authentication timer;

[0031] Count the number of area codes of different tracking area codes whose authentication result is authentication failure;

[0032] If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, determine that the authentication file of the SIM card is abnormal;

[0033] If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer.

[0034] Optionally, the receiving module is configured to receive an authentication request corresponding to the tracking area code provided by the network side;

[0035] After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes:

[0036] After determining the authentication result of authentication failure corresponding to the first authentication request, if it fails to obtain the second tracking area code provided by the network side, then obtain a plurality of cell identifiers corresponding to the first tracking area code;

[0037] Receive the first authentication request provided by the cell base stations corresponding to the plurality of cell identifiers;

[0038] Authenticate the first authentication request provided by the cell base stations corresponding to the plurality of cell identifiers by using the authentication file provided by the SIM card.

[0039] Optionally, a determination module is used to start a first authentication timer;

[0040] Count the number of area codes of different tracking area codes whose authentication result is authentication failure;

[0041] If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, determine that the authentication file of the SIM card is abnormal;

[0042] If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer and start a second authentication timer;

[0043] Count the number of identifiers of a plurality of cell identifiers whose authentication result is authentication failure;

[0044] If the timing duration is within the time limit range of the second authentication timer and the number of identifiers is greater than the identifier number threshold, determine that the authentication file of the SIM card is abnormal;

[0045] If the timing duration reaches the time limit range of the second authentication timer and the number of identifiers is less than the identifier number threshold, clear the second authentication timer.

[0046] Optionally, it further includes an output module for outputting a prompt message for guiding the user to replace the SIM card.

[0047] In a third aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory. The memory is used to store computer-executable program code, and the program code includes instructions; when the processor executes the instructions, the instructions cause the electronic device to execute the method in the first aspect.

[0048] Fourthly, an embodiment of the present application provides a computer program product containing instructions. When it runs on a computer, it causes the computer to execute the method in the first aspect above.

[0049] Fifthly, an embodiment of the present application provides a computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When it runs on a computer, it causes the computer to execute the method in the first aspect above.

[0050] In some embodiments of the present application, after the user terminal successfully recognizes the SIM card and does not find any abnormality with the SIM card, it will continue to execute the authentication registration task. After receiving the registration request from the user terminal, the network side, as a response, will send an authentication request generated based on the tracking area code to the user terminal. After the user terminal authenticates the authentication request using the authentication file and obtains an authentication failure result, it will change to a different tracking area code. By eliminating the factors that may affect the authentication process one by one, it is finally determined that the authentication file is abnormal. Since there are many contents involved in the two-way authentication process and the problem of abnormal authentication files is relatively hidden, through the above solution, it is possible to accurately determine the abnormality of the authentication file in the SIM card without the support of professional personnel and professional equipment, improving the work efficiency of determining the abnormal authentication file. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The schematic embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0052] Figure 1 is a schematic structural diagram of a communication system provided by an exemplary embodiment of the present application;

[0053] Figure 2 is a schematic flowchart of an exception handling method provided by an exemplary embodiment of the present application;

[0054] Figure 3a is a schematic flowchart of a two-way authentication method provided by an exemplary embodiment of the present application;

[0055] Figure 3b is a schematic flowchart of a repeated authentication method provided by an exemplary embodiment of the present application;

[0056] Figure 4 is a schematic diagram of the process of changing the tracking area code provided by an exemplary embodiment of the present application;

[0057] Figure 5a is a schematic flowchart of another two-way authentication method provided by an exemplary embodiment of the present application;

[0058] Figure 5b Schematic flowchart of another repeated authentication method provided by an exemplary embodiment of the present application;

[0059] Figure 6 Schematic diagram of the process of replacing the authentication cell provided by an exemplary embodiment of the present application;

[0060] Figure 7 Schematic diagram of the structure of an exception handling device provided by an exemplary embodiment of the present application;

[0061] Figure 8 Schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. Detailed implementation manners

[0062] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part rather than all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of the present application.

[0063] The Tracking Area Code (TAC) is an identification code in a mobile communication network, used to identify and manage a Tracking Area. In a mobile communication network, a tracking area is an area composed of multiple base stations and usually contains multiple cells. The tracking area manages a group of adjacent cells, enabling seamless handover of mobile devices within the tracking area. Among them, the TAC consists of two parts: the Mobile Country Code (MCC) and the Mobile Network Code (MNC). The MCC is used to identify a country or region and is a unique numerical code. The MNC is used to identify a specific mobile network operator and is also a numerical code. The combination of the MCC and the MNC constitutes a unique tracking area code. The role of the tracking area code in a mobile communication network is to uniquely identify a tracking area so that each component in the network can identify and manage this area. When a terminal device connects to a mobile communication network, it uses the TAC to identify the tracking area it is in and communicates through the base stations in the network. At the same time, the tracking area code is also used for important authentication information in two-way authentication registration. During authentication registration, it is necessary to ensure the successful authentication registration of the new SIM card before establishing an effective network connection with the network side.

[0064] A cell refers to a specific geographical area covered by a wireless base station. Each cell has a unique identifier, called the Cell ID. A tracking area may contain multiple cells at the same time. In other words, multiple cells correspond to the same Tracking Area Code (TAC). A wireless base station is a device in a mobile communication network that provides communication with terminal devices (such as mobile phones) through radio signals. Each base station is responsible for covering a certain range of cells to provide wireless communication services. Therefore, when performing the SIM card authentication and registration task, it is necessary to ensure that the base station of the cell is normal. If the base station of the cell is abnormal, it may also cause the registration to fail. Each cell has a unique cell identifier, which can be identified by the Cell ID. The Cell ID is a unique code used to distinguish different cells in the entire mobile communication network. The range and coverage area of a cell can be adjusted as needed. In urban areas, due to the high population density and high communication demand, cells are usually smaller and have a smaller coverage area. In rural or suburban areas with a sparse population, the range of cells may be larger and the coverage area will also increase accordingly.

[0065] The user terminal can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. For example, the terminal device can be a mobile phone, smart TV, wearable device, tablet (Pad), computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, and so on. The embodiments of this application do not limit the specific technologies and specific device forms adopted by the terminal device.

[0066] The Subscriber Identity Module (SIM) is a pluggable smart card, commonly referred to as the SIM card, which is used to store and manage user identity recognition and authentication information in communication devices. SIM cards are typically used in mobile phones, smartphones, tablets, and other devices connected to cellular networks. The SIM card stores information related to the user's identity, including the International Mobile Subscriber Identity (IMSI), authentication keys (such as Ki), personal identity information, etc. The IMSI in the SIM card is a unique identifier used to identify and locate the user's identity in the mobile network.

[0067] After inserting a new SIM card into the card slot of the user terminal, the user terminal device first identifies the SIM card using specific communication protocols. These communication protocols define the data exchange methods and specifications between the user terminal device and the SIM card. Specifically, the user terminal device sends instructions to the SIM card to identify the type and functions of the SIM card. The user terminal reads the identification information in the SIM card, such as the IMSI (International Mobile Subscriber Identity), ICCID (Integrated Circuit Card Identification), etc. During the authentication process, the network uses the authentication key in the SIM card to verify with the authentication center to ensure the security and legality of the communication between the device and the network. The SIM card can also store some user-personalized data, such as the contact list, text messages, applications, etc. In addition, the SIM card can support mobile payment, identity authentication, data storage, and other additional functions, depending on the specific SIM card type and the functions supported by the operator. All in all, the SIM card is a smart card used to store user identity recognition and authentication information, and it is a key component for mobile communication devices to connect to the mobile network and perform two-way authentication. Only after successful two-way authentication can the user terminal establish a network connection using the SIM card.

[0068] During the two-way authentication process, the user terminal initiates a registration request, and in response, the network sends an authentication request corresponding to the tracking area code and other related authentication information. If the authentication file in the SIM card is damaged, the authentication registration will fail. However, this fault is relatively hidden. When the user device can read the SIM card normally, it is usually unable to directly detect whether the authentication file in the SIM card is damaged, nor can it distinguish whether it is a user terminal fault or a network fault. In the prior art, if you want to check whether the authentication file in the SIM card is damaged, you need to use professional equipment and professionals to detect whether the authentication file of the SIM card is damaged. In other words, during the conventional authentication registration process, it is impossible to detect whether the authentication file is damaged. In two-way authentication, the TAC provided by the network and the authentication file of the SIM card are used at the same time, making it difficult to distinguish which end is at fault. Therefore, the embodiment of the present application provides a solution, and the basic idea is:

[0069] After inserting the SIM card into the card slot of the user terminal, the user terminal will identify and read the SIM card information. If the user terminal cannot identify or the reading fails, it means that there is a fault in the SIM card or the user terminal. Usually, a pop-up window will pop up on the user terminal to remind the user to reinsert the SIM card or restart the user terminal. If the user terminal can successfully identify and read the SIM card information, the user terminal will further initiate a registration request. Specifically, during the authentication process, the network end, the user terminal and the SIM card are required to provide relevant information to participate in the authentication. Therefore, during the authentication registration process, the user terminal first initiates a registration request to the network end of the tracking area corresponding to the tracking area code, and the network end sends an authentication request containing authentication parameters (that is, one tracking area code corresponds to one authentication request, and when the tracking area code changes, the authentication request also changes). If the tracking area code is abnormal or the authentication file is abnormal, it will cause authentication failure. Furthermore, the tracking area code can be changed to initiate authentication requests multiple times. If the authentication result after changing the tracking area code is still authentication failure, the problem of abnormal tracking area code can be ruled out, and it can be determined that the authentication registration failure is caused by abnormal authentication file of SIM card. Therefore, by disassembling the authentication registration process, the key information (such as tracking area code) in the relevant steps of authentication registration is replaced, so as to eliminate the factors that may cause the same abnormality, and then accurately lock the abnormal SIM card authorization file problem that is difficult to troubleshoot.

[0070] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0071] Figure 1 The structure diagram of the communication system provided by an exemplary embodiment of the present application is shown in FIG. Figure 1As shown in the figure, the system 100 includes: a user terminal 101, a SIM card 102, and a network terminal 103. In the network terminal 103, there is an authentication center 103a and a base station 103b of the cell.

[0072] Among them, the SIM card 102 is inserted into the card slot of the user terminal 101. The user terminal 101 can identify and read the information in the SIM card 102. The user terminal 101 communicates with the SIM card 102 through the SIM card slot, using a specific communication protocol (such as the ISO 7816 protocol). These protocols define the data exchange methods and specifications between the device and the SIM card. Identifying and reading SIM card information: The device sends instructions to the SIM card to identify the type and function of the SIM card. The device will read the identification information in the SIM card, such as IMSI (International Mobile Subscriber Identification Number), ICCID (Integrated Circuit Card Identification Number), etc. After the user terminal successfully identifies and reads it, it will establish a connection relationship with the network terminal 103. Specifically,

[0073] A tracking area contains multiple cells, and each cell has its own base station. Generally, during the connection establishment process, the user terminal establishes a connection relationship with the nearest available base station. The base station of the cell determines the tracking area to which the terminal device belongs by parsing the TAC information in the connection request, and receives an authentication request sent by the authentication center. The authentication request contains authentication parameters (including encrypted authentication information encrypted using an encryption algorithm agreed upon with the user terminal, authentication information, etc.).

[0074] After receiving the registration request from the user terminal, the authentication center verifies the legality of the SIM card by comparing it with the SIM card identity information stored in the local database. Then, the authentication center generates an authentication request containing authentication parameters based on the obtained authentication key and other parameters related to the user terminal, and sends the authentication request to the user terminal. The user terminal uses the authentication file to check whether the authentication request is verified. If the result obtained by encrypting the authentication information using the encryption algorithm in the authentication file is consistent with the encrypted authentication information in the authentication parameters carried in the authentication request, it means that the authentication is passed; otherwise, it means that the authentication fails. The information in these authentication files usually includes IMSI, authentication key (Ki) for encrypting the authentication information, etc. The user terminal determines whether it has successfully established a connection with the network based on the authentication result. If the authentication is successful, the user terminal can normally access the network and use various services. If the authentication fails, the user terminal may be prohibited from accessing the network or can only access limited services.

[0075] It should be noted that there is no restriction on the type of SIM card supported by the user terminal here. In addition, the user terminal device can be a dual-SIM dual-standby device, and the process for handling abnormal authentication files is the same as that for non-dual-SIM dual-standby devices.

[0076] The following will illustrate the process of troubleshooting abnormal authentication files of the SIM card during the two-way authentication process through specific embodiments.

[0077] Figure 2 It is a schematic flowchart of an exception handling method provided by an exemplary embodiment of this application. The execution subject of this method can be a user terminal. As Figure 2 shown, this method specifically includes the following steps:

[0078] Step 201: After identifying the SIM card, obtain the tracking area code provided by the network side.

[0079] Step 202: Receive the authentication request corresponding to the tracking area code provided by the network side.

[0080] Step 203: If the authentication results of using the authentication files provided by the SIM card for the authentication requests corresponding to different tracking area codes are all authentication failures, it is determined that the authentication files of the SIM card are abnormal.

[0081] After the user terminal inserts the SIM card, it will further identify and read the information in the SIM card, including: IMSI (International Mobile Subscriber Identity), ICCID (Integrated Circuit Card Identity), authentication key ki, etc. During the identification and reading process of the user terminal, it will judge whether the SIM card is normal according to the identification and reading results. If it can be successfully identified and read, it is considered that the SIM card has no abnormality. If it cannot be identified or read, at this time, the user terminal has not established a connection relationship with the network side, and the problem troubleshooting process and the determination of the abnormal cause are relatively simple. Generally, it is considered that the SIM card is abnormal, or the user terminal is abnormal. Prompt the user to further troubleshoot, and the user can be prompted to perform relevant operations to solve the abnormality, such as re-plugging the SIM card, changing the card slot, and restarting the user terminal.

[0082] After the user terminal successfully identifies the SIM card, it further executes the relevant steps of two-way authentication. The user terminal will attempt to connect to the mobile communication network. During the connection process, the user terminal will listen to the system information broadcast sent by the base station of the cell. The system information broadcast contains the relevant parameters and information of the mobile communication network, including the tracking area code (TAC) and the cell identification code (CELL ID), etc.

[0083] After receiving the system information broadcast, the user terminal extracts the tracking area code (TAC) from it and uses it for subsequent authentication and registration processes. The user terminal uses the TAC as the unique identifier of the tracking area to establish a correct connection and communication with the mobile communication network. It should be noted that during the connection process, the user terminal may switch between different tracking areas to ensure seamless connection to the network end during the movement of the mobile device. When switching to a new tracking area, the user terminal obtains the TAC of the new tracking area through the new system information broadcast. It should be noted that if the SIM card has successfully completed authentication and registration, there is no need to re-authenticate and register in the new tracking area when switching to the new tracking area. If the SIM card has not completed authentication and registration, it is still necessary to attempt authentication and registration when switching to the new tracking area.

[0084] In practical applications, if the user moves the user terminal from one tracking area to another, resulting in a change in the TAC, but since the SIM card has not been replaced, the authentication file has not changed. Furthermore, authentication is performed for different authentication requests using different TACs and the unchanged authentication file.

[0085] In the case where different tracking area codes are changed and the authentication file of the SIM card remains unchanged, if multiple attempts to authenticate and register fail, it is considered that the problem is not with the tracking area code but with the unchanged authentication file. Therefore, a prompt message can be output on the display interface of the user terminal to prompt the user to replace the SIM card.

[0086] If the authentication is successful after changing the tracking area code, generating a new authentication request, and continuing to perform the authentication and registration task, it can be confirmed that the previous tracking area code was abnormal, and there is no need for the user to replace the SIM card or the user terminal.

[0087] The user terminal does not have the authority to investigate whether the tracking area code and the authentication file are correct. Therefore, the only way to determine the cause of the authentication failure is to exclude the controllable authentication information, that is, by changing the tracking area code involved in the two-way authentication link during authentication and registration while keeping the authentication file unchanged. Thus, the problem of abnormal authentication files in the SIM card can be accurately determined without the support of professional personnel and professional equipment.

[0088] Such as Figure 3a This is a schematic flow diagram of the two-way authentication method provided by an exemplary embodiment of the present application. As can be seen from FIG. 3, receiving the authentication request corresponding to the tracking area code provided by the network end includes: Step 301: Receiving the first authentication request corresponding to the first tracking area code provided by the network end.

[0089] After receiving the authentication request corresponding to the tracking area code provided by the network side, the following steps are further included: Step 302: After determining the authentication result of authentication failure corresponding to the first authentication request, obtain a second tracking area code provided by the network side. Step 303: Receive a second authentication request corresponding to the second tracking area code provided by the network side. Step 304: Authenticate the second authentication request by using the authentication file provided by the SIM card.

[0090] After the network side receives a registration request, the network side sends an authentication request to the user terminal. When the user terminal executes the authentication task, if the authentication file or the tracking area code in the SIM card is damaged or missing, it may cause the authentication to fail, that is, it is impossible to determine whether the current SIM card is legal. Therefore, the user terminal records the result of authentication failure. It may also be due to various reasons such as network congestion, authentication center congestion, or unstable base station signal, resulting in the authentication failing, that is, it is impossible to determine whether the SIM card corresponding to the current authentication request is legal. Therefore, the user terminal records the result of authentication failure. On the user terminal side, only the authentication result of authentication failure is known, but the reason for failure is unknown. Therefore, further investigation is needed. One possibility is that due to the current network congestion, the method of repeatedly attempting authentication can be adopted. Specifically,

[0091] The authentication requests with the same tracking area code can be used to repeatedly attempt authentication. Figure 3b It is a schematic flowchart of the repeated authentication method provided by an exemplary embodiment of the present application. Specifically, as described in step 301, receiving the first authentication request corresponding to the first tracking area code provided by the network side includes:

[0092] Step 301a: Receive the first authentication request corresponding to the first tracking area code provided by the network side.

[0093] Step 301b: Count the number of times the first authentication request is received.

[0094] Step 301c: When the number of receptions is greater than the retry times threshold corresponding to the first tracking area code, terminate receiving the first authentication request.

[0095] Step 301d: Record the authentication result of authentication failure corresponding to the first authentication request.

[0096] When the user terminal receives the first authentication request provided by the network side, it will count the number of times the first authentication request is received. The reason why the network side repeats the first authentication request is to avoid the problem of authentication failure due to temporary unstable data transmission in the network. After multiple attempts (for example, when the number of times the first authentication request is received is greater than the retry count threshold), if the authentication result of authentication failure is still obtained, the influence of temporary network instability on the authentication result can be excluded. Then, the authentication result of the first authentication request failing authentication will be recorded, and subsequently, other methods can be used to continue to attempt authentication. For example, methods such as changing the tracking area code or changing the cell will be described in detail in subsequent embodiments and will not be repeated here.

[0097] For example, the retry count threshold here is 5 times. Without changing the tracking area code, if the user terminal continuously receives the first authentication request provided by the network side and determines that the authentication result based on the authentication request is successful before the repeated reception count reaches 5 times (for example, at the 3rd retry or the 4th retry), then the SIM card and the user terminal successfully establish a connection with the network, clear the statistical data of the transmission count, and display authentication registration success prompt information such as "Welcome to use XX communication service" on the display interface of the user terminal. From the fact that authentication success is obtained after multiple repeated attempts, it can be known that both the authentication file and the tracking area code are okay, and the previous multiple failures may be due to problems such as network congestion.

[0098] If it is determined that the authentication result based on the authentication request is authentication failure after the repeated transmission count reaches the 5th time, then because the retry count threshold has been reached, the user terminal will no longer receive the first authentication request (or the network side counts the transmission count and stops sending when the transmission count reaches the retry count threshold). Record the authentication result of the first authentication request failing authentication. After the above multiple attempts, the adverse influence of factors such as temporary network instability on the authentication result can be excluded, but the root cause of the authentication failure cannot be confirmed currently, and the user terminal still needs to use other methods to further analyze and find the reason for the authentication failure.

[0099] In the case where it has been determined that the first authentication request fails authentication, if the user moves the user terminal in space, that is, moves from the first tracking area to the second tracking area, correspondingly, the tracking area code will also change. The user terminal receives the base station broadcast information of the second tracking area and obtains the second tracking area code carried in the broadcast information.

[0100] The network side generates a second authentication request corresponding to the second tracking area code, but does not change the authentication file, and will execute the authentication registration task after receiving the second authentication request corresponding to the second tracking area code. When using the second authentication request to execute the authentication registration task, specifically, it can use, for example Figure 3aand Figure 3b Perform the authentication task in the manner described above. That is, the second authentication request can be received multiple times within the retry count threshold until the authentication is successful; if the authentication is not successful after exceeding the retry count threshold, a third authentication request can be generated and authenticated again, and so on, repeating the attempt.

[0101] It should be noted that when generating the second authentication request, only the tracking area code is changed, and the authentication file is not changed. Because during the process of the user moving with the user terminal, although the user undergoes a spatial transformation relative to the tracking area, the SIM card has not been replaced, which can rule out the adverse effects of abnormal first tracking area codes and abnormal networks and base stations in the tracking area corresponding to the first tracking area code on the authentication result.

[0102] In one or more embodiments of the present application, if the authentication request results after changing different tracking area codes are all authentication failures, determining that the authentication file of the SIM card is abnormal includes:

[0103] Count the number of area codes of the different tracking area codes for which the authentication result is an authentication failure;

[0104] If the number of area codes is greater than or equal to the code number threshold, determine that the authentication file of the SIM card is abnormal.

[0105] As described above, after an authentication request is recorded as an authentication failure, another authentication request with a different tracking area code is changed. In order to be able to lock the cause of the abnormality faster, a code number threshold can be set, that is, the number of times of allowing the change of the tracking area code is set. If the authentication results of changing the tracking area code multiple times and generating different authentication requests multiple times are all authentication failures, the adverse effects of various factors of each tracking area code and the network side on the authentication result can be ruled out. In other words, it is not an abnormal tracking area code or network side abnormality that causes the authentication failure, but an abnormality of another important piece of information in the authentication request: the authentication file that causes the authentication failure. Through the above multi-step analysis and troubleshooting, it can be finally determined that the authentication failure is caused by an abnormal authentication file, and without the need for professional equipment, professional personnel, and specific technical support from the network side, the special abnormality can be accurately locked without in-depth analysis of the authentication file.

[0106] For example, assume that the code quantity threshold is 5 (in actual applications, to ensure the accuracy of the abnormal analysis result, the code quantity threshold is at least 2, because it is difficult to determine whether it is a tracking area code problem or an authorization file problem only through one tracking area code). When the user terminal receives an authentication request corresponding to a certain tracking area code and is finally recorded as an authentication failure, the user terminal will receive the tracking area codes provided by other tracking areas. If the quantity of the area codes of the successively obtained tracking area codes does not reach 5 (for example, at the 3rd or 4th), and the authentication result of a certain authentication request is authentication success, then the SIM card and the user terminal successfully establish a connection with the network, clear the statistical data of the transmission times, and display a prompt message of successful authentication registration such as "Welcome to use a certain communication service" on the display interface of the user terminal. Then, through multiple replacements of the tracking area code and obtaining successful authentication, it can be known that the authentication file is okay, and the previous multiple failures may be caused by problems such as the tracking area code or the tracking area network.

[0107] If the quantity of the area codes of the successively replaced tracking area codes reaches the 5th and the authentication result of the user terminal is authentication failure, then because the reached code quantity threshold, the user terminal will no longer receive other authentication requests, record the authentication results of multiple authentication requests with authentication failures. After the above multiple attempts, the adverse effects of factors such as abnormal tracking area codes and abnormal tracking area networks on the authentication result can be excluded. After all possible factors are excluded one by one, only the authentication file has not been replaced. Therefore, it can be relatively accurately determined that the abnormal authentication file is the reason for the authentication failure.

[0108] It should be noted here that in the case of successful authentication, even if the user moves spatially with the user terminal from one tracking area to another, when the SIM card is successfully authenticated and considered a legitimate user terminal, there is no need to perform repeated authentication registration, but directly establish a connection relationship with the base station in another tracking area.

[0109] Such as Figure 4 is a schematic diagram of the process of replacing the tracking area code provided by an exemplary embodiment of the present application. From Figure 4As can be seen, insert the SIM card into the card slot of the user terminal and turn on the power of the user terminal. During the startup process of the user terminal, read the SIM card information. If the reading fails, display "Please re-insert the SIM card" on the display interface of the user terminal. In the case of successfully reading the SIM information, the user terminal will quickly perform two-way authentication registration with the base station currently connected, including receiving the first tracking area code broadcast by the base station, the user terminal reads the authentication file in the SIM card, and then sends a registration request to the network side. After receiving the registration request, the network side will send an authentication request corresponding to the first tracking area code to the user terminal for authentication. It is easy to understand that the two-way authentication process will not be shown to the user through the display interface, and only the authentication result (authentication success, authentication failure) and information that needs to guide the user to perform subsequent operations will be shown to the user.

[0110] The specific connection establishment process is as follows: Establish a connection relationship between the user terminal and the base station of the first cell in the first tracking area. If the authentication fails after multiple attempts, record the authentication result with the first tracking area as failed, and do not immediately display the relevant prompt information of authentication failure on the user's display interface, but wait to try to establish a connection relationship with other tracking areas again and perform authentication-related tasks later.

[0111] As Figure 4 shown, after the user moves with the user terminal to another tracking area, receive the second tracking area code broadcast by the adjacent base station. Furthermore, the user terminal receives the second authentication request corresponding to the second tracking area code. Here, assume the code quantity threshold is 2. Then, after the network side provides the second authentication request and gets the authentication result of authentication failure, it can be known that various influencing factors on the network side (such as tracking area network, base station, tracking area code, etc.) have been excluded from the adverse effects on the abnormal authentication result. Therefore, it can be determined by the exclusion method that the authentication file is abnormal, resulting in authentication failure. Then, output a prompt message for guiding the user to replace the SIM card on the display interface of the user terminal. It should be noted that the abnormal authentication file can be various abnormal reasons such as the authentication file being damaged or lost. For example, the authentication key ki is lost.

[0112] After the user obtains a new SIM card from the network operator, remove the SIM card determined to have an abnormal authentication file from the card slot, insert the new SIM card, and successfully authenticate and establish a connection with the network.

[0113] It should be noted that when the user moves spatially, moving from one tracking area to another can achieve the replacement of the tracking area code. Of course, with the support of the network side or under specific conditions (such as in a laboratory), the virtual tracking area code can also be replaced.

[0114] In one or more embodiments of the present application, if the authentication request results after replacing different tracking area codes are all authentication failures, it is determined that the authentication file of the SIM card is abnormal, including:

[0115] Start the first authentication timer;

[0116] Count the number of area codes of the different tracking area codes for which the authentication result is an authentication failure;

[0117] If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal;

[0118] If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer.

[0119] In practical applications, when a user uses a user terminal, the user has no permission or ability to modify the tracking area code. If the tracking area code needs to be replaced, the user needs to actually move the user terminal in space. The tracking area usually ranges from several square kilometers to several hundred square kilometers. For example, the first tracking area is County A, and the second tracking area is County B. If the tracking area code needs to be replaced, the user needs to move from County A to County B. In some cases, for example, when the user is at work, it is difficult to achieve a long-distance and large-scale spatial movement in a short time, which means that the tracking area code cannot be continuously replaced. At this time, other methods need to be adopted to determine whether the authentication file is abnormal, which will be described in detail in subsequent embodiments and will not be repeated here.

[0120] To solve any abnormal problems, the user's usage experience needs to be considered. Therefore, when troubleshooting abnormalities, it is impossible to troubleshoot without a time limit. Since the SIM card authentication registration is unsuccessful, it means that the user terminal cannot connect to the network and the user cannot use the user terminal. The user can accept not being able to use the network for a period of time. Therefore, a first authentication timer can be set for the authentication process.

[0121] When inserting the SIM card into the card slot and starting the authentication, the first authentication timer is started, and at the same time, the retry count and the number of area codes are counted. If the authentication task is completed within the time limit range of the first authentication timer, in one case, when the timing duration is less than the first authentication timer and the number of area codes is less than the code number threshold, and the user terminal receives an authentication success authentication result, the first timer is cleared. In another case, when the timing duration is less than the first authentication timer and the number of area codes is greater than or equal to the code number threshold, and the user terminal receives an authentication failure authentication result, a feedback message of authentication failure is output on the display interface of the user terminal, and the first timer is cleared.

[0122] If the timing duration exceeds the time limit range of the first authentication timer, but the number of the area codes is less than the code number threshold, the first authentication timer is cleared, and subsequent supplementary authentication steps are executed.

[0123] Such as Figure 5a FIG. is a schematic flow chart of another two-way authentication method provided by an exemplary embodiment of the present application. As can be seen from Figure 5b it, receiving the authentication request corresponding to the tracking area code provided by the network side includes:

[0124] Step 501: Receive a first authentication request corresponding to a first tracking area code provided by the network side.

[0125] After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes:

[0126] Step 502: After determining an authentication result of authentication failure corresponding to the first authentication request, if it fails to obtain a second tracking area code provided by the network side, obtain a plurality of cell identifiers corresponding to the first tracking area code.

[0127] Step 503: Receive the first authentication request provided by a cell base station corresponding to the plurality of cell identifiers.

[0128] Step 504: Authenticate the first authentication request provided by the cell base station corresponding to the plurality of cell identifiers by using an authentication file provided by the SIM card.

[0129] In the case where the user cannot achieve spatial movement within a certain range and replace a plurality of tracking area codes in a short time, the reason for the authentication failure can be judged by replacing the cell base station. Specifically,

[0130] After the network side sends an authentication request, if the authentication file or the tracking area code is damaged or missing, it may cause the authentication to fail, that is, it is impossible to judge whether the SIM card of the current authentication request is legal. Therefore, the user terminal obtains an authentication result of authentication failure. It may also be due to network congestion or authentication center congestion, or unstable base station signals in a certain cell and other reasons, resulting in the authentication failing, that is, it is impossible to judge whether the SIM card with a registration requirement currently is legal. Therefore, an authentication result of authentication failure is fed back to the user terminal. On the user terminal side, only the authentication result of authentication failure is known, but the reason for the failure is unknown. Therefore, further investigation is needed. One possibility is that due to the current base station being busy, the method of replacing different base stations to attempt authentication can be adopted to solve the problem.

[0131] After the user terminal records the authentication result of the first authentication request as a failure, it can then continue to attempt authentication in other ways. Preferably, it is by changing the tracking area code. Of course, as mentioned before, in many cases, the user cannot meet the conditions for changing the tracking area code (for example, the user has been in a fixed tracking area without spatial movement), then the user terminal attempts authentication registration by changing the cell.

[0132] It should be noted that in the embodiment of changing the cell, the first tracking area code may not be the first tracking area code in the authorization registration process. For example, it can be the second or third after the change. Correspondingly, the meaning of being unable to obtain the second tracking area code is being unable to obtain the third or fourth. On this basis, attempt to perform authorization registration by changing different cell base stations.

[0133] There are often multiple cells in a tracking area, and each cell has its own base station. The cell identifier can be understood as any one of the cell name (Cell Name), physical cell identity (Physical Cell Identity, PCI), cell global identifier (Cell Global Identifier, CGI), etc. The cell identifier can be provided by the base station to the user terminal together with the tracking area code when broadcasting information. When changing the cell base station, perform neighbor cell search to obtain the cells around the location of the user terminal and establish a cell list. Detect the signal strength and quality of each cell in the cell list, and preferentially select the cell with good signal strength and quality to attempt authentication registration. After receiving the feedback of authentication failure, select the next cell from the list to attempt authentication registration again. In this embodiment, it is not necessary to change the tracking area code and the authentication file. If the authentication still fails after changing multiple cells, the abnormal influence of factors such as temporary network instability or temporary base station instability on the authentication failure result can be excluded.

[0134] In practical applications, multiple cells can be changed simultaneously when changing the tracking area code, or different cells can be changed when unable to obtain the next tracking area code. No matter which method is adopted, its function is to be able to discover or exclude the adverse influence of the network side on the authentication result.

[0135] Figure 5b The flow diagram of another repeated authentication method provided by an exemplary embodiment of the present application. Specifically, if the authentication request results after changing different tracking area codes are all authentication failures, then determining that the authentication file of the SIM card is abnormal includes:

[0136] 504: Start the first authentication timer;

[0137] 505: Count the number of area codes of different tracking area codes for which the authentication result is authentication failure;

[0138] 506: If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, determine that the authentication file of the SIM card is abnormal;

[0139] 507: If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer and start the second authentication timer;

[0140] 508: Count the number of identifiers of multiple cell identifiers for which the authentication result is authentication failure;

[0141] 509 If the timing duration is within the time limit range of the second authentication timer and the number of identifiers is greater than the identifier number threshold, determine that the authentication file of the SIM card is abnormal;

[0142] 510: If the timing duration reaches the time limit range of the second authentication timer and the number of identifiers is less than the identifier number threshold, clear the second authentication timer.

[0143] As described above, in the case where more tracking area codes cannot be replaced, the method of replacing cells is adopted. However, for any solution to abnormal problems, the user experience needs to be considered. Therefore, when troubleshooting abnormalities, it is impossible to conduct troubleshooting without a time limit. Since the SIM card authentication registration is not successful, it means that the user terminal cannot connect to the network and the user cannot use the user terminal. The user can accept not being able to use the network for a period of time. Therefore, the first authentication timer and the second authentication timer can be set for the authentication process. Among them, the first authentication timer is used to time the tracking area code replacement cycle, and the second authentication timer is used to time the cell replacement cycle.

[0144] When inserting the SIM card into the card slot and starting the authentication, the first authentication timer is started, and at the same time, the retry count and the number of area codes are counted. If the authentication task is completed within the time limit range of the first authentication timer, in one case, when the timing duration is less than the first authentication timer and the number of area codes is less than the code number threshold, and the user terminal receives an authentication success authentication result, the first timer is cleared. In another case, when the timing duration is less than the first authentication timer and the number of area codes is greater than or equal to the code number threshold, and the user terminal receives an authentication failure authentication result, a feedback message of authentication failure is output on the display interface of the user terminal, and the first timer is cleared.

[0145] If the timing duration exceeds the time limit range of the first authentication timer, but the number of area codes is less than the code number threshold, the first authentication timer is cleared, and subsequent supplementary authentication steps are executed. While clearing the first authentication timer, a second authentication timer is started, and the number of identifiers for replacing the cell identifier is counted. Specifically,

[0146] When the first authentication timer times out and the number of area tracking code replacements is less than the code number threshold, count the number of identifiers of multiple cell identifiers for which the authentication result is authentication failure without replacing the tracking area code and the authentication file. If the timing duration is within the time limit range of the second authentication timer and the number of identifiers is greater than the identifier number threshold, it is determined that the authentication file of the SIM card is abnormal. During this process, by replacing the base stations corresponding to different cell identifiers, the influence of unstable factors on the network side on the authentication result can be excluded, so that it can be determined that it is very likely that the authentication fails because of the abnormal authentication file.

[0147] If the timing duration reaches the time limit range of the second authentication timer and the number of identifiers is less than the identifier number threshold, the second authentication timer is cleared. In this case, since the number of tracking area codes does not reach the code number threshold, the number of cell replacements does not reach the identifier number threshold, and both the first authentication timer and the second authentication timer have timed out. At this time, the user terminal can output a prompt message to prompt the user to go to the business hall of the telecommunications operator for professional help.

[0148] Such as Figure 6 is a schematic diagram of the process of replacing the authentication cell provided by an exemplary embodiment of the present application. Combining Figure 4 with the corresponding embodiment, if the user terminal cannot obtain a new tracking area code, different cell base stations will be replaced within the available tracking area. For example, first use the first base station in the first tracking area for authentication registration. Specifically, send the authentication request to the first base station, and then the first base station sends the authentication request to the user terminal. After determining the authentication failure result, establish a connection with the adjacent second base station and send the authentication request to the second base station, and then the second base station sends the authentication request to the user terminal. And so on, multiple different cells in this tracking area can be used for authentication registration. If the authentication still fails after replacing the cells and the number of cell identifiers exceeds the identifier number threshold, a prompt message for guiding the user to replace the SIM card is output on the display interface of the user terminal.

[0149] In some of the processes described in the above embodiments and the accompanying drawings, a plurality of operations appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order in which they appear herein or may be executed in parallel. The serial numbers of the operations, such as 401, 402, etc., are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. Additionally, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, nor do they limit that "first" and "second" are of different types.

[0150] Figure 7 FIG. is a schematic structural diagram of an exception handling device provided in another exemplary embodiment of the present application. As Figure 7 shown, the device includes:

[0151] An acquisition module 71, configured to acquire a tracking area code provided by a network side after identifying a SIM card.

[0152] A receiving module 72, configured to receive an authentication request corresponding to the tracking area code provided by the network side.

[0153] A determination module 73, configured to determine that the authentication file of the SIM card is abnormal if the authentication results of the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures.

[0154] Optionally, the receiving module 72 is configured to receive a first authentication request corresponding to a first tracking area code provided by the network side;

[0155] After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes:

[0156] After determining the authentication failure result corresponding to the first authentication request, acquire a second tracking area code provided by the network side;

[0157] Receive a second authentication request corresponding to the second tracking area code provided by the network side; authenticate the second authentication request using the authentication file provided by the SIM card.

[0158] Optionally, the sending module 72 is further configured to receive a first authentication request corresponding to the first tracking area code provided by the network side;

[0159] Count the number of times the first authentication request is received;

[0160] When the number of receptions is greater than the retry times threshold corresponding to the first tracking area code, terminate receiving the first authentication request;

[0161] Record the authentication result of authentication failure corresponding to the first authentication request.

[0162] Optionally, a determination module 73 is configured to count the number of area codes of the different tracking area codes for which the authentication result is authentication failure;

[0163] If the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal.

[0164] Optionally, a determination module 73 is configured to start a first authentication timer;

[0165] Count the number of area codes of the different tracking area codes for which the authentication result is authentication failure;

[0166] If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal;

[0167] If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer.

[0168] Optionally, a sending module 72 is configured to receive a first authentication request corresponding to a first tracking area code provided by the network side;

[0169] After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes:

[0170] After determining the authentication result of authentication failure corresponding to the first authentication request, if it fails to obtain a second tracking area code provided by the network side, obtain a plurality of cell identifiers corresponding to the first tracking area code;

[0171] Receive the first authentication request provided by the cell base station corresponding to the plurality of cell identifiers;

[0172] Authenticate the first authentication request provided by the cell base station corresponding to the plurality of cell identifiers by using the authentication file provided by the SIM card.

[0173] Optionally, a determination module 73 is configured to start a first authentication timer;

[0174] Count the number of area codes of the different tracking area codes for which the authentication result is authentication failure;

[0175] If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal;

[0176] If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer and start the second authentication timer;

[0177] Count the number of identifiers of multiple cell identifiers whose authentication result is authentication failure;

[0178] If the timing duration is within the time limit range of the second authentication timer and the number of identifiers is greater than the identifier number threshold, determine that the authentication file of the SIM card is abnormal;

[0179] If the timing duration reaches the time limit range of the second authentication timer and the number of identifiers is less than the identifier number threshold, clear the second authentication timer.

[0180] Optionally, it further includes an output module 74 for outputting a prompt message for guiding the user to replace the SIM card.

[0181] The internal functions and structures of the exception handling device are described above, such as Figure 8 is a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application. In practice, the exception handling device can be implemented as an electronic device, including: a memory 81, a processor 82, and a communication component 83.

[0182] The memory 81 is used to store computer programs and can be configured to store various other data to support operations on the electronic device. Examples of these data include instructions for any application program or method for operating on the electronic device, contact data, phone book data, messages, pictures, videos, etc.

[0183] The memory 81 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0184] The processor 82 is coupled to the memory 81 and is used to execute the computer program in the memory 81 for:

[0185] After identifying the SIM card, obtain the tracking area code provided by the network side;

[0186] Receive the authentication request corresponding to the tracking area code provided by the network side;

[0187] If the authentication results of the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, it is determined that the authentication file of the SIM card is abnormal.

[0188] Optionally, the processor 82 is further configured to receive a first authentication request corresponding to a first tracking area code provided by the network side;

[0189] After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes:

[0190] After determining the authentication failure result corresponding to the first authentication request, obtain a second tracking area code provided by the network side;

[0191] Receive a second authentication request corresponding to the second tracking area code provided by the network side;

[0192] Authenticate the second authentication request using the authentication file provided by the SIM card.

[0193] Optionally, the processor 82 is further configured to receive a first authentication request corresponding to the first tracking area code provided by the network side;

[0194] Count the number of times the first authentication request is received;

[0195] When the number of receptions is greater than the retry times threshold corresponding to the first tracking area code, terminate receiving the first authentication request;

[0196] Record the authentication failure result corresponding to the first authentication request.

[0197] Optionally, the processor 82 is further configured to count the number of area codes of the different tracking area codes whose authentication results are authentication failures;

[0198] If the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal.

[0199] Optionally, the processor 82 is further configured to start a first authentication timer;

[0200] Count the number of area codes of the different tracking area codes whose authentication results are authentication failures;

[0201] If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal;

[0202] If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer.

[0203] Optionally, the processor 82 is further configured to receive a first authentication request corresponding to the first tracking area code provided by the network side;

[0204] After sending the authentication request to the network side, it further includes:

[0205] After determining the authentication result of authentication failure corresponding to the first authentication request, if the acquisition of the second tracking area code provided by the network side fails, then acquire a plurality of cell identifiers corresponding to the first tracking area code;

[0206] Receive the first authentication request provided by the cell base stations corresponding to the plurality of cell identifiers;

[0207] Authenticate the first authentication request provided by the cell base stations corresponding to the plurality of cell identifiers by using the authentication file provided by the SIM card.

[0208] Optionally, the processor 82 is further configured to start a first authentication timer;

[0209] Count the number of area codes of the different tracking area codes whose authentication result is authentication failure;

[0210] If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, determine that the authentication file of the SIM card is abnormal;

[0211] If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer and start a second authentication timer;

[0212] Count the number of identifiers of a plurality of cell identifiers whose authentication result is authentication failure;

[0213] If the timing duration is within the time limit range of the second authentication timer and the number of identifiers is greater than the identifier number threshold, determine that the authentication file of the SIM card is abnormal;

[0214] If the timing duration reaches the time limit range of the second authentication timer and the number of identifiers is less than the identifier number threshold, clear the second authentication timer.

[0215] Optionally, the processor 82 is further configured to output a prompt message for guiding the user to replace the SIM card.

[0216] Further, as Figure 8 shown, the electronic device further includes: other components such as a communication component 83, a display 84, a power supply component 85, an audio component 86, etc. Figure 8 Only some components are schematically shown, which does not mean that the electronic device only includes Figure 8 the components shown.

[0217] Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which when executed can implement the steps executable by an electronic device in the above method embodiments.

[0218] The above Figure 8 The communication component therein is configured to facilitate communication between the device where the communication component is located and other devices in a wired or wireless manner. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0219] The above Figure 8 The display therein includes a screen, and the screen can include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions, but also detect the duration and pressure associated with the touch or swipe operations.

[0220] The above Figure 8 The power supply component therein provides power for various components of the device where the power supply component is located. The power supply component can include a power management system, one or more power supplies, and other components associated with generating, managing and distributing power for the device where the power supply component is located.

[0221] The above Figure 8 The audio component therein can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), which is configured to receive external audio signals when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode and a voice recognition mode. The received audio signals can be further stored in the memory or sent via the communication component. In some embodiments, the audio component further includes a speaker for outputting audio signals.

[0222] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0223] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, as well as the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0224] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0225] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0226] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0227] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0228] A computer-readable medium includes permanent and non-permanent, removable and non-removable media that can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer-readable medium does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0229] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.

[0230] The above description is only for the embodiments of the present application and is not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. An exception handling method, characterized in that, applied to a user terminal, the method includes: After recognizing the SIM card, obtain the tracking area code provided by the network side; Receive the authentication request corresponding to the tracking area code provided by the network side; If the authentication results of the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, it is determined that the authentication file of the SIM card is abnormal, where the different tracking area codes are the tracking area codes corresponding to different tracking areas.

2. The method according to claim 1, characterized in that, The receiving the authentication request corresponding to the tracking area code provided by the network side includes: Receive the first authentication request corresponding to the first tracking area code provided by the network side; After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes: After determining the authentication failure result corresponding to the first authentication request, obtain the second tracking area code provided by the network side; Receive the second authentication request corresponding to the second tracking area code provided by the network side; Authenticate the second authentication request using the authentication file provided by the SIM card.

3. The method according to claim 1 or 2, characterized in that, The receiving the first authentication request corresponding to the first tracking area code provided by the network side includes: Receive the first authentication request corresponding to the first tracking area code provided by the network side; Count the number of times the first authentication request is received; When the number of receptions is greater than the retry times threshold corresponding to the first tracking area code, terminate receiving the first authentication request; Record the authentication failure result corresponding to the first authentication request.

4. The method according to claim 1, characterized in that, The if the authentication results of the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, it is determined that the authentication file of the SIM card is abnormal includes: Count the number of area codes of the different tracking area codes whose authentication results are authentication failures; If the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal.

5. The method according to claim 1, characterized in that, The if the authentication results of the authentication requests corresponding to different tracking area codes using the authentication file provided by the SIM card are all authentication failures, it is determined that the authentication file of the SIM card is abnormal includes: Start the first authentication timer; Count the number of area codes of the different tracking area codes whose authentication results are authentication failures; If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, it is determined that the authentication file of the SIM card is abnormal; If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer.

6. The method according to claim 1, characterized in that, The receiving the authentication request corresponding to the tracking area code provided by the network side includes: Receive a first authentication request corresponding to a first tracking area code provided by the network side; After receiving the authentication request corresponding to the tracking area code provided by the network side, it further includes: After determining an authentication result of authentication failure corresponding to the first authentication request, if it fails to obtain a second tracking area code provided by the network side, obtain a plurality of cell identifiers corresponding to the first tracking area code; Receive the first authentication request provided by the cell base stations corresponding to the plurality of cell identifiers; Authenticate the first authentication request provided by the cell base stations corresponding to the plurality of cell identifiers by using an authentication file provided by the SIM card.

7. The method according to claim 6, wherein, If the authentication results of authenticating the authentication requests corresponding to different tracking area codes by using the authentication file provided by the SIM card are all authentication failures, determining that the authentication file of the SIM card is abnormal includes: Start a first authentication timer; Count the number of area codes of the different tracking area codes whose authentication results are authentication failures; If the timing duration is within the time limit range of the first authentication timer and the number of area codes is greater than or equal to the code number threshold, determine that the authentication file of the SIM card is abnormal; If the timing duration reaches the time limit range of the first authentication timer and the number of area codes is less than the code number threshold, clear the first authentication timer and start a second authentication timer; Count the number of identifiers of a plurality of cell identifiers whose authentication results are authentication failures; If the timing duration is within the time limit range of the second authentication timer and the number of identifiers is greater than the identifier number threshold, determine that the authentication file of the SIM card is abnormal; If the timing duration reaches the time limit range of the second authentication timer and the number of identifiers is less than the identifier number threshold, clear the second authentication timer.

8. The method according to claim 1, wherein, After determining that the authentication file of the SIM card is abnormal, it further includes: Output a prompt message for guiding the user to replace the SIM card.

9. An exception handling device, wherein, The device includes: An acquisition module, configured to acquire a tracking area code provided by the network side after identifying the SIM card; A receiving module, configured to receive an authentication request corresponding to the tracking area code provided by the network side; A determination module, configured to determine that the authentication file of the SIM card is abnormal if the authentication results of authenticating the authentication requests corresponding to different tracking area codes by using the authentication file provided by the SIM card are all authentication failures, where the different tracking area codes are respectively the tracking area codes corresponding to different tracking areas.

10. An electronic device, wherein, It includes: A processor and a memory; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory, so that the processor executes the method according to any one of claims 1-8.

11. A computer-readable storage medium, wherein, The computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are run, the method described in any one of claims 1-8 is implemented.

12. A computer program product, comprising a computer program or instructions, wherein, when the computer program or instructions are executed by a processor, the method described in any one of claims 1-8 is implemented.

Images