RU2802818C2 - Method for processing anomalies during registration in a communication network, equipment, information storage medium and integral circuits - Google Patents

Abstract

FIELD: processing of anomalies during registration in a communication network.

SUBSTANCE: method includes: initiation, by the terminal device, of the M-th registration request to the autonomous communication network of the fifth generation (5G SA), where M is a positive integer less than 5; if the cumulative number M of failures is not less than the first predetermined number of failures corresponding to the first predetermined cause information, executing, by the terminal device, the first processing policy corresponding to the first predetermined cause information, where this first processing policy comprises: ceasing to initiating a 5G SA registration request communication, and initiating a registration request to a second communication network other than the 5G SA communication network. Therefore, the abnormal registration situation can be quickly terminated and registered with another communication network in the event of an anomaly occurring during registration with the communication network, so as to reduce the time affected by the registration anomaly.

EFFECT: eliminating frequent registration failures due to anomalies in the communication network or poor signal passing during registration in the communication network and improving the quality of user service.

18 cl, 13 dwg, 4 tbl

Description

This application claims priority to China Patent Application No. 202011140963.3, which was filed with the National Intellectual Property Administration of China on October 22, 2020, entitled “METHOD FOR PROCESSING NETWORK REGISTRATION ANOMALIES, EQUIPMENT, STORAGE MEDIA AND INTEGRATED CIRCUIT” (“METHOD FOR PROCESSING NETWORK REG ISTRATION ANOMALY, APPARATUS, STORAGE MEDIUM, AND CHIP"), and which is incorporated herein by reference in its entirety.

Field of technology to which the invention relates

This application relates to the field of communication technology, and in particular to a method for processing registration anomalies in a communication network, hardware, storage medium and integrated circuit (chip).

State of the art

Today, if a terminal device registers with a communications network, there may be situations where the terminal device fails to register with the communications network because an anomaly has occurred in the interaction between the terminal device and the communications network. If a terminal device fails to register with the communications network, the terminal device typically waits for a specified 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 specified period 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). Once the number of registration failures of a terminal device reaches a predetermined maximum number of registration attempts, the terminal device will no longer initiate a registration request on the communication network for a period of time and will initiate a registration request on other communication networks to resume service. It can be understood that if an anomaly always exists when a terminal device tries to register with a communication network, then since multiple registration attempts have to be made, the registration procedure is time-consuming so that the provision of services cannot be quickly resumed, which negatively affects the user experience services.

The essence of the invention

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

According to the first aspect, a method is proposed for processing anomalies when registering in a communication network, comprising: initiation, by a terminal device, of an M registration request into a standalone (SA) fifth generation ( ^5th generation, 5G) communication network, where M is a positive integer the number is less than N and N is a 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 of M failures; and if the failure reason information of the Mth registration attempt corresponds to the first specified reason information and the cumulative number of failures M is not less than the first specified number of failures corresponding to the first specified failure reason information, executing, by the terminal device, a first processing policy corresponding to the first specified information about the reasons, where this first processing policy contains: stopping the initiation of a registration request into a 5G SA communication network and initiating a registration request into a second communication network other than the 5G SA communication network. The first specified 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 the 5G network SA communication, registration failure due to refusal to register from the 5G SA communication network.

According to the above technical solution, if an anomaly occurs when registering in a 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 (as compared to protocol provisions) termination of registration is satisfied. If this condition is satisfied, the registration procedure is completed ahead of schedule, so that there is no need to repeat attempts several times according to the protocol, but one can register with another communication network to quickly resume providing services at that moment. Therefore, according to the technical solution of this application, the anomalous registration procedure can be completed ahead of schedule (earlier than required by the protocol), and registration can be carried out in another network if an anomaly occurs during registration in the network, to reduce the time when the registration anomaly occurs, and thereby solving the problem of frequent registration failures due to an anomaly in the network or poor signal conditions during registration in the communication network and improving the provision of services to the user.

In some exemplary embodiments, the second communication network is a long term evolution (LTE) communication network, and 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 condition of early termination of registration attempts in accordance with the information about the causes of registration failures and the cumulative number of failures, the mobile phone stops initiating registration requests to the 5G SA network and can at that moment 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 period of time affected by registration anomalies , and improving the provision of services to the user.

The M number can 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 Mth 5G SA registration request, that terminal device experiences 5G SA registration failure consecutively M-1 times. For example, if M is equal to 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 exemplary embodiments, if the number M is greater than 1 and less than N before the terminal device initiates the M-th 5G SA communications network registration request, the terminal device fails to register with the 5G SA communications network M-1 times sequentially.

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

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

In some exemplary embodiments, after the terminal device initiates 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 failed to register in the 5G SA communication network for the (M+1)th time, the terminal device receives information about the reason for the (M+1)th registration failure and the cumulative number of M+1 failures; And

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

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

In some possible implementations, after the terminal device has prohibited the initiation of a registration request for the 5G SA communication network within a first predetermined penalty time interval, the method further comprises, by the terminal device, initiating a registration request for the 5G SA communication network after the expiration of the first specified penalty interval. time.

In some exemplary embodiments, prior to the terminal device initiating a request to register with the 5G SA communication network upon expiration of a first predetermined penalty time interval, the method further comprises: receiving, by the terminal device, command information transmitted by the 5G SA communication network or a second communication network, wherein 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 a terminal device, a registration request to a 5G SA communication network comprises: initiating, by a terminal device, a registration request to a 5G SA communication network in accordance with the command information.

In some possible implementations, after the terminal device initiates a registration request for a 5G SA communications network, the method further comprises: prohibiting the terminal device from initiating a registration request for a 5G SA communications network during a second specified penalty time interval if the terminal device fails register in the 5G SA communication network for M consecutive times and if the information about the reasons for registration failure for the Mth consecutive time matches the first specified reason information.

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

In some exemplary embodiments, the method further comprises: pre-storing, by the terminal device, at least one match, wherein the collection of the at least one match comprises a first match and a second match, the first match being a match between the first specified cause information, the first predetermined number of failures and the first processing policy, and the second match is a correspondence between the second predetermined cause information, the second predetermined number of failures and the first processing policy.

If the cause information of the Mth registration failure matches the first specified cause information, the method further comprises: determining, by the terminal device, that the first predetermined number of failures corresponds to the first specified cause information according to the first correspondence.

In some possible implementations, the procedure for initiating, by a terminal device, a request to register with a second communication network other than a 5G SA communication network comprises: searching, by a terminal device, for at least one available communication network other than the 5G SA communication network in question, where this the plurality of at least one available communication network contains a second communication network, and the quality of the received reference signal from the second communication network belonging to this plurality 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 apparatus for processing registration anomalies. The apparatus is configured to implement the method according to the first aspect or any possible implementation of the first aspect. In particular, the apparatus may comprise 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 apparatus for processing registration anomalies. This apparatus comprises: a processor, the processor is coupled to a storage device, the storage device is configured to store a computer program or instructions, and the processor is configured to execute the computer program or instructions stored in the memory 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 hardware implements the method according to the first aspect.

Optionally, the hardware contains one or more processors.

Optionally, the hardware may also include a storage device coupled to the processor.

Optionally, the apparatus may include one or more storage devices.

Optionally, the memory 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 medium for storing information is provided. This computer-readable storage medium stores a computer program (which may also be referred to as an instruction or code) for implementing the method of 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 a fifth aspect, the present application provides an integrated circuit (chip) comprising a processor. The processor is configured to read and execute a computer program stored in a memory device to implement a method according to the first aspect or any of the possible embodiments of the first aspect.

Optionally, the integrated circuit further includes a memory device, and the processor is connected to this memory device through a circuit or 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 called an instruction or code), such that when executing the computer program, the computer implements the method according to the first aspect. A computer is a communication equipment.

Brief description of drawings

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

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

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

Fig. 4 is a simplified logic diagram of a method for handling registration anomalies in a communications network according to an embodiment of the present application.

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

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

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

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

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

Fig. 10 is a simplified logic diagram of a method for handling registration anomalies in a communications network according to an embodiment of the present application, applicable to a scenario where registration failure is caused by a communication channel being released (disconnected).

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

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

Fig. 13 is a simplified block diagram of communication equipment 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. It will be appreciated that the embodiments that will be described herein constitute only a portion, but not all, of the embodiments of the present application. Based on the options discussed in this application, all other options that can be obtained by a person skilled in the relevant field without any significant creative effort will fall within the 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), wideband code division multiple access (CDMA). 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” system (new radio, NR).

A terminal device is a device that provides a user with voice communications and/or a data connection, and in particular is a device that provides a user with voice communications, or a device that provides a user with a data connection, or a device , providing the user with both voice and data connections. This terminal device may comprise, for example, a hand-held device having a radio communication function, or a processing device connected to a radio modem. The terminal device may communicate with a backbone network device using a radio access network (RAN) device and exchange voice and/or data messages with the RAN. The terminal device can be a user equipment (UE), a radio terminal device, a mobile terminal device, a device-to-device (D2D) terminal device, a vehicle-to-everything (V2X) terminal device. , terminal device for machine-to-machine / machine-type communications, M2M/MTC, terminal devices for the 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 or other similar device. For example, the terminal device may be a mobile telephone (also referred to as a "cellular telephone"), a computer with a mobile terminal device, or a portable, handheld, hand-held or computer-integrated mobile device. For example, the 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), 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 processing power. For example, the terminal device may be a reader such as a bar code 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 additionally be a relay. Alternatively, it may be understood that any device capable of transmitting and receiving data communications 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 the terminal device may be a terminal device or may be hardware capable of supporting the terminal device to perform those functions, such as an integrated circuit system, and the 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 hardware configured to perform terminal functions is a terminal device.

The network device in 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 may be installed in the device. The device may be, but is not limited to: an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller, BSC), base transceiver station (BTS), home base station (home evolved NodeB, or home Node B, HNB), video band unit (BBU), access point (AP) in a wireless system fidelity (wireless fidelity, WIFI), radio relay node, transit radio communication 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 a transceiver point (TRP or TP) in the New Radio (NR) system, one or a group of antenna panels (containing several antenna panels) of a base station in 5G system, or may be a communications network node constituting a gNB or transmission point, such as a video band unit (BBU), 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 base station functions may be different.

In some deployments, a gNB may contain a centralized unit (CU) and a distributed unit (DU). The gNB may further include an active antenna unit (AAU). The CU module implements some functions of the gNB, and the DU module implements some functions of the gNB. For example, the CU module 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 RF signal processing and the active antenna. Since RRC control plane information ultimately becomes PHY layer information or information converted from PHY layer information, in such an architecture, higher layer signaling such as RRC control plane signaling can also be considered information transmitted by a DU module or transmitted by a pair of DU modules +AAU. It can be understood that the network device may be a device comprising one or more of the groups of CU module node, DU module node, and AAU module node. In addition, the CU may be divided into a network device in the RAN or a network device in the core network (CN). This application is not limited to this.

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

1) SA communication network: Autonomous communication network, which refers to the newly built 5G communication network, including the new base station, backhaul and core communication network. By introducing a new network element and interface, the SA communication network also applies new technologies such as communication network virtualization and software-defined large-scale 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 SA communications network will be greater than those of 3G and 4G systems.

In comparison with the SA communication network, there are also non-standalone communication networks, namely 5G NSA (non-standalone) networks, the deployment of which involves the deployment of a 5G communication network using the existing 4G network infrastructure. The 5G network carrier based on non-standalone architecture (NSA) carries only user data, and the control signaling of this 5G carrier is still carried over the 4G network.

2) Registration in the communication network

To receive the service provided by the 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 terminal device is powered on. For example, assuming that the terminal device is currently in the 5G SA communication network, after powering 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 a terminal device leaves the area where it is currently registered (the current registration area) and enters a new tracking area (TA), the mobile registration update procedure is started. For example, if a terminal device moves from an LTE communications network where it is currently registered to a 5G SA communications network, the terminal device initiates registration with the 5G SA communications network to perform a mobile registration update.

It should be noted that the above example lists two types of registrations in a communications network. The embodiments of this application do not limit the type of registration in a communication network. It can be understood that, when actually implemented, the registration procedure in a communication network may be some other type of procedure for registration in a communication network, such as periodic registration. Periodic logging can be triggered by the periodic timer T3512, which transmits signals from the communications network so that when the periodic timer expires, the periodic logging 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 shows a simplified diagram of the architecture of a communication system according to one of the variants of this application. The communication system shown in FIG. 1 may include a terminal device 01 and a communication network SA 02. As an example, the communications network SA 02 may comprise an access network device (eg, a gNB) and a core communications network device (eg, a 5G communications core network device, designated 5GC). Accordingly, the SA communication network may be referred to as a 5G SA communication network. Radio communication can be established between the terminal device 01 and the 5G SA communication network 02, so that the SA communication network can provide communication services to the terminal device 01. The terminal device 01 first needs to initiate a registration request to the 5G SA communication network 02, and the device will be able to obtain authorization to access the service provided by the 5G SA communication network 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 core communication network device as an example. It will 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 containing one or more terminal devices. This is not limited in this application.

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

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

As an example, after the terminal device transmits a registration request message to the SA communication network, if the terminal device receives the registration acceptance message returned by the SA communication network, it is considered that the terminal device has successfully registered with the SA communication network. This is a normal registration scenario in a communication network.

As another example, if a terminal device receives a registration refusal message returned from the SA communication network, or the terminal device does not receive a registration response message (whether a registration acceptance message or a registration refusal message) within a specified period of time after transmission registration request messages to the SA communication network (one of the protocols uses a T3510 timer that counts 15 seconds), or an anomaly occurs in the lower-level communication channel, registration of the terminal device fails. This is a communication network registration anomaly scenario.

As shown in part (a) of FIG. 1, the terminal device 01 initiates registration (initial registration or mobile registration update) in the communication network SA 02. As shown in part (b) of FIG. 1, the terminal device 01 failed to initiate registration in the communication network SA 02, in other words, an anomaly occurred when registering in the communication network. For such an anomaly in registration, the corresponding technique proposes a registration processing policy: if the network registration fails, the terminal device accumulates the number of registration attempts (registration attempt 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 again initiates registration in the communication SA network (this is also called initiation of registration in the SA communication network). 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 SA communication network during this period of time. It should be noted that 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 network 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 SA communication network, described in detail.

For example, in FIG. 3 is a simplified logic diagram of a method 200 for handling an anomaly in a communications network registration as used in the prior art. The 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 the counter below.

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

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

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

S202. If registration fails, the terminal devices accumulate in counter 1 (counter=1) and start timer T3511.

Timer T3511 is set to 10 seconds.

S203. When timer T3511 expires, the terminal device again initiates registration with the SA communication network (referred to as the 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 a set duration of timer T3511. On the one hand, if the terminal device receives the registration acceptance message returned as feedback by the SA communication network within 10 seconds after transmitting the registration request, the 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 transmission of the registration request (eg, the core communication network device in the SA communication network did not respond to the registration request), the registration of the terminal device failed.

S205. When timer T3511 expires, the terminal device initiates registration with the SA communication network (called 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 terminal device registration procedure succeeds or fails, refer to the detailed description of successful registration and unsuccessful registration in the above description of step S204, which will not be repeated here.

S207. When timer T3511 expires, the terminal device again initiates registration with the SA communication network (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 terminal device registration procedure succeeds or fails, refer to the detailed description of successful registration and unsuccessful registration in the above description of step S204, which will not be repeated here.

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

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

For a description of the procedure for determining whether the terminal device registration procedure succeeds or fails, refer to the detailed description of successful registration and unsuccessful registration in the above description of step S204, which will not be repeated here.

The duration corresponding to the T3502 timer 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 can initiate registration with other communication networks. When the timer T3502 expires, the terminal device can determine whether to initiate registrations in the SA communication network again, according to the actual situation. If the terminal device again initiates registration in the SA communication network, 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 timer T3510 expiring during the initial registration or mobile registration process in the SA communication network (eg, the core communication 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 methods used in the prior art to handle a situation where an anomaly occurs in the registration process. As shown in Table 1, in the above prior art solutions, when an anomaly occurs in the SA communication network registration process, the terminal device must wait 10 seconds and then re-initiate 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 attempts is 5, so the registration procedure in the SA communication network can only complete after 5 failures, which takes more than 40 seconds. During this period, the terminal device is in a state of waiting in the SA communication network, in other words, regardless of the reason for registration failure, the terminal device will continue to attempt to register in the SA communication network 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 SA communication network, the registration procedure takes a long time so that services cannot be quickly resumed.

Table 1

No. Reason for registration failure Scenario provided in the relevant protocols A method of handling a situation in a known appropriate technique 1 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 re-initiates logging 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 on the SA communications network for a period of time. 2 No response from the core network Timer T3510 has expired

In light of this, one embodiment of the present application proposes a method for handling an online registration anomaly. 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 process of registration in the SA communication network, so as to leave this communication network earlier and return to the LTE communication network for registration, thereby reducing the length of time affected by registration anomalies and improving the user experience of the services.

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

In fig. 4 shows a logical diagram for processing a registration anomaly in a communication network according to one of the variants of this 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 specified integer. Optionally, the number N may be negotiated between the terminal device and the 5G SA communication network or provided by the protocol (for example, N may be 5). This is not limited in this application. For convenience of description, the number N equal to 5 is used in the following 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 a first (in other words, initial) registration request to the 5G SA communication network. 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 sequentially M-1 times. For example, if M is equal to 2, the terminal device initiates a second registration request to the 5G SA communication network after the first registration attempt to the 5G SA communication network fails. If M is equal to 3, the terminal device initiates a third registration request to the 5G SA communication network after attempts to register to the 5G SA communication network have failed two consecutive times. If M is equal to 4, the terminal device initiates a fourth registration request to the 5G SA communication network after attempts to register 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 SA communication network, which is actually implemented by transmitting a registration request message to the 5G SA communication 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 or an access and mobility management function (AMF) network element). For convenience of consideration, some descriptions of the specific signaling interaction between the terminal device and the communication network element are omitted below.

S320. If the Mth registration attempt fails, the terminal device receives information about the reasons for the failure of the Mth registration attempt and the cumulative number M of failures.

In the exemplary embodiment of the present application, the cumulative failure number M is a number obtained by accumulating the number of failures if the terminal device fails to register M consecutive times. It can be understood that the terminal device counts another one each time the terminal device fails to register with the 5G SA communication network, and accumulates these units to obtain a cumulative failure number of 1 after the first failed time. By analogy, after the (M-1)th registration failure, a cumulative number of M-1 failures is accumulated. After the Mth registration failure, a cumulative number of M failures is accumulated. This cumulative number M of failures may also be called 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 why the first registration attempt failed 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 the 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 the 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 the cumulative number of failures equal to 4.

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

Method 1: If a terminal device successfully registers with the 5G SA communication network, the terminal device can update the current cumulative failure count to zero.

Method 2: If a terminal device is turned off or switched to airplane mode, the terminal device can update the current cumulative number of failures to zero, setting it to zero.

Optionally, the reason for the Mth registration failure may be that the 5G SA communication network (such as the core communication network) did not respond to the registration request and registration failed, or it may be that the 5G SA communication network (such as the core communication network communication network) returns a registration refusal message, so registration failed. Registration failure may also be caused by a low-level failure of the terminal device, or may be caused by some other possible reason that can be determined according to actual applications. This is not limited in the embodiments of this application. There are various possibilities in which registration failure is due to a low-level failure of the terminal device, such as registration failure due to failure to establish a communication channel, failure of registration due to release (disconnection) of a communication channel after establishment, or some other possible situation, which can be determined according to actual applications. This is not limited in the embodiments of this application.

In fig. Figure 5 shows a simplified diagram of the system protocol stack architecture. For simplicity of description, only a few levels related to the present technical solution will be considered here. As shown in FIG. 5, the system protocol stack architecture contains, 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 called the upper layer, and the RRC control layer, PDCP protocol layer, RLC control layer, MAC control layer, and PHY layer are collectively called lower layers. As noted in this context, a lower-layer link failure or low-layer anomaly may mean that the anomaly has occurred 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 occurred at several low levels.

As an example, the following Table 2 lists a number of reasons that may cause a terminal device to fail to register with a communications network, and the protocol scenarios that correspond to those reasons. As shown in Table 2, the set of reasons associated with registration failure may contain the following four items: (1) Reasons associated with failure to establish a communication channel (in other words, registration failure due to failure to establish a communication channel), such as communication link failure, suspension due to switching between systems, random access failure and loss of communication network. (2) Reasons 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 failure of recovery, release (disconnection) of the communication channel, other reasons, redirection from the standard communication network NR to LTE communication network, upper layer anomaly, RRC control anomaly and lowest layer anomaly. (3) No response from the core communication network, in other words, registration failure due to no response from the communication network. (4) Refusal of registration from the core communication network during the initial registration process, in other words, registration failure due to a registration refusal received from the communication network. Failure to establish a communication link and disconnection (release) of a communication link correspond to the failure situations of the lower layers (lower layer failure) provided in the protocol, and the lack of response from the core communication network corresponds to the situation in the T3510 timer expiration scenario (T3510 timeout) provided in the protocol.

table 2

It should be noted that Table 2 also indicates a reason for registration failure that is not described in the protocol: failure to register from the core communications network (reason #9). Although the registration failure scenario from the communication network (reason #9) during the initial registration process is not described in the protocol, to actually implement this scenario, you can refer to how the situation is handled in the T3510 timer expiration scenario and in the lower layer failure scenario.

In fig. 6 is a simplified logic diagram of the procedure for establishing a radio link 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 device, and then the terminal device establishes an RRC control connection in accordance with this RRC control connection establishment parameter. After the RRC control connection establishment is completed, the terminal device establishes a radio link with the communication network.

As shown in FIG. 2, fig. 5 and fig. 6, the precondition for a terminal device to successfully transmit a registration request message to a communication network is as follows: a radio channel has been successfully established between the terminal device and a radio access network (RAN), and the channel carries out normal, mainly signaling interaction between the terminal device and the RRC control level. In other words, during 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 at the RRC control layer, link establishment may fail, which further causes registration failure. In addition, before the network responds with a registration accept message, if the radio access network releases (disconnects) the radio channel, registration will also fail.

In addition, since the random access procedure is a necessary procedure for establishing a radio channel between the terminal device and the radio access network, only after the completion of the random access procedure can communication for communication between the access network device (base station) and the terminal device be normally carried out. Only after successful completion of the random access procedure will the terminal device be able to transmit an RRC control connection establishment request to the radio access network (RAN). This procedure is represented primarily by the appropriate interaction between the RRC control layer and the levels below the RRC control layer. Therefore, if the random access procedure fails, communication link establishment fails, causing registration to fail.

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 reasons for registration failure, the terminal device obtains information about the reason for registration failure in different ways. In the following, in accordance with the above Table 2, each registration failure reason is described in detail, and a possible embodiment of a terminal device for obtaining information about the reasons for registration failure corresponding to a particular registration attempt is described.

First, reasons relating to the failure of the communication channel establishment will be given, including the failure of the RRC radio control channel establishment in the process of registration in the SA communication network.

1) Link Failure: This means that an anomaly occurs at the RRC control layer causing 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 may be reflected in the log content generated during the registration process. For example, during the registration process in the communication SA network, if the terminal device fails to establish a communication link, the RRC control layer responds with a communication link failure message sent by the NAS layer and records an interaction message to generate log content from which it can be learned. that the link establishment failure is caused by an RRC control connection establishment failure. Accordingly, the terminal device can obtain information about the reason for registration failure 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 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 the communication link to fail to be established.

In this case, information about the reason for registration failure may be reflected in the log content generated during the registration process. For example, in the process of registration in an SA communication network, 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 known that the suspension has occurred. switching between systems causes failure to establish a communication channel. Accordingly, the terminal device can obtain information about the reason for registration failure from the content of the log.

3) Random Access Failure: This means that the random access procedure fails during the link establishment process, causing the link establishment to fail.

In this case, information about the reason for registration failure may be reflected in the log content generated during the registration process. For example, in the process of registration in the SA communication network, a message related to random access in the process of establishing a communication channel by the terminal device may indicate a failure of the random access, 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 random access failure is causing the communication link to fail. Accordingly, the terminal device can obtain information about the reason for registration failure from the content of the log.

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

In this case, information about the reason for registration failure may be reflected in the content of the registration log during the registration procedure. For example, during the process of registration in the SA communication network, the terminal device was unable to establish a communication channel, and the signal quality in the SA communication network is below the threshold level, which does not satisfy the residency criterion. This is recorded to generate log content from which it can be recognized that the loss of the communications network causes the communications link to fail. Accordingly, the terminal device can obtain information about the reason for registration failure from the content of the log.

Secondly, the set of reasons related to the release (disconnection) of a communication channel includes reasons related to the fact that an RRC control radio channel is released (disconnected) after the RRC control radio channel has been successfully established in the registration process in the SA communication network.

5) Recovery 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), causing that link to be released (disconnected).

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

6) Communication channel release (disconnect): A connection failure on the RRC control channel causes the communication channel to become released (disconnected).

This scenario cannot be observed from the radio interface signaling, but can be observed from the log or phenomenon: during the registration process in the SA communication network, after the establishment of the RRC control channel, if at a 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, report the link anomaly to the RRC control layer.

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

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

8) Redirection from NR network to LTE network: This means that the communication channel is released (disconnected) due to redirection from NR network to LTE network.

In this scenario, the radio interface signaling can be observed. During the registration process in the communication SA network, after establishing the RRC control channel, the communication network transmits an RRC control release message (RRC Release), which carries redirection information to the LTE network.

9) Upper layer anomaly: An anomaly occurs at the NAS layer level, causing the communication channel to become released (disconnected).

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

10) RRC Control Anomaly: An anomaly occurs at the RRC control layer, causing the communication channel to be released (disconnected).

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

11) Low Layer Anomaly: This means that an anomaly occurs at a lower layer (such as the MAC, PDCP, or PHY control layers), causing the communication channel to release (disconnect).

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

Third, timer T3510 expired: After the terminal device sent 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 is not correctly received by the communication network, the communication network transmits a registration failure message to the terminal device, and this message contains the value of the registration failure reason. After the terminal device transmits a registration request message to the communication network, the communication network transmits a registration refusal message to the terminal device, and this message contains a registration refusal reason value. For example, the magnitude of the reason is #9.

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

The above word “corresponds” can be understood as full 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 specified similarity threshold (for example, 80%), the two pieces of information can be considered consistent. If the degree of similarity obtained by comparing Information 1 and Information 2 is less than a given similarity threshold, the two pieces of information can be considered inconsistent. In particular, this can be determined according to actual usage requirements and is not limited in the present embodiment.

Optionally, in this embodiment of the present application, the first specified cause information may indicate that the registration failure occurred due to a 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 to indicate that the release (disconnection) of the communication channel has occurred). The first specified cause information may also indicate that registration failure occurred due to no response from the 5G SA communication network, or may indicate that registration failure occurred due to registration failure from the communication network. Alternatively, the first cause information given may indicate any one of the 13 reasons for enrollment failure listed in Table 2 above. To simplify the description, only some reasons for registration failures are used below as examples.

In some embodiments, the terminal device may previously store at least one match, and each such match represents a match between a given cause information, a given number of failures, and a processing policy. For example, the at least one correspondence is a correspondence between the first predetermined cause information, the first predetermined number of failures, and the first processing policy, and the correspondence between the second predetermined cause information, the second predetermined number of failures, and the first processing policy. The first processing policy may be that the terminal device stops initiating a registration request to a 5G SA communication network and initiates a registration request to a second communication network. As an example, refer to the matching list or the specified cause information list shown in the following Table 3, the matching list example shows three matches: if the specified cause information indicates a communication link failure, the corresponding specified number of failures is 2, and the corresponding processing policy is the first processing policy; if the specified cause information indicates a random access failure, the corresponding specified failure number 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

Specified cause information Set number of failures Processing Policy Indicates communication link failure 2 The terminal device stops the initiation of a registration request to the 5G SA communication network and initiates a registration request to the second communication network Indicates random access failure 2 Indicates the release (disconnection) of a communication channel 1

It should be noted that, for ease of description, Table 3 above lists only three different types of specified information about the causes and corresponding numbers of failures. It can be understood that in actual implementation, predetermined failure numbers corresponding to these three types of predetermined cause information may be set according to the actual situation. In addition to this, other versions of the specified cause information and corresponding failure numbers other than the above three types of specified 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. This is not limited in this application.

It should further be noted that the example used above provides, for illustration purposes, three different types of specified cause information, all corresponding to the same processing policy. These embodiments of the present application may further comprise the following implementations: different specified cause information may be subject to different processing policies. For example, if the predetermined cause information indicates a random access failure, the corresponding processing policy may be that the terminal device stops initiating the registration request to the 5G SA communication network and initiates the registration request to the second communication network. If the predetermined 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, so-called “race” registration is carried out, when registration requests are initiated in both communication networks at once, 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 specified in combination with factors such as communication network situation, terminal device characteristics, and service impact, and this relationship may also be adjusted according to changes in the situation in the communication network. Optionally, a particular relationship can be considered comprehensively by analyzing a large number of log entries related to the problems and taking into account various positions, network situations of different equipment suppliers, 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 cause information of the Mth registration failure and the cumulative number of failures M with the predetermined cause information and the predetermined number of failures in the above pre-stored ratio list for determining whether the cause information of the Mth failed registration attempt matches the first specified cause information, and whether the cumulative number of failures M is not less than the first specified number of failures corresponding to the first specified cause information, in other words, whether the current scenario satisfies the registration anomaly condition for early registration.

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

If the terminal device determines that the cause information of the Mth registration failure corresponds to the first specified cause information, and that the cumulative number of failures M is not less than the first specified number of failures corresponding to the first specified cause information, in other words, satisfies the early condition ) registration is completed, the terminal device continues to execute the next step S340. Otherwise, the terminal device continues to execute the next step S350.

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

In the exemplary embodiment of the present application, if the cause information of the Mth registration failure corresponds to the first specified cause information, and the cumulative number of failures M is not less than the first specified number of failures corresponding to the first specified 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 failure condition according to the registration failure cause information and the cumulative number of failures, the terminal device may temporarily stop the initiation registration request to the 5G SA communication network and may initiate transmission of the registration request to the second communication network at that time.

In this embodiment of the present application, Table 4 shows the processing methods in accordance with the present application and the processing methods used in the prior 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 SA communication network registration process, the terminal device needs to wait 10 seconds before re-initiating the registration according to the protocol. If an anomaly still appears 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 registration procedure in the SA communication network can only be completed after 5 unsuccessful attempts, which takes more than 40 seconds. During this period, the terminal device is in a state of waiting in the SA communication network, in other words, regardless of the reasons for registration failure, the terminal device will continue to attempt to register in the SA communication network after waiting for a period of time while registration attempts remain unsuccessful. Unlike the prior art, according to the processing method in the present application, if an anomaly occurs during the registration process of a terminal device in an SA communication network, the terminal device obtains information about the reason for registration failure and the cumulative number of failures to determine whether the condition for early registration is satisfied. (early) registration completion. If the condition is satisfied, the current round of registration in the SA communication network can be completed early. At this time, the terminal device can register with another communication network (LTE communication network) to provide services in order to realize fast exit.

In light of this, the technical solutions of the present application can solve the problem of frequent failures of registration attempts due to anomalies in the communication network or poor signal conditions during the registration process in the SA communication network, so as to leave the network sooner and return to the LTE communication network for registration, thereby thereby reducing the time affected by anomalies in the registration process and improving the quality of service for the user of the services.

Optionally, the step where 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 registration fails in the 5G SA communication network, this second communication network may be provided by the protocol or may be negotiated between the terminal device and the 5G SA communication network. In an example in which the second communication network provided by the protocol is an LTE communication network, if a terminal device fails to register with the 5G SA communication network and it satisfies the early registration completion condition, the terminal device may then register with the LTE network. communication in accordance with the protocol.

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

Optionally, the received reference signal quality parameter may be, but is not limited to, at least one of the following: received signal strength indication (RSSI), 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 communication network defined by that communication network, the terminal device may still choose to register with such at least one available communication network.

Optionally, in the present application, the second communication network may be an LTE communication network. For example, if a mobile phone fails to register with a 5G SA communication network several times in succession, if it is determined that the current registration anomaly scenario satisfies the early registration termination condition according to the registration failure cause information and the cumulative number of failures, the mobile phone stops initiation of a registration request to the 5G SA communication network and may at this moment initiate the transmission of a registration request to the LTE communication network. Therefore, according to the communication network registration anomaly processing method proposed in this 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 services for the user.

S350. The terminal device initiates the (M+1)th registration request to the 5G SA communication network upon expiration of the first timeout interval.

In some embodiments, if the M-th registration failure cause information does not correspond to the first predetermined cause information, or if the M-th registration failure cause information matches the first predetermined cause information and the cumulative number of failures M 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 upon expiration of the first timeout interval.

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

In some embodiments, if the current registration anomaly scenario satisfies the condition for early termination of registration, that communication network SA may be penalized, such as disabling some functions of the communication SA network, in other words, not initiating registration with the communication SA network for a period of time. time. A progressive penalty method can be used, the first penalty interval is T1, the second penalty interval is T2, the third penalty interval is T3, etc. In this case, T3 > T2 > T1, and the parameters T1, T2 and T3 can be specialized according to the requirements. After the penalty interval duration has expired, functions for operating in the SA communication network may be restored, and the terminal device configures a parameter to decide whether to immediately initiate registration in the SA communication network.

In particular, an appropriate length of the penalty interval can be set in advance for a given cause information. Accordingly, if the terminal device satisfies the condition for early completion of registration, 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 for the first predetermined cause information. Specifically, if the cause information of the Mth registration failure matches the specified cause information, and the cumulative number of failures M is not less than the first specified number of failures corresponding to the first specified cause information, in other words, the condition for early termination of registration is satisfied, the terminal device may prohibit initiation of the 5G SA communication network registration request within a first predetermined penalty time interval corresponding to the first predetermined reason information.

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

As an option, different predetermined cause information may be correspondingly specified using different predetermined penalty time intervals. For example, if the predetermined cause information indicates that the registration failure occurred due to a communication link failure, the corresponding predetermined penalty time interval may be 12 minutes. If the predetermined cause information indicates that the registration failure occurred due to 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 is not limited to this application.

According to the network registration anomaly processing method proposed in the embodiments of the present application, if an anomaly occurs during registration in a 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 of registration is satisfied. If this condition is satisfied, the registration procedure ends early, there is no need to retry several times according to the protocol, and one can register with another communication network to quickly resume services at that 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 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, referring to FIGS. 4, as shown in FIG. 7, after step S350, method 300 may further comprise the following steps S360 to S380.

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

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

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

If the (M+1)th registration failure cause information corresponds to the second predetermined cause information, and the cumulative number of failures M+1 is not less than the second predetermined number of failures corresponding to the second predetermined cause information, the terminal device continues to carry out 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 a first processing policy corresponding to the second specified cause information.

To describe 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.

It should be noted that the second predetermined cause information and the first predetermined cause information may be the same or different. In the same situation, the second given number of failures is equal to the first given number of failures.

In some embodiments, after the terminal device successfully registers with the second communication network and after a first predetermined penalty time interval has elapsed, if a certain condition is satisfied, the terminal device may return to the 5G SA communication network to register. 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 upon expiration of a first predetermined penalty time interval, the terminal device may autonomously return to the 5G SA communications network to register.

Method 2: The 5G SA communication network can command the terminal device to return to the 5G SA communication network.

After the first predetermined penalty time interval, the 5G SA communication network may transmit 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 SA communication network, the terminal device may initiate transmission of a registration request to the 5G SA communication network according to the command information, and the command information is used as an instruction to initiate transmission of the registration request to the 5G SA communication network.

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

For example, assuming that a terminal device is currently resident in a second communication network, the terminal device collects a received reference signal quality parameter from the second communication network and received signal quality parameters from other communication networks (including a 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 a received reference signal in each communication network according to a 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 include the second network instructing 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 that in the second communication network.

In another example, the protocol may provide that upon expiration of a first predetermined penalty time interval, the second communication network commands the terminal device to return to the 5G SA communication network to register.

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

For example, assume that the specified number of failures corresponding to the first specified cause information is 2, if the terminal device fails to register with the 5G SA communication network two times consecutively and the reason information of the second registration failure corresponds to the first specified reason information, the terminal device prohibits initiation of a registration request to the 5G SA communication network within 12 minutes and at this time registers in the LTE communication network. Next, when the terminal device returns to the 5G SA communication network for registration, then if this terminal device fails to register to the 5G SA communication network two times successively and the reason information for the second registration failure still matches the first specified reason information, the terminal device prohibits initiation of a registration request for the 5G SA communication network within 2 hours. The length of the penalty interval is increased from 12 minutes to 2 hours, which may reduce the time a user's service is affected.

In light of the potential challenges in the registration anomaly scenarios above, based on actual user experience, appropriate processing policies have been further developed for scenarios in which registration failure occurred due to link establishment failure, random access failure, or channel release (disconnection). communications. For a description of specific implementation options, see the following options (from the first option to the third option). The following embodiments are all examples described using a case in which the second communication network is an LTE communication network. It should be noted that the scenarios implemented in the current product represent 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 in which registration failure occurs due to communication link failure

The first option logs out of the current communications network for a scenario in which registration failure occurred due to a communications link failure during the registration process (in other words, if the registration attempt on the 5G SA communications network was unsuccessful and registration occurred on a second communications network). Assuming that the specified cause information indicates that the failure of the registration attempt was due to a communication link failure, the corresponding specified number of attempts is 2; and assume that the method for progressively increasing the penalty is as follows: the SA communication network sets a penalty interval of 12 minutes (in other words, the first predetermined time penalty interval) in the first round, and sets a penalty interval of 2 hours (in other words, the second predetermined time penalty 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, completes the registration procedure in the SA communication network, and penalizes the SA communication network where the duration The first penalty interval is 12 minutes. After the penalty interval time has expired (after 12 minutes), the terminal device may resume use of the SA communication network functionality and re-initiate registration with the SA communication network. 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 SA network early and sets a penalty interval for that communication SA network (“penalizes” the network) of 2 hours. To simplify the description, in the following the symbol C is used to represent the value of the cumulative number of failures.

In fig. 8 is a simplified logic diagram of a method for handling registration anomalies in a communications network according to an embodiment of the present application, applied to a scenario in which registration failure is caused by a communications 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 SA communication network.

If a terminal device is turned on (assuming that the terminal device accesses the SA communications network by default after power-on) or switches from another system to the SA communications network, the terminal device initiates the transmission of a registration request to the SA communications network to access that SA communications network. SA communication network.

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

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

The registration procedure may fail during the registration process for a number of reasons, however, the current registration anomaly scenario may not satisfy the early registration 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, lack of response from the communication network or registration refusal received from the communication network) from the specified list of specified information about the reasons, but the cumulative number of failures has not reached the corresponding specified number. Therefore, the current registration anomaly scenario does not satisfy the early registration termination condition, and the terminal device may continue to attempt to register with the SA communication network.

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 on the SA network for communication, and may continue attempting to register with the SA communications 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 SA communication network.

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

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

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

S416. If the cause of the current registration failure is a communication link failure, 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, the terminal device prohibits the initiation of a registration request to the SA communication network for 12 minutes, and initiates transmission of the registration request to the network LTE communications.

Since the communication link failure causing 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 to register.

According to related technical solutions, if it fails to register two times consecutively, the terminal device accumulates a number of failed attempts equal to C=2 and starts a timer T3511 with a duration of 10 seconds, during which the terminal device waits on the SA network for communication and continues to try to register. Unlike the prior art, in the present application, if failure to register consecutively two times is caused by a communication link failure, the terminal device may prematurely complete the current round of registration in the SA communication network, set a penalty interval in the SA communication network ("penalize" the network) for 12 minutes , disable SA communication network functionality and do not initiate registration with the SA communication network. At this time, the terminal device can return to the LTE communication network to register in order to provide service when quickly switching between networks.

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

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 regains the functionality to operate in the SA communication network and can return to the SA communication network to register again, and carries out steps S417 to S422. For a 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 as the first round of the registration procedure, and steps S417 to S422 can be considered as 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 length of the penalty interval in the second round of the registration procedure is increased to reduce the time affected by the registration anomaly. For details, see the description of step S422. If the cause of the current registration failure is a communication link failure, and the cumulative number of failures is equal to the corresponding predetermined number 2, the terminal device prohibits the initiation of a registration request to the SA communication network for 2 hours, and initiates transmission of the registration request to the LTE communication network. The duration of the penalty interval increases from 12 minutes to 2 hours.

In the prior art, if registration failure occurs a second time, the terminal device accumulates a failure number of C=2 and starts a timer T3511 of 10 seconds during which the terminal device waits on the SA network for communication. Unlike the known technology, according to this application, the terminal device can prematurely complete the current round of the registration procedure in the SA communication network in the second round of the registration procedure at this moment, sets the duration of the penalty interval (“penalizes”) in the SA network equal to 2 hours, disables the functional SA network capabilities and does not initiate registration in the SA communication network. At this time, the terminal device can return back to the LTE communication network to register in order to provide service when quickly switching between networks.

In the technical solution proposed in the first embodiment, according to this application, the registration procedure in the SA communication network can be completed early if the reason for the second failure of the registration procedure is a failure of the communication channel, and there is no need to continue accumulating the number of registration attempts (corresponding to the cumulative number of failures). In addition to this, the SA communication network applies progressively increasing penalty intervals, so that the duration 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 the 12 minute ban after five failed registration attempts, the prior art increases the penalty interval 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, the terminal device can quickly transition to the LTE communication network if an anomaly occurs during the registration process of the 5G SA network, thereby reducing the time affected by the registration anomaly and improving the provision of service to the user.

Second option: Scenario in which registration failure occurs due to random access failure

In the second option, a network exit configuration 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 to the 5G SA communication network fails, registration to the second communication network is performed ). Assuming that the specified cause information indicates that the registration failure occurred due to random access failure, the corresponding specified number of failures is 2; and assuming that the policy of progressively increasing penalty intervals is as follows: in the SA communication network, the duration of the penalty interval ("penalty") is set to 12 minutes (in other words, the first specified penalty interval time) in the first round, and the duration of the penalty interval is 2 hours (in other words, a second specified penalty time interval) in the second and each of the 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 early termination condition of the registration procedure is currently satisfied, terminates the registration procedure in the SA communication network, and sets a penalty interval in that SA communication network (“ “penalizes” the network), where the first duration of the penalty interval is 12 minutes. After the penalty interval expires (after 12 minutes), the terminal device may resume its SA communications network functionality and again initiate a registration request to the SA communications network. In the second round of the registration procedure, if the reason for the second registration failure is still a random access failure, the terminal device terminates the SA communication network registration procedure early and sets the SA communication network penalty interval to 2 hours.

In fig. 9 is a simplified logic diagram of a method for processing a registration anomaly in a communications network according to an embodiment of the present application, applied to a scenario in which a registration failure occurs due to a 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 SA communication network.

If a terminal device is turned on or switched from another system to an SA communication network, the terminal device initiates transmission of a registration request to the SA communication network for access to that SA communication network.

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

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

The registration procedure may fail during the registration process for a number of reasons, however, the current registration anomaly scenario may not satisfy the early registration 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 be an anomaly in establishing a communication channel, a lack of response from the communication network, or a registration refusal received from the communication network) from the specified list of specified information about the reasons, but the cumulative number of failures has not reached the corresponding specified number. Therefore, the current registration anomaly scenario does not satisfy the early registration termination condition, and the terminal device may continue to attempt to register with the SA communication network.

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 early registration 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 on the SA network for communication.

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

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

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

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

S516. If the cause of the current registration failure is a communication link failure, 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, the terminal device prohibits the initiation of a registration request to the SA communication network for 12 minutes, and initiates transmission of the registration request to the network LTE communications.

Since the communication link failure causing 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 related technical solutions, if it fails to register two consecutive times, the terminal device accumulates a number of failed attempts equal to C=2 and starts a timer T3511 with a duration of 10 seconds, during which the terminal device waits in the SA network for communication and continues to attempt to register after expiration the duration of the timer, so the registration procedure takes a long time. In the technical solution of the present application, if failure to register consecutively two times is caused by random access failure, the terminal device may terminate the current round of registration in the SA communication network early, set a penalty interval in the SA communication network ("penalize" the network) to 12 minutes, disable the functionality to work in the SA communications network and does not initiate registration in the SA communications network. At this time, the terminal device can return to the LTE communication network to register in order to provide service when quickly switching between networks.

In contrast, in the technical solution of the present application, if an anomaly occurs during the SA communication network registration process and if the cause of the second anomaly is a random access failure scenario, the SA communication network registration procedure can be completed early and the terminal device returns to the LTE network connection 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 regains the functionality to operate in the SA communication network and can return to the SA communication network to register again, and carries out steps S517 to S522. For a 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 as the first round of the registration procedure, and steps S517 to S522 can be considered as 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 length of the penalty interval in the second round of the registration procedure is increased to reduce the time affected by the registration anomaly. For details, see the description of step S422. If the cause of the current registration failure is random access failure, and the cumulative number of failures is equal to the corresponding predetermined number 2, the terminal device prohibits initiation of the registration request to the SA communication network for 2 hours, and initiates transmission of the registration request to the LTE communication network. The duration of the penalty interval increases from 12 minutes to 2 hours.

In the prior art, if registration failure occurs a second time, the terminal device accumulates a failure number of C=2 and starts a timer T3511 of 10 seconds during which the terminal device waits on the SA network for communication. Unlike the prior art, according to the present application, the terminal device can complete the current round of the registration procedure in the SA communication network ahead of schedule (compared to the protocol) in the second round of the registration procedure at this moment, sets the duration of the penalty interval (“penalizes”) in the SA network, 2 hours disables functionality for the SA network and does not initiate registration with the SA communications network. At this time, the terminal device can return back to the LTE communication network to register in order to provide service when quickly switching between networks.

In the technical solution proposed in the second embodiment, according to the present application, the registration procedure in the SA communication network can be completed early if the reason for the second failure of the registration procedure is random access failure, and there is no need to continue accumulating the number of registration attempts (corresponding to the cumulative number of failures). In addition to this, the SA communication network applies progressively increasing penalty intervals, so that the duration 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 the 12 minute ban after five failed registration attempts, the prior art increases the penalty interval 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, the terminal device can quickly transition to the LTE communication network if an anomaly occurs during the registration process of the 5G SA network, thereby reducing the time affected by the registration anomaly and improving the provision of service to 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 option, a network exit configuration to another communication network is proposed for a scenario in which the registration failure occurs due to the release (disconnection) of the communication channel with the network during the registration process (in other words, if 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: in the SA communication network, the duration of the penalty interval ("penalty") is set to 12 minutes (in other words, the first specified penalty interval time) in the first round, and the duration of the penalty interval is 2 hours (in other words, a second specified penalty time interval) in the second and each of the subsequent rounds. For example, if the reason for the second registration failure is the release (disconnection) of the communication channel from the network in the first round of the registration procedure, the terminal device determines that the condition for early termination of the registration procedure is currently satisfied, completes the registration procedure in the SA communication network and establishes an SA in this network communication penalty interval (“fines” the network), where the first duration of the penalty interval is 12 minutes. After the penalty interval has expired (after 12 minutes), the terminal device may resume its functionality to operate in the SA communication network and again initiate a registration request to the SA communication network. 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 in the SA communication network early and sets a penalty interval in the SA communication network equal to 12 hours.

In fig. 10 is a simplified logic diagram of a method for handling a registration anomaly in a communications network, according to an embodiment of the present application, applied to a scenario in which registration failure occurs due to a communication channel being released (disconnected) from 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 SA communication network.

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, the terminal device initiates transmission of a registration request to the communication network SA 02 for access to the communication network SA 02.

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

The terminal device can determine whether the current registration anomaly scenario satisfies the condition of early termination of the registration procedure according to information about the cause of registration failure and the cumulative number of failures. For example, if it is determined that the current registration failure occurred due to a release (disconnection) of the communication channel with the network, and the cumulative number of failures C is not less than the corresponding predetermined number of failures 2, it may 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 condition of early termination of the registration procedure, the terminal device continues by executing the next step S613. If it is determined that the current registration anomaly scenario does not satisfy the early termination condition of the registration procedure, the terminal device may start a timer (eg, T3511), wait while remaining in the SA communication network, and continue attempting to register after the timer has expired.

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

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

In prior art solutions, if registration fails 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 on the SA network for communication and continues to attempt to register after the timer duration has expired. , so the registration procedure takes a lot of time. According to the technical solution of the present application, if registration failure occurs due to the release (disconnection) of the communication channel with the network, the terminal device can prematurely complete the current round of registration in the SA communication network, set a penalty interval in the SA communication network (“fine” the network) with a duration of 12 minutes, disable functionality for working in the SA communication network and do not initiate registration in the SA communication network. At this time, the terminal device can return to the LTE communication network to register in order to provide services and achieve rapid switching to this network. In contrast, in the technical solution of the present application, when an anomaly occurs in the SA communication network registration process, if the cause of the second anomaly is a communication channel release (disconnection) scenario, the SA communication network registration procedure can be completed early 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 increasing the quality of service provided 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 regains the functionality to operate in the SA communication network and can return to the SA communication network to register again, and carries out steps S614 to S616. For a 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 as the first round of the registration procedure, and steps S614 to S616 can be considered as 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 length of the penalty interval in the second round of the registration procedure is increased to reduce the time affected by the registration anomaly. For details, see the description of step S616. If the cause of 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 a registration request to the SA communication network for 12 hours, and initiates transmission of the registration request to the LTE communication network. The duration of the penalty interval increases from 12 minutes to 12 hours.

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

According to the technical solution proposed in this third embodiment, in this application, the registration procedure in the SA communication network can be completed early if the reason for the first failure in the registration process is the release (disconnection) of the communication channel with the network, so that there is no need to continue accumulating the number of registration attempts (corresponding to the cumulative number of failures). In addition, in the SA network, communications set progressively larger penalty intervals, with the duration of the penalty interval in the first round being set to 12 minutes. In the second round and each subsequent round, the penalty interval is 12 hours. Compared to the 12 minute ban after five unsuccessful registration attempts used in the prior art, the penalty interval here is extended 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 during registration in the 5G SA communication network, thereby reducing the time affected by the registration anomaly and improving the provision of services to the user.

It should be noted that although the present application currently only lists 13 anomaly causes and three options are given, it can be understood that the registration anomaly cause is a variable input parameter of the proposed technical solution, and that other causes can also be entered using logic for implementing the technical solution of this application. Therefore, the current list of causes of anomalies may continue to expand. In addition to this, the option configuration parameters can be flexibly modified and tailored 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 registration procedure in the SA communication network 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 SA network communication may be terminated earlier if an anomaly occurs. The specific selection of the maximum number of registration attempts for various anomaly causes may be tailored to different possible implementations. This is not limited in this application. Secondly, according to the technical solution of the present application, the duration of the penalty interval can be specialized, and a policy of progressively increasing the duration of the penalty interval can be constructed. For example, the length 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 different possible ways to design a policy to progressively increase the length of the penalty interval. This is not limited in this application. 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 different possible ways to select the timer length appropriate for the specific cause of the anomaly. This is not limited in this application.

It should also be noted that in embodiments of this 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 than)" can be replaced by "greater than" and "less than" can be replaced by "less than or equal to (not more than)".

Each embodiment described herein may represent an independent technical solution, or these embodiments may be combined in accordance with its internal logic, and all of these technical solutions will fall within the scope of the present 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 may be used in the 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 may be used in the terminal device. It can be understood that the methods and operations implemented by the backbone 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 the backbone device.

Variants of the method proposed by this application are discussed above, and then variants of the equipment proposed by this application will be described. It should be understood that the description of the hardware options corresponds to the description of the method options. Therefore, for content that will not be described in detail, reference may be made to the above method variations. For the sake of brevity, this will not be repeated here.

The technical solutions proposed by embodiments of the present application are described above primarily from the point of view of interaction between devices. It can be understood that in order to perform the above functions, each device, such as a transmitting device or a receiving device, contains corresponding hardware circuits and structures and/or software modules for performing various functions. One skilled in the art will know that, in combination with the modules and steps of the example algorithms described in the embodiments of the present invention, the present application may be implemented in hardware or 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 specific application and design constraints of the technical solutions. Various techniques may be used by those skilled in the art to implement the described functionality in any given application, but such implementation should not be considered beyond the scope of this application.

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

In fig. 12 is a simplified block diagram of an apparatus 700 for processing registration anomalies in a communications network in accordance with 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 method embodiments. The apparatus 700 includes a transceiver module 710 and a processor module 720. The transceiver module 710 is configured to perform operations related to transmitting and receiving signals on the terminal device side in the above method embodiments. The transceiver module 710 may also be referred to as a communication interface or communication module. The processing unit 720 is configured to perform data processing and data processing-related operations on the terminal device side in the above method embodiments.

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

The processor module 720 is configured to, if the Mth registration attempt fails, obtain information about the reason for the Mth registration failure and the cumulative number of M failures; and if the reason information of the Mth registration failure corresponds to the first specified reason information, and the cumulative number of failures M is not less than the first specified number of failures corresponding to the first specified reason information, execute the first processing policy corresponding to the first specified reason information, where this first processing policy comprises stopping the initiation of a registration request into a 5G SA communication network and initiating a registration request into 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 a first (in other words, initial) registration request to the 5G SA communications network. If M is greater than 1 and less than 5, before the transceiver module 710 initiates the Mth 5G SA registration request, the equipment 700 will fail to register with the 5G SA communication network M-1 times sequentially. For example, if M is 2, the equipment 700 initiates a second registration request to the 5G SA communication network after the first attempt to register 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 has failed 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 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 SA communication network and can at this time initiate a registration request to the LTE communication network. Therefore, when using the registration anomaly processing equipment proposed in this application, the mobile phone can, if an anomaly occurs during 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 during which the service for the user is affected and increasing 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 M-th registration request to the 5G SA communication network, the equipment 700 will fail to register to the 5G SA network M-1 times sequentially.

In some embodiments, the apparatus 700 may further include a counter module. This counter module is configured to add one each time the equipment 700 fails in an attempt to register with the 5G SA communication network, and accumulates a cumulative number of failures M 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 a communication channel after establishment, registration failure due to for lack of response from the 5G SA communication network or registration failure due to refusal to register 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 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 of the Mth registration failure matches the first specified cause information and the cumulative number of failures M is less than the first specified number of failures.

In some embodiments, the processor module 720 is further configured to, if the equipment 700 fails when attempting to register with a 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 of M+1 failures; and if the reason information of the (M+1)th registration failure corresponds to the second specified reason information, and the cumulative number of M+1 failures is not less than the second specified number of failures corresponding to the second specified reason information, execute the first processing policy corresponding to the second given information about the reasons.

In some embodiments, the processor module 720 is specifically configured to prohibit initiation of a 5G SA communications network registration request 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 communication network after the expiration of the first predetermined penalty time interval.

In some embodiments, the transceiver module 710 is particularly configured to receive command information transmitted by a 5G SA communications network or a second communications network and initiate a registration request to the 5G SA communications 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 communications network registration request during a second predetermined penalty time interval if the transceiver module 710 fails to register with the 5G SA communications network consecutively M times, and the reason information is the M th Registration failure corresponds to the first specified cause information. The second predetermined penalty time interval may be greater than the first predetermined penalty time interval.

In some embodiments, hardware 700 may further include a storage module. This memory module is configured to previously store at least one match, where the plurality of at least one match comprises a first match and a second match, such that the first match is a match of a first predetermined cause information, a first predetermined number of failures, and a first processing policy. , and the second match is a 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 a first predetermined number of failures corresponding to the first predetermined cause information according to the first match if the cause information of the M-th registration failure matches the first predetermined cause information.

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

According to the characteristics of the registration anomaly processing apparatus proposed in the exemplary embodiment of the present application, if an anomaly occurs during registration in a communication network, the terminal device can obtain information about the reason for registration failure and the cumulative number of failures, in order to determine whether the condition for early termination is satisfied. registration procedures. If this condition is satisfied, the registration procedure is completed early, so that there is no need 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 anomalous registration can be completed earlier (earlier than the protocol) and, if an anomaly occurs when registering in a communication network, it is possible to register in another communication network 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 poor signal conditions during the registration process in the communication network, and improve the quality of service provision to the user.

The apparatus 700 of the embodiments of the present application may comply with the methods contemplated by the embodiments of the present application, and the above and other operations and/or functions of the modules of the apparatus 700 are intended to implement the corresponding method procedures. For the sake of brevity, the details will not be described here again.

In fig. 13 shows a simplified block diagram of communication equipment 900 according to one embodiment of the present application. This communications equipment 900 includes: a processor 910, a storage device 920, a communications interface 930, and a bus 940.

In one possible embodiment, the processor 910 in the hardware 900 shown in FIG. 13 may correspond to a processor module 720 in the hardware 700 shown in FIG. 12. Communication interface 930 in the 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 unit within processor 910, or may be an external storage unit independent of processor 910, or may further be a component comprising a storage unit within processor 910 and an external storage unit not 910 processor dependent.

Optionally, hardware 900 may further include a bus 940. Memory 920 and communications interface 930 may be coupled to processor 910 via 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, data bus, control bus, or other similar bus. For ease of description, FIG. 13 shows only one line, which does not mean that there is only one tire or only one type of tire.

It should be understood that in embodiments of the present application, processor 910 may include a 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. The general purpose processor may be a microprocessor, or the processor may be any conventional processor or other similar device. Alternatively, processor 910 employs one or more integrated circuits to execute appropriate programs to implement the technical solutions provided by embodiments of the present application.

Memory 920 may include read-only memory (ROM) and random access memory (RAM) and provide commands and data to processor 910. A portion of processor 910 may optionally contain a non-volatile random access memory device. For example, processor 910 may further include device type information.

When the hardware 900 is operating, the processor 910 executes computer-executable instructions from the storage device 920 to carry out the steps of the above methods using the 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 the above and other operations and/or functions of the modules in the apparatus 700 are accordingly directed to implementing the corresponding procedures of the methods of the present application. For the sake of brevity, the details will not be described here again.

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

As an option, in some embodiments, the subject embodiments of this application further provide a computer program product. This computer program product contains program code, such that when a computer executes this 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 contain 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 procedure. The application layer may contain an application such as a browser, address book, word processor software, or instant messaging software.

The variants of this application do not specifically limit in any way the specific structure of the execution object that implements the methods proposed by the variants of this application, as long as the program in which the code of the methods implemented by the variants of this application is written can be executed to carry out communication according to the variants of this application. For example, an execution entity for performing the methods of embodiments of the present application may be a terminal device or a network device, or a function module in a terminal device or network device that can invoke a program and execute the 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 herein can 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, floppy disk, or magnetic tape), an optical disk (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 information storage media described herein may indicate one or more devices and/or other computer readable media used for storing information. The term "machine-readable media" may include, but is not limited to, radio and various other media that may store, contain and/or carry commands and/or data.

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

It can further be understood that the memory device described in the embodiments of the present application may be a volatile memory device or a non-volatile memory device, or may comprise both a volatile memory device and a non-volatile memory device. The non-volatile storage device may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM) , electrically erasable EPROM (EEPROM) or flash memory device. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. For example, without limitation, RAM may take various forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM , SDRAM), double data rate SDRAM (DDR SDRAM), 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 processor, an ASIC, an FPGA or other programmable logic device, or a discrete hardware component, a memory device may be integrated into the processor.

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

Even one of ordinary skill in the art may be aware that the modules and steps in the examples described with reference to the embodiments contemplated herein 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 application and design constraints imposed on the technical solutions. Various techniques may be used by those skilled in the art to implement the described functionality for each particular application, but such implementations should not be considered beyond the scope of this application.

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

In the embodiments 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 version of the equipment is just an example. For example, modularization is simply a partitioning of logical functions, so in real-life cases a different partitioning may be used. For example, several modules or components may be combined or integrated into another system, or some features may be ignored or not implemented. In addition, the relationships presented or discussed herein, or direct connections or connections for communication, may be implemented using certain interfaces. Indirect connections 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 one location, or may be distributed across multiple network modules. Some or all of the modules may be selected according to actual need to achieve the objectives of the technical solutions of the embodiments of this application.

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

If any functions are implemented in the form of software function modules sold or used as independent products, these functions may also be stored on a computer-readable storage medium. Based on such understanding, technical solutions of the present application that are essentially or partially known in similar art, or some such technical solutions, can be implemented in the form of a computer program product. The computer program product is stored on a storage medium and contains a number 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 this application. The above information storage medium may be, without limitation: any medium capable of storing program code, such as a USB flash drive, removable hard drive, 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 this description are the same as those commonly understood by those skilled in the art to which this application pertains. In this application, the terms used herein are intended merely to describe the purposes of particular embodiments and not to limit the present application.

The foregoing descriptions are merely about specific embodiments of the present application and are not intended to limit the scope of the present application. Any variations or substitutions readily identifiable by one skilled in the art within the technical scope of this application shall fall within the scope of protection of this application. Therefore, the scope of protection of the present application must correspond to the scope of protection of the Claims.

Claims (41)

1. A method for processing anomalies during registration in a communication network, containing: initiation, by the terminal device, of the Mth registration request into the fifth generation autonomous communication network (5G SA), where M is a positive integer less than 5; if the Mth registration is unsuccessful and the cumulative number of M failures is not less than the first predetermined number of failures, the terminal device executes a first processing policy, where the first processing policy comprises: stopping initiation of a registration request to a 5G SA communication network and initiating a registration request to a second network communications other than the 5G SA communications network. 2. The method according to claim 1, in which the first predetermined failure number corresponds to the first predetermined cause information, and the first processing policy corresponds to the first predetermined cause information; if the M-th registration failure cause information corresponds to the first specified cause information and the cumulative number of failures M is not less than the first specified number of failures corresponding to the first specified cause information, executing, by the terminal device, a first processing policy corresponding to the first specified reason information. 3. The method according to claim 1 or 2, in which The first specified cause information is used to indicate any one of the following reasons: registration failure due to link establishment failure, registration failure due to link release after establishment, registration failure due to no response from the 5G SA communications network, or registration failure due to registration refusal received from the 5G SA communication network. 4. Method according to any one of paragraphs. 1-3, wherein after the terminal device receives information about the cause of the Mth registration failure and the cumulative number M of failures, the method further comprises: initiation, by the terminal device, of the (M+1)th registration request to the 5G SA communication network after the expiration of the first timeout interval, if the reason information for the Mth registration failure does not correspond to the first specified reason information or if the reason information for the Mth 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. 5. The method according to claim 4, in which 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, the terminal device obtains information about the reason for the (M+1)th registration failure and the cumulative number of M+1 failures; And if the reason information of the (M+1)th registration failure corresponds to the second specified reason information and the cumulative number of M+1 failures is not less than the second specified number of failures corresponding to the second specified reason information, the terminal device executes the first processing policy corresponding to the second specified information about the reasons. 6. The method according to claim 4 or 5, in which the method additionally contains: starts, by the terminal device, timer T3511 if the M-th registration failure cause information does not match the first specified cause information or if the M-th registration failure cause information matches the first specified cause information and the cumulative number of M failures is less than the first specified number of failures , in which the specified time duration of timer T3511 is equal to the first timeout interval. 7. Method according to any one of paragraphs. 4–6, in which the first timeout interval is 10 seconds. 8. Method according to any one of paragraphs. 3–7, in which the procedure for stopping the terminal device from initiating a registration request to the 5G SA communication network contains: prohibition, by the terminal device, from initiating a registration request to the 5G SA communication network during the first specified penalty time interval corresponding to the first specified reason information. 9. The method of claim 8, wherein the first predetermined penalty time interval is greater than the first waiting time interval. 10. The method according to claim 8 or 9, in which after the terminal device prohibits the initiation of a registration request to the 5G SA communication network during the first specified penalty time interval, the method further comprises: initiation, by the terminal device, of a registration request into the 5G SA communication network after the expiration of the first specified penalty time interval. 11. The method according to claim 10, 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 a 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 a terminal device, a registration request for a 5G SA communication network contains: initiation, by the terminal device, of a registration request into the 5G SA communication network in accordance with the command information. 12. The method according to claim 10 or 11, in which after the terminal device initiates a registration request for the 5G SA communication network, the method further comprises: prohibits the terminal device from initiating a registration request to the 5G SA communication network during the second specified penalty time interval if the terminal device fails in attempts to register to the 5G SA communication network consecutively M times, and information about the reason for the Mth registration failure corresponds to the first specified information about the reasons wherein the second predetermined penalty time interval is greater than the first predetermined penalty time interval. 13. Method according to any one of paragraphs. 3–12, in which the method additionally contains: pre-storing by the terminal device of at least one match, where the plurality of at least one match comprises a first match and a second match, the first match represents a match between a first predetermined cause information, a first predetermined number of failures, and a first processing policy, and the second match represents is a correspondence between the second predetermined cause information, the second predetermined number of failures, and the first processing policy; And if the M-th registration failure cause information corresponds to the first predetermined cause 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 correspondence. 14. Method according to any one of paragraphs. 3–13, in which the procedure for a terminal device to initiate a registration request into a second communication network other than a 5G SA communication network comprises: a search by the terminal device for at least one available communication network other than a 5G SA communication network, wherein the plurality of at least one available communication network comprises said second communication network, and the quality of a received reference signal from the second communication network from the plurality of at least one of one available communication network is optimal; And initiating, by the terminal device, a registration request into this second communication network. 15. Method according to any one of paragraphs. 3-14, wherein 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, the terminal device has already failed to register to the 5G SA communication network M-1 times sequentially. 16. Method according to any one of paragraphs. 3–15, additionally containing: counting by the terminal device one each time the terminal device fails in an attempt to register with the 5G SA communication network, and accumulating a cumulative number of failures M if the Mth registration attempt fails. 17. Equipment for processing anomalies when registering a terminal in a communication network, containing: a storage device, a processor and a program stored in the storage device and executed by the processor, where when executing this program, the processor implements the method according to any one of paragraphs. 1–16. 18. An integrated circuit for processing anomalies when registering a terminal in a communication network, comprising a processor, wherein the processor is coupled to a memory device, the memory device is configured to store a computer program, and the processor is configured to execute a computer program stored in the memory device so that the integrated circuit the circuit implemented the method according to any one of paragraphs. 1–16.