WO2024124579A1

WO2024124579A1 - Access anomaly handling method and apparatus

Info

Publication number: WO2024124579A1
Application number: PCT/CN2022/139775
Authority: WO
Inventors: 毛玉欣; 张会龙; 李松; 沈洋
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-12-16
Filing date: 2022-12-16
Publication date: 2024-06-20
Also published as: CN116325982A

Abstract

The present application relates to the technical field of communications. Provided are an access anomaly handling method and apparatus. The method comprises: using a counter to count the number of times a terminal device re-initiates a registration request due to an anomaly during the current registration process of accessing a network; and according to said number of times, determining whether to suspend the current registration process of the terminal device. By means of using the technical solution of the present application, the situation of deadlock can be avoided in the case of abnormal registration, and if a certain number of registration request re-tries is reached, the current registration process of a terminal device can be effectively suspended.

Description

A method and device for handling access exceptions

Technical Field

The present application relates to the field of communication technology, and in particular to a method and device for handling access exceptions.

Background technique

The terminal device (User Equipment, UE) needs to initiate the network access registration process to access the wireless network. Only after successful registration can various data services be carried out through the network.

At present, when a terminal device initiates a registration process for accessing a network (such as initial registration, registration update, or scheduled registration, etc.), if an exception occurs, the terminal device will continuously re-initiate a new registration request until the registration is successful. However, this retry mechanism can easily cause a deadlock under certain abnormal circumstances, which in turn causes the terminal device to be unable to complete or terminate the registration process.

Summary of the invention

The present application proposes an access exception processing method and device, which can solve the technical problem that the retry mechanism in the above-mentioned prior art can easily cause deadlock under certain abnormal circumstances, thereby causing the terminal device to be unable to complete or terminate the registration process.

The first aspect of the present application provides an access exception handling method, which is applied to the terminal device side for execution. The method includes: using a counter to count the number of times that an exception occurs during the current registration process of the terminal device accessing the network, resulting in the re-initiating of a registration request; based on the number of times, determining whether to terminate the current registration process of the terminal device.

In some embodiments of the present application, the method further includes: when the terminal device meets a preset condition, setting the initial value of the counter to 0, wherein meeting the preset condition includes one of the following:

The terminal device is in a just-started state;

The serving cell selected by the terminal device changes;

The tracking area (TA) where the terminal device is located changes;

The terminal device is registered successfully.

In some embodiments of the present application, the counter is a shared counter; the shared counter is used to count the sum of the number of times the registration request is re-initiated due to different registration anomalies; when the sum of the times counted by the shared counter is equal to the total preset number threshold, the current registration process of the terminal device is terminated.

In some embodiments of the present application, the counter is a counter corresponding to a predetermined registration abnormality; when the counter reaches a cumulative number corresponding to the predetermined registration abnormality equal to a preset number threshold corresponding to the predetermined registration abnormality, the current registration process of the terminal device corresponding to the predetermined registration abnormality is terminated.

In some embodiments of the present application, the abnormal registration situation includes at least one of the following:

The Non-Access Stratum (NAS) layer of the terminal device receives an indication of a failure to send a registration request message from a lower layer;

The NAS layer of the terminal device receives an indication of a Radio Resource Control (RRC) connection suspension from a lower layer;

The NAS layer of the terminal device receives an indication of a failure in the registration completion message;

The NAS layer of the terminal device receives an indication that the registration completion message failed, and the current tracking area identifier (Tracking Area ID, TAI) of the terminal device changes.

In some embodiments of the present application, terminating the current registration process of the terminal device includes: controlling the terminal device to no longer initiate a registration request to the network at a current access location, wherein the current access location includes one of the following:

The serving cell currently selected by the terminal device;

The TA where the terminal device is currently located.

In some embodiments of the present application, the method further includes: setting a waiting time and starting timing; after the waiting time ends, controlling the terminal device to re-initiate a registration request and resetting the initial value of the counter to 0.

In some embodiments of the present application, the method also includes: adding the cell identifier of the service cell currently selected by the terminal device to a first prohibited list to prohibit the terminal device from selecting the service cell corresponding to the cell identifier in the first prohibited list to initiate a registration request; when the service cell currently selected by the terminal device changes, controlling the terminal device to re-initiate the registration request, resetting the initial value of the counter to 0, and removing the cell identifier from the first prohibited list.

In some embodiments of the present application, the method also includes: adding the TAI of the TA in which the terminal device is currently located to a second prohibited list to prohibit the terminal device from initiating a registration request when it is in the TA corresponding to the TAI in the second prohibited list; when the TA in which the terminal device is currently located changes, controlling the terminal device to re-initiate the registration request, resetting the initial value of the counter to 0, and removing the TAI from the second prohibited list.

In some embodiments of the present application, the method also includes: adding the radio access technology (Radio Access Technology, RAT) currently selected by the terminal device to a third prohibited list to prohibit the terminal device from selecting the access network corresponding to the RAT in the third prohibited list to initiate a registration request; when the RAT currently selected by the terminal device changes, controlling the terminal device to re-initiate the registration request; if the registration is successful, removing the RAT from the third prohibited list and resetting the initial value of the counter to 0.

In some embodiments of the present application, the counter does not count registration anomalies of the emergency call service.

The second aspect of the present application provides an access exception processing device, which is applied to the terminal device side, and the device includes: a statistical module, which is configured to use a counter to count the number of times that an exception occurs during the current registration process of the terminal device accessing the network, resulting in the re-initiating of a registration request; a determination module, which is configured to determine whether to terminate the current registration process of the terminal device based on the number of times.

The third aspect embodiment of the present application provides a communication device, which includes: a transceiver; a memory; a processor, which is connected to the transceiver and the memory respectively, and is configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the method of the first aspect embodiment of the present application.

The fourth aspect embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the method of the first aspect embodiment of the present application can be implemented.

The embodiment of the present application provides an access exception processing method and device, which uses a counter to count the number of times a terminal device re-initiates a registration request due to an exception during the current registration process of accessing the network, and then determines whether to terminate the current registration process of the terminal device based on the cumulative number of times obtained by statistics, thereby avoiding deadlock when a registration exception occurs. If a certain number of registration request retries is reached, the current registration process of the terminal device can be effectively terminated.

Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

FIG1 is a timing diagram of an example of an access registration process according to an embodiment of the present application;

FIG2 is a schematic diagram of a flow chart of a method for handling access exceptions according to an embodiment of the present application;

FIG3 is a schematic diagram of a flow chart of a method for handling access exceptions according to an embodiment of the present application;

FIG4 is a schematic diagram of a flow chart of a method for handling access exceptions according to an embodiment of the present application;

FIG5 is a schematic diagram of a flow chart of a method for handling access exceptions according to an embodiment of the present application;

FIG6 is a timing diagram of an example of an access exception processing method according to an embodiment of the present application;

FIG7 is a block diagram of an access exception processing device according to an embodiment of the present application;

FIG8 is a schematic diagram of the structure of a communication device according to an embodiment of the present application;

FIG. 9 is a schematic diagram of the structure of a chip provided in an embodiment of the present application.

Detailed ways

Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limitations on the present application. It should be noted that, in the absence of conflict, the embodiments of the present application and the features in the embodiments may be combined with each other.

The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the embodiments of the present application. The singular forms of "a" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that, although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the embodiments of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determination".

The terminal equipment (UE) needs to initiate the access registration process to access the network. Only after the registration is successful can various data services be carried out through the network. Taking the 5G terminal accessing the 5G core network (5G Core Network, 5GC) and initiating a registration request as an example to illustrate the registration process of network access, as shown in Figure 1. The terminal equipment uses the following process for initial access registration and registration update.

Step 1. The terminal device sends a registration request message to the radio access network ((Radio) Access Network, (R)AN).

The registration request message includes access node (AN) parameters, registration type, Subscription Concealed Identifier (SUCI) or 5G-Subscription Concealed Identifier (5G-GUTI) or Permanent Equipment Identifier (PEI), requested slice selection assistance information (NSSAI), last visited TAI (if available), etc. The registration type indicates whether the terminal device wants to perform initial registration, mobility registration update, periodic registration update or emergency registration, etc. The last visited TAI can be included to help the Access and Mobility Management Function (AMF) network element generate a registration area for the terminal device.

Step 2: (R)AN selects the AMF network element based on the RAT and the requested NSSAI.

If the (R)AN cannot select a suitable AMF network element, it forwards the Registration Request message to the AMF network element that has been configured in the (R)AN.

Step 3. (R)AN sends a registration request message for accessing network N2 to the new AMF network element.

The registration request message contains parameters of the access network N2, a registration request, etc. The parameters of the access network N2 include the selected public land mobile network identifier (Public Land Mobile Network IDentity, PLMN ID), location information, and a cell identifier related to the service cell selected by the terminal device.

Step 4. If the AMF network element has changed since the last registration process, the new AMF network element can query the stored Subscription Permanent Identifier (SUPI) and UE context of the terminal device from the old AMF network element.

Step 5: If the terminal device does not provide SUCI and does not retrieve SUCI from the old AMF network element, the new AMF initiates an identity request procedure to the terminal device to request SUCI.

Step 6. The new AMF network element may decide to initiate UE authentication by calling the Authentication Server Function (AUSF) network element.

The AMF network element selects the AUSF network element based on the SUPI or SUCI.

Step 7. If the AMF network element has changed since the last registration process, or if the terminal device provides a SUPI that does not refer to a valid context in the AMF network element, the AMF network element based on the SUPI selects Unified Data Management (UDM) and registers with the UDM network element.

If the AMF network element does not have the subscription data of the terminal device, the AMF network element retrieves the access and mobility subscription data, etc. from the UDM network element.

Step 8. The new AMF network element establishes/modifies the access management (AM) policy association with the Policy Control Function (PCF) network element.

Step 9. If the list of Protocol Data Unit (PDU) sessions to be activated is included in the registration request in step 1, the AMF network element sends an Nsmf_PDUSSession_UpdateSMContext request to the Session Management Function (SMF) associated with the PDU sessions in order to activate the user plane connections of these PDU sessions.

Step 10: The new AMF network element sends a registration acceptance message to the terminal device, indicating that the registration request has been accepted.

The Registration Accept message contains the Registration Area, Mobility Restrictions, Allowed NSSAI, Strict Periodic Registration Timer Indication, etc. If the AMF network element allocates a new Registration Area (RA), it shall send the Registration Area to the terminal device. If the Registration Area is not included in the Registration Accept message, the terminal device shall consider the old Registration Area as valid. Mobility Restrictions are included if Mobility Restrictions apply to the UE and the Registration Type is not Emergency Registration.

Step 11: The new AMF network element executes the terminal device policy association establishment.

For registration of emergency call service, this step will be skipped. The new AMF network element sends a Npcf_UEPolicyControl create request to the PCF network element. The PCF network element sends a Npcf_UEPolicyControl create response to the new AMF network element. The PCF network element triggers the terminal device configuration update process to update the terminal device policy.

Step 12: When the terminal device successfully updates itself after receiving the NSSAI related information, the terminal device sends a registration completion message to the AMF network element.

Step 13. The remaining steps of the registration process can refer to 3GPP TS 23.502.

The exceptions and solutions encountered during the registration process of the network access shown in Figure 1 are as follows:

A. If the Registration Request message sent from the Access Stratum (AS) to the NAS layer fails, or the AS layer indicates that the RRC connection is suspended due to a change in the serving cell.

The registration process for mobility or periodic registration updates needs to be aborted and immediately re-initiated. The terminal device needs to set the 5GS (5G System) update status to "5U2 NOT UPDATED" [In order to describe the detailed terminal device behavior, the 5GS update (5U) status related to a specific user is determined. 5U2 NOT UPDATED is used to indicate that the last registration or service request attempt failed, such as no response or rejection message was received from the AMF network element].

B. The Registration Complete message fails to be delivered, indicating that the current TAI has changed.

If the current TAI changes and the changed current TAI is not included in the TAI list of the terminal device, the registration process for mobility or periodic registration updates needs to be aborted and a new registration request needs to be initiated immediately. The terminal device needs to set the 5GS update status to "5U2 NOT UPDATED".

If the current TAI changes and the changed current TAI is still included in the TAI list of the terminal device, how to rerun the ongoing process depends on the configuration of the terminal device.

C. The Registration Complete message fails to be delivered and indicates that the current TAI has not changed. How to rerun the ongoing process depends on the configuration of the terminal device.

In the above exception handling process (such as the above three registration exceptions A, B, and C) for the registration process (such as initial registration, registration update, or scheduled registration, etc.), the terminal device will continuously re-initiate new registration requests until the registration is successful. However, this retry mechanism can easily cause deadlock, which in turn causes the terminal device to be unable to complete or terminate the registration process.

To this end, this embodiment proposes an access exception processing method and device, which can solve the technical problem that the retry mechanism in the prior art can easily cause deadlock under certain abnormal circumstances, thereby causing the terminal device to be unable to complete or terminate the registration process.

The access exception processing method and device provided by the present application are described in detail below with reference to the accompanying drawings.

Fig. 2 shows a schematic flow chart of a method for handling access exceptions according to an embodiment of the present application. As shown in Fig. 2, the method is applied to the terminal device side and may include the following steps.

Step 201: Use a counter to count the number of times a registration request is re-initiated due to anomalies in the current registration process of the terminal device accessing the network.

The current registration process of accessing the network may be an initial registration process when the terminal device is just turned on, or a registration update process initiated due to a change in the current access location, or a registration process triggered regularly according to a preset period, etc.

This embodiment pre-sets a registration attempt counter (registrationattemptcounter), i.e., a counter, and sets a preset number threshold of the counter (for example, it can be set to 5 times, etc.). During the current registration process of the terminal device accessing the network, if an abnormality occurs and causes a registration request to be re-initiated, the counter will be accumulated by 1 accordingly.

Step 202: Determine whether to terminate the current registration process of the terminal device according to the cumulative number of times obtained by statistics.

For example, when the cumulative number of times obtained by statistics is equal to a preset number threshold, the terminal device terminates the current registration process and no longer initiates a registration request to the network (RAN).

As can be seen from the above, the access exception handling method provided in this embodiment can avoid deadlock when a registration exception occurs, and can effectively terminate the current registration process of the terminal device if a certain number of registration request retries is reached.

Fig. 3 shows a schematic flow diagram of a method for handling access exceptions according to an embodiment of the present application. Based on the embodiment shown in Fig. 2, as shown in Fig. 3, the method is applied to the terminal device side and may include the following steps.

Step 301: When the terminal device meets a preset condition, the initial value of the counter is set to 0.

Among them, satisfying the preset conditions includes one of the following:

The terminal device is in the state of just being powered on; the service cell selected by the terminal device changes; the TA where the terminal device is located changes; the terminal device is successfully registered.

For example, after the terminal device is turned on, if it needs to access the network, it will initiate the initial registration process. At this time, the initial value of the counter is first set to 0, and then the counter is used for statistics, such as the process shown in steps 302 to 303. Or after the terminal device successfully registers this time, the initial value of the counter is reset to 0 for use in the next scheduled registration process.

For another example, when the service cell selected by the terminal device changes or the TA in which the terminal device is located changes, a registration update process is initiated, at which time the initial value of the counter is first set to 0, and then the counter is used for statistics, such as executing the process shown in steps 302 to 303. It should be noted that, according to actual needs, when the service cell selected by the terminal device changes or the TA in which the terminal device is located changes, the initial value of the counter may not be set to 0, and then the cumulative statistics are continued based on the number of times the counter has counted, that is, the process shown in steps 302 to 303 is executed.

Step 302: Use a counter to count the number of times a registration request is re-initiated due to anomalies in the current registration process of the terminal device accessing the network.

In some examples, the counter does not count the registration exceptions for the emergency call service. For example, when the registration request initiated by the terminal device to the network is a registration request for the emergency call service, even if an exception occurs, the counter will not be used to count accordingly, that is, the counter will not count the exceptions for emergency registration, so as to improve the success rate of users obtaining emergency call services.

Step 303: Determine whether to terminate the current registration process of the terminal device according to the cumulative number of times obtained by statistics.

In some examples, terminating the current registration process of the terminal device may specifically include: controlling the terminal device to no longer initiate a registration request to the network at the current access location, wherein the current access location includes one of the following:

The service cell currently selected by the terminal device; the TA where the terminal device is currently located.

For example, when the cumulative number of times obtained by statistics is equal to a preset number threshold, the terminal device terminates the current registration process and no longer initiates a registration request to the network (RAN) in the currently selected service cell or the current TA.

By applying the access exception processing method provided in this embodiment, a deadlock situation can be avoided when a registration exception occurs. If a certain number of registration request retries is reached, the current registration process of the terminal device can be effectively terminated.

FIG4 shows a flow chart of an access exception handling method according to an embodiment of the present application. Based on the embodiment shown in FIG2, as an optional method, the counter may be a shared counter, that is, a counter that uniformly counts different registration exception situations, and the shared counter is used to count the sum of the number of times the registration request is re-initiated due to different registration exception situations; when the sum of the times counted by the shared counter is equal to the total preset number threshold, the current registration process of the terminal device is terminated. A specific example can be shown in FIG4. The method is applied to the terminal device side and may include the following steps.

Step 401: Use a shared counter to count the total number of times registration requests are re-initiated due to different registration anomalies.

In some examples, the registration abnormality may include at least one of the following:

1. The NAS layer of the terminal device receives an indication of failure to send a registration request message from the lower layer (the layer below the protocol); 2. The NAS layer of the terminal device receives an indication of RRC connection suspension from the lower layer (such as the AS layer indicating that the RRC connection is suspended due to a cell change); 3. The NAS layer of the terminal device receives an indication of failure to send a registration completion message; 4. The NAS layer of the terminal device receives an indication of failure to send a registration completion message, and the current TAI of the terminal device changes.

This embodiment can uniformly count the above-mentioned several abnormal registration situations and set corresponding preset number thresholds. Or it is not limited to these abnormal registration situations, and can also include other abnormal registration situations, and then uniformly count these abnormal registration situations and set corresponding preset number thresholds, such as for the abnormal processing of registration request and registration complete messages, the value of the shared counter needs to be increased by 1.

In some examples, the shared counter in step 401 does not count the registration anomalies of the emergency call service. For example, when the registration request initiated by the terminal device to the network is a registration request for the emergency call service, even if any of the above registration anomalies occurs, the counter will not be used to count accordingly, so as to improve the success rate of the user obtaining the emergency call service.

Step 402: When the sum of the times counted by the shared counter is equal to the total preset times threshold, the current registration process of the terminal device is terminated.

In some examples, after terminating the current registration process of the terminal device, the method of this embodiment may also include: setting a waiting time and starting a timer; after the waiting time ends, controlling the terminal device to re-initiate a registration request and resetting the initial value of the counter to 0.

For example, when the sum of the times counted by the shared counter is equal to the total preset number threshold, the current registration process of the terminal device is terminated, the waiting time is set and the timing is started. After the waiting time is over, the terminal device is controlled to re-initiate the registration request and reset the initial value of the shared counter to 0.

In some examples, after terminating the current registration process of the terminal device, the method of this embodiment may also include: adding the cell identifier of the service cell currently selected by the terminal device to a first prohibited list to prohibit the terminal device from selecting the service cell corresponding to the cell identifier in the first prohibited list to initiate a registration request, such as prohibiting the terminal device from selecting the service cells corresponding to the cell identifiers in the first prohibited list to initiate a registration request; when the service cell currently selected by the terminal device changes, controlling the terminal device to re-initiate the registration request, resetting the initial value of the counter to 0, and removing the cell identifier from the first prohibited list.

For example, when the sum of the times counted by the shared counter is equal to the total preset times threshold, the current registration process of the terminal device is terminated, and the terminal device adds the cell ID of the currently selected service cell to the cell forbidden list. If the cell forbidden list is set, when the service cell currently selected by the terminal device changes, the terminal device re-initiates the registration request, and the counter returns to the initial value 0. At the same time, the cell ID added to the cell forbidden list is removed from the forbidden list.

In some examples, after terminating the current registration process of the terminal device, the method of this embodiment may also include: adding the TAI of the TA in which the terminal device is currently located to a second prohibited list to prohibit the terminal device from initiating a registration request when it is in the TA corresponding to the TAI in the second prohibited list, such as prohibiting the terminal device from initiating a registration request when it is in the TA corresponding to the TAI in the second prohibited list; when the TA in which the terminal device is currently located changes, controlling the terminal device to re-initiate the registration request, resetting the initial value of the counter to 0, and removing the TAI from the second prohibited list.

For example, when the sum of the times counted by the shared counter is equal to the total preset times threshold, the current registration process of the terminal device is terminated, and the terminal device adds the TAI of the current TA to the TAI forbidden list (forbidden TAI list). If a TAI forbidden list is set, when the TA currently in which the terminal device is located changes, the terminal device re-initiates a registration request, and the counter returns to the initial value of 0. At the same time, the TAI added to the forbidden list will be removed from the forbidden list.

In some examples, after terminating the current registration process of the terminal device, the method of this embodiment may also include: adding the RAT currently selected by the terminal device to a third prohibited list to prohibit the terminal device from selecting the access network corresponding to the RAT in the third prohibited list to initiate a registration request, such as prohibiting the terminal device from selecting the access networks corresponding to the RAT in the third prohibited list to initiate a registration request; when the RAT currently selected by the terminal device changes, controlling the terminal device to re-initiate the registration request; if the registration is successful, removing the RAT from the third prohibited list, and resetting the initial value of the counter to 0.

For example, when the sum of the times counted by the shared counter is equal to the total preset number threshold, the current registration process of the terminal device is terminated, and the terminal device adds the currently selected RAT to the RAT prohibited list. If the RAT prohibited list is set, the terminal device re-executes the RAT selection and initiates a registration request. If the registration is successful, the RAT previously added to the RAT prohibited list is deleted, and the counter is restored to the initial value of 0.

FIG5 shows a flow chart of an access exception handling method according to an embodiment of the present application. Based on the embodiment shown in FIG2, as an optional method, each registration exception situation is provided with a corresponding counter and a preset number threshold, that is, for different registration exception situations, there are corresponding counters and preset number thresholds, such as a counter corresponding to a predetermined registration exception situation; when the counter reaches the cumulative number of times corresponding to the predetermined registration exception situation equal to the preset number threshold corresponding to the predetermined registration exception situation, the current registration process of the terminal device corresponding to the predetermined registration exception situation is terminated. Specifically, as shown in FIG5, the method is applied to the terminal device side and may include the following steps.

Step 501: Utilize the counters corresponding to each registration abnormality to count the number of times the registration request is re-initiated due to each abnormality.

This embodiment can count the above-mentioned several abnormal registration situations respectively and set the preset number thresholds for each of them. Or it is not limited to these abnormal registration situations, and can also include other abnormal registration situations, and then count these different abnormal registration situations respectively and set the preset number thresholds for each of them. For example, the abnormal processing of the registration request and registration complete message needs to be counted respectively, and the value of the counter corresponding to the abnormal registration situation is increased by 1.

Step 502: When the counter reaches a cumulative number corresponding to a predetermined registration abnormality equal to a preset number threshold corresponding to the predetermined registration abnormality, the current registration process of the terminal device corresponding to the predetermined registration abnormality is terminated.

The predetermined registration abnormality may be any one of the aforementioned registration abnormalities, or may not be limited to these registration abnormalities, but may be any one of the registration abnormalities including these registration abnormalities.

Aborting the current registration process of the terminal device corresponding to the predetermined registration abnormality includes: controlling the terminal device to no longer initiate a registration request to the network at the current access location, wherein the current access location includes one of the following:

For example, when the cumulative number of times counted for registration abnormality situation a is equal to the preset number threshold corresponding to the registration abnormality situation a, the terminal device terminates the current registration process corresponding to the registration abnormality situation a, and no longer initiates a registration request to the network (RAN) in the currently selected service cell or the current TA.

For example, when the cumulative number of times counted for registration abnormality situation b is equal to the preset number threshold corresponding to the registration abnormality situation b, the terminal device terminates the current registration process corresponding to the registration abnormality situation b, sets the waiting time and starts timing. After the waiting time ends, the terminal device is controlled to re-initiate the registration request and reset the initial value of the counter of registration abnormality situation b to 0.

For example, when the cumulative number of times counted for registration abnormality c is equal to the preset number threshold corresponding to the registration abnormality c, the terminal device terminates the current registration process corresponding to the registration abnormality c, and the terminal device adds the cell ID of the currently selected service cell to the cell prohibited list. If the cell prohibited list is set, when the service cell currently selected by the terminal device changes, the terminal device re-initiates the registration request and restores the counter of the registration abnormality c to the initial value of 0. At the same time, the cell ID added to the cell prohibited list is removed from the prohibited list.

For example, when the cumulative number of times counted for registration abnormality d is equal to the preset number threshold corresponding to the registration abnormality d, the terminal device terminates the current registration process corresponding to the registration abnormality d, and the terminal device adds the TAI of the current TA to the TAI forbidden list (forbidden TAI list). If the TAI forbidden list is set, when the TA currently in which the terminal device is located changes, the terminal device re-initiates the registration request and restores the counter of the registration abnormality d to the initial value of 0. At the same time, the TAI added to the forbidden list is removed from the forbidden list.

For example, when the cumulative number of times counted for registration abnormality e is equal to the preset number threshold corresponding to the registration abnormality e, the terminal device terminates the current registration process corresponding to the registration abnormality e, and the terminal device adds the currently selected RAT to the RAT prohibited list. If the RAT prohibited list is set, the terminal device re-executes the RAT selection and initiates a registration request. If the registration is successful, the RAT previously added to the RAT prohibited list is deleted, and the counter of the registration abnormality e is restored to the initial value of 0.

As shown in Figure 6, it is a timing diagram of a method for access processing exception provided in an embodiment of the present application. The method comprises the following steps:

Step 601, when the terminal device (UE) is turned on or the service cell (cell) currently selected by the terminal device, or the TA in which the terminal device is currently located changes, the registration attempt counter (registrationattemptcounter) set for the registration request failure (Registration request failure) is initialized with an initial value of 0 and a threshold value of 5.

Step 602: The terminal device initiates a registration request to the (R)AN.

Step 603: (R)AN selects an AMF network element serving the terminal device according to the registration request of the terminal device.

Step 604: (R)AN forwards the registration request to the AMF network element.

Step 605: When the terminal device does not receive a registration acceptance or registration failure message within a preset time (given time), and the registration request is not a registration request for an emergency call service, the terminal device increases the value of the counter by 1.

Step 606: The terminal device re-initiates the registration request process.

Step 607: When the terminal device does not receive a registration acceptance or registration failure message within the preset time (given time), and the registration request is not a registration request for an emergency call service, the terminal device increases the value of the counter by 1. When the value of the counter is equal to 5, the terminal device terminates the registration request process. The terminal device will no longer initiate a registration request in the current access location (the cell currently selected by the terminal device or the TA currently located by the terminal device).

When the cell currently selected by the terminal device changes, or the current TAI of the terminal device changes, the terminal device can reinitialize the counter and re-initiate the access registration process.

In the above embodiments provided by the present application, the method provided by the embodiment of the present application is introduced from the perspective of the terminal device. In order to implement the various functions in the method provided by the above embodiments of the present application, the terminal device may include a hardware structure and a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. A certain function of the above functions can be executed in the form of a hardware structure, a software module, or a hardware structure plus a software module.

Corresponding to the access exception handling methods provided in the above-mentioned embodiments, the present application also provides an access exception handling device. Since the access exception handling device provided in the embodiment of the present application corresponds to the access exception handling methods provided in the above-mentioned embodiments, the implementation method of the access exception handling method is also applicable to the access exception handling device provided in this embodiment, and will not be described in detail in this embodiment.

FIG7 is a schematic diagram of the structure of an access exception processing device provided in an embodiment of the present application, and the access exception processing device can be used on the terminal device side.

As shown in Figure 7, the device may include: a statistical module 71, configured to use a counter to count the number of times a registration request is re-initiated due to anomalies occurring during the current registration process of the terminal device accessing the network; a determination module 72, configured to determine whether to terminate the current registration process of the terminal device based on the number of times.

In some embodiments, the statistics module 71 is further configured to set the initial value of the counter to 0 when the terminal device meets a preset condition, wherein meeting the preset condition includes one of the following:

The terminal device is in a just-started state;

The serving cell selected by the terminal device changes;

The TA where the terminal device is located changes;

The terminal device is registered successfully.

In some embodiments, the counter is a shared counter; the shared counter is used to count the sum of the number of times registration requests are re-initiated due to different registration anomalies; when the sum of the times counted by the shared counter is equal to the total preset number threshold, the current registration process of the terminal device is terminated.

In some embodiments, the counter is a counter corresponding to a predetermined registration abnormality; when the counter reaches a cumulative number corresponding to the predetermined registration abnormality equal to a preset number threshold corresponding to the predetermined registration abnormality, the current registration process of the terminal device corresponding to the predetermined registration abnormality is terminated.

In some embodiments, the registration abnormality includes at least one of the following:

The NAS layer of the terminal device receives an indication from a lower layer that a registration request message fails to be sent;

The NAS layer of the terminal device receives an indication of RRC connection suspension from a lower layer;

The NAS layer of the terminal device receives an indication of a registration completion message failure, and the current TAI of the terminal device changes.

In some embodiments, the determination module 72 is specifically configured to control the terminal device to no longer initiate a registration request to the network at the current access location, wherein the current access location includes one of the following:

The serving cell currently selected by the terminal device;

The TA where the terminal device is currently located.

In some embodiments, the determination module 72 is further configured to set a waiting time and start timing; after the waiting time is over, the terminal device is controlled to re-initiate a registration request and reset the initial value of the counter to 0.

In some embodiments, the determination module 72 is also configured to add the cell identifier of the service cell currently selected by the terminal device to a first prohibited list to prohibit the terminal device from selecting the service cell corresponding to the cell identifier in the first prohibited list to initiate a registration request; when the service cell currently selected by the terminal device changes, the terminal device is controlled to re-initiate the registration request, the initial value of the counter is reset to 0, and the cell identifier is removed from the first prohibited list.

In some embodiments, the determination module 72 is also configured to add the TAI of the TA in which the terminal device is currently located to a second prohibited list to prohibit the terminal device from initiating a registration request when it is in the TA corresponding to the TAI in the second prohibited list; when the TA in which the terminal device is currently located changes, control the terminal device to re-initiate the registration request, reset the initial value of the counter to 0, and remove the TAI from the second prohibited list.

In some embodiments, the determination module 72 is also configured to add the RAT currently selected by the terminal device to a third prohibited list to prohibit the terminal device from selecting an access network corresponding to the RAT in the third prohibited list to initiate a registration request; when the RAT currently selected by the terminal device changes, control the terminal device to re-initiate a registration request; if the registration is successful, remove the RAT from the third prohibited list and reset the initial value of the counter to 0.

In some embodiments, the counter does not count registration exceptions for emergency call services.

By applying the technical solution of this embodiment, a deadlock situation can be avoided when a registration is abnormal. If a certain number of registration request retries is reached, the current registration process of the terminal device can be effectively terminated.

Please refer to Figure 8, which is a schematic diagram of the structure of a communication device 1800 provided in this embodiment. The communication device 1800 can be a network device, or a user device, or a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a processor that supports the user device to implement the above method. The device can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.

The communication device 1800 may include one or more processors 1801. The processor 1801 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.

Optionally, the communication device 1800 may further include one or more memories 1802, on which a computer program 1804 may be stored, and the processor 1801 executes the computer program 1804 so that the communication device 1800 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory 1802. The communication device 1800 and the memory 1802 may be provided separately or integrated together.

Optionally, the communication device 1800 may further include a transceiver 1805 and an antenna 1806. The transceiver 1805 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function. The transceiver 1805 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., and is used to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is used to implement a transmitting function.

Optionally, the communication device 1800 may further include one or more interface circuits 1807. The interface circuit 1807 is used to receive code instructions and transmit them to the processor 1801. The processor 1801 executes the code instructions to enable the communication device 1800 to execute the method described in the above method embodiment.

In one implementation, the processor 1801 may include a transceiver for implementing the receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

In one implementation, the processor 1801 may store a computer program 1803, which runs on the processor 1801 and enables the communication device 1800 to perform the method described in the above method embodiment. The computer program 1803 may be fixed in the processor 1801, in which case the processor 1801 may be implemented by hardware.

In one implementation, the communication device 1800 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiment. The processor and transceiver described in the present application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication device described in the above embodiments may be a network device or a user device, but the scope of the communication device described in the present application is not limited thereto, and the structure of the communication device may not be limited by FIG. 8. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

(1) Independent integrated circuit IC, or chip, or chip system or subsystem;

(2) having a set of one or more ICs, and optionally, the IC set may also include a storage component for storing data and computer programs;

(3) ASIC, such as modem;

(4) Modules that can be embedded in other devices;

(5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

(6)Others

For the case where the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 9. The chip shown in Figure 9 includes a processor 1901 and an interface 1902. The number of processors 1901 can be one or more, and the number of interfaces 1902 can be multiple.

Optionally, the chip further includes a memory 1903, and the memory 1903 is used to store necessary computer programs and data.

Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrated. Available media can be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks (SSD)), etc.

A person skilled in the art may understand that the various numerical numbers such as first and second involved in the present application are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application, but also indicate the order of precedence.

At least one in the present application can also be described as one or more, and a plurality can be two, three, four or more, which is not limited in the present application. In the embodiments of the present application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no order of precedence or size between the technical features described by the "first", "second", "third", "A", "B", "C" and "D".

As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and/or data to a programmable processor.

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution of this application can be achieved, and this document is not limited here.

In addition, it should be understood that the various embodiments described in the present application may be implemented individually or in combination with other embodiments when the solution permits.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments applied for herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for handling access exceptions, characterized in that it is applied to a terminal device side for execution, and the method comprises:

A counter is used to count the number of times a registration request is re-initiated due to anomalies in the current registration process of the terminal device accessing the network;

According to the number of times, it is determined whether to terminate the current registration process of the terminal device.
The method according to claim 1, characterized in that the method further comprises:

When the terminal device meets a preset condition, the initial value of the counter is set to 0, wherein meeting the preset condition includes one of the following:

The terminal device is in a just-started state;

The serving cell selected by the terminal device changes;

The tracking area TA where the terminal device is located changes;

The terminal device is registered successfully.
The method according to claim 1 or 2 is characterized in that the counter is a shared counter; the shared counter is used to count the sum of the number of times the registration request is re-initiated due to different registration anomalies; when the sum of the times counted by the shared counter is equal to the total preset number threshold, the current registration process of the terminal device is terminated.
The method according to claim 1 or 2 is characterized in that the counter is a counter corresponding to a predetermined registration abnormality; when the counter reaches a cumulative number of times corresponding to the predetermined registration abnormality equal to a preset number threshold corresponding to the predetermined registration abnormality, the current registration process of the terminal device corresponding to the predetermined registration abnormality is terminated.
According to the method of claim 3 or 4, the abnormal registration situation includes at least one of the following:

The non-access stratum NAS layer of the terminal device receives an indication of a failure to send a registration request message from a lower layer;

The NAS layer of the terminal device receives an indication of radio resource control RRC connection suspension from a lower layer;

The NAS layer of the terminal device receives an indication of a failure in the registration completion message;

The NAS layer of the terminal device receives an indication of a registration completion message failure, and the current tracking area identifier TAI of the terminal device changes.
The method according to claim 5, characterized in that terminating the current registration process of the terminal device comprises:

Control the terminal device to no longer initiate a registration request to the network at the current access location, wherein the current access location includes one of the following:

The serving cell currently selected by the terminal device;

The TA where the terminal device is currently located.
The method according to claim 6, characterized in that the method further comprises:

Set the waiting time and start timing;

After the waiting period ends, the terminal device is controlled to re-initiate a registration request and the initial value of the counter is reset to 0.
The method according to claim 6, characterized in that the method further comprises:

Adding the cell identifier of the serving cell currently selected by the terminal device to the first prohibited list, so as to prohibit the terminal device from selecting the serving cell corresponding to the cell identifier in the first prohibited list to initiate a registration request;

When the serving cell currently selected by the terminal device changes, the terminal device is controlled to re-initiate a registration request, the initial value of the counter is reset to 0, and the cell identifier is removed from the first prohibited list.
The method according to claim 6, characterized in that the method further comprises:

Adding the TAI of the TA in which the terminal device is currently located to a second prohibited list, so as to prohibit the terminal device from initiating a registration request when it is in a TA corresponding to the TAI in the second prohibited list;

When the TA currently located by the terminal device changes, the terminal device is controlled to re-initiate a registration request, the initial value of the counter is reset to 0, and the TAI is removed from the second prohibited list.
The method according to claim 6, characterized in that the method further comprises:

Adding the radio access technology RAT currently selected by the terminal device to a third prohibited list, so as to prohibit the terminal device from selecting an access network corresponding to the RAT in the third prohibited list to initiate a registration request;

When the RAT currently selected by the terminal device changes, controlling the terminal device to re-initiate a registration request;

If the registration is successful, the RAT is removed from the third prohibited list, and the initial value of the counter is reset to 0.
The method according to any one of claims 1 to 10 is characterized in that the counter does not count registration anomalies of the emergency call service.
An access exception processing device, characterized in that it is applied to a terminal device side, and the device comprises:

A statistics module is configured to use a counter to count the number of times a registration request is re-initiated due to an abnormality in a current registration process of the terminal device accessing the network;

The determination module is configured to determine whether to terminate the current registration process of the terminal device according to the number of times.
A communication device, comprising: a transceiver; a memory; a processor, connected to the transceiver and the memory respectively, configured to control the wireless signal reception and transmission of the transceiver by executing computer executable instructions on the memory, and capable of implementing the method described in any one of claims 1 to 11.
A computer storage medium, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by a processor, the method according to any one of claims 1 to 11 can be implemented.