CN112888018B

CN112888018B - Network injection method and terminal equipment

Info

Publication number: CN112888018B
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: 2023-07-25
Anticipated expiration: 2041-01-22
Also published as: CN112888018A

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 modifying a first priority of a first network into a second priority when network congestion occurs in the first network. Comprising the following steps: when the first network is congested, modifying the first priority of the first network to a second priority; attempting to annotate on the second network in response to a change in priority of the first network; the first network is a network which tries to annotate the network at present or is already annotated; 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 PLMNs.

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 3GPPTS24.501 requirement for Congestion control, if the network side detects signaling Congestion, the access and mobility management function (Access and Mobility Management Function, AMF) performs normal Non-access stratum (NAS) level Congestion control (general NAS level Congestion control), and the AMF informs the terminal device that Congestion has occurred at the network side by carrying a reject message or deregistration request with a cause value #22 (Congestion) of 5G network side reject service (5 GMM), and at the same time indicates the duration of a timer. When the terminal device receives the related message (i.e. reject message or deregistration request), the terminal device starts a corresponding timer, and the terminal device can only stay in the current serving cell until the timer is overtime, and performs a normal cell reselection procedure, which may cause 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 at a network side in the prior art.

In order to solve the technical problems, the embodiment of the invention is realized as follows:

in a first aspect, a method for injecting a net 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 place a mesh on a second network in response to a change in priority of the first network;

the first network is a network which is currently tried to be annotated, or a network which is already annotated; 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, there is provided a terminal device comprising: the processing module is used for modifying the first priority of the first network into the second priority when the first network is congested;

In a third aspect, there is provided a terminal device comprising: a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program implementing the method of casting a net as in the first aspect when executed by the processor.

In a fourth aspect, a computer readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, implements the method of casting a net as in the first aspect.

The embodiment of the invention provides a network injection method, which is used for modifying a first priority of a first network into a second priority when network congestion occurs in the first network; attempting to annotate on the second network in response to a change in priority of the first network; the first network is a network which tries to annotate the network at present or is already annotated; 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 PLMNs. Through the scheme, when the first network is congested, the terminal equipment can modify the priority of the first network into the second priority lower than the current first priority, so that the terminal equipment is triggered to respond to the change of the priority of the first network, and network injection is attempted to be carried out on the second network (networks of different PLMNs or networks of different network systems), so that when congestion occurs on the network side, the terminal equipment does not need to wait for a longer time on the first network, but actively tries to access other networks, thereby reducing the time that the terminal equipment cannot normally provide service and ensuring the service quality of the terminal equipment.

Drawings

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

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

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

fig. 4A is a schematic diagram of a method for injecting a net according to an embodiment of the present invention;

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

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

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

fig. 5 is a schematic diagram two of a method for injecting a net according to an embodiment of the present invention;

fig. 6 is a schematic diagram III of a method for injecting a net 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 hardware structure of a terminal device according to an embodiment of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

It should be noted that, in the embodiments of the present invention, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

First, the related technical content of the embodiment of the present invention will be described:

according to the current requirements of 3gpp ts24.501 regarding Congestion control chapters, if the network side detects signaling Congestion, the AMF may perform general NAS level Congestion control, and the AMF may notify the terminal device of Congestion by using a reject message or deregistration request that the cause value of 5G network side reject service (5 GMM cause value) is Congestion (# 22), and at the same time, the network device carries a value indication (back-off timer T3346 value IE) of the duration of a mobility management fallback timer T3346 (hereinafter may be referred to as Congestion timer T3346, or referred to as T3346 timer), when receiving the reject message or deregistration request, the terminal device may start the T3346 timer, and when the reject message has been integrity protected, consider the information carried in the reject message to be safe, and at the same time, the duration of the timer may adopt the value provided in the T3346 value IE by the network side, and when the reject message has not been integrity protected, consider the information carried in the reject message to be not be safe, and may adopt a range of, for example, from the duration of 30min to a random value (for example, may be in a range of 30 min).

Currently, when the congestion timer T3346 is started, the following scenario is divided:

(1) An emergency service;

(2) Emergency service fallback (fallback);

(3) The UE is configured with high priority access on the current public land mobile network (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 normal service cannot be provided. Wherein the signaling connection request may include: initial registration requests, periodic/mobility registration requests, and Service requests (Service requests), etc.

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 the core network device).

As shown in fig. 1, which is a schematic diagram of general NAS level congestion control, in the scenario shown in fig. 1, a terminal device is in a state of not injecting a network, and a specific interaction flow is as follows:

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

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

The terminal device may send a registration request message (Registration Request) to the network device to attempt to annotate the network while the terminal device is in an un-annotated state.

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

In case of network congestion of the network device, a registration reject 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.

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, a registration request may not be sent to the network device until the T3346 timer expires.

It can be seen that in the scenario shown in fig. 1, the terminal device tries to inject the network unsuccessfully due to the congestion control of the network side signaling, and may be in the state of not injecting the network for a long time.

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

201. The network device detects the signaling congestion and decides to initiate 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 service for the terminal device.

In the network-infused state, the terminal device may send a Service Request message (Service Request) to the network device to Request provision of a Service from the network device.

The above-mentioned request for service process (i.e. sending a service request message) may also be due to a mobile registration update or a registration request process triggered by periodic registration (mobility registration updating or periodic registration) (i.e. sending a registration request message).

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

In case of network congestion of the network device, a service reject message may be sent to the terminal device.

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

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 the current NAS level congestion control scenario, a 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, the terminal device may be in the network-injected state for a long time, but cannot provide normal service, due to the network-side signaling congestion control.

In the scenario shown in fig. 1, or in the scenario shown in fig. 2, based on the current protocol frame and the UE implementation mechanism, the UE can only continue to wait in the current serving cell, execute a normal cell reselection procedure, wait for the timeout of the T3346 timer or after the congestion on the network side is relieved, and can restart the connection between signaling and the network side to resume the normal service, which may result in failing to provide the normal service for a long time.

In order to solve the above-mentioned problems, an embodiment of the present invention provides a network injection method, where when a first network is congested, 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 respond to a change of the priority of the first network, and attempt to perform network injection on a second network (networks of different PLMNs or networks of different network systems) so that when congestion occurs on a network side, the terminal device does not need to wait for a long time on the first network, but actively try to access other networks, thereby reducing a time when the terminal device cannot normally provide services, and ensuring service quality of the terminal device.

Fig. 3 is a schematic architecture diagram of a wireless communication system, 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 invention, the network congestion can refer to network congestion at the core network equipment side.

In the embodiment of the present invention, 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 device, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal 40Digital Assistant,PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle 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 (Public Land Mobile Network, PLMN) network, etc. 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 ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, 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 (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned 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 security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present invention, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The 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 can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

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-generation (NR) system, or an evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, a micro base station (also called "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.

The technical scheme of the embodiment of the invention can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

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

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

In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

In the description of the embodiments of the present invention, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, etc.

As shown in fig. 4A, an embodiment of the present invention provides a method for injecting a net, which includes:

401. when the first network is congested, the terminal equipment modifies the first priority of the first network into the second priority.

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 first network is congested, and after the terminal device receives the rejection message, it may learn that the first network is congested, and at this time, the first priority of the first network may be modified to be the second priority. Accordingly, on the basis of the alternative implementation manner, the reject message may carry a value indication (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 determine that the first network is congested in other manners, for example, after sending the registration request message or the service request message, the feedback message is not received for a certain period of time, or may consider that the first network is congested, where the first priority of the first network may be modified to be the second priority. Accordingly, on the basis of this alternative implementation manner, 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 rejection message may be a message for rejecting the network injection request of the terminal device, or the rejection message may be a message for rejecting the service request of the terminal device.

Optionally, the first network is a network of current trial injection networks.

Illustratively, after 103 or 104 described above and shown in fig. 1, the terminal device may learn that the first network is congested.

Optionally, the first network is an already-injected network.

Illustratively, after 203 or 204 described above and shown in fig. 2, the terminal device may learn that the first network is congested.

Wherein the second priority is lower than the first priority, 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 first network is congested and the target condition is satisfied. The embodiment of the invention specifically comprises the following implementation modes:

implementation a, if the first network is congested, the current terminal device is registered with the first network, and there is a user service request, modifying the first priority of the first network to a second priority.

Implementation B, if the first network is congested, the current terminal device is registered in the first network, there is a user service request, and the remaining time period of the congestion timer T3346 is longer than a preset time period, modifying the first priority of the first network to the second priority.

Implementation C, if the first network is congested, the current terminal device is registered in the first network, and the congestion timer T3346 is longer than the preset duration, modifying the first priority of the first network to the second priority.

Implementation D, if the first network is congested and the current terminal device is not registered in the first network, modifying the first priority of the first network to the second priority.

Implementation E, if the first network is congested, the current terminal device is not registered in the first network, and the congestion timer T3346 is longer than the preset duration, modifying the first priority of the first network to the second priority.

The preset duration may be a time duration 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, it may be assisted to determine whether the terminal device needs to quickly restore service, and modify the current network priority to trigger the terminal device to attempt to annotate the network in other networks.

Optionally, when the first network is congested, the terminal device may output first query information, where the first query information is used to query the user whether to re-perform network selection; after the terminal device outputs the first query information, a first selection input of the user for the first query information may be received, the first selection input being used to confirm re-execution of the network selection; the first priority of the first network is modified to a second priority in response to the first selection input.

The first query information may be audio information, text information, video information, etc.

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

It should be noted that if the first query information is also played in a voice broadcast manner, then the user can learn whether to re-execute the network selection by receiving the voice information of the user for the first query information and analyzing the voice information.

Optionally, one way to output 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 annotate the network preferentially to other PLMNs;

after the terminal device outputs the option information, the terminal device receives an input from a user for a first option, where the first option is an option indicating a network that preferentially tries to access 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 of "waiting for network congestion relief" and "first try to annotate networks to other PLMNs" by outputting text information as shown in 42, and when the user clicks a control of "first try to annotate networks to other PLMNs", the terminal device may be triggered to modify the first priority of the first network to the second priority, and attempt to annotate networks in the second network in response to the change of the priority. When the user clicks the control of the "wait for network congestion relief" option, the terminal device waits for network congestion relief of the first network.

Alternatively, another way to output 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 prioritize network injection to networks of other PLMNs;

(3) Indicating an option to prioritize network injection to networks of other network formats.

After the terminal device outputs the option information, the terminal device receives input of a user aiming at a target option, wherein the target option is an option for indicating to preferentially try to access to the network of other PLMN or an option for indicating to preferentially try to annotate the network to the network of other network modes.

As an example, as shown in fig. 4D, which is a schematic diagram of an interface for outputting query information by a terminal device, the terminal device displays three options of "waiting for network congestion relief", "first-trial-injection-to-other-PLMN networks", and "first-trial-injection-to-other-network-system networks" by outputting text information as shown in 43, and when the user clicks a control of "first-trial-injection-to-other-PLMN network" option or "first-trial-injection-to-other-network-system network" option, the terminal device may be triggered to modify the first priority of the first network to the second priority, and in response to the priority change, attempt to perform injection on the second network. When the user clicks the control of the "wait for network congestion relief" option, the terminal device waits for network congestion relief of the first network.

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

In the embodiment of the invention, when the first network is congested, the user can be queried by outputting the query information, and whether the network selection is to be re-executed is determined according to the selection input of the user to the query information, so that the user will is considered, and the man-machine interaction performance is improved.

Further, after the user makes an input whether to re-execute the network selection according to the output query information, the terminal device may save the selection record of the user, and in the subsequent network injection process of the terminal device, the user may also receive, through an interface configured by the terminal device, the user to change the option indicated by the previous selection record.

For example, in the case of congestion in the first network, the user selects "take preference for the network of the other PLMN", and the terminal device may keep the selection for use in the subsequent network injection process, but the user may also modify the selection to "take preference for the network of the other network system" through the interface configured by the terminal device.

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

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

when the first network is congested, a first prompt message is output, and the first prompt message is used for prompting a user to change tariffs after network selection is performed again.

Generally, the tariffs corresponding to networks of different PLMNs may be different, and after switching from the network of the first PLMN to the network of another PLMN, the tariffs of the terminal device may change, so that the tariffs may change in case of re-injecting the network to the networks of other PLMNs.

Illustratively, as shown in FIG. 4B, the "Yes" control is presented with "tariffs may change".

Illustratively, as shown in FIG. 4C, the "tariff may change" is prompted at a control of the "network to try first to annotate network to other PLMNs" option.

Illustratively, as shown in fig. 4D, the "tariff may change" is prompted at a control of the "take precedence to network of other PLMNs" option or "take precedence to network of other network formats" 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 to wait for a period of time, for example, "3 minutes is expected to wait" as shown in the figures.

In the above-mentioned network injection method, the tariff may be changed after the user is prompted to re-perform the network selection, in such a way that the user refers to the prompting message to select whether to re-perform the network selection.

Further, the user may also be notified of possible tariff adjustment conditions (e.g., adjustment range of tariffs, e.g., estimated 30% increase in tariffs after re-performing network selection) so that the user may choose whether to re-perform network selection based on the particular adjustment conditions, providing the user with valid reference information.

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

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

In the above-mentioned network injection method, the user is prompted to generate congestion, and the current network congestion is relieved and needs to wait for the shortest time (congestion waiting time), in this way, the user is enabled to choose whether to execute network selection again by referring to the congestion waiting time prompting message.

Optionally, the first query message, the first prompt message and the second prompt message may be output through the same message, and 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 annotate the network on the second network in response to a change in priority of the first network.

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

For example, the first network may be a network in PLMN1 and the second network is a network in PLMN2, and PLMN1 and PLMN2 are different PLMNs.

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, in response to a change in priority of the first network, attempting to perform a network injection on the second network includes a plurality of possible implementations, which are 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 tried in the current PLMN);

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

The network type priority of the previous trial injection network is higher than that of the next trial injection network.

Optionally, the order of the network system priority from top to bottom may be: 5G, 4G, 3G, 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 annotate the 4G network in the first PLMN in response to a change in priority of the first network; if the network injection is successful in the 4G network, the 4G network provides service for the terminal equipment; if the network injection fails in the 4G network, continuing to attempt the network injection in the 3G network of the first PLMN; if the network injection is successful in the 3G network, the 3G network provides service for the terminal equipment; if the network injection fails in the 3G network, continuing to attempt the network injection in the 2G network of the first PLMN; if the network injection is successful in the 2G network, the 2G network provides service for the terminal equipment; if the network connection fails in the 2G network, the network connection fails in the first PLMN.

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

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 annotate the network in the 3G network in the first PLMN in response to a change in priority of the first network; if the network injection is successful in the 3G network, the 3G network provides service for the terminal equipment; if the network injection fails in the 3G network, continuing to attempt the network injection in the 2G network of the first PLMN; if the network injection is successful in the 2G network, the 2G network provides service for the terminal equipment; if the network connection fails in the 2G network, the network connection fails in the first PLMN.

It should be noted that, the order of the network system priorities may also be 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 selected preferentially to try to annotate the network, and when the annotating is unsuccessful, the network is tried 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 tariffs are not changed.

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

attempting to annotate at one network of the first PLMN in response to a change in priority of the first network; if the network injection fails, the next network of the first PLMN tries to perform the network injection; failing to annotate the network in the first PLMN; attempting to annotate the network at one other PLMN; if the network injection fails, the network of the next other PLMN tries to perform the network injection; until successful network injection to the target network or failure in other PLMNs.

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

The network system priority of the last trial injection network is higher than that of the next trial injection network; and/or, the PLMN priority of the last trial-and-error network is higher than the PLMN priority of the next trial-and-error network.

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

Optionally, the priority of different PLMNs may be set according to the tariffs of different PLMNs. For example, a higher priority setting for a lower tariff PLMN will result in a lower priority setting for a higher tariff PLMN.

It can be understood that the correspondence between different PLMNs and different priorities may be set according to other manners besides tariffs, which is not limited by the embodiment of the present invention.

Further, if PLMN1, PLMN2 and PLMN3 other than the first PLMN are available for the terminal equipment to attempt access, and the priority of PLMN1, PLMN2 and PLMN3 is higher than PLMN2 and PLMN2 is higher than PLMN3 in order from high to low, then the terminal equipment may attempt to annotate the network in PLMN1 after the first PLMN fails to annotate the network; if the network injection in the PLMN1 is successful, providing service for the terminal equipment by the network of the PLMN 1; if the network injection fails in the PLMN1, further attempting to inject the network in the PLMN2 can be tried; if the network injection in the PLMN2 is successful, providing service for the terminal equipment by the network of the PLMN 2; if the network injection in the PLMN2 fails, the network injection in the PLMN3 can be further tried, and if the network injection in the PLMN3 is successful, the network of the PLMN3 provides service for the terminal equipment; if the network injection fails in the PLMN3, the network injection fails in other PLMNs.

Optionally, the above procedure of attempting to annotate in PLMN1, the procedure of attempting to annotate in PLMN2, and the procedure of attempting to annotate in PLMN3 are similar to the procedure of attempting to annotate in the first PLMN, and are not repeated here.

Further, when the current PLMN cannot successfully perform network injection, the network injection is performed to other PLMNs, and when the network injection is performed in each PLMN, the network type priority is considered, so that the terminal device can inject the network as much as possible to the network with the higher network type priority, 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 systems are preferentially tried to be annotated in a network with high network system priority);

and trying to annotate the network according to the network type 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 other than the first PLMN are available for the terminal device to try to annotate the network, the terminal device may try to annotate the network in the 5G network in PLMN1, PLMN2, and PLMN3 after the 5G network of the first PLMN fails; if the 5G network in the PLMN1, the PLMN2 or the PLMN3 is successfully injected, the 5G network in the PLMN1, the PLMN2 or the PLMN3 provides service for the terminal equipment; if the 5G network in each PLMN fails to perform network sharing, further attempting to perform network sharing on the 4G network in each PLMN; if the network injection of the 4G network in each PLMN is successful, the 4G network provides service for the terminal equipment; if the 4G network in each PLMN fails to be injected uniformly, further attempting to inject the network in the 3G network in each PLMN, and if the 3G network in each PLMN is successful, providing service for the terminal equipment by the 3G network; if the 3G network in each PLMN fails to be injected, further attempting to inject the network in the 2G network in each PLMN, and if the 2G network in each PLMN is successful, providing service for the terminal equipment by the 2G network; if the 2G network in each PLMN fails, the network fails.

In the above implementation manner, when the current first network cannot be successfully injected, other PLMNs are moved to perform network injection, and when the networks are injected in each PLMN, the network type priority is prioritized, so that the terminal device can inject the network to the network with higher network type priority as much as possible, and the service quality can be preferentially ensured.

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

attempting to annotate the network at one other PLMN in response to a change in priority of the first network; if the network injection fails, the network of the next other PLMN tries to perform the network injection; until successful network injection to the target network or failure in other PLMNs.

For example, if PLMN1, PLMN2 and PLMN3 other than the first PLMN where the first network is located exist and are available for the terminal equipment to attempt access, and the priority of PLMN1, PLMN2 and PLMN3 is sequentially higher than PLMN2 and higher than PLMN3 from higher to lower, then the terminal equipment may attempt to annotate the network in PLMN1 after the first network fails to annotate the network; if the network injection in the PLMN1 is successful, providing service for the terminal equipment by the network of the PLMN 1; if the network injection fails in the PLMN1, further attempting to inject the network in the PLMN2 can be tried; if the network injection in the PLMN2 is successful, providing service for the terminal equipment by the network of the PLMN 2; if the network injection in the PLMN2 fails, the network injection in the PLMN3 can be further tried, and if the network injection in the PLMN3 is successful, the network of the PLMN3 provides service for the terminal equipment; if the network injection fails in the PLMN3, the network injection fails in other PLMNs.

In the implementation manner, when the network cannot be successfully injected in the first PLMN where the current first network is located, the network injection is performed to other PLMNs, and when the network injection is performed in each PLMN, the network type priority is considered, so that the terminal equipment can inject the network as much as possible to the network with higher network type priority in other PLMNs, the service quality can be preferentially ensured to a greater extent, and the probability of successful network injection is improved.

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

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

Optionally, in the network injection method provided by the embodiment of the present invention, after the terminal device attempts to inject the network in the second network, if the terminal device successfully injects the network to the target network (may be a network of the same PLMN as the first network or a network that does not communicate with the first network), the priority of the target network is determined; if the priority of the target network is smaller than that of the first network, determining the residual duration of the congestion timer T3346; after the remaining period of time, an attempt is made to annotate the network on 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, an attempt is made to annotate the network on the first network.

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

Alternatively, before the terminal device attempts to annotate the network with the second network, the terminal device may record the previous first network (or first PLMN), e.g. the identity of the first network may be saved 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 the injection.

Since the terminal device needs to prioritize the network to be injected to the network with high priority, after switching from the first network to the network to be injected to the target network, in the case that the priority of the target network is low, after the remaining duration of the congestion timer T3346, that is, after the time-out of the T3346 timer, the terminal device tries to return to the first network to perform the network injection to return to the network with high priority.

Optionally, after the first PLMN network fails in the first network, or after the other PLMNs fail in the second network, the terminal device may start a waiting timer, where the 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 annotate the network or request 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 execute the step of attempting to perform the network injection on the second network after the waiting timer times out;

the congestion relief message is used for indicating network congestion relief of the first network.

Optionally, in the embodiment of the present invention, power consumption of the terminal device may be considered, and a 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 power consumption of the terminal device is saved; the shorter the duration of the waiting timer is set, the greater the power consumption of the terminal device.

Optionally, in the embodiment of the present invention, during the process of attempting to perform the network injection on the second network (including the process of injecting the network on the first PLMN where the first network is located and the process of injecting the network on other PLMNs), if the congestion timer T3346 expires, stopping the current process of attempting to perform the network injection, and returning to attempt to perform the network injection on the first network.

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

The notification message may further carry a name of the first network of the annotated network, and other information (e.g., tariff information) of the first network.

Alternatively, in case the terminal device tries to record a first network (or a first PLMN) before it can play back in the second network, the record for the first network or the first PLMN may be deleted after receiving the congestion release message.

According to the implementation mode, in the process of injecting the network through the second network, aiming at the situation that the waiting timer is not overtime or still resides 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 injecting the network, so that the problem that the terminal equipment cannot provide the network for a long time can be avoided, and meanwhile, the network switching is ensured to be avoided to the greatest 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 a non-network injection state and a scenario 2 in which the terminal device is in a network injection state.

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

501. the network device detects the first network signaling congestion and decides to initiate congestion control.

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

The registration request message is used for requesting to perform network casting on 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 network congestion occurs in the first network and rejecting the terminal equipment to perform network injection in the first network.

Alternatively, the terminal device may receive a registration rejection message sent by the network device, and after the terminal device receives the registration rejection message, 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, or the network device may send the duration indication information as a separate message to the terminal device.

Optionally, the network device may inform the terminal device that the first network is congested through the reason value #22 (Congestin) of rejecting service in the registration reject message, and carries a value indication (back-off timer T3346 value IE) of the duration of the T3346 timer, so that when the terminal device receives the registration reject message, it may be known that the network device is congested, and it is unable to perform network injection on the first network, and it is required to start the T3346 timer, and retry to perform network injection on the first network after the T3346 timer times out.

504. The terminal device starts a T3346 timer.

Alternatively, 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 indication of the network device, e.g., the back-off timer T3346 value IE described above.

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

(3) The duration of the T3346 timer is configured according to the preset duration.

The preset duration may be configured in a mode specified by a standard protocol, or the preset duration may be configured in a mode indicated by a network device, or the preset duration may be configured by a terminal device in a user-defined mode.

505. When the target condition is met, the terminal device modifies the first priority of the first network to the 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 T3346 timer to timeout, so as to trigger the terminal device to respond to the change of the priority of the first network and attempt to perform the network injection in other networks.

Since the terminal device will normally prioritize the network to the higher priority network, after modifying the priority of the first network to a lower priority, the terminal device may be triggered to attempt to register to another network with a higher priority than the second priority.

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

1) Currently unregistered to the first network;

2) Is not currently registered with the first network and the congestion timer T3346 remains longer than a preset duration.

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

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

Alternatively, the terminal device may wait for the congestion timer T3346 to timeout or wait for network congestion relief of the first network when the target condition is not satisfied.

In this embodiment, aiming at the scene that the terminal device does not annotate the network currently, when the terminal device tries to annotate the network, the terminal device can be triggered by modifying the priority, and the terminal device tries to annotate the network to other networks, 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 the scene.

As shown in fig. 6, an embodiment of the present invention provides a method for injecting a net, which includes:

601. the network device detects the signaling congestion and decides to initiate 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 reject message to the terminal device.

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

Alternatively, the terminal device may receive a service rejection message sent by the network device, and after the terminal device receives the service rejection message, 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 the service request rejection message or the deregistration request message, and the network device may also send the duration indication information to the terminal device as a separate message.

Optionally, the network device may inform the terminal device that the first network is congested through the reason value #22 (Congestin) of rejecting the service in the service reject message, and carries a value indication (back-off timer T3346 value IE) of the duration of the T3346 timer, so that when the terminal device receives the service reject message, it may be known that the network device is congested, and it is unable to provide service for the terminal device, and it is required to start the T3346 timer, and retry to request the first network to provide service for the terminal device after the T3346 timer times out.

604. The terminal device starts a T3346 timer.

The configuration of the duration of the T3346 timer may be referred to the related description in 504, which is not repeated here.

605. When the target condition is met, the terminal device modifies the first priority of the first network to the second priority.

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

1) Currently registered with the first network and there is a user service request;

2) The method comprises the steps that the congestion timer T3346 is registered to a first network at present, a user service request exists, and the residual time length of the congestion timer T3346 is longer than the preset time length;

3) The first network is currently registered and the congestion timer T3346 remains longer than a preset duration.

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

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

In this embodiment, aiming at the scene that the terminal device has been injected into the network currently, when the terminal device requests a service, the service request caused by congestion at the network side is refused, the terminal device can be triggered by modifying the priority, and the terminal device tries to inject the network to other networks, thereby solving the problem that the network device cannot provide the service for the terminal device in a long time due to the existing congestion control mechanism in the scene, and the terminal device cannot provide the service for the user.

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

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

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

The first network is a network which tries to annotate the network at present or is already annotated; 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 PLMNs.

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 the first network is congested; 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 the congestion timer T3346, and modify the first priority of the first network to 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 the first priority of the first network to the second priority when the target condition is met;

meeting the target condition includes one of:

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

The method comprises the steps that the user service request exists when the user service request is registered to a first network currently, and the residual time length of a congestion timer T3346 is longer than the preset time length;

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

currently unregistered to the first network;

is not currently registered with the first network and the congestion timer T3346 remains longer than a preset duration.

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

if the network injection fails, the next network of the first PLMN tries to perform the network injection;

until successful network injection to the target network or failure of network injection in 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 attempt to perform a network injection on a network of one other PLMN in response to a change in priority of the first network;

if the network injection fails, the network of the next other PLMN tries to perform the network injection;

Until successful network injection to the target network or failure in other PLMNs.

Optionally, the processing module 701 is further configured to determine a priority of the target network after the successful network injection to the target network; if the priority of the target network is smaller than that of the first network, determining the residual duration of the congestion timer T3346; after the remaining period of time, an attempt is made to annotate the network on 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, an attempt is made to annotate the network on the first network.

Optionally, the processing module 701 is further configured to start a waiting timer after the first PLMN fails to network, or after the other PLMNs fail to network, where the 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, attempting to annotate or request service on the first network;

if the congestion relief message is not received within the duration of the waiting timer, repeating the step of attempting to perform network injection on the second network after the waiting timer is overtime;

Optionally, the processing module 701 is further configured to, in response to a change in the priority of the first network, after attempting to perform the network injection on the second network, if the congestion timer T3346 expires during the process of attempting to perform the network injection on the second network, stop the current process of attempting to perform the network injection; an attempt is made to play a mesh over a first network.

Optionally, the processing module 701 is specifically configured to output first query information when the first network is congested, where the first query information is used to query the user whether to re-perform network selection;

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

the first priority of the first network is modified to a second priority in response to the 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 annotate the network preferentially to other PLMNs;

the processing module 701 is specifically configured to receive an input from a user regarding a first option, where the first option is an option indicating that access to a network of another PLMN is preferentially attempted.

an option to indicate waiting for network congestion relief;

indicating an option to prioritize network injection to networks of other PLMNs;

indicating an option to prioritize network injection to networks of other network formats.

The processing module 701 is specifically configured to receive an input from a user regarding a target option, where the target option is an option indicating that access to a network of another PLMN is preferentially attempted, or an option indicating that network injection is preferentially attempted to a network of another network system.

Optionally, the processing module 701 is further configured to output a first prompting message when the first network is congested, where the first prompting message is used to prompt the first network to congestion, and the first prompting 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 processing module 701 is further configured to output a second prompting message when the first network is congested, where the second prompting message is used to prompt the user that the tariff will be changed after the network selection is performed again.

The embodiment of the invention also provides a terminal device, which can include a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program can realize each process executed by the terminal device in the method embodiment when being executed by the processor, and can achieve the same technical effect, and for avoiding repetition, the description is omitted here.

Fig. 8 is a schematic 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 (wireless fidelity, wiFi) module 870, processor 880, and power supply 890. Wherein the radio frequency circuit 810 includes a receiver 811 and a transmitter 812. Those skilled in the art will appreciate that the handset configuration shown in fig. 8 is not limiting of the handset and may include more or fewer components than shown, or may combine certain components, or may be arranged in a different arrangement of components.

The RF circuit 810 may be used for receiving and transmitting signals during a message or a call, and in particular, after receiving downlink information of a base station, it is processed by the processor 880; in addition, the data of the design uplink is sent to the base station. Typically, the RF circuitry 810 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (low noise amplifier, LNA), a duplexer, and the like. In addition, the RF circuitry 810 may also communicate with networks and other devices via wireless communications. The wireless communications may use any communication standard or protocol including, but not limited to, global system for mobile communications (global system of mobile communication, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), long term evolution (long term evolution, LTE), email, short message service (short messaging service, SMS), and the like.

The memory 820 may be used to store software programs and modules, and the processor 880 performs various functional applications and data processing of the cellular phone by executing the software programs and modules stored in the memory 820. The memory 820 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, 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 to generate key signal inputs related to user settings and function controls of the handset. In particular, 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, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 831 or thereabout using any suitable object or accessory such as a finger, stylus, etc.), and actuate the corresponding connection device according to a predetermined program. Alternatively, the touch panel 831 may include two portions of a touch detection device and a touch controller. The touch detection device detects the touch azimuth 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 detection device and converts it into touch point coordinates, which are then sent to the processor 880 and can receive commands from the processor 880 and execute them. In addition, the touch panel 831 may be implemented in various types of resistive, capacitive, infrared, surface acoustic wave, and the like. 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 (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.

The display unit 840 may be used to display information input by a user or information provided to the user and various menus of the mobile phone. The display unit 840 may include a display panel 841, and optionally, the display panel 841 may be configured in the form of a liquid crystal display (liquid crystal display, LCD), an organic light-Emitting diode (OLED), or the like. Further, the touch panel 831 may overlay the display panel 841, and when the touch panel 831 detects a touch operation thereon or thereabout, the touch operation is transferred to the processor 880 to determine the type of touch event, and the processor 880 then provides a corresponding visual output on the display panel 841 according to the type of touch event. Although in fig. 8, the touch panel 831 and the display panel 841 are implemented as two separate components to implement the input and input 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 a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 841 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 841 and/or the backlight when the mobile phone moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for applications of recognizing the gesture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured with the handset are not described in detail herein.

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

WiFi belongs to a short-distance wireless transmission technology, and a mobile phone can help a user to send and receive emails, browse webpages, access streaming media and the like through a WiFi module 870, so that wireless broadband Internet access is provided for the user. Although fig. 8 shows a WiFi module 870, it is understood that it does not belong to the necessary constitution of the handset, and can be omitted entirely as needed within the scope of 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 running or executing software programs and/or modules stored in the memory 820 and calling data stored in the memory 820, thereby performing overall monitoring of the mobile phone. In the alternative, processor 880 may include one or more processing units; preferably, the processor 880 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 880.

The handset further includes a power supply 890 (e.g., a battery) for powering the various components, which may be logically connected to the processor 880 through a power management system, as well as performing functions such as managing charge, discharge, and power consumption by the power management system. Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which will not be described herein.

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

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 the first network has network congestion; 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;

meeting the target condition includes one of:

currently unregistered to the first network;

Optionally, the first network and the second network are networks with different network systems of the first PLMN, and the processor 880 is specifically configured to attempt to perform a network injection on 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 attempt to annotate the network of one other PLMN in response to a change in priority of the first network;

Optionally, the processor 880 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 smaller than that of the first network, determining the residual duration of the congestion timer T3346; after the remaining period of time, an attempt is made to annotate the network on the first network.

Optionally, the processor 880 is specifically configured to 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;

Optionally, the processor 880 is further configured to start a waiting timer after the first PLMN fails to network, or after the other PLMNs fail to network, where the duration of the waiting 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, attempt to perform the network injection on the second network, and if the congestion timer T3346 expires during the attempt to perform the network injection on the second network, stop the current attempt to perform the network injection process; an attempt is made to play a mesh over 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 the first network congestion occurs, where the first query information is used to query the user whether to re-perform network selection; and controlling the RF circuitry 810 to receive a first selection input by a user for the first query information, the first selection input for confirming re-execution of the network selection; the first priority of the first network is modified to a second priority in response to the 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;

the processor 880 is specifically configured to control the RF circuit 810 to receive user input for a first option indicating a priority to attempt to access a network of another PLMN.

an option to indicate waiting for network congestion relief;

The processor 880 is specifically configured to receive, via the RF circuit 810, user input regarding a target option, where the target option is an option indicating a preference for attempting to access a network of another PLMN or an option indicating a preference for attempting to annotate a network of another network system.

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

Optionally, the processor 880 is further configured to output a second prompting message through the display unit 840 or the audio circuit 860 when the first network is congested, where the second prompting message is used to prompt the user that the tariff will be changed after re-performing the network selection.

The embodiment of the invention provides a computer readable storage medium, which is characterized in that the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program realizes each process executed by a terminal device in the embodiment of the method, and can achieve the same technical effect, so that repetition is avoided, and no redundant description is provided herein.

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

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 one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method of the embodiments of the present invention.

The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.

Claims

1. The network injection method is characterized by being applied to terminal equipment and comprising the following steps of:

the first network is a network which is currently tried to be annotated, or a network which is already annotated; 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 PLMNs;

when the first network is congested, modifying the first priority of the first network to the second priority, including:

When the first network is congested, outputting first inquiry information, wherein the first inquiry information is used for inquiring whether a user re-executes network selection; 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 the first priority of the first network to the second priority in response to the first selection input;

the method further comprises the steps of:

after the user makes an input of whether to re-perform network selection according to the first inquiry information, a selection record of the user is saved so that the user changes options indicated by the selection record through an interface configured by the terminal equipment.

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 network congestion occurs in the first network; modifying the first priority of the first network to the second priority.

4. A method according to 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 to the second priority.

5. The method according to claim 4, wherein the method further comprises:

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 a second priority comprises:

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

the meeting the target condition includes one of:

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

Currently registered to the first network, and the congestion timer T3346 is longer than a preset time period;

currently unregistered with the first network;

7. The method of claim 6, wherein the first network and the second network are networks of different network types of the first PLMN, wherein attempting to annotate at the second network in response to a change in priority of the first network comprises:

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

if the network injection fails, attempting to perform the network injection on the next network of the first PLMN;

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

8. The method of claim 6, wherein the first network and the second network are networks of different PLMNs, the attempting to annotate on the second network in response to a change in priority of the first network comprising:

Attempting to annotate at a network of one other PLMN in response to a change in priority of the first network;

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

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

determining the priority of the target network;

if the priority of the target network is smaller than that of the first network, determining the residual duration of the congestion timer T3346;

after the remaining time period, an attempt is made to annotate the network on the first network.

10. The method of claim 9, wherein said attempting to annotate on said first network after said remaining period of time 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;

after the back-off timer expires, an attempt is made to annotate the network at the first network.

11. The method of claim 7, wherein after the first PLMN implantation failure, further comprising:

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

if a congestion relief message is received within the duration of the wait timer, attempting to annotate or request service on the first network;

12. The method of claim 8, wherein after the other PLMN network injection failure, further comprising:

13. The method of claim 6, wherein attempting to place a mesh in a second network after the priority of the first network is changed comprises:

if the congestion timer T3346 is overtime in the process of trying to annotate the network in the second network, stopping the current process of trying to annotate the network;

an injection is attempted over the first network.

14. The method of claim 1, wherein outputting the first query information comprises:

the following option information is output:

an option to indicate waiting for network congestion relief;

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

An input from a user is received for a first option, the first option being the option indicating a priority to attempt access to a network of another PLMN.

15. The method of claim 1, wherein outputting the first query information comprises:

the following option information is output:

an option to indicate waiting for network congestion relief;

indicating an option to prioritize network injection to networks of other network formats;

and receiving input of a user aiming at a target option, wherein the target option is an option for indicating to preferentially try to access networks of other PLMNs, or an option for indicating to preferentially try to annotate networks to networks of other network systems.

16. The method as recited in claim 6, further comprising:

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

17. The method as recited in claim 1, further comprising:

and when the first network is congested, outputting a second prompting message, wherein the second prompting message is used for prompting the user to change tariffs after re-executing network selection.

18. A terminal device, comprising:

the processing module is used for outputting first inquiry information when the first network is congested, wherein the first inquiry information is used for inquiring whether a user re-executes network selection; 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; attempting to place a mesh on a second network in response to a change in priority of the first network;

A module for performing the following operations:

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

20. A computer-readable storage medium, comprising: the computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of casting a net as claimed in any one of claims 1 to 17.