CN112888018A

CN112888018A - Network injection method and terminal equipment

Info

Publication number: CN112888018A
Application number: CN202110089817.0A
Authority: CN
Inventors: 谢朝阳
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-01-22
Filing date: 2021-01-22
Publication date: 2021-06-01
Anticipated expiration: 2041-01-22
Also published as: CN112888018B

Abstract

The embodiment of the invention discloses a network injection method and terminal equipment, which are applied to the technical field of communication and can be used for changing a first priority of a first network into a second priority when the first network has network congestion. The method comprises the following steps: when the first network has network congestion, modifying the first priority of the first network into a second priority; attempting to annotate the network at the second network in response to a change in priority of the first network; the first network is a network which is currently trying to log in the network, or a network which is logged in the network; the second priority is lower than the first priority, and the first network and the second network are networks of different PLMNs, or the first network and the second network are networks of different network systems of the first PLMN.

Description

Network injection method and terminal equipment

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a network injection method and terminal equipment.

Background

According to the current requirement of 3gpp ts24.501 for Congestion control, if the network side detects signaling Congestion, the Access and Mobility Management Function (AMF) will execute general Non-Access stratum (NAS) level Congestion control (generic NAS level Congestion control), and the AMF informs the terminal device that Congestion has occurred on the network side by carrying a reject message or a de-registration request with the cause value of #22(Congestion) for 5G network side reject service (5GMM), and at the same time, indicates the duration of a timer. When the terminal device receives the relevant message (i.e., the reject message or the deregistration request), the terminal device starts a corresponding timer, and the terminal device can only continue to reside in the current serving cell before the timer expires, and performs a normal cell reselection procedure, which may result in that the terminal device cannot normally provide services for a long time.

Disclosure of Invention

The embodiment of the invention provides a network injection method and terminal equipment, which are used for solving the problem that the terminal equipment can not normally provide service for a long time when congestion occurs on a network side in the prior art.

In order to solve the above technical problem, the embodiment of the present invention is implemented as follows:

in a first aspect, a method for networking is provided, including:

when network congestion occurs in a first network, modifying the first priority of the first network into a second priority;

attempting to annotate a network at a second network in response to a change in priority of the first network;

the first network is a network which is used for trying to annotate the network currently or is an annotated network; the second priority is lower than the first priority, and the first network and the second network are networks of different PLMNs, or the first network and the second network are networks of different network systems of the first PLMN.

In a second aspect, a terminal device is provided, which includes: the system comprises a processing module, a first priority and a second priority, wherein the processing module is used for modifying the first priority of a first network into the second priority when the network congestion occurs in the first network;

In a third aspect, a terminal device is provided, including: a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the networking method according to the first aspect.

In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the networking method according to the first aspect.

The embodiment of the invention provides a network injection method, which comprises the steps of modifying a first priority of a first network into a second priority when the first network has network congestion; attempting to annotate the network at the second network in response to a change in priority of the first network; the first network is a network which is currently trying to log in the network, or a network which is logged in the network; the second priority is lower than the first priority, and the first network and the second network are networks of different PLMNs, or the first network and the second network are networks of different network systems of the first PLMN. Through the scheme, when network congestion occurs in the first network, the terminal device can modify the priority of the first network into a second priority lower than the current first priority, so that the terminal device is triggered to respond to the change of the priority of the first network and try to perform network injection in the second network (networks of different PLMNs or networks of different network standards), and therefore when the network side is congested, the terminal device does not need to wait for a long time in the first network but actively tries to access other networks, time that the terminal device cannot normally provide service can be shortened, and service quality of the terminal device is guaranteed.

Drawings

Fig. 1 is a first schematic diagram illustrating general NAS level congestion control according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a general NAS level congestion control according to an embodiment of the present invention;

fig. 3 is a block diagram of a wireless communication system according to an embodiment of the present invention;

fig. 4A is a first schematic diagram illustrating a network injection method according to an embodiment of the present invention;

fig. 4B is a first schematic interface diagram of a terminal device according to an embodiment of the present invention;

fig. 4C is a schematic interface diagram of a terminal device according to an embodiment of the present invention;

fig. 4D is a third schematic interface diagram of a terminal device according to an embodiment of the present invention;

fig. 5 is a second schematic diagram of a network injection method according to an embodiment of the present invention;

fig. 6 is a third schematic diagram of a network injection method according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a hardware structure of a terminal device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that, in the embodiments of the present invention, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

First, the related technical content of the embodiment of the invention is introduced:

according to the current requirement of 3GPP TS24.501 on the Congestion control section, if the network side detects signaling Congestion, the AMF performs general NAS level Congestion control, and the AMF may notify the terminal device that Congestion has occurred by using a reject message or a de-registration request whose cause value for service rejection (5G network side cause value) is Congestion (#22(Congestion)) and simultaneously carries a value indication (back-off timer T3346 IE) of the duration of a mobility management fallback timer T3346 (hereinafter referred to as Congestion timer T3346 or T3346 timer), the terminal device starts the T3346 timer when receiving the reject message or the de-registration request, and considers that the information carried in the reject message is safe when the reject message is integrity protected, and the duration of the timer may adopt the value provided in the T3346 IE by the network side, when the reject message is not integrity protected, the information carried in the reject message is considered to be unsafe, and the duration of the timer may adopt a random value within a default range (e.g., between 15min and 30 min).

At present, when the congestion timer T3346 is started, the following scenarios are divided:

(1) emergency services;

(2) emergency service fallback (fallback);

(3) the UE is configured with high priority access on a current Public Land Mobile Network (PLMN);

(4) the UE initiates a de-registration request.

The terminal device is not allowed to initiate a signaling connection request, and cannot provide normal service. Wherein, the signaling connection request may include: initial registration requests, periodic/mobility registration requests, Service requests (Service requests), and the like.

Taking the 5G network as an example, when the 5G network is initially established, if the terminal device moves to an area with limited capacity and the current area data user is overloaded, the terminal device may receive congestion control from the network side (which may be a core network device).

As shown in fig. 1, a schematic diagram of general NAS level congestion control, where in the scenario shown in fig. 1, the terminal device is in a non-network-injection state, a specific interaction flow is as follows:

101. the network device detects the signaling congestion and decides to start the congestion control.

102. The terminal device sends a registration request message to the network device.

In the non-network-injection state of the terminal device, the terminal device may send a Registration Request message (Registration Request) to the network device to attempt network injection.

103. The network device sends a registration rejection message to the terminal device.

In case of network congestion at the network device, a registration rejection message may be sent to the terminal device.

In one implementation, the registration reject message may carry a value of the duration of the T3346 timer.

In another implementation, the network device may carry the value of the duration of the T3346 timer through other messages.

104. The terminal device starts a T3346 timer.

And the terminal equipment configures the T3346 timer according to the value of the duration of the T3346 timer and starts the T3346 timer.

105. After the T3346 timer expires, a registration request message is again sent to the network device.

In the current NAS level congestion control scenario, no registration request may be sent to the network device until the T3346 timer expires.

It can be seen that in the scenario shown in fig. 1, due to the reason of network side signaling congestion control, the terminal device fails to attempt to annotate the network, and may be in the network non-annotated state for a long time.

Fig. 2 is a schematic diagram of general NAS level congestion control, where in the scenario shown in fig. 2, the terminal device is in a network-injected state, and a specific interaction flow is as follows:

201. the network device detects the signaling congestion and decides to start the congestion control.

202. The terminal device sends a service request message to the network device.

The service request message is used for requesting the network device to provide the service for the terminal device.

The terminal device may send a Service Request message (Service Request) to the network device to Request the network device to provide a Service while the terminal device is in the network-attached state.

The above-mentioned service request procedure (i.e., sending the service request message) may also be a registration request procedure (i.e., sending the registration request message) triggered by a mobile registration update or a periodic registration (i.e., sending the registration request message).

203. The network device sends a service rejection message to the terminal device.

In the event of network congestion at the network device, a service rejection message may be sent to the terminal device.

In one implementation, the value of the duration of the T3346 timer may be carried in the service reject message.

204. The terminal device starts a T3346 timer.

205. After the T3346 timer expires, a service request message is again sent to the network device.

In current NAS level congestion control scenarios, the service request message may not be sent to the network device until the T3346 timer expires.

It can be seen that in the scenario shown in fig. 2, due to the network side signaling congestion control, the terminal device may be in the state of being in the network-injected state for a long time but cannot provide normal service.

In the scenario shown in fig. 1 or the scenario shown in fig. 2, based on the current protocol framework and the UE implementation mechanism, the UE can only continue to stay in the current serving cell, execute a normal cell reselection procedure, and wait for the T3346 timer to time out or the network side congestion is relieved, and then re-initiate signaling to recover the signaling connection with the network side to recover the normal service, which may result in that the normal service cannot be provided for a long time.

In order to solve the above problem, an embodiment of the present invention provides a network injection method, where when a network congestion occurs in a first network, a terminal device may modify a priority of the first network to a second priority lower than a current first priority, so as to trigger the terminal device to attempt to inject a network into a second network (a network of a different PLMN or a network of a different network type) in response to a change in the priority of the first network, so that when the network congestion occurs on a network side, the terminal device does not need to wait for a long time in the first network, but actively tries to access another network, thereby reducing a time during which the terminal device cannot normally provide a service, and ensuring a service quality of the terminal device.

Fig. 3 is a schematic diagram of an architecture of a wireless communication system applied in an embodiment of the present invention, where the wireless communication system includes a network device and a terminal device, and the network device may include a core network device and a base station. The architecture diagram of the wireless communication system shown in fig. 3 is merely an exemplary illustration, and in practice, the system may include more terminal devices or network devices, which is not limited in the embodiment of the present invention. In the embodiment of the present invention, the network congestion may refer to network congestion on a core network device side.

In this embodiment, the terminal device may be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, a user equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, 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 Network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like. In the embodiment of the invention, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.).

In the embodiment of the present invention, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in city (smart city), a wireless terminal device in smart home (smart home), or the like.

By way of example, and not limitation, in embodiments of the present invention, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a Next Radio (NR) system, or an evolved base station (evolved Node B) in an authorized assisted access long-term evolution (LAA-LTE) system, which may be an eNB or an e-NodeB) macro base station, a micro base station (also referred to as a "small base station"), a pico base station, an Access Point (AP), a Transmission Point (TP), or a new generation base station (g-NodeB).

The technical scheme of the embodiment of the invention can be applied to various communication systems, such as: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an Advanced Long Term Evolution (LTE-A) System, a New Radio (NR) System, an Evolution System of an NR System, an LTE (LTE-based Access to unlicensed spectrum, an LTE-U) System on an unlicensed spectrum, an NR (NR-based Access to unlicensed spectrum, an NR-U) System on an unlicensed spectrum, a Non-Terrestrial communication network (UMTS-based network, UMTS) System, a Universal Mobile telecommunications network (UMTS) System, WLAN), Wireless Fidelity (WiFi), a fifth Generation communication (5th-Generation, 5G) system, or other communication systems, etc.

It should be understood that the terms "system" and "network" are often used interchangeably herein.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.

In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In the description of the embodiments of the present invention, the term "correspond" may indicate that there is a direct correspondence or an indirect correspondence between the two, may also indicate that there is an association between the two, and may also indicate and be indicated, configure and configured, and so on.

As shown in fig. 4A, an embodiment of the present invention provides a network injection method, where the method includes:

401. and the terminal equipment modifies the first priority of the first network into the second priority when the network congestion occurs in the first network.

Optionally, the terminal device may receive a rejection message sent by the network device, where the rejection message may be used to indicate that the network congestion occurs in the first network, and after receiving the rejection message, the terminal device may learn that the network congestion occurs in the first network, and at this time, may modify the first priority of the first network to the second priority. Correspondingly, on the basis of the optional implementation manner, the reject message may carry a back-off timer T3346 value IE (back-off timer T3346 value IE) of the duration of the T3346 timer, and the terminal device may configure the duration of the T3346 timer according to the value indication.

Optionally, the terminal device may also determine that the network congestion occurs in the first network in other manners, for example, after sending the registration request message or the service request message, the terminal device does not receive the feedback message within a certain time, or may consider that the network congestion occurs in the first network, and at this time, the first priority of the first network may be modified to the second priority. Accordingly, on the basis of this optional implementation, the terminal device may configure the duration of the T3346 timer according to a random value between 15min and 30min, or the terminal device may configure the duration of the T3346 timer according to a preset duration.

The reject message may be a message rejecting a network injection request of the terminal device, or the reject message may be a message rejecting a service request of the terminal device.

Optionally, the first network is a network of a current interest network.

Illustratively, after 103 or 104 as shown in fig. 1, the terminal device may learn that network congestion occurs in the first network.

Optionally, the first network is a network already in charge of network.

Illustratively, after 203 or 204 shown in fig. 2, the terminal device may learn that network congestion occurs in the first network.

Wherein the second priority is lower than the first priority, and optionally, the second priority may be the lowest priority.

Optionally, the terminal device may modify the first priority of the first network to the second priority when the network congestion occurs in the first network and the target condition is satisfied. The embodiment of the invention specifically comprises the following implementation modes:

implementation A, if the first network has network congestion, the current terminal device is registered to the first network, and a user service request exists, the first priority of the first network is modified to the second priority.

In implementation B, if the network congestion occurs in the first network, the current terminal device is registered in the first network, there is a user service request, and the remaining duration of the congestion timer T3346 is greater than the preset duration, the first priority of the first network is modified to the second priority.

In implementation mode C, if the network congestion occurs in the first network, the current terminal device is registered in the first network, and the remaining duration of the congestion timer T3346 is greater than the preset duration, the first priority of the first network is modified to the second priority.

And D, if the first network has network congestion and the current terminal equipment is not registered to the first network, modifying the first priority of the first network into the second priority.

And E, if the first network has network congestion, the current terminal equipment is not registered to the first network, and the remaining time length of the congestion timer T3346 is greater than the preset time length, modifying the first priority of the first network into a second priority.

The preset duration may be a time length threshold set in combination with power consumption of the terminal device, and according to comparison between the preset duration and the remaining duration of T3346, whether the terminal device needs to recover service quickly may be determined in an auxiliary manner, and a current network priority is modified to trigger the terminal device to attempt to log in another network.

Optionally, when the network congestion occurs in the first network, the terminal device may output first query information, where the first query information is used to query the user whether to perform network selection again; after the terminal device outputs the first query information, a first selection input of a user for the first query information can be received, wherein the first selection input is used for confirming to re-execute network selection; the first priority of the first network is modified to a second priority in response to a first selection input.

The first query message may be an audio message, a text message, a video message, or the like.

Optionally, as shown in fig. 4B, a first interface for the terminal device to output query information is shown, where the terminal device queries, through outputting an interface shown as 41 and including text information, whether the current network is congested and whether to re-execute network selection, where the "yes" and "no" controls are set, and when the user clicks the "yes" control, the terminal device may be triggered to modify the first priority of the first network into the second priority, and attempt to perform network injection on the second network in response to the change in the priority. And when the user clicks the No control, the terminal equipment waits for the network congestion of the first network to be relieved.

It should be noted that, if the first query information may also be played in a voice broadcast manner, then the voice information of the user for the first query information is received, and the voice information is analyzed to know whether the user selects to re-execute network selection.

Optionally, one way to output the first query message is to output the following option information:

(1) an option to indicate waiting for network congestion relief;

(2) indicating an option to attempt to camp preferentially on other PLMNs;

after the terminal device outputs the option information, the terminal device receives input of a user for a first option, wherein the first option is an option indicating that the terminal device preferentially attempts to access to networks of other PLMNs.

For example, as shown in fig. 4C, which is a schematic diagram of an interface for outputting query information by a terminal device, the terminal device displays two options, namely "waiting for network congestion relief" and "trying to preferentially pour network to a network of another PLMN" by outputting text information as shown in 42, and when a user clicks a control of the "trying to pour network to a network of another PLMN preferentially" option, the terminal device may be triggered to modify a first priority of a first network into a second priority, and attempt to pour network in a second network in response to the change of the priority. And when the user clicks the control of the 'waiting network congestion relief' option, the terminal equipment waits for the network congestion relief of the first network.

Optionally, another way of outputting the first query information is to output the following option information:

(1) an option to indicate waiting for network congestion relief;

(2) indicating an option to attempt to provision networks to other PLMNs first;

(3) indicating the option to attempt to cast the network to the network of the other network standard first.

After the terminal device outputs the option information, the terminal device receives input of a user for a target option, wherein the target option is an option indicating that a network access to other PLMN is tried preferentially, or an option indicating that a network is preferred to be registered to other network systems.

For example, as shown in fig. 4D, a third interface schematic diagram of a terminal device outputting query information is shown, where the terminal device displays three options, namely, "wait for network congestion relief", "attempt to inject a network to another PLMN preferentially" and "attempt to inject a network to a network of another network system preferentially" by outputting text information as shown in 43, and when a user clicks a control of the option "attempt to inject a network to another PLMN preferentially" or the option "attempt to inject a network to a network of another network system preferentially", the terminal device may be triggered to modify the first priority of the first network into the second priority, and attempt to inject a network in the second network in response to the change in the priority. And when the user clicks the control of the 'waiting network congestion relief' option, the terminal equipment waits for the network congestion relief of the first network.

It should be noted that, the above-mentioned several implementations of outputting the first query message are merely exemplary descriptions, and there may be many possible implementations in practical applications, and the specific implementation form of outputting the first query message is not limited.

In the embodiment of the invention, when the first network has network congestion, the user can be inquired by outputting the inquiry information, and whether to execute network selection again is determined according to the selection input of the user to the inquiry information, so that the user will is considered, and the man-machine interaction performance is improved.

Further, after the user makes an input of whether to re-execute network selection according to the output inquiry information, the terminal device may store a selection record of the user, and in a subsequent network registration process of the terminal device, the user may receive, through an interface configured by the terminal device, that the user changes an option indicated by the previous selection record.

For example, the user selects "attempt to preferentially attempt network injection to a network of another PLMN" in the case of congestion of the first network, and the terminal device may retain the selection for use in the subsequent network injection process, but the user may modify the selection to "attempt network injection to a network of another network system preferentially" through an interface configured by the terminal device.

In the embodiment, an interface for modifying network selection by a user is configured, so that network selection can be flexibly realized.

Optionally, the network injection method provided in the embodiment of the present invention further includes:

and when the network congestion occurs in the first network, outputting a first prompt message, wherein the first prompt message is used for prompting the user that the tariff can be changed after the user re-executes the network selection.

Usually, the tariffs for networks of different PLMNs may be different, and the tariff of the terminal device may change after a handover from a network of a first PLMN to a network of another PLMN, so that the tariff may change in case of a network re-established to a network of another PLMN.

Illustratively, as shown in FIG. 4B, the "change in tariff" is prompted at the "YES" control.

Illustratively, as shown in fig. 4C, the "tariff may change" is prompted at a control of the "prior attempt to camp on a network of other PLMNs" option.

Illustratively, as shown in fig. 4D, the "tariff may be changed" is prompted at the control of the "network to which network injection is to be prioritized to other PLMN" option or the "network to which network injection is to be prioritized to other network standard" option.

Further, when the user selects to wait for the network congestion relief of the first network, the user may be prompted in the corresponding options in fig. 4B, 4C, and 4D for a waiting time period, for example, "wait for 3 minutes is expected" as shown in the figures.

In the network injection method, the user is prompted that the tariff may be changed after the network selection is re-executed, so that the user can refer to the prompt message to select whether to re-execute the network selection.

Further, the user may be notified of possible tariff adjustment conditions (e.g., an adjustment range of the tariff, for example, an expected increase of 30% of the tariff after network selection is re-performed) so that the user can select whether to re-perform network selection according to the specific adjustment conditions, thereby providing effective reference information for the user.

Optionally, in the network injection method provided in the embodiment of the present invention, when the network congestion occurs in the first network, the terminal device outputs a second prompt message, where the second prompt message is used to notify that the network congestion occurs in the first network, and the second prompt message includes a congestion waiting duration, where the congestion waiting duration is determined according to a remaining duration of the congestion timer T3346.

The congestion waiting duration may be the shortest duration that the current network congestion relief needs to wait.

In the network injection method, the user is prompted that the network equipment generates congestion and the shortest time length (congestion waiting time length) for waiting for the current network congestion relief is required, so that the user can refer to the congestion waiting time length prompting message to select whether to execute network selection again.

Optionally, the first query message, the first prompt message, and the second prompt message may be output through the same message, or the first query message, the first prompt message, and the second prompt message may also be output through different messages, which is not limited in the embodiment of the present invention.

402. The terminal device attempts to perform network injection in the second network in response to a change in the priority of the first network.

Optionally, the first network and the second network are networks of different PLMNs.

Illustratively, the first network may be a network in PLMN1, while the second network is a network in PLMN2, and PLMN1 is a different PLMN than PLMN 2.

Optionally, the first network and the second network are networks of different network systems of the first PLMN.

Illustratively, the first network is a 5G network of the first PLMN and the second network is a 4G network of the first PLMN.

In the embodiment of the present invention, the attempting to perform network injection in the second network in response to the change of the priority of the first network includes multiple possible implementations, which are separately described below.

In a first possible implementation: the first network and the second network are networks of different network systems of the first PLMN (network injection is attempted in the current PLMN);

the terminal equipment responds to the change of the priority of the first network and attempts network injection in one network of the first PLMN; if the network injection fails, attempting network injection in the next network of the first PLMN; until successful network injection to the target network or network injection failure at the first PLMN.

The network system priority of the last network test is higher than that of the next network test.

Optionally, the sequence of the network system priorities from top to bottom may be: 5G networks, 4G networks, 3G networks, and 2G networks.

For example, assuming that the first network is a 5G network in the first PLMN, the terminal device may first attempt to perform network injection in the 4G network in the first PLMN in response to a change in priority of the first network; if the network injection in the 4G network is successful, the 4G network provides service for the terminal equipment; if the network injection in the 4G network fails, continuing to attempt to inject the network in the 3G network of the first PLMN; if the network injection in the 3G network is successful, the 3G network provides service for the terminal equipment; if the network injection in the 3G network fails, continuing to attempt to inject the network in the 2G network of the first PLMN; if the network injection in the 2G network is successful, the 2G network provides service for the terminal equipment; and if the network injection fails in the 2G network, the network injection fails in the first PLMN.

Optionally, the sequence of the network system priorities from top to bottom may be: 5G networks, 4G networks (4G networks have the same priority as 5G networks), 3G networks, and 2G networks.

For example, assuming that the first network is a 5G network in the first PLMN, or a 4G network, the terminal device may first attempt to perform network injection in the 3G network in the first PLMN in response to a change in priority of the first network; if the network injection in the 3G network is successful, the 3G network provides service for the terminal equipment; if the network injection in the 3G network fails, continuing to attempt to inject the network in the 2G network of the first PLMN; if the network injection in the 2G network is successful, the 2G network provides service for the terminal equipment; and if the network injection fails in the 2G network, the network injection fails in the first PLMN.

It should be noted that the order of the network system priorities may also be in other realizable forms, and the embodiment of the present invention is not limited.

In the implementation manner, the network in the PLMN where the first network is located is preferentially selected to try to annotate the network, and when the network is not successfully annotated, the terminal device tries to annotate the network to other PLMNs, so that the terminal device can annotate the network in the current PLMN as much as possible, and the cost is not changed.

In a second possible implementation: the first network and the second network are networks of different network systems of the first PLMN (network injection is attempted in the current PLMN, and if the network injection fails, network injection is attempted in other PLMNs);

attempting a network injection at a network of the first PLMN in response to a change in priority of the first network; if the network injection fails, attempting network injection in the next network of the first PLMN; network injection failure in the first PLMN; network injection is attempted in a network of another PLMN; if the network injection fails, network injection is attempted in the network of the next other PLMN; until successful network injection to the target network or network injection failure at other PLMNs.

Wherein the other PLMNs are PLMNs different from the first PLMN of the first network;

the network system priority of the last network test is higher than that of the next network test; and/or the PLMN priority of the last network attempt is higher than the PLMN priority of the next network attempt.

In the embodiment of the invention, different PLMNs can correspond to different priorities.

Optionally, the priority of different PLMNs may be set according to the tariff of the different PLMNs. For example, the priority of the PLMN with lower tariff is set higher, and the priority of the PLMN with higher tariff is set lower.

It can be understood that the correspondence between different PLMNs and different priorities may also be set according to other manners except for the tariff level, and the embodiment of the present invention is not limited.

Further, assuming that PLMNs 1, 2, and 3 other than the first PLMN are available for the terminal device to attempt access, and the priorities of the PLMNs 1, 2, and 3 are sequentially from high to low, that the PLMN1 is higher than the PLMN2, and the PLMN2 is higher than the PLMN3, the terminal device may first attempt to perform network injection in the PLMN1 after the network injection failure of the first PLMN; if successful network injection in the PLMN1 is successful, the network of the PLMN1 provides service for the terminal equipment; if the network injection fails in the PLMN1, further attempts to inject the network in the PLMN2 can be made; if successful network injection in the PLMN2 is successful, the network of the PLMN2 provides service for the terminal equipment; if the network injection fails in the PLMN2, further attempting to inject the network into the PLMN3 may be performed, and if the network injection succeeds in the PLMN3, the network of the PLMN3 provides services for the terminal device; if the network injection fails at the PLMN3, the network injection fails at other PLMNs.

Optionally, the above procedure of attempting to perform network injection in PLMN1, the procedure of attempting to perform network injection in PLMN2, and the procedure of attempting to perform network injection in PLMN3 are similar to the above procedure of attempting to perform network injection in the first PLMN, and are not described here again.

Further, when network injection in the current PLMN is not successful, other PLMNs are used for network injection, and when network injection is performed in each PLMN, the network system priority is considered, so that the terminal device can inject the network to the network with the higher network system priority as much as possible, for example, the service quality can be preferentially ensured.

In a third possible implementation: the first network and the second network are networks of different network systems of the first PLMN, or the first network and the second network are networks of different PLMNs (network injection is tried in a network with a high network system priority level preferentially);

and trying to annotate the network according to the network system priority, and not limiting the first PLMN where the first network is located.

For example, assuming that the first network is a 5G network in the first PLMN, if PLMN1, PLMN2, and PLMN3 outside the first PLMN are available for the terminal device to attempt to participate in network injection, the terminal device may first attempt to participate in network injection in the 5G network in PLMN1, PLMN2, and PLMN3 after the network injection of the 5G network in the first PLMN fails; if the network injection of the 5G network in the PLMN1, the PLMN2 or the PLMN3 is successful, the 5G network in the PLMN1, the PLMN2 or the PLMN3 provides service for the terminal equipment; if the network injection of the 5G networks in the PLMNs fails, the 4G networks in the PLMNs can be further tried to try to inject the network; if the 4G network in each PLMN succeeds in network injection, the 4G network provides service for the terminal equipment; if the network injection of the 4G networks in the PLMNs fails, the network injection of the 3G networks in the PLMNs can be further tried, and if the network injection of the 3G networks in the PLMNs succeeds, the 3G networks provide services for the terminal equipment; if the network injection of the 3G network in each PLMN fails, the network injection can be further tried in the 2G network in each PLMN, and if the network injection of the 2G network in each PLMN succeeds, the 2G network provides service for the terminal equipment; and if the network injection of the 2G network in each PLMN fails, the network injection fails.

In the implementation manner, when network injection in the current first network is not successful, other PLMNs are used for network injection, and network system priority is preferentially considered when network injection is performed in each PLMN, so that the terminal equipment can inject the network to the network with higher network system priority as much as possible, and service quality can be preferentially ensured.

In a fourth possible implementation: the first network and the second network are networks of different PLMNs (network injection is attempted in other PLMNs);

attempting a network injection at a network of another PLMN in response to a change in priority of the first network; if the network injection fails, network injection is attempted in the network of the next other PLMN; until successful network injection to the target network or network injection failure at other PLMNs.

For example, assuming that PLMN1, PLMN2, and PLMN3 other than the first PLMN where the first network is located are available for the terminal device to attempt to access, and the priority of PLMN1, PLMN2, and PLMN3 is in order from high to low that PLMN1 is higher than PLMN2 and PLMN2 is higher than PLMN3, the terminal device may first attempt to perform network injection in PLMN1 after network injection failure of the first network; if the network injection is successful in the PLMN1, the network of the PLMN1 provides service for the terminal equipment; if the network injection fails in the PLMN1, further attempts to inject the network in the PLMN2 can be made; if successful network injection in the PLMN2 is successful, the network of the PLMN2 provides service for the terminal equipment; if the network injection fails in the PLMN2, further attempting to inject the network into the PLMN3 may be performed, and if the network injection succeeds in the PLMN3, the network of the PLMN3 provides services for the terminal device; if the network injection fails at the PLMN3, the network injection fails at other PLMNs.

In the implementation manner, when network injection cannot be successfully performed in the first PLMN where the current first network is located, other PLMNs are used for network injection, and when network injection is performed in each PLMN, the network system priority is considered, so that the terminal device can perform network injection to networks with higher network system priorities in other PLMNs as much as possible, service quality can be preferentially ensured to a greater extent, and the probability of network injection success is improved.

In the network injection method of the embodiment of the invention, when the terminal device attempts to successfully inject the network on the second network, namely successfully inject the network to the target network, the terminal device can output the notification message, and the notification message can prompt that the current network injection is successful and can normally provide service.

The notification message may also carry the network name of the network to be injected and other information (e.g., tariff information) of the network.

Optionally, in the network injection method provided in the embodiment of the present invention, after the terminal device attempts to perform network injection in the second network, if the terminal device successfully injects the network into the target network (which may be a network of the same PLMN as the first network, or a network of a PLMN that is not the same as the first network), the priority of the target network is determined; if the priority of the target network is less than the priority of the first network, determining the remaining duration of a congestion timer T3346; after the remaining time period, attempting to perform network injection in the first network.

Optionally, the terminal device may configure the duration of the back-off timer according to the remaining duration, and start the back-off timer; the duration of the back-off timer is greater than or equal to the remaining duration; after the back-off timer expires, a network injection is attempted in the first network.

For example, assuming that network congestion occurs in the previous first network (denoted as network 1), in the network injection method according to the embodiment of the present invention, network injection is successful in network 2, but the priority of network 2 is smaller than the priority of network 1, at this time, the remaining duration of congestion timer T3346 may be determined, and assuming that the remaining duration of congestion timer T3346 is 5min, the terminal device may wait for 5min, determine that network congestion of network 1 may have been relieved, and may attempt to return to network 1 to attempt network injection.

Optionally, before the terminal device attempts to perform network injection in the second network, the terminal device may record the previous first network (or first PLMN), for example, an identifier of the first network may be stored in the terminal device. Upon determining that the priority of the target network is lower than the recorded priority of the first network, an attempt may be made to return to the first network for network injection.

Since the terminal device needs to preferentially perform network injection to the network with high priority, after the network injection is switched from the first network to the target network, under the condition that the priority of the target network is low, after the remaining duration of the congestion timer T3346, namely after the T3346 timer is overtime, the terminal device may attempt to return to the first network for network injection so as to return to the network with high priority for network injection.

Optionally, after the network injection failure of the first PLMN where the first network is located is performed, or after the network injection failure of other PLMNs (that is, after the network injection failure of the second network), the terminal device may start a waiting timer, where a duration of the waiting timer is greater than or equal to 0 and less than the congestion timer T3346. If the congestion relief message is received within the duration of the waiting timer, the terminal device may attempt to participate in the network or request for service in the first network; if the congestion relief message is not received within the duration of the waiting timer, the terminal device may repeatedly perform the step of attempting to perform network injection in the second network after the waiting timer is overtime;

wherein the congestion removal message is used to indicate network congestion removal for the first network.

Optionally, in the embodiment of the present invention, the power consumption of the terminal device may be considered, and the duration of the waiting timer may be set for a scenario in which the network side may release the congestion state in advance.

For example, the longer the duration of the waiting timer is set, the more the power consumption of the terminal device is saved; the shorter the duration of the pending timers is set, the greater the power consumption of the terminal device.

Optionally, in the embodiment of the present invention, in the process of attempting to perform network injection in the second network (including the process of performing network injection in the first PLMN where the first network is located and the process of performing network injection in other PLMNs), if the congestion timer T3346 times out, the process of currently attempting to perform network injection is stopped, and the process of attempting to perform network injection in the first network is returned.

In the network injection method of the embodiment of the invention, when the terminal equipment returns the first network for network injection or returns the first network to request the service successfully, the terminal equipment can output a notification message which can prompt the current network to provide the service normally.

The notification message may also carry the name of the first network of the network to be injected and other information (e.g., tariff information) of the first network.

Optionally, in the case that the terminal device records the first network (or the first PLMN) before the terminal device attempts to perform network injection in the second network, the record for the first network or the first PLMN may be deleted after receiving the congestion relief message.

According to the implementation mode, in the process of network injection of the second network, aiming at the condition that the waiting timer is not overtime or still stays in the first network, if the congestion of the first network is determined to be relieved, the first network is immediately returned to the first network for network injection, so that the problem that the terminal equipment cannot provide the congestion for a long time is avoided, and meanwhile, network switching is not carried out to the maximum extent.

The following describes an exemplary network injection method provided by the embodiment of the present invention with respect to a scenario 1 in which the terminal device is in an unmarked state and a scenario 2 in which the terminal device is in a marked state.

In scenario 1, as shown in fig. 5, an embodiment of the present invention provides a network injection method, where the method includes:

501. the network device detects that the first network signaling is congested and decides to start congestion control.

502. The terminal device sends a registration request message to the network device.

The registration request message is used for requesting network injection in the first network.

503. The network device sends a registration rejection message to the terminal device.

The registration rejection message is used for indicating that the first network has network congestion, and rejecting the terminal device to perform network injection in the first network.

Optionally, the terminal device may receive a registration rejection message sent by the network device, and after receiving the registration rejection message, the terminal device may start the congestion timer T3346 and modify the first priority of the first network to the second priority.

Optionally, the terminal device may further receive duration indication information sent by the network device, where the duration indication information is used to indicate the duration of the congestion timer T3346.

It should be noted that the duration indication information may be carried in the registration request rejection message, and the network device may also send the duration indication information to the terminal device as a single message.

Optionally, the network device may notify the terminal device of the network Congestion of the first network through a cause value #22(Congestion) of the denial of service in the registration reject message, and carry a back-off timer T3346 value IE for the duration of the T3346 timer, so that when the terminal device receives the registration reject message, it may be known that the network Congestion of the network device occurs, the network cannot be registered in the first network, the T3346 timer needs to be started, and the network registration in the first network is retried after the T3346 timer is timed out.

504. The terminal device starts a T3346 timer.

Optionally, the duration of the T3346 timer may be configured by at least one of:

(1) the duration of the T3346 timer is configured according to the network device's indication, e.g., the back-off timer T3346 value IE described above.

(2) Configuring the duration of a T3346 timer according to a random value between 15min and 30 min;

(3) and configuring the duration of the T3346 timer according to the preset time length.

The preset time length can be configured in a manner specified by a standard protocol, or the preset time length can be configured in a manner indicated by network equipment, or the preset time length can be configured by a user through terminal equipment.

505. And when the target condition is met, the terminal equipment modifies the first priority of the first network into a second priority.

After the terminal device starts the T3346 timer, the first priority of the first network may be directly modified to the second priority without waiting for the timeout of the T3346 timer, so as to trigger the terminal device to attempt to perform network injection in another network in response to the change of the priority of the first network.

Generally, since the terminal device preferentially registers to the network with higher priority, after the priority of the first network is modified to be lower priority, the terminal device may be triggered to attempt to register to other networks with higher priority than the second priority.

In this embodiment, satisfying the target condition includes one of:

1) currently not registered with the first network;

2) the first network is not registered currently, and the remaining duration of the congestion timer T3346 is greater than the preset duration.

506. The terminal device attempts to perform network injection in the second network in response to a change in the priority of the first network.

For the description of 506, reference may be made to the description related to 402 above, which is not repeated here.

Alternatively, the terminal device may wait for the congestion timer T3346 to time out or for the network congestion of the first network to be relieved when the target condition is not satisfied.

In this embodiment, for a scenario in which the terminal device does not currently annotate the network, when trying to annotate the network, the network annotation due to the congestion at the network side is unsuccessful, the terminal device may trigger by modifying the priority, and the terminal device goes to other networks to try to annotate the network, thereby solving the problem that the terminal device cannot annotate the network for a long time and cannot provide service for the user due to the existing congestion control mechanism in this scenario.

As shown in fig. 6, an embodiment of the present invention provides a network injection method, where the method includes:

601. the network device detects the signaling congestion and decides to start the congestion control.

602. The terminal device sends a service request message to the network device.

The service request message is used for requesting the first network to provide service for the terminal equipment.

603. The network device sends a service rejection message to the terminal device.

The service rejection message is used for indicating that the first network has network congestion and rejecting to provide service for the terminal equipment.

Optionally, the terminal device may receive a service rejection message sent by the network device, and after receiving the service rejection message, the terminal device may start the congestion timer T3346 and modify the first priority of the first network to the second priority.

It should be noted that the duration indication information may be carried in a service request reject message or a deregistration request message, and the network device may also send the duration indication information to the terminal device as a single message.

Optionally, the network device may notify the terminal device of the network Congestion of the first network through a cause value #22(Congestion) of the service rejection message, and carry a back-off timer T3346 value IE for the duration of the T3346 timer, so that when the terminal device receives the service decision message, it may be known that the network Congestion of the network device fails to provide service for the terminal device, the T3346 timer needs to be started, and after the T3346 timer is overtime, the network device is retried to request the first network to provide service for the terminal device.

604. The terminal device starts a T3346 timer.

For the configuration manner of the duration of the T3346 timer, reference may be made to the related description in 504, and details are not described here.

605. And when the target condition is met, the terminal equipment modifies the first priority of the first network into a second priority.

In this embodiment, satisfying the target condition includes one of:

1) currently registered to a first network and having a user service request;

2) the current network is registered to the first network, a user service request exists, and the remaining time of the congestion timer T3346 is longer than the preset time;

3) the current network is registered to the first network, and the remaining duration of the congestion timer T3346 is greater than the preset duration.

606. The terminal device attempts to perform network injection in the second network in response to a change in the priority of the first network.

For the description of 606, reference may be made to the description related to 402 above, which is not repeated herein.

In this embodiment, for a scenario in which a terminal device has already been subscribed to a network, when requesting a service, a service request due to congestion at a network side is rejected, the terminal device may trigger by modifying a priority, and the terminal device attempts to subscribe to the network by another network, so as to solve a problem that the terminal device cannot provide the service for the terminal device for a long time due to an existing congestion control mechanism in the scenario, and thus the terminal device cannot provide the service for a user.

As shown in fig. 7, an embodiment of the present invention provides a terminal device, where the terminal device includes:

a processing module 701, configured to modify a first priority of a first network into a second priority when network congestion occurs in the first network;

attempting to annotate the network at the second network in response to a change in priority of the first network;

the first network is a network which is currently trying to log in the network, or a network which is logged in the network; the second priority is lower than the first priority, and the first network and the second network are networks of different PLMNs, or the first network and the second network are networks of different network systems of the first PLMN.

Optionally, the second priority is the lowest priority.

Optionally, the processing module 701 is specifically configured to receive a rejection message sent by the network device, where the rejection message is used to indicate that network congestion occurs in the first network; the first priority of the first network is modified to a second priority.

Optionally, the processing module 701 is specifically configured to receive a rejection message sent by the network device, start a congestion timer T3346, and modify the first priority of the first network into the second priority.

Optionally, the processing module 701 is further configured to receive duration indication information sent by the network device, where the duration indication information is used to indicate a duration of the congestion timer T3346.

Optionally, the processing module 701 is specifically configured to modify a first priority of the first network into a second priority when the target condition is met;

the satisfying of the target condition includes one of:

currently registered to a first network and a user service request exists;

the current time is registered to the first network, a user service request exists, and the remaining time of the congestion timer T3346 is longer than the preset time;

the current time is registered to the first network, and the remaining time of the congestion timer T3346 is longer than the preset time;

currently not registered with the first network;

the first network is not registered currently, and the remaining duration of the congestion timer T3346 is greater than the preset duration.

Optionally, the first network and the second network are networks of different network systems of the first PLMN, and the processing module 701 is specifically configured to attempt network injection in one network of the first PLMN in response to a change of the priority of the first network;

if the network injection fails, attempting network injection in the next network of the first PLMN;

until successful network injection to the target network or network injection failure at the first PLMN.

Optionally, the first network and the second network are networks of different PLMNs, and the processing module 701 is specifically configured to, in response to a change of the priority of the first network, attempt network injection in a network of another PLMN;

if the network injection fails, network injection is attempted in the network of the next other PLMN;

until successful network injection to the target network or network injection failure at other PLMNs.

Optionally, the processing module 701 is further configured to determine a priority of the target network after successful network injection to the target network; if the priority of the target network is less than the priority of the first network, determining the remaining duration of a congestion timer T3346; after the remaining time period, attempting to perform network injection in the first network.

Optionally, the processing module 701 is specifically configured to configure a duration of the back-off timer according to the remaining duration, and start the back-off timer; the duration of the back-off timer is greater than or equal to the remaining duration;

after the back-off timer expires, a network injection is attempted in the first network.

Optionally, the processing module 701 is further configured to start a waiting timer after the network injection failure of the first PLMN or after the network injection failure of other PLMNs, where a duration of the waiting timer is greater than or equal to 0 and is less than the congestion timer T3346;

if the congestion removal message is received within the duration of the waiting timer, trying to annotate the network or requesting service on the first network;

if the congestion removal message is not received within the duration of the waiting timer, repeatedly executing the step of trying to perform network injection in the second network after the waiting timer is overtime;

Optionally, the processing module 701 is further configured to, in response to the change of the priority of the first network, after attempting to perform network injection in the second network, in a process of attempting to perform network injection in the second network, if the congestion timer T3346 times out, stop a process of currently attempting to perform network injection; an attempt is made to annotate a network on a first network.

Optionally, the processing module 701 is specifically configured to output first query information when the network congestion occurs in the first network, where the first query information is used to query a user whether to re-execute network selection;

receiving a first selection input of a user for the first inquiry information, wherein the first selection input is used for confirming to re-execute network selection;

the first priority of the first network is modified to a second priority in response to a first selection input.

Optionally, the processing module 701 is specifically configured to output the following option information:

an option to indicate waiting for network congestion relief;

indicating an option to attempt to camp preferentially on other PLMNs;

the processing module 701 is specifically configured to receive an input of a user for a first option, where the first option is an option indicating a priority attempt to access to a network of another PLMN.

an option to indicate waiting for network congestion relief;

indicating an option to attempt to provision networks to other PLMNs first;

indicating the option to attempt to cast the network to the network of the other network standard first.

The processing module 701 is specifically configured to receive an input of a user for a target option, where the target option is an option indicating to preferentially attempt to access to a network of another PLMN, or an option indicating to preferentially attempt to provision a network of another network system.

Optionally, the processing module 701 is further configured to output a first prompt message when the network congestion occurs in the first network, where the first prompt message is used to prompt that the network congestion occurs in the first network, and the first prompt message includes a congestion waiting duration, and the congestion waiting duration is determined according to a remaining duration of the congestion timer T3346.

Optionally, the processing module 701 is further configured to output a second prompt message when the network congestion occurs in the first network, where the second prompt message is used to prompt the user that the tariff will be changed after the network selection is performed again.

The embodiment of the present invention further provides a terminal device, where the terminal device may include a processor, a memory, and a computer program stored in and executable on the memory, and when the computer program is executed by the processor, each process executed by the terminal device in the foregoing method embodiments may be implemented, and the same technical effect may be achieved, and in order to avoid repetition, details are not described here again.

Fig. 8 is a schematic diagram of a hardware structure of a terminal device according to an embodiment of the present invention. The terminal device may include: radio Frequency (RF) circuitry 810, memory 820, input unit 830, display unit 840, sensor 850, audio circuitry 860, wireless fidelity (WiFi) module 870, processor 880, and power supply 890. Radio frequency circuit 810 includes, among other things, a receiver 811 and a transmitter 812. Those skilled in the art will appreciate that the handset configuration shown in fig. 8 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The RF circuit 810 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, for processing downlink information of a base station after receiving the downlink information to the processor 880; in addition, the data for designing uplink is transmitted to the base station. In general, RF circuit 810 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuit 810 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), etc.

The memory 820 may be used to store software programs and modules, and the processor 880 executes various functional applications and data processing of the cellular phone by operating the software programs and modules stored in the memory 820. The memory 820 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 820 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 830 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 830 may include a touch panel 831 and other input devices 832. The touch panel 831, also referred to as a touch screen, can collect touch operations performed by a user on or near the touch panel 831 (e.g., operations performed by the user on the touch panel 831 or near the touch panel 831 using any suitable object or accessory such as a finger, a stylus, etc.) and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 831 may include two portions, i.e., a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts it to touch point coordinates, and sends the touch point coordinates to the processor 880, and can receive and execute commands from the processor 880. In addition, the touch panel 831 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 830 may include other input devices 832 in addition to the touch panel 831. In particular, other input devices 832 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 840 may be used to display information input by the user or information provided to the user and various menus of the cellular phone. The display unit 840 may include a display panel 841, and the display panel 841 may be configured in the form of a Liquid Crystal Display (LCD), an organic light-Emitting diode (OLED), or the like, as an option. Further, touch panel 831 can overlay display panel 841, and when touch panel 831 detects a touch operation thereon or nearby, communicate to processor 880 to determine the type of touch event, and processor 880 can then provide a corresponding visual output on display panel 841 based on the type of touch event. Although in fig. 8, the touch panel 831 and the display panel 841 are two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 831 and the display panel 841 may be integrated to implement the input and output functions of the mobile phone.

The terminal device may also include at least one sensor 850, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor that adjusts the brightness of the display panel 841 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 841 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

Audio circuitry 860, speaker 861, microphone 862 may provide an audio interface between the user and the handset. The audio circuit 860 can transmit the electrical signal converted from the received audio data to the speaker 861, and the electrical signal is converted into a sound signal by the speaker 861 and output; on the other hand, the microphone 862 converts collected sound signals into electrical signals, which are received by the audio circuit 860 and converted into audio data, which are then processed by the audio data output processor 880 and transmitted to, for example, another cellular phone via the RF circuit 810, or output to the memory 820 for further processing.

WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the WiFi module 870, and provides wireless broadband Internet access for the user. Although fig. 8 shows WiFi module 870, it is understood that it does not belong to the essential constitution of the handset, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 880 is a control center of the mobile phone, connects various parts of the entire mobile phone using various interfaces and lines, and performs various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 820 and calling data stored in the memory 820, thereby integrally monitoring the mobile phone. Optionally, processor 880 may include one or more processing units; preferably, the processor 880 may integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 880.

The handset also includes a power supply 890 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 880 via a power management system to manage charging, discharging, and power consumption. Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.

In this embodiment of the present invention, the processor 880 is configured to modify a first priority of the first network to a second priority when the first network has network congestion;

Optionally, the second priority is the lowest priority.

Optionally, the radio frequency circuit 810 is configured to receive a rejection message sent by the network device, where the rejection message is used to indicate that network congestion occurs in the first network; the processor 880 modifies the first priority of the first network to the second priority after the radio frequency circuit 810 receives the rejection message sent by the network device.

Optionally, the radio frequency circuit 810 is specifically configured to receive a rejection message sent by the network device, start the congestion timer T3346, and the processor 880 modifies the first priority of the first network to the second priority after the radio frequency circuit 810 receives the rejection message sent by the network device.

Optionally, the radio frequency circuit 810 is further configured to receive duration indication information sent by the network device, where the duration indication information is used to indicate a duration of the congestion timer T3346.

Optionally, the processor 880 is specifically configured to modify the first priority of the first network to the second priority when the target condition is met;

the satisfying of the target condition includes one of:

currently registered to a first network and a user service request exists;

currently not registered with the first network;

Optionally, the first network and the second network are networks of different network types of the first PLMN, and the processor 880 is specifically configured to attempt network injection in one network of the first PLMN in response to a change in priority of the first network;

Optionally, the first network and the second network are networks of different PLMNs, and the processor 880 is specifically configured to, in response to a change in priority of the first network, attempt network injection at a network of another PLMN;

Optionally, the processor 880 is further configured to determine the priority of the target network after successful network injection to the target network; if the priority of the target network is less than the priority of the first network, determining the remaining duration of a congestion timer T3346; after the remaining time period, attempting to perform network injection in the first network.

Optionally, the processor 880 is specifically configured to configure a duration of the back-off timer according to the remaining duration, and start the back-off timer; the duration of the back-off timer is greater than or equal to the remaining duration;

Optionally, the processor 880 is further configured to start a wait timer after the network injection failure of the first PLMN or after the network injection failure of the other PLMNs, where a duration of the wait timer is greater than or equal to 0 and less than the congestion timer T3346;

Optionally, the processor 880 is further configured to, in response to the change of the priority of the first network, after attempting to perform network injection in the second network, stop the current process of attempting to perform network injection if the congestion timer T3346 times out in the process of attempting to perform network injection in the second network; an attempt is made to annotate a network on a first network.

Optionally, the processor 880 is specifically configured to control the display unit 840 or the audio circuit 860 to output first query information when network congestion occurs in the first network, where the first query information is used to query the user whether to perform network selection again; and controlling the RF circuit 810 to receive a first selection input of the user for the first query information, the first selection input for confirming to re-perform the network selection; the first priority of the first network is modified to a second priority in response to a first selection input.

Optionally, the processor 880 is specifically configured to output the following option information:

an option to indicate waiting for network congestion relief;

indicating an option to attempt to camp preferentially on other PLMNs;

the processor 880 is specifically configured to control the RF circuitry 810 to receive user input for a first option, the first option being an option indicating a prior attempt to access a network of another PLMN.

an option to indicate waiting for network congestion relief;

indicating an option to attempt to provision networks to other PLMNs first;

The processor 880 is specifically configured to receive, through the RF circuit 810, a user input for a target option, where the target option is an option indicating a preferential attempt to access a network of another PLMN or an option indicating a preferential attempt to participate in a network of another network system.

Optionally, the processor 880 is further configured to output a first prompt message through the display unit 840 or the audio circuit 860 when the network congestion occurs in the first network, where the first prompt message is used to prompt the first network to have the network congestion, and the first prompt message includes a congestion waiting duration, where the congestion waiting duration is determined according to a remaining duration of the congestion timer T3346.

Optionally, the processor 880 is further configured to output a second prompt message through the display unit 840 or the audio circuit 860 when the network congestion occurs in the first network, where the second prompt message is used to prompt the user that the tariff will be changed after the network selection is performed again.

An embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process executed by a terminal device in the foregoing method embodiments, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A network injection method is applied to terminal equipment and comprises the following steps:

2. The method of claim 1, wherein the second priority is a lowest priority.

3. The method of claim 1, wherein modifying the first priority of the first network to the second priority when network congestion occurs in the first network comprises:

receiving a rejection message sent by a network device, wherein the rejection message is used for indicating that the first network has network congestion; modifying the first priority of the first network to the second priority.

4. The method of claim 3, wherein modifying the first priority of the first network to the second priority when network congestion occurs in the first network comprises:

and receiving the rejection message sent by the network equipment, starting a congestion timer T3346, and modifying the first priority of the first network into a second priority.

5. The method of claim 4, further comprising:

and receiving duration indication information sent by the network equipment, wherein the duration indication information is used for indicating the duration of the congestion timer T3346.

6. The method of claim 4, wherein modifying the first priority of the first network to the second priority comprises:

when a target condition is met, modifying the first priority of the first network into a second priority;

the meeting of the target condition includes one of:

currently registered with the first network and having a user service request;

when the user service request exists, the user service request is registered to the first network, and the remaining time length of the congestion timer T3346 is greater than the preset time length;

currently registered to the first network, and the remaining duration of the congestion timer T3346 is greater than a preset duration;

is not currently registered with the first network;

the congestion timer T3346 is not registered to the first network currently, and the remaining duration of the congestion timer T3346 is greater than a preset duration.

7. The method according to any of claims 1 to 6, wherein the first network and the second network are networks of different network systems of a first PLMN, and the attempting to perform network injection in the second network in response to the change of the priority of the first network comprises:

attempting a network injection at a network of the first PLMN in response to a change in priority of the first network;

if the network injection fails, attempting network injection in a next network of the first PLMN;

until successful network injection to the target network, or network injection failure in the first PLMN;

8. The method of any of claims 1 to 6, wherein the first network and the second network are networks of different PLMNs, and wherein attempting to annotate the network at the second network in response to the change in priority of the first network comprises:

attempting a network injection at a network of another PLMN in response to a change in priority of the first network;

if the network injection fails, network injection is attempted in the network of the next PLMN;

until successful network injection to the target network, or network injection failure in the other PLMN;

wherein the other PLMN is a different PLMN than a first PLMN of the first network;

9. The method according to claim 7 or 8, wherein after the successful network injection to the target network, further comprising:

determining a priority of the target network;

if the priority of the target network is less than the priority of the first network, determining the remaining duration of the congestion timer T3346;

attempting to perform network injection in the first network after the remaining duration.

10. The method of claim 9, wherein attempting to advertise in the first network after the remaining duration comprises:

configuring the duration of a back-off timer according to the residual duration, and starting the back-off timer; the duration of the back-off timer is greater than or equal to the remaining duration;

attempting to perform network injection in the first network after the back-off timer expires.

11. The method according to claim 7 or 8, wherein after the first PLMN network injection failure or after the other PLMN network injection failure, further comprising:

starting a waiting timer, wherein the duration of the waiting timer is greater than or equal to 0 and less than the congestion timer T3346;

if a congestion relief message is received within the duration of the waiting timer, attempting to log in the network or requesting service on the first network;

if the congestion removal message is not received within the duration of the waiting timer, after the waiting timer is overtime, the step of trying to perform network injection in the second network is repeatedly executed;

wherein the congestion relief message is used to indicate network congestion relief for the first network.

12. The method of claim 1, wherein attempting to target a network in a second network in response to the change in priority of the first network comprises:

in the process of trying to perform network injection in the second network, if the congestion timer T3346 is overtime, stopping the process of trying to inject the network currently;

attempting to annotate a network on the first network.

13. The method of claim 4, wherein modifying the first priority of the first network to the second priority when network congestion occurs in the first network comprises:

when network congestion occurs in a first network, outputting first inquiry information, wherein the first inquiry information is used for inquiring whether a user performs network selection again;

receiving a first selection input of the user for the first query information, the first selection input being used to confirm re-execution of network selection;

modifying a first priority of the first network to a second priority in response to the first selection input.

14. The method of claim 13, wherein outputting the first query message comprises:

the following option information is output:

an option to indicate waiting for network congestion relief;

indicating an option to attempt to camp preferentially on other PLMNs;

the receiving a first selection input of the user for the first query information includes:

receiving input of a user for a first option, wherein the first option is an option of indicating a prior attempt to access to networks of other PLMNs.

15. The method of claim 13, wherein outputting the first query message comprises:

the following option information is output:

an option to indicate waiting for network congestion relief;

indicating an option to attempt to provision networks to other PLMNs first;

indicating an option to preferentially attempt to annotate a network to a network of another network type;

and receiving input of a user for a target option, wherein the target option is an option indicating that a network of other PLMN is tried to be accessed preferentially, or an option indicating that a network of other network system is tried to be accessed preferentially.

16. The method of claim 13, further comprising:

when the network congestion occurs in the first network, outputting a first prompt message, wherein the first prompt message is used for prompting the network congestion of the first network, the first prompt message comprises congestion waiting time, and the congestion waiting time is determined according to the remaining time of the congestion timer T3346.

17. The method of claim 13, further comprising:

and when the first network has network congestion, outputting a second prompt message, wherein the second prompt message is used for prompting that the user changes the tariff after re-executing network selection.

18. A terminal device, comprising:

the system comprises a processing module, a first priority and a second priority, wherein the processing module is used for modifying the first priority of a first network into the second priority when the network congestion occurs in the first network; attempting to annotate a network at a second network in response to a change in priority of the first network;

19. A terminal device, comprising: a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the networking method of any one of claims 1 to 17.

20. A computer-readable storage medium, comprising: the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the networking method of any of claims 1 to 17.