RU2786947C1 - Method for anomaly processing during registration in the communication network, equipment, storage media and integrated circuit - Google Patents

Abstract

FIELD: anomaly processing during registration in the communication network.

SUBSTANCE: if in the process of registration in 5G SA communication network an anomaly occurs, terminal station device receives information on the reason for the registration failure and cumulated number of failures to determine whether the condition for early termination of the registration process is met. If the condition is met, the process of registration in 5G SA communication network will terminate early, in addition, there is no need to try again five times as per the protocol and you can quickly return to the LTE communication network to resume services.

EFFECT: solving the problem of frequent registration failures caused by anomalies in the communication network or poor signal conditions in the network registration process.

15 cl, 13 dwg, 4 tbl

Description

The present application claims the priority of Chinese Patent Application No. 202011140963.3, which was filed with the National Intellectual Property Administration of China on October 22, 2020 under the title "METHOD FOR PROCESSING NETWORK REGISTRATION ANOMALY, HARDWARE, STORAGE MEDIA AND INTEGRAL CIRCUIT." STORAGE MEDIUM, AND CHIP"), and which is incorporated herein by reference in its entirety.

The field of technology to which the invention belongs

The present application relates to the field of communication technologies, and in particular, to a method for processing registration anomalies in a communication network, apparatus, information storage medium, and an integrated circuit (chip).

State of the art

Today, if a terminal device registers with a communication network, there may be situations where the terminal device fails to register with the communication network because an anomaly has occurred in the communication between the terminal device and the communication network. If the terminal device fails to register with the communication network, the terminal device typically waits for a predetermined timeout interval and then re-initiates the network registration request. If this terminal device still fails to register with the communication network, this terminal device waits for a predetermined amount of time and then tries again. In this way, the terminal device will try several times (for example, the maximum number of registration attempts is 5). After the number of registration failures of the terminal device reaches the predetermined maximum number of registration attempts, the terminal device will no longer initiate a registration request in the communication network for a certain period of time and initiate a registration request in other communication networks to resume service. It can be understood that if an anomaly always exists when the terminal device attempts to register with the communication network, since several registration attempts are made, the registration procedure is time-consuming so that services cannot be resumed quickly, which adversely affects the user's quality of service. services.

The essence of the invention

Embodiments of the present application provide a communication network registration anomaly handling method, an apparatus, an information storage medium, and an integrated circuit (chip) that can solve the problem of frequent registration failures due to communication network anomalies or poor signal conditions during network registration. .

According to the first aspect, a method for handling anomalies during registration in a communication network is proposed, comprising: initiating, by a terminal device, an M-th registration request to a standalone (standalone, SA) fifth generation (5 ^th generation, 5G) communication network, where M is a positive integer the number is less than N and N is the given integer; if the M-th registration attempt fails, obtaining by the terminal device information about the reasons for the failure of the M-th registration attempt and the cumulative number M of failures; and if the failure reason information of the Mth registration attempt matches the first predetermined reason information and the cumulative number M of failures is not less than the first predetermined number of failures corresponding to the first predetermined failure reason information, the terminal device executes the first processing policy corresponding to the first predetermined information about the reasons where this first processing policy contains: stopping the initiation of a registration request to the 5G SA communication network and initiating a registration request to a second communication network other than the 5G SA communication network. The first predetermined cause information is used to indicate any one of the following: registration failure due to link establishment failure, registration failure due to link release (break) after establishment, registration failure due to no response from 5G network Link SA, registration failure due to registration denied from 5G SA link network.

According to the above technical solution, if an anomaly occurs during registration in the communication network, the terminal device can obtain information about the reason for registration failure and the cumulative number of failures to determine whether the condition for early (compared to the provisions of the protocol) termination of registration is satisfied. If this condition is met, the registration procedure ends early, so that it is not necessary to retry several times according to the protocol, but it is possible to register with another communication network to quickly resume services at that moment. Therefore, according to the technical solution of the present application, the abnormal registration procedure can be completed ahead of schedule (earlier than required by the protocol), and registration can be performed in another network if an anomaly occurs during registration in the network, in order to reduce the time when the registration anomaly occurs, and thereby solving the problem of frequent registration failures due to an anomaly occurring in the network or poor signal conditions during registration with the communication network, and improving service provision to the user.

In some possible implementations, the second communication network is a communication network according to the long term evolution (LTE) standard, and if the mobile phone fails to register in the 5G SA communication network several times consecutively, if it is determined that the current registration anomaly scenario satisfies the condition of early completion of registration attempts according to the registration failure reason information and the cumulative number of failures, the mobile phone stops initiating registration requests to the 5G SA network, and may at this time initiate transmission of the registration request to the LTE communication network. Therefore, according to the communication network registration anomaly handling method proposed in the present application, the mobile phone can quickly terminate the registration procedure in the 5G SA communication network if a registration anomaly occurs and return to the LTE network for registration, thereby reducing the time span affected by the registration anomalies. , and improving the provision of services to the user.

The M number may be 1, 2, 3, or 4. If the M number is 1, the terminal device initiates the first (in other words, initial) registration request to the 5G SA communication network. If the number M is greater than 1 and less than 5, before the terminal device initiates the M-th registration request to the 5G SA communication network, this terminal device experiences registration failure to the 5G SA communication network successively M-1 times. For example, if M is 2, the terminal device initiates a second registration request to the 5G SA communication network after the first registration to the 5G SA communication network fails.

In some possible implementations, if the number M is greater than 1 and less than N, before the terminal device initiates the Mth registration request to the 5G SA communication network, the terminal device fails to register to the 5G SA communication network successively M-1 times.

In some exemplary embodiments, the method further comprises: counting, by the terminal device, each time the terminal device experiences a registration failure with the 5G SA communication network, and accumulating a cumulative number of failures M in the event of an Mth registration failure.

In some possible implementations, after receiving, by the terminal device, information about the cause of the M-th registration failure and the cumulative number M of failures, the method further comprises: initiating, by the terminal device, an (M+1)-th registration request to the 5G communication SA network after the first waiting time interval if the M-th failure cause information does not match the first specified information, or if the M-th failure cause information matches the first specified cause information and the cumulative number M of failures is less than the first specified number of failures.

In some possible implementations, upon initiation, by the terminal device, of the (M+1)th registration request to the 5G SA communication network after the first timeout interval, the method further comprises:

if the terminal device fails to register with the 5G communication SA network for the (M+1)th time, obtaining by the terminal device information about the reason for the (M+1)th registration failure and the cumulative number M+1 of failures; and

if the reason information of the (M+1)th failure corresponds to the second predetermined cause information, and the cumulative number M+1 of failures is not less than the second predetermined number of failures corresponding to the second predetermined cause information, the terminal device executes the first processing policy corresponding to the second given information about the causes.

In some possible implementations, the procedure for stopping, by a terminal device, initiating a registration request to a 5G SA communication network, comprises: prohibiting, by a terminal device, initiating a registration request to a 5G SA communication network within a first predetermined penalty time interval corresponding to the first predetermined cause information. This first predetermined penalty time interval is greater than the first waiting time interval.

In some exemplary embodiments, after prohibiting, by the terminal device, initiating a registration request to a 5G SA communication network within a first predetermined penalty time interval, the method further comprises, initiating, by the terminal device, a registration request to a 5G SA communication network after the expiration of the first predetermined penalty interval. time.

In some possible implementations, before the terminal device initiates a registration request to the 5G SA communication network after the expiration of the first predetermined penalty time interval, the method further comprises: receiving, by the terminal device, command information transmitted by the 5G SA communication network or the second communication network, where this command information is used as a command to initiate a registration request to the 5G SA communication network.

In this case, the procedure for initiating, by the terminal device, the registration request to the 5G communication SA network comprises: initiating, by the terminal device, the registration request to the 5G communication SA network according to the command information.

In some possible implementations, after the terminal device initiates the 5G SA communication network registration request, the method further comprises: prohibiting, by the terminal device, initiating the 5G SA communication network registration request within a second predetermined penalty time interval if the terminal device failed register with the 5G communication SA network for consecutive M times, and if the registration failure reason information for the Mth consecutive time matches the first given cause information.

The second predetermined penalty time interval is greater than the first predetermined penalty time interval.

In some possible implementations, the method further comprises: pre-storing, by the terminal device, at least one match, where the combination of these at least one match contains a first match and a second match, the first match is a match between the first given cause information, the first predetermined number of failures and the first processing policy, and the second match is the correspondence between the second predetermined cause information, the second predetermined number of failures and the first processing policy.

If the M-th registration failure reason information matches the first predetermined reason information, the method further comprises: determining, by the terminal device, that the first predetermined number of failures corresponds to the first predetermined cause information according to the first match.

In some possible implementations, the procedure for initiating, by a terminal device, a registration request to a second communication network other than the 5G SA communication network comprises: searching, by the terminal device, for at least one available communication network other than the 5G SA communication network in question, where this the set of at least one available communication network contains the second communication network, and the quality of the received reference signal from the second communication network belonging to this set of at least one available communication network is optimal; and initiating, by the terminal device, a registration request to the second communication network.

According to a second aspect, the present application provides an apparatus for handling registration anomalies. The apparatus is configured to carry out the method according to the first aspect, or any possible implementation of the first aspect. In particular, the hardware may include modules configured to implement the method according to the first aspect, or any possible variant of the first aspect.

According to a third aspect, the present application provides an apparatus for handling registration anomalies. This apparatus comprises: a processor, this processor is connected to a storage device, this storage device is configured to store a computer program or instructions, and the processor is configured to execute a computer program or instructions stored in the storage device, so that the method according to the first aspect is carried out.

For example, the processor is configured to execute a computer program or instructions stored in a storage device such that the apparatus implements the method according to the first aspect.

As an option, the hardware contains one or more processors.

As an option, the hardware may also include a storage device coupled to the processor.

As an option, the apparatus may contain one or more storage devices.

As an option, the storage device may be integrated with the processor or may be provided separately.

As an option, the apparatus may further comprise a transceiver.

According to a fourth aspect, a computer-readable storage medium is provided. This computer-readable storage medium stores a computer program (which may also be referred to as an instruction or code) for carrying out the method according to the first aspect.

For example, when executing a computer program, the computer implements the method according to the first aspect. The computer may be a communications equipment.

According to the fifth aspect, the present application provides an integrated circuit (chip) containing a processor. The processor is configured to read and execute a computer program stored in the storage device for implementing the method according to the first aspect or any of the possible implementations of the first aspect.

Optionally, the integrated circuit further comprises a storage device, and the processor is connected to this storage device via a circuit or a wire.

Additionally, as an option, the integrated circuit also contains a communication interface.

According to the sixth aspect, the present application provides a computer program product. This computer program product contains a computer program (also referred to as an instruction or code), so that when the computer program is executed, the computer performs the method according to the first aspect. A computer is a communications equipment.

Brief description of the drawings

Fig. 1 is a simplified diagram of the architecture of a communication system according to one embodiment of the present application.

Fig. 2 is a simplified diagram of the interaction between a terminal device and a communication network in a communication system according to one embodiment of the present application.

Fig. 3 is a simplified flow diagram of a method for handling registration anomalies in a communication network in the prior art.

Fig. 4 is a simplified flow diagram of a method for handling registration anomalies in a communication network according to one embodiment of the present application.

Fig. 5 is a simplified diagram of the system's protocol stack architecture.

Fig. 6 shows a simplified signaling interaction diagram for a terminal device and a communication network to establish a radio link.

Fig. 7 is a simplified logic diagram of another method for handling registration anomalies in a communication network according to one embodiment of the present application.

Fig. 8 shows a simplified logic diagram of a method for handling registration anomalies in a communication network according to one embodiment of the present application, applicable to a scenario where registration failure is caused by a communication link failure.

Fig. 9 is a simplified flow diagram of a method for handling registration anomalies in a communication network according to an embodiment of the present application applicable to a scenario where registration failure is caused by random access failure.

Fig. 10 is a simplified flow diagram of a method for handling registration anomalies in a communication network according to one embodiment of the present application, applicable to a scenario where registration failure is caused by a release (disconnection) of a communication channel.

Fig. 11 is a simplified diagram of the interaction between a terminal device and a communication network in a communication system according to one embodiment of the present application applicable to a communication system.

Fig. 12 is a simplified block diagram of an apparatus for processing a registration anomaly in a communication network according to one embodiment of the present application.

Fig. 13 is a simplified block diagram of a communication apparatus according to one embodiment of the present application.

Description of options

In order to make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the options that will be described here are only part, but not all of the options of the present application. Based on the options considered in this application, all other options that can be obtained by a person skilled in the art without any significant creative effort will fall within the protection scope of this application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as the global system for mobile communications (GSM), code division multiple access (CDMA) system, broadband code division multiple access (CDMA) system, wideband code division multiple access (WCDMA), general packet radio service (GPRS), long term evolution (LTE), frequency division duplex (FDD) LTE , LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX), future 5G system or the New Radio (NR) system.

A terminal device is a device that provides a user with voice and/or communication for sending and receiving data, and in particular is a device that provides a user with voice communication, or a device that provides a user with a connection for sending and receiving data, or a device , which provides the user with both a voice connection and a data connection. This terminal device may comprise, for example, a hand-held device having a radio function or a processing device connected to a radio modem. The terminal device may communicate with the backbone network device using a radio access network (RAN) device and exchange voice messages and/or data with the RAN. The terminal device may be a user equipment (user equipment, UE), a radio terminal device, a mobile terminal device, a terminal device for inter-machine communication (device-to-device, D2D), a terminal device for installation on a vehicle (vehicle to everything, V2X) , terminal device for machine type communications (machine-to-machine /machine-type communications, M2M/MTC), terminal devices for the Internet of things (Internet of things, IoT), subscriber unit, subscriber station , mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent ) or user device (user device) or other similar device. For example, a terminal device may be a mobile phone (also referred to as a "cellular phone"), a computer with a mobile terminal device, or a portable, handheld, handheld, or computer-embedded mobile apparatus. For example, a terminal device may be a device such as a personal communication service (PCS) telephone, a cordless telephone, a Session Initiation Protocol (SIP) telephone, a wireless local loop (WLL) station, or personal digital assistant (PDA). The terminal device may further be a device with limited functionality, such as a device with low power consumption, or a device with limited memory capacity, or a device with limited computing power. For example, the terminal device may be an information reader such as a barcode identification device, radio frequency identification (RFID), sensor, Global Positioning System (GPS) device, or laser scanner.

In one embodiment of the present application, the terminal device may further be a relay. Alternatively, it can be understood that any device capable of transmitting and receiving data communication with a base station may be considered a terminal device.

In one embodiment of the present application, the hardware configured to perform the functions of a terminal device may be a terminal device, or may be hardware capable of supporting the terminal device in performing these functions, such as an integrated circuit system, and this hardware may be installed in the device. terminal. In embodiments of the present application, an integrated circuit system may comprise one integrated circuit (chip) or an integrated circuit (chip) and another discrete device. The technical solutions proposed in the embodiments of the present application are described using an example in which the equipment configured to perform the functions of the terminal is a terminal device.

The network device in the embodiments of the present application may be a device capable of performing a random access function for a terminal device, or an integrated circuit (chip) that can be installed in this device. The device can be, but is not limited to: an evolved Node B (evolved Node B, eNB), a radio network controller (RNC), a Node B (Node B, NB), a base station controller, BSC), base transceiver station (BTS), home base station (home evolved NodeB, or home Node B, HNB), baseband unit (BBU), access point (AP) in a wireless system wireless fidelity (WIFI), radio relay node, radio transit node, transmission point (TP) or transceiver point (transmission and reception point, TRP), or other similar device, or may be a fifth generation communication system device ( the fifth generation, 5G), for example, a 5G base station (gNB) or transceiver point (TRP or TP) in the New Radio (new radio, NR) system, one or a group of antenna panels (containing several antenna panels) base station in a 5G system, or may be a communication network node constituting a gNB node or a transmitting point such as a video band unit (BBU), a distributed unit (DU). The 5G base station may be a macro base station, a micro base station, a relay station, an access point, or the like in various forms. In systems using different radio access technologies, the names of devices that have the functions of a base station may be different.

In some deployments, a gNB node may contain a centralized unit (CU) and a distributed unit (DU). The gNB node may further comprise an active antenna unit (AAU). The CU module implements some gNB host functionality and the DU implements some gNB host functionality. For example, the CU is responsible for executing the protocol and non-real-time services, and performing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU module is responsible for executing the physical layer protocol and real-time services, and performing the functions of the radio link control (RLC), media access control (MAC) and physical layer (physical, PHY) layers. The AAU module implements some physical layer processing functions, as well as functions related to high-frequency signal processing and an active antenna. Since the RRC control layer information eventually becomes PHY layer information or information converted from PHY layer information, in such an architecture, higher layer signaling, such as RRC control layer signaling, can also be considered information transmitted by a DU, or transmitted by a pair of DUs. +AAU. It can be understood that a network device may be a device containing one or more nodes from the groups - a CU module node, a DU module node, and an AAU module node. In addition, the CU can be divided into a network device in the RAN network or a network device in the core communication network o (core network, CN). In the present application, this is not limited.

To facilitate understanding of embodiments of the present application, a number of terms used in these application variants are described below in order to assist those skilled in the art in achieving the best understanding.

1) SA communication network: Autonomous communication network, which means a newly built 5G communication network, including a new base station, a backhaul and a backbone communication network. By introducing a new network element and interface, the communication network SA also adopts new technologies such as communication network virtualization and large-scale software-defined communication network, and combining with 5G NR technology. In addition, the technical challenges associated with protocol design, network planning and deployment, and interoperability with the communication SA network will outstrip those of 3G and 4G systems.

Compared to the communication network SA, there are also non-standalone communication networks, namely 5G NSA (non-standalone) networks, the deployment of which comprises the deployment of a 5G communication network using the existing 4G network infrastructure. The 5G network carrier based on the non-autonomous (NSA) network architecture only carries user data, and the control signaling of this 5G carrier is still transmitted through the 4G network.

2) Registration in the communication network

In order to receive a service provided by a communication network, the terminal device first needs to register with the communication network, in other words, register to access the communication network. In general, registration in a communication network can be divided into two types:

(a) Initial registration: The initial registration procedure starts when the power of the terminal device is turned on. For example, assuming that the terminal device is currently in the 5G SA communication network, after power-on, the terminal device initiates registration with the 5G SA communication network to perform initial registration.

(b) Mobile registration update (also called mobile registration): If the terminal device leaves the area where it is currently registered (current registration area) and enters a new tracking area (TA), the mobile registration update procedure is started. For example, if the terminal device moves from the LTE communication network where it is currently registered to the 5G SA communication network, this terminal device initiates registration with the 5G SA communication network to perform mobile registration renewal.

It should be noted that the above example lists two types of registrations in the communication network. Options of the present application do not limit the type of registration in the communication network. It can be understood that, when actually implemented, the registration procedure in the communication network may be some other type of procedure for registering in the communication network, such as periodic registration. The periodic registration can be started by a periodic timer T3512 signaling from the communication network side, so that when the periodic timer expires, the periodic registration procedure is started. This type of registration is similar to the heartbeat mechanism, the purpose of which is to notify the network that the terminal device is still operating in the service area.

(a) in FIG. 1 is a simplified diagram of the architecture of a communication system according to one embodiment of the present application. The communication system shown in Fig. 1 may include a terminal device 01 and a communication network SA 02. As an example, the communication network SA 02 may comprise an access network device (eg, a gNB node) and a backbone communication network device (eg, a 5G backbone network device designated as 5GC). Accordingly, the communication network SA may be referred to as a 5G communication network SA. A radio link can be established between the terminal device 01 and the 5G communication network SA 02, so that the communication network SA can provide communication services to the terminal device 01. The terminal device 01 first needs to initiate a registration request to the 5G communication network SA 02, and this device can obtain authorization to access the service provided by the 5G communication network SA 02 only after successful registration. It should be noted that FIG. 1 offers an illustrative description using a terminal device, an access network device, and a communication backbone device as an example. It may be understood that embodiments of the present application may be applied to a communication system comprising one or more access network devices, or may be applied to a communication system comprising one or more terminal devices. In the present application, this is not limited.

It should be noted that, as shown in FIG. 2, the terminal device 01 initiates a registration request to the 5G communication network SA 02. Specifically, the terminal device transmits a registration request message to a communication network element device (eg, a RAN network device such as a gNB) in the 5G communication network SA 02. After receiving the registration request, the communication network element device may receive a REGISTRATION ACCEPT message or a REGISTRATION REJECT message to the terminal device 01. A detailed description of the signaling interaction between the devices of the communication network elements after the communication network receives the registration request message is given in the relevant technical sources and will not be repeated here.

The result of the registration procedure of the terminal device in the communication network may be the success or failure of the registration.

As an example, after the terminal device transmits a registration request message to the communication network SA, if the terminal device receives the registration accept message returned by the communication network SA, the terminal device is considered to have successfully registered with the communication network SA. This is a normal registration scenario for a communication network.

As another example, if the terminal device receives a Registration Deny message returned from the communication network SA, or this terminal device does not receive a Registration Response message (whether a Registration Accept message or a Registration Deny message) within a predetermined time interval after transmission SA registration request message (one of the protocols uses a T3510 timer of 15 seconds), or an anomaly occurs in the downstream link, the terminal device registration fails. This is a scenario of an anomaly in registration in a communication network.

As shown in part (a) in FIG. 1, the terminal device 01 initiates registration (initial registration or mobile registration renewal) with the communication network SA 02. As shown in part (b) in FIG. 1, the terminal device 01 failed to initiate registration with the communication network SA 02, in other words, an anomaly occurred when registering with the communication network. For such an anomaly in registration, the corresponding technique proposes a registration processing policy: if registration with the network fails, the terminal device accumulates the number of registration attempts (registration attempts counter). If the number of registration attempts is less than 5, the terminal device starts timer T3511 (10 seconds), and after timer T3511 expires, the terminal device initiates registration with the communication network SA again (this is also called initiation of registration with the communication network SA). If the number of registration attempts is 5, the terminal device starts timer T3502 (12 minutes by default), and does not initiate a registration request to the communication network SA within this time period. It should be noted that the details of this anomaly handling policy can be found in the descriptions of Sections 5.5.1.2.7 and 5.5.1.3.7 of Protocol 24.501, where the method of handling, on the terminal device side, the situation when the communication core does not respond to a registration request or when an anomaly occurs in the lower layer communication channel during the initial registration process and during the mobile registration process in the communication network SA, is described in detail.

For example, in FIG. 3 is a simplified flow diagram of a method 200 for handling an anomaly in a registration in a communication network used in the prior art. Method 200 may be applied to the communication system shown in FIG. 1. As shown in FIG. 3, method 200 may comprise the following steps S201 to S210. It should be noted that, for convenience of description, the number of registration attempts is indicated by a counter below.

S201. The terminal device initiates registration with the communication network SA (denoted as the first registration attempt).

For example, when the terminal device transmits a registration request to the communication network SA, this terminal device may start timer T3510, for example, the set duration is 15 seconds, and determine whether the registration is successful according to whether a response message is received within this set time. duration. It should be noted that the timer T3510 is started every time the terminal device initiates a registration request to the communication network SA.

On the one hand, if the terminal device receives the registration acceptance message fed back from the communication network SA within 15 seconds after transmission of the registration request, the terminal device has successfully registered. On the other hand, if the terminal device does not receive the registration request response message within 15 seconds after the transmission of the registration request (for example, the backbone network in the communication network SA does not respond to the registration request and timer T3510 has expired accordingly), the registration of the terminal device fails. . Therefore, the registration failure scenario is called the timer T3510 timeout scenario. Of course, registration failure can also be caused by other reasons, such as registration failure due to low layer link failure, and then registration failure due to low layer link failure can be referred to as a low layer link failure scenario.

S202. If registration fails, the terminal device accumulates in counter 1 (counter=1) and starts timer T3511.

Timer T3511 is set to 10 seconds.

S203. When timer T3511 expires, the terminal device again initiates registration with the communication network SA (referred to as a second registration attempt).

S204. If registration fails, the terminal device accumulates counter 2 (counter=2) and starts timer T3511.

For example, the terminal device may determine whether the registration was successful according to whether the response message was received within the set duration of timer T3511. On the one hand, if the terminal device receives the registration acceptance message returned as feedback by the communication network SA within 10 seconds after transmission of the registration request, this terminal device is successfully registered. On the other hand, if the terminal device did not receive the registration request response message within 10 seconds after the transmission of the registration request (for example, the backbone network device in the communication network SA did not respond to the registration request), registration of the terminal device failed.

S205. When timer T3511 has expired, the terminal device initiates registration with the communication network SA (referred to as the third registration attempt).

S206. If registration fails, the terminal device accumulates counter 3 (counter=3), and starts timer T3511.

For a description of the procedure for determining whether the registration procedure of the terminal device has succeeded or failed, refer to the details of registration success and registration failure in the above description of step S204, which will not be repeated here.

S207. When the timer T3511 has expired, the terminal device again initiates registration with the communication network SA (referred to as the fourth registration attempt).

S208. If registration fails, the terminal device accumulates counter 4 (counter=4), and starts timer T3511.

For a description of the procedure for determining whether the registration procedure of the terminal device has succeeded or failed, refer to the details of registration success and registration failure in the above description of step S204, which will not be repeated here.

S209. If timer T3511 expires, the terminal device initiates registration with the communication network SA again (referred to as the fifth registration attempt).

S210. If registration fails, the terminal device accumulates into a counter (counter=5), and starts timer T3502.

For a description of the procedure for determining whether the registration procedure of the terminal device has succeeded or failed, refer to the details of registration success and registration failure in the above description of step S204, which will not be repeated here.

The duration corresponding to timer T3502 is 12 minutes by default. The terminal device does not register with the SA network again within this duration. At this time, the terminal device may initiate registration with other communication networks. When the timer T3502 expires, the terminal apparatus may determine whether to initiate registrations in the communication network SA again, according to the actual situation. If the terminal device initiates registration with the communication network SA again, the specific registration procedure is still carried out in accordance with the above registration procedure in steps S201 to S210.

The registration anomaly described above may be caused by the expiration of timer T3510 during initial registration or mobile registration in the communication network SA (eg, the backbone network device does not respond to the registration request), or may be caused by a failure at a lower level. For example, the following table 1 shows known techniques for handling the situation when an anomaly occurs during the registration process. As shown in Table 1, in the above prior art, when an anomaly occurs in the process of registering with the communication network SA, the terminal device must wait 10 seconds and then re-initiate the registration according to the protocol. If an anomaly still occurs during the registration retry process, the terminal device must wait another 10 seconds and try again. The maximum number of retries is 5, so the SA communication network registration procedure can only be completed after 5 failures, which takes more than 40 seconds. During this period, the terminal device is in the waiting state in the communication network SA, in other words, regardless of the reason for the registration failure, the terminal device will continue to try to register in the communication network SA after waiting for a period of time while the registration remains unsuccessful. Therefore, in a situation where an anomaly always occurs when the terminal device initiates registration in the communication network SA, the registration procedure takes a long time so that services cannot be quickly resumed.

Table 1

no. Reason for registration failure Scenario provided in relevant protocols Situation Processing Method in Known Related Technique one Low level failure Low level failure The terminal device accumulates the number of registration failures. If the number of failures is less than 5, the terminal device starts timer T3511 (10 seconds), and initiates registration again when the timer expires. If the number of failures becomes 5, the terminal device starts timer T3502 (12 minutes by default), and does not initiate a registration request with the communication network SA for a period of time. 2 No response from backbone network Timer T3510 expired

In light of this, one embodiment of the present application proposes a method for handling network registration anomalies. The method can be applied to the communication system shown in FIG. 1, and can solve the problem of frequent registration failures in the communication network due to anomalies in the communication network or poor signal conditions in the registration process in the communication network SA, so as to leave this communication network earlier and return to the LTE communication network for registration, thereby reducing the length of the time period affected by registration anomalies and improving the service user experience.

According to the communication network registration anomaly handling method proposed in the present embodiment of the present application, if an anomaly occurs in the process of registration with the communication network SA, the terminal device obtains registration failure reasons and the cumulative number of failures to determine whether the condition for early completion of the procedure is satisfied. registration. If this condition is satisfied, the registration procedure in the SA communication network is completed early, and it is not necessary to retry five times according to the protocol, but it is possible to quickly return to the LTE communication network to resume services. The condition for early completion of registration is that the current registration failure reason information is the specified cause information (cause), and the current number of registration attempts (also called the cumulative failure number) is not less than the specified number (n) corresponding to the specified registration information. reasons. The parameters cause and the number n can be flexibly specialized. This predetermined cause information includes, but is not limited to, link setup failure, random access failure, RRC control link disconnection from the network, timer T3510 expiration, and a registration rejection message by the communication network in the registration process. The following describes in detail the method of processing the registration anomaly in the communication network according to the present embodiment of the present application with reference to the accompanying drawings.

In FIG. 4 is a flowchart for processing a registration anomaly in a communication network according to one embodiment of the present application. This method is applied to the communication network shown in FIG. 1. As shown in FIG. 4, method 300 may comprise the following steps S310 to S350.

S310. The terminal device initiates the M-th registration request to the 5G SA communication network.

Here, M may be a positive integer less than N, and N may be a given integer. Optionally, the number N may be negotiated by the terminal device and the 5G SA communication network, or provided by the protocol (for example, N may be equal to 5). In the present application, this is not limited. For convenience of description, the following uses the number N equal to 5 as an example to illustrate the description.

As an example, assuming N=5, M may be 1, 2, 3, or 4. If M is 1, the terminal device initiates the first (in other words, initial) registration request to the 5G communication SA. If M is greater than 1 and less than 5, before the terminal device initiates the M-th registration request to the 5G SA communication network, the terminal device fails to register to the 5G SA communication network for a consecutive M-1 times. For example, if M is 2, the terminal device initiates a second registration request to the 5G SA communication network after the first attempt to register to the 5G SA communication network fails. If M is 3, the terminal device initiates a third registration request to the 5G SA communication network after registration attempts to the 5G SA communication network have failed two consecutive times. If M is 4, the terminal device initiates a fourth registration request to the 5G SA communication network after registration attempts to the 5G SA communication network have failed three consecutive times.

It should be noted that in this embodiment of the present application, the terminal device initiates a registration request to the 5G communication SA network, which is actually implemented by sending a registration request message to the 5G network SA network element device. In other words, the communication network registration procedure comprises a signaling interaction between a terminal device and a communication network element (such as a gNB node or an access and mobility management function (AMF) network element). For ease of reference, some descriptions of a specific signaling interaction between a terminal device and a communication network element are omitted below.

S320. In case of failure of the M-th registration attempt, the terminal device receives information about the reasons for the failure of the M-th registration attempt and the cumulative number M of failures.

In the exemplary embodiment of the present application, the cumulative number of failures M is a number obtained by cumulating the number of failures if the terminal device fails to register M successive times. It can be understood that the terminal device counts another one every time the terminal device fails to register with the 5G SA communication network, and accumulates these ones to obtain a cumulative failure number of 1 after the first failure time. By analogy, after the (M-1)th registration failure, a cumulative number of M-1 failures are accumulated. After the M-th registration failure, a cumulative number of M failures is accumulated. This cumulative number M of failures may also be referred to as the number of registration attempts.

For example, if M is 1 when the first registration attempt fails, the terminal device can obtain information about the reason for the failure of the first registration attempt and the cumulative number of failures equal to 1.

As another example, if M is 2, if the first and second registration attempts fail, the terminal device can obtain information about the reason for the failure of the second registration attempt and a cumulative number of failures equal to 2.

As another example, if M is 3, if three consecutive registration attempts fail, the terminal device can obtain information about the reason for the failure of the third registration attempt and a cumulative number of failures equal to 3.

As another example, if M is 4, if four consecutive registration attempts fail, the terminal device can obtain information about the reason for the failure of the fourth registration attempt and a cumulative number of failures equal to 4.

In some embodiments, during the process of registering a terminal device with a 5G communication SA network, the terminal device may, in some scenarios, update the current cumulative number of failures to zero. The set of specific implementation options for cumulative failure cleanup includes, but is not limited to, the following two ways:

Method 1: If the terminal device successfully registers with the 5G SA communication network, this terminal device can update the current cumulative number of failures to zero.

Method 2: If the terminal device is turned off or switched to flight mode, that terminal device may update the current cumulative number of failures to zero, making it equal to zero.

Optionally, the reason for the M-th registration failure may be that the 5G SA communication network (such as the core communication network) did not respond to the registration request and the registration failed, or it could be that the 5G SA communication network (such as the core network) returns a registration denied message, so the registration has failed. The registration failure may also be caused by a low-level failure of the terminal device, or may be caused by some other possible cause, which can be determined according to actual applications. In the embodiments of the present application, this is not limited. Various cases are possible in which registration failure is due to a low-level failure of the terminal device, for example, registration failure due to failure to establish a communication channel, registration failure due to release (disconnection) of the communication channel after establishment, or some other possible situation, which can be determined according to actual applications. In the embodiments of the present application, this is not limited.

In FIG. 5 is a simplified diagram of the system's protocol stack architecture. For ease of description, only a few levels related to the present technical solution will be considered here. As shown in FIG. 5, the protocol stack architecture of the system comprises, from top to bottom, a non-access stratum (NAS), an RRC control layer, a PDCP protocol layer, an RLC control layer, a MAC control layer, and a physical layer (PHY). For ease of description, the NAS layer layer is referred to as the upper layer, and the RRC control layer, PDCP protocol layer, RLC control layer, MAC control layer, and PHY layer are collectively referred to as lower layers. As noted in this context, a lower layer link failure or low layer anomaly may mean that the anomaly originated in one of the layers such as the RRC control layer, the PDCP protocol layer, the RLC control layer, the MAC control layer, and the PHY physical layer, or may mean that the anomaly has arisen at several low levels.

As an example, the following Table 2 lists a number of reasons that can cause a terminal device to fail to register with a communication network, and the scenarios provided in the protocol corresponding to these reasons. As shown in Table 2, the set of reasons related to registration failure can include the following four items: (1) Reasons related to the failure to establish a communication channel (in other words, registration failure due to the failure to establish a communication channel), such as link failure, suspension due to switching between systems, random access failure, and loss of communication network. (2) Causes related to the release (disconnection) of the communication channel (in other words, registration failure due to the release (disconnection) of the communication channel), such as recovery failure, release (disconnection) of the communication channel, other reasons, redirection from the communication network of the standard NR to the LTE communication network, upper layer anomaly, RRC control anomaly and lowest layer anomaly. (3) No response from the backbone communication network, in other words, registration failure due to no response from the communication network. (4) Registration denied from the backbone during initial registration, in other words, registration failure due to registration denied from the communications network. Failure to establish a communication link and disconnection (release) of the communication link correspond to the failure situations of the lower layers (lower failure) provided in the protocol, and the absence of a response from the core communication network corresponds to the situation in the scenario of the expiration of the timer T3510 (T3510 timeout) provided in the protocol.

table 2

It should be noted that Table 2 also lists a reason for registration failure that is not described in the protocol: registration failure from core communications network (cause #9). Although the registration failure scenario from the communication network (cause #9) during the initial registration process is not described in the protocol, for the actual implementation of this scenario, you can refer to the handling of the situation in the timer expiration scenario T3510 and in the lower level failure scenario.

In FIG. 6 is a simplified flow diagram of a procedure for establishing a radio bearer between a terminal device and a communication network (which may be referred to as link establishment for short). As shown in FIG. 6, the terminal device transmits an RRC control connection establishment request to the communication network, the communication network transmits an RRC control connection establishment parameter to the terminal apparatus, and then the terminal apparatus establishes an RRC control connection in accordance with this RRC establishment parameter. After completing the establishment of the RRC control connection, the terminal device establishes a radio bearer with the communication network.

As shown in FIG. 2, fig. 5 and FIG. 6, the precondition for the terminal device to successfully transmit the registration request message to the communication network is that the radio bearer is successfully established between the terminal device and the radio access network (RAN), and the normal, mainly signaling, communication between the terminal device is carried out over the channel. and the RRC control layer. In other words, in the registration process, the terminal device needs to establish a radio link with the communication network before transmitting the registration request to the communication network. If an anomaly occurs in the RRC control layer, a link establishment failure may occur, further causing registration failure. In addition, before the network responds with a registration accept message, if the radio access network releases (disconnects) the radio channel, the registration will also fail.

In addition, since the random access procedure is a necessary procedure for establishing a radio bearer between the terminal device and the radio access network, only after the completion of the random access procedure can communication between the access network device (base station) and the terminal device normally take place. Only after successful completion of the random access procedure, the terminal device will be able to send an RRC control connection establishment request to the radio access network (RAN). This procedure is mainly represented by the relevant interaction between the RRC control layer and the layers below the RRC control layer. Therefore, if the random access procedure fails, a link establishment failure occurs, causing registration failure.

In this embodiment of the present application, the Mth registration failure reason information received by the terminal device may be radio interface signaling or registration information, which may indicate any one of the above reasons. It should be noted that, for different registration failure reasons, the terminal device obtains registration failure reason information in different ways. In the following, in accordance with the above Table 2, each registration failure reason is described in detail, and an exemplary embodiment of the terminal apparatus for obtaining registration failure reason information corresponding to a particular registration attempt is described.

First, reasons relating to failure to establish a communication link will be given, including failure to establish an RRC radio control bearer in the SA registration process.

1) Link failure: This means that an anomaly occurs in the RRC control layer causing the link establishment to fail. Such an anomaly may occur at any time during the connection establishment process shown in FIG. 6.

In this case, information about the reason for registration failure can be reflected in the log content generated during the registration process. For example, in the process of registering with the communication network SA, if the terminal device fails to establish a communication channel, the RRC control layer responds with a communication failure message transmitted by the NAS layer layer, and records an interaction message to generate log content, from which it can be learned, that the link establishment failure is caused by the RRC control connection establishment failure. Accordingly, the terminal device can obtain registration failure reason information from the content of the log.

2) Suspension due to switching between systems: This means that the terminal device switches from the SA communication network system to another system (such as the LTE communication network) in the process of establishing a communication channel, the registration procedure in the SA communication network is interrupted, the RRC control connection is necessary suspend, which causes a link establishment failure.

In this case, information about the reason for registration failure can be reflected in the log content generated during the registration process. For example, in the process of registering with a communication network SA, if the terminal device fails to establish a communication channel and is then in other systems (such as an LTE communication network), this phenomenon is recorded to generate registration signal content from which it can be learned that the suspension is due to for switching between systems causes a failure to establish a communication channel. Accordingly, the terminal device can obtain registration failure reason information from the log content.

3) Random access failure: It means the failure of the random access procedure in the link establishment process, which causes the link establishment failure.

In this case, information about the reason for registration failure can be reflected in the log content generated during the registration process. For example, in the process of registering with the communication network SA, the message relating to random access in the process of establishing a communication channel by the terminal device may indicate a random access failure, or the message of the random access procedure is incomplete. These messages or events are recorded to generate log content from which it can be understood that a random access failure causes a link establishment failure. Accordingly, the terminal device can obtain registration failure reason information from the log content.

4) Communication network loss: This means that the signal quality in the communication network does not satisfy the residency condition in the communication link establishment process, and a communication network loss occurs, causing the communication link establishment to fail.

In such a case, information about the reason for registration failure can be reflected in the content of the logbook at the entrance of the registration procedure. For example, during the process of registering with the communication network SA, the terminal device failed to establish a communication channel, and the signal quality in the communication network SA is below the threshold level, which does not satisfy the residence criterion. This is recorded to generate log content, from which it can be known that the loss of the communication network causes a failure to establish a communication link. Accordingly, the terminal device can obtain registration failure reason information from the content of the log.

Secondly, the set of reasons related to the release (disconnection) of the communication channel contains reasons related to the fact that the RRC control bearer is released (disconnected) after this radio control bearer RRC was successfully established in the registration process in the communication network SA.

5) Restoration failure: This means a link recovery failure if the RRC control channel transitions from the inactive state (RRC_INACTIVE) to the connected state (RRC_CONNECTED), which causes the link to be released (disconnected).

This scenario can be observed from the signaling of the radio interface. During registration with the communication network SA, if the RRC control channel is in the idle state, the terminal device does not transmit an RRC resume request message or an RRC resume complete message.

6) Release (disconnection) of the communication channel: failure of the connection on the RRC control channel, which causes the release (disconnection) of the communication channel.

This scenario cannot be observed from the signaling of the radio interface, but can be observed from the log or phenomenon: in the process of registration in the communication network SA, after the establishment of the RRC control channel, if in the lower layer below the RRC control layer (such as the RLC control layer, MAC control layer or PHY physical layer) a loss of synchronization or access failure occurs, the link anomaly is reported to the RRC control layer.

7) Other reasons: This means that the communication network voluntarily releases (disconnects) the communication channel before responding to the registration accept message or the registration rejection message after successful establishment of the communication channel.

This scenario can be observed from the signaling of the radio interface. In the registration process with the communication network SA, after the RRC control channel is established, the communication network transmits an RRC Control Release (RRC Release) message, which does not carry information such as suspension or redirection, and directly releases (releases) the RRC control channel.

8) Redirection from NR network to LTE network: This means the release (disconnection) of the communication channel occurs due to redirection from NR network to LTE network.

In this scenario, radio interface signaling can be observed. In the process of registering with the communication network SA, after establishing the RRC control channel, the communication network transmits an RRC Control Release (RRC Release) message, which carries forwarding information to the LTE network.

9) Upper layer anomaly: An anomaly occurs at the NAS layer layer causing the link to be released (disconnected).

This scenario cannot be observed directly from the radio interface signaling, but can be observed from a log or phenomenon: during registration in the communication network SA, after the RRC control channel is established, an anomaly occurs at the NAS layer layer, which instructs the RRC control layer to release ( disconnection) of the RRC control level.

10) RRC control anomaly: An anomaly occurs at the RRC control layer, causing the link to be released (disconnected).

This scenario cannot be directly observed from the signaling of the radio interface, but can be observed from the log or phenomenon: in the registration process of the communication network SA, that after the establishment of the RRC control channel, an anomaly occurs in the RRC control channel, so that the release (disconnection) of the control channel occurs directly RRC.

11) Lower layer anomaly: This means that an anomaly occurs at a lower layer (such as MAC, PDCP or PHY control layers) causing the link to be released (disconnected).

This scenario cannot be observed directly from the radio interface signaling, but can be observed from the log or phenomenon: in the process of registering with the communication network SA after the establishment of the RRC control channel, an anomaly occurs at the lower layer, and this anomaly is reported to the RRC control layer, which causes the release (disconnection) of the RRC channel.

Third, timer T3510 expired: After the terminal device transmitted a registration request message to the communication network, the communication network did not respond with a REGISTRATION ACCEPT or REGISTRATION REJECT message.

Fourth, failure from the core communication network: If the initial request initiated by the terminal device was not correctly received by the communication network, the communication network sends a registration denied message to the terminal device, and this message contains the value of the registration refusal reason. After the terminal device sends a registration request message to the communication network, the communication network sends a registration denied message to the terminal device, and the message contains the value of the registration denied reason. For example, the cause value is #9.

S330. The terminal device determines whether the registration failure cause information of the Mth registration failure corresponds to the first predetermined cause information, and whether the cumulative failure number M is not less than the first predetermined failure number corresponding to the first predetermined cause information.

The above word "corresponds" can be understood as the complete or partial equivalence of information. For example, if the degree of similarity obtained by comparing Information 1 and Information 2 is not less than a predetermined similarity threshold (eg, 80%), the two pieces of information can be considered to be consistent. If the degree of similarity obtained by comparing Information 1 and Information 2 is less than a predetermined similarity threshold, the two pieces of information can be considered inconsistent. In particular, this can be determined in accordance with the actual requirements for use, and this is not limited in this embodiment of the present application.

Optionally, in this embodiment of the present application, the first predetermined cause information may indicate that the registration failure occurred due to the failure to establish a communication channel (or indicates that the communication channel could not be established), or may indicate that the registration failure occurred due to for the release (disconnection) of the communication channel after its establishment (or indicate that the release (disconnection) of the communication channel has occurred). The first predetermined cause information may also indicate that registration failure has occurred due to no response from the 5G SA communication network, or may indicate that registration failure has occurred due to registration failure from the communication network. Alternatively, the first given cause information may indicate any one of the 13 registration failure reasons shown in Table 2 above. To simplify the description, only some of the causes of registration failures are used as examples in the following.

In some embodiments, the terminal device may previously store at least one match, and each such match is a match between a given cause information, a given number of failures, and a processing policy. For example, at least said correspondence is the correspondence between the first specified cause information, the first specified number of failures, and the first processing policy, and the correspondence between the second specified cause information, the second specified number of failures, and the first processing policy. The first processing policy may be that the terminal device stops initiating a registration request to the 5G communication network SA and initiates a registration request to the second communication network. As an example, refer to the match list or the set cause information list in the following Table 3, the match list example shows three matches: if the given cause information indicates a link failure, the corresponding set number of failures is 2, and the corresponding processing policy is the first processing policy; if the predetermined cause information indicates a random access failure, the corresponding predetermined number of failures is 2, and the corresponding processing policy is the first processing policy; and if the predetermined cause information indicates release (disconnection) of the communication channel, the corresponding predetermined number of failures is 1, and the corresponding processing policy is the first processing policy.

Table 3

Preset Cause Information Set number of failures Processing policy Indicates a communication link failure 2 The terminal device stops initiating a registration request to the 5G communication network SA and initiates a registration request to the second communication network Denotes random access failure 2 Indicates the release (disconnection) of the communication channel one

It should be noted that, for ease of description, only three different types of specified cause information and corresponding failure numbers are listed in Table 3 above. It can be understood that, in the actual implementation, the predetermined failure numbers corresponding to these three types of predetermined cause information can be set according to the actual situation. In addition, other predetermined cause information and corresponding failure numbers other than the three types of predetermined cause information can also be set according to the actual situation. This may be negotiated between the terminal device and the communication network, or provided by the protocol. In the present application, this is not limited.

It should further be noted that the above is an example in which, for illustration purposes, there are three different types of predetermined cause information, all of which correspond to the same processing policy. These variants of the present application may further contain the following implementations: different given cause information may correspond to different processing policies. For example, if the given cause information indicates a random access failure, the corresponding processing policy may be that the terminal device stops initiating a registration request to the 5G SA communication network and initiates a registration request to the second communication network. If the given cause information indicates release (disconnection) of the communication channel, the corresponding processing policy may be that the terminal device initiates a registration request to the 5G SA communication network and initiates a registration request to the second communication network. With this approach, the so-called "race" registration is carried out, when registration requests are initiated immediately in both communication networks, and the network in which it was possible to register first is used as a resident communication network.

In some embodiments, the relationship between the predetermined cause information, the corresponding predetermined number of failures, and the processing policy may be predetermined in combination with factors such as the communication network situation, terminal device performance, and service impact, and the relationship may also be adjusted in accordance with changes in the situation in the communication network. As an option, a particular ratio can be comprehensively considered by analyzing a large number of log entries related to problems and taking into account different positions, communication network situations of different equipment vendors, the influence of terminal device services, or other similar factors.

In the above step S330, if the terminal device fails to register, the terminal device may respectively compare the reason information of the M-th registration failure and the cumulative number M of failures with the predetermined cause information and the predetermined number of failures in the above previously stored ratio list for determining whether the reason information of the Mth failed registration attempt corresponds to the first given cause information, and whether the cumulative number M of failures is not less than the first given number of failures corresponding to the first given reason information, in other words, whether the current registration anomaly scenario satisfies condition for early ending registration.

In some embodiments, the terminal device may first determine if the reason information of the Mth registration failure matches the first given cause information, and if the reason information of the Mth registration failure matches the first given reason information, the terminal device determines the first given reason information. the number of failures corresponding to the first given cause information according to the specified first match. The terminal device then compares the cumulative number M of failures with the first predetermined number of failures and determines whether the cumulative number M of failures is not less than the first predetermined number of failures.

If the terminal device determines that the reason information of the M-th failed registration attempt matches the first predetermined reason information, and that the cumulative number M of failures is not less than the first predetermined number of failures corresponding to the first predetermined reason information, in other words, satisfies the early (early) condition ) completion of registration, the terminal device proceeds to the next step S340. Otherwise, the terminal device continues with the next step S350.

S340. The terminal apparatus stops initiating the registration request to the 5G SA communication network and initiates transmission of the registration request to a second communication network other than the 5G SA communication network.

In the exemplary embodiment of the present application, if the Mth registration failure reason information matches the first predetermined reason information, and the cumulative number M of failures is not less than the first predetermined number of failed attempts corresponding to the first predetermined reason information, the terminal device may implement the first processing policy, corresponding to the first given cause information. In other words, if the terminal device fails to register with the 5G SA communication network several times in succession, if it is determined that the current registration anomaly scenario satisfies the registration termination condition according to the registration failure reason information and the cumulative number of failures, the terminal device may temporarily stop the initiation registration request to the 5G communication network SA, and may initiate transmission of the registration request to the second communication network at this time.

In this embodiment of the present application, Table 4 shows the processing methods according to the present application and the processing methods used in the known art in scenarios in which registration failure is caused by various reasons. The number C indicates the cumulative number of failures, for example, C=2 indicates that the cumulative number of failures is 2.

Table 4

As can be seen from Table 4, according to the processing method of the prior art, if an anomaly occurs in the process of registering with the communication network SA, the terminal device needs to wait 10 seconds before re-initiating the registration according to the protocol. If an anomaly still occurs during the registration retry process, the terminal device needs to wait another 10 seconds and try again. The maximum number of attempts is 5, and the SA communication network registration procedure can only be completed after 5 unsuccessful attempts, which takes more than 40 seconds. During this period, the terminal device is idle in the communication network SA, in other words, regardless of the reasons for registration failure, the terminal device will continue to try to register in the communication network SA after waiting for a period of time while registration attempts remain unsuccessful. Contrary to the known art, according to the processing method of the present application, if an anomaly occurs in the process of registering a terminal device with the communication network SA, the terminal device obtains registration failure reason information and a cumulative number of failures to determine whether the condition for early registration is satisfied. (early) completion of registration. If the condition is satisfied, the current round of registration in the communication network SA can be completed earlier. At this time, the terminal device may register with another communication network (LTE communication network) to provide services in order to realize a fast exit.

In light of this, the technical solutions of the present application can solve the problem of frequent failure of registration attempts due to anomalies in the communication network or poor signaling conditions in the registration process in the SA communication network, in order to leave this network earlier and return to the LTE communication network for registration, thus thereby reducing the time affected by registration process anomalies and improving the user experience of the services.

Optionally, the step in which the terminal device initiates a registration request to the second communication network in the above step S340 may be implemented in one of the following two ways:

Method 1: If the terminal device completes registration early and registers with the second communication network after failing to register with the 5G SA communication network, this second communication network may be provided by a protocol or may be negotiated between the terminal device and the 5G SA communication network. In the example in which the second communication network provided by the protocol is an LTE communication network, if the terminal device fails to register with the 5G SA communication network and satisfies the registration early completion condition, the terminal device can register with the LTE network at that time. communications according to the protocol.

Method 2. The terminal device searches for at least one available communication network other than the 5G SA communication network, where this set of at least one available communication network contains the specified second communication network. In addition, the terminal device obtains a quality parameter of the received reference signal from each communication network in said set of at least one available communication network. If the quality of the signal indicated by the quality parameter of the received reference signal from said second communication network of the set of at least one available communication network is optimal, the terminal device initiates transmission of a registration request to this second communication network. In other words, the terminal device may select the communication network with the best signal quality from the plurality of found available communication networks to initiate registration.

Optionally, the quality parameter of the received reference signal may be, but is not limited to, at least one of the following parameters: received signal strength indication (RSSI), received reference signal power (reference signal received power, RSRP) and/or signal-to-noise ratio (SNR).

It should be noted that even if the signal quality in the specified at least one available communication network found by the terminal device is lower than the signal quality in the 5G SA communication network, then as long as the signal quality in the communication network satisfies the minimum signal quality requirements for access to network defined by that communication network, the terminal device may still choose to register with such at least one available communication network.

As an option, in this embodiment of the present application, the second communication network may be an LTE communication network. For example, if the mobile phone fails to register with the 5G SA communication network several times in succession, if it is determined that the current registration anomaly scenario satisfies the early (early) end of registration condition according to the registration failure reason information and the cumulative number of failures, the mobile phone stops initiating a registration request to the 5G communication network SA, and may at that time initiate transmission of the registration request to the LTE communication network. Therefore, according to the communication network registration anomaly handling method proposed in the present application, the mobile phone can quickly leave the 5G SA communication network and return to the LTE communication network for registration, thereby reducing the time affected by the registration anomaly and improving the quality of service for the user.

S350. The terminal device initiates an (M+1)th registration request to the 5G communication SA network after the first timeout interval has elapsed.

In some embodiments, if the Mth registration failure cause information does not match the first predetermined cause information, or if the Mth registration failure reason information matches the first predetermined cause information and the cumulative number M of failures is less than the first predetermined number of failures, the terminal device may initiate transmission of the (M+1)-th registration request to the 5G SA communication network after the first timeout interval has elapsed.

The first timeout interval may be negotiated by the terminal device and the communication network, or provided by the protocol. In the present application, this is not limited. For example, the first timeout interval may be 10 seconds.

In some embodiments, if the current registration anomaly scenario satisfies the condition for an early termination of the registration, this communication network SA can be "penalized", for example, disable some functions of the communication SA network, in other words, do not initiate registration with the communication SA network for some period time. The progressive penalty method can be used, the first penalty interval is T1, the second penalty interval is T2, the third penalty interval is T3, and so on. In this case, T3 > T2 > T1, and the parameters T1, T2 and T3 can be customized according to the requirements. After the duration of the penalty interval has elapsed, the functions for operation in the communication network SA can be restored, and the terminal device specializes a parameter to decide whether to initiate registration with the communication network SA immediately.

In particular, the appropriate length of the penalty interval can be set in advance for the given cause information. Accordingly, if the terminal device satisfies the condition for early termination of registration, the initiation of transmission of the registration request to the 5G SA communication network is suspended within a predetermined penalty time interval. For example, the first predetermined penalty time interval may be set accordingly to the first predetermined cause information. In particular, if the registration failure reason information of the M-th registration failure corresponds to the predetermined reason information, and the cumulative number M of failures is not less than the first predetermined number of failures corresponding to the first predetermined reason information, in other words, the condition for early (early) completion of the registration is satisfied, the terminal device may prohibit initiation of the registration request to the 5G SA communication network within the first predetermined penalty time interval corresponding to the first predetermined cause information.

The first predetermined penalty time interval may be negotiated between the terminal device and the communication network, or provided in a protocol. In the present application, this is not limited. The protocol may provide that the first given penalty time interval must be greater than the first timeout interval. For example, the first predetermined penalty time interval may be 12 minutes.

As an option, different predetermined cause information may be respectively predetermined using different predetermined penalty time intervals. For example, if the predetermined cause information indicates that the registration failure was due to a link failure, the corresponding predetermined penalty time interval may be 12 minutes. If the predetermined reason information indicates that the registration failure occurred due to the release (disconnection) of the communication channel, the corresponding predetermined penalty time interval may be 15 minutes, which can be determined according to the actual usage requirements, and this is not limited in the present application.

According to the network registration anomaly handling method provided in the embodiments of the present application, if an anomaly occurs during registration with a communication network, the terminal device can obtain registration failure reason information and a cumulative number of failures to determine whether a condition for early completion of registration is satisfied. If this condition is met, the registration procedure ends early (early), there is no need to retry several times according to the protocol, and it is possible to register in another communication network to quickly resume services at this moment. Therefore, according to the technical solutions of the present application, when an anomaly occurs in the registration process in a communication network, the abnormal registration procedure can be completed early and can be carried out in another communication network to reduce the time affected by the influence of anomalies in the registration process, thereby solving the problem of frequent failures. registration due to anomalies in the communication network or poor signal conditions in the network and improving the provision of services to the user.

In some embodiments, with reference to FIG. 4 as shown in FIG. 7, after step S350, method 300 may further comprise the following steps S360-S380.

S360. If the terminal device fails to register with the 5G SA communication network for the (M+1)th time, this terminal device obtains information about the reason for the (M+1)th registration failure and the cumulative number M+1 of failures.

For a detailed description of how the terminal device obtains information about the cause of the (M+1)th registration failure and the cumulative number M+1 of failures, the above step S320, in which the terminal device obtains information about the cause of the Mth registration failure, can be referred to. and the cumulative number M of failures. The detailed description will not be repeated here.

S370. The terminal apparatus determines whether the registration failure reason information corresponds to the (M+1)th registration failure of the second predetermined cause information, and whether the cumulative number M+1 failures is not less than the second predetermined failure number corresponding to the second predetermined cause information.

If the (M+1)th registration failure reason information corresponds to the second predetermined reason information, and the cumulative failure number M+1 is not less than the second predetermined failure number corresponding to the second predetermined reason information, the terminal device proceeds to the next step S380. Otherwise, the terminal device may wait to continue registering with the 5G SA communication network, for example, the terminal device may initiate transmission of a registration request to the 5G SA communication network after the first timeout interval.

S380. The terminal device executes the first processing policy corresponding to the second predetermined cause information.

For the description of the second predetermined cause information, the corresponding second predetermined number of failures, and the corresponding first processing policy, reference may be made to the above detailed description of the first predetermined cause information, the corresponding first predetermined number of failures, and the corresponding first processing policy. The detailed description will not be repeated here.

Note that the second predetermined cause information and the first predetermined cause information may be the same or different. In the same situation, the second specified number of failures is equal to the first specified number of failures.

In some embodiments, after the terminal device successfully registers with the second communication network and after the first predetermined penalty time has elapsed, if a certain condition is met, the terminal device may return to the 5G SA communication network for registration. The following example describes three possible implementations.

Method 1: The terminal device can autonomously return to the 5G SA communication network. For example, the protocol may also provide that after the first predetermined penalty time has elapsed, the terminal device may autonomously return to the 5G SA communication network for registration.

Method 2: The 5G SA communication network may instruct the terminal device to return to the 5G SA communication network.

After the first predetermined penalty time interval, the 5G SA communication network may send command information to the terminal device instructing the terminal device to return to the 5G SA communication network. After receiving the command information transmitted by the 5G communication SA network, the terminal apparatus can initiate transmission of a registration request to the 5G communication SA network according to the command information, and this command information is used as an instruction to initiate transmission of the registration request to the 5G communication SA network.

Method 3: The second communication network may instruct the terminal device to return to the 5G SA communication network.

For example, assuming that the terminal device is currently resident in the second communication network, this terminal device collects the quality parameter of the received reference signal from the second communication network and the quality parameters of the received signal from other communication networks (including the 5G SA communication network) in real time, and reports these received signal quality parameters to the second communication network. The second communication network determines the quality of the received reference signal in each communication network according to the quality parameter of the received reference signal in the corresponding communication network, and then determines the communication network in which the terminal device may be suitable to reside. The protocol may provide that the second network instructs the terminal device to return to the 5G SA communication network for registration if the second communication network determines that the quality of the received reference signal in the 5G SA communication network is higher than in the second communication network.

In another example, the protocol may provide that after the first predetermined penalty time has elapsed, the second communication network instructs the terminal device to return to the 5G SA communication network for registration.

In some embodiments, when the terminal device returns to the 5G SA communication network for registration, then if the registration attempt fails for the same reason, the terminal device may increase the duration of the penalty interval. For example, if the terminal device fails to register with the network in the 5G SA communication network for M consecutive times, and the registration failure reason information for the Mth registration failure matches the first set reason information, the terminal device prohibits the initiation of the registration request in the 5G network Communication SA within the second predetermined penalty time interval. The second predetermined penalty time interval is greater than the first predetermined penalty time interval. Optionally, a second predetermined penalty time interval may be negotiated between the terminal device and the 5G communication SA network or provided in the protocol. In the present application, this is not limited.

For example, suppose that the predetermined number of failures corresponding to the first predetermined cause information is 2, if the terminal device failed to register with the 5G SA communication network two consecutive times and the second registration failure reason information corresponds to the first predetermined reason information, the terminal device prohibits initiating a registration request to the 5G SA communication network within 12 minutes and at this time registering to the LTE communication network. Further, when the terminal device returns to the 5G SA communication network for registration, then if this terminal device fails to register with the 5G SA communication network twice consecutively and the second registration failure reason information still matches the first set reason information, the terminal device prohibits initiating a registration request to the 5G SA communication network already within 2 hours. The duration of the penalty interval is increased from 12 minutes to 2 hours, which can reduce the time during which the service for the user is affected.

In light of possible problems under the conditions of the registration anomaly scenarios above, taking into account the actual experience of users, appropriate processing policies have been further developed for scenarios in which registration failure occurred due to failure to establish a communication channel, failure of random access or release (disconnection) of the channel connections. For a description of specific implementation options, see the following options (from the first option to the third option). All of the following options are examples described using the case in which the second communication network is an LTE communication network. It should be noted that the scenarios implemented in the current product are only a subset of the complete technical solution. Of course, different policies can be further specialized for other scenarios. The following specific options do not represent the entire technical solution.

First option: Scenarios where registration failure is due to a link failure

In the first option, the current communication network is exited for the scenario in which registration failure occurred due to a communication channel failure during the registration process (in other words, if an attempt to register in the 5G SA communication network was unsuccessful and registration in the second communication network occurred). Assuming that the predetermined reason information indicates that the registration attempt failed due to a communication link failure, the corresponding predetermined number of attempts is 2; and suppose that the method for progressively increasing the penalty is as follows: in the communication network SA, set a penalty interval of 12 minutes (in other words, the first specified penalty time interval) in the first round, and set a penalty interval of 2 hours (in other words, the second specified penalty time interval) in the second round and in each subsequent round. For example, if the second registration failure is a communication link failure that occurred in the first round of the registration procedure, the terminal device determines that the registration early termination condition is currently satisfied, ends the registration procedure with the communication network SA, and penalizes the communication network SA, where the duration is The first penalty interval is 12 minutes. After the penalty interval time has expired (after 12 minutes), the terminal device may resume using functionality to operate on the communication network SA and initiate registration with that communication network SA again. In the second round of the registration procedure, if the reason for the second registration failure is still a communication link failure, the terminal device terminates the registration procedure with the communication network SA early and sets the penalty interval ("penalizes" the network) for this communication network SA to 2 hours. To simplify the description, the symbol C is used in the following to represent the value of the cumulative number of failures.

In FIG. 8 is a simplified flow diagram of a method for handling registration anomalies in a communication network according to an embodiment of the present application applied to a scenario in which registration failure is caused by a communication link failure. As shown in FIG. 8, method 400 may comprise the following steps S411 to S422.

S411. The terminal device initiates transmission of the registration request to the communication network SA.

If the terminal device powers up (assume that this terminal device accesses the default communication network SA after being powered on) or switches from another system to the communication SA network, this terminal device initiates the transmission of a registration request to the communication SA network to access this communication SA network.

S412. In case of registration failure, the terminal device accumulates the number C=1 of failed attempts, obtains information about the registration failure reason, and determines whether the current registration anomaly scenario satisfies the registration procedure early termination condition.

The terminal device can determine whether the current registration anomaly scenario satisfies the registration procedure termination condition according to the registration failure reason information and the cumulative number of failures. For example, if it is determined that the current registration failure is due to a link failure and the cumulative number C of failures is not less than the corresponding predetermined number of failures 2, it can be determined that the current registration anomaly scenario satisfies the registration procedure early termination condition. If it is determined that the current registration anomaly scenario satisfies the registration procedure early termination condition, the terminal device proceeds with the execution of the next step S413. If it is determined that the current registration anomaly scenario does not satisfy the registration procedure termination condition, the terminal device may start a timer (eg, T3511), wait while remaining in the communication network SA, and continue attempting to register after the timer expires.

The registration procedure may fail in the registration process for a number of reasons, however, the current registration anomaly scenario may not satisfy the registration termination condition because the reason for the current registration failure may not be in the specified list of specified cause information, or it may be a cause (for example, an establishment anomaly communication channel, no response from the communication network, or refusal of registration from the communication network) from the specified list of predetermined cause information, but the cumulative number of failures did not reach the corresponding predetermined number. Therefore, the current registration anomaly scenario does not satisfy the registration termination condition, and the terminal device may continue to attempt to register with the communication network SA.

S413. If the condition for early termination of the registration procedure is not satisfied, the terminal device starts a timer.

For example, if the registration procedure fails and the current registration anomaly scenario does not satisfy the registration termination condition, the terminal device starts timer T3511 with a duration of 10 seconds (corresponding to the first timeout interval), during which the terminal device waits in the communication network SA, and may continue trying to register with the SA communication network after these 10 seconds have elapsed.

S414. If the timer duration has expired, the terminal device initiates transmission of a registration request to the communication network SA.

For example, timer T3511 expires after 10 seconds, and the terminal device re-initiates transmission of a registration request to the communication network SA.

S415. If the registration procedure fails, the terminal device accumulates the number C=2 of failed attempts, obtains registration failure reason information, and determines whether the current registration anomaly scenario satisfies the registration procedure early termination condition.

For example, if the registration failure reason information indicates that the current registration failure is caused by a random access failure, and that the cumulative number C of failures is not less than a predetermined number 2, it can be determined that the current registration anomaly scenario satisfies the registration procedure termination condition.

S416. If the reason for the current registration failure is a communication link failure, and the cumulative number of failures is equal to the corresponding predetermined number of 2, the condition for early termination of the registration procedure is satisfied, the terminal device prohibits the initiation of a registration request to the communication network SA for 12 minutes, and initiates the transmission of the registration request to the network LTE communications.

Since the failure of the communication channel that caused the current registration failure satisfies the predetermined cause information, and the cumulative number of failures is equal to the corresponding predetermined number 2, the condition for early termination of the registration procedure is satisfied. Therefore, the terminal device can quickly leave the current network and move to another communication network for registration.

According to the relevant technical solutions, if it fails to register twice consecutively, the terminal device accumulates the number of failed attempts equal to C=2 and starts the timer T3511 with a duration of 10 seconds, during which the terminal device waits in the communication network SA and continues to try to register. Contrary to the known art, in the present application, if the failure to register two times consecutively is caused by a communication link failure, the terminal device can terminate the current round of registration in the communication network SA early, set the penalty interval in the communication network SA ("fine" the network) to 12 minutes , disable the functionality to work in the communication SA network and do not initiate registration with the communication SA network. At this time, the terminal apparatus may return to the LTE communication network for registration to perform fast switching service.

With this approach, if an anomaly occurs in the SA communication network registration process and if the second anomaly is caused by a link failure scenario, the terminal device can terminate the SA communication network registration procedure early and return to the LTE communication network for registration, reducing the time within which the service for the user is affected.

After the terminal device registers with the LTE communication network, the penalty interval for the communication network SA ends, in other words, after 12 minutes, the terminal device recovers the functionality for working with the communication network SA and can return to the communication network SA to register again, and performs steps S417 to S422. For the description of steps S417 to S422, refer to the above detailed description of steps S411 to S416, which will not be repeated here.

Steps S411 to S416 can be considered the first round of the registration procedure, and steps S417 to S422 can be considered the first round of the registration procedure. Of course, the registration procedure may have more rounds. Unlike the first round of the registration procedure, the duration of the penalty interval in the second round of the registration procedure is increased to reduce the time affected by the registration anomaly. See the description of step S422 for details. If the reason for the current registration failure is a failure of the communication channel, and the cumulative number of failures is equal to the corresponding predetermined number of 2, the terminal device prohibits the initiation of a registration request to the communication network SA for 2 hours, and initiates the transmission of the registration request to the LTE communication network. The duration of the penalty interval is increased from 12 minutes to 2 hours.

In the prior art, if a registration failure occurs a second time, the terminal device accumulates the number of failures equal to C=2 and starts timer T3511 with a duration of 10 seconds, during which the terminal device waits in the communication network SA. Unlike the prior art, according to the present application, the terminal device can terminate the current round of the registration procedure in the communication network SA early in the second round of the registration procedure at this point, sets the duration of the penalty interval (“penalizes”) in the SA network to 2 hours, disables the functional the ability to work in the SA network and does not initiate registration with the communication SA network. At this time, the terminal device may go back to the LTE communication network to register to perform the fast switching service.

In the technical solution proposed in the first variant according to the present application, the registration procedure in the communication network SA can be completed early if the reason for the second failure of the registration procedure is the failure of the communication channel, and it is not necessary to continue to accumulate the number of registration attempts (corresponding to the cumulative number of failures). In addition, the communication network SA applies progressively increasing penalty intervals, so that the length of the penalty interval is set to 12 minutes in the first round. In the second round and in each subsequent round, the duration of the penalty interval is set to 2 hours. Compared to a ban of 12 minutes after five failed registration attempts in the prior art, the length of the penalty interval is increased to 2 hours, thereby reducing the impact on services for the user by reducing the time affected by the registration anomaly. Therefore, according to the present application, a terminal device can quickly transition to an LTE communication network if an anomaly occurs in the registration process in the 5G SA network, thereby reducing the time affected by the registration anomaly and improving service provision for the user.

Second option: Scenario where registration failure is due to random access failure

In the second option, a configuration of leaving the network to another communication network is proposed for a scenario in which registration failure occurs due to random access failure in the registration process (in other words, if registration in the 5G SA communication network is unsuccessful, registration in the second communication network is performed ). Assuming that the predetermined cause information indicates that the registration failure was due to a random access failure, the corresponding predetermined number of failures is 2; and assuming that the policy of progressively increasing penalty intervals is as follows: the communication network SA sets the duration of the penalty interval ("penalty") to 12 minutes (in other words, the first given penalty interval time) in the first round, and the duration of the penalty interval is 2 hours (in other words, the second given penalty time interval) in the second and each of subsequent rounds. For example, if the reason for the second registration failure is a random access failure in the first round of the registration procedure, the terminal device determines that the registration procedure early termination condition is currently satisfied, terminates the registration procedure in the communication network SA, and sets a penalty interval in the communication network SA (" fines" network), where the first duration of the penalty interval is 12 minutes. After the expiration of the penalty interval (12 minutes later), the terminal device may resume its functionality to operate the communication network SA and initiate the registration request to the communication network SA again. In the second round of the registration procedure, if the reason for the second registration failure is still random access failure, the terminal device terminates the registration procedure with the communication network SA early and sets the penalty interval in the communication network SA to 2 hours.

In FIG. 9 is a simplified flow diagram of a method for handling a registration anomaly in a communication network according to an embodiment of the present application applied to a scenario in which registration failure occurs due to random access failure. As shown in FIG. 9, method 500 comprises the following steps S511 to S522.

S511. The terminal device initiates transmission of the registration request to the communication network SA.

If the terminal device turns on or switches from another system to the communication network SA, this terminal device initiates the transmission of a registration request to the communication network SA to access this communication network SA.

S512. In case of registration failure, the terminal device accumulates the number C=1 of failed attempts, obtains information about the registration failure reason, and determines whether the current registration anomaly scenario satisfies the registration procedure early termination condition.

The terminal device can determine whether the current registration anomaly scenario satisfies the registration procedure termination condition according to the registration failure reason information and the cumulative number of failures. For example, if it is determined that the current registration failure is due to a link failure and the cumulative number C of failures is not less than the corresponding predetermined number of failures 2, it can be determined that the current registration anomaly scenario satisfies the registration procedure early termination condition. If it is determined that the current registration anomaly scenario satisfies the registration procedure early termination condition, the terminal device proceeds with the execution of the next step S513. If it is determined that the current registration anomaly scenario does not satisfy the registration procedure termination condition, the terminal device may start a timer (eg, T3511), wait while remaining in the communication network SA, and continue attempting to register after the timer expires.

The registration procedure may fail in the registration process for a number of reasons, however, the current registration anomaly scenario may not satisfy the registration termination condition because the reason for the current registration failure may not be in the specified list of specified cause information, or it may be a reason (for example, the reason may be link establishment anomaly, no response from the communication network, or registration denied from the communication network) from the specified list of predetermined cause information, but the cumulative number of failures did not reach the corresponding predetermined number. Therefore, the current registration anomaly scenario does not satisfy the registration termination condition, and the terminal device may continue to attempt to register with the communication network SA.

S513. If the condition for early termination of the registration procedure is not satisfied, the terminal device starts a timer.

For example, if the registration procedure fails and the current registration anomaly scenario does not satisfy the registration termination condition, the terminal device starts timer T3511 with a duration of 10 seconds (corresponding to the first timeout interval), during which the terminal device waits in the communication network SA.

S514. If the timer duration has expired, the terminal device initiates transmission of a registration request to the communication network SA.

For example, timer T3511 expires after 10 seconds, and the terminal device re-initiates transmission of a registration request to the communication network SA.

S515. If the registration procedure fails, the terminal device accumulates the number C=2 of failed attempts, obtains registration failure reason information, and determines whether the current registration anomaly scenario satisfies the registration procedure early termination condition.

For example, if the registration failure reason information indicates that the current registration failure is caused by a random access failure, and that the cumulative number C of failures is not less than a predetermined number 2, it can be determined that the current registration anomaly scenario satisfies the registration procedure early termination condition.

S516. If the reason for the current registration failure is a communication link failure, and the cumulative number of failures is equal to the corresponding predetermined number of 2, the condition for early termination of the registration procedure is satisfied, the terminal device prohibits the initiation of a registration request to the communication network SA for 12 minutes, and initiates the transmission of the registration request to the network LTE communications.

Since the failure of the communication channel that caused the current registration failure satisfies the predetermined cause information, and the cumulative number of failures is equal to the corresponding predetermined number 2, the condition for early termination of the registration procedure is satisfied. Therefore, the terminal device can quickly move to another communication network for registration.

According to the relevant technical solutions, if it failed to register twice consecutively, the terminal device accumulates the number of failed attempts equal to C=2 and starts timer T3511 with a duration of 10 seconds, during which the terminal device waits in the communication network SA and continues to try to register after duration of the timer, so that the registration procedure takes a long time. In the technical solution of the present application, if the failure to register twice consecutively is due to a random access failure, the terminal device can terminate the current registration round in the communication network SA early, set the penalty interval in the communication network SA ("penalize" the network) to 12 minutes, disable the functionality to operate on the SA communication network and not initiate registration with the SA communication network. At this time, the terminal apparatus may return to the LTE communication network for registration to perform fast switching service.

In contrast, in the technical solution of the present application, if an anomaly occurs during the registration process in the communication network SA, and if the second anomaly is caused by a random access failure scenario, the registration procedure in the communication network SA can be completed early, and the terminal device returns to the LTE network. connections for registration, thereby reducing the time during which the service for the user is affected, and improving the provision of the service to the user.

After the terminal device registers with the LTE communication network, the penalty interval for the SA communication network ends, in other words, after 12 minutes, the terminal device restores the functionality to operate in the communication network SA and can return to the SA communication network to register again, and performs steps S517 to S522. For the description of steps S517 to S522, refer to the above detailed description of steps S511 to S516, which will not be repeated here.

Steps S511 to S516 can be considered the first round of the registration procedure, and steps S517 to S522 can be considered the second round of the registration procedure. Of course, the registration procedure may have more rounds. Unlike the first round of the registration procedure, the duration of the penalty interval in the second round of the registration procedure is increased to reduce the time affected by the registration anomaly. See the description of step S422 for details. If the reason for the current registration failure is random access failure, and the cumulative number of failures is equal to the corresponding predetermined number of 2, the terminal apparatus prohibits initiating a registration request to the communication network SA for 2 hours, and initiates transmission of the registration request to the LTE communication network. The duration of the penalty interval is increased from 12 minutes to 2 hours.

In the prior art, if a registration failure occurs for the second time, the terminal device accumulates the number of failures equal to C=2 and starts timer T3511 with a duration of 10 seconds, during which the terminal device waits in the communication network SA. Unlike the prior art, according to the present application, the terminal device can terminate the current round of the registration procedure in the communication network SA early (compared to the protocol) in the second round of the registration procedure at this point, sets the length of the penalty interval ("penalizes") in the network SA, set to 2 hours disables SA networking functionality and does not initiate registration with the SA communication network. At this time, the terminal device may go back to the LTE communication network to register to perform the fast switching service.

In the solution proposed in the second embodiment of the present application, the registration procedure in the communication network SA can be completed early if the reason for the second registration procedure failure is a random access failure, and it is not necessary to continue accumulating the number of registration attempts (corresponding to the cumulative number of failures). In addition, the communication network SA applies progressively increasing penalty intervals, so that the length of the penalty interval is set to 12 minutes in the first round. In the second round and in each subsequent round, the duration of the penalty interval is set to 2 hours. Compared to a ban of 12 minutes after five failed registration attempts in the prior art, the length of the penalty interval is increased to 2 hours, thereby reducing the impact on services for the user by reducing the time affected by the registration anomaly. Therefore, according to the present application, a terminal device can quickly transition to an LTE communication network if an anomaly occurs in the registration process in the 5G SA network, thereby reducing the time affected by the registration anomaly and improving service provision for the user.

Third option: Scenario in which registration failure occurs due to the release (disconnection) of the communication channel with the network

In the third variant, the configuration of leaving the network to another communication network is proposed for the scenario in which the registration failure occurs due to the release (disconnection) of the communication channel with the network in the registration process (in other words, if the registration in the 5G SA communication network is unsuccessful, registration in the second communication network). Assuming that the predetermined cause information indicates that the registration failure occurred due to the release (disconnection) of the communication channel with the network, the corresponding predetermined number of failures is 2; and assuming that the policy of progressively increasing penalty intervals is as follows: the communication network SA sets the duration of the penalty interval ("penalty") to 12 minutes (in other words, the first given penalty interval time) in the first round, and the duration of the penalty interval is 2 hours (in other words, the second given penalty time interval) in the second and each of subsequent rounds. For example, if the reason for the second registration failure is the release (disconnection) of the communication channel with the network in the first round of the registration procedure, the terminal device determines that the condition of early termination of the registration procedure is currently satisfied, ends the registration procedure in the communication network SA, and sets the network SA communication penalty interval ("penalizes" the network), where the first duration of the penalty interval is 12 minutes. After the expiration of the penalty interval (after 12 minutes), the terminal device may resume its functionality to operate in the communication network SA and initiate the registration request in the communication network SA again. In the second round of the registration procedure, if the reason for the second registration failure is still the release (disconnection) of the communication channel with the network, the terminal device terminates the registration procedure with the communication network SA early and sets the penalty interval in the communication network SA to 12 hours.

In FIG. 10 is a simplified flow diagram of a method for handling a registration anomaly in a communication network according to one embodiment of the present application, applied to a scenario in which registration failure occurs due to the release (disconnection) of a communication channel with the network. As shown in FIG. 10, method 600 comprises the following steps S511 to S616.

S611. The terminal device initiates transmission of the registration request to the communication network SA.

As shown in FIG. 11(a), if the terminal device 01 is turned on or switched from another system to the communication network SA 02, this terminal device initiates the transmission of a registration request to the communication network SA 02 to access this communication network SA 02.

S612. In case of registration failure, the terminal device accumulates the number C=1 of failed attempts, obtains information about the registration failure reason, and determines whether the current registration anomaly scenario satisfies the registration procedure early termination condition.

The terminal device can determine whether the current registration anomaly scenario satisfies the registration procedure termination condition according to the registration failure reason information and the cumulative number of failures. For example, if it is determined that the current registration failure is due to the release (disconnection) of the communication channel with the network, and the cumulative number C of failures is not less than the corresponding specified number of 2 failures, it can be determined that the current registration anomaly scenario satisfies the condition of early termination of the procedure registration. If it is determined that the current registration anomaly scenario satisfies the registration procedure early termination condition, the terminal device proceeds with the execution of the next step S613. If it is determined that the current registration anomaly scenario does not satisfy the registration procedure termination condition, the terminal device may start a timer (eg, T3511), wait while remaining in the communication network SA, and continue attempting to register after the timer expires.

S613. If the current registration failure is due to the release (disconnection) of the communication channel with the network, and the cumulative number of failures is equal to the corresponding predetermined number of 1 failed attempts, the condition for early termination of the registration procedure is satisfied, the terminal device prohibits the initiation of a registration request to the communication network SA within 12 minutes and initiates a registration request to the LTE communication network.

Since the release (disconnection) of the network link that caused the current registration failure corresponds to the predetermined cause information, and the cumulative number of failures is equal to the corresponding predetermined number of failed attempts 1, the condition for early termination of the registration procedure is satisfied. Therefore, as shown in FIG. 11(b), the terminal device 01 can quickly enter the LTE communication network 03 for registration.

In prior art, if a registration failure occurs for the first time, the terminal device accumulates the number C=1 of failed attempts, starts a timer T3511 with a duration of 10 seconds, during which the terminal device waits in the SA communication network, and continues to attempt to register after the timer duration has expired. so the registration procedure takes a long time. According to the technical solution of the present application, if the registration failure occurred due to the release (disconnection) of the communication channel with the network, the terminal device can terminate the current round of registration in the SA communication network ahead of schedule, set a penalty interval in the SA communication network ("penalize" the network) with a duration of 12 minutes, disable the functionality to work in the SA communication network and do not initiate registration with the SA communication network. At this time, the terminal device may return to the LTE communication network to register for services and achieve fast switching to this network. In contrast, in the technical solution of the present application, when an anomaly occurs in the registration process in the communication network SA, if the reason for the second anomaly is the release (disconnection) scenario of the communication channel, the registration procedure in the communication network SA can be completed ahead of schedule, and the terminal device returns to LTE communication network for registration, thereby reducing the time during which the service for the user is affected and improving the quality of service provision to the user.

After the terminal device registers with the LTE communication network, the penalty interval for the SA communication network ends, in other words, after 12 minutes, the terminal device restores the functionality to operate in the communication network SA and can return to the SA communication network to register again, and performs steps S614 to S616. For the description of steps S614 to S616, refer to the above detailed description of steps S611 to S613, which will not be repeated here.

Steps S611 to S613 can be considered the first round of the registration procedure, and steps S614 to S616 can be considered the second round of the registration procedure. Of course, the registration procedure may have more rounds. Unlike the first round of the registration procedure, the duration of the penalty interval in the second round of the registration procedure is increased to reduce the time affected by the registration anomaly. See the description of step S616 for details. If the reason for the current registration failure is the release (disconnection) of the communication channel, and the cumulative number of failures is equal to the corresponding predetermined number 1, the terminal device prohibits the initiation of the registration request to the communication network SA for 12 hours, and initiates the transmission of the registration request to the LTE communication network. The duration of the penalty interval is increased from 12 minutes to 12 hours.

In the prior art, if the network registration failure occurs for the first time, the terminal device accumulates the number of failures equal to C=1 and starts timer T3511 with a duration of 10 seconds, during which the terminal device waits in the communication network SA. In contrast to the prior art, according to the present application, the terminal device can terminate the current round of registration in the communication network SA early in the second round of the registration procedure at this point, set the penalty interval in the communication network SA ("fine" the network) to 12 hours, disable the functionality to operate on the Communication SA network and not initiate registration with that Communication SA network. At this time, the terminal device may return to the LTE communication network to register for services to achieve fast switching to this network.

According to the technical solution proposed in this third embodiment, in the present application, the registration procedure in the communication network SA can be completed ahead of time if the reason for the first failure in the registration process is the release (disconnection) of the communication channel with the network, so that it is not necessary to continue to accumulate the number of registration attempts (corresponding to the cumulative number of failures). In addition, progressively increasing penalty intervals are set in the communication network SA, and the length of the penalty interval in the first round is set to 12 minutes. In the second round and in each subsequent round, the duration of the penalty interval is 12 hours. Compared to the prior art prohibition of 12 minutes after five unsuccessful registration attempts, the length of the penalty interval is increased here to 12 hours, thereby reducing the undesirable impact on the services provided to the user by reducing the time affected by the registration anomaly. Therefore, according to the present application, the terminal device can quickly switch to the LTE communication network for registration if an anomaly occurs when registering with the 5G SA communication network, thereby reducing the time affected by the registration anomaly and improving service provision to the user.

It should be noted that although only 13 causes of anomalies are currently listed in the current embodiment of the present application, and three options are given, it can be understood that the cause of an anomaly during registration is a variable input parameter of the proposed technical solution, and that other causes can also be entered using the logic of the implementation of the technical solution of the present application. Therefore, the currently existing list of causes of anomalies can continue to expand. In addition, the variant configuration parameters can be flexibly modified and customized according to the communication network situation.

According to the communication network registration anomaly handling method proposed in the embodiments of the present application, the terminal device can quickly switch to another communication network when an anomaly occurs in the registration process in the 5G SA communication network, and if the condition for early completion of the registration procedure is satisfied, the terminal device can complete the registration procedure in the communication network SA and quickly switch to the LTE communication network for registration, thereby reducing the time affected by the registration anomaly and improving the provision of services to the user.

It should be noted that, firstly, according to the technical solution of the present application, the maximum number of registration attempts (the protocol provides for 5) can be specialized in accordance with various causes of anomalies (in other words, information about the reason for registration failure), so that the registration procedure in Network SA communication may be terminated sooner if an anomaly occurs. The specific choice of the maximum number of registration attempts for various anomaly causes can be specialized in different possible implementations. In the present application, this is not limited. Secondly, according to the technical solution of the present application, the duration of the penalty interval can be specialized, and you can build a policy of progressive increase in the length of the penalty interval. For example, the duration of the penalty interval in the second round of the registration procedure is longer than in the first round of the registration procedure. There are various possible ways to build a policy of progressively increasing the duration of the penalty interval. In the present application, this is not limited. Thirdly, according to the technical solution of the present application, the timer can be started without a fixed duration, depending on the causes of the anomaly. There are various possible ways to select the duration of the timer time corresponding to the particular cause of the anomaly. In the present application, this is not limited.

It should also be noted that in embodiments of the present application, "greater than" may be replaced by "greater than or equal to" (not less), "less than or equal to (not greater than)" may be replaced by "less than" or "greater than or equal to ( not less)" can be replaced by "greater than" and "less than" can be replaced by "less than or equal to (not greater than)".

Each option described here may be an independent technical solution, or these options can be combined in accordance with internal logic, and all of these technical solutions fall within the protection scope of this application.

It can be understood that the methods and operations implemented by the access network device in the above method embodiments may also be implemented by a component (eg, an integrated circuit (chip) or circuit) that can be used in this access network device. The methods and operations implemented by the terminal device in the above method embodiments may also be implemented by a component (eg, an integrated circuit (chip) or circuit) that can be used in this terminal device. It can be understood that the methods and operations implemented by the backbone network device in the above method embodiments may also be implemented by a component (eg, an integrated circuit (chip) or circuit) that can be used in this backbone network device.

The variants of the method proposed by the present application are discussed above, and the options for the equipment proposed by the present application will be described below. It should be understood that the description of the apparatus options corresponds to the description of the method options. Therefore, for content that will not be described in detail, the above embodiments of the method may be referred to. This, for brevity, will not be repeated here.

The technical solutions offered by the variants of the present application are described above mainly in terms of interaction between devices. It can be understood that in order to perform the above functions, each device, such as a transmitter or receiver, contains appropriate hardware circuits and structures and/or software modules to perform various functions. A person skilled in the art may be aware that, in combination with the modules and algorithm steps of the examples described in the embodiments of the present invention, the present application may be implemented in hardware or as a combination of hardware and computer software. Whether a function is implemented in hardware or through computer software that controls the hardware depends on the particular application and design constraints of the technical solutions. Those skilled in the art may use various methods to implement the described functions in a particular application, but such an implementation should not be considered outside the protection scope of the present application.

In embodiments of the present application, the functional modules of the transmitter or receiver may be broken down in accordance with the above method examples. For example, functional modules may be broken down according to functions, or two or more functions may be integrated into a single processor module. An integrated module may be implemented in the form of hardware, or it may be implemented in the form of a functional software module. It should be noted that, in embodiments of the present application, the modularization is only an example and is simply a partitioning of logical functions, so other partitioning methods are possible in actual implementations. The following description is made using an example in which the division into functional modules corresponds to the functions.

In FIG. 12 is a simplified block diagram of an apparatus 700 for handling registration anomalies in a communication network, according to one embodiment of the present application. The apparatus 700 may be configured to perform an action performed by an access network device in the above embodiments of the method. The apparatus 700 includes a transceiver module 710 and a processor module 720. The transceiver module 710 is configured to perform signal transmission and reception operations on the terminal device side in the above embodiments. Transceiver module 710 may also be referred to as a communication interface or communication module. The processor module 720 is configured to perform data processing and data processing operations on the terminal device side in the above embodiments.

The transceiver module 710 is configured to initiate an M-th registration request to the 5G SA communication network, where M is a positive integer less than N and N is a predetermined integer.

The processor module 720 is configured to, in the event of failure of the M-th registration attempt, obtain information about the reason for this M-th registration failure and the cumulative number M of failures; and if the registration failure cause information of the M-th registration failure corresponds to the first specified cause information, and the cumulative number M of failures is not less than the first specified number of failures corresponding to the specified first predetermined cause information, execute the first processing policy corresponding to the first predetermined cause information, where this first processing policy comprises stopping the initiation of a registration request to the 5G SA communication network and initiating a registration request to a second communication network other than the 5G SA communication network.

In some embodiments, N may be equal to 5. For example, M may be equal to 1, 2, 3, or 4. If M is equal to 1, the transceiver module 710 initiates the first (in other words, initial) registration request to the 5G communication SA network. If M is greater than 1 and less than 5, before the transceiver module 710 initiates the Mth registration request to the 5G SA communication network, the apparatus 700 will fail to register to the 5G SA communication network successively M-1 times. For example, if M is 2, apparatus 700 initiates a second registration request to the 5G SA communication network after the first registration attempt to the 5G SA communication network has failed.

In some embodiments, the second communication network may be an LTE communication network. For example, when a mobile phone failed to register with the 5G SA communication network several times consecutively, if it is determined that the current registration anomaly scenario satisfies the registration termination condition according to the registration failure reason information and the cumulative number of failures, the mobile phone stops initiating the request. registration to the 5G communication network SA and may initiate a registration request to the LTE communication network at this time. Therefore, by using the registration anomaly handling apparatus of the communication network proposed in the present application, the mobile phone can, if an anomaly occurs in the registration process in the 5G SA communication network, quickly leave this communication network and return back to the LTE communication network for registration, thereby reducing the time that the service to the user is affected and improving the quality of service delivery to the user.

In some embodiments, if M is greater than 1 and less than N, before the transceiver module 710 initiates the Mth registration request to the 5G SA communications network, the apparatus 700 will fail to register to the 5G SA network successively M-1 times.

In some embodiments, apparatus 700 may further comprise a counter module. This counter module is configured to add one each time the apparatus 700 fails to register with the 5G SA communications network, and accumulates a cumulative number M of failures when registration fails for the Mth time.

In some embodiments, the first predetermined cause information may be used to indicate any one of the following conditions: registration failure due to failure to establish a communication channel, registration failure due to release (disconnection) of the communication channel after establishment, registration failure due to for no response from the 5G SA communication network or registration failure due to registration refusal from the 5G SA communication network.

In some embodiments, the transceiver module 710 is further configured to initiate an (M+1)-th registration request to the 5G SA communication network after the first timeout interval has elapsed if the M-th registration failure cause information does not match the first predetermined cause information, or if the reason information of the Mth registration failure matches the first predetermined cause information and the cumulative number M of failures is less than the first predetermined number of failures.

In some embodiments, the processor module 720 is further configured to, if the apparatus 700 fails to register with the 5G SA communications network for the (M+1)th time, obtain information about the reason for the (M+1)th registration failure. and the cumulative number M+1 of failures; and if the reason information of the (M+1)th registration failure corresponds to the second predetermined cause information, and the cumulative number M+1 of failures is not less than the second predetermined number of failed attempts corresponding to the second predetermined cause information, execute the first processing policy corresponding to the second given information about the causes.

In some embodiments, the processor module 720 is specifically configured to prohibit the initiation of a registration request to the 5G SA communication network during a first predetermined penalty time interval corresponding to the first predetermined cause information. This first predetermined penalty time interval is greater than the first waiting time interval.

In some embodiments, the transceiver module 710 is further configured to initiate a registration request to the 5G SA communications network after the first predetermined penalty time has elapsed.

In some embodiments, the transceiver module 710 is specifically configured to receive command information transmitted by the 5G SA communication network or the second communication network and initiate a registration request to the 5G SA communication network in accordance with the command information. This command information is used as a command to initiate a registration request to the 5G SA communication network.

In some embodiments, the processor module 720 is further configured to prohibit initiation of a 5G SA communication network registration request for a second predetermined penalty time interval if the transceiver module 710 fails to register with the 5G SA communication network consecutively M times, and the reason information is Mth registration failure corresponds to the first specified reason information. The second predetermined penalty time interval may be greater than the first predetermined penalty time interval.

In some embodiments, apparatus 700 may further comprise a memory module. This memory module is configured to prestore at least one match, where the collection of at least one match contains the first match and the second match, such that the first match is the match of the first given cause information, the first given number of failures, and the first processing policy , and the second match is the match of the second predetermined cause information, the second predetermined number of failures, and the first processing policy.

In some embodiments, the processor module 720 is further configured to determine the first predetermined number of failures corresponding to the first predetermined cause information according to the first match if the Mth registration failure cause information matches the first predetermined cause information.

In some embodiments, transceiver module 710 is specifically configured to initiate a registration request to a second communication network if apparatus 700 searches for at least one available communication network other than a 5G SA communication network, where the set of at least one available communication network comprises the specified second communication network, and the quality of the received reference signal in the second communication network from the set of at least one available communication network is optimal.

In accordance with the characteristics of the registration anomaly processing apparatus proposed in the present embodiment of the present application, if an anomaly occurs during registration in the communication network, the terminal device can obtain information about the reason for registration failure and the cumulative number of failures to determine whether the condition for early termination is satisfied. registration procedures. If this condition is met, the registration procedure ends early, so that it is not necessary to retry several times according to the protocol, and at this time it is possible to register with another communication network to quickly resume services. Therefore, according to the technical solution of the present application, the abnormal registration can be completed earlier (early than the protocol) and if an anomaly occurs during registration in a communication network, it is possible to register in another communication network in order to reduce the time affected by the registration anomaly, and solve the problem of frequent registration failures due to anomalies in the communication network or bad signal conditions during the registration process in the communication network, and improve the quality of service to the user.

Apparatus 700 according to the variants of the present application may correspond to the methods considered by the variants of the present application, as well as the above and other operations and/or functions of the modules of the apparatus 700 are intended to implement the corresponding procedures of the methods. For brevity, details will not be described here again.

In FIG. 13 is a simplified block diagram of communication apparatus 900 according to one embodiment of the present application. This communications apparatus 900 includes: a processor 910, a memory 920, a communications interface 930, and a bus 940.

In one possible implementation, processor 910 in hardware 900 shown in FIG. 13 may correspond to processor module 720 in hardware 700 shown in FIG. 12. Communication interface 930 in apparatus 900 shown in FIG. 13 may correspond to the transceiver module 710 in the apparatus 700 shown in FIG. 12.

The processor 910 may be coupled to a storage device 920. This storage device 920 may be configured to store program code and data. Therefore, memory 920 may be a storage module within processor 910, or may be an external storage module independent of processor 910, or may further be a component comprising a storage module within processor 910 and an external storage module that is not processor dependent 910.

Optionally, hardware 900 may further comprise a bus 940. Memory 920 and communication interface 930 may be coupled to processor 910 via this bus 940. Bus 940 may be a Peripheral Component Interconnect (PCI) bus, a bus with extended industry standard architecture (EISA) or other similar bus. Bus 940 can be classified as an address bus, a data bus, a control bus, or the like. For ease of description, in FIG. 13 shows only one line, which does not mean that there is only one bus or tires of only one type.

It should be understood that in embodiments of the present application, the processor 910 may include a central processing unit (central processing unit, CPU). The processor may be another general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or other similar device. A general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. Alternatively, processor 910 employs one or more integrated circuits to execute appropriate programs in order to implement the technical solutions proposed by the variants of the present application.

The memory device 920 may include read-only memory (ROM) and random access memory (RAM) and provide instructions and data to the processor 910. Part of the processor 910 may further contain a non-volatile random access memory. For example, processor 910 may further contain device type information.

If hardware 900 is operating, processor 910 executes computer-executable instructions from memory 920 to perform the steps of the above methods using hardware 700.

It should be understood that the apparatus 900 of the embodiments of the present application may correspond to the apparatus 700 of the embodiments of the present application, and that the above and other operations and/or functions of the modules in the apparatus 700, respectively, are directed to the implementation of the corresponding procedures of the methods of the present application. For brevity, details will not be described here again.

Optionally, in some embodiments, embodiments of the present application further describe a computer-readable storage medium that stores program code such that when the computer program code is executed on a computer, the computer performs the method according to the above aspects.

As an option, in some embodiments, contemplated embodiments of the present application further provide a computer program product. This computer program product contains program code such that when the computer executes the program code, the computer implements the method according to the above aspects.

In embodiments of the present application, a terminal device or network device comprises a hardware layer, an operating system layer running at the hardware layer, and an application layer running at the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and a storage device (also called main storage). An operating system at the operating system level may be any one or more computer operating systems such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system implementing services using a process. The application layer may contain an application such as a browser, address book, word processor software, or instant messaging software.

Variants of the present application do not specifically limit the specific structure of the execution object that implements the methods proposed by the variants of the present application, as long as the program in which the code of the methods implemented by the variants of the present application is written can be executed to communicate according to the variants of the present application. For example, an executing entity for performing the methods provided by embodiments of the present application may be a terminal device or network device, or a functional module in a terminal device or network device that can call a program and execute that program.

Aspects or features of the present application may be implemented as a method, apparatus, or product using standard programming and/or engineering techniques. The term "product" as used in this application may encompass a computer program that can be accessed from any computer-readable component, carrier or other medium. For example, a computer-readable medium may include, but is not limited to, a magnetic storage component (such as a hard disk drive, floppy disk, or magnetic tape), an optical disc (such as a compact disc, CD), or a digital versatile disc. , DVD)), a microprocessor card, and a flash memory component (such as an erasable programmable read-only memory (EPROM), card, or flash drive).

The various storage media described herein may indicate one or more devices and/or other computer-readable media used to store information. The term "computer-readable media" may include, but is not limited to, radio and various other media that may store, contain, and/or carry instructions and/or data.

It should be understood that the processor described in the embodiments of this application may be a central processing unit (central processing unit, CPU), or may be other general purpose processor, digital signal processor (digital signal processor, DSP), application specific integrated circuit (application specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistorized logic devices, discrete hardware component, or other similar device. A general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

Further, it can be understood that the storage device described in the embodiments of the present application may be a volatile storage device or a non-volatile storage device, or may contain both a volatile storage device and a non-volatile storage device. The non-volatile storage device may be read only memory (ROM (read-only memory, ROM)), programmable ROM (ROM) (PROM (programmable ROM, PROM)), erasable PROM (PROM) (EPROM (erasable PROM, EPROM)) , an electrically erasable PROM (EPROM) (EEPROM (electrically EPROM, EEPROM)) or a flash memory device. The volatile memory may be random access memory (RAM). For example, RAM can be used as an external cache. For example, without limitation, RAM can take various forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM , SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), dynamic random access memory with synchronous communication (synchlink DRAM, SLDRAM) and random access memory with direct resident access bus (direct rambus RAM, DR RAM).

It should be noted that if the processor is a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, or a discrete hardware component, a memory (information storage module) may be integrated into the processor.

Further, it should be noted that the storage device described herein may include, without limitation, the listed storage devices and storage devices of any other suitable types.

Even those of ordinary skill in the art may be aware that the modules and steps in the examples described with reference to the embodiments discussed in this application may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific applications and design constraints imposed on the technical solutions. Specialists in this area can use different methods to implement the described functions for each particular application, but such implementation options should not be considered outside the protection scope of this application.

Those skilled in the art may clearly understand that, for convenience and brevity of description, for the specific operating procedures of the systems, apparatus, and modules described above, reference may be made to the corresponding procedures in the above embodiments of the method, and details will not be described here.

In the variants proposed in this application, it should be clear that the described system, apparatus and method can be implemented in other ways. For example, the described embodiment of the apparatus is merely an example. For example, modularization is simply a partitioning of logic functions, so a different partitioning may be used in real-life cases. For example, several modules or components may be combined or integrated into another system, or some features may be ignored or omitted. In addition, the relationships presented or discussed herein or direct links or connections for communication may be implemented using some interfaces. Indirect links or connections for communication between devices or modules may be implemented in electronic, mechanical or other forms.

Modules described as separate parts may or may not be physically separate, and parts represented as modules may or may not be physical modules, may be located in the same location, or may be distributed across multiple network modules. Some or all of the modules may be selected according to the actual need to achieve the objectives of the technical solutions of the variants of the present application.

In addition, functional modules in embodiments of the present application may be integrated in one module, or each of the modules may exist separately physically, or two or more modules may be integrated in one module.

If any functions are implemented in the form of software functional modules sold or used as independent products, these functions may also be stored on a computer-readable storage medium. Based on such an understanding, the technical solutions of the present application, which are essentially or partially known in the art, or some such technical solutions may be implemented in the form of a computer program product. This computer program product is stored on a storage medium and contains a set of instructions for controlling a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods described in the embodiments of the present application. The above storage medium may be, without limitation: any medium capable of storing program code, such as a USB flash drive, removable hard disk, ROM (read-only memory, ROM), RAM (random access memory, RAM ), magnetic disk or optical disk.

Unless otherwise indicated, the meanings of all technical and scientific terms used in the present description are the same as those meanings that are commonly understood by specialists in the field to which this application relates. In this application, the terms used in its presentation, are intended simply to describe the purposes of specific options, but not to limit the present application.

The above descriptions are simply dedicated to specific embodiments of the present application, but are not intended to limit the scope of protection of the present application. Any variations or substitutions easily determined by a person skilled in the art within the technical scope of this application should fall within the protection scope of this application. Therefore, the scope of protection of the present application should be consistent with the scope of protection of the Claims.

Claims (37)

1. A method for processing anomalies during registration in a communication network, comprising: initiating, by the terminal device, an M-th registration request to a fifth generation autonomous communications network (5G SA), where M is a positive integer less than 5; if the M-th registration attempt fails, obtaining by the terminal device information about the reason for this M-th registration failure and the cumulative number M of failures; and if the reason information of the M-th registration failure corresponds to the first predetermined reason information, and the cumulative number M of failures is not less than the first predetermined number of failures corresponding to the first predetermined reason information, the terminal device executes the first processing policy corresponding to the first predetermined reason information , where this first processing policy comprises: stopping the initiation of a registration request to the 5G SA communication network, and initiation of the registration request to a second communication network other than the 5G SA communication network, in which the first predetermined cause information is used to indicate any one of the following reasons: registration failure due to failure to establish a communication channel, registration failure due to release (disconnection) of a communication channel after establishment, registration failure due to no response from 5G SA communication network or registration failure due to registration failure received from the 5G SA communication network. 2. The method of claim 1, wherein after the terminal device has received information about the reason for the M-th registration failure and the cumulative number M of failures, the method further comprises: initiating, by the terminal device, the (M+1)-th registration request to the 5G SA communication network after the expiration of the first timeout interval, if the M-th registration failure cause information does not match the first specified cause information, or if the cause information M- The th registration failure corresponds to the first predetermined cause information, and the cumulative number M of failures is less than the first predetermined number of failures. 3. The method of claim 2, wherein after the terminal device initiates the (M+1)th registration request to the 5G SA communication network after the expiration of the first timeout interval, the method further comprises: if the terminal device fails to register with the 5G SA communication network for the (M+1)th time, obtaining by the terminal device information about the reason for the (M+1)th registration failure and the cumulative number M+1 of failures; and if the reason information of the (M+1)th registration failure corresponds to the second predetermined cause information, and the cumulative number M+1 of failures is not less than the second predetermined number of failures corresponding to the second predetermined cause information, the terminal device executes the first processing policy corresponding to the second given information about the causes. 4. The method according to claim 2 or 3, in which the method further comprises: starting, by the terminal device, timer T3511 if the reason information of the Mth registration failure does not match the first predetermined cause information, or if the reason information of the Mth registration failure matches the first predetermined cause information and the cumulative number M of failures is less than the first predetermined number failures, in which the predetermined time duration of the timer T3511 is equal to the first timeout interval. 5. The method according to one of paragraphs. 2-4, in which the first timeout interval is 10 seconds. 6. The method according to one of paragraphs. 1-5, in which the procedure for stopping by the terminal device of initiating a registration request to the 5G SA communication network comprises: forbidding, by the terminal device, initiating a registration request to the 5G SA communication network within the first predetermined penalty time interval corresponding to the first predetermined cause information. 7. The method of claim 6, wherein the first predetermined penalty time interval is greater than the first wait time interval. 8. The method according to claim 6 or 7, wherein after the terminal device prohibits initiating a registration request to the 5G SA communication network for a first predetermined penalty time interval, the method further comprises: initiating, by the terminal device, a registration request to the 5G SA communication network after the expiration of the first predetermined penalty time interval. 9. The method of claim 8, wherein before the terminal device initiates a registration request to the 5G SA communication network after the expiration of the first predetermined penalty time interval, the method further comprises: receiving, by the terminal device, command information transmitted by the 5G SA communication network or the second communication network, where the command information is used as a command to initiate a registration request to the 5G SA communication network; and the procedure for initiating, by the terminal device, a registration request to the 5G SA communication network contains: initiating, by the terminal device, a registration request to the 5G SA communication network according to the command information. 10. The method according to claim 8 or 9, wherein after the terminal device initiates a registration request to a 5G SA communication network, the method further comprises: prohibition, by the terminal device, of initiating a registration request to the 5G SA communication network for a second predetermined penalty time interval if the terminal device has failed in attempts to register to the 5G SA communication network consecutively M times, and the information about the reason for the M-th registration failure corresponds to the first predetermined information about the reasons wherein the second predetermined penalty time interval is greater than the first predetermined penalty time interval. 11. The method according to one of paragraphs. 1-10, wherein the method further comprises: prestoring by the terminal device at least one match, where the set of at least one match comprises a first match and a second match, the first match is a match between the first given cause information, the first given number of failures, and the first processing policy, and the second match is is a correspondence between the second predetermined cause information, the second predetermined number of failures, and the first processing policy; and if the reason information of the M-th registration failure matches the first given reason information, the method further comprises: determining by the terminal device a first predetermined number of failures corresponding to the first predetermined cause information according to the first match. 12. The method according to one of paragraphs. 1-11, wherein the procedure for initiating a registration request by a terminal device to a second communication network other than the 5G SA communication network comprises: search by the terminal device for at least one available communication network other than the 5G SA communication network, where the set of at least one available communication network contains the specified second communication network, and the quality of the received reference signal from this second communication network from the set of at least one available communication network is optimal; and initiating, by the terminal device, a registration request to this second communication network. 13. The method according to one of paragraphs. 1-12, in which if M is greater than 1 and less than N, before the terminal device initiates the M-th registration request to the 5G SA communication network, this terminal device has already failed to register to the 5G SA communication network successively M-1 times. 14. The method according to one of paragraphs. 1-13, additionally containing: counting by one by the terminal device each time that terminal device fails in an attempt to register with the 5G SA communication network, and accumulating the cumulative number M of failures if the M-th registration attempt fails. 15. Equipment for processing anomalies during registration, containing: a memory device, a processor and a program stored in the memory device and executed by the processor, where, when executing this program, the processor carries out the method according to one of paragraphs. 1-14.

Images