CN117956569A - Network registration processing method and related device - Google Patents

Abstract

The present application provides a method and a related device for processing network registration, which can stop converting the received first rejection information into the second rejection information when detecting that the number of consecutive abnormal network registrations of the terminal device reaches a first preset number of times, wherein the first rejection information is rejection information prohibiting the network registration, and the second rejection information is rejection information allowing the network registration to be retried. The terminal device can be automatically controlled to not retry the network registration as much as possible when the network environment is stable and the registration cannot be successful, which greatly saves the power consumption of the device.

Description

Network registration processing method and related device

Technical Field

The present application relates to the field of communication technology, and in particular to a method for processing network registration and related devices.

Background technique

In a mobile communication system, the device side needs to register with the network before using the network. The network side will determine whether the device side is allowed to register or not. If registration is not allowed, the network side will feedback corresponding rejection information. Currently, when a network registration fails, the device side will generally optimize and try to register repeatedly. However, there are some scenarios where registration is impossible. Repeated attempts at this time will cause the device to generate unnecessary power consumption.

Summary of the invention

In view of this, the present application provides a network registration processing method and related apparatus, which can automatically identify scenarios where registration cannot be successful and control itself not to perform network registration too many times in scenarios where registration cannot be successful, thereby greatly saving device power consumption.

In a first aspect, an embodiment of the present application provides a method for processing network registration, which is applied to a terminal device, and the method includes:

If the number of consecutive abnormalities in the network registration of the terminal device reaches a first preset number, the conversion of the received first rejection information into the second rejection information is stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried.

In a second aspect, an embodiment of the present application provides a network registration processing device, which is applied to a terminal device, and the device includes:

A processing unit is used to stop converting a received first rejection message into a second rejection message if the number of consecutive abnormalities in the network registration of the terminal device reaches a first preset number, wherein the first rejection message is a rejection message prohibiting the network registration, and the second rejection message is a rejection message allowing the network registration to be retried.

In a third aspect, an embodiment of the present application provides a terminal device, comprising a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for executing the steps of any method in the first aspect of the embodiment of the present application.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps described in any method of the first aspect of the embodiment of the present application.

In a fifth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute some or all of the steps described in any method of the first aspect of the embodiment of the present application. The computer program product may be a software installation package.

It can be seen that through the above-mentioned network registration processing method and related devices, when the number of consecutive abnormal network registrations of the terminal device reaches the first preset number, the conversion of the received first rejection information into the second rejection information can be stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried. When the network environment is stable and the registration cannot be successful, the terminal device can be automatically controlled to not retry the network registration as much as possible, which greatly saves the power consumption of the device.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

FIG2 is a flow chart of a method for processing network registration provided in an embodiment of the present application;

FIG3 is a flow chart of another method for processing network registration provided in an embodiment of the present application;

FIG4 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

FIG5 is a block diagram of functional units of a network registration processing device provided in an embodiment of the present application;

FIG6 is a block diagram of the functional units of another network registration processing device provided in an embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

It should be understood that the term "and/or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article indicates that the associated objects before and after are in an "or" relationship. The "plurality" appearing in the embodiments of the present application refers to two or more.

In the embodiments of the present application, "at least one item" or similar expressions refer to any combination of these items, including any combination of single items or plural items, and refer to one or more, and multiple refers to two or more. For example, at least one item of a, b, or c can represent the following seven situations: a, b, c, a and b, a and c, b and c, a, b, and c. Among them, each of a, b, and c can be an element or a set containing one or more elements.

The "connection" that appears in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and the embodiments of the present application do not impose any limitations on this.

Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

The following is an explanation of the relevant contents, concepts, meanings, technical issues, technical solutions, beneficial effects, etc. involved in the embodiments of the present application.

1. Communication systems, terminal equipment and network equipment

1. Communication system

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based Access to Unlicensed Spectrum, LTE-U) system, NR on unlicensed spectrum (NR-based Access to Unlicensed Spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wi-Fi), 6th Generation (6G) communication system or other communication systems.

It should be noted that the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, communication systems can not only support traditional communication systems, but also support device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine type communication (MTC), vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, narrowband Internet of things (NB-IoT) communication, etc. Therefore, the technical solutions of the embodiments of the present application can also be applied to the above communication systems.

Since the embodiments of the present application describe various embodiments in conjunction with terminal devices and network devices, the terminal devices and network devices involved will be described in detail below.

2. Terminal equipment

Terminal equipment can be a device with transceiver functions, and can also be called terminal, user equipment (UE), remote terminal equipment (remote UE), relay equipment (relay UE), access terminal equipment, user unit, user station, mobile station, mobile station, remote station, mobile device, user terminal equipment, intelligent terminal equipment, wireless communication equipment, user agent or user device. It should be noted that relay equipment is a terminal equipment that can provide relay forwarding services for other terminal equipment (including remote terminal equipment).

For example, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned autonomous driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

For another example, the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system (such as an NR communication system, a 6G communication system), or a terminal device in a future evolved public land mobile communication network (PLMN), etc., without specific limitation.

In some possible implementations, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; can be deployed on the water surface (such as ships, etc.); can be deployed in the air (such as airplanes, balloons and satellites, etc.).

In some possible implementations, the terminal device may include a device with wireless communication functions, such as a chip system, a chip, or a chip module. For example, the chip system may include a chip and may also include other discrete devices.

3. Network equipment

A network device may be a device with transceiver functions, used for communicating with terminal devices.

In some possible implementations, the network device may be a base station (BS) in a communication system or a device deployed in a radio access network (RAN) for providing wireless communication functions.

For example, the network device can be an evolved node B (eNB or eNodeB) in an LTE communication system, a next generation evolved node B (ng-eNB) in an NR communication system, a next generation node B (gNB) in an NR communication system, a master node (MN) in a dual-connection architecture, a second node or secondary node (SN) in a dual-connection architecture, etc., without specific limitation.

In some possible implementations, the network device may also be a device in the core network (CN), such as an access and mobility management function (AMF), a user plane function (UPF), etc.; it may also be an access point (AP) in a WLAN, a relay station, a communication device in a future evolved PLMN network, a communication device in an NTN network, etc.

In some possible implementations, the network device may include a device that provides wireless communication functions for the terminal device, such as a chip system, a chip, or a chip module. For example, the chip system may include a chip, or may include other discrete devices.

In some possible implementations, the network device may be an independent node to implement the functions of the above-mentioned base station, or the network device may include two or more independent nodes to implement the functions of the above-mentioned base station. For example, the network device includes a centralized unit (CU) and a distributed unit (DU), such as gNB-CU and gNB-DU. Further, in some other embodiments of the present application, the network device may also include an active antenna unit (AAU). Among them, the CU implements part of the functions of the network device, and the DU implements another part of the functions of the network device. For example, the CU is responsible for processing non-real-time protocols and services, and implements the functions of the radio resource control (RRC) layer, the service data adaptation protocol (SDAP) layer, and the packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, and implements the functions of the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer. In addition, the AAU can implement some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this network deployment, high-level signaling (such as RRC signaling) can be considered to be sent by the DU, or sent by the DU and the AAU together. It can be understood that the network device may include at least one of the CU, DU, and AAU. In addition, the CU can be classified as a network device in the RAN, or the CU can be classified as a network device in the core network, without specific limitation.

In some possible implementations, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

In some possible implementations, a network device may provide services for a cell, and a terminal device in the cell may communicate with the network device through transmission resources (such as spectrum resources). The cell may be a macrocell, a small cell, a metro cell, a microcell, a pico cell, a femto cell, etc.

4. Example

The following is an exemplary description of the system architecture of network registration in an embodiment of the present application.

For example, a network architecture of a communication system in an embodiment of the present application can be referred to Figure 1. As shown in Figure 1, the communication system 10 may include a network device 110 and a terminal device 120. The terminal device 120 may communicate with the network device 110 in a wireless manner.

Among them, the terminal device 120 may include a scene recognition unit, which can determine whether the terminal device 120 is in a network stable scene through the motion state of the terminal device 120 collected by motion sensors such as an inertial measurement unit, an acceleration sensor, an angular velocity sensor, and a magnetic field sensor. The modem in the terminal device 120 can obtain the current scene information determined by the scene recognition unit, and then execute the corresponding network registration processing method.

FIG. 1 is only an example of a network architecture of a communication system, and does not limit the network architecture of the communication system of the embodiment of the present application. For example, in the embodiment of the present application, the communication system may also include a server or other devices. For another example, in the embodiment of the present application, the communication system may include multiple network devices and/or multiple terminal devices.

2. A method for processing network registration

Before using network functions, the terminal device needs to register with the network, that is, send a network registration request to the network device. If the network device determines that the terminal device meets the registration conditions, it will allow it to register, and the network registration of the terminal device will be successful. If the network device determines that the terminal device does not meet the registration conditions, it will return a rejection message to refuse registration, and the network registration of the terminal device will fail.

For example, the network registration process of LTE may include power-on residence, initialization of the subscriber identity module (Subscriber Identity Module, SIM), selection of PLMN, selection of cell, registration, connection and reconfiguration, data transmission process, measurement switching process, etc., which will not be repeated here. In the network registration process, if the registration fails, the network device will return a rejection message, which varies according to the network standard and may exist in the form of a rejection reason value (cause). For example, the 3GPP protocol specifies the code of the rejection reason value, such as #7, EPS services not allowed; #8, EPS services and non-EPS services not allowed; #14, EPS services not allowed in this PLMN; #11, PLMN not allowed; #16, MSC temporarily not reachable; #6, Illegal ME; #10, Implicitly separated. detached), and the ESM RejectCause value is #28; and #0, the rejection information fed back when the network side processes the user registration is not standardized, etc.

It should be noted that rejection information can be divided into two categories. The first category is the rejection information that directly prohibits the terminal device from registering on the network again, such as #6, etc. The second category is the rejection information that the terminal device can still try to register on the network again, such as #12, #13, etc. The specific classification is not listed here, and the specific function of the rejection information shall prevail.

Currently, when a terminal device receives a second type of rejection message, it will try to register with the network again; when a terminal device receives a first type of rejection message, it can convert the first type of rejection message received into a second type of rejection message in order to register with the network again, or it can directly soft restart (such as entering and exiting airplane mode) to register with the network again. This mechanism was originally set to prevent the terminal device from being unable to connect to the network, but in some scenarios, repeated re-registration of the network is unnecessary and increases the power consumption of the device.

For example, if the SIM card of the terminal device is an abnormal card, registration will not be successful at this time; for example, if there is a local abnormality or congestion in the network environment, resulting in failure of registration, registration will not be successful until the network environment is restored.

In the above scenario, multiple network registrations are just repeating invalid steps, causing unnecessary power consumption of the terminal device.

Based on the above problems, an embodiment of the present application provides a network registration processing method, which is applied to a terminal device and can identify whether the current network registration cannot be successfully registered. When the terminal device cannot be successfully registered, the terminal device is controlled to stop network registration as much as possible, thereby greatly saving device power consumption.

The technical solutions, beneficial effects, concepts, etc. involved in the embodiments of the present application are described in detail below.

1. Network stability scenario

It should be noted that the network stability scenario in the embodiment of the present application is a scenario in which the cell of the terminal device does not change. It can be understood that in the network stability scenario, the serving cell and the adjacent cell of the terminal device are stable, and the cell measured by the terminal device is also approximately stable. In the network stability scenario, it can be ensured that the process and specific content of each network registration are the same.

2. How to detect whether the terminal device is in a stable network scenario

It should be noted that the movement state of the terminal device can be detected to determine whether the terminal device is in a stable network scenario. If the movement state of the terminal device is static or slightly moving, it can be determined that the location of the terminal device has not changed significantly. The cell is closely related to the location, and different locations correspond to different cells. When the location of the terminal device has not changed significantly, it can be considered that the service cell and adjacent cell of the terminal device are stable, that is, the terminal device is in a stable network scenario. For ease of understanding, the following example illustrates how to detect the movement state of the terminal device.

1) Determine whether the terminal device is in a stationary state

The terminal device can detect its own acceleration and/or angular velocity and other information through the motion sensor it is equipped with, and determine its own speed in combination with the time information. When the speed is 0, it can be determined that the terminal device is in a stationary state, otherwise it is not in a stationary state. It can be understood that the speed here can be the average angular velocity and/or average speed of the terminal device, etc., and no specific limitation is made here.

2) Determine whether the terminal device is in a micro-motion state

In a possible example, the terminal device can collect information such as acceleration and/or angular velocity through the motion sensor carried by itself, and calculate its own speed in combination with time information. When the speed is greater than 0 but continuously less than a first speed threshold, it can be determined that it is in a micro-motion state, otherwise it is not in a micro-motion state. It can be understood that the first speed threshold is a lower speed. When the speed is less than the first speed threshold, the terminal device may be in a scenario where it is used by a user. In this scenario, the rotation of the terminal device and slight speed changes will not change the service cell and adjacent cell of the terminal device. It can be understood that the speed here can be the average angular velocity and/or average speed of the terminal device, etc., and no specific limitation is made here.

In a possible example, the terminal device can collect information such as acceleration and acceleration direction through the motion sensor carried by itself, and then determine the acceleration in each direction and the acceleration duration in each direction, and determine the displacement distance in each direction according to the acceleration in each direction and the acceleration duration in each direction, and the actual coordinates of the terminal device can be determined according to the displacement distance in each direction and the initial coordinates of the terminal device, and the straight-line displacement distance of the terminal device can be determined according to the initial coordinates and the actual coordinates. When the straight-line displacement distance is less than the preset displacement threshold, it can be determined that the terminal device is in a micro-motion state, otherwise it is not in a micro-motion state. It can be understood that when the straight-line displacement distance of the terminal device is less than the preset displacement threshold, it means that the position of the terminal device has not changed significantly. In the scenario where the position has not changed significantly, the service cell and the adjacent cell of the terminal device are stable.

3. Network standard

In order to determine whether the terminal device is in a scenario where network registration cannot be successful no matter what, it is necessary to first introduce the concept of network standard. The network standard in the embodiment of the present application can be divided into 2G, 3G, 4G (LTE), 5G, 6G or even higher network standards. It should be noted that the second generation mobile communication technology (second generation, 2G) can be a general term for multiple network standards. For example, the global mobile communication system (Code Division Multiple Access, CDMA) and the code division multiple access technology (Global System For Mobile Communication, GSM) are both 2G network standards. In general, the third generation mobile communication technology (third generation, 3G) can also include multiple network standards, such as TD-SCDMA network standard, WCDMA network standard, EVDO network standard, etc., which belong to 3G network standards. The fourth generation communication system (the 4th generation communication system, 4G) can also include multiple network standards, for example, TD-LTE, FDD-LTE, etc. belong to 4G network standards. The fifth generation mobile communication technology (5th Generation Mobile Communication Technology, 5G) can include network standards for non-independent networking and network standards for independent networking. It should be noted that the above English expressions are commonly used in the communications field, and the corresponding Chinese expressions will not be repeated here.

4. How to determine network registration anomalies

It should be noted that the network standards supported by the terminal devices and the frequency bands of each network standard are different, so there will be some differences in determining network registration anomalies.

In a possible embodiment, the terminal device supports 4G network standard, 3G network standard and 2G network standard. Then, when the following conditions are met, it can be determined that the network registration of the terminal device is abnormal:

The terminal device registered for the full-band network under the 4G network standard and was rejected by the network side;

The terminal device registered for the full-band network under the 3G network standard and was rejected by the network side;

The terminal device attempts to register for the full-band network under the 2G network standard and is rejected by the network side.

That is, when the terminal device still cannot register successfully after a complete search of all network standards (2G/3G/4G) and all frequency bands, it can be determined that this network registration is abnormal. It can be understood that no matter under which network standard the network registration is performed and is rejected by the network side, the terminal device will receive a rejection message returned by the network side. The type of rejection information can be the first type or the second type. At this time, the terminal device can convert the received first type of rejection information into the second type of rejection information for the next network registration. The terminal device can also perform a soft restart when receiving the first type of rejection information for the next network registration.

In a possible embodiment, the terminal device can support 5G network standard, 4G network standard, 3G network standard and 2G network standard. Then, when the following conditions are met, it can be determined that the network registration of the terminal device is abnormal:

The terminal device registered for the full-band network under the 5G network standard and was rejected by the network side;

The terminal device registered for the full-band network under the 4G network standard and was rejected by the network side;

The terminal device registered for the full-band network under the 3G network standard and was rejected by the network side;

The terminal device registered for the full-band network under the 2G network standard and was rejected by the network side;

That is, when the terminal device still cannot register successfully after a complete search of all network standards (2G/3G/4G/5G) and all frequency bands, it can be determined that the network registration is abnormal.

In a possible embodiment, the terminal device may support 5G network standard, 4G network standard, 3G network standard, or the terminal device may support 5G network standard, 4G network standard, or the terminal device may support 4G network standard, 3G network standard, or the terminal device may support 5G network standard, 3G network standard, etc. Regardless of the network standard supported by the terminal device, the final determination of whether the network registration of the terminal device is abnormal can be made by determining whether the registration is successful through a complete full-network standard and full-frequency band search. The above exemplary description does not represent a specific limitation on the present application.

In a possible embodiment, when repeated network registration is performed in a certain frequency band under a certain network standard and the number of times rejected by the network side reaches the number threshold corresponding to the frequency band, it can be determined that the current network registration is abnormal. For example, if the terminal device currently uses a 5G network standard, then when it is detected that repeated network registration is performed in the a frequency band of the 5G network standard and is rejected 4 times, it can be determined that the current network registration is abnormal. For example, if the terminal device currently uses a 4G network standard, then when it is detected that repeated network registration is performed in the x frequency band of the 4G network standard and is rejected 3 times, it can be determined that the current network registration is abnormal. No further details are given here.

In a possible embodiment, under 5G and higher network standards, the network side may return a rejection message disabling 5G and higher network standards. When the terminal device receives such a rejection message, it will automatically disable the disabled network standard during subsequent network registration, and will not perform network registration under the disabled network standard. The disabled network standard will no longer be used as a condition for determining whether the network registration of the terminal device is abnormal. For example, when network registration is performed under the 5G network standard and is rejected by the network side, the network side may return a rejection reason value #27 (N1 mode not allowed). When the terminal device receives #27, the 5G network standard will be unavailable. When the terminal device performs network registration subsequently, the terminal device will determine whether the network registration of the terminal device is abnormal based on the conditions corresponding to supporting 4G network standards, 3G network standards, and 2G network standards.

5. Processing of network registration

1) First instruction

In order to save device power consumption, an embodiment of the present application introduces a first instruction, which is used to turn off the function of converting the received first-type rejection information into the second-type rejection information. Since this function is turned on in the default network registration process to prevent further attempts after a registration failure, turning off this function through the first instruction here can make the terminal device directly stop registering with the network in response to the first-type rejection information when it receives the first-type rejection information again, thereby greatly saving device power consumption.

It should be noted that the terminal device will count the number of network registration anomalies. If the counted number of consecutive network registration anomalies of the terminal device reaches a first preset number, a first instruction will be generated. The first preset number can be set freely and is not specifically limited here.

2) Second instruction

In a possible embodiment, after the first instruction is generated, when the terminal device re-registers with the network, it receives the second type of rejection information, or when the terminal device re-registers with the network, it receives the first type of rejection information and performs a soft restart, and it can still continue to register with the network. It can be understood that the soft restart is a self-recovery mechanism, and generally there is an upper limit to recovery. In this case, the terminal device will still repeatedly register with the network, causing unnecessary power consumption. In order to solve the above problem, the embodiment of the present application introduces a second instruction, which is used to convert the received second type of rejection information into the first type of rejection information and prohibit soft restart when the first type of rejection information is received.

Specifically, after the first instruction is generated, if the number of consecutive network registration exceptions of the terminal device reaches a second preset number, the second instruction is generated, and the second preset number is greater than the first preset number. For example, the first preset number can be 2 and the second preset number can be 5.

For example, when the terminal device receives the second type of rejection information #12, it can convert #12 into the first type of rejection information #8. #8 can make the terminal device unusable in both the circuit switching domain and the packet switching domain. Since soft restart is prohibited at this time, the terminal device no longer has the ability to register with the network. The terminal device will be in a state where it cannot register with the network, further saving device power consumption.

6. Foolproofing mechanism

After the second instruction is generated, the terminal device cannot be used in both the circuit switching domain and the packet switching domain. If the reason why the terminal device cannot register successfully is due to network congestion and other reasons rather than the SIM card itself being an abnormal card, then when the network is restored, if the terminal device is still in a stable network scenario, then even if the network is restored, the terminal device will not be able to perceive it. In order to solve this problem, the embodiment of the present application introduces an anti-fool mechanism.

In a possible embodiment, after the second instruction is generated, if it is detected that the terminal device is still in the above-mentioned network stability scenario but exceeds the preset time, initialization processing is performed and network registration is allowed. The initialization processing can be to clear the historical record information of network registration, restore the default settings, etc., such as setting the number of consecutive abnormal network registrations of the terminal device to zero, allowing the first rejection information received to be converted to the second rejection information, and allowing a soft restart when the first rejection information is received, etc., which will not be described in detail here. It can be understood that after allowing network registration, the network registration processing method described in the embodiment of the present application is still used.

In a possible embodiment, after the second instruction is generated, if it is detected that the terminal device is still in the above-mentioned network stable scenario but receives a user feedback instruction, initialization processing is performed and network registration is allowed. The user feedback instruction can be a user manually entering or exiting the flight mode, or other instructions for allowing network registration again, which are not specifically limited here.

It can be understood that in any of the above steps 1-5, if it is detected that the terminal device is not in the above-mentioned network stability scenario, the default processing method will be restored to perform network registration. The default processing method includes allowing the received first type of rejection information to be converted into the second type of rejection information and allowing a soft restart when the first type of rejection information is received.

7. An example of a method for processing network registration

In combination with the above content, an example of a network registration processing method in an embodiment of the present application is described below.

As shown in FIG. 2 , it is a flowchart of a method for processing network registration according to an embodiment of the present application, which is applied to a terminal device and specifically includes the following steps:

Step 201: If the number of consecutive network registration anomalies of the terminal device reaches a first preset number, stop converting the received first rejection information into the second rejection information.

Among them, the terminal device is in a network stable scenario, and the above-mentioned network stable scenario is a scenario in which the cell of the above-mentioned terminal device has not changed. The first instruction can be used to instruct to stop converting the received first rejection information into the second rejection information. The above-mentioned first rejection information (the first type of rejection information) is rejection information prohibiting the network registration, and the above-mentioned second rejection information (the second type of rejection information) is rejection information allowing retry of the network registration.

It can be seen that through the above-mentioned network registration processing method and related devices, when it is detected that the number of consecutive abnormal network registrations of the terminal device reaches the first preset number, the conversion of the received first rejection information into the second rejection information can be stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried. When the network environment is stable and the registration cannot be successful, the terminal device can be automatically controlled to not retry the network registration as much as possible, which greatly saves the power consumption of the device.

For the contents not described in detail above, please refer to the description of 1-6 above, which will not be repeated here.

8. Another example of a method for processing network registration

In combination with the above content, another method for processing network registration in an embodiment of the present application is described below by way of example.

As shown in FIG3 , it is a flowchart of another method for processing network registration according to an embodiment of the present application, which is applied to a terminal device and specifically includes the following steps:

Step 301, detecting the motion state of the terminal device.

In a possible embodiment, the speed of the terminal device can be detected. When the speed is 0, it is determined that the motion state belongs to the static state; when the speed is greater than 0 but continuously less than a first speed threshold, or, when the speed is continuously greater than or equal to the first speed threshold but the duration is less than a duration threshold, or, when the cumulative duration that the speed is greater than or equal to the first speed threshold is less than the cumulative duration threshold, it is determined that the motion state belongs to the micro-motion state.

Step 302: If the motion state is a stationary state or a slight motion state, it is determined that the terminal device is in a stable network scenario.

It can be seen that this can ensure that the terminal device can still determine whether its service cell and adjacent cell have changed through the motion sensor when there is no network service in the future.

Step 303: Count the number of times the terminal device performs network registration continuously abnormally.

The following steps may be repeatedly performed until the counted number of consecutive abnormalities in network registration of the terminal device reaches the first preset number:

S1, determining the network standard information supported by the terminal device and the frequency band information of each supported network standard;

S2, performing the network registration in each of the network standards, and searching in each frequency band of each of the network standards to perform the network registration;

S3, if the rejection information corresponding to each of the above network standards is received and registration is still not possible after searching in each frequency band of each of the above network standards, it is determined that the above network registration is abnormal, and the number of consecutive network registration abnormalities of the above terminal device is increased by one.

It can be seen that this can ensure that the terminal device is in a scenario where network registration cannot be successful no matter what.

Step 304: If the number of consecutive network registration anomalies of the terminal device reaches a first preset number, stop converting the received first rejection information into the second rejection information.

Step 305: If the number of consecutive network registration exceptions of the terminal device reaches a second preset number, the received second rejection information is converted into the first rejection information and a soft restart is prohibited when the first rejection information is received.

Among them, the second preset number of times is greater than the first preset number of times, and a second instruction can be used to instruct to convert the received second rejection information into the first rejection information and prohibit soft restart when the first rejection information is received.

It can be seen that this can further save the power consumption of the terminal device.

Step 306: If it is detected that the terminal device is still in the network stable scenario but exceeds the preset time, or if it is detected that the terminal device is still in the network stable scenario but receives a user feedback instruction, initialization processing is performed and the network registration is allowed.

Among them, the above-mentioned initialization processing includes setting the counted number of consecutive abnormalities in the network registration of the above-mentioned terminal device to zero, allowing the received first rejection information to be converted into the above-mentioned second rejection information, and allowing at least one of soft restart when the above-mentioned first rejection information is received.

This can prevent the terminal device from being unable to register with the network even when the network is restored, thereby improving the user experience.

In a possible embodiment, at any stage of steps 301-306, if it is detected that the above-mentioned terminal device is not in the above-mentioned network stable scenario, the above-mentioned network registration is performed in a default processing manner, and the above-mentioned default processing manner includes allowing the above-mentioned first rejection information received to be converted into the above-mentioned second rejection information and allowing a soft restart when the above-mentioned first rejection information is received.

For the contents not described in detail above, please refer to the description of 1-7 above, which will not be repeated here.

3. Exemplary description of a terminal device

A terminal device in an embodiment of the present application is described below in conjunction with FIG4 , which is a schematic diagram of the structure of a terminal device in an embodiment of the present application. The terminal device 400 includes a processor 401 , a memory 402 , and a communication bus 403 for connecting the processor 401 and the memory 402 .

In some possible implementations, the memory 402 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or portable read-only memory (CD-ROM), and the memory 402 is used to store the program code executed by the terminal device 400 and the transmitted data.

In some possible implementations, the terminal device 400 further includes a communication interface, which is used to receive and send data.

In some possible implementations, the processor 401 may be one or more central processing units (CPUs). When the processor 401 is a central processing unit (CPU), the central processing unit (CPU) may be a single-core central processing unit (CPU) or a multi-core central processing unit (CPU).

In some possible implementations, the processor 401 may be a baseband chip, a chip, a central processing unit (CPU), a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.

In a specific implementation, the processor 401 in the terminal device 400 is used to execute the program instructions 421 stored in the memory 402 to perform the following operations:

If the number of consecutive abnormalities in the network registration of the terminal device reaches a first preset number, the conversion of the received first rejection information into the second rejection information is stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried.

It can be seen that through the above-mentioned network registration processing method and related devices, when it is detected that the number of consecutive abnormal network registrations of the terminal device reaches the first preset number, the conversion of the received first rejection information into the second rejection information can be stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried. When the network environment is stable and the registration cannot be successful, the terminal device can be automatically controlled to not retry the network registration as much as possible, which greatly saves the power consumption of the device.

It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and the terminal device 400 can be used to execute the above method embodiment of the present application, which will not be repeated here.

4. Exemplary description of a network registration processing device

The above mainly introduces the scheme of the embodiment of the present application from the perspective of the execution process on the method side. It is understandable that, in order to realize the above functions, the electronic device includes a hardware structure and/or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment provided herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application can divide the terminal device into functional units according to the above method example. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

In the case of dividing each functional module according to each function, FIG5 is a block diagram of functional units of a network registration processing device provided in an embodiment of the present application, and the network registration processing device 500 includes:

Processing unit 510 is used to stop converting the received first rejection information into the second rejection information if the number of consecutive abnormalities in the network registration of the terminal device reaches a first preset number, wherein the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried.

It can be seen that through the above-mentioned network registration processing method and related devices, when it is detected that the number of consecutive abnormal network registrations of the terminal device reaches the first preset number, the conversion of the received first rejection information into the second rejection information can be stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried. When the network environment is stable and the registration cannot be successful, the terminal device can be automatically controlled to not retry the network registration as much as possible, which greatly saves the power consumption of the device.

It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and the network registration processing device 500 can be used to execute the above method embodiment of the present application, which will not be repeated here.

V. Exemplary Description of Another Network Registration Processing Device

In the case of adopting an integrated unit, another network registration processing device 600 in an embodiment of the present application is described in detail below in conjunction with Figure 6, and the network registration processing device 600 includes a processing unit 601 and a communication unit 602, wherein the processing unit 601 is used to execute any step in the above method embodiment, and when performing data transmission such as sending, the communication unit 602 can be selectively called to complete the corresponding operation.

The network registration processing device 600 may further include a storage unit 603 for storing program codes and data. The processing unit 601 may be a processor, the communication unit 602 may be a wireless communication module, and the storage unit 603 may be a memory.

The processing unit 601 is specifically used for:

If the number of consecutive abnormalities in the network registration of the terminal device reaches a first preset number, the conversion of the received first rejection information into the second rejection information is stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried.

It can be seen that through the above-mentioned network registration processing method and related devices, when it is detected that the number of consecutive abnormal network registrations of the terminal device reaches the first preset number, the conversion of the received first rejection information into the second rejection information can be stopped, the first rejection information is the rejection information prohibiting the network registration, and the second rejection information is the rejection information allowing the network registration to be retried. When the network environment is stable and the registration cannot be successful, the terminal device can be automatically controlled to not retry the network registration as much as possible, which greatly saves the power consumption of the device.

It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and the network registration processing device 600 can be used to execute the above method embodiment of the present application, which will not be described in detail.

6. Other examples

An embodiment of the present application also provides a chip, including a processor, a memory, and a computer program or instructions stored in the memory, wherein the processor executes the computer program or instructions to implement the steps described in the above method embodiment.

An embodiment of the present application also provides a chip module, including a transceiver component and a chip, the chip including a processor, a memory and a computer program or instructions stored in the memory, wherein the processor executes the computer program or instructions to implement the steps described in the above method embodiment.

An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps of any method recorded in the above method embodiments, and the above computer includes an electronic device.

The present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute some or all of the steps of any method described in the method embodiment. The computer program product may be a software installation package, and the computer includes an electronic device.

It should be noted that, for the above-mentioned various embodiments, for the sake of simple description, they are all expressed as a series of action combinations. Those skilled in the art should be aware that the present application is not limited by the described order of actions, because some steps in the embodiments of the present application can be performed in other orders or simultaneously. In addition, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions, steps, modules or units involved are not necessarily required by the embodiments of the present application.

In the above embodiments, the embodiments of the present application have different focuses on the description of each embodiment. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

The steps of the method or algorithm described in the embodiments of the present application can be implemented in hardware or by executing software instructions by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (electrically EPROM, EEPROM), registers, hard disks, mobile hard disks, read-only compact disks (CD-ROMs) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a terminal device or a management device. Of course, the processor and the storage medium can also be present in a terminal device or a management device as discrete components.

Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiments of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server, or data center to another website site, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

The modules/units included in the devices and products described in the above embodiments may be software modules/units or hardware modules/units, or may be partially software modules/units and partially hardware modules/units. For example, for the devices and products applied to or integrated in the chip, the modules/units included therein may all be implemented in the form of hardware such as circuits, or at least some of the modules/units may be implemented in the form of software programs, which run on the processor integrated inside the chip, and the remaining (if any) modules/units may be implemented in the form of hardware such as circuits; for the devices and products applied to or integrated in the chip module, the modules/units included therein may all be implemented in the form of hardware such as circuits, and different modules/units may be located in the same component (such as a chip, circuit module, etc.) or different components of the chip module, or at least some of the modules/units may be It is implemented in the form of a software program, which runs on a processor integrated inside the chip module, and the remaining (if any) modules/units can be implemented in hardware such as circuits; for various devices and products applied to or integrated in the terminal equipment, the various modules/units contained therein can be implemented in hardware such as circuits, and different modules/units can be located in the same component (for example, chip, circuit module, etc.) or in different components in the terminal equipment, or, at least some modules/units can be implemented in the form of a software program, which runs on a processor integrated inside the terminal equipment, and the remaining (if any) modules/units can be implemented in hardware such as circuits.

The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the embodiments of the present application. It should be understood that the above description is only the specific implementation method of the embodiments of the present application and is not intended to limit the protection scope of the embodiments of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the protection scope of the embodiments of the present application.

Claims (11)

1. A method for processing network registration, applied to a terminal device, the method comprising:

If the number of continuous network registration abnormality of the terminal equipment reaches a first preset number, the received first rejection information is stopped being converted into second rejection information, wherein the first rejection information is rejection information for prohibiting network registration, and the second rejection information is rejection information for allowing retry of network registration.

2. The method of claim 1, wherein the terminal device is in a network stability scenario, the network stability scenario being a scenario in which a cell of the terminal device is unchanged.

3. The method according to claim 1 or 2, wherein after stopping converting the received first reject information into the second reject information if the number of times the terminal device performs network registration continuation abnormality reaches the first preset number of times, the method further comprises:

If the number of continuous network registration abnormality of the terminal equipment reaches a second preset number, converting the received second rejection information into the first rejection information and prohibiting soft restart when the first rejection information is received, wherein the second preset number is larger than the first preset number.

4. The method according to claim 2, wherein before stopping converting the received first reject information into the second reject information if the number of consecutive anomalies in network registration by the terminal device reaches the first preset number of times, the method further comprises:

detecting the motion state of the terminal equipment;

and if the motion state belongs to a static state or a inching state, determining that the terminal equipment is in the network stable scene.

5. The method of claim 4, wherein the detecting the motion state of the terminal device comprises:

detecting the speed of the terminal equipment;

determining that the motion state belongs to the stationary state when the speed is 0;

And determining that the motion state belongs to the inching state when the speed is greater than 0 and continuously smaller than a first speed threshold, or when the speed is continuously greater than or equal to the first speed threshold and continuously longer than a continuously longer threshold, or when the accumulated time length of the speed greater than or equal to the first speed threshold is smaller than an accumulated time length threshold.

6. The method of claim 4, wherein if the motion state belongs to a stationary state or a jog state, the method further comprises, after determining that the terminal device is in the network stabilization scenario:

Determining network system information supported by the terminal equipment and frequency band information of each supported network system;

performing the network registration under each network system, and searching under each frequency band of each network system to perform the network registration;

If the rejection information corresponding to each network system is received and the network registration is still impossible to register after searching under each frequency band of each network system, determining that the network registration is abnormal, and adding one to the counted number of continuous network registration abnormality times of the terminal equipment.

7. The method according to any one of claims 3-6, wherein if the number of consecutive anomalies in network registration by the terminal device reaches a second preset number, converting the received second reject information into the first reject information and prohibiting soft restart upon receipt of the first reject information, the method further comprises:

If the terminal equipment is detected to be still in the network stability scene and exceeds a preset time period, or if the terminal equipment is detected to be still in the network stability scene and receives a user feedback instruction, initializing and allowing the network registration, wherein the initializing comprises at least one of zeroing the counted number of continuous abnormality of the network registration of the terminal equipment, allowing the received first rejection information to be converted into the second rejection information and allowing soft restart to be performed when the first rejection information is received.

8. The method according to any one of claims 3-6, further comprising:

And if the terminal equipment is detected not to be in the network stability scene, performing network registration in a default processing mode, wherein the default processing mode comprises the steps of allowing the received first rejection information to be converted into the second rejection information and allowing soft restart to be performed when the first rejection information is received.

9. A processing apparatus for network registration, applied to a terminal device, the apparatus comprising:

And the processing unit is used for stopping converting the received first rejection information into second rejection information if the number of continuous abnormal network registration times of the terminal equipment reaches a first preset number of times, wherein the first rejection information is rejection information for prohibiting network registration, and the second rejection information is rejection information for allowing retry of network registration.

10. A terminal device, comprising: a processor, a memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the processor, the programs comprising instructions for performing the steps in the method of any of claims 1-8.

11. A computer storage medium storing a computer program comprising program instructions which, when executed by a processor, cause the processor to perform the method of any of claims 1-8.